Chapter 5: Traffic Port Management

Table Of Contents

Traffic Port Management

5.1  About Port Types

5.2  Selecting a Traffic Port

5.3  SDH Ports

5.3.1  Configuring ONS 15305 SDH Port Structure (Channelization)

5.3.2  Modifying or Removing ONS 15305 SDH Port Structure

5.3.3  Setting and Reading Path Trace Identifiers

5.3.4  Monitoring SDH Port Performance

5.3.5  Enabling the SDH Port to Carry Traffic and Report Alarms

5.3.6  ONS 15305 SDH Port Synchronization Quality Output Signaling

5.3.7  Use the SDH Port as a Synchronization Source Input

5.3.8  Carry Management Traffic DCC by SDH Port Channels

5.4  PDH Ports

5.4.1  Setting the Port Mode for ONS 15305

5.4.2  Setting a Loop in an ONS 15305 PDH Port

5.4.3  Setting a Loop in an ONS 15302 PDH port

5.4.4  Releasing a Loop in a PDH Port

5.4.5  Assign VC12s in ONS 15302

5.4.6  Setting and Reading Path Trace Identifiers

5.4.7  Monitoring PDH Port VC-n Performance

5.4.8  Monitoring PDH E1 Port Performance

5.4.9  Enabling the PDH Port to Carry Traffic and Report Alarms

5.4.10  Cross-connect the ONS 15305 PDH Port to another Port

5.5  LAN Ports

5.5.1  ONS 15305 - LAN Port Attributes

5.5.2  ONS 15302 LAN Port Attributes

5.6  ONS 15305 SDH Cross-Connection Management

5.6.1  SDH Layer Network and Cross Connections

5.6.2  Open the Cross Connection GUI

5.6.3  Browsing Existing Cross-connections

5.6.4  Setting up Cross-connections

5.6.5  Modifying Cross Connections

5.6.6  Protecting Cross Connections

5.6.7  Deleting Cross-connections

5.6.8  Advanced Cross-connection Operations

5.7  ONS 15305 SDH Protection Management

5.7.1  Introduction

5.7.2  Protect Section by MSP

5.7.3  Modify MSP

5.7.4  Delete MSP

5.7.5  Command MSP Switch

5.7.6  Legal combinations of SNCP and MSP

5.7.7  SubNetwork Connection Protection

5.8  ONS 15302 SDH Protection Management

5.8.1  Multiplex Section Protection

5.9   Ethernet Standardized Mapping

5.9.1  Introduction

5.9.2  GFP Alarm and Event Conditions

5.9.3  GFP Performance Monitoring

5.9.4  VCAT - Virtual Concatenation

5.9.5  VC Level for VCAT

5.9.6  LCAS- Link Capacity Adjustment Scheme

5.9.7  VCAT and LCAS Alarms and Events

5.10  VCAT and LCAS Configuration Modes

5.10.1  VCAT with LCAS Enabled- Mode 1

5.10.2  VCAT Without LCAS Enabled- Mode 2

5.11  Administrative Bandwidth for VCAT

5.11.1  Bandwidth for uni-directional VCAT

5.12  Circuit Protection for VCAT

5.12.1  CirCuit Protection For Uni-directional Modes For ONS 15305

5.12.2  Circuit proTection For Symmetrical VCAT

5.13  Establish a standardized Mapping With CEC

5.14  Bi-directional VCAT Without LCAS

5.15  ONS 15305 Proprietary NxVC-12 EoS Mapping

5.15.1  Introduction

5.15.2  WAN to SDH mapping- Custom GUI

5.15.3  Add Initial WAN Port Capacity

5.15.4  Modify WAN Port Capacity

5.15.5  Protecting a WAN Port

5.15.6  Modifying Protection Parameters of the WAN Port

5.15.7  Commanding WAN Port Protection Switch

5.15.8  Setting Path Trace Identifiers for WAN Port

5.15.9  Reading Path Trace Identifiers for WAN Port

5.15.10  Monitoring WAN Port Performance

5.15.11  Advanced WAN Port Operations

5.16  ONS 15302 Proprietary NxVC-12 EoS Mapping

5.16.1  WAN ports and the Mapping

5.16.2  Differences between ONS 15305 and ONS 15302

5.16.3  Force LAN Down

5.16.4  Increase Capacity in the SDH Server Layer

5.16.5  Decrease Capacity in the SDH Server Layer

5.16.6  Setting Path Trace Identifiers for WAN Port

5.16.7  Reading Path Trace Identifiers for WAN Port

5.16.8  Monitoring WAN Port Performance

5.16.9  Advanced WAN Port Operations

Traffic Port Management

5.1  About Port Types

One of the advantages of the ONS 15305 compared to other products is the possibility to equip it with a number of different port types. Some ports are part of the base unit and always present, (management port, AUX ports, alarm input and output ports). The alarm ports and auxiliary port cannot be created or deleted.

See also the "4.2.1  Manage the Management Interfaces of the Network Element" section on page 4-2, the "Alarm Ports" section on page 4-35, and the "AUX Port - ONS 15305" section on page 4-36.

Traffic ports are available on replacable traffic modules. When a slot is configured to support a specific traffic module the ports of the traffic module is automatically created as described in the "4.11  Manage Slots on ONS 15305" section on page 4-85.

In this chapter we concentrate on the configuration of the traffic ports. The chapter is organized according to the following structure:

•SDH ports

•PDH ports

•LAN ports

•WAN ports

5.2  Selecting a Traffic Port

Traffic ports are always located on a traffic module in slot 1 to 4. In ONS 15305 managed objects for modules and ports are available when the slot is configured for a specific module type. This section describes how to select a traffic port regardless of the traffic it carries.

Step 1 Click on the ONS 15305 managed object, and then the slot managed object (where the port is) in the management tree.

Step 2 When the slot is expanded, click on the port managed object with the desired port number.

Step 3 The port is selected and the attributes related to the physical and electrical characteristics of the port is displayed in the attributes view.
The physical port usually carries a set of protocols (for example SDH) and the protocols are available from the management tree.

5.3  SDH Ports

Note Some procedures in this chapter apply for both ONS 15302 and ONS 15305. For procedures that only apply for ONS 15305, this is stated in the procedure heading.

5.3.1  Configuring ONS 15305 SDH Port Structure (Channelization)

By default the SDH ports are unstructured (or not-channelized) when created. Only the SDH port, rs, ms and aug1 managed objects are available. In this state the paths inside the STM-N frame cannot be terminated nor cross-connected, but the port can be used as a protection port in an MSP protection scheme and as a synchronization source candidate. It can also carry DCN traffic in the DCC channels.

The motivation for structuring an SDH port is to identify the paths in the STM-N frame and make them available for cross-connection. As you structure the port it will fan out in the management tree, showing termination points that are now available for cross-connection.

5.3.1.1  SDH Structuring Wizard

This wizard lets you to change the structure of an SDH object. The next steps let you set up the type of structure you want.

Figure 5-1 Open The Structuring Wizard

Step 1 Select desired SDH port

Step 2 Right-click and select Structure.

Figure 5-2 SDH Structuring Wizard

No changes will be performed until you press Finish and you can abort the wizard at any given time by pressing the Cancel button.

Structure Information displays the current SDH structure. The decisions you make in subsequent steps will affect this structure

Structure Type; Select the type of SDH structure you want.

Completing the Structure SDH Structuring Wizard; This step lists all the changes that will be performed when you press Finish.

The following sections show how to perform structuring using the Management Tree.

5.3.1.2  AU4 Termination Points for Cross-connection

Step 1 Select an SDH port, Figure 5-3.

Step 2 Select the rs and then the ms managed objects as the port expands.

Step 3 Select the aug1 managed object that should be structured. (STM-N ports have N aug1 objects).

Figure 5-3 Select the Aug1 Managed Object

Step 4 Set the Structure attribute to au4ToCrossConnect, Figure 5-4.

Figure 5-4 Set the Structure Attribute

Step 5 Click Save on the toolbar.

Step 6 Repeat for the other aug1 objects on the port if you want to structure them as au4ToCrossconnect.

5.3.1.3  Tu3 Termination Points for XC

Tu3 termination points for XC.

Step 1 Perform Step 1 to Step 3 in the "AU4 Termination Points for Cross-connection" section.

Step 2 Set the Structure attribute to tug3x3.

Step 3 Select the au4, vc4 and then the tug3 managed object that should be structured.

Step 4 Set the structure attribute to tu3ToCrossConnect.

Step 5 Click Save on toolbar.

Step 6 Repeat for the other tug3 objects on the port if you want to structure them as tu3ToCrossconnect.

5.3.1.4  Tu12 Managed Objects for XC

Tu12 managed objects for XC.

Step 1 Perform Step 1 to Step 3 in the "AU4 Termination Points for Cross-connection" section.

Step 2 Set the Structure attribute of the tug3 managed object to tu12x21.

Step 3 Click Save on the toolbar.

Step 4 Repeat for the other tug3 objects on the port if you want to structure them as x21tu12.

5.3.2  Modifying or Removing ONS 15305 SDH Port Structure

It is also possible to modify or remove the structure of an SDH port when the involved termination points are not cross-connected.

5.3.2.1  Modify between Tu12 and Tu3 Objects

Modify between Tu12 and Tu3 objects.

Step 1 Remove all cross-connections that are terminated in the tu12 or tu3 termination points belonging to the tug3 object that you want to modify.

Step 2 Follow the guidelines in "Configuring ONS 15305 SDH Port Structure (Channelization)" section, to make tu3 or tu12 termination points of an SDH port available for cross-connection.

5.3.2.2  Modify between Au4 and Tu3 or Tu12 Objects

How to modify between Au4 and Tu3 or Tu12 objects.

Step 1 Remove all cross-connections that are terminated in the au4, tu12 or tu3 termination points belonging to the aug1 object that you want to modify.

Step 2 Set the tug3 Structure to unStructured for all tug3 objects contained by the aug1 object that should be modified, "Modify between Tu12 and Tu3 Objects" section.

Step 3 Follow the guidelines in "Configuring ONS 15305 SDH Port Structure (Channelization)" section, to make au4, tu3 or tu12 termination points of an SDH port available for cross-connection.

Note Modification of the structure involves deletion of existing termination points and creation of new termination points (if new structure is not unStructured). To avoid unintentional traffic loss, ONS 15305 will not allow modification of the structure before all cross-connections belonging to a structure object have been deleted.

Note The structure of all contained tug3 objects must have been set to unStructured before the aug1 can be modified.

5.3.3  Setting and Reading Path Trace Identifiers

Path Trace are available at two levels in the SDH port:

•RS path trace that will be terminated in the STM-N port on the opposite side of the link.

•VC-4 Path Trace that will be terminated in the SDH node terminating the VC-4 path.

5.3.3.1  Set or Read RS Path Trace Identifiers

How to set or read RS path trace identifiers:

Step 1 Select an SDH port.

Step 2 When the SDH port managed object is expanded, click on the rs.

Step 3 Click on PathTrace.

Step 4 The following attributes can be set:

•PathTrace

Set to enable if TIM alarms should be reported when there is a mismatch between. PathTraceReceived and PathTraceExpected.

•PathTraceExpected

Enter a value for the path trace identifier that you expect to receive from the other side of the path.

•PathTraceTransmitted

Enter a value for the path trace identifier that you want to transmit to the other side of the path.

Step 5 The following attributes can be read:

•PathTraceReceived

The actual received path trace identifier from the other side of the link.

Step 6 Click Save on the toolbar.

5.3.3.2  Set or Read VC-4 Path Trace Identifiers

Note VC4 path trace is available only when the SDH port is structured with a VC-4 object, that means aug1 Structure is tug3x3, "Configuring ONS 15305 SDH Port Structure (Channelization)" section.

Step 1 Select an SDH port.

Step 2 Select the rs and then the ms managed objects as the port expands.

Step 3 Select the aug1 managed object that contains the vc4 to measure.

Step 4 Select the au4 and then the vc4 managed objects as the port expands.

Step 5 Click on PathTrace.

The attributes are the same as for RS path trace Step 4.

Step 6 Click Save on the toolbar after setting the path trace parameters.

Note When path trace is set to enabled, AIS is inserted downstream instead of the original signal when there is a mismatch between expected and received path trace.

5.3.4  Monitoring SDH Port Performance

Performance Monitoring is available at three levels in the SDH port:

•RS PM, monitoring near end of the regenerator section.

•MS PM, monitoring near and far end of the multiplexer section.

•VC-4 PM, monitoring near and far end of the VC-4 path.

5.3.4.1  Read RS PM Counters

How to read rs pm counters

Step 1 Select an SDH port.

Step 2 When the SDH port managed object is expanded, select the rs managed object.

Step 3 Click on the vc12 (for e1 ports) or vc3 (for e3 ports) managed object.

Step 4 Click on PmG826NearEnd to read near end PM data or PmG826FarEnd to read far end PM data.

Step 5 The following attributes are available:

•Current15Min ES,SES, BBE and UAS

•Current24Hour ES, SES, BBE and UAS

Step 6 To see the performance history of the previous 16x15 minute counters click on Interval15Min, or click on Interval24Hour to see the previous 24 hour counter.

Step 7 The following attributes are available:

•Interval15Min ES,SES, BBE and UAS

•Interval24Hour ES, SES, BBE and UAS

5.3.4.2  Read MS PM Counters

How to read ms pm counters

Step 1 Select an SDH port.

Step 2 Select the rs and then the ms managed objects as the port expands.

Step 3 Click the PMG826 link for PmG826NearEnd to read near end PM data or PmG826FarEnd to read far end PM data.

Step 4 The attributes are the same as for RS PM.

5.3.4.3  Read VC-4 PM Counters

How to read VC-4 pm counters

Step 1 Select an SDH port.

Step 2 Select the rs and then the ms managed objects as the port expands.

Step 3 Select the aug1 managed object that contains the vc4 to measure.

Step 4 Select the au4 and then the vc4 managed objects as the port expands.

Step 5 Click the PMG826 link for PmG826NearEnd to read near end PM data or PmG826FarEnd to read far end PM data.

Step 6 The attributes are the same as for RS PM in "Read RS PM Counters" section.

5.3.5  Enabling the SDH Port to Carry Traffic and Report Alarms

By default the Administrative Status of the SDH port is set to disabled when the port is created. No alarms are reported before it is enabled.

Step 1 Select an SDH port.

Step 2 Set AdminStatus to enabled.

Step 3 Click Save on the toolbar.

Note If disabled, the following applies:
- No alarms are reported towards the port.
- PM counters for the port will only count 0.
- If the port is part of MSP, the port will not be selected for traffic (unless this is a working port and the protecting port also is disabled or has SPI/RS/MS alarm).

Note Even if the SDH port is enabled it will only report alarms if the AlarmReporting attribute of the slot is set to enabled.

5.3.6  ONS 15305 SDH Port Synchronization Quality Output Signaling

STM-N signals are often used to carry synchronization information. A dedicated protocol is used to indicate the quality of the signal that is output from one SDH node to the next SDH node.

Step 1 Select an SDH port.

Step 2 Set EgressSSM to t0 or doNotUse. T0 will always indicate the quality status of the internal clock.

Step 3 Click Save on the toolbar.

Note When an SDH port is used as a synchronization source candidate, the S1 byte will be set to DoNotUse automatically.

5.3.7  Use the SDH Port as a Synchronization Source Input

See the "4.6.4  Add Synchronization Source Candidate (T0 or T4)" section on page 4-44.

5.3.8  Carry Management Traffic DCC by SDH Port Channels

See the "4.3.2  DCC Configuration" section on page 4-17.

5.4  PDH Ports

ONS 15305 can be equipped with two different PDH port types:

•E1 Ports (2 Mbps) supporting transparent data and NT functionality of ISDN PRA. E1 Ports are available when the slot is configured for the 8xE1 module or the 63xE1 module.

•E3 Ports (34/45 Mbps) supporting transparent data. E3 Ports are available when the slot is configured for the 6xE3 module.

ONS 15302 is equipped with E1 ports.)

5.4.1  Setting the Port Mode for ONS 15305

How to set the port mode for ONS 15305:

Step 1 Select a PDH port, Figure 5-5.

Step 2 When the PDH port managed object is expanded, select the e1 or e3 managed object.

Step 3 For e1 ports set the E1Mode attribute to tra (2 Mbps transparent G.703), pra (ISDN PRA) or
pra-fixed ( ISDN primary rate access with fixed timing)

Figure 5-5 Set the E1 Mode Attribute

.

Step 4 For e3 ports set the E3Mode attribute to e3 (34 Mbps transparent G.703) or t3 (45 Mbps) transparent G.703).

Step 5 Click Save on the toolbar.

5.4.2  Setting a Loop in an ONS 15305 PDH Port

How to set a loop in an ONS 15305 PDH port

Step 1 Select a PDH port, Figure 5-6.

Step 2 When the PDH port managed object is expanded, select the e1 or e3 managed object.

Step 3 Set the Admin Loop Mode attribute to ll2 (loop back to network) or ll3 (loop back to customer).

Figure 5-6 Set Admin Loop Mode Attributes

Step 4 Click Save on the toolbar.

Note There are a number of restrictions for setting the loops of PDH ports. Cisco Edge Craft cannot set and release loops when the E1Mode is set to pra. (in this mode loops can only be managed from an NT1 or similar). A loop cannot be set when PDH port AdminStatus is set to disabled.

5.4.3  Setting a Loop in an ONS 15302 PDH port

How to set a loop in an ONS 15302 PDH port

Step 1 Select desired PDH port.

Step 2 When the PDH port managed object is expanded, select the e1 managed object.

Step 3 Set the AdminLoopMode attribute to ll2 (loop back to network) or ll3 (loop back to customer).

Step 4 Click Save on the toolbar.

5.4.4  Releasing a Loop in a PDH Port

Release a loop in a PDH port:

Step 1 Select a PDH port.

Step 2 When the PDH port managed object is expanded, select the e1 or e3 managed object.

Step 3 Set the AdminLoopMode attribute to noLoop.

Step 4 Click Save on the toolbar.

Note Alternatively, any loop will be released if PDH port AdminStatus is set from enabled to disabled.

5.4.5  Assign VC12s in ONS 15302

Assign VC12s in ONS 15302:

Step 1 Expand desired PDH port in the management tree, to view VC12 managed object attributes, Figure 5-7.

Step 2 Set AssignedCbklm to desired value, Figure 5-7.

You can use the WAN to SDH mapping window to view available VC12s with cbklm values.

Step 3 Click Save.

Figure 5-7 Assign VC 12 Por

t

5.4.6  Setting and Reading Path Trace Identifiers

Set and read path trace identifiers

Step 1 Select a PDH port.

Step 2 When the PDH port managed object is expanded, click on the e1 or e3 managed object.

Step 3 Click on the vc12 (E1) or vc3 (E3) managed object.

Step 4 Click on PathTrace.

The following attributes can be set:

•PathTrace

Set to enable if TIM alarms should be reported when there is a mismatch between PathTraceReceived and PathTraceExpected.

•PathTraceExpected

Enter a value for the path trace identifier that you expect to receive from the other side of the path.

•PathTraceTransmitted

Enter a value for the path trace identifier that you want to transmit to the other side of the path.

Step 5 The following attributes can be read:

•PathTraceReceived

The actual received path trace identifier from the other side of the link.

Step 6 Click Save on the toolbar.

Note When path trace is set to enabled, AIS is inserted downstream instead of the original signal when there is a mismatch between expected and received path trace.

5.4.7  Monitoring PDH Port VC-n Performance

Monitor PDH port VC-n performance:

Step 1 Select a PDH port.

Step 2 When the PDH port managed object is expanded, select the e1 or e3 managed object.

Step 3 Click on the vc12 (for e1 ports) or vc3 (for e3 ports) managed object.

Step 4 Click on the PMG826 link for PmG826NearEnd to read near end PM data or PmG826FarEnd to read far end PM data.

Step 5 The following attributes are available:

•Current15Min ES, SES, BBE and UAS

•Current24Hour ES, SES, BBE and UAS

Step 6 To see the Performance history of the previous 16x15 minute counters click on Interval15Min, or click on Interval24Hour to see the previous 24 hour counter, Figure 5-8 and Figure 5-9.

Step 7 The following attributes are available

•Interval15Min ES, SES, BBE and UAS

•Interval24Hour ES, SES, BBE and UAS

Figure 5-8 Select Interval24Hour

Figure 5-9 Set Interval24Hour Attributes

5.4.8  Monitoring PDH E1 Port Performance

The E1 counters are based on CRC-4 counters for near end and E-bit counters for far end monitoring.

Defect criteria for near end is LOS-TX(Loss Of Signal), LOF-TX(Loss Of Frame) and module/slot alarms. For far end there are no alarms present to indicate any defects.

The valid flag for previous intervals and past 24 hours is set only when the port has been in PRA-mode during the whole period. For ports in TRA-mode, the PM counters can only be used to indicate SES/UAS due to LOS-TX or module/slot alarms.

Step 1 Select a PDH E1 port.

Step 2 When the PDH port managed object is expanded, select the e1 managed object.

Step 3 Click on the PMG826 link for PmG826NearEnd to read near end PM data or PmG826FarEnd to read far end PM data.

Step 4 The following attributes are available:

•Current15Min ES, SES, BBE and UAS

•Current24Hour ES, SES, BBE and UAS

Step 5 To see the Performance history of the previous 16x15 minute counters click on Interval15Min, or click on Interval24Hour to see the previous 24 hour counter.

Step 6 The following attributes are available

•Interval15Min ES, SES, BBE and UAS

•Interval24Hour ES, SES, BBE and UAS

5.4.9  Enabling the PDH Port to Carry Traffic and Report Alarms

By default the administrative status of the PDH port is set to disabled when the port is created. No traffic will pass through the port and no alarms are reported before it is enabled.

Step 1 Select a PDH port.

Step 2 Set AdminStatus to enabled.

Step 3 Click Save on the toolbar.

Note When disabled the PDH port generates AIS upstream and downstream.

5.4.10  Cross-connect the ONS 15305 PDH Port to another Port

See the "ONS 15305 SDH Cross-Connection Management" section.

5.5  LAN Ports

About port attributes and their modification options.

5.5.1  ONS 15305 - LAN Port Attributes

An ONS 15305 slot can for example be configured to carry an E100-WAN-8 module, see "4.11  Manage Slots on ONS 15305" section on page 4-85 for details.

Step 1 When the module is installed in the desired slot, click desired LAN port to view modifiable attributes, Figure 5-10.

Step 2 Attributes marked as bold are modifiable.

Figure 5-10 LAN Port Attributes

:

These Attributes are modifiable:

•AdminAutoNegotiationMode

disabled or enabled

•AdminBackPressureMode

disabled or enabled

•AdminFlowControlMode

on, off or auto negotiation

•AdminStatus

up, down or testing

•AssignPhysicalAddress

reserve or default

•Description

string

•DuplexAdminMode

none, half or full

•SpeedAdmin mode

not set, 10M, 100M or 1000M

Step 3 Click Save if attribute modifications are performed.

5.5.2  ONS 15302 LAN Port Attributes

The ONS 15302 is equipped with 4 LAN ports, Figure 5-11. For configuration of LAN ports see "ONS 15305 - LAN Port Attributes" section.

Figure 5-11 LAN Port Attributes - ONS 15302

5.6  ONS 15305 SDH Cross-Connection Management

The purpose of this section is to describe the tasks involved when managing cross connections between termination points on the network element.

The section involves management of the complete life cycle of a cross connection, including creation, presentation, modification, deletion and manual operation of the sub-network connection protection switch.

A cross connection is defined by its termination points. Only termination points with the same characteristic information can be cross-connected. The characteristic information of a termination point defines the format of the signal that can be transferred by this termination point. Format defines the capacity of the signal, for example TU-12 and VC-12 have the same characteristic information since they both have a 2 Mbps traffic capacity.

Unidirectional and bidirectional point to point cross connections with or without protection are supported.

The protection scheme supported by the first release of ONS 15305 is SNC/I, (inherent monitoring). ONS 15305 Release. 2.0 supports Non-intrusive monitoring SNC/N

The first part of this section gives a short introduction to SDH layers and cross connections which is meant to help the reader in understanding the requirements specified in this document. For further reading on SDH and cross connections, please see ITU-T Recommendations G-Series.

5.6.1  SDH Layer Network and Cross Connections

An SDH network has layered structure as depicted in Figure 5-12. The layers operate in a client/server based scenario. The service layer generates the bit streams that are to be carried across the SDH network. This layer is not part of SDH. The path layer is a virtual layer and can only be observed through a management system. It is in this layer that the cross connection management and structuring of the SDH ports are performed. The path layer works on containers.

Figure 5-12 SDH Layer Network

The ONS 15305 network element has support for VC-4 in the higher order layer and in the lower order layer VC-12 and VC-3.

5.6.1.1  SDH Port Structuring

The multiplexing structure of the SDH ports determine which layers and their termination points that are available to be cross connected. The multiplexing structure for SDH in all layers are shown in Figure 5-13 (taken from ITU-T Recommendation G.707.) The C.B.K.L.M value determines the path trough the structure. The usage of the C.B.K.L.M value follows the rules defined in Table 5-1.

Only traffic on non-terminated containers called connection termination points can be cross connected, that means AU-4, TU-3, and TU-12. The other containers, VC-4, VC-3, and VC-12, represent trail termination points where the traffic can be read.

Figure 5-13 SDH Multiplexing Structure

The original illustration used in Figure 5-13, is found in ITU-T G.707/Y1322 (10/2000).

C.B.K.L.M Value Usage

Table 5-1 C.B.K.L.M Value Usage

Rules

Examples

When referring to SDH objects the complete C.B.K.L.M value is used even if some fields are in-significant.

Not significant fields in C.B.K.L.M are set to 0.

AU-4 in STM-16: C.B.0.0.0
TU-3 in STM-16: C.B.K.0.0

C identifies which AUG4. If no AUG4 exists, its is set to 1, like a phantom AUG4.B identifies which AUG1. If no AUG1 exists, its is set to 1, like a phantom AUG1.

STM-1: C = 1, B = 1
There is one AUG1 in STM-1 and a phantom AUG4

STM-4:
C = 1, B = 1 - 4
There is one AUG4 in STM-4

STM-16: C = 1 - 4, B = 1 - 4

Example:

AU-4 in STM-1: 1.1.0.0.0

TU-3 in STM-4: 1.3.3.0.0

TU-12 in STM-16: 2.4.2.7.2

The C.B.K.L.M value is used for VC objects associated with E1, E3, and E4 modules but the C and B values are always 0.

VC-12 on E1 module: 1.1.1.1.1

Protecting: 1.1.1.1.2

VC-3 on E3 module: 1.1.1.0.0

Protecting: 1.1.2.0.0

VC-4 on E4 module: 1.1.0.0.0 (not release1)

Protecting: 1.2.0.0.0

For VC objects for WAN

VC-12 on E1 module: 1.1.x.y.z

VC-3 on E3 module: x.y.z.0.0 (not release 1)

VC-4 on E4 module: x.y.0.0.0 (not release 1)

Combination 0.0.0.0.0 is not a legal value and can be used as en error code.

Cross-Connection Management

Cross-connection management is the management of connectivity within the network element itself. Cross-connections (XC) are set up between connection termination points with the same characteristic information, for example cross connections between AU-4s, or between TU-3s, between VC-12 and TU-12, or between two VC-12s.

Figure 5-14 Slot - Port - CTP Relations

In ONS 15305 there are four slots that can hold an SDH module. The module can be of different types, that means, STM-1, STM-4, or STM-16. In this document the STM-1 module with 8 ports is used as an example.

In addition the ONS 15305 can have PDH modules with a number of E1 or E3 ports. The E1 and E3 ports have a corresponding VC-12 or VC-3, respectively. These VCs can be cross connected to termination points on the SDH modules or with each other.

5.6.1.2  Example

A slot with an 8 x STM-1 module has eight ports. Available CTPs on port no.8 in slot no. 1 are shown in Figure 5-14. There is one AU-4 on the port and depending on the structuring of the AU-4 container, there are 63 TU-12s, 3 TU-3s, or a combination of TU-12s and TU-3s since the TUG-3s can be structured independently, which can be cross connected. This means that in this single slot there are 8 x 63 = 504 CTPs (maximum) in the lower layer and 8 x 1 = 8 CTPs in the higher layer. And what are the possible CTPs to be cross connected to? If we assume that all four slots in this ONS 15305 are equipped with 8 x STM-1 modules there are 3 x 504 = 1512 possible choices for the connecting CTP in the lower layer and 8 x 3 = 24 in the higher layer. If an ONS 15305 is equipped with four STM-16 modules, each of these modules has 4 x 4 x 63 = 1008 TU-12 CTPs. This means that the cross connect matrix in the fabric has the dimension 4032 x 4032.

Figure 5-15 Largest Possible Cross Connect Matrix

This is a very large number of choices and impossible for a user to keep track of.

In addition there are several different types of cross connections:

•Point-to-point

•WAN XCs (special type of point-to-point, see the "WAN Ports and the Mapping" section).

•Drop and continue (not in R1).

•Broadcast (not in R1)

All of these types can be with or without protection and uni-directional or bidirectional, Figure 5-16 to Figure 5-21.

Figure 5-16 Unidirectional XC, Unprotected

Unprotected, unidirectional cross connects can be used for test loops, as illustrated in Figure 5-16.

In Figure 5-17 protection has been set up for the termination point A1 and B2. The protected termination point A1 has no switching possibility since the cross connection is uni-directional, but termination point B2 has switching.

Figure 5-17 Uni-directional XC, Protected

The bidirectional, unprotected cross connection is depicted in Figure 5-18. For bidirectional cross- connections all termination points have switching possibilities when protected. In Figure 5-19 the termination points A1 and B2 are protected, that means A1 can choose to receive from either B1 or the protection and B2 can switch between A2 or the protection.

Figure 5-18 Bidirectional XC, Unprotected

Figure 5-19 Bidirectional, Protected

Figure 5-20 Example of Bidirectional, Unprotected, Point-to-point XC

Figure 5-21 Example of Bidirectional, Protected, Point-to-point XC

Examples of an unprotected, bidirectional, point-to-point cross connect and a protected, bidirectional, point-to-point cross connect are given in Figure 5-20 and Figure 5-21, respectively.

5.6.1.3  XC Fabric

The connection management is taken care of by a Fabric as depicted in Figure 5-22. The Fabric has an interface that offers a set of methods that helps you in the cross connection management tasks on any layer. The Fabric can create, delete, and modify cross connections. It has several options for listing of XCs, for example, all XCs with the same characteristic information, all available CTPs on one port of a specific characteristic information. A third possible listing of CTPs can be a pre-defined grouping of points. A user might be indifferent to which specific CTP that is used in a XC as long as it a member of a specific group of CTPs. The system will choose an arbitrary CTP in the group. This will simplify the selection of CTP for you.

Figure 5-22 XC Fabric

5.6.2  Open the Cross Connection GUI

You have two possible choices for opening of the Cross Connection GUI.

Step 1 You can start the cross-connection GUI from the desktop menu. The system presents an empty cross-connection GUI, Figure 5-23.

Figure 5-23 Select Cross Connect

or;

Step 2 Click on an SDH port, Figure 5-24

Figure 5-24 Select SDH Port Cross Connect

The system presents the cross-connection GUI with the relevant data from the selected managed object in the management tree.

The cross-connection GUI allows you to filter the selection based on predefined set of queries.

5.6.2.1  Cancelling a query

Queries in progress can be cancelled by selecting the Stop operation from the tool bar or the menu.

5.6.2.2  Cross-connection GUI - Overview

Figure 5-18 displays the cross-connection screen.

Figure 5-25 Cross-connection GUI - Overview

5.6.3  Browsing Existing Cross-connections

Cross connections can be browsed in the cross connect window in the following manner:

5.6.3.1  Browsing all Cross-connections

To browse all:

Step 1 Open the cross-connects window from the equipment menu.

Step 2 A list of all cross-connections is shown.

Note For bidirectional cross-connections the termination points are located in the A column and the B column, according to how the cross-connection was created. One termination point can be in both the A and B-end column if the cross-connections are unidirectional. By default the cross-connections are sorted based on the A-end. Click the B column header to sort based on the B-end.

5.6.3.2  Browsing Cross-connections of a Port

Browse a port:

Step 1 Select a port.

Step 2 Right click on the port and select cross-connects.

A list of all cross-connections to and from the port is shown.

5.6.3.3  Filtering the Content of the Cross-connection List

To filter the content of the cross connection list, follow these steps:

Step 1 Open the Cross-connects window from the equipment menu or from a port as described above.

Step 2 Click the Filter button in the toolbar, Figure 5-26.

Step 3 Select the filtering criteria you want for slot and port or combinations of them.

Figure 5-26 Example of Filtering Criteria - Cross-connections

.

Step 4 Click Apply.

The cross-connects window shows only cross-connections where at least one of the termination points are included in the filtering criteria.

A filter icon is displayed in the status bar of the window to indicate that the filter is active.

5.6.3.4  Refreshing the Cross-connect Window

Refreshing the window will refresh the available TP list and cross-connection list based on the last operations performed by the local user of Cisco Edge Craft.

Step 1 Select Refresh from the View menu or click the Refresh button on the toolbar or press F5.

5.6.4  Setting up Cross-connections

Cross connections can be se up between a number of different ports.

5.6.4.1  From a 2 Mbps E1 Port to a Timeslot in an SDH Port

Creating a cross-connection from a 2 Mbps E1 port to a timeslot in an SDH port (TU-12 termination point).

Step 1 Open the Cross-connects window from the equipment menu.

Step 2 Select the VC/TU12 tab in the bottom of the window, Figure 5-27.

Figure 5-27 Select the VC/TU12 Tab

.

Step 3 Make sure the Content panel is available in the left part of the window. If it is not available select the Content button in the toolbar.

Step 4 Select the Available TP List in the Content panel. The list contains the free E1 ports and TU-12 termination points in ONS 15305.

Note If the available TP List in the content panel does not show the E1 termination points that you want to cross-connect from, you have to make sure the slot is configured for E1 ports, Setting the Port Mode for ONS 15305.

Note If the available TP List in the content panel does not show the TU-12 termination points that you want to cross-connect to, you have to make sure they are made available for cross-connection, Configuring ONS 15305 SDH Port Structure (Channelization).

Note You can create bidirectional or unidirectional cross-connections. In the available TP list you will see whether the termination point is available in both directions or as A-end or B-end.

Step 5 Double-click the E1 port in the available TP list. A new cross-connection is created with the E1 port as the A-end.

Step 6 Double-click the TU-12 (timeslot) that you want to connect to. The TU-12 is moved to the B-end of the cross-connection.

Step 7 Select Direction (unidirectional or bidirectional).

Step 8 Click Save on the toolbar.

Note Remember that both the E1 port and the SDH port must be enabled before traffic can flow between the ports, ( Enabling the SDH Port to Carry Traffic and Report Alarms and ONS 15305 SDH Port Synchronization Quality Output Signaling.)

5.6.4.2  From a 45 Mbps E3 (T3) Port to a Timeslot in an SDH Port

Creating a cross-connection from a 45 Mbps E3 (T3) port to a timeslot in an SDH port (TU-3 termination point):

Step 1 Open the cross-connects window from the equipment menu.

Step 2 Select the VC/TU3 tab in the bottom of the window, Figure 5-28.

Figure 5-28 Select the VC/TU12 Tab

.

5.6.4.3  Creating a Pass-through Cross-connection

Creating a pass-through cross-connection from one SDH port to another SDH port:

Step 1 Open the Cross-connects window from the equipment menu.

Step 2 Select the TU-12 or TU-3 or AU-4 tab termination points for both A and B ends in the bottom of the window.

5.6.5  Modifying Cross Connections

A cross-connection is a relationship between termination points and the relationship cannot be modified after it has been created.

It is not possible to modify the direction (bidirectional or unidirectional) of a cross-connection in the supported release of ONS 15305. The only parameter that can be modified is the description of the cross-connection.

Cross-connections can be protected after they have been created, Protecting Cross Connections.

5.6.6  Protecting Cross Connections

The A-end or B-end of a cross-connection can be protected by the SNC protection scheme when a cross-connection is being set up or after the cross-connection has been set up.

Note When the cross-connection is uni-directional and protectedTp is a, a static bridge will be created from the A-end to the B and protection termination points. (SNCP parameters are not used).

Note When the cross-connection is uni-directional and protected TP is b, a SNC protection switch is created where the signal from A is working connection and the signal from protection is protection connection. In this case the SNCP parameters are available after the cross-connection has been saved.

Step 1 Open the Cross-connects window from the equipment menu.

Step 2 Set the protectedTP attribute to a or b for one or more cross-connections. This is the termination point you want to protect.

Step 3 Select the cross-connection you want to protect.

Step 4 Make sure the content panel is available in the left part of the window. If it is not available select the Content button in the toolbar.

Step 5 Select the available TP list in the content panel. The list contains the free TU12/VC12 or TU3/VC3 or AU4 termination points in ONS 15305.

Note If the available TP list in the content panel does not show the termination points that you want to protect your WAN channel with, you have to make sure they are made available for cross-connection, Configuring ONS 15305 SDH Port Structure (Channelization).

Note You can protect bidirectional or unidirectional cross-connections. In the available TP list you will see whether the termination point is available in both directions or as A-end or B-end.

Step 6 Select the termination point that you want to protect your a or b-end with.

Step 7 Click on the Set Prot button in the toolbar. The protection TP is filled in for the selected cross-connection.

Step 8 Select the next cross-connection to protect and insert the protection TP. Proceed until all cross-connections are protected (cross-connections that have the protected TP attribute set to a or b).

Step 9 Click Save on toolbar.

Note By default the protection is disabled and will not work before it is enabled. Follow instructions below to enable SNC protection SNC protection.

5.6.6.1  SNC Protection

How to set up a Sub network connection protection:

Step 1 Select the cross-connections where you want to enable protection. (SHIFT and CTRL buttons can be used for multiple selection).

Step 2 Click the SNCP button in the toolbar, Figure 5-29.

Step 3 Set the Enabled attribute to enabled and click OK.

Figure 5-29 Select Enabled Attributes

.

Step 4 Click Save on toolbar.

Note It is not possible to modify the protection termination point after it has been saved. If you want to modify the protection termination point, the ProtectedTP must first be saved as none. Then the protection TP can be modified. Remember to set the Protected TP back to a or b.

5.6.6.2  Modifying Protection Parameters of a Cross-connection

A-end or B-end of cross-connections are protected as described in the "Protecting Cross Connections" section. The SNC is then set up with a number of default parameters. The parameters can easily be modified.

Step 1 Open the Cross-connects window from the Equipment menu.

Step 2 Select a cross-connection in the Cross-connect Window.

Step 3 Select the cross-connections where you want to modify protection parameters (Shift and Ctrl buttons can be used for multiple selection).

Step 4 Click the SNCP button in the toolbar.

Step 5 Modify the SNC protection parameters and click OK.

Step 6 Click Save on toolbar.

5.6.6.3  Commanding Cross-connection Protection Switch

The Cisco Edge Craft user can control the SNC protection switch by sending a command.

Step 1 Open the cross-connects window from the equipment menu.

Step 2 Select the cross-connections where you want to modify protection parameters (Shift and Ctrl buttons can be used for multiple selection).

Step 3 Click the SNCP button in the toolbar, Figure 5-30.

Step 4 Select the SncpCommand and click OK.

Figure 5-30 Select SNCP Command

.

Step 5 Click Save on toolbar.

Depending on the priority of the command and current status of each channel, a switch can now take place for some or all selected cross-connections.

5.6.7  Deleting Cross-connections

A cross connection can be deleted in the following manner:

Step 1 Open the cross-connection GUI by selecting cross-connects from equipment menu.

Step 2 Select the panel for the type of cross-connection(s) you want to delete (VC or TU12, VC or TU3 or VC or AU4).

Step 3 Select the cross-connections that you want to delete.

Step 4 Click Delete on the toolbar.

Step 5 Click Save on toolbar.

5.6.8  Advanced Cross-connection Operations

For frequent users of Cisco Edge Craft, it is possible to make use of the enhanced editing facilities to speed up the configuration work.

5.6.8.1  Setting up of Multiple Cross-connections by Multiple Selection

You can set up multiple cross connections this way:

Step 1 Select the Termination points that you want to use as A-ends. Use Shift or Ctrl buttons to select more than one termination point.

Step 2 Click Add on toolbar. The same number of cross-connections as the selected TPs are created with the A-end filled in.

Step 3 Select the TU-12 termination points that you want to add to the B-ends of the cross-connections in the same way.

Step 4 Click the Set B button on the toolbar.

Step 5 If you want to protect the connections, select the TU-12 termination points that you want to add to the cross-connections.

Step 6 Click the Set Prot button on the toolbar. Remember to set ProtectedTP to a or b.

Step 7 Click Save on the toolbar.

Note You are only allowed to set the B or protection termination points of cross-connections where B or P are not in use.
If you want to modify the A or B termination point the cross-connection must be deleted and created again.
If you want to modify the protection termination point the ProtectedTP must first be saved as none. Then the protection TP can be modified. Remember to set the ProtectedTP back to a.

Note If you do not select the same number of instances of cross-connections and termination points, the A or B end will be filled in with as many TPs as available, starting from the top of the selected cross-connection list. If more TPs are selected than cross-connections, the last TPs will not be used.

5.6.8.2  Setting up Multiple Cross-connections by Repeated Operations

Another way to set up multiple cross connections is to repeat an operation:

Step 1 Double-click the termination point you want to use as A-end. A new cross-connection is created.

Step 2 Double-click the termination point you want to use as B-end. B-end is filled in.

Step 3 Repeat Step 1and Step 2 for as many cross-connections as you want.

Step 4 Click Save on toolbar.

5.6.8.3  Entering Termination Points Manually

You can enter termination points manually like this:

Step 1 Add a new cross-connection.

Step 2 Click on the A, B or Protection termination points. A list of slots appears.

Step 3 Select a slot. A list of ports appears.

Step 4 Select a port.

Step 5 Continue selecting each of the CBKLM values.

Step 6 Enter the information the same way (or select from list of free TPs) for the other termination points.

Step 7 Click Save on the toolbar.

Note The information can also be entered directly without selecting the numbers from the drop down list. Remember to use the following format: <slot/port/C.B.K.L.M>

5.7  ONS 15305 SDH Protection Management

The purpose of this section is to guide the user through management of the 1+1 linear multiplex section Protection (MSP) between two SDH ports.

5.7.1  Introduction

The section involves management of the complete life cycle of an MSP, including creation, presentation, modification, deletion and manual operation the MSP switch.

5.7.1.1  Multiplex Section Protection

Figure 5-31 1+1 MSP between two ONS 15305

The 1+1 MSP provides protection of the SDH ports by replacing the supporting trail when it fails as illustrated in Figure 5-31. This is a 100% redundant protection scheme.

Figure 5-32 Protection Switching Scenarios

Both working and protection trails are enabled and the signal is bridged to both, Figure 5-32.

a. The received signal from the working trail is forwarded to the receiving client while the protection is not. If the working trail fails and a switch is performed, the traffic on the protection trail is received by the client, Figure 5-32.

b. Traffic from working trail is ignored. The network element uses a bidirectional switching protocol, that means, both ends of the trails switches simultaneously. To synchronize this simultaneously switching, the network elements signal to each other in the K1 and K2 bytes in the MS overhead of the SDH traffic. A bidirectional switching protocol gives a better control of the traffic in the network but uses a little more time to perform the switching than a uni-directional switching protocol does.

The switching has two different modes:

•Revertive traffic returns to the working trail when recovered.

•Non-revertive traffic stays on protection trail indefinitely or until told otherwise.

The time to wait before restoring the trail can be defined.

When switching either from or to protection, an event notification will be emitted.

5.7.2  Protect Section by MSP

MSP object for SDH port protection:

Step 1 In the management tree right click the SDH port that should be the working port.

Figure 5-33 Select SDH Port

.

Step 2 Click Add in the pop-up menu. An msp object is created below the port, Figure 5-33.

Step 3 Select the msp object in the management tree, Figure 5-34.

Figure 5-34 Select MSP Object

.

Step 4 Fill in the ProtectionSlot and ProtectionPort attributes, Figure 5-35.

Figure 5-35 Select Protection Port Attributes

Step 5 The list will only contain ports when the conditions below are fulfilled:

Working and Protection port must be selected from slot 1 and 2 or 3 and 4. Thus it is not possible to set up MSP protection with Working port from slot 1 and Protection port from slot 3. Working and Protection ports can be selected from the same slot.

A Protection port must be unstructured on the highest structurable level:

•ONS 15305 Release 1.1 / 1.0:

– aug1

•ONS 15305 Release 2.0:

–aug4 for STM4 and STM16,

– aug1 for STM1.

See the "Modifying or Removing ONS 15305 SDH Port Structure" section

The port must not be connected to a remote module.

Use default or fill in new values for the other attributes.

Step 6 Click Save on the toolbar.

The MSP scheme is created in ONS 15305 and starts working immediately. You will also see that the same msp object is now available under the protection port. You will also see that if the msp has the same Object identifier (for example 1.2.) as the parent SDH port, the port is a working port. If it has a number that is different from the parent SDH port (for example SDH port is 1.4 and msp is 1.2) it is a protection port for the SDH port with the same object identifier as the msp object.

5.7.3  Modify MSP

How to modify an MSP object:

Step 1 In the management tree right click the SDH port that is the working port.

Step 2 Select msp object below the SDH port.

Step 3 Modify the attributes of the MSP scheme.

Step 4 Click Save on toolbar.

Note If the link is operating on the protection section in bidirectional mode, you might brake traffic if you set the Mspenabled to disabled or OperatingMode to unidirectional in one of the nodes This is due to the behavior of the APS protocol.

Note To avoid problems always make sure the link is operating on the working section and to command it to lockout of protection before making the modifications.

5.7.4  Delete MSP

How to delete an MSP object:

Step 1 In the management tree right click the SDH port that is the working port.

Step 2 Select MSP and Delete in the pop-up menu. The msp object disappears both from the working port and the protection port in the management tree.

Step 3 Click Save on the toolbar.

Note Be aware that it is possible to delete an MSP when traffic is on protection section. This will cause a short break during switchover time. (If working section is available).

Note To avoid problems always make sure the link is operating on the Working section and to command it to lockout of protection before deleting the MSP.

5.7.5  Command MSP Switch

How to set an MSP switch command:

Step 1 In the management tree right click the SDH port that is the working port.

Step 2 Select msp object below the SDH port.

Step 3 Select one of the commands under MspCommand, Figure 5-36.

Figure 5-36 Select MspCommands Attribute

.

Step 4 Click Save on the toolbar.

Note Commands will only take place if there are no higher priority requests in the system.

Note A new command will clear the current command before executing the new command. In this case the new command might not be executed when the new command has lower priority than the old command because the MSP will search for the request with highest priority present. For example sending a manual switch to protection command instead of a forced switch to protection command will not work if there is a signal degrade request on the protection section.

Note All commands can be cleared by the clear command.

5.7.6  Legal combinations of SNCP and MSP

It is possible to use both SNCP and MSP in an ONS 15305 simultaneously, as long as the following is satisfied:

The protected SNCP entity can be part of an MSP protected port, but the working or protection entity can not, for example consider an STM-4 ring where some TU-12s are dropped off the ring and sent to an ONS 15302 via an STM-1 link. In this case, SNCP can be used in the ring, protecting the TU-12s to be dropped from the ring toward the ONS 15302. MSP can then be used for the STM-1 link to protect the traffic between the ONS 15305 and the ONS 15302. This is because the TU-12s that are dropped from the ring are the protected TU-12s, while the TU-12s in the ring are the working and protection TU-12s. Consequently, it is not possible to use MSP on the east or west links of the ring, since the TU-12s that are carried here are the working or protection part of the SNCP protected path's.

5.7.7  SubNetwork Connection Protection

SNCP is strongly related to the cross-connection that is protected in the network element. In Cisco Edge Craft SNCP related issues are handled from the cross-connections GUI.

Note The maximum number of SNCP instances that can be used with guaranteed switching time below 50 ms, is 252. This corresponds to one full STM-4 (or four STM-1s) structured into TU-12s. These 252 SNCP instances can be a mixture of AU-4, TU-3 and TU-12 in any combination, and taken from any C.B.K.L.M address within an STM-1/4/16. A larger number of instances than 252 can be used, but in this case we cannot guarantee switching times below 50 ms.
The resolution of the Hold-off timer is N x 100ms +/- 60 ms. That means for a 500 ms Hold-off timer, the real timer value can be any value between 440 ms and 560 ms. The Working, protection and protected parts of an SNCP protected path can be carried over different link rates. For example for an SNCP protected TU-12, the working TU-12 could be carried over an STM-16 link, while the protection TU-12 could be carried over an STM-4 link.

5.7.7.1  Protect Connection by SNCP

See the "SNC Protection" section.

5.7.7.2  Modify SNCP

See the "Modifying Protection Parameters of a Cross-connection" section.

5.7.7.3  Command SNCP Switch

See the "Commanding Cross-connection Protection Switch" section.

5.8  ONS 15302 SDH Protection Management

The ONS 15302 offers 1+1 linear multiplex section protection (MSP).

5.8.1  Multiplex Section Protection

The protocol used for K1 and K2 (b1 to b5) is defined in ITU-T G.841, clause 7.1.4.5.1. The protocol used is 1+1 bidirectional switching compatible with 1:n bidirectional switching.

The operation of the protection switch is configurable as described in the "Modify MSP Parameters" section.

5.8.1.1  Modify MSP Parameters

How to modify MSP parameters.

Step 1 Select SDH1 port (working) and click on the msp object, Figure 5-37 and Figure 5-38.

Figure 5-37 Select SDH1/MSP1 Attributes

Modifiable parameters:

•Enabled

Set to enabled or disabled.

•Mode

Set to unidirectional or bidirectional.

•MspCommand

Set one of the following.

•OperatingType

Set to reverting or non-reverting.

•WtrTime

Wait to restore time; number of seconds to wait before switching back to the preferred link after it has been restored (0,1....,12 minutes, default 5 min (300 seconds)).

Figure 5-38 Set MSP Command

Step 2 Click Save.

5.9   Ethernet Standardized Mapping

The Cisco network elements (ONS 15305 2.0 and ONS 15302 2.0) support two different modes of Ethernet over SDH (EOS) mapping:

•Cisco proprietary mapping combined with inverse multiplexing at VC-12 level.
See the "ONS 15305 Proprietary NxVC-12 EoS Mapping" section and the "ONS 15302 Proprietary NxVC-12 EoS Mapping" section.

•Ethernet over standardized mapping (EOS): GFP-F mapping, combined with Virtual Concatenation (VCAT) at VC-12, VC-3 and VC-4(ONS 15305) level, and Link Capacity Adjustment Scheme (LCAS).

Note See the ONS 15305 2.0 and ONS 15302 2.0 Installation and Operation Guides for Hardware details (modules and network elements).

This section describes EOS. The support of the different EOS modes are module dependent. WAN traffic modules support standardized mapping:

•Octal LAN 10/ 100Base- TX module with standard mapper circuits (E100-WAN-8)

•Dual Optical LAN 1000Base-LX Module with standard mapper circuits (GigE-WAN-2)

Presentation and modification of other WAN port parameters are described in the "Configuring ONS 15305 SDH Port Structure (Channelization)" section.

5.9.1  Introduction

The GFP, VCAT and LCAS standards provide a standardized (non-proprietary) way of allocating bandwidth for packet services through circuit switched networks such as SDH and SONET.

Note SONET is the American National Standards Institute standard for synchronous data transmission on optical media. This is mentioned as SDH in this section.

These standards ensure inter-operability between mixed vendor transport networks, providing the required support for establishing packet (Ethernet) services over a circuit switched transport network. These are much required properties when extending packet switched GFP- Generic Framing Procedure

A main benefit of these standards compared to pure Ethernet/MPLS metro and national wide networks is that all the SDH benefits of network resilience provided by protection schemes (MSP, SNC) are maintained while still providing full Ethernet service interfaces at the endpoints of the transport network.

This also enables owners of existing SDH network infrastructure to adapt their existing networks to the mixed packet- and circuit switched client environments of today.

GFP is a generic format for encapsulating client-side data and control packets in order to enable controlled transport though an SDH network.

Note GFP is an ITU-T standard providing a common reference for inter working between different vendors transport network components, eliminating the need for the proprietary schemes used by today's network element manufacturers (such as Cisco).

GFP is a method used to encapsulate and map packet traffic in a way that is optimal for transport through circuit switched (line switched) networks such as SDH networks. The packaging conserves both client-side data and control information transparently through the switched network.

The packaging process performs the following:

•Adding and removing GFP overhead at the entry/exit points of the transport network, providing administrative information to the SDH network to allow it to transport the packages through the network according to the client side quality requirements.

•Allow better bandwidth utilization through the SDH network when mapping packets to SDH transport channels by transforming client side line character stream coding (Layer 1 coding) to a more bandwidth efficient scheme.

•Providing generic support for transport network services such as VCAT and LCAS

•Adding packet (Ethernet) service information, allowing the SDH network the possibility to differentiate between client side service requirements at the same port (for example pint-to-point Ethernet services and multipoint-to-multipoint (LAN) services).

•Providing an end-to-end (near-end to far-end) management channel to be used by the VCAT/LCAS (or other) methods

5.9.2  GFP Alarm and Event Conditions

The following alarm and event conditions apply:

• Client Signal Fail

• GFP Frame Delineation Loss Event

• Payload Type Mismatch

• Client Payload Type Mismatch

5.9.3  GFP Performance Monitoring

The following performance parameters apply:

• Total number GFP frames transmitted and received

• Total number Client management frames transmitted and received

• Number of bad GFP frames received, based upon payload CRC calculation

• Number of HEC uncorrected errors

A degrade alarm is available for the error type PMs, which are:

• Number of bad GFP frames received, based upon payload CRC calculation

• Number of HEC uncorrected errors

The error type PMs are handled in a similar way as the SDH performance parameters. The non error type PMs are handled in the same way as the RMON counters, the non error type PMs are:

•Total number GFP frames transmitted and received

•Total number Client management frames transmitted and received

5.9.4  VCAT - Virtual Concatenation

VCAT provides efficient bandwidth allocation for mapped packet traffic in the SDH network. Bandwidth is provided by assigning a group of SDH VCs to transport the GFP packet belonging to a client interface.

VCAT is a standardized end-to-end method for better bandwidth utilization of the SDH channels by allocating SDH bandwidth in increments in steps corresponding to increments of the SDH specific VC bandwidth (n*VC12, n*VC3, n*VC4 etc.).

This is a non-proprietary method similar to, but exceeding the Cisco proprietary Ethernet port bandwidth allocation by using several VC12 's to provide the required bandwidth, as described in the "Assign VC12s in ONS 15302" section.

VCAT allows using VC12's, VC3's, VC4's into VC groups, routing it through selectable AUs/TUs on different ports. Further, it compensates for delays caused by different routes through the network, and assures that end-pint traffic is assembled in the same sequence as it was disassembled at the entry-points.

5.9.5  VC Level for VCAT

The VC available VCAT VC levels depends on the Ethernet port:

Fast Ethernet

•VC-12-nv (n=1.50)

•VC-3-nv (n=1,2,3)

•VC-4-nv (n=1) - (ONS 15305)

Gigabit Ethernet (ONS 15305)

•VC-3-nv (n=1.21)

•VC-4-nv (n=1.7)

The VC- level is individually configurable pr. mapper port. A mix of different VC- levels in one VC Group is not allowed and will result in an error.

Note The number of available Ethernet ports varies between the different network elements. Mapping type is defined per Ethernet port, and will apply to all VCs in the VC Group assigned to the port.

The mapping is flexible, and can be done to several SDH ports per Ethernet port within the mapping layer:

•VC12 channels to TU12

•VC3 channels to TU3

•VC4 channels to AU4

5.9.6  LCAS- Link Capacity Adjustment Scheme

LCAS provides on-the-fly bandwidth adjustments within a VCAT VC Group by allocating or de-allocating VCs from the VC Group. This is normally done to remove failing VCs from a VCAT VC Group, and provides both failure resilience and rapid restoration of traffic capacity.

VCAT works similar to Cisco proprietary mapping, but has more features, and is ITU-T standardized, allowing for inter operability with other vendors.

LCAS is a feature added to VCAT VC Groups, allowing for dynamic allocation and re-allocation of bandwidth in an operative Ethernet port.

LCAS is a standardized method to adjust the bandwidth of the packet transport channel through the SDH network on the fly. This bandwidth adjustment will typically be caused by the operative status (ok/fail) of the different VCs used in a VCAT Virtual Circuit group.

5.9.7  VCAT and LCAS Alarms and Events

The following alarms are related to the VCAT and LCAS:

Table 5-2 VCAT and LCAS Alarm and Event Conditions

Alarm expression

Description

lom

Vcat, loss of

sqm

Vcat sequence indicator mismatch

loa

Lcas loss of alignment for channels with traffic

loaNoTraf

Lcas loss of alignment channels w/wo traffic

acMstTimeout

Lcas acMst timeout

rsAckTimeout

Lcas RS-ack timeout

eosMultiple

Lcas two or more channels have EOS

eosMissing

Lcas one channel has EOS

sqNonCont

Lcas missing SQ detected in set of channels

sqMultiple

Lcas equal SQ for two or more channels

sqOor

Lcas SQ outside of range

gidErr

Lcas Group Id different for active channels

ctrlOor

Lcas undefined Ctrl-word for one or more channels

lcasCrc

Lcas CRC error detected

nonLcas

Lcas non-Lcas source detected

mnd

Lcas member not deskewable

fopr

Lcas failure of protocol

plcr

Lcas partial loss of capacity receive

tlcr

Lcas total loss of capacity receive

plct

Lcas partial loss of capacity transmit

tlct

Lcas total loss of capacity transmit

5.10  VCAT and LCAS Configuration Modes

The two different operation modes for the VCAT and LCAS functionality are:

•VCAT with LCAS enabled - Mode 1

•VCAT without LCAS enabled - Mode 2

5.10.1  VCAT with LCAS Enabled- Mode 1

VCAT with LCAS enabled is always uni-directional, which enables the possibility to have different capacity in each direction, but requires a separate cross connect/ capacity setup in each direction.

The connections will however very often be bi-directional, and to reduce the number of configuration steps it is possible to enables the following parameter:

• Symmetric capacity

If symmetric capacity is enabled the VC Group is automatically set up with the same capacity in each direction, but the symmetric capacity consists of two uni-directional connections. With the symmetric mode disabled the capacity of the VC Group will need to be configured separately in each direction.

5.10.2  VCAT Without LCAS Enabled- Mode 2

When VCAT is used without LCAS, there is no mechanism for removing of a faulty VC container in a VCG group. To solve this problem the network element has, in addition to the standard mode, a proprietary mode.

The following configurations are available in mode 2:

• Default mode, unidirectional connections with the possibility of configuring symmetric capacity as explained in mode 1. Same features as in mode 1 but without LCAS

• Bidirectional mode

If bidirectional mode is enabled, the cross connections should not be uni-directional, but bi-directional. In addition RDI signalling is enabled. A faulty container in a VC Group is removed based upon the VC alarm condition or based upon RDI signalling (similar to Cisco proprietary mapping). This will allow a VC Group to continue operation even if the VCG has a failed member. This configuration mode is proprietary.

5.11  Administrative Bandwidth for VCAT

Network elements use the administrative bandwidth as a separate defined parameter, independently of the actual assignment of TPs. The administrative bandwidth is used as a notification in case the actual (operative) bandwidth differs from the administrative bandwidth. In ONS 15302, the administrative bandwidth is implicit when selecting the TPs to be mapped to the Ethernet port.

5.11.1  Bandwidth for uni-directional VCAT

The administrative bandwidth can be:

•Symmetrical
Same bandwidth downstream and upstream.

•Asymmetrical
Different defined bandwidths for the two directions.

In uni- directional VCAT, the upstream (traffic flow towards the SDH ports) and downstream (traffic flow towards the Ethernet port) is routed in separate, uni-directional VC Groups. An ethernet port is a LAN port with Layer 1 or WAN port, expressed with character `x' in GUI.

The bandwidth is provided by mapping STM-n port(s) as termination points to the Ethernet port. The TPs will carry VCs in a VC Group assigned to the Ethernet port.

Note The configuration is manually set for both directions.

5.11.1.1  Bandwidth for Bi-directional VCAT

The administrative bandwidth for bi- directional VCAT (Equivalent to Cisco proprietary mapping) is identical for both directions (transmit and receive), as the same TUs and AU's are used to provide the bandwidth.

Note The bandwidth must also be implemented through cross-connecting the Ethernet port channels (ONS 15305) to the designated AU's or TUs.

Bi-directional VCAT is a Cisco proprietary version of VCAT. It has symmetric capacity, and LCAS is not allowed.

To circumvent transmission failures due to the loss of VCs in a VC Group, RDI signaling is enabled, allowing the network element to automatically detect and remove faulty VCs in the VC Group. Failures will be indicated by error notifications and the reduction of the displayed operative capacity.

5.12  Circuit Protection for VCAT

If the network element contains an SDH cross connect, SNC/N or SNC/I is allowed when supported by the network element.

See the "Protecting a WAN Port" section and the "Protecting Cross Connections" section.

5.12.1  CirCuit Protection For Uni-directional Modes For ONS 15305

You define circuit protection when cross connecting Ethernet port channels to the SDH ports. Since the VCs are unidirectional, the VC termination can be both A-side (transmit) and B-side (receive), as illustrated in the figure below:

Figure 5-39

VCAT with SNC- Illustration

See the "Protecting Cross Connections" section.

5.12.2  Circuit proTection For Symmetrical VCAT

Circuit protection is the same for symmetrical VCAT and Cisco proprietary mapping modes.

5.13  Establish a standardized Mapping With CEC

You establish, modify and delete an Ethernet mapping at the endpoints of a Ethernet path through the network.

You can perform the standardized mapping in the Management Tree or in the WAN mapping GUI. Each mapping operation on an attribute in Management Tree results in a corresponding update of the associated network element attribute(s) in the WAN mapping GUI, see Figure 5-40.

Figure 5-40

standardized mapping- GUI overviews

5.13.0.1  BeFore You Start

•The STM-n port(s) are structured to the required level (TU12, TU3, AU4). See the "ONS 15305 SDH Cross-Connection Management" section.

•The slot(s) expects an Ethernet port with a mapper module.

The following procedures exemplifies standardized mapping types:

• Uni- directional VCAT with LCAS

• Bi-directional VCAT Without LCAS (Remains - GHE)

Note The activities in the examples can be parallel, and the order is less significant.

5.13.0.2  Uni- directional VCAT with LCAS

You have selected the Ethernet mapping to be symmetrical uni- directional VCAT VC- level 3 with LCAS. ONS 15305 with Mapper module E100-WAN-8 as the Ethernet port (here: WANx) is used as an example.

Note This procedure is generic, and the example can easily be used for Uni- directional without LCAS by disabling the LCAS attribute(s).

Step 1 Select configuration Mode to expected Ethernet port.

Figure 5-41

Slot configuration- ONS 15305 example

Step 2 Select the VC Group from desired Ethernet port (here: WANx)

Figure 5-42

Ethernet port - VC Group view

Step 3 Select VC level from Concatenation.
The appropriate structuring level is set to VCAT enabled port.

Figure 5-43

VC Group concatenation- Example VC level

Step 4 Press LCAS from VC Group and select LCAS as LCAS Operational mode.
LCAS is enabled for the VCAT enabled port, independent direction.

Figure 5-44

Enable LCAS

Step 5 Select VC Group and press Bandwidth.

Step 6 Set the same Administrative Capacity for downstream and upstream.

Figure 5-45 Administrative Capacity- Symmetrical Uni- directional VCAT

Step 7 View Operational capacity (optional verification.)

Figure 5-46 Operational Capacity- example asymmetrical capacity

Step 8 Save the Ethernet port configuration to the network element.

Step 9 Open WAN- to- SDH mapping GUI.

Step 10 Browse Ethernet port from Search bar.

Step 11 Check LCAS Channel Status for VC channels (here: WAN).

Figure 5-47

WAN- to- SDH Mapping- LCAS Traffic Status

Alternative procedure:

Select one VC channel from VC group in Management Tree and choose Traffic as LCAS Channel Status. Repeat the operation for all VCs.

Figure 5-48

LCAS traffic set for one VC Channel

Step 12 Select one direction (upstream/ downstream) pane.

Step 13 Replace Search bar with Available TPs pane.
A list of available VC termination points is presented.

Note If the list is empty, you should see "BeFore You Start" on page -48 or/ and SDH Structuring Wizard.

Step 14 Select the desired TPs, see the "Advanced WAN Port Operations" section.
The bandwidth is provided for distribution of the Ethernet port traffic through the STM port.

Note Repeat the mapping steps for traffic distribution in both directions in accordance to the chosen symmetrical uni- directional VCAT mode.

Step 15 Define VC cross connection point for circuit protection.

For procedure and scheme (SNC/I, SNC/N), see the "Protecting a WAN Port" section and the "Protecting Cross Connections" section.

5.14  Bi-directional VCAT Without LCAS

With this VCAT configuration mode, each VC is used for traffic in both directions (equivalent to symmetrical uni- directional VCAT).

•Mode (no LCAS or softLCAS bi- directional)

•Directionality (bi-directional)

•The VC-to-TP cross connections is defined to be bi-directional.

Figure 5-49

Lcas Operation Mode

Figure 5-50

Bi- directional VCAT- Example VC- level 12

A WAN port is mapped to the SDH network with the following parameters settings:

•The required bandwidth provided for the WAN port through the SDH network

•The specified mapping mode is established

•Cross connections of WAN port channels to the target SDH Port(s) TPs established with the intended directionality and circuit protection schemes.

5.15  ONS 15305 Proprietary NxVC-12 EoS Mapping

The purpose of this section is to describe the tasks involved in assigning capacity from the SDH server layer to WAN ports with proprietary NxVC-12 EoS Mapping.

5.15.1  Introduction

The total assigned WAN capacity is made up of SDH channels.

One SDH channel is equivalent to a VC-12 (2 Mbps). Mapping to VC-3 and VC-4 is also supported. This section only describes the VC-12/TU-12 layer rate.

ONS 15305 supports Fast Ethernet module; Dual Optical LAN 1000Base-LX Module with Mapper, GigE-WAN-2 and

GigaBit Ethernet module: Octal LAN 10/100Base-TX Module with Mapper, E100-WAN-8.

The table below shows how many VC channels there are on each WAN port on the two modules.

Table 5-3 Mapping to VC-n

Module

VC-12

VC-3

VC-4

E100-WAN-8

50

3

1

GigE-WAN-2

NA

21

7

The SDH channels can be from different SDH ports.

The WAN channels can be sub-network connection (SNC) protected. ONS 15305 supports the protection schemes SNC/I (inherent monitoring) and SNC/N (Non-Intrusive monitoring.

5.15.1.1  WAN Ports and the Mapping

The eight WAN ports are located on the 8xSTM-1 module. They are connected to a Galileo switch, Figure 5-51. A WAN port has a maximum capacity of 100 Mbps.

Figure 5-51 The 8 x STM-1 Module with WAN Ports

Figure 5-52 shows that the potential capacity of 100 Mbps is realized through 50 channels each able to carry 2.160 Mbps. The capacity of the WAN port is therefore decided by how many channels that are used for traffic.

A WAN port can be mapped to one STM-1 port, that means there are potentially 63 available VC-12s. Only the 50 first of these are used. These 50 channels have hard coded mapping to 50 VC-12 containers.

The C.B.K.L.M numbering is described in the "C.B.K.L.M Value Usage" section.

Figure 5-52 View of one WAN Port and its Logical View

The WAN VC-12s are cross connected to the available TU-12s on the SDH ports. All 50 WAN VC-12s are always available for cross connection. A WAN VC-12 always represents the termination point A in a cross connection and the connection is always bidirectional. The cross connection can be protected.

If a VC-12 (or channel) that is not cross connected exists inside the WAN capacity, the network element issues an alarm on the WAN VC-12 (unequipped alarm).

The order of the channels is essential and must be the same on both sides of a WAN connection, for example, containers sent from channel 1 must be received on channel 1. A sequence number is used to indicate the correct order of the VC-12 on the receiving side of a WAN connection between two ONS 15305. If the connection is not between two ONS 15305, the sequence number will be zero. A scenario where the cross connection between two TU-12s and two VC-12s in one ONS 15305 is wrong is illustrated in Figure 5-53.

Figure 5-53 Sequence Numbers for Correct Order of TU-12 to VC-12 Cross Connects.

Alarms and performance monitoring data are collected and reported for those VC-12s that are within the WAN capacity.

5.15.2  WAN to SDH mapping- Custom GUI

How to search, list and open terminations points for mapping

5.15.2.1  Open WAN to SDH Mapping

Step 1 Open WAN to SDH mapping from Equipment menu.
The list of WAN Channels will be empty.

Figure 5-54 WAN- to- SDH Mapping- GUI Overview

A search bar is available for browsing Ethernet ports.

Step 2 Select the desired Port.

Step 3 Press Search Now.

The list of WAN Channels will be displayed for the selected Ethernet port.

Figure 5-55 WAN port search- example uni- directional

5.15.2.2  List Available Termination Points

Step 4 Click Available TPs List.

A list of available STM- n ports is presented in accordance to VC- level.

Figure 5-56 WAN channels list- example VC/ TU 12

5.15.2.3  Cancelling a Query

Queries in progress can be cancelled by selecting the Stop operation.

5.15.3  Add Initial WAN Port Capacity

The addition of WAN port capacity is performed in a two step process.

The first step is to set the administrative capacity of the WAN port. This will tell ONS 15305 how many of the 50 possible WAN channels to use for mapping into the SDH server layer.

Step 1 Select a WAN port.

Step 2 When the WAN port managed object is expanded, select Bandwidth.

Figure 5-57 Set Bandwidth

.

Step 3 Set the Bandwidth to a value between 0 and 100 Mbps, Figure 5-57.

Step 4 Click Save on the toolbar.

The next step is to cross-connect the WAN channels that are in use after setting the administrative capacity.

Step 5 Select the WAN port again, right click and select WAN to SDH mapping, Figure 5-58.

Figure 5-58 Select WAN Port Attributes

A list of all the WAN channels of the WAN port is shown. The list shows the static relation between each channel number and a VC12 object in the WAN port. The WithinCapacity attribute indicates if the channel is in use by the WAN channel (that means if it was included when setting the administrative capacity above).

Figure 5-59 Set WAN Port Attributes

.

Step 6 Make sure the Content panel is available in the left part of the window, Figure 5-59.

If it is not available select the Content button in the toolbar.

Step 7 Select the Available VC/TU12 List in the content panel. SHIFT and CTRL buttons can be used for multiple selection The list contains the free TU12 termination points in ONS 15305, Figure 5-60.

Figure 5-60 Select Available VC/TU12

Note If the Available VC or TU12 List in the content panel does not show the TU12 termination points that you want to map your WAN port to, you have to make sure they are made available for cross-connection, see the "Configuring ONS 15305 SDH Port Structure (Channelization)" section.

Step 8 Double-click the TU12 termination point that you want to use to map to your WAN channel number 1. The selected TU12 is inserted as the B termination Point for channel 1.

Step 9 Double-click the termination point that you want to use to map to your WAN channel number 2.

Step 10 Continue until all channels that are within capacity has a B termination point.

Step 11 Click Save on the toolbar.

Note Remember to perform the same operation on the WAN port on the other side of the SDH network and add cross-connections in intermediate nodes. The WAN channel will only work if it is connected to the WAN channel with the same channel number on the opposite end of the SDH network.

Note The WAN port will not report alarms on channels that are not part of the administrative capacity.

5.15.4  Modify WAN Port Capacity

You can modify the WAN port capacity in the same way as you added the initial WAN capacity, "Add Initial WAN Port Capacity" section.

Step 1 Select a WAN port.

Step 2 When the WAN port managed object is expanded, select Bandwidth.

Step 3 Set the Bandwidth to a new value between 0 and 100 Mbps.

Step 4 Click Save on the toolbar.

Step 5 Select the WAN port again, right click and select WAN to SDH mapping.

A list of all the WAN channels of the WAN port is shown. The list shows the static relation between each channel number and a VC12 object in the WAN port. The WithinCapacity attribute indicates if the channel is in use by the WAN channel (that means if it was included when setting administrative capacity above).

Step 6 If you increased the administrative capacity ( Add Initial WAN Port Capacity), more channels have the WithinCapacity attribute set and they need a B termination point to be mapped to the SDH server layer, Add Initial WAN Port Capacity.

Step 7 If you decreased the administrative capacity ( Add Initial WAN Port Capacity), less channels have the WithinCapacity attribute set and the B termination points can be released for other purposes, Add Initial WAN Port Capacity.

5.15.4.1  Increasing Capacity in the SDH Server Layer:

Make sure the content panel is available in the left part of the window. If it is not available select the content button in the toolbar.

Step 1 Select the Available VC or TU12 List in the content panel. The list contains the free TU12 termination points in ONS 15305.

Note If the available VC or TU12 list in the content panel does not show the TU12 termination points that you want to map your WAN port to, you have to make sure they are made available for cross-connection, Configuring ONS 15305 SDH Port Structure (Channelization).

Step 2 Double-click the TU12 termination point that you want to use to map to your first new WAN channel. The selected TU12 is inserted as the B termination Point for this channel.

Step 3 Double-click the termination point that you want to use to map to your next new WAN channel.

Step 4 Continue until all new channels that are within capacity has a B termination point.

Step 5 Click Save on the toolbar.

Step 6 Remember to perform the same operation on the WAN port on the other side of the SDH network and adding cross-connections in intermediate SDH nodes.

5.15.4.2  Decreasing Capacity in the SDH Server Layer

Step 1 Select the WAN channels that are no longer used by the WAN port mapping (channels with B termination points, but not WithinCapacity). Multiple selection is possible with Shift or Ctrl buttons, Figure 5-61.

Step 2 Click Delete on the toolbar. The selected channels become red.

Figure 5-61 Select WAN Channels

.

Step 3 Click Save on toolbar. The SDH TU12 termination points are released from WAN port mapping.

Step 4 Remember to perform the same operation on the WAN port on the other side of the SDH network and deleting cross-connections in intermediate SDH nodes.

Note It is not possible to modify the B termination point after it has been saved. If you want to modify the B termination point the channel must first be deleted, and then a new termination point can be added.

5.15.5  Protecting a WAN Port

WAN ports can be protected by the SNC protection scheme in the VC12 or TU12 SDH layer. That means that the WAN channels (not necessarily all WAN channels of a WAN port) can have two different routes through the SDH server network, and that the receiving WAN channel selects the route with the best signal.

Step 1 Add initial WAN port capacity as described in "Add Initial WAN Port Capacity" section.

Step 2 Set the ProtectedTP attribute to a for the WAN channels you want to protect, Figure 5-62.

Figure 5-62 Select Protected Mode

Step 3 Select the first WAN channel you want to protect.

Step 4 Make sure the content panel is available in the left part of the window. If it is not available select the content button in the toolbar.

Step 5 Select the available VC or TU12 list in the content panel. The list contains the free TU12 termination points in ONS 15305.

Note If the available VC or TU12 list in the content panel does not show the TU12 termination points that you want to protect your WAN channel with, you have to make sure they are made available for cross-connection, Configuring ONS 15305 SDH Port Structure (Channelization).

Step 6 Select the TU12 termination point that you want to protect your WAN channel with.

Step 7 Click on the Set Prot button in the toolbar. The protection TP is filled in for the selected WAN channels.

Step 8 Select the next WAN channel to protect and insert the protection TU12. Proceed until all WAN channels are protected (channels that have the Protected TP attribute set to a).

Step 9 Click Save on toolbar. Remember to perform the same operation on the WAN port on the other side of the SDH network and adding cross-connections in intermediate nodes.

Note By default the protection is disabled and will not work before it is enabled.

Step 10 Select the WAN channels where you want to enable protection (Shift and Ctrl buttons can be used for multiple selection).

Step 11 Click the SNCP button in the toolbar, Figure 5-63.

Step 12 Set the Enabled attribute to enabled and click OK.

Figure 5-63 Set SNCP Properties Enabled

.

Step 13 Click Save on toolbar. Remember to perform the same operation on the WAN port on the other side of the SDH network. (However SNC protection is not bidirectional and does not have to be enabled in both ends simultaneously for the SNC protection scheme to work on the side that is enabled).

Note It is not possible to modify the protection termination point after it has been saved. If you want to modify the protection termination point the ProtectedTP must first be saved as none. Then the protection TP can be modified. Remember to set the ProtectedTP back to "a" (See Figure 5-62).

5.15.6  Modifying Protection Parameters of the WAN Port

WAN ports are protected as described in "Protecting a WAN Port" section. The SNC is then set up with a set of default parameters. The parameters can easily be modified, Figure 5-64.

Step 1 Select a WAN port.

Step 2 Right click and select WAN to SDH mapping.

Step 3 Select the WAN channels where you want to modify protection parameters (Shift and Ctrl buttons can be used for multiple selection).

Step 4 Click the SNCP button in the toolbar.

Step 5 Modify the SNC protection parameters and click OK.

Figure 5-64 Set SNCP Properties Protection

.

Step 6 Click Save on toolbar.

5.15.7  Commanding WAN Port Protection Switch

The Cisco Edge Craft user can control the SNC protection switch by sending a command, Figure 5-65.

Step 1 Select a WAN port.

Step 2 Right click and select WAN to SDH mapping.

Step 3 Select the WAN channels where you want to modify protection parameters (Shift and Ctrl buttons can be used for multiple selection).

Step 4 Click the SNCP button in the toolbar.

Step 5 Select the SncpCommand and click OK.

Figure 5-65 Set SNCP Properties Command

.

Step 6 Click Save on toolbar. Depending on the priority of the command and current status of each channel, a switch can now take place for some or all selected WAN channels.

5.15.8  Setting Path Trace Identifiers for WAN Port

Path Trace parameters can be set for each channel (VC12) in the WAN port.

Step 1 Select a WAN port.

Step 2 Click on the PathTraceWAN parameter group.

Step 3 The following attributes can be set collective for all channels of the WAN port:

•PathTrace

Set to enable if TIM alarms should be reported for the WAN port when there is a mismatch between PathTraceReceived and PathTraceExpected.

•PathTraceExpected

Enter a value for the path trace identifier that you expect to receive from the other side of the WAN channels.

•PathTraceTransmitted

Enter a value for the path trace identifier that you want to transmit to the other side of the WAN channels.

Step 4 Click Save on toolbar.

Note When path trace is set to enabled, AIS is inserted downstream instead of the original signal when there is a mismatch between expected and received path trace.

5.15.9  Reading Path Trace Identifiers for WAN Port

Path trace parameters can be read for each channel (VC12) in the WAN port.

Step 1 Select a WAN port.

Step 2 When the WAN port managed object is expanded, click on the channel (vc12) where you want to see the Received Path Trace.

Step 3 Click on PathTraceVC12

Step 4 The following attributes can be read:

•PathTrace

Set to enable if TIM alarms should be reported when there is a mismatch between PathTraceReceived and PathTraceExpected.

•PathTraceExpected

Enter a value for the path trace identifier that you expect to receive from the other side of the path.

•PathTraceTransmitted

Enter a value for the path trace identifier that you want to transmit to the other side of the path.

•PathTraceReceived

The actual received path trace identifier from the other side of the link.

Note When path trace is set to enabled, AIS is inserted downstream instead of the original signal when there is a mismatch between expected and received PathTrace.

5.15.10  Monitoring WAN Port Performance

Follow the steps below to set up monitoring of WAN port performance.

Step 1 Select a WAN port.

Step 2 When the WAN port managed object is expanded, click on the channel (vc12) where you want to see the Performance data.

Step 3 Click on PmG826NearEndVc12 to read near end PM data or PmG826FarEndVC12 to read far end PM data.

Step 4 The following attributes are available

•Current15Min ES,SES, BBE and UAS

•Current24Hour ES, SES, BBE and UAS

Step 5 To see the Performance history of the previous 16x15 minute counters click on Interval15Min, or click on Interval24Hour to see the previous 24 hour counter.

Step 6 The following attributes are available

•Interval15Min ES, SES, BBE and UAS

•Interval24Hour ES, SES, BBE and UAS

5.15.11  Advanced WAN Port Operations

For frequent users of Cisco Edge Craft, it is possible to make use of the enhanced editing facilities to speed up the configuration work.

5.15.11.1  Selection and Insertion of Multiple Termination Points

Multiple termination points are selected like this:

Step 1 Select the channels where you want to add termination points as B-end or Protection. Use Shift or Ctrl buttons to select more than one channel, or simply drag the mouse down the list while pressing the left mouse button.

Step 2 Select the TU-12 termination points that you want to add to the B-ends of the channels in the same way.

Step 3 Click the Set B button in the toolbar.

Step 4 Select the TU-12 termination points that you want to add to the Protection TPs of the channels.

Step 5 Click the Set Prot button in the toolbar.

Step 6 Click Save on the toolbar.

Note You are only allowed to set the B or protection termination points of channels where B or P are not in use.
If you want to modify the B termination point the relation with the existing B termination point must first be deleted. Then a new termination point can be added.
If you want to modify the protection termination point the ProtectedTP must first be saved as none. Then the protection TP can be modified. Remember to set the ProtectedTP back to a.

Note If you do not select the same number of instances of WAN channels and termination points, the channels will be filled in with as many TPs as available, starting from the top of the selected channel list. If more TPs are selected than channels, the last TPs will not be used.

Entering Termination Points Manually

How to enter termination points manually.

Step 1 Select an unconfigured WAN channel.

Step 2 Click on the B termination point. A list of slots appears.

Step 3 Select a slot. A list of ports appears.

Step 4 Select a port.

Step 5 Continue selecting each of the CBKLM values.

Step 6 Enter the Protection termination point the same way if used (and set ProtectedTP to a).

Step 7 Click Save on the toolbar.

Note The information can also be entered directly without selecting the numbers from the drop down list. Remember to use the following format: <slot/port/C.B.K.L.M>

5.16  ONS 15302 Proprietary NxVC-12 EoS Mapping

The purpose of this chapter is to describe the tasks involved in assigning capacity from the SDH server layer to WAN ports by proprietary NxVC-12 EoS Mapping.

ONS 15302 supports the Fast Ethernet module: WAN+

Each SDH channel is equivalent to a VC-12 (2.160 Mbps). ONS 15302 has one or four WAN ports depending on the hardware configuration. The table below shows how many VC channels there are on each WAN port.

Table 5-4

Module

VC-12

VC-3

VC-4

WAN MODULE +

50

3

NA

5.16.1  WAN ports and the Mapping

The network element has one or four WAN ports. A WAN port has a maximum capacity of 100 Mbps.

The WAN ports are logical ports and not physical ports. The potential capacity of 100 Mbps is realized and guaranteed through 47-50 VC12s each able to carry 2.160 Mbps. The overhead, that means, extra bits, are used to handle escaped characters. The capacity of the WAN port is therefore decided by how many VC12s that are assigned to the port.

ONS 15302 has one STM-1 port and potentially 63 VC12s are available fro a WAN port. Each WAN port has 50 channels that are dynamically mapped to VC12s.

The VC-12s have static cross connections to the available TU-12s on the SDH ports.

The order of the 0-50 channels are essential and must be the same on both sides of a WAN connection, for example containers sent from channel 1 must be received on channel 1, Figure 5-66.

Figure 5-66 View of the WAN Ports and their Logical View

Alarms and performance monitoring data is collected and reported for the VC-12s.

5.16.2  Differences between ONS 15305 and ONS 15302

In ONS 15305 each WAN port always has a potential capacity of 100 Mbps realized through 50 channels. The available capacity is not dependent on the capacity used by the other WAN ports. When you set the capacity, the system selects the first X channels corresponding to this capacity. The channels have a static mapping to VC-12s. You must cross connect the VC-12s to TU-12s to activate the capacity.

In ONS 15302 each WAN port also has a potential capacity of 100 Mbps, but the available capacity is dependent of the capacity used by the other WAN ports. You set and activate the capacity indirectly by selecting a set of channels and map them to VC-12s. The VC-12s are statically cross connected to TU-12s.

In ONS 15302 the Admin Capacity only indicates the number of channels that are mapped from the WAN to SDH GUI, and cannot be altered to choose bandwidth allocation in the way you can in ONS 15305.

5.16.3  Force LAN Down

This feature requires alternate routes for the IP traffic.

In situation where the WAN-connection is lost, the network element must be informed in order to initiate a switch-over. You can make this happen by forcing the equivalent LAN-port down.

A WAN Down situation will force down an equivalent Ethernet port. This situation will trigger the WanDown alarm. WanDown is the only trigger mechanism in forcing an equivalent LAN-port down.

Note This criteria covers all traffic-affecting alarms at levels higher than VC-12 by means of SSF (Server Signal Failure).

ONS 15302 supports the Force Ethernet Status Down feature- functioning as a new switch mode. When the mode is activated, a fixed relation between WAN-ports and LAN-ports is established, for example 1-5, 2-6, 3-7 and 4-8, that is, a WanDown alarm on WAN port 7 will autonomously force LAN port 3 down and so on. This requirement applies to all types of ONS 15302 WAN-ports, for instance ports with proprietary VC-12 mapping and ports with VC-12 or VC-3 GFP mapping, see the "Ethernet Standardized Mapping" section.

5.16.3.1  Force LAN down on WAN down alarm

In cases of mode transitions, you are recommended to follow this procedure:

Step 1 Delete all VLAN entries in VLAN-tables for desired network element.

Figure 5-67 VLAN entry- example

Step 2 Click WAN in Management Tree.

The WAN mode is displayed as normal (default setting.) in Attributes.

Step 3 Change WANmode from Normal to LAN down on WAN down.

Step 4 Press Save.

Figure 5-68 Force LAN down on WAN down

Step 5 Restart device.

5.16.3.2  Cross-connect the WAN Channels

How to cross connect WAN channels:

Step 1 Select the WAN port again, right click and select WAN to SDH mapping, Figure 5-69.

Step 2 A list of all the WAN channels of the WAN port is shown. The list shows the static relation between each channel number and a VC12 object in the WAN port.

Figure 5-69 Select a WAN port

If the Administrative Capacity is set, the WithinCapacity attribute indicates if the channel is in within the desired capacity, Figure 5-70.

If the Administrative Capacity is not set, the WithinCapacity attribute indicates numbers of channels mapped.

Figure 5-70 Set WAN Attributes

Step 3 Make sure the Content panel is available in the left part of the window.

If it is not available, select the Content button in the toolbar.

Step 4 Select the available VC or TU12 List in the content panel. The list contains the free TU12 termination points in ONS 15305, Figure 5-71.

Figure 5-71 Select Available VC/TU12 Container

.

Step 5 Double-click the TU12 termination point that you want to use to map to your WAN channel number 1. The selected TU12 is inserted as the B termination Point for channel 1.

Step 6 Double-click the termination point that you want to use to map to your WAN channel number 2.

Step 7 If AdministrativeCapacity is set, continue until all channels that are within capacity has a B termination point.

Step 8 Click Save on the toolbar.

Note Remember to perform the same operation on the WAN port on the other side of the SDH network and adding cross-connections in intermediate nodes. The WAN channel will only work if it is connected to the WAN channel with the same channel number on the opposite end of the SDH network.

Note The WAN port will not report alarms on channels that are not part of the administrative capacity.

5.16.4  Increase Capacity in the SDH Server Layer

Make sure the content panel is available in the left part of the window. If it is not available select the content button in the toolbar

Step 1 Select the available VC or TU12 List in the content panel. The list contains the free TU12 termination points in ONS 15302.

Step 2 Double-click the TU12 termination point that you want to use to map to your first available WAN channel. The selected TU12 is inserted as the B termination Point for this channel.

Note For the ONS 15302, mapping must be performed in a continuos range.

Step 3 Double-click the termination point that you want to use to map to.

Step 4 If AdministrativeCapacity is set, continue until all channels that are within capacity has a B termination point.

Step 5 Click Save on the toolbar.

Note Remember to perform the same operation on the WAN port on the other side of the SDH network and adding cross-connections in intermediate SDH nodes.

5.16.5  Decrease Capacity in the SDH Server Layer

How to decrease the capacity in the SDH server layer:

Step 1 Select the WAN channels that are not used anymore by the WAN port mapping (channels with B termination points, but not WithinCapacity). Multiple selection is possible with Shift or Ctrl buttons.

Note For the ONS 15302, deleting mappings, must be performed in a continuos range.

Step 2 Click Delete on the toolbar. The selected channels become red, Figure 5-72.

Figure 5-72 Delete WAN Port

.

Step 3 Click Save on toolbar. The SDH TU12 termination points are released from WAN port mapping.

Step 4 Remember to perform the same operation on the WAN port on the other side of the SDH network and deleting cross-connections in intermediate SDH nodes.

Note It is not possible to modify the B termination point after it has been saved. If you want to modify the B termination point the mapping must first be deleted, and then a new termination point can be added.

5.16.6  Setting Path Trace Identifiers for WAN Port

Path trace parameters can be read for each channel (VC12) in the WAN port.

Step 1 Select a WAN port.

Step 2 Click on the PathTraceWAN parameter group

Step 3 The following attributes can be set for all channels of the WAN port:

•PathTrace

Set to enable if TIM alarms should be reported for the WAN port when there is a mismatch between PathTraceReceived and PathTraceExpected.

•PathTraceExpected

Enter a value for the path trace identifier that you expect to receive from the other side of the WAN channels.

•PathTraceTransmitted

Enter a value for the path trace identifier that you want to transmit to the other side of the WAN channels.

Step 4 Click Save on toolbar.

Note When path trace is set to enabled, AIS is inserted downstream instead of the original signal when there is a mismatch between expected and received path trace.

5.16.7  Reading Path Trace Identifiers for WAN Port

Path trace parameters can be read for each channel (VC12) in the WAN port.

Step 1 Select a WAN port.

Step 2 When a WAN port managed object is expanded, click on the channel (vc12) where you want to see the Received Path Trace.

Step 3 Click on PathTraceVC12.

Step 4 The following attributes can be read:

•PathTrace

Set to enable if TIM alarms should be reported when there is a mismatch between PathTraceReceived and PathTraceExpected.

•PathTraceExpected

Enter a value for the path trace identifier that you expect to receive from the other side of the path.

•PathTraceTransmitted

Enter a value for the path trace identifier that you want to transmit to the other side of the path.

•PathTraceReceived

The actual received path trace identifier from the other side of the link.

Note When path trace is set to enabled, AIS is inserted downstream instead of the original signal when there is a mismatch between expected and received PathTrace.

5.16.8  Monitoring WAN Port Performance

The WAN port's near and far end PM data can be monitored:

Step 1 Select a WAN port.

Step 2 When the WAN port managed object is expanded, click on the channel (vc12) where you want to see the Performance data.

Step 3 Click on PmG826NearEndVc12 to read near end PM data or PmG826FarEndVC12 to read far end PM data.

Step 4 The following attributes are available:

•Current15Min ES,SES, BBE and UAS

Step 5 To see the Performance history of the previous 16x15 minute counters click on Interval15Min.

The following attributes are available:

•Interval15Min ES,SES, BBE and UAS

5.16.9  Advanced WAN Port Operations

For frequent users of Cisco Edge Craft, it is possible to make use of the enhanced editing facilities to speed up the configuration work.

Selection and Insertion of Multiple Termination Points

Step 1 Select the channels where you want to add termination points as B-end. Use Shift or Ctrl buttons to select more than one channel, or simply drag the mouse down the list while pressing the left mouse button.

Step 2 Select the TU-12 termination points that you want to add to the B-ends of the channels in the same way.

Step 3 Click the Set B button in the toolbar.

Step 4 Click Save on the toolbar.

Note You are only allowed to set the B termination points of channels where B is not in use.
If you want to modify the B termination point the relation with the existing B termination point must first be deleted. Then a new termination point can be added.

Note If you do not select the same number of instances of WAN channels and termination points, the channels will be filled in with as many TPs as available, starting from the top of the selected channel list. If more TPs are selected than channels, the last TPs will not be used.

Rules	Examples
When referring to SDH objects the complete C.B.K.L.M value is used even if some fields are in-significant.
Not significant fields in C.B.K.L.M are set to 0.	AU-4 in STM-16: C.B.0.0.0 TU-3 in STM-16: C.B.K.0.0
C identifies which AUG4. If no AUG4 exists, its is set to 1, like a phantom AUG4.B identifies which AUG1. If no AUG1 exists, its is set to 1, like a phantom AUG1.	STM-1: C = 1, B = 1 There is one AUG1 in STM-1 and a phantom AUG4 STM-4: C = 1, B = 1 - 4 There is one AUG4 in STM-4 STM-16: C = 1 - 4, B = 1 - 4 Example: AU-4 in STM-1: 1.1.0.0.0 TU-3 in STM-4: 1.3.3.0.0 TU-12 in STM-16: 2.4.2.7.2
The C.B.K.L.M value is used for VC objects associated with E1, E3, and E4 modules but the C and B values are always 0.	VC-12 on E1 module: 1.1.1.1.1 Protecting: 1.1.1.1.2 VC-3 on E3 module: 1.1.1.0.0 Protecting: 1.1.2.0.0 VC-4 on E4 module: 1.1.0.0.0 (not release1) Protecting: 1.2.0.0.0
For VC objects for WAN	VC-12 on E1 module: 1.1.x.y.z VC-3 on E3 module: x.y.z.0.0 (not release 1) VC-4 on E4 module: x.y.0.0.0 (not release 1)
Combination 0.0.0.0.0 is not a legal value and can be used as en error code.

Alarm expression	Description
lom	Vcat, loss of
sqm	Vcat sequence indicator mismatch
loa	Lcas loss of alignment for channels with traffic
loaNoTraf	Lcas loss of alignment channels w/wo traffic
acMstTimeout	Lcas acMst timeout
rsAckTimeout	Lcas RS-ack timeout
eosMultiple	Lcas two or more channels have EOS
eosMissing	Lcas one channel has EOS
sqNonCont	Lcas missing SQ detected in set of channels
sqMultiple	Lcas equal SQ for two or more channels
sqOor	Lcas SQ outside of range
gidErr	Lcas Group Id different for active channels
ctrlOor	Lcas undefined Ctrl-word for one or more channels
lcasCrc	Lcas CRC error detected
nonLcas	Lcas non-Lcas source detected
mnd	Lcas member not deskewable
fopr	Lcas failure of protocol
plcr	Lcas partial loss of capacity receive
tlcr	Lcas total loss of capacity receive
plct	Lcas partial loss of capacity transmit
tlct	Lcas total loss of capacity transmit