This procedure provides an example for establishing an Ethernet packet ring on a bidirectional line switched ring (BLSR) without using Nonpreemptible Unprotected Traffic (NUT) access (Release 3 and later). A packet ring is a set of Ethernet switches (Ethernet circuit packs) connected to each other in a ring configuration. When the packet ring is first established, the capacity of the ring is predetermined by the number of STS-1 cross-connections (1-21 [LNW67/68], 1-48 [LNW70/LNW170]) applied to the ring and switches. The tagging mode, virtual switch ID, and spanning tree group is also predetermined. For example, see Figure 11-8, SONET layer BLSR protected Ethernet packet ring on a BLSR without NUT.
This procedure assumes that the BLSR ring network configuration has already been established and no alarms are present.
This procedure uses TL1 commands and specific WaveStar® CIT menu selections to illustrate the detailed provisioning parameters.
Important!
This configuration is only possible using the LNW67/68/70 GbE circuit packs. The LNW70/LNW170 circuit pack allows cross-connections to any of the 32 VCGs in SWITCHED mode. On the LNW67/68 circuit packs, cross-connections must be made to both VCG 1 and VCG 3, therefore requiring all 4 VCGs. The LNW66 FE circuit pack only has 2 VCGs. No multipoint cross-connections are allowed in this configuration.
Prior to performing this procedure, refer to Before you begin and Required equipment in this chapter and you must have complete work instructions for this procedure that detail:
The network configuration and the nodes participating in the packet ring network.
The shelf slots, circuit packs, ports, VCGs involved in the packet ring network.
The number and type of cross-connections to be made at each node.
For circuit packs not supporting LCAS, once the capacity of the packet ring is established, additional capacity (cross-connections) may not be added in service without service interruption.
The tagging mode (transparent or 802.1q), virtual switch ID, and spanning tree group ID.
Use this procedure as an example to establish an Ethernet packet ring on a BLSR ring. See Figure 11-8, SONET layer BLSR protected Ethernet packet ring on a BLSR without NUT for an example.
1 |
Use the WaveStar® CIT to log in to one of the terminating nodes, if not already performed. Reference: Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar® CIT session | ||||||||
2 |
On the System View menu, select Administration → OSI Routing Map to retrieve a node-to-node listing of every node in the network. As an alternative, you can select View → Rings → Ring Map from the System View menu, then select the 2F BLSR port protection group and click Select. Select NVMRING in the Ring Map Source selection box. You may also Display Ring Map Graph using this command. Important! If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the ring (indicating node-to-node connections) and list each node's TID. Result: The OSI Neighbor Map window opens if the Administration → OSI Routing Map command was used. A list of NEs and NE neighbors is displayed if the View → Rings → Ring Map command was used. | ||||||||
3 |
Verify that the system configuration is the same as specified on your work instructions. | ||||||||
4 |
From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the packet ring being established. | ||||||||
5 |
Verify that the Ethernet circuit packs have been installed into the required slot of the Function Unit or Growth group (A, B, C, D, or G) at each NE providing Ethernet service. Reference: Procedure 4-13: Install Gigabit Ethernet circuit packs | ||||||||
6 |
Important! If the Ethernet circuit pack is already in service, the existing tagging mode cannot be changed without removing all existing service. CONFIGURE TAGGING MODE Determine the existing tagging mode for the circuit pack being provisioned. Use the TL1 rtrv-eqpt command or select View → Equipment from the System View menu, select the CP, then click Select. Note the VLAN Tagging Mode and other parameter values. The VLAN Tagging Mode for the LNW67/68 circuit packs must be set to TRANS or 802.1TAG. The VLAN Tagging Mode for the LNW70/LNW170 circuit packs must be set to SWITCHED. Important! When GbE circuit packs are installed in the shelf, the default "NOTAG" mode is assigned to the circuit pack. | ||||||||
7 |
Select one of the following:
| ||||||||
8 |
If you are going to change the VLAN Tagging Mode that presently exists AND a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode. Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1 rtrv-vrtsw command or select the View → Data → Virtual Switch command from the System View menu, select the GbE circuit pack being provisioned, then click Select. Note if a virtual switch ID has been assigned. | ||||||||
9 |
If required, use the TL1 dlt-vrtsw command or select the Configuration → Data → Delete Virtual Switch command from the System View menu, select the circuit pack being provisioned, then click Select. Highlight the VRTSW ID being deleted, then click Apply. Read the warning message, then click Yes to execute the command. Click Close to exit. | ||||||||
10 |
Use the TL1 ed-eqpt command or select the Configuration → Equipment command from the System View menu, select the circuit pack being provisioned, then click Select. Verify/Select the tagging mode (802.1TAG, TRANS [LNW66,67,68], or SWITCHED [LNW70/LNW170]) in the VLAN Tagging Mode box. | ||||||||
11 |
Verify/Enter other parameter values (for example, Burst Size, Credit Interval[LNW67/68], Ethernet Cross Connect Mode and Port Configuration [LNW70/LNW170]), as required, then click Apply. Read the warning message, then click OK to make your changes. Click Close to exit. Reference: Procedure 11-13: Provision Ethernet circuit pack parameters | ||||||||
12 |
Once a virtual switch is created and service has been established on the circuit pack, you cannot delete the virtual switch without interrupting service. ASSIGN VIRTUAL SWITCH ID
| ||||||||
13 |
ESTABLISH SONET CROSS-CONNECTIONS Determine the necessary cross-connections to be made at each terminating node and any pass-through cross-connections to made at any non terminating nodes in the network. | ||||||||
14 |
One at a time at each node in the network, use the TL1 ent-crs-sts1 command to provision the cross-connections. Or, select Configuration → Cross-Connections from the System View menu to start the Cross-Connection Wizard. Use the Cross-Connection Wizard to provision the 2F BLSR Add/Drop Ethernet and 2-Way Point-to-Point, Through pass-through cross-connections. For example, see Figure 11-8, SONET layer BLSR protected Ethernet packet ring on a BLSR without NUT. Important! Cross-connections at the terminating nodes must be made to both VCG 1 and VCG 3. Reference: Refer to Procedure 11-24: Make cross-connections for Ethernet service for cross-connection examples. | ||||||||
15 |
From the System View menu, select View → Cross-Connections to verify that the proper connections have been made. | ||||||||
16 |
Important! For LNW70/LNW170 circuit packs, each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG. Select View → Data → Ethernet/Data/VCG Port to verify that VCG Membership has been Enabled in both Input and Ouput Direction. If required, use the TL1 ed-vcgtrib command to enable tributaries, or from the System View menu at each node, select Configuration → Equipment. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click Select. Select Enabled for the VCG Membership in both the Input and Output Direction. Click Apply, read the warning message, then click Yes to execute the command. Repeat this step for each tributary being enabled. Click Close to exit. When Input VCG Membership (source) (inmbs) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When Output VCG Membership (sink) (outmbs) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network). Reference: Procedure 11-33: Provision LCAS, add/enable/remove tributaries | ||||||||
17 |
After all cross-connections are made, click on the Alarm List button on the System View window and verify no alarms are present. | ||||||||
18 |
If alarms are present, look for missing or improperly made cross-connections. Reference: Alcatel-Lucent 1665 Data Multiplexer (DMX) Alarm Messages and Trouble Clearing Guide, 365-372-302 | ||||||||
19 |
Important! For LNW70/LNW170 circuit packs, at least one tributary at each end of the circuit must be Enabled in order for the VCG to go in service. If required, after all cross-connections have been made, verify that the WAN (VCG) Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select View → Data → Ethernet/Data/VCG Port. Result: The View LAN (Ethernet) WAN (VCG) Port window opens. | ||||||||
20 |
Expand the details for the circuit pack being used. Select the required VCG v( ) port, then click Select at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display. | ||||||||
21 |
Click on the VCG Data tab. Under the Fault section of the parameter display, verify the VCG Monitoring Mode is IS (in service). If the VCG Monitoring Mode is IS, proceed to Step 22.
Reference: Alcatel-Lucent 1665 Data Multiplexer (DMX) Alarm Messages and Trouble Clearing Guide, 365-372-302 | ||||||||
22 |
CREATE SPANNING TREE GROUP If required, determine a preferred spanning tree configuration (span to be blocked under nominal conditions), the preferred root node, and spanning tree root priorities for this service. Important! It is not necessary to determine a preferred spanning tree configuration. A default spanning tree configuration is configured when you establish the spanning tree group. Reference: Procedure 11-25: Create preferred spanning tree configuration | ||||||||
23 |
Use the TL1 ent-stgrp command to assign and provision the parameters for the ports involved in the spanning tree group. Or select Configuration → Data → Create Spanning Tree Group command from the CIT System View menu. For example, see Figure 11-8, SONET layer BLSR protected Ethernet packet ring on a BLSR without NUT. Important! Both VCGs at each terminating node must be part of the same spanning tree group. Spanning tree default parameters support a network of up to nine nodes. Networks running 802.1w rapid spanning tree protocol (Release 2 or later) support more than nine nodes participating in a spanning tree. To support more than nine nodes in the spanning tree, the maximum age timer must be increased. Note that spanning tree restoration time increases as the number of nodes increase. If the network consists of more than nine (9) nodes which are participating in the spanning tree configuration, use the following formula to determine the proper setting for the spanning tree maximum age timer (stmaxage): 2N + 6, where N equals the number of nodes. For example, if the network consists of 16 nodes, then the stmaxage timer should be set to 38 seconds: 2 x (16) + 6= 38. | ||||||||
24 |
Repeat all the assignments in this procedure at each Ethernet node in the network. End of steps |
November 2011 | Copyright © 2011 Alcatel-Lucent. All rights reserved. |