This procedure provides an example for configuring point-to-point BLSR protected GbE Ethernet service using the 802.1q tagging mode. See Figure 11-12, Point-to-Point GbE using 802.1q tagging mode for an example.
This procedure uses TL1 commands and specific WaveStar® CIT menu selections to illustrate the detailed provisioning parameters. If you prefer, you can use the Data Provisioning Wizard to perform the provisioning in this procedure. From the System View menu, select Configuration → Ethernet Service to invoke the wizard.
Important!
On connected Gigabit Ethernet devices with autonegotiation turned on/enabled, if transmission is interrupted in one direction of transmission on a Gigabit Ethernet device, then transmission will also be disabled in the other direction. For example, if one fiber in a transmit/receive pair is cut, then one-way transmission on the other fiber can be maintained only if autonegotiate is turned off/disabled and the link state is forced good at the transmit source equipment.
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:
Use this procedure as an example for configuring point-to-point BLSR protected GbE Ethernet service using the 802.1q tagging mode. See Figure 11-12, Point-to-Point GbE using 802.1q tagging mode 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 Neighbor Map command and note the NEs connected to Main 1 and Main 2. Access each of the NEs identified and select the Administration → OSI Neighbor Map command and note the NEs connected to Main 1 and Main 2. Repeat the above until the backbone ring can be sketched. 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 Neighbor 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 service to be established. | ||||||||
5 |
Important! If the Ethernet circuit pack is already in service, the existing tagging mode cannot be changed without removing all existing cross-connections and virtual switch provisioning. CONFIGURE TAGGING MODE Determine the existing tagging mode and parameters 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 802.1TAG. The VLAN Tagging Mode for the LNW70/LNW170 circuit packs must be set to SWITCHED. | ||||||||
6 |
Select one of the following:
| ||||||||
7 |
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. If a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode. | ||||||||
8 |
If a virtual switch has been provisioned, delete it by using the TL1 dlt-vrtsw command or select the Configuration → Data → Delete Virtual Switch command from the System View menu, highlight 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. | ||||||||
9 |
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. | ||||||||
10 |
Verify/Select the tagging mode in the Select VLAN Tagging Mode box. | ||||||||
11 |
Verify/Enter other parameter values (for example, Burst Size, Credit Interval[LNW67/68], Ethernet Cross Connect Mode [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. If the service you are establishing in this procedure is a second service on an existing GbE circuit pack with all LAN/WAN ports in the same virtual switch, then the existing virtual switch ID must be retained or the ports not in service must be removed from the existing virtual switch and added to a new virtual switch ID. ASSIGN VIRTUAL SWITCH ID
| ||||||||
13 |
ESTABLISH SONET CROSS-CONNECTIONS Determine the necessary 2F BLSR Add/Drop and 2-Way Point-to-Point, Through cross-connections to be made at each terminating and non terminating node in the network. Important! Note that full rate Gigabit service requires 21 STS-1 or equivalent cross-connections. | ||||||||
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 at each of the non terminating nodes in the network to provision the 2-Way Point-to-Point, Through cross-connections, and at the terminating Ethernet nodes to provision the 2F BLSR Add/Drop cross-connections. Important! Note that cross-connections at the terminating nodes are add/drop and cross-connections at the non terminating nodes are pass-through. Reference: Procedure 11-24: Make cross-connections for Ethernet service | ||||||||
15 |
From the System View menu, select View → Cross-Connections at each node 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 |
After the VLAN ID for customer untagged frames is assigned and service is established in the 802.1q mode, changing the VLAN ID may affect service. If the VLAN IDs are different, service will be affected. When the VLAN ID for customer untagged frames is changed at one point in the network, the VLAN ID must be changed at all points. ASSIGN VLAN IDs Use the TL1 ent-vlan command to assign the default VLAN ID for customer untagged frames or the customer VLAN ID for tagged frames to the associated LAN ports and VCG WAN ports. Or select Configuration → Data → Create VLAN command from the CIT System View menu. For example, see Figure 11-12, Point-to-Point GbE using 802.1q tagging mode. Reference: In Figure 11-12, Point-to-Point GbE using 802.1q tagging mode, assume a GbE circuit pack is installed in Function slot d-1 and LAN port 2 at each circuit pack is used for service. Note that a service has been established between Node 1 and Node 3 for customer untagged frames using a default VLAN ID of 34. Note that a service has been established between Node 1 and Node 3 for customer tagged frames using a VLAN ID of 55. | ||||||||
23 |
PROVISION LAN PORTS Use the TL1 ed-eport command to provision the LAN port parameters, or select Configuration → Equipment from the System View menu. Expand the details for the circuit pack, highlight the LAN Port, then click Select. Provision the parameters as required. Reference: Procedure 11-11: Provision Ethernet LAN port parameters | ||||||||
24 |
Click Apply. Read the warning message, then click Yes to execute the command. | ||||||||
25 |
PROVISION VCGS Use the ed-vcg TL1 command to provision the WAN (VCG) port parameters, or select Configuration → Equipment from the System View menu, if window is not already open from the previous step. Expand the details for the circuit pack, highlight the VCG port, then click Select. Provision the parameters as required. Reference: Procedure 11-12: Provision Ethernet VCG parameters | ||||||||
26 |
Click Apply. Read the warning message, then click Yes to execute the command. Click Close to exit or repeat from Step 23 for other port provisioning. End of steps |
November 2011 | Copyright © 2011 Alcatel-Lucent. All rights reserved. |