This procedure assumes that an existing “working” unprotected LNW170 circuit pack is already installed in the shelf and you want to establish protected LNW170 LAG groups. It is assumed the existing LNW170 VLAN Tagging Mode is provisioned as SWITCHED and is in service.
The following is required after both slots are equipped with LNW170 circuit packs, before changing the Slot Protection State to PROT:
The VLAN Tagging Mode on both circuit packs must be set to SWITCHED.
The Port Configuration must result in the same port rates on the companion LAG ports (ports 1, 2, 5 or 6) on the companion circuit packs. For example, GT_FX and FT_FX are NOT compatible.
The Ethernet Cross Connect Mode and Transmission Audit parameters must be set the same on both circuit packs.
There must not be any Link Aggregation Groups (LAGs) provisioned on either companion circuit pack.
Only the circuit pack selected in setting Slot Protection State to PROT can be provisioned with cross-connections or virtual switches, and the provisioned virtual switches cannot be on ports 3, 4, 7 or 8. The ports will be unavailable after the Protection State is provisioned to PROT.
Complete the following steps to change the Slot Protection State from Unprotected to Protected for a Function/Growth group equipped with LNW170 100/1G FXS circuit pack(s):
1 |
Important! If the Function/Growth group is equipped with a working LNW170 100/1G FXS circuit pack and the companion circuit pack is a different circuit pack type, the companion circuit pack must be removed before changing the Slot Protection State to Protected. Two circuit packs that are different circuit pack types are not compatible when the Slot Protection State is Protected. If required, remove the companion circuit pack from the affected Function/Growth group according to local procedures and select Configuration → Update System → Update All. | ||
2 |
Important! All virtual switches and cross-connections must be removed from ports 3, 4, 7 and 8 on the installed working circuit pack. If service is being provided on those ports, the service must be moved/removed before continuing with this procedure. If required, use the Configuration → Data → Delete Virtual Switch and/or Configuration → Cross-Connections command to delete the required virtual switches or cross-connections on ports 3, 4, 7 and 8. | ||
3 |
Important! Any PTMs installed in ports 3, 4, 7, or 8 must be removed. Remove any PTM’s from ports 3, 4, 7, or 8 on both LNW170 circuit packs. | ||
4 |
Important! No provisioned Link Aggregation Groups can exist on the installed working LNW170 100/1G FXS circuit pack. From the System View, select View → Data → LA Group, select (highlight) the required LNW170 100/1G FXS circuit pack, then click Select. Verify that no Link Aggregation Groups exist on the circuit pack. If required, select Configuration → Data → Create/Modify/Delete LA Group to delete any Link Aggregation Groups on the required LNW170 100/1G FXS circuit pack. Reference: Procedure 11-38: Create/Modify/Delete link aggregation group (LAG) | ||
5 |
Install an LNW170 in the companion slot. Reference: Procedure 4-14: Install Gigabit Ethernet circuit packs | ||
6 |
From the System View, select Configuration → Equipment, select the newly inserted LNW170 100/1G FXS circuit pack, then click Select. Provision the VLAN Tagging Mode to SWITCHED, Ethernet Cross Connect Mode, Transmission Audit, and Port Configuration port rates the same as the companion circuit pack. Provision other parameters as required. If required, select the working LNW170 100/1G FXS circuit pack, then click Select. View the existing Port Configuration and Ethernet Cross Connect Mode parameter settings to be used. | ||
7 |
Changing the Slot Protection State of the LNW170 100/1G FXS circuit pack causes a circuit pack reset which may take up to several minutes to complete and disrupt service. Wait until the circuit pack reset is complete before performing additional provisioning. From the System View, select Configuration → Equipment, select the original working LNW170 100/1G FXS circuit pack, then click Select. Provision the Slot Protection State to PROT. Result:
Reference: Procedure 4-15: Provision Ethernet circuit packs/LAN port/VCG for service | ||
8 |
Select View → Equipment to access the affected circuit packs and verify that the Slot Protection State changed to Protected. | ||
9 |
If required, use the TL1 ed-eport command to provision the LAG member LAN ports and LAG port parameters, or select Configuration → Equipment from the System View menu. Expand the details for the circuit pack, select the LAG group or expand the details for the LAG group, highlight the member LAN port, then click Select. Provision the parameters as required. Reference: Procedure 11-8: Provision Ethernet LAN port parameters | ||
10 |
If required, use the TL1 ent-erate command to provision the LAG related QoS parameters, or select Configuration → Data → Provision QoS Service from the System View menu. Expand the details for the circuit pack, highlight the LAG port, then click Select. Provision the parameters as required. Reference: Procedure 11-23: Provision Ethernet quality of service (QoS) - LNW70/LNW170 | ||
11 |
If required, use the TL1 ed-lagrp command to modify the LAG, or select Configuration → Data → Create/Modify/Delete LA Group from the System View menu. Select (highlight) the circuit pack, then click Select. Modifying a LAG consists of changing the hashtype, or changing the protocol parameter.
| ||
12 |
Click twice in the Hash Type or Protocol box. Select the Hash Type or Protocol value, as required. Click Apply, read the warning message then click Yes to execute the command. Click Close to exit. | ||
13 |
As required, complete other L2 provisioning (for example, virtual switch, vlan, spanning tree groups, cross-connections) using the procedures in this chapter. | ||
14 |
A default port tag (Virtual LAN tagging mode Transparent) or default VLAN (Virtual LAN tagging mode 802.1 Tag) must be provisioned for the LAG group in order to pass any untagged frames. Perform one of the following as required:
End of steps |
November 2011 | Copyright © 2011 Alcatel-Lucent. All rights reserved. |