Device Management
Device Management
Device Management
2017 Device management
Device management
Contents
1. 9 Device support
1.1. 9.1 Device support overview
1.1.1. Devicespecific release information
1.1.2. Devicespecific guides
1.2. 9.2 Sample workflow to configure and manage devices
1.3. 9.3 1830 PSS support
1.4. 9.4 1830 PSS OCS support
1.5. 9.5 5780 DSC support
1.6. 9.6 7210 SAS support
1.6.1. 7210 SASD support
1.6.2. 7210 SASE support
1.6.3. 7210 SASK support
1.6.4. 7210 SASM support
1.6.5. 7210 SASMxp support
1.6.6. 7210 SASR support
1.6.7. 7210 SAST support
1.6.8. 7210 SASX support
1.6.9. System resource profile
1.7. 9.7 7450 ESS support
1.7.1. Automatic provisioning for CPM5 SFMs
1.8. 9.8 7705 SAR support
1.8.1. 7705 SAR MWA support
1.8.2. 7705 SAR NEtO support
1.8.3. 7705 SAR SCADA support
1.8.4. 7705 SAR auxiliary alarm daughter cards
1.8.5. 7705 SAR 6port E&M daughter cards
1.8.6. 7705 SAR 12port SDI card
1.8.7. 7705 SAR ISC
1.8.8. 7705 SAR Power Injector card
1.8.9. 7705 SAR Optical Add/Drop Mux cards
1.8.10. 7705 SAR CSMv2 card
1.8.11. 7705 SAR 2 x 10Gig Bridged Ethernet XFP + 1 x 2.5G Virtual Ethernet card
1.8.12. 7705 SAR 6port FXS Adapter card
1.8.13. 7705 SAR 8port FXO Adapter card
1.8.14. 7705 SAR 10port 1GigE/1port 10GigE XAdapter card
1.8.15. 7705 SAR 8port GigE SFP card (48/+24 V dc)
1.8.16. 4 x 10/100/1000 1Gig SFP + 1 x 10Gig SFP + 1 x 10Gig XFP card
1.8.17. 7705 SAR GPS receiver module
1.8.18. 7705 SAR Packet Microwave card
1.8.19. 7705 SAR Voice & TeleProtection MDA
1.8.20. 7705 SARA
1.8.21. 7705 SARF
1.8.22. 7705 SARH
1.8.23. 7705 SARHc
1.8.24. 7705 SARM
1.8.25. 7705 SARW
1.8.26. 7705 SARWx
1.8.27. 7705 SARX
1.8.28. Dynamic system IP address updates for 7705 SAR nodes
1.9. 9.9 7710 SR support
1.10. 9.10 7750 SR MG support
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 1/269
06.07.2017 Device management
1.11. 9.11 7750 SR support
1.11.1. Automatic provisioning for CPM5 SFMs
1.12. 9.12 7850 VSG/VSA support
1.13. 9.13 7950 XRS support
1.13.1. Variants
1.13.2. Shelf components
1.14. 9.14 9471 WMM support
1.15. 9.15 9500 MPR and 9500 MPRe support
1.16. 9.16 9966 MS SC Gateway support
1.17. 9.17 eNodeB support
1.18. 9.18 OmniSwitch support
1.18.1. OmniSwitch LAG objects
1.18.2. Using WebView to manage an OmniSwitch
1.18.3. OmniSwitch port modes
1.19. 9.19 GNE support
1.19.1. GNE drivers
1.19.2. Statistics support
1.19.3. Alarm support
2. 10 Device commissioning and management
2.1. 10.1 Device commissioning overview
2.1.1. Inband and outofband management
2.1.2. IPv6 device management
2.1.3. Secure file transfers
2.2. 10.2 GNE commissioning
2.2.1. GNE drivers
2.2.2. Invoking alternate element managers
2.2.3. GNE profiles
2.2.4. Configuring userdefined alarms for GNEs
2.3. 10.3 Workflow to commission AlcatelLucent devices
2.4. 10.4 Device commissioning procedures
2.4.1. Procedure 101 To commission a device for 5620 SAM management
2.4.2. Procedure 102 To commission an OmniSwitch for 5620 SAM management
2.4.3. Procedure 103 To configure the 5620 SAM SNMP trap sources
2.4.4. Procedure 104 To configure polling for a 7450 ESS, 7705 SAR, 7710 SR, 7750 SR,
or 7950 XRS
2.4.5. Procedure 105 To configure polling for a 7210 SAS
2.4.6. Procedure 106 To edit polling settings for multiple devices
2.5. 10.5 Workflow to commission GNEs
2.6. 10.6 GNE commissioning procedures
2.6.1. Procedure 107 To prepare a GNE for 5620 SAM management
2.6.2. Procedure 108 To configure an alternate EMS for a specific GNE
2.6.3. Procedure 109 To modify a GNE profile
2.6.4. Procedure 1010 To create a GNE alarm catalog
2.6.5. Procedure 1011 To create a transform function for a GNE alarm catalog
2.6.6. Procedure 1012 To add an alarm mapping to a GNE alarm catalog
2.6.7. Procedure 1013 To delete a GNE alarm catalog
3. 11 Device discovery
3.1. 11.1 Device discovery overview
3.1.1. Device discovery using IPv6
3.1.2. Device SNMP management
3.1.3. Device management states
3.1.4. Using multiple management interfaces
3.1.5. Postdiscovery actions on discovered NEs
3.2. 11.2 Configuring SSH security on devices
3.2.1. SSH2 host key management
3.2.2. SSH2 and device CLI sessions
3.2.3. SSH2 and script management
3.2.4. SSH2 and secure file transfers
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 2/269
06.07.2017 Device management
3.3. 11.3 Device mediation policies
3.3.1. Event notification polices
3.4. 11.4 NE resynchronization
3.4.1. Initial synchronization
3.4.2. Resynchronization status
3.5. 11.5 Server resource management
3.6. 11.6 Workflow for device discovery
3.7. 11.7 Device discovery procedures
3.7.1. Procedure 111 To enable SNMPv3 management of a device
3.7.2. Procedure 112 To enable or disable SNMP streaming on an NE
3.7.3. Procedure 113 To verify that SSH2 is enabled on a device
3.7.4. Procedure 114 To enable SSH host key persistence on a device
3.7.5. Procedure 115 To configure device mediation
3.7.6. Procedure 116 To assign an event notification policy to an NE
3.7.7. Procedure 117 To configure a management network
3.7.8. Procedure 118 To configure an additional management interface on a main server
3.7.9. Procedure 119 To configure an additional management interface on an auxiliary
server
3.7.10. Procedure 1110 To configure a postdiscovery action
3.7.11. Procedure 1111 To configure a discovery rule
3.7.12. Procedure 1112 To enable, disable, or delete a discovery rule
3.7.13. Procedure 1113 To view the postdiscovery action execution status
3.7.14. Procedure 1114 To manage a postdiscovery action failure on an NE
3.7.15. Procedure 1115 To manage, suspend, or unmanage a device
3.7.16. Procedure 1116 To change from SNMPv2 to SNMPv3 management of a device
3.7.17. Procedure 1117 To switch from nonsecure to secure mediation
3.7.18. Procedure 1118 To specify which management address the 5620 SAM uses to
remanage a device
3.7.19. Procedure 1119 To rescan the network for a device according to a discovery rule
3.7.20. Procedure 1120 To partially or fully resynchronize NEs with the 5620 SAM
database
3.7.21. Procedure 1121 To manually accept a mismatched SSH host key
3.7.22. Procedure 1122 To view the SSH2 host keys to identify active and mismatched
keys
3.7.23. Procedure 1123 To list and save SNMP MIB information
3.7.24. Procedure 1124 To delete a device from the managed network
4. 12 Device CLI sessions
4.1. 12.1 Device CLI sessions overview
4.1.1. vi editor support
4.2. 12.2 Workflow to use a 5620 SAM CLI
4.3. 12.3 CLI procedures
4.3.1. Procedure 121 To configure the 5620 SAM CLI console preferences
4.3.2. Procedure 122 To open and close a 5620 SAM device CLI session
5. 13 Working with network objects
5.1. 13.1 Working with network objects overview
5.1.1. Object deployment status
5.2. 13.2 Working with equipment group objects
5.3. 13.3 Working with physical links
5.4. 13.4 Workflow to manage network objects
5.5. 13.5 Working with network objects procedures
5.5.1. Procedure 131 To monitor the deployment status of a network object
5.5.2. Procedure 132 To view network resources assigned to network objects
6. 14 Device object configuration
6.1. 14.1 Device object configuration overview
6.2. 14.2 Working with device objects
6.3. 14.3 Working with ring group objects
6.4. 14.4 Workflow to manage device objects
6.5. 14.5 General device configuration procedures
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 3/269
06.07.2017 Device management
6.5.1. Procedure 141 To create an object
6.5.2. Procedure 142 To modify NE properties
6.5.3. Procedure 143 To configure NE custom properties
6.5.4. Procedure 144 To enable FIPS1402
6.5.5. Procedure 145 To create an operational group
6.5.6. Procedure 146 To configure a 7210 SAS operational group
6.5.7. Procedure 147 To enable and configure global cflowd sampling on an NE
6.5.8. Procedure 148 To enable the automatic selection of an RD on an NE
6.5.9. Procedure 149 To add a span of control to an NE
6.5.10. Procedure 1410 To configure load balancing
6.5.11. Procedure 1411 To enable or disable 802.1X
6.5.12. Procedure 1412 To configure an exclusive policy editing restriction on an NE
6.5.13. Procedure 1413 To configure active card alarms on an NE
6.5.14. Procedure 1414 To configure a TWAMP server
6.5.15. Procedure 1415 To enable LLDP on an NE
6.5.16. Procedure 1416 To configure the BFD flap detection interval on an NE
6.5.17. Procedure 1417 To enable a Q in Q untagged SAP on an NE
6.5.18. Procedure 1418 To configure DHCPv6 Advertise messages on an NE
6.5.19. Procedure 1419 To configure Python script protection on an NE
6.5.20. Procedure 1420 To configure SFLOW on an NE
6.5.21. Procedure 1421 To create a chassislevel PBB configuration
6.5.22. Procedure 1422 To configure serving network information on an NE
6.5.23. Procedure 1423 To configure L2TP on an NE
6.5.24. Procedure 1424 To configure WLAN GW redundancy on an NE
6.5.25. Procedure 1425 To configure the RADIUS CoA port on an NE
6.5.26. Procedure 1426 To configure data persistence on an NE
6.5.27. Procedure 1427 To configure DNS security extensions
6.5.28. Procedure 1428 To enable or disable ICMP extensions on a NE
6.5.29. Procedure 1429 To configure a noservice loopback port on the 7210 SAS
6.5.30. Procedure 1430 To configure CFM DMM version 1 interoperability on the 7210
SAS
6.5.31. Procedure 1431 To configure two WRED slopes on a 7210 SAS
6.5.32. Procedure 1432 To configure framebased accounting for QoS policies on a 7210
SAS
6.5.33. Procedure 1433 To configure the global system resource profile on a 7210 SAS
6.5.34. Procedure 1434 To configure a system resource profile policy for the 7210 SASR
6.5.35. Procedure 1435 To configure portbased scheduling on the 7210 SASR
6.5.36. Procedure 1436 To configure buffer management for the 7210 SAS
6.5.37. Procedure 1437 To configure watermark settings on a 7705 SAR
6.5.38. Procedure 1438 To configure QoS ingress aggregate rates on the 7705 SARM/ME
6.5.39. Procedure 1439 To launch an MCT on a 9500 MPRe NE connected to a 7705 SAR
6.5.40. Procedure 1440 To start and stop a Webview or Secure Webview session on an
OmniSwitch
6.5.41. Procedure 1441 To configure the dying gasp alarm on an OmniSwitch
6.6. 14.6 Ring group configuration procedures
6.6.1. Procedure 1442 To create a ring group
6.6.2. Procedure 1443 To remove a device from a ring group or a ring group
7. 15 Logical group object configuration
7.1. 15.1 Logical group object configuration overview
7.2. 15.2 Working with CCAG objects
7.3. 15.3 Working with ISAAA groups
7.4. 15.4 Working with ISATunnel groups
7.5. 15.5 Working with ISALNS groups
7.6. 15.6 Working with ISANAT groups
7.7. 15.7 Working with ISAVideo groups
7.8. 15.8 Working with ISAWLAN GW groups
7.8.1. WLAN GW tunnels
7.9. 15.9 Working with IGH objects
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 4/269
06.07.2017 Device management
7.10. 15.10 Working with LAG objects
7.10.1. LAG link mapping profiles
7.10.2. LAG utilization TCAs
7.10.3. BFD on Ethernet LAGs
7.11. 15.11 Workflow to manage logical group objects
7.12. 15.12 Workflow to configure weighted perlink hashing on a LAG
7.13. 15.13 Logical group object configuration procedures
7.13.1. Procedure 151 To configure a CCAG
7.13.2. Procedure 152 To configure an ISAAA group and ISAAA partitions
7.13.3. Procedure 153 To configure AA subscriber statistics collection on an ISAAA group
or partition
7.13.4. Procedure 154 To configure special study objects on an ISAAA group or partition
7.13.5. Procedure 155 To configure an AA subscriber policy override on an ISAAA group
or partition
7.13.6. Procedure 156 To configure cflowd collectors on an ISAAA group or partition
7.13.7. Procedure 157 To configure an ISAtunnel group
7.13.8. Procedure 158 To configure an ISALNS group
7.13.9. Procedure 159 To configure an ISAVideo group
7.13.10. Procedure 1510 To configure an ISAWLAN GW group
7.13.11. Procedure 1511 To create an IGH and add members
7.14. 15.14 LAG configuration procedures
7.14.1. Procedure 1512 To create a LAG
7.14.2. Procedure 1513 To modify a LAG
7.14.3. Procedure 1514 To manually rebalance LAG subscribers
7.14.4. Procedure 1515 To configure an OmniSwitch LAG
7.14.5. Procedure 1516 To configure OmniSwitch dynamic LAG members
7.14.6. Procedure 1517 To create a LAG link mapping profile
7.14.7. Procedure 1518 To view microBFD sessions on a LAG
8. 16 Shelf object configuration
8.1. 16.1 Shelf object configuration overview
8.2. 16.2 Working with shelf objects
8.2.1. Chassis modes
8.2.2. Timing synchronization
8.2.3. SCADA on the 7705 SAR
8.2.4. Power management on the 7950 XRS
8.2.5. Reboot hold
8.3. 16.3 Working with card and card slot objects
8.3.1. Card provisioning and chassis modes
8.4. 16.4 Working with daughter card objects
8.4.1. IMM daughter cards
8.4.2. MDA modes for the 7705 SAR
8.5. 16.5 Working with bundle objects
8.5.1. Multilink PPP bundles
8.5.2. IMA group bundles
8.5.3. FR group bundles
8.6. 16.6 Workflow to manage shelf objects
8.7. 16.7 Shelf object configuration procedures
8.7.1. Procedure 161 To configure the device chassis mode
8.7.2. Procedure 162 To configure a VWM shelf for a 7210 SAS
8.7.3. Procedure 163 To configure 7210 SAS dry contact sensors
8.7.4. Procedure 164 To configure the IMM card type on a 7210 SASR
8.7.5. Procedure 165 To configure switch fabric multicast ingress replication rates
8.7.6. Procedure 166 To configure IMPM overrides
8.7.7. Procedure 167 To enable mixed mode
8.7.8. Procedure 168 To configure timing synchronization
8.7.9. Procedure 169 To configure an IEEE 1588 PTP clock on a 7705 SAR
8.7.10. Procedure 1610 To configure an IEEE 1588 PTP port on a 7705 SAR
8.7.11. Procedure 1611 To configure system time on a 7705 SAR
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 5/269
06.07.2017 Device management
8.7.12. Procedure 1612 To configure SNTP on a 7705 SAR
8.7.13. Procedure 1613 To configure NTP on supported devices
8.7.14. Procedure 1614 To configure SCADA on a 7705 SAR
8.7.15. Procedure 1615 To configure a 7705 SAR MW link
8.7.16. Procedure 1616 To configure a 7705 SAR MW link member
8.7.17. Procedure 1617 To configure 7705 SAR auxiliary alarm definitions
8.7.18. Procedure 1618 To configure the IEEE 1588 PTP clock on a 7210 SAS, 7450 ESS,
or 7750 SR
8.7.19. Procedure 1619 To configure the IEEE 1588 PTP peer of a 7210 SAS, 7450 ESS,
or 7750 SR
8.7.20. Procedure 1620 To manage an OmniSwitch running configuration
8.7.21. Procedure 1621 To configure OmniSwitch health monitoring
8.7.22. Procedure 1622 To configure a CCM on a 7950 XRS20
8.7.23. Procedure 1623 To manage the internal fan on a 7210 SASD
8.7.24. Procedure 1624 To configure a power supply tray
8.7.25. Procedure 1625 To configure a power management zone on a 7950 XRS
8.7.26. Procedure 1626 To provision an APEQ on a 7950 XRS
8.7.27. Procedure 1627 To configure a variable power supply APEQ on a 7950 XRS
8.8. 16.8 Card and card slot object configuration procedures
8.8.1. Procedure 1628 To assign a card type
8.8.2. Procedure 1629 To configure egress WRED queue control on an XCM, IOM 3 or
IMM forwarding plane
8.8.3. Procedure 1630 To configure IMPM on an XCM, 2 x XP MDA IOM 3, or IMM
forwarding plane
8.8.4. Procedure 1631 To configure an ingress queue group on a forwarding plane
8.8.5. Procedure 1632 To configure NE DDoS protection on a forwarding plane
8.8.6. Procedure 1633 To enable named pool mode
8.8.7. Procedure 1634 To enable Stable Pool Sizing
8.8.8. Procedure 1635 To enable Ingress Buffer Allocation
8.8.9. Procedure 1636 To select system resource profile policies for the 7210 SASR
8.8.10. Procedure 1637 To configure OmniSwitch stacks
8.8.11. Procedure 1638 To configure an OmniSwitch CPU temperature threshold
8.8.12. Procedure 1639 To configure a CPM on a 7950 XRS
8.9. 16.9 Daughter card slot object configuration procedures
8.9.1. Procedure 1640 To configure an MDA
8.9.2. Procedure 1641 To configure IMPM on an MDA
8.9.3. Procedure 1642 To view the operational multicast channel properties of an MDA
8.9.4. Procedure 1643 To configure a module card on a 7705 SARM/ME or 7705 SARH
8.10. 16.10 Bundle configuration procedures
8.10.1. Procedure 1644 To create an FR group bundle
8.10.2. Procedure 1645 To modify an FR group bundle
8.10.3. Procedure 1646 To create an IMA group bundle
8.10.4. Procedure 1647 To modify an IMA group bundle
8.10.5. Procedure 1648 To create an MLPPP bundle
8.10.6. Procedure 1649 To modify an MLPPP bundle
8.10.7. Procedure 1650 To configure an MLPPP bundle for multiclass service transmission
8.10.8. Procedure 1651 To configure an MLPPP bundle as a network interface on a
channelized ASAP MDA
9. 17 Port and channel object configuration
9.1. 17.1 Port and channel object configuration overview
9.2. 17.2 Working with port and channel objects
9.2.1. Digital diagnostics monitoring
9.2.2. Tagged and untagged VLAN ports
9.2.3. Connection termination points for services and interfaces
9.2.4. STS3 to STS192 clear channel
9.2.5. DS3 clear channel
9.2.6. DS0 channel groups
9.2.7. Ethernet ports
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 6/269
06.07.2017 Device management
9.2.8. PoE
9.2.9. Moving and copying SAPs between ports
9.2.10. SONET/SDH and TDM port encapsulation
9.2.11. SONET clear channel applications
9.2.12. TDM channelization and clear channel applications
9.2.13. ATM encapsulation
9.3. 17.3 SONET and SDH subchannel applications and structure
9.3.1. SONET DS3 payload
9.3.2. SONET VT1.5 and VT2 payloads
9.3.3. SONET subchannel syntax
9.3.4. Comparison of SONET and SDH hierarchies
9.3.5. SDH AU4 and AU3 subchannel applications
9.3.6. SDH TU3 payload
9.3.7. SDH E3 or DS3 payload
9.3.8. SDH TU11 and TU12 payloads
9.4. 17.4 Workflow to manage port objects
9.5. 17.5 Workflow to manage channel objects
9.6. 17.6 Port configuration procedures
9.6.1. Procedure 171 To configure Ethernet ports
9.6.2. Procedure 172 To change the port mode
9.6.3. Procedure 173 To migrate SAPs from access mode to hybrid mode
9.6.4. Procedure 174 To configure the 5620 SAM to retain nondefault port MTU values
9.6.5. Procedure 175 To copy or move L2 SAPs between ports
9.6.6. Procedure 176 To copy or move L2 access interface SAPs between services
9.6.7. Procedure 177 To move L3 SAPs within or between ports on the same NE
9.6.8. Procedure 178 To move L3 subscriber interface SAPs between ports on the same
NE
9.6.9. Procedure 179 To add a queue group to an Ethernet port
9.6.10. Procedure 1710 To configure SONET ports
9.6.11. Procedure 1711 To configure an HSMDA override
9.6.12. Procedure 1712 To configure TDM DS3 ports
9.6.13. Procedure 1713 To configure serial ports
9.6.14. Procedure 1714 To configure PW ports
9.6.15. Procedure 1715 To configure a 7210 SASM channelized TDM DS1 or E1 port
9.6.16. Procedure 1716 To assign QoS policies to a 7210 SAS Ethernet port
9.6.17. Procedure 1717 To create a 7210 SAS SHG
9.6.18. Procedure 1718 To configure a virtual Ethernet port on a 7705 SAR 2port ring
MDA
9.6.19. Procedure 1719 To configure PoE ports on a 7210 SAS
9.6.20. Procedure 1720 To configure PoE ports on a 7705 SAR
9.6.21. Procedure 1721 To configure GPS on a 7705 SAR
9.6.22. Procedure 1722 To configure a 7705 SAR ASAP channelized TDM port
9.6.23. Procedure 1723 To configure a 7710 SR channelized TDM DS1 or E1 port
9.6.24. Procedure 1724 To configure OmniSwitch Ethernet ports
9.6.25. Procedure 1725 To configure OmniSwitch PoE Ports
9.7. 17.7 Channel and framing link configuration procedures
9.7.1. Procedure 1726 To configure SONET clear channels
9.7.2. Procedure 1727 To perform a bulk channel creation on ports that support multiple
subchannels
9.7.3. Procedure 1728 To configure SONET subchannels
9.7.4. Procedure 1729 To configure SDH subchannels
9.7.5. Procedure 1730 To create VT15 (TU11) or VT2 (TU12) subchannels
9.7.6. Procedure 1731 To create TDM DS1 or E1 channels
9.7.7. Procedure 1732 To configure TDM DS1 or E1 channels
9.7.8. Procedure 1733 To create serial channels
9.7.9. Procedure 1734 To create TDM DS3 channels
9.7.10. Procedure 1735 To configure TDM DS3 channels
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 7/269
06.07.2017 Device management
9.7.11. Procedure 1736 To configure a DS3/E3 channel as a network interface on a
channelized ASAP MDA
9.7.12. Procedure 1737 To configure an L3 interface on a DS3/E3 channel on a
channelized ASAP MDA
9.7.13. Procedure 1738 To configure a PVC
9.7.14. Procedure 1739 To create an ILMI link
9.7.15. Procedure 1740 To configure an ILMI link
10. 18 Inventory management
10.1. 18.1 Inventory management overview
10.2. 18.2 Sample inventory management workflow
10.3. 18.3 Workflow to manage inventory
10.4. 18.4 Inventory management procedures
10.4.1. Procedure 181 To list and sort equipment information
10.4.2. Procedure 182 To save an inventory list
10.4.3. Procedure 183 To inventory the CLEI codes of NE objects
10.4.4. Procedure 184 To inventory the card software versions of one NE
10.4.5. Procedure 185 To inventory the port types of one NE
10.4.6. Procedure 186 To inventory the shelf data for one NE
10.4.7. Procedure 187 To inventory all cards
10.4.8. Procedure 188 To inventory all CCMs
10.4.9. Procedure 189 To inventory all fan trays
10.4.10. Procedure 1810 To inventory all flash memory units
10.4.11. Procedure 1811 To inventory all physical links
10.4.12. Procedure 1812 To inventory all ports
10.4.13. Procedure 1813 To inventory all power supply trays
10.4.14. Procedure 1814 To inventory all processors
10.4.15. Procedure 1815 To inventory all shelves
10.4.16. Procedure 1816 To inventory all management ports
10.4.17. Procedure 1817 To collect inventory data for NE SLA audits
11. 19 Card migration
11.1. 19.1 Card migration management overview
11.1.1. Restrictions
11.2. 19.2 Workflow to manage card migration
11.3. 19.3 Card migration management procedures
11.3.1. Procedure 191 To create a card migration event
11.3.2. Procedure 192 To execute a saved card migration event
12. 20 TCA
12.1. 20.1 TCA overview
12.1.1. TCA operation
12.1.2. TCA policy rules
12.1.3. TCA configuration example
12.2. 20.2 Workflow to configure TCA
12.3. 20.3 TCA management procedures
12.3.1. Procedure 201 To configure a custom profile TCA
12.3.2. Procedure 202 To configure a TCA policy
12.3.3. Procedure 203 To apply a TCA policy to objects using the object properties forms
13. 21 Bulk operations
13.1. 21.1 Bulk operations overview
13.2. 21.2 Workflow to manage bulk operations
13.3. 21.3 Bulk operations procedures
13.3.1. Procedure 211 To create a bulk change
13.3.2. Procedure 212 To modify a bulk change
13.3.3. Procedure 213 To execute a bulk change
13.3.4. Procedure 214 To view executed batch information
13.3.5. Procedure 215 To stop one or more bulk changes
14. 22 Autoprovision
14.1. 22.1 Autoprovision overview
14.2. 22.2 Workflow to configure network devices using autoprovision
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 8/269
06.07.2017 Device management
14.3. 22.3 Autoprovision procedures
14.3.1. Procedure 221 To configure a source template
14.3.2. Procedure 222 To configure a target template
14.3.3. Procedure 223 To apply a target template to an unprovisioned NE
Device management
9 Device support
10 Device commissioning and management
11 Device discovery
12 Device CLI sessions
13 Working with network objects
14 Device object configuration
15 Logical group object configuration
16 Shelf object configuration
17 Port and channel object configuration
18 Inventory management
19 Card migration
20 TCA
21 Bulk operations
22 Autoprovision
1. 9 — Device support
9.1 Device support overview
9.2 Sample workflow to configure and manage devices
9.3 1830 PSS support
9.4 1830 PSS OCS support
9.5 5780 DSC support
9.6 7210 SAS support
9.7 7450 ESS support
9.8 7705 SAR support
9.9 7710 SR support
9.10 7750 SR MG support
9.11 7750 SR support
9.12 7850 VSG/VSA support
9.13 7950 XRS support
9.14 9471 WMM support
9.15 9500 MPR and 9500 MPRe support
9.16 9966 MS SC Gateway support
9.17 eNodeB support
9.18 OmniSwitch support
9.19 GNE support
9.1 Device support overview
The 5620 SAM can manage the following AlcatelLucent devices:
1830 PSS 7850 VSG/VSA
1830 PSS OCS 7950 XRS
7210 SASD 9471 WMM
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 9/269
06.07.2017 Device management
7210 SASD ETR 9500 MPR
7210 SASE 9500 MPRe
7210 SASK 9966 MS SC Gateway
7210 SASK ETR eNodeB
7210 SASM OS 6250M
7210 SASM ETR OS 6250SME
7210 SASMxp OS 6400
7210 SASMxp ETR OS 6450
7210 SASR OS 6850
7210 SAST OS 6900
7210 SAST ETR OS 6855
7210 SASX OS 9600
7450 ESS OS 9700
7705 SAR OS 9700E
7710 SR OS 9800
7750 MG OS 9800E
7750 SRc4 OS 10K
7750 SR
7750 SRc12
7750 SR12E
The 5620 SAM also provides limited management support for generic NEs, which are typically nonAlcatelLucent
devices using SNMP.
For corenetwork devices such as the 7450 ESS, 7710 SR, and 7750 SR, the 5620 SAM supports the current
software release and the three immediately previous major releases. For example, a 5620 SAM, Release 13.0
system can manage a 7750 SR, Release 13.0, 12.0, 11.0, or 10.0. Older device releases are not supported.
For devices other than corenetwork devices, the 5620 SAM release support varies. See the 5620 SAM Network
Element Compatibility Guide for specific device support information.
The 5620 SAM GUI displays a device feature or function only if the device supports the feature or function. The 5620
SAM user documentation describes the major variations in support, including devicespecific procedures for specific
implementations, but does not describe the following minor GUI variations for different devices:
partial support for the parameter list on a form
partial support for the buttons and tabs on a form
Devicespecific release information
The following documents describe 5620 SAM support for devicespecific releases:
5620 SAM Network Element Compatibility Guide—lists the device releases and functions that the 5620 SAM
supports
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 10/269
06.07.2017 Device management
5620 SAM Parameter Guide—lists and describes the supported parameters; includes devicespecific
variations in parameter defaults and ranges
See the device user documentation for information about device functions, parameters, and CLI commands that are
outside the scope of the 5620 SAM documentation. Contact AlcatelLucent technical support for specific network or
facility considerations.
Caution When a device introduces a maintenance release, you must ensure that your 5620 SAM
software supports the new device release before you upgrade the device to the new release. You may
need to upgrade the 5620 SAM to support the new device release. See the 5620 SAM Network
Element Compatibility Guide for more information.
Devicespecific guides
The 5620 SAM User Guide describes the management of the majority of AlcatelLucent devices, however for some
devices, for example, optical, LTE, and small cell devices are described in other guides. If the information is
contained in the 5620 SAM User Guide, the sample workflow in this chapter describes the highlevel steps that are
required to configure and manage the device.
9.2 Sample workflow to configure and manage devices
The following is a generic workflow of the highlevel tasks that are typically used to configure and manage supported
devices using the 5620 SAM. This workflow is common to all 5620 SAMmanaged devices but not all tasks apply to
all device types. As appropriate, review the workflow associated with each task for detailed instructions.
Note 1 You can use an OSS client to configure many of the functions available on the 5620 SAM
GUI. See “Communication with the 5620 SAM server” in the 5620 SAM XML OSS Interface Developer
Guide for information.
Note 2 You can use 5620 SAM scripts and templates to configure managed devices. See the 5620
SAM Scripts and Templates Developer Guide for information.
Prerequisite tasks
1. Plan your 5620 SAM deployment for managing devices by determining the following:
the number of NEs the 5620 SAM is to manage, the redundancy requirements and the hardware
required for the 5620 SAM system
the management network latency and management network bandwidth requirements
the naming conventions for 5620 SAM objects that you create
See the 5620 SAM Planning Guide for the full list of deployment considerations.
2. Install the 5620 SAM software, as described in the 5620 SAM | 5650 CPAM Installation and Upgrade Guide.
3. Integrate the 5620 SAM with other AlcatelLucent products, such as the 5650 CPAM or another thirdparty
products as required; see the 5620 SAM Integration Guide.
4. Review the 5620 SAM Network Element Compatibility Guide for releasespecific information about the
compatibility of managed device features in 5620 SAM releases. Install the physical device as per the
appropriate devicespecific hardware user documentation.
Review GUI basics for managing devices
5. Familiarize yourself with 5620 SAM GUI operations for configuring and managing devices such as the
following:
navigating the GUI, performing searches, and customizing the 5620 SAM GUI user preferences; see
chapter 3.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 11/269
06.07.2017 Device management
creating custom workspaces to simplify navigation and operation; see chapter 4.
managing devices using the equipment navigation tree; see chapter 5.
managing equipment using topology maps; see chapter 6.
creating schedules to allow for the automatic execution of tasks at designated times; see chapter 7.
6. Launch the onproduct user documentation to access the 5620 SAM customer documentation and search
tools. Refer to the 5620 SAM Documentation Map for entry points into the 5620 SAM documentation suite
according to network type, functional area of interest, device type, or user roles.
Perform account and security tasks
7. Set up all required 5620 SAM user accounts and user groups with the required scope of command roles, span
of control permissions, and the ongoing monitoring and management of those accounts. See “5620 SAM user
security” in the 5620 SAM System Administrator Guide for more information.
8. Perform the required 5620 SAM and UNIX security management tasks for accessing and securing the
managed device. See “NE user and device security” and “TCP enhanced authentication” in the 5620 SAM
System Administrator Guide for more information.
Prepare network devices for 5620 SAM management
9. Commission AlcatelLucent devices for 5620 SAM management and ensure all nonAlcatelLucent devices
have a GNE profile. Configure how and when the 5620 SAM polls the devices for MIB changes; see chapter
10.
10. Create a mediation security policy and discovery rule to define the criteria required to add devices to the
managed network, and optionally configure SSH2 security for CLI sessions; see chapter 11.
11. Use a Telnet or SSH CLI from the 5620 SAM for device access; see chapter 12.
12. Customize the default systemwide behavior of 5620 SAM settings as required to meet your specific
operational requirements for managing devices such as the 5620 SAM software and license system
components, network functions, systemwide alarm settings, and system preferences. See “5620 SAM
component configuration” in the 5620 SAM System Administrator Guide for the full list of settings that can be
customized.
Configure and manage the discovered device
13. Configure and manage equipment navigation tree objects including:
general network objects; see chapter 13
device objects; see chapter 14
logical group objects; see chapter 15
shelf, card, and daughter card objects; see chapter 16
port and channel objects; see chapter 17
14. Perform additional device management functions, as required such as the following:
equipment inventories of managed devices; see chapter 18
card migrations; see chapter 19
configure thresholdcrossing alarms; see chapter 20
bulk configuration changes; see chapter 21
automatic provisioning; see chapter 22
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 12/269
06.07.2017 Device management
Manage the network functions
15. Configure NE routing and forwarding on NEs; see chapter 28. As required, configure specific routing and
forwarding functions and services such as:
NE protocols; see chapter 29
OpenFlow; see chapter 30
ISNAT groups; see chapter 31
MPLS and LSPs; see chapter 32
MPLSTP; see chapter 33
GMPLSUNI; see chapter 34
service tunnels to carry service traffic; see chapter 35
IPsec sessions; see chapter 36
ISAVideo groups and members, see chapter 37
16. Configure network redundancy, protection, and offloading as required to ensure network availability in case of
a network device or path failure using functions such as:
VRRP; see chapter 39
APS; see chapter 40
WiFi offloading; see chapter 41
MC peer groups; see chapter 42
MC IPsec; see chapter 43
MC endpoint groups; see chapter 44
MC LAG groups; see chapter 45
MC synchronization groups; see chapter 46
MC ring groups; see chapter 47
Create policies to manage devices
17. Depending on your service delivery model, create, distribute, and assign the appropriate service or routing
policies that define the conditions for managing network devices using the 5620 SAM; see chapter 48 for
general information about 5620 SAM policy management. See chapters 49 to 67 for specific policy information
and the associated workflows to configure the policy.
Create services over devices
18. Familiarize yourself with 5620 SAM service management and QoS concepts prior to configuring services over
the devices; see chapter 68. Configure the following adjunct service delivery methods to support the creation
of network services as required:
shared queue groups to allow SAP or IP interface forwarding classes to be redirected; see chapter 69.
virtual ports to support clustering and enforce the aggregate rate of each destination BSAN; see chapter
70.
create and manage customers and the services they subscribe to; see chapter 71.
tunnel administrative groups to enable services to use a PW template; see chapter 86.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 13/269
06.07.2017 Device management
19. Configure the following network services as required:
services for residential subscribers; see chapter 72.
VLAN services; see chapter 73.
VLL services; see chapter 74.
VPLS; see chapter 75.
IES; see chapter 76.
VPRN services; see chapter 77.
SPB services; see chapter 78.
PW routing and dynamic MSPW services; see chapters 79 and 81.
Composite services; see chapters 83.
Dynamic services; see chapter 84.
Monitor, maintain, and troubleshoot devices
20. Configure 5620 SAM alarm policies, and monitor incoming alarms to check the type and characteristics of the
alarms, and to resolve the network problems or physical equipment failures identified by the alarms; see
chapter 38.
21. Perform the following service assurance functions as required, to ensure that services offered over network
devices meet the predefined service quality level expected by customers:
use the 5620 SAM Service Test Manager to group OAM diagnostic tests into suites of manual and
automaticallygenerated tests; see chapter 87.
use OAM diagnostic tools to troubleshoot network problems and for SLA verification; see chapter 88.
configure Ethernet CFM to detect, isolate, and report connectivity faults in Ethernet networks; see
chapter 89.
create mirror services to troubleshoot customer traffic issues or for use with Lawful Intercept; see
chapters 91 and 92.
test and report network delay and loss using CFM messaging in Layer 2 networks; see chapter 90.
perform ondemand verifications of the configuration of services and physical links using an RCA audit;
see chapter 93.
create a copy of the SAP configuration of an enduser service to emulate the bandwidth, throughput,
and QoS requirements of a service; see chapter 94.
configure Application Assurance to provide deeppacket inspection and applicationbased subscriber
traffic management; see chapter 85.
22. Collect 5620 SAM and NE statistics to monitor network and service performance, compile equipment usage
and billing data, and ensure SLA compliance; see the 5620 SAM Statistics Management Guide.
23. Perform device maintenance functions, as required, for example:
configuration backups and restores; see chapter 24
checkpoint file creation and configuration rollbacks; see chapter 25
deployment management; see chapter 26
software upgrades; see chapter 27
configure the OLC state of a device object to specify whether the object is in maintenance or inservice
mode to suppress or display object alarms
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 14/269
06.07.2017 Device management
24. Identify and resolve performance issues in a 5620 SAMmanaged network or on a 5620 SAM system as
required; see the 5620 SAM Troubleshooting Guide.
9.3 1830 PSS support
The 1830 Photonic Service Switch product family provides CWDM, DWDM, and OTN capabilities. Photonic
networking increases flexibility and operational automation. The 5620 SAM supports the following 1830 PSS devices:
1830 PSS1 edge aggregation device; the supported variants are the following:
1830 PSS1 AHP amplifier
1830 PSS1 GBE edge devices
1830 PSS1 MD4H edge device
1830 PSS4 edge device
1830 PSS16 end office device
1830 PSS32 central office device
The following documents describe 5620 SAM management and configuration of the 1830 PSS:
5620 SAM User Guide—Describes management of optical devices which does not differ from other network
elements
5620 SAM Optical User Guide—Describes 1830 PSS discovery, configuration, and management using the
5620 SAM
5620 SAM Optical Parameter Reference—Provides a list of all optical device parameters that the 5620 SAM
supports
9.4 1830 PSS OCS support
The OCS component of the 1830 Photonic Service Switch provides OTH switching and control functions using
matrix cards. The 5620 SAM supports the 1830 PSS OCS product family of devices which includes:
1830 PSS64
1830 PSS36
See the current 5620 SAM Network Element Compatibility Guide for information about the 1830 PSS support in a
5620 SAM release.
The following documents describe 5620 SAM management and configuration of the 1830 PSS:
5620 SAM User Guide—Describes management of optical devices which does not differ from other network
elements
5620 SAM Optical User Guide—Describes 1830 PSS discovery, configuration, and management using the
5620 SAM
5620 SAM Optical Parameter Reference—Provides a list of all optical device parameters that the 5620 SAM
supports
9.5 5780 DSC support
The 5620 SAM allows you to view the properties for the equipment, instance, Diameter proxy agent, and policy
charging rules for the 5780 DSC. The 5780 DSC is represented in the 5620 SAM equipment navigation tree. The
instance, Diameter proxy agent, and policy charging rule properties are viewable using the Manage Mobile Core
DSC Instances 5620 SAM main menu option.
The 5620 SAM LTE EPC User Guide describes 5780 DSC discovery and management using the 5620 SAM.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 15/269
06.07.2017 Device management
9.6 7210 SAS support
This section describes the 5620 SAM support for AlcatelLucent 7210 SAS devices.
7210 SASD support
The 7210 SASD is an intelligent Ethernet edgedemarcation device that extends enhanced Carrier Ethernet VPN
service delivery to the CE. The license for a 7210 SASD is based on the chassis type. The 5620 SAM supports the
following chassis types:
7210 SASD 6F 4T
7210 SASD 6F 4T ETR
Note The 5620 SAM supports only access mode for 7210 SASD 6F 4T ETR ports.
7210 SASE support
The 7210 SASE is a Carrier Ethernet CE device that is typically owned and managed by a customer. Using software
based on the 7750 SR OS and managed by the 5620 SAM, the 7210 SASE extends Carrier Ethernet VPN services
to the CE. The 7210 SASE can also be deployed as an aggregation device for smaller sites.
7210 SASE daughter cards
The 7210 SASE supports an integrated 2 × 12Gig IOM card on a single chassis. The equipment navigation tree
displays a card slot with one daughter card that contains 12 × 100/1000 Ethernet SFP ports and 12 × 10/100/1000
Ethernet ports.
7210 SASK support
The 7210 SASK is an intelligent Gigabit Ethernet switch typically used for Ethernetbased L2 services and Ethernet
mobile backhaul applications. The switch provides aggregation and demarcation for VLL and VPLS services managed
to the customer edge. The 7210 SASK supports up to 128 services, and provides enhanced hierarchical QoS on
ingress and egress.
The 7210 SASK supports a 5port IOM card provisioned with the following port types:
2 × 1Gig SFP
2 × 10/100/1000BASETX
1 × combination port (SFP or RJ45)
The 5620 SAM supports the following chassis variants:
7210 SASK 2F 2T 1C
7210 SASK 2F 2T 1C ETR
The 7210 SASK (nonETR variant) is not equipped with a fan.
7210 SASM support
The 7210 SASM is a CE device that provides MPLSenabled metropolitan and WAN Carrier Ethernet service
delivery, Ethernetbased mobile backhaul, and residential service access. In access uplink mode, the 7210 SASM
provides Ethernet aggregation and demarcation for services managed to the customer edge.
The 5620 SAM supports two chassis modes for the 7210 SASM:
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 16/269
06.07.2017 Device management
Access uplink: the device provides network service transport using Ethernet QinQ encapsulation. Ports are
configured in access or L2 uplink mode.
Network: the device provides network service transport using IP/MPLS encapsulation. Ports are configured in
access, network, or hybrid mode.
The chassis mode is changed using a CLI to modify the device BOF. A reboot of the device is required for the
change to take effect. When you change the chassis mode of a 7210 SASM, you must unmanage and remanage
the NE. The 5620 SAM displays the chassis mode as the State parameter, in the Uplink Mode panel on the General
tab of the shelf properties form for the device.
See the NE documentation for more information.
The 5620 SAM supports the following 7210 SASM chassis variants:
7210 SASM 24F
7210 SASM 24F 2XFP
7210 SASM 24F 2XFP ETR
7210 SASMxp support
The 7210 SASMxp is an IP/MPLSenabled 1GigE and 10GigE access and aggregation device, typically used for
customer edge and service aggregation. The 7210 SASMxp has 28 ports:
22 × 1Gig SFP
4 × 10Gig SFP+
2 × Combo (SFP or RJ45)
The 5620 SAM supports the following 7210 SASMxp chassis variants:
7210 SASMxp 22F 2C 4SFP+
7210 SASMxp 22F 2C 4SFP+ ETR
Note The 7210 SASMxp is not a variant of the 7210 SASM. The 7210 SASMxp does not
necessarily share all the features of the 7210 SASM. In the 5620 SAM guides, stated support and
functionality for the 7210 SASM does not necessarily include the 7210 SASMxp.
The 7210 SASMxp ETR supports PoE connections on ports 23 and 24. See Procedure 1719 for more information.
7210 SASR support
The 7210 SASR is an MPLSenabled Ethernet switch suitable for aggregating 1Gig and 10Gig rings in access
Ethernet networks. The 7210 SASR supports 60 Gig redundant switching capacity and is capable of MPLS and
MPLSTP service transport.
This three rackunit device has six IMM card slots and two CPM/SF slots. Each IMM has 10Gig fullduplex/20Gig
halfduplex switching capacity with a single CPM/SF.
The 5620 SAM supports the following firstgeneration IMM cards on the 7210 SASR:
2 × 10Gig XFP
10 × 1Gig SFP + 1 × 10Gig XFP
10 × 1Gig SFP
The 5620 SAM supports the following secondgeneration IMM cards on the 7210 SASR:
10 × 1Gig SFP + 1 × 10Gig SFP+
2 × 10Gig SFP+
4 × 10Gig SFP+
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 17/269
06.07.2017 Device management
22 CSFP (11 × 1Gig SFP or 22 × 1Gig CSFP)
Any of the card types can be installed in any of the six IMM card slots, with the exception that secondgeneration
IMM cards cannot be mixed with firstgeneration IMM cards on the same chassis.
For the 22 CSFP card, the 5620 SAM displays 22 ports on the navigation tree, even when SFP transceivers are
used.
The 7210 SASR supports access, network, or hybrid port modes. For 1Gig ports the port speed is variable.
7210 SAST support
The 7210 SAST is an Ethernet access device that provides MPLSenabled metropolitan and WAN Carrier Ethernet
service delivery, Ethernetbased mobile backhaul, and residential service access. In access uplink mode, the 7210
SAST provides Ethernet aggregation and demarcation for services managed to the customer edge.
The 5620 SAM supports two chassis modes for the 7210 SAST:
Access uplink: the device provides network service transport using Ethernet QinQ encapsulation. Ports are
configured in access or L2 uplink mode.
Network: the device provides network service transport using IP/MPLS encapsulation. Ports are configured in
access, network, or hybrid mode.
The chassis mode is changed using a CLI to modify the device BOF. A reboot of the device is required for the
change to take effect. When you change the chassis mode of a 7210 SAST, you must unmanage and remanage
the NE. The 5620 SAM displays the chassis mode as the State parameter, in the Uplink Mode panel on the General
tab of the shelf properties form for the device.
See the NE documentation for more information.
The 7210 SAST is equipped with the following ports:
12 × 10/100/1000 Ethernet SFP
10 × 10/100/1000BaseTX copper
4 × 10GigE XFP
The 5620 SAM supports the following chassis variants:
7210 SAST 12F 10T 4XFP
7210 SAST 12F 10T 4XFP ETR
The 7210 SAST ETR supports PoE connections on ports 19, 20, 21, and 22. See Procedure 1719 for more
information.
7210 SASX support
The 7210 SASX is an MPLSenabled Ethernet aggregation device for small and mediumsized networks that
provides business, mobile backhaul, and residential services. The 7210 SASX is similar to the 7210 SASM, but has
10Gb/s uplink ports, enhanced traffic management, greater scalability, and hierarchical QoS functions.
The 5620 SAM supports the 7210 SASX 24F 2XFP.
System resource profile
The 5620 SAM supports system resource allocation on 7210 SAS devices using the system resource profile. You
can configure system resources to suit your network requirements by assigning more resources to functions that are
used extensively, and fewer resources to functions that are used less. Unused functions can be disabled, and their
resources made available for other functions. The functional areas that are configurable vary depending on the
chassis type; see Table 91.
Table 91 System resource profile
Function Applicable NE chassis
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 18/269
06.07.2017 Device management
G8032 fast flood 7210 SASM (in network mode), 7210 SASMxp, 7210 SASR
SAP Aggregate 7210 SASD, 7210 SASM, 7210 SASMxp, 7210 SASR, 7210 SAST, 7210
Meter SASX
SAP ingress 7210 SASD, 7210 SASE, 7210 SASK, 7210 SASM, 7210 SASMxp, 7210
internal ACL SASR, 7210 SAST, 7210 SASX
SAP egress 7210 SASD, 7210 SASK, 7210 SASM, 7210 SASMxp, 7210 SASR, 7210
internal ACL SAST, 7210 SASX
SAP ingress QoS 7210 SASD, 7210 SASE, 7210 SASK, 7210 SASM, 7210 SASMxp, 7210
SASR, 7210 SAST, 7210 SASX
QoS Network 7210 SASR
Ingress
DHCP snooping 7210 SASE
Queues 7210 SASX
Ethernet CFM 7210 SASD, 7210 SASM, 7210 SASMxp, 7210 SASR, 7210 SASX
Router 7210 SASD, 7210 SASM, 7210 SASMxp, 7210 SASR, 7210 SAST, 7210
SASX
QoS 7210 SASR
Note Configuration changes for G8032 fast flood, SAP Aggregate Meter, Queues, Router, and QoS
are boottime enabled, and take effect during the next NE reboot. Changes to all other functions are
runtime enabled and take effect immediately, when sufficient resources are available.
System resources are allocated in units called chunks. The number of chunks and the chunk size vary by device
chassis.
Resources are allocated by assigning a value from the applicable range. A value of zero disables the function. The
sum of resources allocated must not exceed the total available resources for the system. If you assign more than the
allocated number of chunks, functions are disabled.
For SAP ACL and SAP QoS functions, configuring system resources is accomplished in two steps. First, divide
overall system resources among the main functional areas: SAP ingress internal ACL, SAP egress internal ACL, and
SAP ingress QoS. Second, allocate the resources specified for each functional area to the criteria within that
function, such as MAC, IPv4, and 64 or 128bit IPv4/v6. The total number of chunks assigned to the criteria must not
exceed the number of chunks allocated to the function. When you specify a value of MAX, the system allocates
resources as required on a firstcome, firstserved basis, up to the available limit.
For 7210 SAS chassis types other than the 7210 SASR, all system resource profile allocations are configured
globally on the NE properties form; see Procedure 1433.
For the 7210 SASR, some resource allocations are configured globally on the NE properties form, and some are
configured using system resource profile policies assigned to card slots on the device; see Procedures 1434 and 16
36.
See the 7210 SAS documentation for more information about system resource allocation.
9.7 7450 ESS support
The AlcatelLucent 7450 Ethernet Service Switch supports serviceaware Ethernet aggregation across IP/MPLS
based networks, providing VPLS, VLL and advanced IP services. The 7450 ESS supports a wide range of interfaces.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 19/269
06.07.2017 Device management
A Network Domain feature allows users to determine which network ports are eligible to transport traffic of individual
SDPs. This information is used for the SAPingress queue allocation algorithm applied to VPLS SAPs. See chapter
28 for more information.
The 5620 SAM provides network management functions for the 7450 ESS.
The 7450 ESS OAM toolkit includes ITUTY.1731 with Synthetic Loss Measurement (SLM), IEEE 802.1ag, IEEE
802.3ah, Ethernet local management interface (ELMI), VPLS OAM and service mirroring. This toolkit is also
integrated into the 5620 SAM.
Automatic provisioning for CPM5 SFMs
The 5620 SAM automatically provisions and configures the integrated SFMs of CPM5s that feature builtin modules.
The automated provisioning occurs during node discovery.
9.8 7705 SAR support
The 7705 SAR is an IP/MPLS aggregation and mobile backhaul router for the mobile RAN. Located at cell sites, the
7705 SAR uses PW over MPLS to aggregate mobile 2G and 3G traffic that it backhauls to the core network. The
7705 SAR supports ATM, TDM, and Ethernet.
7705 SAR MWA support
A packet microwave card is required to support MWA. The first four ports of the card are microwave aware. An MW
link must be configured to enable MWA. MW link support includes 1+0 and 1+1 HSB protection. When configuring
1+1 HSB, each of the two radios is assigned a role of main radio or spare radio. By default, the main radio assumes
the active status and the spare radio assumes the standby status. For 1+0 protection, MPTHC, MPTHCv2, MPT
HLC, MPTHQAM, and MPTMC are supported. For 1+1 HSB protection, MPTHC, MPTHCv2, MPTHLC, and
MPTHQAM are supported.
1+1 HSB protection is displayed in the 5620 SAM physical topology map. The protection state is shown on the links,
and 1+1 links are grouped in a common link group. The expansion of radio links on the physical map displays eight
links. See section 6.2 for more information about the 5620 SAM physical topology map.
Note 1 If the 9500 MPRe (version 4.2, standalone) is discovered before the 7705 SAR (single NE
with 1+0 protection), the radio link is not shown on the topology map. Only after discovering the 7705
SAR will the radio link be shown on the topology map between the 7705 SAR and the 9500 MPRe.
Note 2 1+1 HSB protection is only supported between two 7705 SAR NEs.
The following protection types are supported:
Radio Protection Switching (RPS)
RPS is always supported in 1+1 radio configurations (HSB). RPS is implemented directly on a pair of MPTs.
Transmission Protection Switching (TPS)
TPS is always supported in 1+1 HSB radio configurations.
Equipment Protection Switching (EPS)
EPS protects the MPT and cables connecting the MPT to the IDU. RPS protection always assumes the MPT
EPS.
See Procedure 1615 for more information about configuring an MW link. See Procedure 1616 for more information
about configuring an MW link member.
7705 SAR NEtO support
The 5620 SAM supports an integrated MCT from the port or NE level on the 7705 SAR8 and 7705 SAR18. The
MCT is distributed with a NEtO client in the 5620 SAM. The configuration of radio parameters is through the MCT.
See Procedure 1439 for more information about starting the MCT from the NE level.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 20/269
06.07.2017 Device management
7705 SAR SCADA support
The 5620 SAM supports SCADA on the 7705 SAR8 and 7705 SAR18, Release 6.1 R1 or later. SCADA is an
industrial data management system that monitors and controls IEDs. See Section 16.2 for more information about
SCADA. See Procedure 1614 for more information about configuring SCADA on the 7705 SAR.
7705 SAR auxiliary alarm daughter cards
The 7705 SAR supports an auxiliary alarm daughter card. This is a unique card that interfaces with realtime
systems. The following inputs and outputs are available:
24 digital inputs that can connect to dry contacts of security sensors, HVAC systems, and telecom systems
Two analog inputs for monitoring battery voltage; each supports a range of 0 to 75V and has configurable
thresholds for alarms and events on each port
Eight drycontact relay outputs that interface to external audible, visual, or telecom equipment using NO or NC
contact pins
The inputs and outputs are listed on the Ports tab of the daughter card slot properties form, in the same manner as
ports on a dataplane daughter card. Each input or output has configurable parameters. The name specified for each
input or output must be unique within the device.
7705 SAR 6port E&M daughter cards
The 7705 SAR supports a sixport E&M daughter card. The configuration of ports and channels on this daughter card
is similar to the 16port DS1/E1 ASAP daughter card. You create a channel under each port, and a channel group
under each channel.
The following configuration restrictions and limitations apply to ports and channels on the six port E&M daughter card:
A port can have only one channel.
A channel can have only one channel group.
A channel group must be in Access mode and use CEM encapsulation.
A channel group MTU is not configurable.
Only CESoPSN Cpipe SAPs can be created on the daughter card.
7705 SAR 12port SDI card
There are two versions of the 12port SDI card. The 12port SDIv2 card is identical to the SDIv1 card. Both cards are
supported on the 7705 SAR8, 7705 SAR8v2, and 7705 SAR18.
The SDI card includes four connectors, each of which supports three ports. Each port in a threeport connector must
be configured to work on the same interface type. The ports operate in access mode and can be configured to work
with the following interfaces:
RS232
V.35
X.21
RS232 interfaces support CEM encapsulation.
V.35 and X.21 interfaces support FR, CEM, HDLC, cHDLC, and IPCP encapsulation.
7705 SAR ISC
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 21/269
06.07.2017 Device management
The 7705 SAR8 and 7705 SAR18 support an ISC that is equipped with a large FPGA and a Winpath network
processor. The FPGA supports multiple applications on the same card by using separate images while providing the
ability to perform IP/MPLS functionality such as pseudowire termination.
The ISC only supports one application running per card at a time. Multiple ISCs can be supported on a 7705 SAR8
or 7705 SAR18, independent of application. At least one networking card is required to provide access to the ISCs.
Network or access mode configuration is not applicable on the ISC; however, the card provides access capabilities.
An ISC is required to configure SCADA on the 7705 SAR8 and 7705 SAR18. For more information about SCADA,
see section 16.2.
Note Only SCADA MDDB is supported on the ISC on the 7705 SAR8 and 7705 SAR18, Release
6.1 R1.
7705 SAR Power Injector card
The 7705 SAR8 and 7705 SAR18 support a Power Injector card to deliver power and data to an MPT radio. Up to
four Power Injector cards can be installed on the 7705 SAR8, and up to eight Power Injector cards can be installed
on the 7705 SAR18.
7705 SAR Optical Add/Drop Mux cards
The 7705 SAR8 and 7705 SAR18 support an Optical Add/Drop Mux (OADM) card in 1, 2, 4, and 8colour variants.
These cards increase bandwidth in a fiber network.
7705 SAR CSMv2 card
The 7705 SAR8 supports a CSMv2 card. All of the 7705 SAR adapter cards are supported with the CSMv2. The 16p
ASAPv1 does not support IP interfaces with the CSMv2. The CSMv2 card is similar in function to the CSMv1 card,
however, the CSMv2 supports more deep channelized MDAs.
Note A router cannot have a mix of CSMv1 and CSMv2 cards. To convert a router with CSMv1
hardware to CSMv2 hardware, the appropriate configuration files must be transferred to the new
CSMv2.
7705 SAR 2 × 10Gig Bridged Ethernet XFP + 1 × 2.5G Virtual Ethernet card
The 2 × 10Gig Bridged Ethernet XFP + 1 × 2.5G Virtual Ethernet card connects to and from access rings carrying a
high concentration of traffic. The 7705 SAR8 supports up to 6 cards and the 7705 SAR18 supports up to 12 cards.
A single card can be installed on the 7705 SAR8 and 7705 SAR18.
The 2 × 10Gig Bridged Ethernet XFP + 1 × 2.5G Virtual Ethernet card is also supported on the 7705 SARM ASAP
and 7705 SARM with fan variants.
A number of 7705 SAR nodes in a ring typically aggregate traffic from customer sites, map the traffic to a service,
and connect to an SR node. The SR node acts as a gateway point out of the ring. A 10GigE ring allows higher
bandwidth services and aggregation on a per 7705 SAR basis.
In a deployment of a 2 × 10Gig Bridged Ethernet XFP + 1 × 2.5G Virtual Ethernet card, each 7705 SAR node in the
ring is connected to the east and west side of the rings over two different 10GigE ports. If 10GigE is the main uplink,
two cards per 7705 SAR8 are required for redundancy. With two cards per 7705 SAR8 node, east and west links of
the ring can be terminated on two different cards, reducing the impact of potential hardware failure. At initialization,
the MAC address of the virtual port is programmed automatically. The card can operate in either LAN or WAN mode.
7705 SAR 6port FXS Adapter card
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 22/269
06.07.2017 Device management
The 7705 SAR8 and 7705 SAR18 support a 6port FXS Adapter card that transports a large number of voice circuits
from one 7705 SAR location to another 7705 SAR location, connected to a PBX. The card can also be configured for
a PLAR application, which is typically used outside of a PBX network.
For a PBX application, the signal is terminated on an FXO interface at a 7705 SAR hub location that is connected to
a PBX. The FXO interface can be either on an 8port FXO Adapter card or 8port Voice & Teleprotection card that is
installed in a 7705 SAR8 or 7705 SAR18 chassis at the 7705 SAR8 hub location. For a PLAR application, the
signal is terminated on an FXS interface on either another 6port FXS Adapter card or an 8port Voice & Tele
protection card that is installed in a 7705 SAR8 or 7705 SAR18 chassis.
The 6port FXS Adapter card has six FXS ports. Each port provides a shortreach, onpremises analog interface to an
analog telephone set.
For standard TDM, the network interface can be a T1/E1 or OC3/STM1 channelized interface. For MPLS, an
Ethernet, T1/E1, OC3/STM1 channelized MLPPP, or OC3/STM1 clear channel interface can be used.
The 6port FXS Adapter card can be configured in access mode only.
7705 SAR 8port FXO Adapter card
The 7705 SAR8 and 7705 SAR18 support an 8port FXO Adapter card providing multiple FXO analog interfaces for
connection to a PBX. The FXO analog interfaces can be connected over the MPLS network via a TDM pseudo wire
(Cpipe) to an FXS interface on an 8port Voice and Teleprotection card. The remote end can also be an FXS interface
in a TDM multiplexer connected to the 7705 SAR by a T1/E1 interface. Each FXO interface separates the analog
signal into two streams, one stream for voice and another for control signaling.
7705 SAR 10port 1GigE/1port 10GigE XAdapter card
There are two versions of the 10port 1GigE/1port 10GigE XAdapter card. The CLI identifier for version 1 is x
10GigE and for version 2, the CLI identifier is x10GigEv2. Both versions are identical except that version 2 is
equipped with a hardwarebased encryption engine that supports features such as IPsec.
The 10port 1GigE/1port/10GigE XAdapter card can be configured for ten 1Gigabit ports or one 10Gigabit port.
When configured for a one 10Gigabit port, the card can operate in either LAN or WAN mode. The card is supported
on the 7705 SAR18.
7705 SAR 8port GigE SFP card (48/+24 V dc)
There are three versions of the 8port Gigabit Ethernet Adapter card. Version 1 and 2 are identical except that version
2 has more memory to support larger tables, such as FIBs and ACLs. Version 2 supports the full IPv6 subnet range
for IPv6 static routes and interface IP addresses. Version 3 is identical to version 2 except that it is equipped with a
hardwarebased encryption engine that supports features such as IPsec. All versions are supported on the 7705
SAR8 and the 7705 SAR18.
4 × 10/100/1000 1Gig SFP + 1 × 10Gig SFP + 1 × 10Gig XFP card
The 7705 SAR8v2, CSMv2, and 7705 SAR18 support a 4 × 10/100/1000 1Gig SFP + 1 × 10Gig SFP + 1 × 10Gig
XFP card, which can operate in either WAN or LAN mode. Only ports 5 and 6 support WAN or LAN mode. Ports 1 to
4 are 1Gig speed and ports 5 and 6 are 10Gig speed.
The card is pluggable only in slots 1 and 2 and is autoprovisioned. IP/MPLS is supported on the 10GigE ports.
The 4 × 10/100/1000 1Gig SFP + 1 × 10Gig SFP + 1 × 10Gig XFP card can only be configured in full duplex mode.
7705 SAR GPS receiver module
The 7705 SARH and 7705 SARWx support a GPS receiver that synchronizes data from GPS satellites, using
GNSS signals. The GPS data provides frequency and time of day, independent of the 5620 SAM network. On the
7705 SARH, the GPS receiver is pluggable, but on the 7705 SARWx, the GPS receiver is integrated.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 23/269
06.07.2017 Device management
When the GPS receiver is operational, it provides information about receiver status and state, signal and quality, and
satellite data. A 7705 SAR equipped with an operational GPS receiver provides information about the antenna’s
location with longitude, latitude, and altitude, and the GPS time in UTC.
The following GPS cards and modules are supported:
7705 SARH GPS receiver module
7705 SARWx 4 GigE 4port xDSL GPS Rx
7705 SARWx 5 GigE GPS Rx
7705 SARWx 5 GigE PoE+ GPS Rx
7705 SAR Packet Microwave card
The 7705 SAR8 and 7705 SAR18 support the Packet Microwave card, 4 × MWA Gig Ethernet (2 TX, 2 SFP) + 4 ×
Gig Ethernet SFP. The 7705 SAR8 supports up to 6 of these cards and the 7705 SAR18 supports up to 12 cards.
The first four ports of the Packet Microwave card are microwave ports and can be linked to a 9500 MPRe device.
7705 SAR Voice & TeleProtection MDA
The 7705 SAR8 and 7705 SAR18 support the Voice & TeleProtection MDA. The 7705 SAR8 supports up to 6
cards and the 7705 SAR18 supports up to 12 cards. Ports 1 and 2 support C37.94 interfaces, ports 3 and 4 support
G.703 Codirectional interfaces, ports 5 and 6 support FXO interfaces, and ports 7 and 8 support FXS interfaces.
7705 SARA
The 7705 SARA is equipped with integrated twelveport Ethernet MDA daughter cards. Depending on the variant, the
7705 SARA can support the configuration of eight Gig Ethernet, four Fast Ethernet, and eight T1/E1 ports. The two
7705 SARA daughter card variants are:
integrated 12port Ethernet, 8port T1/E1, 48 V dc MDA
integrated 12port Ethernet, 48 V dc MDA
The 7705 SARA T1/E1 supports IPCP encapsulation on card 2 ports, on the i8 × channelized DS1/E1 ASAP,
Release 7.0 R1 or later.
7705 SARF
The 7705 SARF integrates eightport Ethernet v3 and 16port DS1/E1 v2 ASAP MDA functions in one chassis.
When the 5620 SAM discovers a 7705 SARF, the integrated MDAs are automatically configured and displayed in the
equipment tree.
7705 SARH
The 7705 SARH is a hardened router and is based on the 7705 SAR8, 7705 SAR18, 7705 SARF, and 7705 SAR
M functionality. The 7705 SARH variants are:
7705 SARH high voltage shelf (88264V AC/DC)
7705 SARH low voltage shelf (–48/–60 and +24 VDC)
The 7705 SARH provides firewall functions and applies a firewall to an L3 network, management, or CPM interface.
The 7705 SARH firewall is a stateful firewall that provides a high level of security. Stateful operation is a key feature
in preventing DoS attacks from reaching the TCP/IP stacks of applications. The 7705 SARH uses a zonebased
virtual firewall design.
The firewall procedures in chapter 66 are only applicable to the 7705 SARH, Release 5.0.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 24/269
06.07.2017 Device management
The 5620 SAM allows you to configure the MDA mode of some MDA types on the 7705 SARH. There are two types
of MDAs:
Compact MDAs
Compact MDAs are integrated in slot 1 and have 8 Ethernet ports. The ports are configurable in network or
access mode.
ports 1 and 2 are Gigabit Ethernet ports
ports 3 and 4 are combo ports
ports 5, 6, 7, and 8 are PoE port types
Combo MDAs
Combo MDAs are modular and configurable, used in slot 2 and slot 3.
ports 1 and 2 are serial ports
ports 3 and 4 are TDM ports
The 7705 SARH supports the 4 × 10/100 Ethernet module card in slots 2 and 3. The module card supports four fast
Ethernet ports in access or network mode. The ports can be bound to a network interface, all routing protocols, and a
VPRN, IES and VLL service.
The 7705 SARH supports power supply tray objects, which are automatically provisioned.
7705 SARHc
The 7705 SARHc is equipped with six Ethernet ports:
two SFP Gigabit Ethernet ports
two RJ45 10/100/1000 Ethernet ports
two PoEcapable RJ45 10/100/1000 Ethernet ports
The 7705 SARHc is equipped with a single internal power supply that operates at +/–20 V dc to 75 V dc. When the
7705 SARHc is used for highvoltage applications, an external high voltage power supply is available.
The 7705 SARHc supports power supply tray objects, which are automatically provisioned.
7705 SARM
The 7705 SARM variants are equipped with an integrated 7port Ethernet card. Depending on the variant, a 7705
SARM may have an integrated 16port channelized DS1/E1 ASAP card or a module slot. The 7705 SARM variants
are:
fancooled chassis with integrated 7port Ethernet card, integrated 16port channelized DS1/E1 ASAP card,
and module slot
fancooled chassis with integrated 7port Ethernet card and module slot
passively cooled chassis with integrated 7port Ethernet card and integrated 16port channelized DS1/E1
ASAP card
passively cooled chassis with integrated 7port Ethernet card
The following module cards can be inserted in the module slot:
GPON module
DSL module
DCM
one Color Optical Add/Drop Mux module (OADM)
6 port Ethernet module
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 25/269
06.07.2017 Device management
The DSL module includes a port with eight xDSL lines. The DCM includes one port with four SHDSL lines and one
port with two xDSL lines. Except for 802.1x, 802.1ab LLDP, line loopbacks, and LAGs, all services and limitations
that apply to Ethernet ports also apply to DCM and DSL modules.
The 6 port Ethernet module supports the following three interfaces:
2 × 100/1000 Mbps ports
2 × 100/1000 Mbps combo ports (2×SFP or 2×Cu RJ.5)
2 × 1000 Mbps (PoE/PoE+) ports
7705 SARW
The 7705 SARW is equipped with an integrated daughter card that supports five data plane Ethernet ports: three
SFP ports and two RJ45 ports. The Ethernet ports are classified as permanent connections with primary surge
protection. Depending on the variant of the card, the two RJ45 ports will or will not support PoE. When the card is
required to support NLOS or LOS microwave radio powered by PoE, the card needs RJ45 ports with PoE capability.
When PoE is not required, a nonPoE card variant is available.
7705 SARWx
The 7705 SARWx transports all types of traffic over a packetswitched network from a mobile cell site to a higher
point of presence or to a mobile telephone switching office.
The Ethernet data ports support the following types of connections:
metrocell connections
microwave device connections—NLOS or LOS microwave connections on the RJ45 PoE+ ports
network connections—Gigabit Ethernet fiber connections on the three SFP ports
The console port and management port provide external management of the 7705 SARWx. The console port uses an
RJ45 serial connector to provide connectivity to the CLI. The management port uses an RJ45 Ethernet connector to
provide outofband system management.
The 5620 SAM supports the following 7705 SARWx variants:
Release 6.1 R2 or later:
5 GigE
Release 6.1 R3 or later:
4 GigE 4port ×DSL
5 GigE PoE+
5 GigE PoE+ GPS Rx
Release 6.1 R4 or later:
4 GigE 4port ×DSL GPS Rx
5 GigE GPS Rx
7705 SARX
The 7705 SARX is a fixed variant with three integrated MDAs. The variants are:
7705 SARX with AC power
7705 SARX with DC power
7705 SARX with AC power (conformal coated)
7705 SARX with DC power (conformal coated)
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 26/269
06.07.2017 Device management
MDA 1: T1/E1
ports 1 to 8 are T1/E1 ports
MDA 2: 2×Combo ports, 4×SFP, 1×SFP+
ports 1 and 2 are GigE combo ports
ports 3 to 6 are GigE SFP
port 7 is 10GigE SFP+
MDA 3: 2×Combo ports, 4×SFP, 1×SFP+
ports 1 and 2 are GigE combo ports
ports 3 to 6 are GigE SFP
port 7 is 10GigE SFP+
Dynamic system IP address updates for 7705 SAR nodes
When a 7705 SAR node is configured to acquire an address from a DHCP pool, the system IP address may change.
You can configure the 5620 SAM to react automatically to the change, and adjust to use the new IP address for
communication and for SDPs destined for the node.
See “To enable dynamic system IP address updates for 7705 SAR nodes” in the 5620 SAM System Administrator
Guide for information about enabling this feature.
9.9 7710 SR support
The AlcatelLucent 7710 SR is a modular, multiservice edge router that aggregates subscriber traffic over a variety of
interfaces. It is based on the AlcatelLucent 7750 SR, and is typically deployed in distributed hub sites and enterprise
customer offices to extend IP services to the network edge.
The 7710 SR chassis is optimized for the delivery of data, voice and video services, and supports up to 4 or up to 12
interfaces of various types and speeds.
9.10 7750 SR MG support
The 5620 SAM supports the discovery and management of the 7 or 12slot AlcatelLucent 7750 SR MG. The 7750
SR MG can be configured with an SGW instance and a PGW instance in an LTE network.
The following documents describe 5620 SAM management and configuration of the 7750 SR MG:
5620 SAM LTE EPC User Guide—Describes 7750 SR MG discovery, configuration, and management using
the 5620 SAM
5620 SAM Wireless Parameter Reference—Describes 7750 SR MG device parameters as represented in the
5620 SAM schema, in addition to parameters on LTE and LTE service forms in the 5620 SAM GUI
9.11 7750 SR support
The AlcatelLucent 7750 SR is a multiservice edge router designed for service providers, cable MSO, and enterprise
customers that deliver residential, business and mobile services through an IP/MPLS network.
Automatic provisioning for CPM5 SFMs
The 5620 SAM automatically provisions and configures the integrated SFMs of CPM5s that feature builtin modules.
The automated provisioning occurs during node discovery.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 27/269
06.07.2017 Device management
9.12 7850 VSG/VSA support
The AlcatelLucent 7850 Virtual Switch Gateway (7850 VSG) is the main hardware component of the data center
solution. The 7850 VSG is a topofrack switch that provides connectivity to servers which store virtual machines
(VMs). It is based on the SROS platform and includes standard Ethernet and L3 routing functionality.
The 7850 Virtual Switch Aggregator (7850 VSA) is a variant of the 7850 VSG. The 7850 VSA functions as an IP
router as an endofrack switch. It includes the SROS feature set, like the 7850 VSG. It can be deployed with the
standalone VSC in a twopart router setup.
The following documents describe 5620 SAM management and configuration of the 7850 VSG/VSA and the data
center feature set:
5620 SAM Nuage Virtualization User Guide—describes data center network management using the 5620 SAM
and 5650 CPAM.
5620 SAM Nuage Virtualization Solutions Guide—provides release overview information and use cases for
using the 5620 SAM to manage a data center network.
9.13 7950 XRS support
The AlcatelLucent 7950 XRS is a largescale routing system that is designed for core deployments. The 5620 SAM
supports the management of the 7950 XRS including device discovery, equipment management, routing
management, OAM, MPLS, QoS policies, and services.
Variants
The 5620 SAM supports the 7950 XRS20, 7950 XRS16c, and 7950 XRS40. The core feature set of the variants is
the same, but there are some physical differences that are described below.
7950 XRS20
The 7950 XRS20 has 20 XMA daughter card slots, which can be configured with XMA cards or compact XMA
cards. The shelf includes two CCMs that support flash memory modules.
7950 XRS16c
The 7950 XRS16c is a lower capacity variant of the 7950 XRS. The shelf has 16 XMA daughter card slots, which
can be configured only with compact XMA cards. Unlike the 7950 XRS20, the 7950 XRS16c shelf does not have a
CCM. The flash memory modules are connected to the CPM.
7950 XRS40
The 7950 XRS40 is composed of two 7950 XRS20 units that are interconnected by cables. 7950 XRS40 nodes
appear in the 5620 SAM as 7950 XRS20 nodes with an expanded equipment shelf, and a Chassis Topology
parameter that displays Extended (XRS40).
Shelf components
You can monitor and manage the following 7950 XRS shelf components using the 5620 SAM navigation tree:
CCMs
XCM card slots; each slot has two XMA daughter card slots
CPM card slots
SFM card slots
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 28/269
06.07.2017 Device management
fan trays
PEQ power supply trays
The number of the preceding components depends on the variant of the 7950 XRS.
The shelf components are N+1 redundant. The fan tray and power supply tray objects are automatically discovered
and provisioned, and require no configuration using the 5620 SAM. See chapter 14 for more information about
configuring shelf objects.
CCMs
The 7950 XRS20 shelf includes two CCMs that support operator access to the routing system. You can view and
monitor CCM and flash memory module properties from the CCM properties form. The CCMs are automatically
detected and provisioned.
Each CCM includes three flash memory modules which can be viewed and monitored by the 5620 SAM. The “cf1”
module is an internal flash module that is embedded in the system. The “cf2” and “cf3” modules are external compact
flash slots.
XCM and XMA cards
The 7950 XRS20 shelf includes ten XCM card slots that can be configured with XCM X20 cards. The 7950 XRS16c
shelf includes eight XCM card slots that can be configured with XCM X16 cards. Each XCM card can house up to
two XMA cards for a total of twenty XMAs per 7950 XRS20 shelf or sixteen XMAs per 7950 XRS16c shelf. XMA
card slots can also be configured with a compact XMA card, or CXMA card. The 7950 XRS16c can be configured
only with CXMA cards. The 5620 SAM supports the management of the following XMA/CXMA types on the 7950
XRS:
20port 10 GE SFP+ CXMA
2port 100 GE CFP CXMA
6port 40 GE QSFP CXMA
40port 10 GE SFP+ XMA
4port 100 GE CXP XMA
Note To configure the 40port 10 GE SFP+ XMA or 4port 100 GE CXP XMA cards on the 7950 XRS
20, you must configure SFM X20 B cards on the shelf. You cannot configure the XMA cards if the
shelf is configured with SFM X20 cards.
CPM cards
The 7950 XRS shelf includes two redundant CPM card slots. Each slot is automatically provisioned with CPM X20
or CPM X16 cards, depending on the variant of the 7950 XRS.
On the 7950 XRS20, each CPM card slot has an association with a CCM. If one of the components is removed, the
appropriate status is applied to the corresponding CPM or CCM. In the 5620 SAM navigation tree, the CPM in Card
Slot A is associated with CCM A. The CPM in Card Slot B is associated with CCM B.
On the 7950 XRS16c, each CPM X16 card includes three flash memory modules, which can be viewed and
monitored with the 5620 SAM. There is no associated CCM for the CPM X16.
SFM cards
The 7950 XRS shelf includes eight SFM card slots. SFM card slots on the 7950 XRS20 can be configured with SFM
X20 or SFM X20 B cards. SFM card slots on the 7950 XRS16c can be configured with SFM X16 or SFM X16 B
cards. You cannot configure a mix of SFM card types cards on one shelf. All configured slots must contain the same
type of SFM card. Seven SFM cards must be operational to provide full capacity to the XCM cards, and one SFM
card is redundant. At least one SFM card must be configured for the system to function.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 29/269
06.07.2017 Device management
Automatic provisioning for CPM5 SFMs
The 5620 SAM automatically provisions and configures the integrated SFMs of CPM5s that feature builtin modules.
The automated provisioning occurs during node discovery.
9.14 9471 WMM support
The 9471 WMM provides MME and SGSN functions, terminating signaling traffic from UE, base stations, SGW, and
other MME and SGSN to provide mobility functions and network access. The 9471 WMM equipment is represented
in the 5620 SAM equipment navigation tree. Configurable parameters are displayed in the WMM instance. 5620 SAM
support for the 9471 WMM includes the following:
configuration management
fault management
PM statistics retrieval and storage
pooling and bulk provisioning functions
inventory management
The following documents describe 5620 SAM management and configuration of the 9471 WMM:
5620 SAM LTE EPC User Guide—Describes 9471 WMM discovery, configuration, and management using the
5620 SAM
5620 SAM Wireless Parameter Reference—Describes 9471 WMM device parameters as represented in the
5620 SAM schema, in addition to parameters on LTE and LTE service forms in the 5620 SAM GUI
9.15 9500 MPR and 9500 MPRe support
The AlcatelLucent 9500 MPR is a microwave digital radio that supports PDH and Ethernet to migrate from TDM to
IP. The 9500 MPR provides a generic, modular IP platform for multiple network applications, such as 2G, 3G,
HSDPA, and WiMAX to accommodate broadband services.
The 9500 MPRe is the standalone, fully outdoor application of the MPTMC ODU, with no shelf unit. The 9500 MPRe
provides fixed or mobile Ethernet site backhauling and supports converged MPLS metro networks.
The following documents describe 5620 SAM discovery, management, configuration, and administration of 9500
MPR/9500 MPRe devices:
5620 SAM User Guide— Describes general device discovery, configuration, and management
5620 SAM MPR User Guide—Describes how to commission, configure, and manage 9500 MPR/9500 MPRe
devices, policies and services
5620 SAM System Administrator Guide—Describes device security management
9.16 9966 MS SC Gateway support
The 5620 SAM supports the management of the 9966 Multistandard Small Cell Gateway. The 9966 MS SC Gateway
is deployed on Advanced Telecommunication Computation Architecture (ATCA) hardware platforms. The 9966 MS
SC Gateway is a key component of the 5620 SAM Small Cell management solution, and integrates the signaling
gateway, voice gateway, and packet gateway functions into one unit, allowing for the management of these functions
within a single data model. The 9966 MS SC Gateway supports both 3G and 4G Small Cell access points, but each
gateway blade in the ATCA chassis needs to be dedicated to either 3G or 4G Small Cell access points. The 9966
MS SC Gateway supports preprovisioning based on the activation of workorders created in the 9952 WPS, as well
as online provisioning.
The 5620 SAM Small Cells User Guide describes the discovery and management of the 9966 MS SC Gateway using
the 5620 SAM.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 30/269
06.07.2017 Device management
9.17 eNodeB support
The eNodeB is an enhanced BTS system for UE access to the LTE RAN network and LTE services in the 700 MHz
spectrum. The eNodeB is available as a compact or distributed system that consists of a BBU and a compact TRDU
or distributed RRH component. Metro cell variants are also supported.
The following documents describe 5620 SAM management and configuration of the eNodeB:
5620 SAM LTE RAN User Guide—Describes eNodeB discovery, configuration, and management using the
5620 SAM
5620 SAM Wireless Parameter Reference—Describes eNodeB device MIM parameters as represented in the
5620 SAM schema, in addition to parameters on LTE and LTE service forms in the 5620 SAM GUI
Note In the event of a short link disconnection between the 5620 SAM and an eNodeB, ensure you
are viewing the most recent configuration information by clicking on the Resync button to perform a
resynchronization of the network element. See the 5620 SAM LTE RAN User Guide for more
information about resynchronizing eNodeB devices.
9.18 OmniSwitch support
The AlcatelLucent OmniSwitch family of devices is a group of Enterprise and Metro Ethernet LAN switches. The
5620 SAM supports the OmniSwitch chassis types listed in Table 92.
Table 92 5620 SAM OmniSwitch support
Family Characteristics AOS Chassis and cards
release support
supported
OS Layer 2+ Fast Ethernet Stackable LAN family of Release NonPoE chassis
6250 switches which includes the OS 6250SME (small 6.6.5 or OS 62508M
and medium enterprise) for the enterprise segment, later (Metro)
and the OS 6250M, for the Metro access segment. OS 625024M
(Metro)
OS 6250
24MD (Metro)
OS 625024
(SME)
PoE chassis
OS 6250P24
(SME)
OS Stackable layer 2+ GigE LAN switch available in 24 Release NonPoE chassis
6400 or 48port variants. Up to eight switches can be 6.4.5 or OS 640024
linked to form a stack. later OS 640048
PoE chassis
OS 6400P24
OS 6400P48
Fiber chassis
OS 6400U24
OS 6400
U24D
OS Stackable GigE LAN switch available in 10, 24, or Release NonPoE chassis
6450 48ports variants, with optional upgrade paths for 10 6.6.5 or OS 645010
GigE stacking, 10 GigE uplinks, and Ethernet later OS 645010L
(Metro) services. OS 645024
OS 645048
PoE chassis
OS 6450P10
OS 6450P10L
OS 6450P24
OS 6450P48
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 31/269
06.07.2017 Device management
Fiber chassis
OS 6450U24
Expansion port
models
OS 6450XNI
U2
OS 6450GNI
U2
OS 6450GNI
C2
Light models
OS 6450C24
L
OS 6450P24
L
OS 6450C48
L
OS 6450P48
L
OS Stackable layer 2/3 GigE fixed configuration switch — NonPoE chassis
6850 available in 24 or 48port variants. Up to eight OS 685024
switches can be linked to form a stack. OS 685024X
OS 685048
OS 685048X
OS 6850
U24X
OS 685024L
OS 685048L
PoE chassis
OS 6850P24
OS 6850P24X
OS 6850P48
OS 6850P48X
OS 6850P24L
OS 6850P48L
OS The OS 6850E is the next evolution of the OS 6850. Release NonPoE chassis
6850E In addition to supporting the features of the OS 6.4.6 or OS 6850E24
6850, the areas of enhancements for OS 6850E later OS 6850E24X
include form factor, new transceiver support, and OS 6850E48
new stacking mode. OS 6850E48X
OS 6850E
U24X
PoE chassis
OS 6850P24
OS 6850E
P24X
OS 6850EP48
OS 6850E
P48X
OS Stackable layer 2/3 GigE switch specifically built for Stackability Fiber chassis
6855 IP network deployments where environmental only on OS 6855U10
operating conditions are unusually demanding. The OS6855 OS 6855U24
OS 6855 is available with up to 24 gigabit ports and U24X OS 6855
four combo ports. chassis, U24X
Release (stackable)
6.4.6 or
Copper with PoE
later
chassis
OS 685514
OS 685524
OS The OS 6900 is a family of standalone aggregation OS 6900 HNI cards
6900 switches that consists of four models: the OS 6900 T20 and OSHNIU6
T20 (20 copper variable speed ports, one expansion OS 6900 QNI cards
slot), the OS 6900T40 (40 copper variable speed T40: OSQNIU3
ports, two expansion slots), the OS 6900X20 (640 Release
Gb/s, 20 fixed SPF+ ports, one expansion slot), and
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 32/269
06.07.2017 Device management
Gb/s, 20 fixed SPF+ ports, one expansion slot), and 7.3.2 or
the OS 6900X40 (1.28 Tb/s, 40 fixed SPF+ ports, later XNI cards
two expansion slots). The OS 6900 can only be OSXNIT8
OS 6900 (OS 6900T20
discovered in SNMPv3. An OS 6900 virtual chassis X20 and
node can only be discovered using the VC IP, and and OS 6900
OS 6900 T40 only)
not the master chassis IP or the slave chassis IP. X40:
All models provide 1+1 redundant hotswappable OSXNIU4
Release
power supplies and a fieldreplaceablefan tray. Each 7.3.1 or OSXNIU12
expansion slot is capable of supporting 120 Gb/s of OS 6900
bandwidth. virtual
The Backup function takes from the /flash/certified chassis:
directory. The Restore function restores the file in Release
the /flash/working directory. 7.3.3_646
OS A fiveslot chassis supporting one CMM and four — CMM cards
9600 network interface modules. It offers a wide range of OS9600CMM
(1) GigE and 10GigE interfaces and powerover OS9700CMM
Ethernet to support IP telephones, WLAN access OS9800CMM
points and video cameras. The OS 9600 supports a
Network interface
maximum of two load sharing power supplies.
cards
2port 10GigE
XFP
6port 10GigE
XFP
20port Fast
OS A highdensity tenslot chassis with two slots for — Ethernet
9700 control and eight slots for network interfaces (10/100 – SW
(1) supporting an aggregation of up to 192 GigE ports or upgradable to
48 10GigE ports. Designed for smart continuous 10/100/1000)
switching operation, the two center slots are RJ45 and 2
dedicated to CMMs allowing redundant port GigE
configurations. The OS 9700 supports a maximum (100/1000)
of three power supplies. SFP
24port GigE
SFP
24port GigE
(10/100/1000)
RJ45
24port GigE
(10/100/1000)
OS A high performance 18slot switch supporting 16 — RJ45 w/PoE
9800 slots for GigE and/or 10GigE network interface OS9GNIP24:
(1) modules. An additional two slots are reserved for 24port
primary and redundant CMMs. The OS 9800 (10/100/1000)
supports a maximum of four power supplies. TX (RJ45)
PoE support
48port GigE
(10/100/1000)
MRJ21
OS The OS 9700E is a high performance switch offering Release Network interface
9700E eight slots for GigE and/or 10GigE Network 6.4.6 or cards
(2) Interface (NI) modules. Additional two slots are later OS9GNI
reserved for primary and redundant Chassis C24E:
Management Modules (CMMs). 24port
10/100/1000
OS The OS 9800E is a high performance switch offering with RJ45
9800E 16 slots for GigE and/or 10GigE Network Interface support
(2) (NI) modules. An additional two slots are reserved OS9GNI
for primary and redundant Chassis Management U24E:
Modules (CMMs). 24port
1000baseX
with
SFP/MiniGBIC
support
OS9GNI
P24E:
24port
(10/100/1000)
T/TX (RJ45)
PoE+ support
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 33/269
06.07.2017 Device management
PoE+ support
OS9XNIU2E:
2port
unpopulated
10GigE with
XFP support
OS9XNI
U12E:
Deployment
fails if MPLS
license is
installed. Does
not support
MPLS/VPLS
operations.
OS The OS 10K is a highcapacity, highperformance Release CMM and CFM cards
10K (3) modular Ethernet LAN switch that provides 5.12 7.3.1 or OS10KCMM
Tb/s of switching performance. The OS 10K has a later OS10KCFM
12 slot chassis configuration: 4 slots for CMM/fabric
XNI cards
cards; and 8 slots for XNI or GNI cards that provide
OS10KXNI
Ethernet, GigE, and 10GigE capabilities.
U32E:
32
unpopulated
10G SFP+
transceiver
connectors
OS10KXNI
U32S:
32
unpopulated
10G SFP+
transceiver
connectors
OS10KXNI
U16E:
16
unpopulated
10G SFP+
transceiver
connectors
GNI cards
OS10KGNI
U48E: 48 SFP
transceiver
connectors
OS10KGNI
C48E: 48
autosensing
ports, each
port is
configurable
as 10BaseT,
100BaseTX, or
1000BaseT
QNI cards
OS10KQNI
U4: 40Gig
network
interface with
pluggable
QSFP
transceiver
connectors
OS10KQNI
U8: 40Gig
network
interface with
pluggable
QSFP
transceiver
connectors
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 34/269
06.07.2017 Device management
connectors
Notes
1. The 5620 SAM also supports the OS 9000 series of LAN switches which includes the OS 9600, OS 9700, and OS 9800.
2. The 5620 SAM also supports the OS 9000E series of LAN switches which includes the OS 9700E and OS 9800E.
3. The behavior of the power supplies is controlled by power management. You will see a power failure alarm even though power supplies
are connected to the OS 10K chassis and is not being used by the 10K node. The 10K power management puts power supply into an
inactive (down) state, if it is not required.
Caution 1 OmniSwitch devices do not support automatic synchronization with the 5620 SAM
database when you use the CLI to make configuration changes. To ensure that you are viewing
accurate OmniSwitch information in the 5620 SAM, you must resynchronize the NE by clicking on the
appropriate Resync button.
Caution 2 OmniSwitch NEs do not send trap notifications for all MIB changes on the NE. To ensure
that you are viewing the current configuration information in the 5620 SAM, you must resynchronize of
the NE by clicking on the appropriate Resync button.
OmniSwitch LAG objects
OmniSwitch NEs support static and dynamic LAGs. When you create a static LAG, you can add ports as LAG
members. The ports that you select as members of a dynamic LAG are first placed into an Unassigned Dynamic
LAG Members group. The OmniSwitch uses LACP to dynamically assign ports from an Unassigned Dynamic LAG
Members group to the appropriate LAG. When a port is assigned to a dynamic LAG, the port is removed from the
Unassigned Dynamic LAG Members group.
You can create VLANs, use 802.1Q framing, configure QoS conditions, and enable other networking functions on a
LAG, which is treated the same as physical link.
OmniSwitch LAG support includes:
up to 32 LAGs on an OS 6250, OS 6400, OS 6450, OS 6850, OS 6850E, or OS 6855 on a stack of
OmniSwitch devices
up to 128 LAGs on an:
OS 9600, OS 9700, and OS 9800
OS 9700E or OS 9800E
OS 6900
OS 10K
two, four, or eight Ethernet links in a LAG
access or network LAGs
Using WebView to manage an OmniSwitch
You can configure and manage an OmniSwitch using the WebView application, an AlcatelLucent webbased element
management tool that runs on an OmniSwitch. WebView supports the following web browsers:
Internet Explorer 6.0 or later for Windows
Netscape 7.1 for Windows
Mozilla Firefox 10.0 or later for RHEL
Note The web browser must have cookies and Java enabled.
See the appropriate OmniSwitch Switch Management Guide for information about configuring and using WebView.
See chapter 14 for information about opening WebView using the 5620 SAM GUI.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 35/269
06.07.2017 Device management
OmniSwitch port modes
The ports of OmniSwitch NEs can operate in either access more or network mode. Access ports can be added to
stacked VLANs as UNI ports, or to standard VLANs as tagged or untagged ports. Network ports can automatically
bind to stacked VLANs as NNI ports when the service is created. OmniSwitch NEs using AOS Release 6.4.6 or
later, or AOS Release 6.6.5 or later, can operate in hybrid mode. Hybrid ports can be added to standard VLANs as
tagged or untagged ports, and also bind to all stacked VLANs on an NE as NNI ports.
Note When a port is changed to hybrid mode, any previous UNI associations will be deleted.
9.19 GNE support
The 5620 SAM provides limited management support of generic NEs, or GNEs, which are typically nonAlcatel
Lucent devices.
Note The 5620 SAM discovers and manages the AlcatelLucent 9500 MSS1c as a GNE; see
Procedure 107 for information about how to discover and manage this device type.
5620 SAM GNE support is limited to the following:
display on topology maps and in the navigation tree, interfaces excluded
physical link creation and representation as a graphical and logical object
trap translation into 5620 SAM alarms
status polling using enterprise MIB object interface alarms
Telnet, SSH, and web sessions invocation
provisioning using CLI scripts
inclusion in a service instance using 5620 SAM scripts
GNE device discovery and polling in the 5620 SAM are configured using the same methods that are used for natively
managed devices, but the 5620 SAM uses preconfigured scripts to manage and unmanage GNEs. See chapter 11 for
information about device discovery. See the 5620 SAM Scripts and Templates Developer Guide for information about
creating CLI scripts using the 5620 SAM Scripts tool.
GNE drivers
Some GNEs have an optional GNE driver that extends existing GNE functions. The driver’s translator component
translates proprietary MIBs to the normalized standard 5620 SAM model. See section 10.2 for information about GNE
drivers.
Statistics support
The 5620 SAM supports the collection of a limited set of statistics counters from standard system, interface, and
routing MIBs on GNEs. These statistics are processed and presented in the same manner as statistics from other
devices. You can view GNE statistics on the Statistics tab of a GNE interface properties form, retrieve them using
the OSSI, and display them graphically using the 5620 SAM Statistics Plotter.
Note 1 To collect or view GNE statistics from routing MIBs, you require a valid 5650 CPAM license
that has a thirdparty router quantity greater than zero.
Note 2 If persistent SNMP indexes are not enabled on a GNE, one or more GNE interface indexes
may change after a GNE reboots. This can cause a mismatch between the statistics records collected
before the reboot and the current interface indexes. The 5620 SAM takes no action to identify or
correct such a mismatch.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 36/269
06.07.2017 Device management
Alarm support
By default, the 5620 SAM supports a limited number of standard system and interface SNMP traps for GNEs. You
can configure the 5620 SAM to raise userdefined alarms in response to specific GNE traps using alarm catalogs.
See section 10.2 for information about configuring userdefined alarms for GNEs.
2. 10 — Device commissioning and management
10.1 Device commissioning overview
10.2 GNE commissioning
10.3 Workflow to commission AlcatelLucent devices
10.4 Device commissioning procedures
10.5 Workflow to commission GNEs
10.6 GNE commissioning procedures
10.1 Device commissioning overview
An device requires preconfiguration before 5620 SAM management of the device is possible. When the
preconfiguration is complete, the 5620 SAM can discover the device, as described in chapter 11. See section 10.3 for
the device commissioning workflow.
Inband and outofband management
The 5620 SAM supports the inband and outofband management of devices. Figure 101 shows an example of in
band and outofband management.
Figure 101 Example of inband and outofband management
When you configure only inband management, management traffic between the 5620 SAM and a device is
transmitted through any port that is configured for network access, except the management port. For inband
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 37/269
06.07.2017 Device management
management, the 5620 SAM sends management traffic to the device system IP address, or to an optionally specified
L3 management interface.
When you configure only outofband management, management traffic between the 5620 SAM and a device is
transmitted through the management port of the device. For outofband management, the 5620 SAM sends
management traffic to the management IP address of the device.
When a device is configured for inband and outofband management, one method provides management redundancy
for the other. However, if the inband and outofband IP addresses are the same, the 5620 SAM cannot determine
which NE interface is active, and management redundancy is compromised. If the inband and outofband IP
addresses are the same on a newly discovered NE, the 5620 SAM raises an alarm.
Note 1 The OmniSwitch does not support management redundancy.
Note 2 The 5620 SAM uses one SNMP trap target for inband and outofband management. The
5620 SAM SNMP IP address must be routable from each IP address when inband and outofband
management are used. See the device documentation for information about configuring an SNMP trap
target.
The type of management is determined during device discovery. When the device is discovered using its
management IP address, system IP address, or L3 interface IP address, the inband and outofband addresses are
synced in the 5620 SAM. This enables configuration of management redundancy, if both inband and outof band are
available. In each case, a valid route to the device must exist. See chapter 11 for more information about the
discovery process.
In Figure 101, an outofband management route allows a ping from the 5620 SAM to the management IP address of
Router 1 (192.168.10.1/32). The inband connection sends management packets to the system IP address on Router
2 (12.12.12.2/32) on MDA port X.
Caution Do not use the 5620 SAM to modify the configuration of the inband port. If the port is shut
down, network visibility is lost.
Note In Figure 101, the IP address of Routers 1 and 2 ends with /number, which is the subnet mask.
Common subnet mask values are:
/31 for two hosts
/30 for two hosts with network and broadcasts numbers
/24 for 254 hosts
Some device types require configuration in addition to the SNMP configuration before they can be managed by the
5620 SAM. See the appropriate part of this section for devicespecific management information.
7705 SAR management bandwidth
Some additional bandwidth management configuration is required on the 5620 SAM, if you want to transmit on in
band management on the 7705 SAR. Currently, if inband and outofband management are both used, then the 7705
SAR will only transmit on the outofband management outofpreference if that route exists.
You need to configure 5620 SAM so that each 7705 SAR with outofband management connectivity has the
following parameter values:
Active Management IP In Band
Auto Revert to Preferred True or False
Management IP selection in Band Preferred
See Procedure 104 for the steps on how to configure these values.
7210 SAS inband and outofband management
The 7210 SAS supports inband and outofband management. The 7210 SASD, 7210 SASE, and 7210 SASK
support static routes, but do not support an IGP or SDPs. The example network shown in Figure 102 and the
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 38/269
06.07.2017 Device management
associated configuration steps describe the configuration required to enable 7210 SASE inband management using
static routes that are distributed to an IGP, which, in the example, is OSPF.
Figure 102 Example 7210 SASE inband management network
The following configuration steps are required to set up the example network:
1. Using the CLI, configure the SNMP security parameters on the devices that you need to discover. See
Procedure 101 for more information.
2. Perform the following steps on Core 1.
Configure an interface on port 1/1/2 that connects to the 5620 SAM server interface.
Configure an interface on port 1/1/3, which is connected to Core 2.
Create an L3 interface on port 1/1/4 by creating an IES.
Create a static route to Edge 1.
Create an ASBR OSPF (area 0.0.0.0) instance on the system and enable OSPF on the interfaces to
Core 2 and the 5620 SAM server.
Create a routing policy to distribute the static route to OSPF.
3. Perform the following steps on Core 2.
Configure an L3 interface on port 1/1/4, which is connected to Core 1.
Configure an L3 interface on port 1/1/3, which is connected to Core 3.
Enable OSPF (area 0.0.0.0) on the system and the interfaces connected to Core 1 and Core 3.
4. Perform the following steps on Core 3.
Create an L3 interface on port 1/1/4, which is connected to Core 2.
Create an L3 interface on port 1/1/3, which is connected to Edge 2.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 39/269
06.07.2017 Device management
Create a static route to Edge 2.
Create an ASBR OSPF (area 0.0.0.0) instance on the system and enable OSPF on the interface to
Core 2.
Create a routing policy to distribute the static route to OSPF.
5. Perform the following steps on Edge 2.
Create an IES L3 interface on port 1/1/3, which is an uplink port.
Create static routes that direct traffic to the IES L3 interface.
6. Perform the following steps on Edge 1.
Create an IES L3 interface on port 1/1/5, which is configured as an uplink port.
Create static routes to direct traffic to the IES L3 interface.
7. Ensure that each 7210 SASE can ping the network interface IP address which is configured on the 5620 SAM
main server.
8. Ensure that the 5620 SAM main server can ping the system IP address of each 7210 SASE.
9. Configure an inband polling policy using the 5620 SAM. See Procedure 105 for more information.
Firewalls and management bandwidth
The ports between 5620 SAM components, and between the 5620 SAM system and the managed devices, must be
open through firewalls to allow proper operation of the software. See the 5620 SAM Planning Guide for more
information about requirements for the following:
firewalls and open ports
communication bandwidth between 5620 SAM components
communication bandwidth between the 5620 SAM and managed network
IPv6 device management
The 5620 SAM supports device management using IPv6. When a device management port or system interface is
configured with an IPv6 address, and the associated discovery rule is configured to scan for the IPv6 address, the
5620 SAM discovers and manages the device using IPv6. To switch between IPv4 and IPv6 management of a
device, you must unmanage the device, create a new discovery rule that specifies the other protocol, and then
rediscover the device.
The 5620 SAM supports the configuration of IPv4 and IPv6 inband and outofband management addresses on the
same device.
Note 1 The 5620 SAM can manage a 7450 ESS, 7710 SR, 7750 SR, or 7950 XRS using IPv6 only
when the device also has an IPv4 inband or outofband management address.
Note 2 To use IPv6 for outofband management of a 7210 SASE, 7210 SASM, 7210 SASR, 7210
SAST, 7210 SASX, or 7705 SAR, you must configure an IPv6 address on the management port and
an IPv4 address on the system interface.
Note 3 The 7210 SASD, 7210 SASK, 7210 SASM, 7210 SASR, 7210 SAST, and 7210 SASX,
support inband management using IPv6.
Secure file transfers
The 5620 SAM supports secure and nonsecure file transfers for backups, restores, software upgrades, and statistics
collection. The device mediation policy determines whether FTP or SCP is used to perform file transfers to and from
the managed devices. SCP requires SSH2. See chapter 11 for more information about configuring SSH2.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 40/269
06.07.2017 Device management
10.2 GNE commissioning
A GNE requires preconfiguration for 5620 SAM management. When the preconfiguration is complete, the 5620 SAM
can discover the device, as described in chapter 11.
The 5620 SAM uses configurable profiles and CLI configuration scripts to discover and manage GNEs. You can use
one GNE profile for multiple GNEs of the same type.
By default, only the 5620 SAM admin user, or a user with an assigned admin scope of command role, can manage
GNE objects. To create and configure GNE objects, a nonadmin user requires a scope of command role that has
Create and Update/Execute permissions on packages and classes that include the following:
genericne—to create GNE interfaces and configure profiles
netw—to create discovery rules
script—to manage scripts
security.MediationPolicy and snmp.PollerManager—to create mediation policies
trapmapper—to create alarm catalogs that map SNMP traps to 5620 SAM alarms
The 5620 SAM can discover a device as a GNE only when the following conditions are in place.
The GNE preconfiguration is complete.
The System Object ID of the GNE is required for the GNE Profile, for example 1.3.6.1.4.1. When
multiple GNE profiles contain possible matches for a system object ID, the profile that contains the
system object ID with the longest or most specific match is chosen.
SNMP and/or NETCONF is configured and enabled on the device, as appropriate.
Telnet or SSH is enabled on the device.
A 5620 SAM GNE profile for the device exists.
A 5620 SAM mediation policy is configured with SNMP and NETCONF settings that match the device
configuration.
A discovery rule for the device exists.
See section 10.5 for the GNE commissioning workflow. See chapter 11 for information about mediation policies and
device discovery.
GNE drivers
A GNE driver is an optional software component that extends existing GNE functions by providing SNMP,
NETCONF, and CLI management of proprietary MIBs. Each driver includes a set of translators that maps MIB
objects to objects in the 5620 SAM model. A GNE driver has one translator for each type of managed MIB object;
depending on the object type, a GNE properties form has an additional tab that displays the object properties.
GNE drivers extend GNE management capabilities in the following areas, as applicable:
configuration management
service management
tunnel management
network assurance
service assurance
device life cycle management
See the 5620 SAM GNE Driver Installation Guide for information about installing a GNE driver. See the 5620 SAM
GNE Driver Compatibility Guide for information about compatibility among GNE drivers, GNE releases, and the 5620
SAM. See the appropriate 5620 SAM driver document for more information about driver capabilities, and discovery
and management instructions.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 41/269
06.07.2017 Device management
Invoking alternate element managers
If an EMS client application for a GNE is installed on a 5620 SAM GUI client station, you can use a rightclick GNE
menu option in the network navigation tree to open the EMS client application. The OSlevel command that opens the
client must be specified in the associated GNE profile, or in the individual GNE configuration, to enable the function.
A command in the configuration of a specific GNE overrides a command in the associated GNE profile.
If the command path is not included, the 5620 SAM attempts to locate the command using the paths listed in the
PATH environment variable of the client station OS.
If the command that opens an EMS client accepts an NE IP address as an argument, you can specify the address
using a keyword in the command entry. The 5620 SAM replaces the keyword with the target GNE IP address as it
runs the command.
An alternate GNE manager is configurable using the GUI or OSS. See Procedure 107 for information about
configuring an alternate EMS in a GNE profile. See Procedure 108 for information about specifying an alternate EMS
in the GNE configuration.
GNE profiles
5620 SAM management of a device as a GNE requires a GNE profile, which defines how the 5620 SAM
communicates with the device. A GNE profile includes the following elements:
a unique GNE name
the system object ID from the device MIB
the GNE category
the interface types that the GNE supports
the interfaces that can be specified as the endpoints of 5620 SAM physical links
an SNMP trap management configuration that associates trap configuration and deconfiguration scripts with
the profile
CLI profile information
an optional alarm catalog that defines the alarms that the 5620 SAM raises in response to SNMP traps from
the device
Configuring userdefined alarms for GNEs
The 5620 SAM monitors SNMP reachability and interface status, and raises a standard alarm for each of the
following events:
coldStart—The GNE restarts.
linkDown—An interface goes out of service.
linkUp—An interface returns to service.
GNE alarm catalogs
You can map GNE SNMP traps to userdefined 5620 SAM alarms in an alarm catalog, and associate the catalog with
a GNE profile. A GNE profile can have one alarm catalog that contains up to 150 traptoalarm mappings.
A mapping is one of the following types:
static—A specific SNMP trap is associated with a specific alarm.
dynamic—The mapping includes one or more transform functions that define alarm properties based on values
in SNMP trap PDUs.
Each mapping in a catalog defines an alarm that the 5620 SAM raises or clears when it receives a specific SNMP
trap. When the 5620 SAM receives a high trap volume and must discard traps that it cannot process, it does not
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 42/269
06.07.2017 Device management
distinguish between standard and userdefined traps. To conserve system resources, AlcatelLucent recommends
that you configure a GNE to send only the required traps to the 5620 SAM.
Traps that map to userdefined alarms require extra processing by the 5620 SAM and are managed in a separate,
resourcelimited queue. When this queue fills, the 5620 SAM discards some of the traps and raises an alarm. You
can monitor the queue length using the 5620 SAM Resource Manager. When a mapping is administratively disabled,
the 5620 SAM raises no alarm in response to an associated trap from a GNE.
GNE trap sequencing and throttling support are configurable in a GNE profile. After the 5620 SAM finishes throttling
traps from a GNE or encounters a trap sequence error, it resynchronizes the discovered device MIBs.
A mapping includes standard elements such as the trap OID, alarm type, probable cause, and severity, but can
include the following optional elements:
trap name
selfclearing designation—specifies that the alarm clears when a specific clearing trap is received, and has the
following requirements:
If the severity of the raising alarm is a static value, the clearing trap must have a static mapping in the
same catalog as the raising trap, and can be linked to only one raising trap.
If the severity of the raising alarm is defined using a transform function, the transform function must
include a raising value pair and a clearing value pair.
FDN extension, which is an alarmname extension that can include the following:
static text
scripting functions—expressions that specify the trap PDU values to include; these allow the same
alarm type to be raised in response to different traps while uniquely identifying the trap origin in the
alarm name.
additional text—used to provide information of value related to the trap event, for example, troubleshooting
actions; the additional text consists of the trap OID by default, but can include the following:
static text
scripting functions—expressions that specify the trap PDU values to include; these are used to
generate a more precise description of the alarm condition
System Address and/or Interface Index varbind positions for a GNE on which to raise an alarm
Note 1 The FDN extension of a GNE alarm is not appended to the Alarm Name field in the 5620
SAM GUI, but is included in the Additional Text field. To create a filter for GNE alarms that have FDN
extensions, you must filter on the Additional Text field.
Note 2 When the 5620 SAM drops or fails to receive an SNMP trap from a GNE, the trap is lost. The
5620 SAM is unable to request that a GNE resend an SNMP trap.
Note 3 If reliable communication via SNMP protocol is required, use “inform event” messaging
instead of trap notifications.
A change to an alarm catalog or to a mapping in a catalog takes effect immediately after you commit the change.
You can use a 5620 SAM GUI or OSS client to configure GNE alarm catalogs and alarm mappings. The GUI
supports the following methods:
configuration forms—for object creation, modification, viewing, and deletion
XML API script—for object creation and modification only
A script template for alarm catalog configuration is available at the following location:
/opt/5620sam/server/nms/sample/xmlapi/AlarmCatalogueTemplate.txt
See “Creating and executing scripts” in the 5620 SAM Scripts and Templates Developer Guide for information about
using the Scripts tool.
An OSS client can also retrieve a catalog or a subset of the alarm mappings in a catalog using the standard methods.
Transform functions
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 43/269
06.07.2017 Device management
A transform function is an optional catalog component that associates one or more values in an SNMP trap PDU
with an alarm property such as the alarm name, probable cause, or severity. For example, you can create a transform
function that assigns an alarm severity of Critical when the value in a specific varbind is 1, Major when the value is
2, and Minor when the value is 3.
When an alarm mapping includes one or more transform functions, the 5620 SAM can raise multiple alarms in
response to the same SNMP trap. A trap value and the associated alarm property value are specified as a value pair
in a transform function. You can also specify a default alarm property value that the 5620 SAM assigns to an alarm
when a received value is not defined in a value pair.
A transform function defines the input value type, such as integer, and the output alarm property type, such as
severity. You can modify these parameters only when the transform function does not contain a value pair and is not
used by a mapping.
A transform function returns an empty string when a received value is not defined in a value pair and no default alarm
property value is assigned. When the transform function defines the alarm name, probable cause, or severity, the
5620 SAM logs an error in response and does not raise an alarm.
10.3 Workflow to commission AlcatelLucent devices
The following workflow describes the highlevel tasks required to commission a device prior to discovery by the 5620
SAM.
1. Enable and configure SNMP on the device.
a. See Procedure 101 for 5620 SAM nativelymanaged devices.
b. See Procedure 102 for the OmniSwitch.
2. If required, configure the source of device SNMP traps; see Procedure 103.
3. If required, use a CLI to enable 5620 SAM inband management of the device by to configure a second trap
destination and trap log on the device. See section 10.2 for information about inband management. See the
device documentation for configuration information.
4. If required, establish a route for inband traffic. For example, to configure a static route or use OSPF. See
chapter 28 for more information on static routes. See chapter 29 for more information about OSPF.
5. Configure the 5620 SAM to use inband, outofband, or inband and outofband polling for the device. A 5620
SAM mediation policy specifies the polling interval. See chapter 11 for information about mediation policies.
a. See Procedure 104 for 7450 ESS, 7705 SAR, 7710 SR, 7750 SR, and 7950 XRS polling configuration
information.
b. See Procedure 105 for 7210 SAS polling configuration information.
c. See Procedure 106 for information about editing polling settings for multiple managed devices.
10.4 Device commissioning procedures
The following procedures describe how to commission devices that are nativelymanaged by the 5620 SAM except
for the devices listed in Table 101. See section 9.1 for a list of all devices managed by the 5620 SAM. See the
appropriate device documentation for information about using a device CLI.
Table 101 Location of device commissioning information
Device Information location
1830 PSS 1830 PSS32/16 Installation and System TurnUp Guide
1830 PSS Engineering and Planning Tool User Guide
1830 PSS DCN Planning and Engineering Guide (Photonic Applications)
1830 PSS Commissioning and Power Balancing Tool User Guide
5780 DSC 5780 DSC User Guide
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 44/269
06.07.2017 Device management
7750 SR MG 5620 SAM LTE EPC User Guide
9471 WMM Contact your AlcatelLucent technical representative
eNodeB Contact your AlcatelLucent technical representative
Procedure 101 To commission a device for 5620 SAM management
Caution Do not apply an SNMP log filter to the 5620 SAM SNMP log. The 5620 SAM cannot
manage an NE that has an SNMP log filter applied to the log used by the 5620 SAM, which is typically
log ID 98. In rare cases, AlcatelLucent may apply filters.
1. Open a console window on the device.
2. Enter the following command to configure the system address:
configure router interface system address nnn.nnn.nnn.nnn/mask
where nnn.nnn.nnn.nnn is the system IP address
mask is the subnet mask
3. Enter the following command to enable Telnet:
configure system security telnetserver
4. Enter the following command to enable FTP:
configure system security ftpserver
5. If required, enter the following command to enable SSH2:
configure system security ssh version 2
6. Enter the following command to enable console, FTP, and SNMP access for the appropriate user account on
the device:
configure system security user user_account access console ftp snmp
where user_account is the appropriate user account for Telnet, FTP, and SNMP access, for example, admin
7. If required, enter the following command to enable hash encryption for passwords and authentication keys
during device configuration save or list operations:
configure system security hashcontrol readversion readversion writeversion
writeversion
where
readversion is the version of encryption accepted during read operations, for example, 1, 2, or all to indicate that both are accepted
writeversion is the version of encryption used during write operations, for example, 1 or 2
Version 1 encryption uses a simple key algorithm that generates the same character string each time it hashes
a specific password or authentication key.
Version 2 encryption uses a more complex key algorithm that generates a different character string each time
it hashes a specific password or authentication key.
8. Enter the following commands in sequence to set the time zone and time:
configure system time zone time_zone offset_from_UCT
admin settime YYYY/MM/DD hh:mm:ss
where
time_zone is the appropriate time zone, for example, EST
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 45/269
06.07.2017 Device management
offset_from_UCT is the offset, in hours, from Universal Coordinated Time, also known as Greenwich Mean Time, for example, if you
specify EST, offset_from_UCT is 5, as EST lags UCT by five hours
YYYY/MM/DD hh:mm:ss is the current local time
9. If required, perform one of the following to enable a time protocol.
a. Enter the following command to enable NTP:
configure system time ntp serveraddress server_IP_address
where
server_IP_address is the IP address of the SNTP server
b. Enter the following command to enable SNTP:
configure system time sntp serveraddress server_IP_address
where
server_IP_address is the IP address of the SNTP server
10. Enter the following in sequence to enable the SNMPv2 engine and to configure an SNMP community:
configure system snmp no shutdown
configure system snmp packetsize 9216
configure system security snmp community community_name rwa version both
where community_name is the SNMPv2 community name
Note 1 The command is used for the 5620 SAM write mediation policy. If you are using
SNMPv2, you must use this mediation policy for read as well, or create another mediation
policy that is also configured for rwa.
Note 2 The SNMPv2 community string name rwa attributes must be enabled for the 5620
SAM to properly manage a device, even if the 5620 SAM is only used to monitor a network.
11. Enter the following commands in sequence to ensure that the device uses persistent SNMP indexes:
bof persist on
bof save
12. Enter the following commands in sequence to save the configuration changes and reboot the device:
admin save
admin synchronize bootenv
admin reboot now
The device initializes with SNMP communication enabled.
13. Enter the following to clear the log ID and trap group ID:
configure log
logid 98
shutdown
exit
no logid 98
no snmptrapgroup 98
exit all
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 46/269
06.07.2017 Device management
14. Use a 5620 SAM client to discover the device and to verify that the device configuration allows management
of the device. See chapter 11 for information about device discovery.
Procedure 102 To commission an OmniSwitch for 5620 SAM management
See the appropriate OmniSwitch documentation for more information about the CLI command syntax and SNMP.
Note 1 The 5620 SAM cannot discover an OmniSwitch that is configured with the factory default
settings.
Note 2 You must use a direct console port connection to access an OmniSwitch for the first time. All
other management methods such as SNMP, Telnet, FTP, and HTTP, are disabled until you enable
them.
1. Open a console window using a direct console port connection to the OmniSwitch.
2. Create a Loopback0 interface and assign an IP address to the interface by entering the following:
ip interface Loopback0 address xxx.xxx.xxx.xxx
where
xxx.xxx.xxx.xxx is the IP address of the interface
Note 1 Loopback0 is the name assigned to an IP interface to identify an address that is used
for network management purposes. The Loopback0 interface is not bound to any VLAN,
therefore it always remains operationally active.
Note 2 The Loopback0 interface name is casesensitive. Ensure that you enter the name
exactly as shown.
3. Enable SNMP sessions on the switch by entering the following:
aaa authentication snmp local
4. Enable FTP, Telnet, HTTP, or SSH sessions, if required, by entering the following:
aaa authentication ftp local
aaa authentication telnet local
aaa authentication http local
aaa authentication ssh local
5. Perform one of the following to configure the required version of SNMP on the switch and the 5620 SAM:
Note The OmniSwitch default user, admin, does not have SNMP access. Before the 5620
SAM can discover an OmniSwitch, you must create at least one user on the switch with SNMP
access.
a. For SNMP v2c:
i. Configure an SNMP v2 user by entering the following:
user user_name password password no auth
where
user_name is a username that corresponds to an SNMP v2 user who the 5620 SAM can identify; AlcatelLucent
recommends that you use the name sam, which is the 5620 SAM default name
password is a password associated with the username; the password is between 8 and 47 characters
Note If you need to use a different SNMPv2 default user name, create an
SNMPv2 default user name on the 5620 SAM. See “To create a default SNMPv2
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 47/269
06.07.2017 Device management
OmniSwitch user on a 5620 SAM system” in the 5620 SAM System Administrator
Guide for information about creating an SNMPv2 default user name.
ii. Configure SNMP v2 trap forwarding to the 5620 SAM by entering the following:
snmp station xxx.xxx.xxx.xxx v2 user_name
where
xxx.xxx.xxx.xxx is the IP address of the 5620 SAM main server
user_name is the username that you created in step i
Note Trap forwarding configuration occurs automatically when the 5620 SAM
discovers a switch and uses the default SNMP v2 user name sam or the user
name configured, if any.
iii. Configure an SNMP security level that allows the switch to accept all SNMP queries by entering
the following:
snmp security no security
iv. Configure an SNMP v2 community string by entering the following:
snmp community map community_string user user_name
where
community_string is the name of an SNMP v2 community string that the 5620 SAM can identify
user_name is the SNMP v2 username created in step i
v. Create a mediation security policy on the 5620 SAM that uses a community string that matches
the string created in step iv. See Procedure 115 for information about creating a mediation
security policy.
vi. Create a discovery rule on the 5620 SAM to discover the switch and reference the policy created
in step v. See Procedure 1111 for information about creating a discovery rule.
b. For SNMP v3:
i. Configure an SNMP v3 user on the switch by entering the following:
user user_name password password security_level
where
user_name is a username that matches an SNMP v3 USM username configured on the 5620 SAM
password is a password associated with the username; the password is between 8 and 47 characters. The password is
the plain text ASCII MD5/SHA authentication key and DES privacy key.
security_level is MD5, MD5 + DES, SHA, or SHA + DES
ii. Configure SNMP v3 trap forwarding to the 5620 SAM by entering the following:
snmp station xxx.xxx.xxx.xxx v3 user_name
where
xxx.xxx.xxx.xxx is the IP address of the 5620 SAM main server
user_name is the username created in step i
Note Trap forwarding occurs automatically when the 5620 SAM discovers a
device with a username that matches the SNMP v3 USM username specified in
the 5620 SAM mediation policy.
iii. Configure the SNMP v3 switch security option that you need by entering the following:
snmp security security_option
where security_option is one of the security options described in Table 102
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 48/269
06.07.2017 Device management
Table 102 SNMP security options
Option Description
no security All SNMP queries are accepted.
authentication set Includes:
SNPM v1 and v2 Gets
Nonauthenticated v3 Gets and GetNexts
Authenticated v3 Sets, Gets, and GetNexts
Encrypted v3 Sets, Gets, and GetNexts
authentication all Includes:
Authenticated v3 Sets, Gets, and GetNexts
Encrypted v3 Sets, Gets, and GetNexts
privacy set Includes:
Authenticated v3 Gets and GetNexts
Encrypted v3 Sets, Gets, and GetNexts
privacy all (default) Includes:
Encrypted v3 Sets, Gets, and GetNexts
traps only Includes:
All SNMP requests are rejected
iv. Create an SNMP v3 user on the 5620 SAM using the NE User Configuration manager. See “NE
user and device security overview” in the 5620 SAM System Administrator Guide for information
about NE user configuration.
Enable SNMP to give the SNMP v3 user SNMP access.
Choose a username that matches the name created on the switch in step i.
Choose the same SNMP v3 authentication protocol, privacy protocol, and password that
is configured on the switch.
v. Create an SNMP v3 mediation security policy. See Procedure 115 for information about
configuring a mediation security policy.
Choose the SNMP v3 (USM) security model option.
Choose a username that matches the name created on the switch in step i.
vi. Create a discovery rule that uses the mediation security policy created in step v. See Procedure
1111 for information about creating discovery rules.
6. Use a 5620 SAM client to discover the switch and to verify that the switch configuration allows you to manage
the switch.
Procedure 103 To configure the 5620 SAM SNMP trap sources
Perform this procedure to configure the sources of SNMP traps associated with log ID 98. If no SNMP log ID on a
device matches the log ID in the 5620 SAM configuration, the 5620 SAM recreates the log ID and SNMP trap group
on the device, which results in a single log file that receives traps from the following sources:
main
security—always included as an SNMP source
change—supported by the 5620 SAM for the 7950 XRS and for the 7750 SR
Caution This procedure requires a restart of each 5620 SAM main server, which is serviceaffecting.
Perform this procedure only during a scheduled maintenance window.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 49/269
06.07.2017 Device management
Perform this procedure only during a scheduled maintenance window.
1. If the 5620 SAM is deployed in a standalone configuration, go to step 3.
2. Perform the following steps to stop the standby main server.
i. Log in to the standby main server station as the samadmin user.
ii. Open a console window.
iii. Enter the following:
bash$ cd /opt/5620sam/server/nms/bin
iv. Enter the following to stop the main server application:
bash$ ./nmsserver.bash stop
v. Enter the following to display the main server status:
bash$ ./nmsserver.bash appserver_status
The command displays a status message.
vi. The main server is stopped when the command displays the following status message:
Application Server is stopped
If the command displays a different message, wait 5m and repeat step 2 v. Do not proceed to the next
step until the server is stopped.
3. Perform the following steps on the primary main server station or the standby main server station:
i. Log in to the main server station as the samadmin user.
ii. Open the /opt/5620sam/server/nms/config/nmsserver.xml file using a plaintext editor.
Caution Contact your AlcatelLucent technical support representative before you
attempt to modify the nmsserver.xml file. Modifying the nmsserver.xml file can have
serious consequences that can include service disruption.
iii. Locate the following text section:
<snmp
ip="samserverIP"
port="nnn"
trapLogId="98"
where
samserverIP is the IP address of the 5620 SAM main server
nnn is the SNMP port number
This default configuration applies to traps from main, security, and change, if available.
iv. Perform one of the following:
To restrict the trap source to main only, add the following line:
logIdSourceBits="80"
To restrict the trap source to main and change, add the following line:
logIdSourceBits="A0"
v. Save and close the nmsserver.xml file.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 50/269
06.07.2017 Device management
vi. Open a console window.
vii. Navigate to the /opt/5620sam/server/nms/bin directory.
viii. Enter the following to restart the main server:
bash$ ./nmsserver.bash force_restart
The main server restarts, and the configuration change takes effect.
4. Close the console windows.
Procedure 104 To configure polling for a 7450 ESS, 7705 SAR, 7710 SR, 7750
SR, or 7950 XRS
1. Choose Equipment or Routing from the navigation tree view selector, rightclick on a 7750 SR, 7450 ESS,
7710 SR, 7705 SAR, or 7950 XRS, and choose Properties. The Network Element form opens.
2. Record the system IP address and the management IP address.
3. If required, configure the Location and Current OLC State parameters.
4. Click on the Polling tab, then the General tab.
5. Enable or disable the Scheduled Polling parameter. Scheduled polling is configured using the Mediation
configuration form. See Procedure 115 for more information.
6. Configure the Redundant Synchronization Mode parameter.
7. Verify that the Persistent SNMP Indices parameter is set to true to ensure persistent SNMP indices are used.
8. Configure the required parameters.
Note 1 To configure LI parameters, you require LI user privileges.
Note 2 To view LI configuration information, you need LI privileges. Rightclick on a discovered
device in the navigation tree and choose Properties from the contextual menu, and click on the
LI Configuration Status tab.
9. View the readonly parameters to determine the current polling status:
Resync Status indicates whether the last poll was successfully completed.
Last Resync Start Time and Last Resync End Time indicate the start and finish of the last poll.
Scheduled Resync Status indicates whether the last scheduled poll was successfully completed.
Last Scheduled Resync Start Time and Last Scheduled Resync End Time indicate the start and finish
of the last scheduled poll.
10. Click on the Management tab and configure the required parameters.
The Auto Revert to Preferred parameter is configurable when the Management IP Selection parameter is set to
Out Of Band Preferred or In Band Preferred.
Note 1 To avoid a communications outage between the 5620 SAM and managed NEs, the
parameter settings in the Management Preference panel must match the parameter settings in
the Notifications Preferred Management panel. See the Management IP Selection parameter
description for more information.
Note 2 If you want to transmit on inband management on the 7705 SAR when both inband
and outofband management are both used, configure the Active Management IP, Auto Revert
to Preferred, and Management IP Selection parameters as described in "7705 SAR
management bandwidth".
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 51/269
06.07.2017 Device management
11. Save your changes and close the form.
Procedure 105 To configure polling for a 7210 SAS
1. Choose Equipment or Routing from the navigation tree view selector, rightclick on a 7210 SAS, and choose
Properties. The Network Element form opens.
2. Record the system IP address and the management IP address.
3. If required, configure the Location and Current OLC State parameters.
4. Click on the Polling tab, then the General tab.
5. Enable or disable the Scheduled Polling parameter. Scheduled polling is configured using the Mediation
configuration form. See Procedure 115 for more information.
6. Verify that the Persistent SNMP Indices parameter is set to true to ensure that persistent SNMP indices are
used.
7. Configure the required parameters in the Bof Configuration panel.
8. View the readonly parameters to determine the current polling status:
Resync Status indicates whether the last poll was successfully completed.
Last Resync Start Time and Last Resync End Time indicate the start and finish of the last poll.
Scheduled Resync Status indicates whether the last scheduled poll was successfully completed.
Last Scheduled Resync Start Time and Last Scheduled Resync End Time indicate the start and finish
of the last scheduled poll.
9. Click on the Management tab and configure the required parameters.
The Auto Revert to Preferred parameter is configurable when the Management IP Selection parameter is set to
Out Of Band Preferred or In Band Preferred.
Note The Active Management IP, Auto Revert to Preferred, and Management IP Selection
parameters are not supported on the 7210 SASD or 7210 SASK. The 7210 SASD and 7210
SASK support only inband management.
10. Click on the 7210 BOF tab to configure uplinks in the BOF for port redundancy.
Note If the image path and configuration file path are local, you do not need to configure the IP
address and routing information for uplink A and uplink B. You can optionally obtain IP
parameters using DHCP when you configure a value of 0 for the uplink port IP address. The
DHCP server should be configured to provide the IP address and the default gateway
information that is used to reach the server where the image and configuration files are stored.
11. Select an uplink port in the Uplink A panel.
12. Configure the required parameters in the Uplink A panel.
13. Select an uplink port in the Uplink B panel.
14. Configure the required parameters in the Uplink B panel.
15. Click on the Uplink Routes tab and click Create. The Uplink Route Configuration form opens.
16. Configure the required parameters and click Apply.
17. Repeat step 16 to add another uplink route. You can add up to ten routes for each uplink.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 52/269
06.07.2017 Device management
18. Save your changes and close the form.
Procedure 106 To edit polling settings for multiple devices
You can use the list of managed devices from the Discovery Manager Resync Status tab to modify polling settings
for a device or devices; for example, when you want to enable or disable polling on numerous managed devices.
1. Choose Administration Discovery Manager from the 5620 SAM main menu. The Discovery Manager form
opens.
2. Click on the Resync Status tab, select multiple devices from the list, and click Properties. The Network
Element (Multiple Instances) form opens.
Note You can only configure those parameters that are common to all devices selected from
the list.
3. Click on the Polling tab and enable or disable the Scheduled Polling parameter.
4. Save your changes and close the forms.
10.5 Workflow to commission GNEs
The following workflow describes the sequence of highlevel tasks required to commission a GNE prior to discovery
by the 5620 SAM.
1. Create a CLI script to enable trap forwarding to each main server in the 5620 SAM system. See the device
documentation for information about configuring SNMP trap targets. See “CLI scripts” in the 5620 SAM Scripts
and Templates Developer Guide for information about using the 5620 SAM to create CLI scripts.
2. Create a CLI script to disable trap forwarding to each main server in the 5620 SAM system. See the device
documentation for information about configuring SNMP trap targets.
3. Prepare the device for 5620 SAM discovery and management using a GNE profile; see Procedure 107.
4. If required, configure or modify a GNE alarm catalog for use with a GNE profile.
Create a GNE alarm catalog; see Procedure 1010.
Create a transform function for the alarm catalog; see Procedure 1011.
Add an alarm mapping to the alarm catalog; see Procedure 1012.
10.6 GNE commissioning procedures
The following procedures describe how to prepare a GNE for 5620 SAM management, and how to modify a GNE
configuration after device discovery.
Procedure 107 To prepare a GNE for 5620 SAM management
Perform this procedure to prepare a GNE, which is typically a nonAlcatelLucent device, for 5620 SAM discovery
and management.
1. Preconfigure the device using a CLI. Perform the following steps.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 53/269
06.07.2017 Device management
i. Enable FTP.
ii. Enable Telnet.
iii. Enable SNMP and/or NETCONF, as appropriate.
iv. Configure at least one SNMPv1, SNMPv2c, or SNMPv3 community.
v. Set the SNMP PDU size to 9216.
vi. Enable persistent SNMP indexes.
2. Choose Administration Generic NE Manager from the 5620 SAM main menu. The Generic NE Manager form
opens.
3. Click Create and choose Create Generic NE Profile. The Generic NE Profile form opens.
4. Configure the required parameters.
The Sys Object ID parameter must begin with the following, which identifies the SMI enterprises subtree
defined in RFC 1213: .1.3.6.1.4.1
Do not enclose the Alternate Element Manager value in quotation marks; the 5620 SAM automatically
encloses the value in quotation marks at run time.
You cannot modify the Generic NE Type parameter after the GNE profile is created; you must delete the GNE
profile and create a profile using the new Generic NE Type parameter value.
Note To specify the target GNE IP address in the Default Element Manager URL or as a
Default Alternate Element Manager command argument, use the %IP% keyword.
5. To associate a GNE driver with the profile, perform the following steps.
i. Click Select to choose a driver.
ii. Click on the Translators tab and click Add.
iii. Select one or more translators and click OK.
6. Click on the CLI Profile tab and configure the required parameters.
7. If required, configure the login confirmation parameters.
The Prompt and Answer parameters are configurable when the Enable Confirm Prompt parameter is selected.
8. If required, configure the second level login security parameters.
The Enable Login Command and Enable Login Prompt parameters are configurable when the Enable Second
Login parameter is selected.
9. To configure an interface for the GNE, perform the following steps:
i. Click on the Interface Types tab and click Add. The Select Generic NE Interface Type form opens.
ii. Choose an interface type and click OK. The form closes.
10. To associate one or more routing MIBs with the GNE profile, perform the following steps.
Note 1 After you discover the device using the GNE profile, you can use the Routing view in
the network navigation tree to view the discovered routing objects.
Note 2 You must configure the GNE interface types before you associate a routing MIB with a
GNE profile. Otherwise, you must perform a customized NE resync of all MIBs and select the
Ignore Timestamps parameter.
i. Click on the Other MIBs tab and click Add. The Select Generic NE Routing MIB form opens.
Note The Other MIBs tab is dimmed if you do not have a valid 5650 CPAM license that
has a thirdparty router quantity greater than zero. See “5650 CPAM routine system
maintenance” in the 5650 CPAM User Guide for information about 5650 CPAM licenses.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 54/269
06.07.2017 Device management
ii. Select one or more MIBs and click OK.
11. Click Apply and confirm your actions. The Trap Configuration tab is enabled
12. Click on the Trap Configuration tab and select a script in the Trap Configuration Script panel. During device
discovery, the 5620 SAM runs this script on the GNE to enable trap forwarding to the 5620 SAM.
13. Select a script in the Trap DeConfiguration Script panel. During device discovery, the 5620 SAM runs this
script on the GNE to enable trap forwarding to the 5620 SAM.
14. Select an alarm catalog in the Alarm Catalogue panel.
15. Save your changes and close the forms.
Procedure 108 To configure an alternate EMS for a specific GNE
Perform this procedure to specify an alternate EMS client application for a specific NE.
Note The EMS that you specify overrides an EMS specified in the associated GNE profile.
1. Rightclick on a GNE object in the network navigation tree and choose Properties. The GNE properties form
opens.
2. Configure the Alternate Element Manager parameter.
Note 1 Do not enclose the Alternate Element Manager value in quotation marks; the 5620
SAM automatically encloses the value in quotation marks at run time.
Note 2 To specify the target GNE IP address as an Alternate Element Manager command
argument, use the %IP% keyword.
3. Save your changes and close the form.
Procedure 109 To modify a GNE profile
Perform this procedure to change a GNE profile configuration.
1. Choose Administration Generic NE Manager from the 5620 SAM main menu. The Generic NE Manager form
opens.
2. Choose Generic NE Profile (Generic NE), select a GNE profile in the list, and click Properties. The Generic
NE Profile form opens.
The following tabs contain configurable parameters:
General—contains parameters that identify the GNE type
CLI Profile—contains parameters that define the console window prompts and commands
Trap Configuration—contains parameters that define the SNMP trap management configuration
Interface Types—allows the association of multiple types of interfaces with the GNE profile
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 55/269
06.07.2017 Device management
Caution If you modify the list of interfaces on the Interface Types tab, you must
resynchronize the entire GNE, as described in step 4.
3. Modify the required parameters for the GNE profile, click OK, and confirm your actions. The form closes.
4. If you modified the list of interfaces on the Interface Types tab, perform the following steps:
i. Rightclick on the GNE in the 5620 SAM topology map and choose Resync Customized Resync. The
Resync Site(s) form opens.
ii. Click Next and select the Ignore Timestamps parameter.
iii. Click Finish and close the Resync Site(s) form. The 5620 SAM resynchronizes the GNE.
Procedure 1010 To create a GNE alarm catalog
Perform this procedure to create an alarm catalog for use with a GNE profile.
1. Choose Administration Generic NE Manager from the 5620 SAM main menu. The Generic NE Manager form
opens.
2. Click Create and choose Generic NE Alarm Catalogue. The Generic NE Alarm Catalogue (Create) form
opens.
3. Configure the required parameters.
4. If required, perform steps 3 to 12 of Procedure 1011 to create a transform function for the catalog.
5. Click on the Mappings tab and click Create. The Generic NE Alarm Mapping (Create) form opens.
6. Configure the required parameters.
7. Perform one of the following:
a. Configure the Alarm Name parameter to specify a static alarm name.
b. Specify a dynamic alarm name:
i. Enable the Specify Transform Function parameter.
ii. Select a transform function beside the Transform Varbind Function parameter.
iii. Configure the Varbind Position parameter.
8. Perform one of the following:
a. Select a probable cause beside the Probable Cause parameter to specify a static probable cause.
b. Specify a dynamic probable cause:
i. Enable the Specify Transform Function parameter.
ii. Select a transform function beside the Varbind Transform Function parameter.
iii. Configure the Varbind Position parameter.
9. Perform one of the following:
a. Specify a static severity by configuring the Severity parameter.
b. Specify a dynamic severity:
Note When you specify the use of a transform function for the alarm severity, the
Mapping Type changes to Raising/Clearing. You cannot create a clearing mapping for
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 56/269
06.07.2017 Device management
this type of mapping; you must use a transform function to clear an alarm when the
alarm severity is defined using a transform function.
i. Enable the Specify Transform Function parameter.
ii. Select a transform function beside the Varbind Transform Function parameter.
iii. Configure the Varbind Position parameter.
10. Configure the varbind positions for specific objects on a GNE in the Alarmed Object panel:
System Address Varbind Position
Interface Index Varbind Position
Note In order to configure the System Address Varbind Position and Interface Index Varbind
Position parameters, you must set the Alarm Name parameter to GNE MTIE Alarm.
11. Click OK and confirm your actions. The form closes.
12. Repeat steps 5 to 11 to create an additional raising alarm mapping, if required.
13. Perform one of the following:
a. If you need to create a clearing alarm, continue to step 14.
b. If you do not need to create a clearing alarm, go to step 20.
14. Select a raising alarm mapping and click Create Clearing. The Generic NE Alarm Mapping form opens.
Note 1 A raising alarm mapping is indicated by the word Raising in the Mapping Type list
column.
Note 2 You can create a clearing alarm mapping only when the corresponding raising alarm is
in the same alarm catalog.
Note 3 You can associate a clearing alarm mapping with only one raising alarm mapping.
Note 4 You cannot create a clearing mapping for a mapping that uses a transform function to
define the alarm severity; you must use a transform function to clear an alarm when the alarm
severity is defined using a transform function.
15. Configure the required parameters:
Note 1 A static clearing alarm mapping inherits the following values from the associated
raising alarm:
Alarm Name—must match raising alarm Alarm Name
Probable Cause—must match raising alarm Probable Cause
FDN Extension—resulting text string must match text string generated by raising alarm
mapping
Additional Text—resulting text string must match text string generated by raising alarm
mapping
See Procedure 1010 for information about modifying the Alarm Name or Probable Cause value.
Note 2 The explicit FDN Extension and Additional Text values can differ from the values in the
raising mapping, but the generated text strings must match. For example, if the object name is
in varbind 2 of the raising trap and in varbind 3 of the clearing trap, the parameter values name
different varbinds but the script output is identical.
Note 3 The alarm severity in a clearing alarm mapping is set to Cleared and cannot be
changed.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 57/269
06.07.2017 Device management
16. If required, specify a dynamic alarm name:
i. Enable the Specify Transform Function parameter.
ii. Select a transform function beside the Varbind Transform Function parameter.
iii. Configure the Varbind Position parameter.
17. If required, specify a dynamic probable cause:
i. Enable the Specify Transform Function parameter.
ii. Select a transform function beside the Varbind Transform Function parameter.
iii. Configure the Varbind Position parameter.
18. Click OK and confirm your actions. The form closes.
19. Repeat steps 14 to 18 to create additional clearing alarm mappings, if required.
20. Save your changes and close the forms.
Procedure 1011 To create a transform function for a GNE alarm catalog
2. Click Create and choose Create Generic NE Alarm Catalogue. The Generic NE Alarm Catalogue form opens.
3. Click on the Transform Functions tab and click Create. The Generic NE Alarm Transform Function form opens
4. Configure the required parameters.
5. If you enabled the Specify Default Out Value parameter, select a value beside the Default Out Value
parameter.
6. Click on the Pairs tab and click Create. The Pair form opens.
7. Configure the In Value parameter.
8. Select a value beside the Out Value parameter.
9. Click OK and confirm your actions. The form closes.
10. Repeat steps 6 to 9 to add another value pair, if required.
11. Click OK and confirm your actions. The form closes.
12. Repeat steps 3 to 11 to create another transform function, if required.
13. Save your changes and close the forms.
Procedure 1012 To add an alarm mapping to a GNE alarm catalog
Note A modification to a GNE alarm catalog takes effect immediately after you commit the change.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 58/269
06.07.2017 Device management
2. Choose Generic NE Alarm Catalogue (Trap to Alarm Mapper), select an alarm catalog, and click Properties.
The Generic NE Alarm Catalogue form opens.
3. If required, configure the Description and Version parameters.
4. Perform steps 5 to 18 in Procedure 1010.
Procedure 1013 To delete a GNE alarm catalog
Note 1 You cannot delete an alarm catalog that is associated with a GNE profile. You must remove
the alarm catalog from each associated GNE profile before you can delete the catalog.
Note 2 When you delete a GNE alarm catalog, you delete the alarm mappings that the catalog
contains.
1. Choose Administration Generic NE Manager from the 5620 SAM main menu. The Generic NE Manager form
opens.
2. Choose Generic NE Alarm Catalogue (Trap to Alarm Mapper), select a GNE alarm catalog, and click
Properties. The Generic NE Alarm Catalogue form opens.
3. Click on the Generic NE Profiles tab and perform one of the following:
a. If no profiles are listed, go to step 4.
b. If profiles are listed, perform the following steps to remove the profile associations:
i. Select a profile and click Properties. The Generic NE Profile form opens.
ii. Click on the Trap Configuration tab and click Clear in the Alarm Catalogue panel.
iii. Click OK and confirm your actions. The form closes.
iv. Repeat steps i to iii for each listed profile.
4. Close the Generic NE Alarm Catalogue form.
5. Select the alarm catalog and click Delete.
6. Confirm your actions and close the form.
3. 11 — Device discovery
11.1 Device discovery overview
11.2 Configuring SSH security on devices
11.3 Device mediation policies
11.4 NE resynchronization
11.5 Server resource management
11.6 Workflow for device discovery
11.7 Device discovery procedures
11.1 Device discovery overview
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 59/269
06.07.2017 Device management
The 5620 SAM discovers devices using SNMP and stores the device properties in the 5620 SAM database. To
discover one or more devices in your network, you create a discovery rule and then scan the network for devices
according to the IP addresses or address ranges specified in the discovery rule.
A discovery rule contains one or more rule elements that specify which devices or subnets are to be included in, or
excluded from, the discovery process. For example, you can configure one rule element to discover a subnet and
another to exclude specific IP addresses from the subnet.
Note 1 The 5620 SAM does not attempt to discover tests or test suites that are configured locally on
a device, for example, using a CLI.
Note 2 If a discovered chassis exceeds the 5620 SAM license count during the execution of a
discovery rule, the 5620 SAM marks the device as Unmanaged.
After you update the 5620 SAM license to accommodate the additional chassis, you must manage the
device manually. See Procedure 1115 for information about managing a device.
When the system IP address, also called the system ID, is used to discover a device, the management is inband.
When the management IP address is used to discover a device, the management is outofband. See chapter 10 for
information about inband and outofband management.
Note If you need to change the system name of a device, you must unmanage and delete the device
from the 5620 SAM before you change the name, and then rediscover the device, See Procedures 11
15 and 1124 for information about unmanaging and deleting devices.
Device discovery using IPv6
The 5620 SAM supports the discovery of devices that use IPv6 inband or outofband management IP addresses. In
order for the 5620 SAM to discover and manage a device that uses IPv6, the device must have an IPv6 address on
the management port, system interface, or both. The 5620 SAM main server must also be given an IPv6 address
during installation.
Note To manage 7750 SR, 7710 SR, 7450 ESS, 7950 XRS devices using IPv6, the device must also
be configured with an IPv4 address on the management port for outofband management, or an IPv4
address on the system interface for inband management.
The IP version that the 5620 SAM uses to discover a device is specified in each discovery rule. If the 5620 SAM
discovers both IPv4 and IPv6 addresses on the system interface of a device, it discovers the device using the
address that corresponds to the IP version specified in the discovery rule.
Device SNMP management
Simple Network Management Protocol, or SNMP, is an applicationlayer protocol that provides a message format to
facilitate communication between SNMP managers and agents. SNMP provides a standard framework for NE
monitoring and management from a central location.
An SNMP manager controls and monitors the activities of network hosts that use SNMP. An SNMP manager uses a
get operation to obtain a value from an SNMP agent, and uses a set operation to store a value in the agent. The
manager uses definitions from a management information base, or MIB, to perform operations on the managed
device, for example, retrieving data values, replying to requests, and processing SNMP notifications called traps.
SNMPv1 and SNMPv2c provide no security, authentication, or encryption. Without authentication, an unauthorized
user is able to perform SNMP network management functions and eavesdrop on management information as it
passes from one system to another.
SNMPv3 requires that an authentication and encryption method such as SSH is assigned to each user for validation
by the NE. SNMPv3 authentication and encryption enable an NE to validate the system that issues an SNMP
message and to determine whether another system has tampered with the message.
For information about devicespecific SNMP support, see the SNMP chapter of the appropriate System Management
Guide for the device. For information about SSH security, see section 11.2.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 60/269
06.07.2017 Device management
SNMP packet size considerations for device discovery
The network infrastructure carrying traffic between the 5620 SAM main and auxiliary servers and the managed NEs
must support packet fragmentation and reassembly when the PDU size is greater than the MTU of the network path.
The 7210 SAS, 7450 ESS, 7705 SAR, 7710 SR, 7750 SR MG, 7750 SR, and 7950 XRS require an SNMP PDU size
of 9216 bytes to be configured and fragmentation support is required in the network path between the 5620 SAM and
the NE.
Consider the following:
When an intermediate network device receives SNMP traffic, it must be able to process fragmentation of
packets. If the SNMP packet exceeds the MTU size of the intermediate device, and the device does not
support fragmentation of packets, the packets may be dropped and device discovery may fail.
Verify that data payloads of the SNMP PDU size can travel from the managed devices to the 5620 SAM by
using a CLI to ping the IP address of the 5620 SAM main server, using a packet size of the configured SNMP
PDU. See “Packet size and fragmentation issues” in the 5620 SAM Troubleshooting Guide for information
about using traceroute and ping to verify packet transport.
SNMP streaming
During the initial discovery of a Release 11.0 R5 or later 7450 ESS, 7710 SR, 7750 SR, or 7950 XRS, the 5620 SAM
enables SNMP streaming on the device, if it is not currently enabled. SNMP streaming facilitates the bulk transfer of
MIBbased configuration data using a streaming mechanism. SNMP streaming may substantially reduce the time that
operations such as NE discovery and resynchronization require in a highlatency network. See Procedure 112 for
information about enabling and disabling SNMP streaming on an NE.
Device management states
A device can be in one of the following management states:
discovered—the 5620 SAM manages the device
unmanaged—an operator has unmanaged the formerly managed device; the management information is
removed from the 5620 SAM database. See see "Unmanaging and deleting devices" in this section for more
information
suspended—an operator has suspended management of the device; see "Suspending device management" in
this section for more information
Unmanaging and deleting devices
Using the 5620 SAM to unmanage a device excludes the device from the managed network, but a reference to the
device remains in the 5620 SAM discovery system. The unmanage function may be used for unusual conditions such
as when the 5620 SAM requires a complete refresh of device data because of data corruption. Unmanaging a device
results in a loss of management data for the selected device, which includes, but is not limited to, the following:
object names and descriptions policies
statistics script results
alarms scheduled activities
physical links device configuration backups
Deleting a device results in the complete loss of management data for the device and completely removes the device
from the managed network.
Caution Unmanaging or deleting a device results in the loss of all historical 5670 RAM AA statistics
for the device.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 61/269
06.07.2017 Device management
Suspending device management
When you need to exclude a device from 5620 SAM management but do not want to lose the 5620 SAM information
about the device, for example, during a maintenance period that may generate an exceptional number of SNMP traps,
you can use a GUI or OSS client to suspend the management of the device.
Caution When you suspend the management of a device, the 5620 SAM raises a critical alarm
against the device.
When you suspend management of a device, the 5620 SAM removes the associated trap targets from the device
configuration, and blocks the following operations:
SNMP deployment and trap handling; all traps from the device are dropped
NETCONF deployments and event subscriptions
statistics collection
automated FTP and other file transfers
GUI or OSS client configuration of device parameters; a configuration attempt results in a failed deployment
scheduled or periodic operations that the 5620 SAM initiates, for example:
connectivity checks
resynchronizations
device configuration backups
device software upgrades
OAM test and test suite execution
Note You cannot suspend the management of a device while a software upgrade or configuration
backup is in progress on the device.
You can use the 5620 SAM to perform the following on a suspended device:
open a Telnet or SSH CLI session
execute CLI scripts
open an FTP session
configure 5620 SAM parameters that affect the device management but are not deployed, such as the inband
or outofband management preferences
Note If you attempt to modify an OAM test or test suite that is deployed to a suspended NE, the
5620 SAM raises an alarm. The alarm does not automatically clear when the NE is remanaged.
As shown in Figure 111, when a device is suspended, the device icons in the network navigation tree and physical
topology map are colored purple. When a suspended device is in a group other than the Network group, only the
lower right corner of the Network group icon is colored purple.The following icons are also colored purple to indicate
that at least one device is suspended:
parent group icon in the network navigation tree Equipment and Routing views
parent group icon in the physical topology map
Note The group icon colors are prioritized; when a group contains one or more unreachable NEs and
one or more suspended NEs, the group icon is colored red.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 62/269
06.07.2017 Device management
Figure 111 GUI representation of suspended device
When you return a suspended device to the managed state, the 5620 SAM rediscovers the device to capture events
such as device reboots or software release changes, and initiates a full device resynchronization based on the
response to a trap sequence ID check.
Note The 5620 SAM also checks the device management parameters to adapt to a switch from one
type of management to another, for example, from inband to outofband.
Using multiple management interfaces
A default SNMP management interface on a 5620 SAM main or auxiliary server is defined during 5620 SAM system
deployment. To segregate the management traffic of different groups of NEs, for example, IPv4 and IPv6 networks,
you can configure additional main and auxiliary server management interfaces.
After you create the required interfaces, you must define the management network and subnets to associate with the
interfaces. The 5620 SAM subsequently attempts to discover the NEs in each network and subnet.
Caution 1 In a segregated network, the same 5620 SAM management interface must be used for the
inband and outofband management of an NE.
Caution 2 When an NE is managed inband and outofband using a nondefault interface, you must
assign the inband and outofband subnets to the interface.
Postdiscovery actions on discovered NEs
In a discovery rule, you can create and specify a postdiscovery action to perform on the successfully discovered
NEs included in the rule. The 5620 SAM performs the postdiscovery action automatically at the end of rule
execution.
A postdiscovery action requires a 5620 SAM control script that manages the autoconfiguration actions performed on
discovered NEs.
For example, an operator specifies a control script as a postdiscovery action in a discovery rule for a subnet. The
control script coordinates the execution of devicespecific child control scripts. The child control scripts call XML
API scripts that each configure a group of discovered NEs, such as aggregation ring or IP backhaul NEs. After the
5620 SAM executes the discovery rule, it invokes the control script to autoconfigure the successfully discovered
NEs in the subnet.
Note Because a postdiscovery action is intended to be autonomous, the 5620 SAM displays an error
message and halts a postdiscovery action that requires user interaction.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 63/269
06.07.2017 Device management
See “Script management” in the 5620 SAM Scripts and Templates Developer Guide for information about creating
control scripts, and for information about viewing example scripts.
From the Managed State tab of the Discovery Manager form, you can do the following:
List the postdiscovery action associated with each managed NE.
View the status of the script execution as it occurs.
View the script run result.
The Node Discovery Control form of an NE displays additional information and allows postdiscovery action
management. See Procedure 1114 for more information.
Postdiscovery actions design considerations
The following conditions apply to postdiscovery actions.
The 5620 SAM performs no logic validation of the associated scripts.
Deletion of the associated control script is blocked.
After a discovery rule runs, the action is not automatically executed on new NEs that are added to the rule. To
execute the action on the new NEs, you must rescan the network using the rule.
An action is performed on an NE only when the Full Resync Status of the NE is Full Resync Done.
If a device fails discovery, the action is not performed, and the script execution status is Not Executed.
Resynchronization of the NE does not invoke the script or change the execution status.
If the control script execution fails, an alarm is raised.
After a postdiscovery action is performed on an NE:
Unmanaging and remanaging the NE has no effect.
Deleting and rediscovering the NE causes the action to be performed on the NE.
11.2 Configuring SSH security on devices
The SSH protocol provides secure file transfer and file system access between the 5620 SAM and managed NEs.
SSH version 2, or SSH2, is enabled by default on many devices.
SSH2 uses paired public and private encryption keys to perform authentication. After an SSH key pair is generated
on an NE, the private key is stored locally, and the public key is used by SSH2 clients. A public key persists in the
5620 SAM for future SSH2 communication with the NE, and is used to verify that the client is connecting to the
correct SSH2 entity.
An SSH2 server on an NE identifies itself to a client by sending a message that is signed using the private key of the
server. The 5620 SAM uses the public key of the SSH2 server to authenticate the server identity.
SSH2 host key management
An NE sends an SSH2 host key when the 5620 SAM first tries to establish an SSH2 connection. The 5620 SAM
automatically accepts the public key fingerprint and stores it locally. The 5620 SAM uses the local fingerprint copy for
authentication during subsequent sessions.
If an NE sends a different host key in a subsequent session, the 5620 SAM rejects the connection attempt and
raises an alarm. If an operator determines that the host key change is valid, for example, because of an NE reboot
while host key persistence on the NE is disabled, the operator can manually delete the mismatched host key from
the 5620 SAM and accept the new key. The 5620 SAM subsequently accepts SSH2 connection requests from the
NE.
Note AlcatelLucent recommends that you enable host key persistence on an SSH2 NE to retain the
public key fingerprint after NE reboots. If public key persistence is disabled, connection attempts after
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 64/269
06.07.2017 Device management
an NE reboot fail until a 5620 SAM operator manually deletes the stored key. See Procedure 1121 for
information about deleting a mismatched host key.
By default, SSH host keys persistence is disabled on the 7210 SAS, 7450 ESS, 7705 SAR, 7710 SR,
7750 SR, and 7950 XRS.
SSH2 and device CLI sessions
When SSH2 for CLI sessions is enabled in the mediation policy of an SSH2capable device, SSH2 instead of Telnet
is used for each CLI session.
SSH1 is used only in SSH CLI sessions on NEs that do not support SSH2. SSH1 is not supported for
communications with GNEs.
SSH2 and script management
When SSH2 for CLI sessions is enabled in the mediation policy of an SSH2capable device, SSH2 is used instead
of Telnet for each script execution session.
SSH1 is used only in SSH CLI sessions on NEs that do not support SSH2. SSH1 is not supported for
communications with GNEs.
SSH2 and secure file transfers
When secure file transfers are specified in the mediation policy of an SSH2capable device, SCP is used instead of
FTP for backups, restores, software upgrades, and statistics collection.
11.3 Device mediation policies
To discover and manage devices in your network, you must create a mediation security policy to setup the security
and communication infrastructure between the 5620 SAM and each device within the specified discovery rule IP
range.
You can also optionally configure other mediation policies to specify other network mediation tasks such as
specifying the polling interval for MIB configuration changes, how the 5620 SAM processes specific events, and how
the 5620 SAM pings devices in the network to ensure they are reachable.
Table 111 describes the device mediation policies you can configure using the 5620 SAM.
Table 111 5620 SAM device mediation policies
Policy type Purpose See
Mediation Defines the network security model and communication protocols used to Procedure
security discover and manage NEs for all 5620 SAM user types except LI users. 115
The policy specifies the SNMP, CLI, and file transfer settings, and the
credentials for security functions.
A discovery rule requires a mediation security policy for:
read access
write access
SNMP trap access
MIB entry Defines the interval at which the 5620 SAM polls NEs MIBs for
configuration changes.
Management Defines the management IP address of the device that the 5620 SAM
ping pings periodically to verify reachability. You can specify which of the
following interfaces the 5620 SAM pings:
Out of Band Management Interface Ping
In Band Management Interface Pin
Standby CPM Ping
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 65/269
06.07.2017 Device management
Event Defines how the 5620 SAM processes specific SNMP events from
notification specific NE types and releases. See "Event notification polices" in this
section for more information.
LI mediation Defines the network security model used for LI mirror service creation; LI Procedure
security users do not use a standard mediation security policy. The policy 929
specifies the NE LI user credentials, the authentication and privacy
protocol types, and the required passwords.
The 5620 SAM GUI displays an LI mediation security policy only for an LI
user. See chapter 92 for information about configuring LI.
Event notification polices
To reduce the 5620 SAM processing load associated with SNMP events, you can configure a policy that specifies
which SNMP traps the 5620 SAM processes. An event notification policy acts as a filter that enables or disables the
processing of specific SNMP traps for a specific NE type and release.
A 5620 SAM operator with an admin or operations scope of command role and write access permission to the policy
package can create an event notification policy during mediation configuration. The 5620 SAM assigns a default
event notification policy to an NE during initial device discovery. You can optionally specify which traps to process
and which to ignore; processing is enabled for all supported traps in the default policy.
The following conditions apply to event notification policies:
After an NE upgrade, the 5620 SAM processes the new traps generated by the upgraded NE. A 5620 SAM
administrator must ensure that the event notification policies that are in effect before an NE upgrade are
correctly configured, and must modify them after the upgrade for new traps, as required.
A 5620 SAM software upgrades does not affect an existing policy.
Caution The 5620 SAM uses SNMP notifications to verify network management functions. Before
you configure an event notification policy, consult AlcatelLucent support to ensure that you do not
disable the processing of traps that the 5620 SAM requires.
SNMP statistics that include the number of ignored traps for an NE are available from the Statistics tab of an NE
properties form.
11.4 NE resynchronization
The Resync contextual menu option for an object specifies that SNMP MIB and CLI information bases for the object
are reread to resynchronize them with the 5620 SAM database. When you choose the Resync option at the NE level,
you can choose to resynchronize all MIBs or perform a customized resynchronization. When you choose to
resynchronize all MIBs, the color of the NE object in the navigation tree is yellow during the resynchronization. See
Procedure 1120 for more information about performing NE resynchronizations.
If SNMP streaming is enabled on an NE, the resynchronization time may be significantly reduced in a highlatency
network. See "SNMP streaming" in section 11.1 for more information.
Initial synchronization
A 5620 SAM operator must ensure that the discovery of each managed NE completes successfully, and that the NE
and 5620 SAM database information are fully synchronized. The First Full Resync Done attribute on the Managed
State tab of the Discovery Manager form indicates whether an NE has undergone one full resynchronization since the
NE discovery, most recent NE software upgrade, or a 5620 SAM system upgrade. If an NE has not undergone one
full resynchronization, and the Resync Status of the NE on the Resync Status tab is Resync Failed, the operator
must manually resynchronize the NE.
Resynchronization status
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 66/269
06.07.2017 Device management
The Resync Status tab of the Discovery Manager form displays the following resynchronization attributes for each
managed NE; the attributes are updated after an attempted resynchronization of all MIBs, but not after a customized
resynchronization attempt:
Resync Status
Last Resync Start Time
Last Resync End Time
Scheduled Resync Status
Last Scheduled Resync Start Time
Last Scheduled Resync End Time
The Resync Status value is one of the following:
Full Resync Done—a resynchronization has successfully completed
Full Resync Failed—a resynchronization attempt has failed
Full Resync Failed does not indicate that the SNMP agent on the NE is unreachable; if the agent is
unreachable, an alarm is raised against the NE and the NE icon color changes to red. When the agent is again
reachable, the alarm clears and the NE icon color changes to green.
In Progress—a resynchronization is in progress
Not Attempted—no resynchronization has been requested
Requested—the resynchronization request is queued for processing.
The Scheduled Resync Status value is one of the following:
In Progress—a resynchronization is in progress
Not Attempted—no resynchronization has been requested
Scheduled Resync Done—a resynchronization has successfully completed
Scheduled Resync Failed—a resynchronization attempt has failed
11.5 Server resource management
The 5620 SAM supports the grouping of NEs by network function for increased SNMP mediation efficiency.
Resource allocation is automatically configured during 5620 SAM installation and network discovery based on the
available system resources, and the numbers and types of NEs that are to be managed. The resource group to which
an NE belongs is initially determined by the device type. The following are the 5620 SAM NE resource groups and
the default device assignments:
global—for 5620 SAM tasks that are not associated with NEs
default—for NEs that do not belong to a specific resource group
core—for 7450 ESS, 7750 SR, and 7950 XRS devices
middle—for 7210 SAS, 7710 SR, and 7705 SAR devices
edge—for OmniSwitch and similar devices
GNE—for other network devices
The 5620 SAM logs the system load of each resource group at regular intervals. An AlcatelLucent support
representative can monitor system resource usage, determine whether the current resource allocation is appropriate,
and reconfigure resource management, if required.
Caution Only a qualified AlcatelLucent support representative can assess or configure 5620 SAM
server resource management. Contact AlcatelLucent technical support for more information.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 67/269
06.07.2017 Device management
11.6 Workflow for device discovery
The following is the sequence of highlevel actions required to enable and manage device discovery.
Preconfigure device for management
1. Configure the AlcatelLucent and GNE devices for management; see chapter 10.
Configure SNMP
2. As required, enable SNMPv3 device management; see Procedure 111.
3. As required, enable or disable SNMP streaming on a device for configuration data transfers to the 5620 SAM;
see Procedure 112.
Configure SSH
4. As required, configure SSH for secure device CLI access.
i. Configure SSH servers on devices; see the device documentation for configuration information.
ii. Ensure that SSH2 is enabled on devices; see Procedure 113.
iii. Enable SSH2 host key persistence on devices that support host key persistence; see Procedure 114.
Configure device mediation
5. Specify the network mediation parameters, and optionally configure the following mediation policies for
devices in specific discovery rules; see Procedure 115:
MIB entry policies that define how to poll specific device MIBs for changes
management ping policies that define periodic device connectivity checks
event notification policies that define how the 5620 SAM processes SNMP traps
6. As required, assign event notification policies to devices; see Procedure 116.
Configure additional management networks
7. If required, configure one or more additional management networks.
i. Define the management network and subnets to associate with nondefault management interfaces on
main and auxiliary servers; see Procedure 117.
ii. Create additional mainserver management interfaces; see Procedure 118.
iii. Create additional auxiliaryserver management interfaces; see Procedure 119.
Configure device discovery
8. If required, create control and XML API scripts for postdiscovery actions. See the 5620 SAM Scripts and
Templates Developer Guide for configuration information.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 68/269
06.07.2017 Device management
9. If required, create postdiscovery actions; see Procedure 1110.
Note You can also create postdiscovery actions during discovery rule creation.
10. Create the required device discovery rules and use the rules to discover devices; see Procedure 1111.
11. Manage discovery rules; see Procedure 1112.
12. As required, manage the postdiscovery actions in discovery rules.
a. View the execution status of an associated script; see Procedure 1113.
b. Manually execute a failed script; see Procedure 1114.
Incidental tasks
13. As required, perform the following.
a. Change the management state of a device; see Procedure 1115.
b. Change from SNMPv2c to SNMPv3 management of a device; see Procedure 1116.
c. Switch from nonsecure to secure mediation; see Procedure 1117.
d. Specify which management IP address is saved for a device when the device is set to an unmanaged
state; see Procedure 1118.
e. Rescan the network using a discovery rule; see Procedure 1119.
f. Synchronize the 5620 SAM information with the device configuration; see Procedure 1120.
g. Manage SSH2 host key acceptance; see Procedures 1121 and 1122.
h. View and save collected SNMP MIB information; see Procedure 1123.
i. Delete a device from the 5620 SAM; see Procedure 1124.
11.7 Device discovery procedures
Use the following procedures to configure device discovery and mediation.
Procedure 111 To enable SNMPv3 management of a device
SNMPv3 provides userbased security. The access granted is restricted to the scope of the configured users and
groups.
Note If you are configuring an NE for LI, you must create a second access group. See chapter 92 for
information about creating an LI user and access group.
1. Open a CLI session on the device.
2. Enter the following commands in the order shown to create a readwritenotify group for general SNMP
mediation on the managed device:
configure system security snmp
access group “SNMPv3_group” securitymodel usm securitylevel privacy read “iso”
write “iso” notify “iso”
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 69/269
06.07.2017 Device management
where
SNMPv3_group is the name to assign to the new SNMP group
3. If mediation of VPRN objects is required, enter the following command to create a readwritenotify group for
this purpose on the managed device:
access group “SNMPv3_group” securitymodel usm securitylevel privacy context
vprn prefix read “vprnview” write “vprnview” notify “iso”
where
SNMPv3_group is the name to assign to the new SNMP group
4. Enter the following command to exit the SNMP group configuration.
exit
5. Enter the following command to obtain the SNMP engine ID of the device.
show system info
The SNMP engine ID is displayed as SNMP Engine ID.
6. Generate an authentication key and a DES privacy key.
An authentication key is used to encrypt a user password.
A DES privacy key is used to encrypt the user SNMP packets.
Note The key authentication method determines the key length. An MD5 key is a 32character
strings; an SHA key is a 40character string.
i. Log in to a 5620 SAM singleuser client, client delegate server, or main server station.
Note 1 If you log in to a RHEL main or client delegate server station, you must log in
as the samadmin user.
Note 2 If you log in to a singleuser client station, you must log in as the user who
installed the client, or as a local administrator.
ii. Open a console window.
iii. On a RHEL station, navigate to the install_directory/nms/bin directory, where install_directory is one of
the following:
the 5620 SAM main server installation location, /opt/5620sam/server
the 5620 SAM client or client delegate server installation location, typically /opt/5620sam/client
iv. On a Windows station, navigate to the install_directory\nms\bin directory, where install_directory is the
5620 SAM client or client delegate server installation location, typically C:\5620sam\client.
v. Enter one of the following to create an MD5 or SHA authentication key:
on a RHEL station:
./nmsclient.bash password2key method password engine_ID
on a Windows station:
nmsclient.bat password2key method password engine_ID
where
method is the type of encryption, either MD5 or SHA
password is an ASCII password string
engine_ID is the SNMP engine ID obtained in step 5
The authentication key is displayed.
vi. Enter the following to create an MD5 or SHA DES privacy key.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 70/269
06.07.2017 Device management
on a RHEL station:
./nmsclient.bash password2key method password engine_ID
on a Windows station:
nmsclient.bat password2key method password engine_ID
where
method is the type of encryption, MD5 or SHA
password is an ASCII password string
engine_ID is the SNMP engine ID obtained in step 5
The DES privacy key is displayed.
vii. Store the generated keys.
7. Using the keys generated in step 6, create an SNMPv3 user on the managed device.
i. Enter the following sequence of commands at the prompt:
configure system security user SNMPv3_user
access snmp
snmp
authentication method authentication_key privacy deskey DES_privacy_key
group SNMPv3_group
exit all
where
SNMPv3_user is the name to assign to the new user
SNMPv3_group is the name of the new SNMP user group created in step 2
method is sha or md5, depending on the authentication method used
authentication_key is the authentication key value generated in step 6
DES_privacy_key is the DES privacy key value generated in step 6
Note A DES privacy key is 32 characters long. If SHA encryption, which produces a
40character key, is used to generate the DES privacy key in step 6, you must provide
only the first 32 characters of the key.
ii. Enter the following to save the configuration changes:
admin save
The device is now ready for management using SNMPv3.
iii. Close the CLI session.
8. Create an SNMPv3 NE user in the 5620 SAM.
See “NE user and device security” in the 5620 SAM System Administrator Guide for specific information about
creating and configuring NE users.
i. Choose Administration Security NE User Configuration from the 5620 SAM main menu. The NE
User Configuration form opens.
ii. Click Create. The NE User (Create) form opens.
iii. Configure the parameters as follows:
Enter the SNMPv3_username value from step 7 as the User Name.
Enable the SNMP option of the Access parameter.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 71/269
06.07.2017 Device management
On the SNMPv3 tab:
Choose MD5 or SHA as the Authentication Protocol, as required.
Choose DES as the Privacy Protocol.
Enter the password used to generate the authentication key in step 6.
Enter the password used to generate the privacy key in step 6.
Note In the mediation security policy that you create for the device, you must specify
the following:
SNMPv3 (USM) as the Security Model value
the SNMPv3_user value from step 7 as the User Name
See Procedure 115 for specific information about creating and configuring mediation
security policies.
Procedure 112 To enable or disable SNMP streaming on an NE
Perform this procedure to control whether an NE uses SNMP streaming for configuration data transfers to the 5620
SAM.
1. Rightclick on an NE in the network navigation tree and choose Properties. The NE properties form opens.
2. Click on the Polling tab, then on the Management tab.
3. Configure the Enable SNMP Streaming parameter.
4. Save your changes and close the form.
Procedure 113 To verify that SSH2 is enabled on a device
Perform this procedure to verify that SSH2 is enabled on a device, and to enable SSH2 on the device, if required.
1. Open a CLI session on the device.
2. Run the following CLI command to see whether SSH2 is enabled:
show system security ssh
3. If required, enter the following command at the prompt to enable SSH2:
configure system security ssh version 2
Note A 7705 SAR may become temporarily unreachable after you enable SSH and start the
SSH server on the device.
4. Close the CLI session.
Procedure 114 To enable SSH host key persistence on a device
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 72/269
06.07.2017 Device management
Perform this procedure to enable the persistence of the server host key on a 7210 SAS, 7450 ESS, 7750 SR, 7705
SAR, 7710 SR, or 7950 XRS. For other devices, see the user documentation for information about configuring SSH2
host key persistence.
1. Open a CLI session on the device.
2. Enter the following at the prompt to disable the SSH server:
configure system security ssh servershutdown
3. Enter the following at the prompt to enable host key persistence:
configure system security ssh preservekey
4. Enter the following at the prompt to enable the SSH server:
configure system security ssh no servershutdown
5. Enter the following at the prompt to verify that the preservekey function is enabled on the server:
show system security ssh
6. Close the CLI session.
Procedure 115 To configure device mediation
Perform this procedure to specify the general network mediation parameters, and to configure the following
communication and security policies for discovery rules:
MIB entry policies that define how to poll specific device MIBs for changes
management ping policies that define periodic device connectivity checks
event notification policies that define how the 5620 SAM processes SNMP traps
Note 1 LI mediation has special configuration requirements; see Procedure 929 for information.
Note 2 To configure SNMPv3 security, you must preconfigure the 5620 SAM and managed devices.
See Procedure 111 for information.
Note 3 For 9500 MPR SNMPv3 password information, see the 9500 MPR documentation.
1. Choose Administration Mediation from the 5620 SAM main menu. The Mediation (Edit) form opens.
2. Configure the parameters on the General tab.
3. Configure a mediation security policy.
Note Some NEs require specific mediation security policies. See the 5620 SAM device
specific documentation for information.
i. Click on the Mediation Security tab.
ii. Click Create or choose the default policy and click Properties. The Mediation Policy form (Create | Edit)
opens.
iii. Configure the general policy and SNMP mediation parameters.
Note 1 The recommended value of the Timeout (milliseconds) parameter for an 1830
PSS mediation policy is 60000.
Note 2 The recommended value of the Retry parameter for an 1830 PSS mediation
policy is 2.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 73/269
06.07.2017 Device management
Note 3 The Community String value must match the community string value on the
managed device.
Note 4 The Community String value for an 1830 PSS mediation policy must be set to
nms_snmp.
iv. If you set the Security Model parameter to SNMPv3 (USM), click Select to choose the required
SNMPv3 user. SNMPv3 user creation is described in Procedure 111.
Note If you specify the use of SNMPv3 in the policy, you must enable SSH2 in the
policy.
v. Configure the remaining parameters.
Note 1 If you choose Secure as the File Transfer Type value, you must set the
Communication Protocol parameter to SSH2.
Note 2 To use SSH2, you must enable SSH2 and host key persistence on the SSH
server of the device. See section 11.2 for information about configuring SSH2.
Note 3 If you choose SSH2 as the Communication Protocol, you must specify the
mediation policy for read and write access in the discovery rule of the device.
Note 4 If you choose SSH2 as the Communication Protocol, the User Name and User
Password parameters must be the SSH user name and password configured on the
device.
Note 5 See chapter 10 for information about enabling FTP access for a device user
account.
vi. Save your changes and close the form.
4. To configure one or more MIB Entry policies, perform the following steps.
i. Click on the MIB Entry Policies tab and click Search. A list of MIBs appears, organized by the product
name of the device that supports the MIB.
ii. Choose one or more MIBs from the list and click Properties. The MIB Entry Policy (Edit) form opens.
iii. Configure the required parameters in the Configuration panel.
Caution Changing the Number of Varbind per PDU value may affect the time required
for subsequent NE resynchronizations and degrade 5620 SAM system performance. Do
not configure the parameter without consulting AlcatelLucent technical support.
iv. Save your changes and close the form.
5. To configure a management ping policy, perform the following steps. A management ping policy specifies how
the 5620 SAM checks the connection to device management IP addresses. Each managed device may
provide one or more of the following addresses:
the system IP address, which is an inband management interface
the management IP address, which is an outofband management interface
the IP address of the standby CPM
Note 1 When the device does not have one or two of the IP addresses, for example, there is
no CPM IP address, ensure that you create a ping policy that does not have its schedule
enabled. This allows the assignment of an inactive ping policy during discovery configuration.
Note 2 The destination interface of the ping is determined during discoveryrule creation. You
can also perform an unscheduled ping from the Managed State tab of the Discovery Manager
configuration form.
Note 3 You can view management connection alarms from the NE properties form of the
managed device that was pinged. For example, from the Discovery Manager form, click on the
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 74/269
06.07.2017 Device management
Resync Status tab. Choose a device from the list and click Properties. From the NE properties
form, click on the Faults tab to view the alarms.
i. Click on the Ping tab.
ii. Click Create or choose a ping policy and click Properties. The Management Ping Policy (Create | Edit)
form opens.
iii. Configure the required parameters.
Note You must enable scheduling for a ping policy to be active. When scheduling is not
enabled, and an assigned managed device is not reachable, management connection
alarms may not be raised.
iv. Save your changes and close the form.
6. To configure event notification policies, perform one of the following. Otherwise, go to step 8.
Caution The 5620 SAM uses SNMP notifications to verify network management functions.
Before you configure an event notification policy, consult AlcatelLucent support to ensure that
you do not disable the processing of traps that the 5620 SAM requires.
a. Select a default trap policy from the list and click Properties. The Event Notification Policy (Edit) form
opens.
b. Create an event notification policy:
i. Click on the Event Notification Policies tab.
ii. Click Create or select a policy and click Properties. The Event Notification Policy (Create | Edit)
form opens.
iii. Configure the parameters.
iv. Click OK. The policy is listed on the form.
v. Apply the changes in the Mediation (Edit) form.
vi. Select the new policy in the list and click Properties. The Event Notification Policy (Edit) form
opens.
7. Enable or disable collection of traps in a policy.
Note You cannot configure the Administrative State parameter in a default event notification
policy. A default policy is indicated by a check mark beside the Default Policy indicator on the
General tab of the Event Notification Policy (Edit) form.
i. Click on the Notification Policies tab. A list of SNMP traps is displayed.
ii. Select an SNMP trap entry in the list and click Properties. The MIB Entry Policy trappolicy (Edit) form
opens.
iii. Configure the Administrative State parameter.
iv. Save your changes and close the forms.
8. Click OK to save your changes and close the Mediation (Edit) form.
Procedure 116 To assign an event notification policy to an NE
Caution The 5620 SAM uses SNMP notifications to verify network management functions. Before
you assign an event notification policy to a device, consult AlcatelLucent support to ensure that you
do not disable the processing of traps that the 5620 SAM requires.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 75/269
06.07.2017 Device management
1. On the equipment tree, rightclick on an NE icon and choose Properties. The Network Element (Edit) form
opens.
2. Click on the Polling tab and click Clear in the Assigned Event Notification Policy panel. The Select button in
the panel is enabled.
3. Select an event notification policy.
4. Save your changes and close the form.
Procedure 117 To configure a management network
Perform this procedure to create a management network and subnets to segregate the traffic between the nondefault
management interfaces on the main and auxiliary servers.
1. Choose Administration System Information from the 5620 SAM main menu. The System Information form
opens.
2. Click on the Management Networks tab.
3. Click Create. The Management Network (Create) form opens.
4. Configure the required parameters.
5. Click on the Management Interfaces tab.
6. Click Add. The Select Interface for Management Network (Create) form opens.
7. Click Search. The management interfaces are listed.
Note The default management interfaces are not listed.
8. Select an interface and click OK.
9. In a redundant 5620 SAM system, you must assign one interface from each main server to a managed
network.
To add another interface, repeat steps 6 to 8.
10. Click on the Management Subnets tab.
11. Click Create. The Management Subnet (Create) form opens.
12. Configure the required parameters.
Note 1 The Subnet Address value that you specify must include a mask that is between /24
and /32 for IPv4 NEs, and between /120 and /128 for IPv6 NEs.
Note 2 The subnets must not overlap.
13. To create an additional subnet, click Apply to save your changes and repeat step 12. Otherwise, click OK to
save your changes and close the form.
14. Click Apply to save your changes. The 5620 SAM attempts to discover NEs in the subnets using the
associated interfaces. The discovered NEs are listed on the Member Network Elements tab.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 76/269
06.07.2017 Device management
15. Save your changes and close the forms.
Procedure 118 To configure an additional management interface on a main
server
Note In a redundant 5620 SAM system, you must configure management interfaces for the required
networks and subnets on each main server. Otherwise, visibility of the networks and subnets is lost
after a server activity switch.
2. Click Properties in the Primary Server panel. The Main Server (Edit) form opens.
3. Click on the Management Interfaces tab.
4. Click Create. The Management Interface (Create) form opens.
5. Configure the required parameters.
6. Click OK. The interface appears in the list.
7. Save your changes and close the forms, as required.
Procedure 119 To configure an additional management interface on an
auxiliary server
2. Click on the Auxiliary Servers tab.
3. Select an auxiliary server and click Properties. The Auxiliary Server (Edit) form opens.
4. Click on the Management Interfaces tab.
5. Click Create. The Management Interface (Create) form opens.
6. Configure the required parameters.
7. Click OK. The interface appears in the list.
8. Save your changes and close the forms, as required.
Procedure 1110 To configure a postdiscovery action
Perform this procedure to create a postdiscovery action that you can associate with one or more discovery rules.
Note You can also create a postdiscovery action during discovery rule creation.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 77/269
06.07.2017 Device management
2. Click on the Post Discovery Actions tab.
3. Click Create or select a postdiscovery action and click Properties. The Post Discovery Action (Create | Edit)
form opens.
4. Configure the required parameters.
5. Click Select beside the Control Script Name parameter and choose a control script.
6. Click Select beside the Control Script Instance Name parameter and choose a control script instance.
7. Save your changes and close the form.
Procedure 1111 To configure a discovery rule
Perform this procedure to configure a discovery rule that contains the mediation, IP information, and policies required
to add NEs or EMS to the managed network.
1. Choose Administration Discovery Manager from the 5620 SAM main menu. The Discovery Manager form
opens.
2. Click Create to create a new discovery rule. The Create Discovery Rule step form opens.
Note 1 When you are finished each step, click Next to advance to the next step. You can
click Finish at any time.
Note 2 Depending on the purpose of the discovery rule, not every step in this procedure needs
to be completed.
3. Configure the required parameters in the Specify General Attributes step.
Note 1 When you close the Discovery Manager form, the 5620 SAM scans the network using
the discovery rule, if the Administrative State parameter of the discovery rule is set to Up.
Note 2 The Group Name parameter specifies the equipment group that discovered NEs are
added to. If the selected equipment group reaches the maximum element limit, any additional
discovered NEs are automatically added to the Discovered NEs group.
Note 3 The Discovered NEs Group Name cannot be chosen when configuring a Discovery
Rule for an EM system. See Procedure 628 for information about creating unique equipment
groups.
4. To add rule elements in the Add Rule Elements step, click Create, configure the required IP parameters, and
click OK. The rule element is added to the list.
5. To add auto discovery rule elements in the Add Auto Discovery Rule Elements ACL step, click Create,
configure the required parameters, and click OK. The rule element is added to the list.
6. In the Configure Mediation Security step, click Select in each of the following panels, as required, to specify
the mediation security policies for:
Read Access Mediation Policy
Write Access Mediation Policy
Trap Access Mediation Policy
Security Access Mediation Policy
Note 1 If you do not specify a policy, the default policy is applied.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 78/269
06.07.2017 Device management
Note 2 A 9500 MSS1c discovery rule requires the default SNMPv2 read and write access
policies.
7. In the Configure Management Ping Policy step, click Select in each of the following panels, as required, to
specify the ping policies for:
Out Of Band Management Interface Ping
In Band Management Interface Ping
Standby CPM Ping
Note 1 If you do not specify a policy, the default policy is applied.
Note 2 Management ping policies are created using the Mediation configuration form. These
are the policies applied during discovery rule creation. You must apply a ping policy even to
interfaces that do not exist. When there is no interface, you must choose a ping policy that has
its Schedule Enabled parameter set to disabled.
For example, if there is no standby CPM or outofband management IP address, specify a ping
policy that has the Schedule Enabled parameter set to disabled for the nonexistent management
and standby CPM interfaces. In this example, a ping policy with the Schedule Enabled
parameter enabled is required for the inband interface that does exist. See Procedure 115 for
information about creating ping policies.
8. In the Configure MIB Statistics Policy step, select a MIB statistics policy, if required.
9. In the Add Discovered Routers to Span(s) step, click Add to specify a span of control for the new NE
contained in the discovery rule. If you do not specify a span, the default span is applied.
Note New devices added to a span from a discovery rule are added explicitly to the span.
When a discovered NE group is part of a userdefined span, new devices that are discovered
using the discovery rule are automatically added to the span.
10. In the Configure Backup Policy step, select a backup policy, if required. If you do not specify a backup policy,
the default policy is applied.
11. The Add NE Self Config Policies step is for wireless management only. See the following for more
information:
“Selfconfiguration and discovery” in the 5620 SAM LTE RAN User Guide for eNodeB management
“SC GW selfconfiguration and discovery” in the 5620 SAM Small Cells User Guide
12. To configure an EMS in the Add EM Systems step:
i. Click Create. The EM System (Create) form opens.
ii. Configure the required parameters in the General tab.
iii. Click on the Element Managers tab.
iv. Click Create. The Element Manager (Create) form opens.
Note 1 After discovering an EM system, the system should be opened and its
administrative state set to Up in order to enable the connection to the 5620 SAM. A
maximum of four EM Systems may have their administrative state set to Up at any time
within the 5620 SAM.
Note 2 A manual resynchronization must be performed in order for alarms from an EM
system to be displayed in the 5620 SAM. This does not apply to the NEtO EM system
for 9500 MPR devices; alarms are aggregated automatically provided the Trap Access
Mediation policy in the Discovery step form is configured.
Note 3 The 5620 SAM is able to manage 10 000 alarms per EM system. When this
limit is reached, a critical alarm is raised and new incoming alarms are deleted. When the
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 79/269
06.07.2017 Device management
alarm counter for the EM System drops to 9000, the critical alarm is cleared and the
5620 SAM performs an alarm resynchronization on the EM system.
v. Configure the required parameters for host, communication, and identification.
vi. Save your changes and return to the Create Discovery Rule form.
13. To specify a postdiscovery action in the Add Post Discovery Action step, perform one of the following:
a. Click Select and use the list form that opens to associate an existing postdiscovery action with the
discovery rule.
b. Create a postdiscovery action to associate with the discovery rule. Perform the following steps.
i. Click Select. The Select Post Discovery Action form opens.
ii. Click Create. The Post Discovery Action (Create) form opens.
iii. Configure the required parameters:
iv. Click Select beside the Control Script Name parameter and use the list form that opens to
choose a control script.
v. Click Select beside the Control Script Instance Name parameter and use the list form that opens
to choose a control script instance.
vi. Save your changes and close the form.
vii. Select the new postdiscovery action and click OK. The new postdiscovery action is associated
with the discovery rule.
14. Click Finish to close the Create Discovery Rule form.
15. Apply your changes in the Discovery Manager form. If the Administrative State of the newly created discovery
rule is set to Up, the 5620 SAM scans the network using the discovery rule.
Procedure 1112 To enable, disable, or delete a discovery rule
When a discovery rule is enabled, the network is scanned according to the discovery rule when the discovery rule is
saved or rescanned. The network is also scanned according to the discovery rule as specified by the Discovery Rule
Scan Interval parameter in the Mediation form. If your discovery rule is disabled, the network is not scanned as
specified by these conditions.
When you delete a discovery rule, only the rule is removed. The NEs discovered using the rule are not removed from
the 5620 SAM, but the Discovery Rule ID for each of the NEs set to 0.
1. Choose Administration Discovery Manager from the main menu. The Discovery Manager (Edit) form opens.
2. Select a discovery rule and click Turn Up to enable the rule, Shut Down to disable the rule, or Delete to delete
the rule.
3. Close the form.
Procedure 1113 To view the postdiscovery action execution status
2. Click on the Managed State tab.
3. View the entries in the Script Execution Status column. The possible values are:
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 80/269
06.07.2017 Device management
unspecified—postdiscovery action not specified in discovery rule
Pending—postdiscovery action execution awaits discovery completion
Not Executed—control script not executed
In Progress—control script execution in progress
Successful—control script execution completed without failure indication
Failed—control script execution unsuccessful
Cleared—Failed state manually cleared
4. For each NE that has a Failed entry, perform the following steps to view the script execution result.
i. Click Show Results. The Results form for the NE opens.
ii. Click Search. A list of script results is displayed.
iii. Select a result in the list and click Properties. The View Result form opens. The form displays
information such as the script name, version, run time, and execution status.
iv. View the information to determine the required corrective action.
v. If required, perform the following steps to export the result information to a file.
Choose File Export from the View Result form main menu, or click on the Export icon. The
Export form opens.
Navigate to the location in which you want to save the file, and enter a filename in the File
Name field.
Click Export. The result text is saved in the specified file.
Note You can also export a script result to a file using the Export button on the Results
form for the NE.
5. To delete a result, perform the following steps.
i. Select the result on the Results form and click Delete. A dialog box appears.
ii. Click Yes. The result is deleted.
Procedure 1114 To manage a postdiscovery action failure on an NE
Perform this procedure to do the following:
reset the script execution status for an NE
manually run the postdiscovery action script against the NE
This action may be required after the script associated with a postdiscovery action fails and the cause of the failure
is corrected.
Note Clearing the status also clears the associated alarm that is raised when postdiscovery script
execution fails.
2. Click on the Managed State tab.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 81/269
06.07.2017 Device management
3. Select an NE with an Execution Status of Failed and click Properties. The Node Discovery Control (Edit) form
opens.
4. Click on the Post Discovery tab.
5. Click Clear. The Script Execution Status changes from Failed to unspecified.
6. To execute the script, perform the following steps.
i. Click Execute Script. The Execute script form opens.
ii. Click Execute. The script executes, and a script object is displayed in the navigation tree of the form.
iii. Select the script object in the navigation tree.
iv. Expand the Status and Script Results panels on the right side of the form to reveal the script execution
information.
v. Click Save Result to save the result in the 5620 SAM database.
7. Close the forms, as required.
Procedure 1115 To manage, suspend, or unmanage a device
Perform this procedure to change the management state of a device.
Note Managing and unmanaging a HIP device is not supported. To unmanage or delete a HIP device,
you must set the EM system administrative state to Down, and then delete the EM system.
2. Click on the Managed State tab.
3. Select a device in the list.
4. Perform one of the following:
a. Click Manage to return an unmanaged or suspended device to the managed state.
b. Click Suspend to suspend the management of the device.
Warning Suspending the management of a device results in a loss of communication
with the device.
Caution When you suspend the management of a device, the 5620 SAM raises a
critical alarm against the device.
c. Click Unmanage to stop the management of the device.
Warning 1 Unmanaging a device results in a loss of management data for the device.
See "Unmanaging and deleting devices" in section 11.1 for more information.
Warning 2 Unmanaging a device results in the loss of all historical 5670 RAM AA
statistics for the device.
5. Save your changes. The Managed State of the device changes to one of the following:
managed, if you are remanaging the device
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 82/269
06.07.2017 Device management
suspended, if you are suspending management of the device
not managed, if you are unmanaging the device
Procedure 1116 To change from SNMPv2 to SNMPv3 management of a device
Perform this procedure to change the management protocol that the 5620 SAM uses for a device from SNMPv2 to
SNMPv3.
1. Perform Procedure 111 to do the following.
Create an SNMPv3 user and group on the device.
Enable SNMPv3 on the device.
2. Perform Procedure 115 to create an SNMPv3 mediation policy.
3. Perform Procedure 1111 to create a new discovery rule for the device. Specify the new SNMPv3 mediation
policy for read, write and trap access on the Mediation Security tab.
If the Administrative State parameter of the discovery rule is Up, the 5620 SAM discovers the device and
begins to manage the device using SNMPv3.
Otherwise, you can discover the device later, as described in step 4.
4. To discover the device after discovery rule creation, perform the following steps.
i. Choose Administration Discovery Manager from the 5620 SAM main menu. The Discovery Manager
(Edit) form opens with the Discovery rules tab displayed.
ii. Select the discovery rule created in step 3 and click Properties. The Topology Discovery Rule (Edit)
form opens.
iii. Ensure that the Administrative State parameter is set to Up.
iv. Click OK to save the change, if required, and close the form.
v. Select the discovery rule and click Rescan. The 5620 SAM discovers and begins to manage the device
using SNMPv3.
vi. Close the Discovery Manager form.
5. Edit the SNMPv2 discovery rule for the device to exclude the device from discovery.
6. Resynchronize the device with the 5620 SAM; see Procedure 1120.
7. Use a CLI on the device to remove the following items, which are no longer required:
SNMPv2 user
SNMPv2 group
SNMPv2 trap targets
Procedure 1117 To switch from nonsecure to secure mediation
2. Click on the Mediation Security tab. You can create a mediation policy as described in Procedure 115, or
modify the default mediation policy to use SSH2. Perform one of the following.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 83/269
06.07.2017 Device management
a. Click Create to create a new mediation policy. The Mediation Policy (Create) form opens.
b. Choose the default policy from the list, and click Edit. The Mediation Policy (Edit) form opens.
3. Configure the required parameters using the prescribed values:
SSH2 as the Communication Protocol
The SSH2 server user name and password as the User Name and User Password
Secure as the File Transfer Type
Note When the File Transfer Type is set to Secure, the Communication Protocol, User
Name, and User Password parameters must be configured with the SSH2 information.
The port that the NE uses for SSH2 communication as the SSH2 Server Port
4. Configure the remaining parameters on the form.
5. Save your changes and close the form.
6. Create a new discovery rule that uses the new SSH2 mediation policy as the readaccess mediation policy
and the writeaccess mediation policy. See Procedure 1111 for information about creating discovery rules.
8. Click on the Managed State tab. A list of managed devices appears.
9. Choose the device from the list that you want to use SSH2 for CLI sessions and secure file transfers.
10. Click Properties and click on the Mediation Security tab.
11. Choose the newly created SSH2 mediation policy as the read access mediation policy.
Note You can also change the mediation policy for a discovery rule by performing step 11 and
choosing a discovery rule from the Discovery Rules tab.
12. Save your changes and close the form.
Procedure 1118 To specify which management address the 5620 SAM uses to
remanage a device
You can specify which management IP address is saved for a device when the device is set to an unmanaged state.
You can configure the 5620 SAM to save the original management IP address or the most recently used management
IP address for a device.
1. Choose Administration Discovery Manager from the 5620 SAM main menu. The Discovery Manager (Edit)
form opens.
2. Click on the Managed State tab.
3. Choose a device and click Properties. The Node Discovery Control (Edit) form opens.
4. Configure the Use Original Management IP parameter and click OK.
5. Save your changes and close the forms.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 84/269
06.07.2017 Device management
Procedure 1119 To rescan the network for a device according to a discovery
rule
2. Select one or more discovery rules and click Rescan.
The 5620 SAM scans the network as specified by the discovery rules and discovers devices. After a device is
discovered, the 5620 SAM server sets the device in a managed state and adds the NE properties to the 5620
SAM database.
Procedure 1120 To partially or fully resynchronize NEs with the 5620 SAM
database
1. On the equipment tree, select one or more NEs, as required.
2. Choose a resynchronization option.
a. Rightclick on one of the selected devices you want to resynchronize with the 5620 SAM database and
choose Resync Resync All MIBs.
Note Choosing Resync All MIBs will fully resynchronize all MIBs for the devices,
ignoring timestamps.
b. Perform a partial resynchronization.
i. Rightclick on one of the selected devices you want to resynchronize with the 5620 SAM
database and choose Resync Customized Resync. The Resync Site(s) form opens.
ii. Select Choose MIB Entries and click Next.
iii. Select one or more MIB entries from the list and click Next.
iv. Configure the Ignore Timestamps parameter.
v. Click Finish and close the form.
Procedure 1121 To manually accept a mismatched SSH host key
Perform this procedure to manually accept a rejected SSH host key in order to establish a connection to the SSH
server on an NE.
Caution Before you accept a mismatched host key, you must verify the validity of the SSH
connection.
1. Open the SSH2 Known Host Key Manager by performing one of the following.
a. Choose Administration Security SSH2 Known Host Key Manager from the 5620 SAM main menu.
The SSH2 Known Host Key Manager filter form opens.
b. Perform the following steps.
i. Choose Administration Discovery Manager from the 5620 SAM main menu. The Discovery
Manager (Edit) form appears.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 85/269
06.07.2017 Device management
ii. Click on the Managed State tab and click Search. A list of managed devices appears.
iii. Select a device in the list and click Properties. The Node Discovery Control (Edit) form opens.
iv. Click on the Mediation Security tab.
v. Click SSH2 Known Host Key. The SSH2 Known Host Key Manager filter form opens.
2. In the SSH2 Server Key Status column header, choose Mismatch SSH2 Host Key as a match criterion using
the dropdown menu.
3. Click Search. A list of mismatched host keys is displayed.
4. Select the required host key entry.
5. Verify with the device administrator that the key fingerprint is the host key of the required device.
6. Click Delete to delete the mismatched host key. The mismatched host key is deleted and a connection to the
SSH server can be established.
7. Close the forms.
Procedure 1122 To view the SSH2 host keys to identify active and
mismatched keys
You can view the SSH2 host keys in order to identify active and mismatched keys.
1. Open the SSH2 known host key manager by performing one of the following.
a. To view the active and mismatched SSH host keys on all managed NEs, choose Administration
Security SSH2 Known Host Key from the 5620 SAM main menu. The SSH2 Known Host Key
Manager form opens.
b. To view the active and mismatched SSH host keys on specific managed NEs:
i. Choose Administration Discovery Manager from the 5620 SAM main menu. The Discovery
Manager (Edit) form appears.
ii. Click on the Managed State tab and click Search. A list of managed devices appears.
iii. Select a device and click Properties. The Node Discovery Control (Edit) form opens.
iv. Click on the Mediation Security tab.
v. Click SSH2 Known Host Key. The SSH2 Known Host Key Manager form opens.
2. Configure the filter criteria and click Search. A list of active and mismatched host keys appears.
3. Close the forms.
Procedure 1123 To list and save SNMP MIB information
You can list and save SNMP MIB information, which may be of use for purposes such as the following:
to maintain a record of the SNMP MIBs that the 5620 SAM supports
to compare SNMP MIB support between 5620 SAM releases
to identify the polling interval for a MIB entry
1. Choose Administration Mediation from the 5620 SAM main menu. The Mediation (Edit) form opens.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 86/269
06.07.2017 Device management
2. Click on the MIB Entry Policies tab.
3. View the polling interval for a MIB entry.
i. Select a MIB entry and click Properties. The MIB Entry Policy (Edit) form opens.
ii. View the polling interval setting in the Configuration panel.
iii. Close the form.
4. Sort the list according to the contents of a column by clicking on the column header.
5. Save the listed information to a file.
i. Rightclick on a column header and choose Save to File. The Save As form opens.
ii. Use the form to specify the file that is to contain the saved information.
iii. Click Save. The information is saved to the specified file.
6. Close the form.
Procedure 1124 To delete a device from the managed network
Warning Deleting a device results in a loss of management data and completely removes the device
from the managed network. See section 11.1 for more information.
If you use the 5670 RAM to process 5620 SAM statistics, deleting an NE results in the loss of all
historical 5670 RAM AA statistics for the NE.
2. Click on the Managed State tab and select a device.
3. If the device is managed, click Unmanage and wait for the state to change to Unmanaged. Otherwise, go to
step 4.
4. Click Delete.
5. Save your changes and close the form. The device is deleted from the 5620 SAM database.
4. 12 — Device CLI sessions
12.1 Device CLI sessions overview
12.2 Workflow to use a 5620 SAM CLI
12.3 CLI procedures
12.1 Device CLI sessions overview
You can perform most NE management functions using the 5620 SAM client GUI. Functions such as the following,
however, require CLI access to a managed NE:
validating GUI configuration actions
configuring items that the GUI cannot, such as LI user access
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 87/269
06.07.2017 Device management
troubleshooting using device debug files
The 5620 SAM client GUI provides CLI access to the managed NEs from the main menu and from NE contextual
menus in topology maps and navigation trees.
Note When you use a CLI to change security parameters on an NE, the changes may not be
synchronized with the 5620 SAM and subsequently not displayed in the GUI. For security reasons, the
5620 SAM cannot retrieve parameters such as passwords from an NE. To ensure that the security
parameters are synchronized, you must use the client GUI to change the values.
Scope of command roles and user permissions on the cli package control CLI command access on an NE. The user
permissions are set when security is configured on the NE locally or by using 5620 SAM configuration forms. See
“NE user and device security” in the 5620 SAM System Administrator Guide for information about setting NE access
privileges.
vi editor support
On a 7450 ESS, 7710 SR, 7750 SR, or 7950 XRS, you can use the vi editor to modify local files. For example, after
you use the 5620 SAM Scripts tool to create a CLI script, you can use a 5620 SAM CLI session to monitor the script
execution on an NE, and then use the vi editor to modify the script. The vi editor is available in 5620 SAM Telnet and
SSH sessions. The vi editor supports the standard vi navigation keys as well as the cursor keys (which are often
called the arrow keys). See the appropriate device documentation for information about the supported vi commands
and functions for a specific device.
See the appropriate device documentation for information about the device CLI command structure and usage. See
“Script management” in the 5620 SAM Scripts and Templates Developer Guide for more information about using the
5620 SAM Scripts tool to create CLI scripts.
12.2 Workflow to use a 5620 SAM CLI
The following workflow describes the sequence of highlevel tasks required to open and use a device CLI from the
5620 SAM client GUI. The following must be true before you can use the 5620 SAM to open a device CLI using the
GUI.
The 5620 SAM user account has console access privileges on the managed devices. See “NE user and
device security” in the 5620 SAM System Administrator Guide for more information about user account
privileges.
The Telnet server on the managed devices is started.
If required, SSH2 is properly configured on the managed devices; see chapter 11 for more information.
1. Configure the 5620 SAM CLI preferences. See Procedure 121 for more information.
2. Open a CLI session and log in to a managed device. See Procedure 122 for more information.
3. Configure the device, view device information, and modify files, as required.
4. Close the CLI session. See Procedure 121 for more information.
12.3 CLI procedures
The following procedures describe how to open CLI sessions using the 5620 SAM and configure the CLI console
preferences.
Procedure 121 To configure the 5620 SAM CLI console preferences
Perform this procedure to customize the 5620 SAM CLI window settings, such as the following:
the console text style and appearance
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 88/269
06.07.2017 Device management
the size of the scrolling buffer
whether to save the session output to a file
1. Open a CLI session, as described in Procedure 122.
2. Rightclick in the CLI window and choose Configure. The Terminal Configuration form opens.
3. Configure the required parameters.
Note When the Send Console To a File parameter is enabled and the Append to file parameter
is disabled, the log file is overwritten each time a new CLI session starts.
4. Click OK. The Terminal Configuration form closes.
Procedure 122 To open and close a 5620 SAM device CLI session
Perform this procedure to open a Telnet or SSH session on a managed device using the 5620 SAM client GUI.
1. Perform one of the following to open a device CLI session.
a. Use the 5620 SAM navigation tree.
i. Choose Equipment from the view selector.
Note 1 The managed device must be configured for Telnet access. See the
appropriate device documentation for information about configuring Telnet access
to the device.
Note 2 SSH sessions use SSH2 by default on the 7210 SAS, 7450 ESS, 7750
SR, 7950 XRS, and GNEs. Ensure that SSH2 is properly configured on the
device and that an SSH2 mediation policy is specified in the device discovery
rule. See chapter 11 for more information about configuring SSH2 security.
b. Use the 5620 SAM main menu.
i. Choose one of the following main menu options:
Tools Network Elements NE Sessions Telnet Session
ii. Perform one of the following to specify an NE as the CLI session target.
Enter the management IP address of the NE beside the dimmed Connect button.
Select an IP address from the dropdown menu.
Click Select to search for the NE.
The Connect button is enabled.
iii. Click Connect.
c. Use the Manage Equipment form.
i. Choose Manage Equipment Equipment from the 5620 SAM main menu. The Manage
Equipment form opens.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 89/269
06.07.2017 Device management
ii. Configure the filter criteria and click Search.
iii. Select an NE in the list.
iv. Click NE Sessions and choose Telnet Session or SSH Session. The Telnet Session or SSH
Session window opens.
d. Use a service topology map.
i. Choose one of the following from the 5620 SAM main menu:
Manage Service Services
ii. Choose a port and click Topology View. The Service Topology map opens.
3. Perform NE management tasks, as required.
4. Click Disconnect to end the CLI session.
Note When you disconnect from a CLI session, the session window remains open to facilitate
the opening of a subsequent CLI session.
5. Perform one of the following.
a. Open a new CLI session; perform the following steps.
i. Perform one of the following to specify an NE as the CLI session target.
Enter the management IP address of an NE beside the dimmed Connect button.
Select an IP address from the dropdown menu.
Click Select to search for an NE.
The Connect button is enabled.
ii. Click Connect.
b. Close the Telnet Session or SSH Session window.
5. 13 — Working with network objects
13.1 Working with network objects overview
13.2 Working with equipment group objects
13.3 Working with physical links
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 90/269
06.07.2017 Device management
13.4 Workflow to manage network objects
13.5 Working with network objects procedures
13.1 Working with network objects overview
The 5620 SAM is used to create, configure, and manage a device with the various children objects required to be part
of a network. Equipment such as the routers, which are at the top of the hierarchy, have properties that are
configured using the CLI and discovered when the 5620 SAM discovery process is run. After the device is
discovered, it is displayed as an object in the navigation tree. See chapter 5 for more information about the navigation
tree.
Objects in the 5620 SAM are considered to have parent/child relationships that are contained within a hierarchy. For
example, a card in a card slot is the parent object of a daughter card. The behavior of each object is defined using
parameters that are specific to the function required. Those parameters can be managed to suit the needs of the
service required. Objects are created and managed using the properties forms found in the contextual menus of the
equipment view.
The network is the top object in the navigation tree. The network icon in the navigation tree is the parent object of all
managed devices. When you expand the network icon, all managed devices are shown as children of the network
parent.
The device object is the discovered device at the top of the hierarchy in the navigation tree, directly below the
network icon. The following children objects of the router are created automatically in the navigation tree after the
device is discovered.
CCAG Card Slot
ISATunnel Group Card Slot A for the CPM and switch fabric
ISAAA Group Card Slot B for the redundant CPM and switch fabric
ISALNS Group Fans
ISANAT Group Power Supplies
ISAVideo Group CCM
LAG SFM Slot
IGH
Shelf
The following objects must be created using property forms or create forms from the contextual menus of the
equipment view or the ring group view.
equipment groups
individual CCAGs with VSMCCA members
individual ISATunnel Groups with ISA IPsec MDA members
individual ISAAA Groups with ISAAA MDA members and ISAAA partitions
individual ISALNS Groups with ISA broadband applications MDA members
individual ISANAT Groups with ISA broadband applications MDA members
individual ISAVideo Groups with ISAVideo MDA members
individual LAGs with subgroups of LAG member ports
IGH members
cards
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 91/269
06.07.2017 Device management
ring groups
daughter cards
Ports are automatically created when the daughter card is created.
channels
For information about ISAMG groups, see the 5620 SAM LTE EPC User Guide.
Configuring an object is accomplished in two steps. First the object must exist or be created, second, the object
parameters are modified. See Procedure 141 to create objects using the navigation tree.
Object deployment status
When you configure an object using the 5620 SAM GUI or the 5620 SAM OSS, the 5620 SAM saves the
configuration and attempts to deploy the changes to the network. Although the value is changed on the configuration
forms, the configuration change may not be fully deployed to the NE.
The 5620 SAM allows you to monitor the deployment state for objects. The Deployment tab on all object properties
forms notifies you of configuration changes that are not fully deployed to the NE. The parameter that was
unsuccessfully deployed is listed, along with the old value and the new value. A deployment icon or warning indicator
appears in the following locations when you change the configuration of an object:
beside all of the parameters on an object properties form for which a deployment is in progress (yellow icon) or
has failed (red icon)
beside the object in the navigation tree (blue icon, regardless of state)
in info tables in map views (blue icon, regardless of state)
in the Deployment column on object list forms (blue icon, regardless of state)
on the Deployment tab (warning indicator)
See chapter 26 for information about how to configure a deployment policy, manage deployments, and troubleshoot
failed deployments. See Procedure 131 for information about how to monitor the deployment of an object
configuration change.
13.2 Working with equipment group objects
The equipment group icons in the navigation tree represent logical equipment groups. Initially, an equipment group
object is created by choosing Create Equipment Group from the 5620 SAM main menu. A Group (Create) form
opens. Additional equipment groups can be created using the Copy button on the equipment group properties form.
The Discovered NEs and the Unmanaged NEs equipment groups are created by default. The Discovered NEs
equipment group contains the discovered devices. The Unmanaged NEs equipment group contains unmanaged NEs
that have been added to the network. You can create new equipment groups and move devices to them using the
topology maps.
Note For existing topologies, the unmanaged NE will not be automatically moved to the Unmanaged
NEs equipment group in the following situations:
existing unmanaged NEs
managed NEs that are unmanaged
Although there is no limit to the number of equipment groups, AlcatelLucent recommends a maximum of 10 000
equipment groups per system for optimal performance. Each equipment group can contain a maximum of 2000
objects. Network elements and immediate child groups are considered objects in an equipment group. A bracketed
number is displayed beside the name of each equipment group in the navigation tree. This number indicates the
current number of objects in the group.
See chapter 6 for information about configuring equipment group objects and managing equipment groups using
maps.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 92/269
06.07.2017 Device management
13.3 Working with physical links
The 5620 SAM allows you to create and manage links at the Layer 1 level. The physical links represent the actual
physical configuration of network connections between ports. You can view and manage physical links from the
physical topology map and the Manage Equipment list form.
Although there is no limit to the number of physical links you can have in a system, AlcatelLucent recommends a
maximum of 10 000 physical links for optimal system performance.
Radio links between 9500 MPRs are shown as physical links by the 5620 SAM, with ports as the endpoint type.
See chapter 6 for information about configuring physical links and managing physical links using maps.
13.4 Workflow to manage network objects
The following workflow describes the sequence of highlevel tasks required to manage and configure network objects.
This workflow assumes that the physical devices have been installed, commissioned, and discovered. See chapter
10 for more information about device commissioning. See chapter 11 for more information about device discovery.
Note Network objects can be accessed using the equipment navigation tree. See chapter 5 for more
information.
1. Create network equipment groups as required; see chapter 6.
2. Configure device objects as required; see chapter 14.
3. Configure logical group objects as required; see chapter 15.
4. Configure shelf, card, and daughter card objects as required; see chapter 16.
5. Configure port and channel objects as required; see chapter 17.
6. Create physical links as required; see chapter 6.
7. Monitor the deployment status of network objects as required; see Procedure 131.
8. View the current network resources assigned to network objects such as IP or MAC addresses as required;
see Procedure 132.
13.5 Working with network objects procedures
Use the following procedure to work with network objects.
Procedure 131 To monitor the deployment status of a network object
1. Open the properties form for the network object.
You can click on the Deployment tab if a warning indicator appears when you open a properties form.
2. Configure the required parameters and click Apply. An icon appears beside the modified parameter:
yellow icon—deployment in progress; the icon disappears when the deployment succeeds
red icon—failed deployment
In addition, a blue deployment icon appears beside the NE object in the navigation tree, in list forms, and in
configured info tables in map views.
A warning indicator appears on the Deployment tab.
3. Click on the Deployment tab.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 93/269
06.07.2017 Device management
4. In the Name column, verify the name of the parameter for which the deployment was unsuccessful. You can
also verify the old value of the parameter before the change was applied, the new parameter value, and the
deployer ID.
5. Navigate to the parameter on the configuration form that failed to deploy, if necessary, by selecting an entry in
the Attributes list and clicking Show Attribute. The attribute is highlighted for a few seconds on the
configuration form.
Note If you choose an entry in the Attributes list that is located on a hidden tab and click
Show Attribute, the hidden tab is temporarily displayed. See Procedure 317 on how to configure
hidden tabs.
6. Troubleshoot the cause of the failed deployment;see Procedure 262.
Procedure 132 To view network resources assigned to network objects
Perform this procedure as required, to view the following network resources assigned to network objects:
duplicate IP addresses
duplicate segment routing SIDs
IP addresses
L2TPv3 tunnels with unknown destinations
MAC addresses
route distinguishers and route targets
segment routing SIDs
1. Choose Tools Network Resources Network Resources from the 5620 SAM main menu. The Network
resources form opens.
2. Select the appropriate tab for the network resource you need to query.
3. Customize the search fields as required to view the chosen network resource assigned to the network objects.
Caution This operation may take a long time to complete for some network resources such as
viewing IP addresses, route distinguishers and route targets, and MAC addresses. ALU
recommends that you use a specific search filter to narrow down the scope of search.
4. Click Search. For some search queries, for example IP addresses, a dialog box appears.
5. If required, acknowledge the dialog box and click Search. The results of your customized search are
displayed.
6. Close the form.
6. 14 — Device object configuration
14.1 Device object configuration overview
14.2 Working with device objects
14.3 Working with ring group objects
14.4 Workflow to manage device objects
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 94/269
06.07.2017 Device management
14.5 General device configuration procedures
14.6 Ring group configuration procedures
14.1 Device object configuration overview
The device object is the discovered device at the top of the hierarchy in the navigation tree, directly below the
network icon.
This chapter contains the procedures to configure device objects using the navigation tree. Device object properties
forms, which are used to configure specific parameters for discovered devices, are accessed using objects on the
5620 SAM navigation tree. See chapter 5 for more information about using the navigation tree.
14.2 Working with device objects
The device icons in the navigation tree represent device objects. See chapter 9 for more information about the
supported device types.
Most of the configured properties for this object are inherited from the device. The Properties contextual menu option
from the navigation tree allows you to configure or modify the parameters for the object. See the specific procedures
in this chapter for the respective tab of the properties form that is to used to configure the device object.
14.3 Working with ring group objects
The 5620 SAM allows you to create and manage ring groups in the ring group view of the navigation tree. Ring
groups are used to group devices logically to represent a typical network topology.
Note The 5620 SAM uses VLAN groups instead of ring groups to group OmniSwitch NEs. See
chapter 74 for more information about VLAN groups.
In the ring group view of the navigation tree, the network icon provides the contextual menu option Create Ring Group
to create ring group icons. Using the properties form of a ring group, you can group devices logically in the ring group.
Figure 141 shows a sample navigation tree ring group view.
Figure 141 Sample navigation tree ring group view
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 95/269
06.07.2017 Device management
14.4 Workflow to manage device objects
The following workflow describes the sequence of highlevel tasks required to manage and configure device objects.
This workflow assumes that the physical devices have been installed, commissioned, and discovered. See chapter
10 for more information about device commissioning. See chapter 11 for more information about device discovery.
Note Device objects can be accessed using the equipment navigation tree. See chapter 5 for more
information about using the equipment navigation tree.
1. As required, configure the following general NE capabilities:
a. Create an object; see Procedure 141.
b. Modify an NE configuration; see Procedure 142.
c. Customize the NE property labels and values in the System preferences form, for example, to specify
the location and site name that differs from the actual NE site name. See the 5620 SAM System
Administrator Guide for more information about configuring system preferences.
d. Customize the NE property values in the NE form; see Procedure 143.
e. Create an operational group; see Procedures 145 and 146.
f. Enable and configure global cflowd on an NE, and create cflowd collectors; see Procedure 147.
g. Associate a span of control with an NE; see Procedure 149.
h. Configure load balancing on an NE; see Procedure 1410.
i. Configure 802.1x authentication on an NE; see Procedure 1411.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 96/269
06.07.2017 Device management
j. Enable or disable an exclusive policy editing restriction on one or more NEs or remove any exclusive
edit locks that were previously set; see Procedure 1412.
k. Configure active card alarms on an NE; see Procedure 1413.
l. Configure a TWAMP server on an NE; see Procedure 1414.
m. Enable LLDP on an NE; see Procedure 1415.
n. Configure BFD flap detection on an NE; see Procedure 1416.
o. Enable a Q in Q untagged SAP on an NE; see Procedure 1417.
p. Configure the DHCPv6 advertise message format on an NE; see Procedure 1418.
q. Configure Python script protection on an NE; see Procedure 1419.
r. Configure SFLOW on an NE; see Procedure 1420.
s. Create a chassislevel PBB configuration; see Procedure 1421.
t. Configure serving network information; see Procedure 1422.
u. Configure the RADIUS CoA port on an NE; see Procedure 1425.
v. Configure data persistence on an NE; see Procedure 1426.
w. Configure DNS security extensions on an NE; see Procedure 1427.
x. Configure the use of vendorspecific ICMP extensions on an NE; see Procedure 1428.
2. As required, configure the following functionality on 7210 SAS NEs:
a. Configure operational groups for fault propagation on a 7210 SAS; see Procedure 146.
b. Configure a noservice loopback port on a 7210 SAS; see Procedure 1429.
c. Configure two WRED slopes on a 7210 SAS; see Procedure 1431.
d. Enable framebased accounting on a 7210 SAS; see Procedure 1432.
e. Configure the system resource profile on a 7210 SAS; see Procedure 1433.
f. Configure a system resource profile policy for 7210 SASR NEs; see Procedure 1434.
g. Configure portbased access egress scheduling on the 7210 SASR; see Procedure 1435.
h. Configure buffer management for the 7210 SAS; see Procedure 1436.
3. As required, configure the following functionality on 7705 SAR NEs:
a. Configure the watermark settings on a 7705 SAR; see Procedure 1437.
b. Configure the QoS ingress aggregate rates on a 7705 SARM; see Procedure 1438.
c. Launch an MCT from a 9500 MPR NE connected to a 7705 SAR; see Procedure 1439.
4. As required, configure the following functionality on OmniSwitch NEs:
a. Start and stop a Webview or Secure Webview session on an OmniSwitch; see Procedure 1440.
b. Configure the dying gasp alarm on an OmniSwitch; see Procedure 1441.
5. As required, configure ring group objects; see Procedures 1442 and 1443.
14.5 General device configuration procedures
Use the following procedures to configure devices using the navigation tree.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 97/269
06.07.2017 Device management
Procedure 141 To create an object
1. On the equipment tree, rightclick on an empty object and choose Properties, or, when available, Create
<objectname>. The properties form or the create form, as applicable, opens.
2. Configure the required parameters.
Certain object parameters are available for configuration. Configuring these parameters creates the object,
however, after the object is created you may need to edit it using properties forms.
3. Save your changes and close the form.
Procedure 142 To modify NE properties
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Use the form to view or modify the NE parameters, as required.
3. Save your changes and close the form.
Procedure 143 To configure NE custom properties
1. On the equipment or routing tree, rightclick on an NE. The Network Element (Edit) form opens.
2. In the Custom Properties panel, configure the userdefined values.
Note 1 The NE custom properties support the extended character set including multibyte
characters.
Note 2 The configured labels and values are displayed in the following locations. You can
configure the labels and values, if required.
NE list form: Choose Manage Equipment Equipment Network Element (from the
object dropdown menu). The appropriate columns display the values and labels.
Tree labels: See Procedure 47.
Topology labels: See Procedure 48.
Info Table: See Procedure 614.
Alarms: See Procedure 3814.
Note 3 You can also configure Custom NE property values using the 5620 SAMO. See the
5620 SAMO XML Reference.
Note 4 The 5620 SAM GUI supports localized language display. See chapter 3 for more
information.
3. Save your changes and close the form.
Procedure 144 To enable FIPS1402
Perform this procedure to enable FIPS1402 level 1 support.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 98/269
06.07.2017 Device management
The 5620 SAM returns an SNMP deployment error from the NE for operations that are not supported because of
FIPS restrictions.
Consider the following when you enable FIPS1402:
the following algorithms are not accessible for keychains:
MD5
HMACMD5
DES
the following algorithms are not available:
MD5
DES
1. On the equipment or routing tree, rightclick on an NE. The Network Element (Edit) form opens.
2. Enable the Enable FIPS1402 parameter.
3. Save your changes and close the form.
4. Reboot the NE.
Procedure 145 To create an operational group
Multiple objects can be bundled in operational groups. If you change the status of the operational group, the status of
every object in the group is changed.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Globals tab, and then the Service tab.
3. Click on the Operational Groups tab and then click Create. The Operational Group (Create) form opens.
4. Configure the required parameters.
5. Bind a BFD interface to the operational group.
i. In the BFD Interface Monitored panel, click Create. The Operational Group BFD Interface (Create) form
opens.
ii. Configure the Interface Type parameter.
iii. For service interfaces, click Select in the Service panel. For network interfaces, click Select beside the
Interface Name parameter.
iv. Choose a service or interface from the displayed list and click OK.
v. Configure the Destination Address parameter.
6. Save your changes and close the forms.
Procedure 146 To configure a 7210 SAS operational group
You can create operational groups for VLANs on supported 7210 SAS NEs. Operational groups provide fault
propagation for ports with null, dot1q, and QinQ encapsulation types.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 99/269
06.07.2017 Device management
You can assign an L2 uplink port to an operational group. Access ports on the same device can monitor the group.
When the L2 uplink port goes down or loses connectivity, the access ports monitoring the group go operationally
down. SAPS associated with the affected ports also switch to operationally down.
Perform this procedure to create or modify an operational group. To associate ports with the group, see Procedure 17
1.
1. In the equipment view of the navigation tree, rightclick on a 7210 SAS NE and choose Properties. The
properties form for the NE opens.
2. Click on the Globals tab, then on the Oper Group tab.
3. Click Create, or choose an operational group and click Properties.
4. Configure the required parameters.
You cannot modify the Displayed Name of an operational group after creation.
5. For existing operational groups, click on the Monitor Oper Group Ports tab to view a list of the ports that are
monitoring the group.
6. Save your changes and close the form.
Procedure 147 To enable and configure global cflowd sampling on an NE
Cflowd collects statistical data based on traffic flows. A flow is a series of packets in a user session. Cflowd data is
used to monitor network usage trends and detect security threats. You can use the 5620 SAM to configure cflowd
sampling for:
global traffic that passes through an NE; you must enable cflowd globally on an NE before you can configure
cflowd collectors. You can create multiple cflowd collectors on an NE. Each collector is deleted if cflowd
sampling is disabled.
traffic that passed through an ISAAA group and/or partitions within the group as well as TCP performance
data collection for AA applications and application groups; see Procedure 156.
unicast and multicast traffic on a routing network interface, IES/VPRN L3 access interface, IES/VPRN tunnel
interface, and VPRN network interface; see Procedures 2810, 3611, 7625, 7769, or 7728.
traffic that is redirected to cflowd using an ACL IP filter policy; see Procedure 502.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the CFLOWD tab.
3. Set the CFLOWD State parameter to Enabled.
4. Configure the required parameters in the CFLOWD Attributes panel.
5. Add a collector.
Note A global NE cflowd configuration can contain up to five collectors.
i. Click on the Collector tab and click Create. The Cflowd Collector Configuration (Create) form opens.
ii. Configure the required parameters.
The Aggregation Type parameter is configurable when the Version parameter is set to version8.
The Autonomous System parameter is configurable when the Version parameter is set to version5 or
version8.
The Template Type parameter is configurable when the Version parameter is set to version9.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 100/269
06.07.2017 Device management
iii. Save your changes and close the form.
6. Save your changes and close the form.
Procedure 148 To enable the automatic selection of an RD on an NE
Since an RD must be unique on each PE in the network, you can allocate either a route distinguisher that you
manually select or an NEselected route distinguisher for each service. When you configure an autoRD on an NE, a
Type1 RD is automatically allocated by the NE based on the community range that you configure.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Globals tab, and then the Service tab.
3. Click on the BGP Groups tab and configure the Enable Auto Route Distinguisher parameter.
4. Configure the IP Address parameter in the Auto RD panel.
5. Configure the parameters in the Community Range panel.
6. Save your changes and close the forms.
Procedure 149 To add a span of control to an NE
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Spans tab and click Add. The Select Span(s) Network Element form opens with a list of
available spans.
3. Choose one or more spans to apply to the NE.
4. Save your changes and close the forms.
Procedure 1410 To configure load balancing
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Globals tab. The Load Balancing tab is displayed.
3. Configure the required load balancing parameters.
To enable systemwide enhanced multicast load balancing to send multicast traffic over a LAG, set the
Multicast Enhanced Load Balancing parameter to true.
To improve the LAG spraying of VLL service packets when ECMP and LAG hashing are performed by the
same NE, set the Service ID Lag Hashing parameter to true.
4. Save your changes and close the form.
Procedure 1411 To enable or disable 802.1X
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 101/269
06.07.2017 Device management
Note Before you can create an 802.1X policy, 802.1X must be enabled on the NE. Before you can
configure 802.1X on an Ethernet access port, 802.1X must be enabled on the NE and an 802.1X policy
must be created and distributed to the NE.
To create and distribute 802.1X policies to the NEs that use 802.1X, see chapter 58.
To configure 802.1X on Ethernet access ports, see Procedure 171 in chapter 17.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Globals tab.
3. Click on the PAE tab and set the Administrative State parameter to Up.
To disable 802.1X on a managed NE, set the Administrative State to Down.
4. Save your changes and close the form.
Procedure 1412 To configure an exclusive policy editing restriction on an NE
You can enable or disable an exclusive policy editing restriction on one or more NEs. When enabled, this prevents
any local policy definitions that reside on the NE from being changed by a global policy update. You can also remove
any exclusive edit locks that were previously set for the selected NE(s).
Note 1 This procedure can only be performed by admin users or users with an assigned policy
management scope of command role.
Note 2 This functionality is not supported on all devices.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
Note You can perform this procedure on multiple NEs if needed. Select the required NEs from
the navigation tree, rightclick on any one of them, and then select Properties.
2. Click on the Globals tab. The Load Balancing tab is displayed.
3. Click on the Exclusive Edit tab.
4. Perform one of the following:
a. Configure the Use Exclusive Edit parameter to enable or disable an exclusive policy editing restriction
for the selected NE(s).
b. Click Reset Exclusive Edit and click Yes to remove any exclusive edit locks that were previously set
for the selected NE(s).
Note The Reset Exclusive Edit option is also available in global routing policies under
the Local Definitions tab.
5. Save your changes and close the form.
Procedure 1413 To configure active card alarms on an NE
You can configure a 7450 ESS, 7710 SR, 7750 SR, or 7950 XRS to view NE alarms through the CLI.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 102/269
06.07.2017 Device management
2. Click on the Globals tab. The Load Balancing tab is displayed.
3. Click on the Alarm Management tab and configure the required parameters.
4. Save your changes and close the form.
Procedure 1414 To configure a TWAMP server
You can enable or disable TwoWay Active Measurement Protocol on a server and view session and connection
statistics.
Note You cannot configure a TWAMP server after an NE upgrade until the NE is fully
resynchronized.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Globals tab. The Load Balancing tab is displayed.
3. Click on the OAM tab and scroll to the OAM TWAMP panel.
4. Configure the Administrative Status parameter.
Note 1 To make changes to TWAMP server parameters, the Administrative Status parameter
must be set to Disabled.
Note 2 If you are configuring a 7705 SAR, Release 6.1 R5 or later, you can modify the
TWAMP prefix Description parameter when the Administrative Status parameter is set to
Enabled.
5. Configure the required parameters in the Server Configuration panel.
6. If you are configuring a 7705 SAR, the Reflector Configuration panel is displayed.
Expand the Reflector Configuration panel and configure the Reflector Test Session Timeout (Seconds)
parameter.
7. Click on the Prefix tab.
8. Perform one of the following:
a. Click Create to add a new prefix. The Prefix TWAMP Server (Create) form opens, with the General tab
displayed.
Note The 5620 SAM allows you to create an unlimited number of prefixes. However, an
NE can only accept a maximum of 100 prefixes. If more than 100 prefixes are created in
the 5620 SAM, the affected NE will issue a deployment error.
b. Select an existing prefix and click Properties. The Prefix TWAMP Server (Edit) form opens, with the
General tab displayed.
9. Configure the required parameters.
10. Click on the Statistics tab.
11. Select either Srv Conns Stats (Assurance) or Prefix Srv Stats (Assurance), as required, from the Select
Object Type dropdown menu.
12. Select either Past 4 Hour(s) or No Filter, as required, from the filter selector.
13. Click Statistics Policies and select Statistics Policy from the menu. The Statistics Policy form opens, with the
General tab displayed.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 103/269
06.07.2017 Device management
14. Configure the required parameters.
15. Click on the Thresholds tab.
16. Perform one of the following, depending on your selection in step 11.
a. Configure the Prefix Srv Stats (Assurance) threshold parameters.
b. Configure the Srv Conns Stats (Assurance) threshold parameters.
17. Save your changes and close the forms.
18. To view TWAMP statistics on a server:
i. Perform steps 1 to 3 of this procedure.
ii. Click on the Prefix tab.
iii. Select either Srv Conns Stats (Assurance) or Prefix Srv Stats (Assurance), as required, from the
Select Object Type dropdown menu.
iv. Select either Past 4 Hour(s) or No Filter, as required, from the filter selector.
v. Click Collect or Collect All. The system compiles the statistics and displays the available records in
the table.
Note The objects listed in the table control the behavior of the TWAMP connections
that match the defined IP prefix.
vi. Select the required record from the table and click Properties. The Statistics Record is displayed.
vii. Save your changes and close the forms.
Procedure 1415 To enable LLDP on an NE
LLDP is a not a routing protocol, but instead, a neighbordiscovery protocol that allows an NE to advertise its identity
and capabilities to other NEs attached to the same physical IEEE 802.1 LAN. As such, it is configured in a different
manner than standard routing protocols.
LLDP also permits information that the devices discovers about peer devices to be stored. LLDP is only applicable
for devices using Ethernet connectivity. To enable LLDP, you must configure the protocol at both the system level
and at the port level. This is done using the 5620 SAM equipment navigation tree.
When LLDP is enabled on a device, it sends and receives LLDP messages on all of the physical interfaces that are
enabled for LLDP transmission. These messages are sent periodically to ensure that information is accurate. These
messages are stored on the local device for a configurable amount of time, and after this time has expired, the
information is discarded.
The 5620 SAM uses the information stored in the applicable LLDP tables on the node to automatically discover the
physical topology in the network. You can use this information to examine the L1/L2 topology and perform appropriate
diagnostics and troubleshooting.
In LLDP, a single LLDP Protocol Data Unit is transmitted in a single Ethernet frame. The basic LLDP PDU consists
of a header, followed by a variable number of information elements known as TLVs that each include fields for Type,
Length, and Value. Type identifies what kind of information is being sent. Length indicates the length of the
information string. Value is the actual information sent. Each LLDP PDU includes three mandatory TLVs followed by
optional TLVs.
Mandatory TLVs include:
Chassis ID: represents the identification of the device transmitting the LLDP frame
Port ID: represents the identification of the port transmitting the LLDP frame
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 104/269
06.07.2017 Device management
TTL: represents the length of time the receive frame shall be valid
Optional TLVs include:
Port Description: represents the description of the port
System Name: this is the administrativelyassigned name of the device
System Description: this is a textual description of the device
System Capabilities: this identifies the capabilities of the device and its function (such as router, switch,
repeater, etc.)
LLDP also supports multiple transmission scopes. The destination MAC address in the LLDP PDU determines how a
frame is propagated through the network, thereby determining the LLDP message scope. Table 141 identifies a set
of destination MAC address and describes the different transmission scopes associated with each address. This
information is also presented graphically in Figure 142.
Table 141 MAC Addresses and transmission scopes
Name Value Purpose
Nearest Bridge 0180C2 Propagation constrained to a single physical link
00000E
Nearest non 0180C2 Propagation constrained by all bridges other than TPMR; intended for
TPMR bridge 000003 use within provider bridged networks
Nearest 0180C2 Propagation constrained by customer bridges
Customer 000000
Bridge
Figure 142 LLDP Multiple Transmission Scopes
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Enable LLDP.
i. Click on the Globals tab and then on the LLDP tab.
ii. Configure the required parameters.
3. Save your changes and close the forms. See Table 142 for additional procedures related to LLDP information.
Table 142 LLDP related tasks
Task See
Use the physical topology map to view and edit various LLDP parameters and Procedure
interconnections. The physical topology map displays the topology based on the 638
nearestbridge LLDP scope. You can modify the map display to highlight the
nearest nonTPMR links or the nearest customer links. After the physical topology
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 105/269
06.07.2017 Device management
of a network has been discovered, you can create a reference checkpoint which is
basically a snapshot of the topology at a specific time. Any subsequent deviations
from this checkpoint can then be displayed.
Configure LLDP on 7450 ESS or 7750 SR ports to send the ifDesc value in place of Procedure
the ifAlias value over port TLV. Additionally, IPv6 addresses can be configured on 171
the Transmit MGMT Address tab.
Configuring LLDP on OmniSwitch Ethernet ports. Procedure
1724
Procedure 1416 To configure the BFD flap detection interval on an NE
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Globals tab, then on the BFD tab.
3. Configure the Operational State Transition Interval (seconds) parameter.
4. Save your changes and close the form.
Procedure 1417 To enable a Q in Q untagged SAP on an NE
Note The Enable Q in Q Untagged Sap parameter is not supported on the 7950 XRS as it is enabled
by default.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Globals tab, then on the Ethernet tab.
3. Enable the Enable Q in Q Untagged Sap parameter.
When you enable the Enable Q in Q Untagged Sap parameter, the 5620 SAM allows the creation of the
following two default SAP types:
The SAP type *.null functions as a default SAP for singletagged frames on a Q in Q port. This SAP
accepts single tags in the range 0 to 4095 as well as untagged traffic.
The SAP type *.* functions as a default SAP for doubletagged frames in a Q on Q port. This SAP
accepts untagged, singletagged, and doubletagged frames with tags in the range 0 to 4095.
4. Save your changes and close the form.
Procedure 1418 To configure DHCPv6 Advertise messages on an NE
Complete this procedure to specify which DHCPv6 client applications on an NE are sent NO_ADDRS_AVAILABLE
messages when the server runs out of addresses.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Globals tab, then on the Subscriber Management tab.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 106/269
06.07.2017 Device management
3. On the DHCPv6 panel, specify one or more DHCPv6 Advertise message format options for the Advertise
Message parameter, and configure other required parameters if available.
4. Save your changes and close the form.
Procedure 1419 To configure Python script protection on an NE
Complete this procedure to configure an NE with a protection key, shared with a Python script policy, and with
source and destination URLs for a protected Python script. For information on Python script policies, see section
57.1.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Globals tab, then on the Subscriber Management tab.
3. Configure the required parameters on the Python Script Protection panel.
The Protection Key parameter value must match the protection key value of the specified Python script policy.
The two values are validated against each other when Python script protection is enabled.
4. Click on the Protect Script button.
5. Save your changes and close the form.
Procedure 1420 To configure SFLOW on an NE
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the SFLOW tab.
3. Configure SFLOW receivers.
i. Select a receiver in the Receiver tab and click Properties. The Receiver (Edit) form opens.
ii. Configure the required parameters.
iii. Save and close the form.
4. Configure egress counter policers and queues.
i. Click on the Egress Counter Map tab, then on the Policers tab.
ii. Click Create. The SFlow Egress Counter Policer form opens.
iii. Configure the required parameters.
iv. Save and close the form.
v. Click on the Queues tab and then click Create. The SFlow Egress Counter Queue form opens.
vi. Configure the required parameters.
vii. Save your changes and close the form.
5. Configure ingress counter policers and queues.
i. Click on the Ingress Counter Map tab, and then on the Policers tab.
ii. Click Create. The SFlow Ingress Counter Policer form opens.
iii. Configure the required parameters.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 107/269
06.07.2017 Device management
iv. Save and close the form.
v. Click on the Queues tab and then click Create. The SFlow Ingress Counter Queue form opens.
vi. Configure the required parameters.
vii. Save your changes and close the form.
6. Click on the Counter Pollers tab to view counter pollers.
7. Save your changes and close the form.
Procedure 1421 To create a chassislevel PBB configuration
Perform this procedure to provide the PBB MAC name configuration at the NE level.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Globals tab, then on the Service tab.
3. Configure the required parameters.
4. Click on the MAC Name tab and click Create. The PBB MAC Name (Create) form opens.
5. Configure the required parameters.
6. Save your changes and close the form.
Procedure 1422 To configure serving network information on an NE
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Globals tab, then on the Serving Network tab.
3. Configure the required parameters.
4. Save your changes and close the form.
Procedure 1423 To configure L2TP on an NE
Perform this procedure to configure a nonmultichassis tunnel ID range on an NE.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Globals tab, then on the L2TP tab.
3. Configure the Non MC Tunnel ID Range Start and End parameters.
The Non MC Tunnel ID Range Start value must not be greater than the End value.
4. Save your changes and close the form.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 108/269
06.07.2017 Device management
Procedure 1424 To configure WLAN GW redundancy on an NE
Perform this procedure to configure a virtual chassis identifier on an NE for the purpose of failover redundancy in
WLAN GW configurations. You will need to perform this procedure on each NE in the redundancy configuration, with
an identical virtual chassis ID string or dual homing key for each.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Globals tab, then on the WLAN GW Sys Config tab.
3. Configure the Virtual Chassis ID and Max Number of GTP Session Held parameters.
4. Save your changes and close the form.
Procedure 1425 To configure the RADIUS CoA port on an NE
Perform this procedure to configure the RADIUS change of authorization port on an NE.
Note You cannot configure the RADIUS CoA port on the 7950 XRS, Release 11.0 R1 or later.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Globals tab, then on the RADIUS tab.
3. Configure the RADIUS CoA Port parameter.
Note If the routing instance is bound to a RADIUS proxy server and the RADIUS CoA port is
set to 1812, all CoA messages are received by the RADIUS proxy server and dropped by port
1812.
4. Save your change and close the form.
Procedure 1426 To configure data persistence on an NE
Use this procedure to configure data persistence on an NE that allows you to store dynamic object information about
an application in a file on the NE.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the Node Persistence tab.
3. Configure the required parameters on each of the following application panels:
ANCP
Application Assurance
DHCP Server
NAT Port Forwarding
Python Policy Cache
Subscriber Management
Note Configuring the File Location parameter for any of the above applications enables data
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 109/269
06.07.2017 Device management
persistency for that application. Ensure that the specified location has sufficient disk space to
handle the volume of dynamic objects that will persisted on it.
4. Save your changes and close the form.
Procedure 1427 To configure DNS security extensions
The 5620 SAM supports configuring DNS security options on 7450 ESS, 7710 SR, 7750 SR, and 7950 XRS nodes,
Release 12.0 R1 or later.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the DNS tab.
3. Configure the required parameters.
4. Save your changes and close the form.
Procedure 1428 To enable or disable ICMP extensions on a NE
Use this procedure to configure the use of vendorspecific ICMP extensions on the 7950 XRS, 7450 ESS, 7705
SAR, 7710 SR, and 7750 SR NEs. Network operators can use the information provided by the ICMP extensions to
diagnose routing problems. By default, ICMP extensions are disabled on devices.
1. On the equipment tree, rightclick on a NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the ICMP tab.
3. Configure the VendorSpecific ICMP Extensions parameter.
4. Save your changes and close the form.
Procedure 1429 To configure a noservice loopback port on the 7210 SAS
When you configure a port loopback with MAC swap on a 7210 SAS NE, you must configure a noservice port. You
can select a physical port or a virtual port. Not all chassis types support virtual noservice ports.
If you select a physical port as a noservice port, the port cannot contain any SAPs.
For virtual noservice ports, the number of available ports and the port names vary depending on the chassis type.
Virtual ports are not displayed on the navigation tree.
You cannot select the same noservice port for more than one function.
See the NE documentation for more information.
1. On the equipment tree, rightclick on a 7210 SAS NE and choose Properties. The Network Element (Edit) form
opens.
2. Click on the Globals tab, then click on the Service tab.
3. Select a loopback noservice port. Perform one of the following:
a. Select a physical loopback noservice port.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 110/269
06.07.2017 Device management
b. Select a virtual loopback noservice port and configure all other required parameters.
The availability of virtual ports vary depending on the chassis type and card type.
4. Save your changes and close the forms.
Procedure 1430 To configure CFM DMM version 1 interoperability on the 7210
SAS
1. On the equipment tree, rightclick on a 7210 SAS NE and choose Properties. The Network Element (Edit) form
opens.
2. Click on the Globals tab, then click on the CFM tab.
3. Configure the DMM Version 1 Compatibility parameter.
4. Save your changes and close the form.
Procedure 1431 To configure two WRED slopes on a 7210 SAS
The 7210 SASD and 7210 SASM support three WRED slopes per queue:
High priority/inprofile TCP
Low priority/outofprofile TCP
NonTCP
Perform this procedure to specify whether only the high priority and low priority slopes are used, and nonTCP slopes
are ignored. This configuration is supported on the 7210 SASD and 7210 SASM, Release 6.0 R1 or later.
1. On the equipment tree, rightclick on a 7210 SAS NE and choose Properties. The Network Element (Edit) form
opens.
2. Click on the QoS tab.
3. Configure the Use WRED Slopes parameter.
4. Save your changes and close the form.
Procedure 1432 To configure framebased accounting for QoS policies on a
7210 SAS
1. On the equipment tree, rightclick on a 7210 SAS NE and choose Properties. The Network Element (Edit) form
opens.
2. Click on the Frame Based Accounting tab.
3. Configure the required parameters.
4. Save your changes and close the form.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 111/269
06.07.2017 Device management
Procedure 1433 To configure the global system resource profile on a 7210
SAS
Perform this procedure to allocate the system resources on a 7210 SAS. The functional areas for which you can
allocate resources depend on the chassis type. See "System resource profile" in section 9.6, and the NE
documentation for more information about system resource allocation.
For the 7210 SASR, system resources for the G8032 Fast Flood, VPLS Up MEP Resource, and Router functions
are configured on the device properties form using this procedure. Other system resources for the 7210 SASR are
allocated using a policy; see Procedure 1434.
To configure portbased scheduling on the 7210 SASR, see Procedure 1435.
Note System hardware resources are shared. Do not assign more than the available resources.
Functions are disabled if you assign more than the amount of available resources.
1. On the equipment tree, rightclick on a 7210 SAS NE and choose Properties. The Network Element (Edit) form
opens.
2. Click on the Globals tab, then click on the System Resource Profile tab.
3. Configure the required parameters.
Configuration changes for the following parameters do not take effect until the NE is rebooted:
G8032 Fast Flood (Configured)
SAP Aggregate Meter (Configured)
SAP Ingress Queues (Configured)
Max IPv6 Routes (Configured)
Max IP subnets (Configured)
Mbs Pool Type
Port Scheduler Mode (Configured)
The SAP Egress Aggregate Meter parameter is configurable when the Total ACL Resource parameter in the
SAP Egress Internal ACL panel is set to a value of 1 or less.
If you set the SAP Egress Aggregate Meter parameter and then configure egress meters on SAPs, you cannot
reset the parameter to a lower value unless you remove all egress meter configurations for all SAPs on the
NE.
In the SAP Ingress Internal ACL panel, the sum of the values for the IPv4 Resource, IPv4/128bit IPv6
Resource, and 64bit IPv6 Resource parameters must not be greater than the value specified for the Total
ACL Resource parameter.
In the SAP Egress Internal ACL panel, the sum of the values for the MAC Resource, IPv4 Resource, 128bit
IPv6 Resource, and 64bit IPv6 Resource parameters must not be greater than the value specified for the
Total ACL Resource parameter.
In the SAP Ingress QoS Resources panel, the sum of the values for the MAC Resource, IPv4 Resource, and
IPv4/v6 Resource parameters must not be greater than the value specified for the Total QoS Resource
parameter.
The value for the Up MEP Resource parameter must not be greater than the value for the Total CFM
Resource parameter.
For the Max IP Subnets parameter, IPv4 subnets use one entry each and IPv6 subnets use two entries each.
You cannot set the Mbs Pool Type parameter to Node when ports on the NE are decommissioned.
Each 128bit address consumes two entries of the available entry resources.
4. Save your changes and close the form.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 112/269
06.07.2017 Device management
Procedure 1434 To configure a system resource profile policy for the 7210
SASR
System resource profiles for the 7210 SASR are configured using the 5620 SAM policy distribution framework
(except for the G8032 Fast Flood, VPLS Up MEP Resource, and Router functions; see Procedure 1433). See
chapter 48 for more information about 5620 SAM policies. You can configure up to 16 system resource profile policies
and distribute them to 7210 SASR devices. A selected policy is assigned to the card slot of the device; see
Procedure 1636.
To configure portbased scheduling on the 7210 SASR using the system resource profile, see Procedure 1435.
See "System resource profile" in section 9.6 and the NE documentation for more information about system resource
allocation.
1. Choose Policies QoS SROS QoS 7210 System Resource Profile Policy from the 5620 SAM main menu.
The 7210 System Resource Profile Policies form opens.
2. Click Create or choose a policy and click Properties.
3. Configure the required parameters.
When the policy is assigned to a card slot and the SAP Aggregate Meter, BiDirectional MIP Egress, or QoS
Network Ingress parameter is modified, you must reboot the card or the node for the modified value to take
effect.
To enable Primary VLAN for egress MIPs on supporting 7210 SASR NEs, you must allocate resources to the
Bi Directional MIP Egress parameter.
In the SAP Ingress Internal ACL panel, the sum of the values for the MAC Resource, IPv4 Resource, 64bit
IPv6 Resource, and 128bit IPv4/v6 Resource parameters must not be greater than the value specified for the
Total ACL Resource parameter.
In the SAP Egress Internal ACL panel, the sum of the values for the MAC Resource, MAC/IPv4 Resource,
128bit IPv6 Resource, and 64bit MAC/IPv6 Resource parameters must not be greater than the value
specified for the Total ACL Resource parameter.
In the SAP Ingress QoS Resources panel, the sum of the values for the MAC Resource, MAC/IPv4
Resource, and 64bit MAC/IPv4/v6 Resource parameters must not be greater than the value specified for the
Total QoS Resource parameter.
The sum of the values for the Down MEP Resource and Up MEP Resource parameters must not be greater
than the value for the Total CFM Resource parameter.
Each 128bit address consumes two entries of the available entry resources.
4. Save your changes and close the form. See Procedure 481 to distribute the policy to NEs.
Procedure 1435 To configure portbased scheduling on the 7210 SASR
Using the global system resource profile, you can configure access ports on the 7210 SASR to use either portbased
or SAPbased egress scheduling. When portbased scheduling is enabled, the port supports eight egress queues, and
all SAPs on the port share the same set of eight queues.
Queues for portbased scheduling are configured in the 7210 port access egress policy assigned to the port; see
Procedure 494. See section 68.9 for more information about configuring scheduling on the 7210 SASR.
SAPbased egress queues are not available when portbased scheduling is enabled. See the NE documentation for
more information.
1. On the equipment tree, rightclick on the required NE and choose Properties. The Network Element (Edit) form
opens.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 113/269
06.07.2017 Device management
2. Click on the Globals tab, then click on the System Resource Profile tab.
3. Configure the Port Scheduler Mode (Configured) parameter.
Changes to the Port Scheduler Mode (Configured) parameter require a reboot of the NE to take effect. The
Port Scheduler Mode (Active) parameter displays the parameter setting currently in effect on the NE.
4. Save your changes and close the form.
Procedure 1436 To configure buffer management for the 7210 SAS
For the 7210 SASM and 7210 SAST, queue buffer resources are by default allocated equally to all ports on the
device. You can decommission unused ports and assign their buffer resources to other ports. Decommissioned ports
cannot be turned up or used for any function. Configurations deployed to a device with decommissioned ports will not
take effect on the decommissioned ports.
Port decommissioning and buffer resource assignment are configured using profiles. You can configure up to 30 buffer
management profiles per NE. Changes to profile configuration take effect when the NE is rebooted. The status for a
profile indicates whether it is currently active or if it requires a reboot before it takes effect.
For the 7210 SAST, you must configure the system resource profile before you configure buffer management; see
Procedure 1433.
See the NE documentation for more information about buffer management.
1. On the equipment tree, rightclick on a 7210 SAS NE and choose Properties. The Network Element (Edit) form
opens.
2. Click on the Globals tab, then on the Port Decommission tab. A list of buffer management profiles is
displayed.
3. Delete one or more buffer management profiles, if required. Choose the profile and click Delete.
4. Configure a buffer management profile:
i. Click Create or choose a profile and click Properties. The Buffer Management form opens.
ii. Configure the ID and Description parameters.
iii. Click on the From tab, then click Add. The Select form opens.
iv. Select one or more ports to decommission and click OK. The Select form closes.
The selected ports are decommissioned the next time the NE reboots.
v. Click on the To tab, then click Add. The Select form opens.
vi. Select one or more ports and click OK. The Select form closes.
The buffer resources of the decommissioned ports are assigned to the selected ports the next time the
NE reboots.
vii. Save your changes and close the form.
5. Repeat step 4 to create additional profiles. You can create up to 30 profiles.
Note You must reboot the NE for changes to buffer management profiles to take effect. The
status for a profile indicates whether it is currently active or if it requires a reboot in order to take
effect.
Procedure 1437 To configure watermark settings on a 7705 SAR
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 114/269
06.07.2017 Device management
1. On the equipment tree, rightclick on a 7705 SAR NE and choose Properties. The Network Element (Edit)
form opens.
2. Click on the Security tab.
3. Configure the required parameters in the Water Mark Settings (Active Sessions) panel.
4. Save your changes and close the form.
Procedure 1438 To configure QoS ingress aggregate rates on the 7705 SAR
M/ME
Perform this procedure to configure QoS access ingress and network ingress aggregate rates on the 7705 SAR
M/ME.
1. On the equipment tree, rightclick on the 7705 SARM/ME NE and choose Properties. The Network Element
(Edit) form opens.
2. Click on the QoS tab.
3. Configure the Aggregate Rate parameter in the Access Ingress panel and in the Network Ingress panel.
4. Save your changes and close the form.
Procedure 1439 To launch an MCT on a 9500 MPRe NE connected to a 7705
SAR
The 5620 SAM supports an integrated MCT from the port or NE level on the 7705 SAR8 and the 7705 SAR18. The
MCT is distributed with a NEtO client in the 5620 SAM. The MCT can be launched from the port that is associated
with the MW link in the navigation tree or from the MW Link Member (Edit) form. You can configure radio parameters
using the MCT.
Consider the following before you launch the MCT:
Java version 1.6 is required to launch the MCT.
The MCT is only supported on a Windows client; however, it is not supported on Windows 7.
Only one MCT session can be open at a time.
1. On the equipment tree, rightclick on a discovered 7705 SAR8 or 7705 SAR18 NE and choose External
Element Manager.
2. Choose the corresponding MW member from the list and click Launch MCT.
3. Enter your login credentials and click OK. A dialog box appears.
Note If the client system does not have the required MCT packages, the packages are
downloaded from the 5620 SAM and saved in a thirdparty folder.
4. Click Accept. The MCT initialization starts, and the MCT main view screen appears.
Note If the MCT is not installed on the client system, the MCT installer window opens. After
the MCT is installed, the MCT main view screen appears for all subsequent launches, with the
MCT version adjusted to the NE version from which the MCT launched.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 115/269
06.07.2017 Device management
Procedure 1440 To start and stop a Webview or Secure Webview session on
an OmniSwitch
1. Choose one of the following to start a Webview or Secure Webview session:
a. On the equipment tree, rightclick on a discovered OmniSwitch and choose Launch Webview or Launch
Secure Webview. A web browser starts and the Webview or Secure Webview login screen appears.
b. On the equipment tree, rightclick on a discovered OmniSwitch and choose Equipment Window. The
Equipment Window form opens. Select the Launch Webview or Launch Secure Webview button on the
form. A web browser starts and the Webview or Secure Webview login screen appears.
2. Enter your user name and password. After a successful login, the Chassis Management Home Page appears.
3. To stop a Webview or Secure Webview session:
i. Click on the Log Out text at the top of the Webview or Secure Webview window. A Confirm Log Out
dialog box appears.
ii. Click Log Out to end the Webview or Secure Webview session.
See the appropriate OmniSwitch Switch Management Guide for information about configuring and using Webview or
Secure Webview.
Procedure 1441 To configure the dying gasp alarm on an OmniSwitch
You can configure the dying gasp alarm for the following OmniSwitch NEs:
OS 6250M, Release 6.6.3 or later OS 6850E, Release 6.4.5 or later
OS 6250SME (Metro), Release 6.6.3 or later OS 6855, Release 6.4.5 or later
OS 6450 (Metro), Release 6.6.3 or later
Note To view the dying gasp alarm on the 5620 SAM, the OmniSwitch NE must be managed using
SNMP v2 with the community string set to public.
2. Perform step 5 of Procedure 102 to configure the NE to be managed using SNMP v2 with a community string
configured to public.
Note 1 If the Backup/Primary power supply fails, a major alarm will be raised. This alarm will
be sent only to the first two SNMP stations configured on the NE. “Show snmp station” lists the
management station address. SAM ip should be first or second.
Note 2 The "Loopback 0" address should not be used for the source IP address field on the
NE.
14.6 Ring group configuration procedures
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 116/269
06.07.2017 Device management
Use the following procedures to manage ring groups using the navigation tree.
Procedure 1442 To create a ring group
You can use the ring group creation function to:
indicate a VLAN ring topology
indicate a VPLS ring topology
configure the properties of the ring group to provide VLAN Internet, BTV (MVR), and L2 VPN (TLS) services
group devices by geographic region
Consider the following before you create a ring group.
Ensure that the devices are commissioned, as described in chapter 10.
Ensure that mediation policies are configured to allow CLI access to the managed devices, as described in
chapter 11.
If you want specific access interfaces to be part of a VLAN service, ensure that the parent device of the
interface is a member of the ring group.
1. Choose Ring Group from the navigation tree view selector. The navigation tree displays the Ring Group view.
2. Rightclick on the Network object and choose Create Ring Group. The Ring Group (Create) form opens.
3. Configure the required parameters.
4. Click Apply. If you set the Ring Group Type parameter to VPLS in step 3, go to step 6.
5. Click on the TLS tab to configure the TLS parameters. The Ethertype and Jumbo Frame parameters are
configurable when the Enabled parameter is selected.
6. Perform one of the following to add a device to the ring group.
a. To add a device using the current properties form:
i. Click on the Group Members tab click Create. The Select Network Elements form opens.
ii. Choose one or more NEs and click OK. The selected devices are listed on the Ring Group
(Create) form.
iii. Click OK and then click Yes.The device objects are listed in the navigation tree under the new
ring group object.
b. To add a device from the navigation tree:
i. Rightclick on the device object in the Equipment view of the navigation tree and choose Add To
Ring Group. The Select Group form opens to display a list of ring groups.
ii. Choose the new ring group and click OK. The device object is listed under the ring group in the
Ring Group view of the navigation tree.
Note All device types can be added as members of a VLAN ring group. Only devices
that support VPLS can be added to a VPLS ring group.
7. To apply a span of control to a ring group:
i. Click on the Spans tab and click Add. The Select Span(s) Ring Groups form opens with a list of
available spans.
ii. Choose one or more spans of control to apply to the ring group.
iii. Save your changes and close the form.
8. As required, provision VLAN services for the ring group as described in chapter 73.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 117/269
06.07.2017 Device management
Procedure 1443 To remove a device from a ring group or a ring group
1. Choose Ring Group from the navigation tree view selector. The navigation tree displays the Ring Group view.
3. To remove a device from the ring group, rightclick on the device object under the ring group and choose
Remove From Ring Group. The device is removed from the ring group.
4. To remove a ring group:
i. Perform step 3 to remove all devices from the ring group.
ii. Rightclick on the Ring Group object and choose Remove Ring Group.
iii. Save your changes and close the form.
Caution Removing a ring group deletes the VLAN services that are associated with the
ring group.
7. 15 — Logical group object configuration
15.1 Logical group object configuration overview
15.2 Working with CCAG objects
15.3 Working with ISAAA groups
15.4 Working with ISATunnel groups
15.5 Working with ISALNS groups
15.6 Working with ISANAT groups
15.7 Working with ISAVideo groups
15.8 Working with ISAWLAN GW groups
15.9 Working with IGH objects
15.10 Working with LAG objects
15.11 Workflow to manage logical group objects
15.12 Workflow to configure weighted perlink hashing on a LAG
15.13 Logical group object configuration procedures
15.14 LAG configuration procedures
15.1 Logical group object configuration overview
Logical group objects are children of the device object. They appear below the device object in the navigation tree.
The following logical group objects are created automatically in the navigation tree after the device is discovered.
CCAG ISANAT Group
ISAAA Group ISAVideo Group
ISATunnel Group LAG
ISALNS Group IGH
Properties forms for logical group objects are accessed using the 5620 SAM navigation tree.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 118/269
06.07.2017 Device management
This chapter contains the procedures to configure logical group objects using the navigation tree. See chapter 5 for
more information about using the navigation tree.
15.2 Working with CCAG objects
CCAGs are navigation tree objects located below device icons. CCAGs are configured manually using the CCAG
object navigation tree menu and subsequent forms. For proper CCAG configuration, a VSMCCA card must be
present in the NE. In the navigation tree, a VSMCCA card can be opened to show its ports. The ports are indicated
by VSM Port x/y/z, which shows port type and the ID of the port.
You must configure the following in the CCAG configuration forms:
General properties such as CCAG ID, Description, CCA Rate Enabled, CCA Rate, Access Adapt QoS, and
Administrative State
CCAG MDA Members which are compatible ports that can belong to a CCAG.
When you create a CCAG, the 5620 SAM creates virtual paths to be used as interconnections to bind services
together. Two unidirectional paths are created: Alpha and Beta. For each path, three virtual ports are created: one for
SAPSAP connections, one for SAPNET connections, and one for NETSAP connections. The last two virtual ports
are used to bind a service and a network interface together.
A maximum of eight cards can be added to a CCAG, with a maximum of eight CCAGs per NE.
15.3 Working with ISAAA groups
ISAAA groups provide AA load balancing, scaling, and redundancy on NEs that contain multiple ISAAA MDAs.
ISAAA redundancy protects against card failure and minimizes service disruption during maintenance or protocol
signature upgrades.
The 5620 SAM supports AA group configuration on the 7450 ESS, 7750 SR MG, and 7750 SR. An NE can have up
to seven ISAAA groups.
Note A singleslot chassis does not support AA configuration.
ISAAA group configuration requires the following:
group number, which can be set only during group creation
up to seven primary group members and one optional backup member
one or more forwarding classes to divert to the AA group
You can use multiple ISAAA groups to scale the application of AA policies, and can divide an AA group into
partitions that are customized for specific VPN services. Each partition has an AA policy, and supports the
configuration of custom protocols, applications, and application groups. Within a partition, you can use application
service options, or ASOs, to create multiple application QoS policies, or AQPs. AA partitions support statistics
collection and data reporting to the 5670 RAM.
Note When you create an ISAAA group or partition, a default AA policy is automatically created for
the group or partition. When you delete a group or partition, the default policy is also deleted.
See chapter 85 for more information about AA groups, partitions, and policies. See Procedure 152 for information
about creating ISAAA groups and partitions. See Procedures 155 and 156 for information about configuring
additional ISAAA group and partition functions.
15.4 Working with ISATunnel groups
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 119/269
06.07.2017 Device management
ISAtunnel groups provide redundancy for IPsec tunneling and encryption functions when multiple ISAIPSEC MDAs
are installed on an NE. ISAIPSEC redundancy protects against card failure and minimizes service interruption during
maintenance or protocol signature upgrades. You can configure up to four ISATunnel groups on one NE.
An ISAtunnel group can operate in one of the following modes:
primary/backup active MDA
multiple active MDAs
The primary/backup configuration provides fault tolerance in the event of an MDA failure. An ISAtunnel group in a
primary/backup configuration can contain a maximum of two MDAs.
Using multiple active MDAs provides load balancing in addition to fault tolerance. This mode of operation is
supported on a 10.0 R4 or later 7750 SR in chassis mode D or higher, and on a 11.0 R1 or later 7450 ESS in mixed
mode. You can include up to 16 MDAs in an ISAtunnel group when the use of multiple active MDAs is enabled.
You can configure an ISAtunnel group on a 7750 SR or 7450 ESS in mixed mode to act only as an IKEv2 responder
during a MC IPsec switchover. This is the automatic behavior for dynamic tunnels, but not for static tunnels. See
chapter 36 for more information about MC IPsec.
15.5 Working with ISALNS groups
The 5620 SAM supports the creation and configuration of ISALNS groups. ISALNS groups provide LNS PPP
session termination on 7750 SR NEs. You can assign an ISALNS group to a tunnel group profile or a tunnel profile.
When an operational L2TP tunnel is established, peers that are associated with the ISALNS group are automatically
created. Session traffic is automatically balanced across the available active ISA broadband application MDAs in the
group. You can add ISA broadband application MDAs to an ISALNS group, and up to four ISALNS groups on each
NE. See Procedure 158 for information about how to create and configure an ISALNS group.
You must configure the following on the ISALNS groups configuration form:
General properties, such as Group Number, Description, and Administrative State
ISALNS Group members
Note You can configure an ISA broadband application MDA only on an IOM3XP module in a 7750
SR 7 or 7750 SR12.
15.6 Working with ISANAT groups
An ISANAT group provides a redundant NAT function for routing instances using ISA Broadband Applications MDAs.
See chapter 31 for information about ISANAT group configuration.
15.7 Working with ISAVideo groups
ISAVideo groups are created to provide packet buffering and packet processing in support of the IPTV video
features.
When configured in the router, video ISAs are logically grouped into video groups. An ISAVideo group allows more
than one video ISA to be treated as a single logical entity for a specific application, where the system performs a
loadbalancing function when it assigns tasks to a member of the group.
ISAVideo groups provide a redundancy mechanism to guard against hardware failure within a group. ISAVideo
groups pool the processing capacity of all the group members and increase the application throughput because of the
increased packet processing capability of the group.
You must configure the following on the ISAVideo groups configuration form:
General parameters
ISAVideo Group members
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 120/269
06.07.2017 Device management
You can add up to four MDAs to an ISAVideo group, and up to four ISAVideo groups on each NE. All members of
an ISAVideo group are primary members.
Note If the parameter ad Insert server is enabled, only one MDA can be added to an ISAVideo
group.
15.8 Working with ISAWLAN GW groups
An ISAWLAN GW group is used to represent multiple hardware adapters as a single entity, allowing for warm
redundancy between multiple WLAN GW ISAs. Only one ISAWLAN GW group can be created per NE. This group
can be numbered 1 to 4, but this number must be exclusive and cannot be in use by an ISANAT group.
The ISAIOM is the child of the ISAWLAN GW group. Only an IOM3 with both ISA BB MDAs populated is valid for
addition. A maximum of six IOMs can be added to an ISAWLAN GW group, with a maximum active IOM limit of five
per group. The required ISAIOMs should be added before the ISAWLAN GW group is turned administratively up.
ISAWLAN GW members are created automatically by the NE when the ISAWLAN GW group is administratively
up, and deleted automatically when the administrative state is down. The number of members is equal to the active
IOM limit.
You can globally list ISAWLAN GW groups from the Manage ISA Functions ISAWLAN main menu. ISAWLAN
GW groups can also be listed from Manage Equipment.
WLAN GW tunnels
WLAN GW tunnels are created dynamically by the NE when the first UE attempts to connect. The tunnel is used to
backhaul traffic from the access point or residential gateway to the WLAN GW. The NE creates tunnels on a per
access point or perresidential gateway basis. WLAN GW tunnels terminate on the WLANGW ISA.
WLAN GW tunnels are viewable on the configuration form for base routing instances, VPRN routing instances, group
interfaces, and ISAWLAN GW groups. The WLAN GW tunnels tab lists the WLAN GW tunnels belonging to a given
routing instance. User equipment information is viewable from the properties form for individual WLAN GW tunnels.
GTP session information (including bearer information) is viewable from the properties form for individual user
equipment items. You can globally list WLAN GW tunnels from the Manage ISA Functions ISAWLAN main
menu.
15.9 Working with IGH objects
IGHs are navigation tree objects located below the device icon. IGHs are configured manually using the configuration
forms available when you choose Create IGH from the IGH object navigation tree contextual menu.
You create an IGH to group together IP links and POS links so that if a configured number of links go out of service
for any reason, the remaining links in the IGH go out of service too. This causes the routing protocols to reconverge
to switch from the primary path to an alternate path.
The following requirements and restrictions apply to IGHs.
IGHs are supported only on network links.
IGHs are supported only on SONET/TDM interfaces with PPP auto encapsulation.
A port or channel needs to be bound to a router interface after the member is added to an IGH.
You can assign a port to only one IGH.
15.10 Working with LAG objects
LAGs are navigation tree objects located below a device icon which aggregate multiple network connections in
parallel to increase throughput beyond what a single connection can sustain, and to provide redundancy in case one
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 121/269
06.07.2017 Device management
of the links fails.
The following minimum configuration is required to enable LACP.
Enable LACP at either end of the LAG group.
Set one end of the LAG group as LACP active.
You must configure the following in the LAG configuration forms:
General properties, such as LAG description, configured address, encapsulation type, and administrative state
Link aggregation group parameters, such as port threshold, port threshold action, and dynamic cost
LACP parameters, such as LACP mode, LACP transmit interval, actor administration key, LACP transmission
standby, and LACP selection criteria
LAG members, which are the compatible ports that can belong to a LAG
Because all ports can have their own MAC address, when ports are part of a LAG, the LAG must have an MAC
address.
The port configuration of the first port added to the LAG is used to compare with subsequently added ports. If a
discrepancy is found with a newly added port, that port is not added to the LAG.
Typically, up to 32 ports can be added to or removed from a LAG on XCM cards or IOM 3 and IMM cards in chassis
mode D. Otherwise, up to only eight ports can be added to or removed from a LAG. Some devices support fewer
ports on a LAG; see the NE documentation for more information. All ports added to a LAG must have the same
parameter settings.
Only ports belonging to one LAG subgroup are considered eligible members of a LAG and can be selected as active
links.
A LAG can be configured with weighted perlink hashing, which allows a more balanced distribution of subscribers
and services across LAG links. For example, significant differences in subscriber or SAP bandwidth requirements
could lead to unbalanced traffic on LAG egress. You can configure each service or subscriber on a LAG with one of
three unique classes and a weight value to distribute services and subscribers across LAG links.
See section 9.18 for OmniSwitchspecific LAG information.
See the 5620 SAM MPR User Guide for 9500 MPRspecific LAG information.
LAG link mapping profiles
You can use a LAG link mapping profile to assign a specific LAG egress port to a SAP or interface, and control how
egress traffic is handled if the specified port fails. You can then configure the specified port to perform admission
control and QoS contract with the knowledge that all traffic for the SAP or interface will egress on that port. You can
also specify a secondary port to handle traffic in the event that the primary port fails. See Procedure 1517 for more
information about creating LAG link mapping profiles.
LAG utilization TCAs
You can enable TCA on a LAG object and determine whether the LAG utilization value exceeds a TCA policy
threshold. The following nodes support enabling TCA on LAG objects:
7710 SR
7450 ESS
7750 SR
7950 XRS
9500 MPR
You can associate a TCA policy with a LAG object from the TCA policy configuration form. See procedure 203 for
information about applying an existing TCA policy to an object from the object properties form. The 5620 SAM
compares the utilization value at each statistics collection to the threshold value in the TCA policy and raises an
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 122/269
06.07.2017 Device management
alarm when the LAG utilization value crosses the specified limit. You need to enable performance statistics collection
on the LAG object to configure a TCA policy. See chapter 20 for more information about TCA.
L1 LAGs support collection of scheduled and ondemand statistics, and plotting of realtime and historical statistics.
L2 and Ethernet LAGs support collection of scheduled statistics and plotting of historical statistics.
BFD on Ethernet LAGs
You can configure an Ethernet LAG to use BFD to speed up the detection of link failures. When BFD is enabled on a
LAG, microBFD sessions are automatically created for each link in the group. The following nodes support enabling
BFD on a LAG:
7450 ESS
7750 SR
7950 XRS
For information about configuring BFD on a LAG, see Procedure 1513. For information about viewing microBFD
sessions on a LAG, see Procedure 1518.
15.11 Workflow to manage logical group objects
The following workflow describes the sequence of highlevel tasks required to manage and configure logical group
objects. This workflow assumes that the physical devices have been installed, commissioned, and discovered. See
chapter 10 for more information about device commissioning. See chapter 11 for more information about device
discovery.
Note Logical group objects can be accessed using the equipment navigation tree. See chapter 5 for
more information about using the equipment navigation tree.
1. As required, configure CCAG objects. See Procedure 151 for more information.
2. As required, create and configure ISAAA groups and ISAAA partitions. See Procedure 152 for more
information. Additionally, perform the following, as required:
a. Configure AA subscriber statistics collection. See Procedure 153 for more information.
b. Configure AA special study objects (subscriber, SAP, spoke SDP binding, or transit subscriber). See
Procedure 154 for more information.
c. Configure a subscriber policy override on an ISAAA group or ISAAA partition. See Procedure 155 for
more information.
d. Configure cflowd collectors on an ISAAA group and/or ISAAA partition. See Procedure 156 for more
information.
3. As required, configure ISATunnel groups. See Procedure 157 for more information.
4. As required, configure ISALNS groups. See Procedure 158 for more information.
5. As required, create and configure ISANAT groups. See Procedure 311 for more information. Additionally,
perform the following, as required:
a. Configure statistics on an ISANAT group. See Procedure 317 for more information.
b. Start or stop a NAT addresspool drain operation. See Procedure 315 for more information.
6. As required, configure ISAVideo groups. See Procedure 159 for more information.
7. As required, configure ISAWLAN GW groups. See Procedure 1510 for more information.
8. As required, configure IGH objects. See Procedure 1511 for more information.
9. As required, configure LAG objects:
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 123/269
06.07.2017 Device management
a. Create and configure a LAG. See Procedures 1512 and 1513 for more information.
b. Create and configure a LAG on an OmniSwitch. See Procedure 1515 for more information.
c. Create and configure a dynamic LAG member on an OmniSwitch. See Procedure 1516 for more
information.
d. Create a LAG Link Mapping Profile. See Procedure 1517 for more information.
15.12 Workflow to configure weighted perlink hashing on a
LAG
The following workflow describes the sequence of highlevel tasks required to configure weighted perlink hashing on
a LAG. This workflow assumes that the physical devices have been installed, commissioned, and discovered. See
chapter 10 for more information about device commissioning. See chapter 11 for more information about device
discovery.
Note LAG objects can be accessed using the equipment navigation tree. See chapter 5 for more
information about using the equipment navigation tree.
1. Configure a LAG object with weighted perlink hashing. See Procedures 1512 or 1513 for more information.
Configure the required service sites as LAG members.
2. If required, configure LAG weighted perlink hashing on a subscriber profile. See Procedure 622 for more
information.
3. As required, configure SAPs for weighted perlink hashing:
Epipe and Ipipe L2 access interface. See Procedure 7421 for more information.
IES L3 access interface. See Procedure 7626 for more information.
IES group interface SAP. See Procedure 7619 for more information.
VPLS L2 access interface (BVPLS, IVPLS or MVPLS). See Procedure 7529 for more information.
VPRN L3 access interface. See Procedure 7772 for more information.
VPRN group interface SAP. See Procedure 7724 for more information.
15.13 Logical group object configuration procedures
Use the following procedures to configure NE logical groups from the navigation tree.
Procedure 151 To configure a CCAG
1. Choose Equipment from the navigation tree view selector.
3. Rightclick on the CCAGs icon and choose Create CCAG, or rightclick an existing CCAG object and choose
Properties. The CCAG (Create|Edit) form opens.
4. Configure the required parameters.
5. Click Apply.
6. Click on the CCAG MDA Members tab to configure CCAG MDA members.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 124/269
06.07.2017 Device management
7. Click Create or select an existing CCAG MDA member and click Properties. The CCAG MDA Member
(Create|Edit) form opens.
i. Select an MDA to add to the CCAG.
ii. Save and close the form.
8. Click on the CCAG Paths tab to modify the internal paths for the CCAG. The Alpha and Beta paths are
displayed.
i. Select a path and click Properties. The CCAG Internal Path (Edit) form opens.
ii. Configure the required parameters.
iii. Click on the Path Cross Connects tab to configure crossconnects for the CCAG internal path, as
outlined in step 9.
iv. Save your changes and close the form.
9. Click on the Path Cross Connects tab to modify the path crossconnects associated with the CCAG.
i. Select a crossconnect entry and click Properties. The Cross Connect (Edit) form opens.
ii. Configure the required parameters.
iii. Click on the Policies tab to specify nondefault ingress and egress queue policy settings.
iv. To specify an egress slope policy other than the default, click Clear in the Egress Slope Policy panel
and select an alternate policy.
v. Configure the Egress Reserved CBS parameter.
vi. To specify an ingress slope policy other than the default, click Clear in the Ingress Slope Policy panel
and select an alternate policy.
vii. Configure the Ingress Reserved CBS parameter.
10. Save your changes and close the forms.
Procedure 152 To configure an ISAAA group and ISAAA partitions
Perform this procedure to create an ISAAA group that contains one or more partitions. ISAAA partitions provide
ISAAA group functions that are limited to the partition scope.
Note When you create an ISAAA group or partition, a default AA policy is automatically created for
the group or partition. When you delete a group or partition, the default policy is also deleted.
1. Choose Equipment from the navigation tree view selector.
3. Rightclick on the ISAAA Groups icon and choose Create ISAAA Group, or rightclick an existing ISAAA
group object and choose Properties. The ISAAA Group (Create|Edit) form opens.
4. Configure the required parameters.
If the ISAAA group is to be added to an ISAWLAN GW, you must set the Subscriber Scale parameter to
Lightweight Internet.
If you are configuring an existing AA group and the associated AA group policy has SAP dependencies, you
cannot modify the Partitions parameter until you remove the SAP dependencies on the group policy.
The following parameters are configurable when the Subscriber Scale parameter is set to something other than
Lightweight Internet:
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 125/269
06.07.2017 Device management
Number of IPv4 Transit Prefix Entries
Number of Remote IPv4 Transit Prefix Entries
Number of IPv6 Transit Prefix Entries
Number of Remote IPv6 Transit Prefix Entries
5. Click Apply.
6. Click on the ISAAA Group Members tab to specify one or more ISAAA MDAs for the ISAAA group.
i. Click Create or select an existing ISAAA group member entry and click Properties. The ISAAA Group
Member (Create|Edit) form opens.
ii. Configure the ISAAA MDA Role parameter.
If the ISAAA group is to be included for Distributed Subscriber Management in an ISAWLAN GW
group, you must set the ISAAA MDA Role parameter to Primary for each group member.
iii. Select a member MDA.
After a reboot, an NE rebalances the AA processing load. Because of this, the MDA slot number
assigned to an AA subscriber or AA SAP on the AA Subscriber or AA SAP Summary form is displayed
as Unassigned if the AA subscribers in the configuration file cannot be accommodated.
iv. Save your changes and close the form.
7. Click on the ISAAA Group Diverted FCs tab to specify one or more traffic forwarding classes to divert to the
ISAAA group.
i. Click Create or select an existing ISAAA group diverted forwarding class entry and click
Properties.The ISAAA Group Diverted FC (Create|Edit) form opens.
ii. Configure the Forwarding Class Name parameter.
iii. Save your changes and close the form.
8. Click on the QoS tab to configure QoS policy parameters for the ISAAA group.
i. Configure the required parameters on the Egress FromSubscriber tab.
You must deselect the Default check box before you can use a slider to specify a Reserved CBS or
Buffer Utilization High Water Mark value.
The value of the Buffer Utilization High Water Mark parameter must be higher than the value of the
Buffer Utilization Low Water Mark parameter.
ii. Select a slope policy in the Slope Policy panel.
iii. Select a network queue policy in the Network Queue Policy panel.
iv. Select a port scheduler policy in the Port Scheduler Policy panel.
v. Click on the Egress ToSubscriber tab and repeat steps 8 i to iv.
9. You can configure the following objects on the ISAAA group if the Partitions parameter was disabled in step
4.
AA subscriber statistics (Procedure 153)
AA special study objects (subscriber, SAP, spoke SDP binding, or transit subscriber) (Procedure 154)
AA subscriber policy override (Procedure 155)
10. Click on the CFLOWD tab To configure cflowd on the ISAAA group (See Procedure 156.
11. If the Partitions parameter on the General tab was enabled in step 4, click on the ISAAA Partitions tab to
configure AA partitions for the group.
i. Click Create or select an existing partition entry and click Properties. The ISAAA Group Partition
(Create|Edit) form opens.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 126/269
06.07.2017 Device management
ii. Configure the required parameters.
iii. Click on the CFLOWD tab to configure cflowd on the partition (See Procedure 156.
iv. The following objects are configurable on ISAAA group partitions:
AA subscriber statistics (Procedure 153)
AA special study objects (subscriber, SAP, spoke SDP binding, or transit subscriber) (Procedure
154)
AA subscriber policy override (Procedure 155)
12. Save your changes and close the forms.
Procedure 153 To configure AA subscriber statistics collection on an ISAAA
group or partition
If partitions are disabled on an ISAAA group, subscriber statistics objects are configured directly on the group. If
partitions are enabled on an ISAAA group, subscriber statistics objects are configured on the individual partitions
within the group.
1. If you are performing this procedure as part of the ISAAA group or partition configuration described in
Procedure 152, go to step 5.
2. Choose Equipment from the navigation tree view selector.
4. Rightclick on the ISAAA Group n icon and choose Properties. The ISAAA Group (Edit) form opens.
5. If you are configuring the subscriber statistics objects on an ISAAA partition, perform the following steps.
i. Click on the ISAAA Partitions tab.
ii. Select a partition in the list and click Properties. The ISAAA Group Partition (Edit) form opens.
6. Click on the AA Subscriber Stats Objects tab.
i. Click Add and choose one of the following options:
Application
Application Group
Charging Group
System Protocol
Custom Protocol
The Select object_type form opens and lists the available objects of the chosen type.
ii. Select an object and click OK. The Select object_type form closes and the AA Subscriber Stats Object
Config form opens.
iii. Configure the parameters in the Export Method Selection panel.
7. Save your changes and close the forms.
Procedure 154 To configure special study objects on an ISAAA group or
partition
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 127/269
06.07.2017 Device management
If partitions are disabled on an ISAAA group, special study objects are configured directly on the group. If partitions
are enabled on an ISAAA group, special study objects are configured on the individual partitions within the group.
1. If you are performing this procedure as part of the ISAAA group or partition configuration described in
Procedure 152, go to step 5.
2. Choose Equipment from the navigation tree view selector.
4. Rightclick on the ISAAA Group n icon and choose Properties. The ISAAA Group (Edit) form opens.
5. If you are configuring the special study objects on an ISAAA partition, perform the following steps.
i. Click on the ISAAA Partitions tab.
ii. Select a partition in the list and click Properties. The ISAAA Group Partition (Edit) form opens.
6. To configure special study subscribers on the ISAAA group or partition, click on the Subscribers tab.
i. Click Create or select an existing special study subscriber and click Properties. The AA Special Study
Subscriber Config (Create|Edit) form opens.
ii. Configure the AA Subscriber Name and AA Stats Type parameters.
iii. Save your changes and close the form.
7. To configure special study subscribers on the ISAAA group or partition, click on the SAPs tab.
Click on one or more of the following buttons and use the list form that opens to select one or more objects,
as required:
Add PerSAP Protocols—to add a SAP for perprotocol monitoring
Add PerSAP Applications—to add a SAP for perapplication monitoring
8. To configure special study spoke SDP bindings on the ISAAA group or partition, click on the Spoke SDP
Bindings tab.
Click on one or more of the following buttons and use the list form that opens to add one or more objects, as
required:
Add PerSpoke SDP Binding Protocols—to add a SAP for perprotocol monitoring
Add PerSpoke SDP Binding Applications—to add a SAP for perapplication monitoring
9. To configure special study transit subscribers on the group or partition, click on the Transit Subscribers tab.
i. Click Create or select an existing transit subscriber entry and click Properties. The AA Special Study
Transit Subscriber Config (Create|Edit) form opens.
ii. Select a transit subscriber.
iii. Configure the AA Stats Type parameter.
10. Save your changes and close the forms.
Procedure 155 To configure an AA subscriber policy override on an ISAAA
group or partition
If partitions are disabled on an ISAAA group, subscriber policy overrides are configured directly on the group. If
partitions are enabled on an ISAAA group, subscriber policy overrides are configured on the individual partitions
within the group.
The AA subscriber policy override is rejected if the subscriber does not have an application profile assigned. You can
add an AA subscriber policy override to a SAP or Spoke SDP, but not to an ESM subscriber.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 128/269
06.07.2017 Device management
1. If you are performing this procedure as part of the ISAAA group or partition configuration described in
Procedure 152, go to step 5.
2. Choose Equipment from the navigation tree view selector.
4. Rightclick on the ISAAA Group n icon and choose Properties. The ISAAA Group (Edit) form opens.
5. If you are configuring the subscriber policy override on an ISAAA partition, perform the following steps.
i. Click on the ISAAA Partitions tab.
ii. Select a partition in the list and click Properties. The ISAAA Group Partition (Edit) form opens.
6. Click on the AA Subscriber Policy Overrides tab.
Note An AA subscriber policy override is rejected if the subscriber does not have an assigned
application profile.
7. Click Create or select an existing policy override entry and click Properties. The AA Subscriber Policy
Override (Create|Edit) form opens.
8. Configure the AA Subscriber Type parameter.
9. Perform one of the following, based on the AA Subscriber Type parameter setting:
a. If it is SAP, select a SAP subscriber in the SAP Subscriber panel.
b. If it is Spoke SDP Binding, select a spoke SDP binding subscriber in the Spoke SDP Binding
Subscriber panel.
c. If it is Transit, select a transit subscriber in the Transit Subscriber panel.
10. Click on the ASO Characteristics tab.
i. Click Create or select an existing policy override ASO characteristic entry and click Properties. The AA
Subscriber Policy Override ASO Characteristic (Create|Edit) form opens.
ii. Select an override ASO characteristic.
iii. Select an override ASO characteristic value.
11. Save your changes and close the forms.
Procedure 156 To configure cflowd collectors on an ISAAA group or
partition
You can configure cflowd collectors on an ISAAA group and/or partitions within the group. The configurable options
differ, depending on which type of object you are configuring.
1. If you are performing this procedure as part of the ISAAA group or partition configuration described in
Procedure 152, go to step 5.
2. Choose Equipment from the navigation tree view selector.
4. Rightclick on the ISAAA Group n icon and choose Properties. The ISAAA Group (Edit) form opens.
If you are configuring cflowd on an ISAAA partition, go to step 8.
5. Click on the CFLOWD tab and configure the required parameters on the General tab.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 129/269
06.07.2017 Device management
6. Click on the Collector tab.
i. Click Create or select an existing collector entry and click Properties. The Cflowd Collector
(Create|Edit) form opens.
ii. Configure the required parameters.
iii. Save your changes and close the form
Note An ISAAA group can contain a maximum of two cflowd collectors.
7. Go to step 12.
8. Click on the ISAAA Partitions tab.
9. Select a partition in the list and click Properties. The ISAAA Group Partition (Edit) form opens.
10. Click on the CFLOWD tab.
11. To add an AA application or application group for cflowd performance monitoring, click on the Performance tab.
Otherwise, go to step 14.
12. To add an AA application for cflowd performance monitoring, perform the following steps.
i. Click Add Applications RTP, Add Applications Comprehensive, or Add Applications TCP. The Select
Applications form opens.
ii. Select one or more applications and click OK.
13. To add an AA application group for cflowd performance monitoring, perform the following steps.
i. Click Add Application Groups RTP, Add Application Groups Comprehensive, or Add Application Groups
TCP. The Select Application Groups form opens.
ii. Select one or more application groups and click OK.
14. To set the cflowd sampling administrative states, click on the States tab and configure the required
parameters.
15. Save your changes and close the forms.
Procedure 157 To configure an ISAtunnel group
1. Choose Equipment from the network navigation tree view selector.
3. Rightclick on the ISATunnel Groups icon and choose Create ISATunnel Group, or rightclick an existing ISA
tunnel group object and choose Properties. The ISATunnel Group (Create|Edit) form opens.
4. Configure the required parameters.
5. Click Apply.
6. Configure the parameters that appear on the OLC panel.
7. Click on the ISA Tunnel Group Members tab.
i. Click Create or select an existing tunnel group member entry and click Properties. The ISA Group
Member (Create|Edit) form opens.
ii. Select a daughter card.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 130/269
06.07.2017 Device management
iii. Save your changes and close the form.
iv. Repeat steps i to iii to configure the backup ISATunnel group member.
8. Save your changes and close the forms.
Procedure 158 To configure an ISALNS group
You can configure an IES or VPRN group interface to terminate LNS PPP sessions. See chapter 76 for information
about configuring an IES group interface. See chapter 77 for information about configuring a VPRN group interface.
1. Choose Equipment from the navigation tree view selector.
3. Rightclick on the ISALNS Groups icon and choose Create ISALNS Group, or rightclick an existing ISA
LNS group object and choose Properties. The ISALNS Group (Create|Edit) form opens.
4. Configure the required parameters.
5. Select a port policy.
6. Click Apply.
7. Configure the parameters that appear on the OLC panel.
8. Click on the ISALNS Group Members tab.
i. Click Create or select an existing LNS group member entry and click Properties. The ISALNS Group
Member (Create|Edit) form opens.
Note You can configure up to six ISALNS group members. For each group member,
you must choose an ISA Broadband Applications MDA. An ISA Broadband Applications
MDA can be configured only on an IOM3XP module on a 7750 SR.
ii. Select the LNS group member MDA.
iii. Repeat steps i and ii to configure additional LNS group members, if required.
9. Save your changes and close the forms.
Procedure 159 To configure an ISAVideo group
1. Choose Equipment from the navigation tree view selector.
3. Rightclick on the ISAVideo Groups icon and choose Create ISAVideo Group, or rightclick an existing ISA
video group object and choose Properties. The ISAVideo Group (Create|Edit) form opens.
4. Configure the required parameters.
5. Click Apply.
6. Configure the parameters that appear on the OLC panel.
7. Click on the Video Group Members tab.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 131/269
06.07.2017 Device management
i. Click Create or select an existing video group member entry and click Properties. The Video Group
Member (Create|Edit) form opens.
ii. Select the video group member card.
iii. Repeat steps i and ii to configure additional LNS group members, if required.
8. Save your changes and close the forms.
Procedure 1510 To configure an ISAWLAN GW group
1. Choose Equipment from the navigation tree view selector.
3. Rightclick on the ISAWLAN GW Groups icon and choose Create ISAWLAN GW Group, or rightclick an
existing ISAWLAN GW Group object and choose Properties. The ISAWLAN GW Groups (Create|Edit) form
opens.
4. Configure the required parameters.
5. Select a port policy.
6. Select a tunnel port policy.
7. Select a NAT RADIUS accounting policy in the NAT panel, if required.
8. Select an ISAAA group in the Distributed Subscriber Management panel, if required.
9. Click Apply. The ISAWLAN GW Group form refreshes with additional tabs.
10. Configure OLC parameters, if required.
11. Click on the ISAIOMs tab.
i. Click Create or select an existing IOM entry and click Properties. The ISAWLAN GW Group IOM
(Create|Edit) form opens.
ii. Select the ISAWLAN GW group member IOM card.
iii. Repeat steps i and ii to configure additional LNS group members, if required.
12. Save your changes and close the forms.
Procedure 1511 To create an IGH and add members
1. Choose Equipment from the navigation tree view selector.
3. Rightclick on the IGHs icon and choose Create IGH. The Create IGH form opens with the Define General
Properties step displayed.
4. Configure the required parameters.
5. Click Next. The Configure IGH Members step displays.
6. Click Create. The Create IGH Member form opens with the Select Ports step displayed.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 132/269
06.07.2017 Device management
Alternatively, you can create IGH members anytime by rightclicking on an existing IGH object and choosing
Create IGH Members from the contextual menu.
7. Choose a port from the list and click Finish.
8. Repeat steps 6 and 7 to add more members, if required.
9. Click Finish.
10. Click Close. The Create IGH form closes.
15.14 LAG configuration procedures
Use the following procedures to manage LAGs using the navigation tree.
Procedure 1512 To create a LAG
This procedure applies to 7950 XRS, 7210 SAS, 7450 ESS, 7710 SR, 7705 SAR, and 7750 SR NEs. See Procedure
1516 for information about configuring a LAG on an OmniSwitch. See the 5620 SAM MPR User Guide for
information about configuring a LAG on a 9500 MPR.
1. Choose Equipment from the navigation tree view selector.
3. Rightclick on LAGs and choose Create LAG. The Create LAG wizard opens.
Configure general properties
4. Configure the required parameters.
If you are creating a LAG for HSMDA, the Port Type parameter must be set to HSMDA. The Encapsulation
Type must be either Dot1Q or QinQ. Setting Mode to network creates a network LAG, and setting it to access
creates an access LAG.
If you are creating a LAG containing ports on an XMDA card on the 7705 SAR18, the Encap Type parameter
must be either Dot1 Q or Null and the Mode must be set to Access.
The Weighted parameter is configurable only if the PerLink Hashing parameter is enabled. The Auto
Rebalance parameter is only configurable only if the Weighted parameter is enabled.
Consider the following when you configure the Enable DEI parameter on a hybrid LAG.
When the Enable DEI parameter is selected, the Enable DEI parameter for the ports in the LAG must
also be selected. See Procedure 171.
Network policies assigned to the ports in the LAG must be configured to use DEI as the profile. The
Default FC Profile parameter and the Profile parameter on the Ingress Dot1p tab must be set to the DEI
option. See Procedure 498.
5. If you are configuring a LAG on a 7210 SAS NE that supports split horizon groups, you can select an SHG in
the Split Horizon Group panel. See Procedure 1717 for information about creating a 7210 SAS SHG.
Note 1 A LAG cannot be added to or deleted from an SHG if it has a SAP configured on it.
Note 2 A LAG cannot belong to more than one SHG; you must remove all SHGs from the
LAG before you can add the LAG to a different SHG.
Configure LAG parameters
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 133/269
06.07.2017 Device management
6. Click Next. The Configure LAG Parameters step displays.
7. Configure the required parameters.
You must set the Port Threshold parameter to 0 when the Standby Signalling parameter is set to Power Off in
step 12.
To add a mix of 10G and 100G ports to the LAG, set the Port Weight Speed (gbps) to 10.
8. Perform one of the following:
a. If you set the Mode parameter in step 4 to Access or Hybrid, go to step 9.
b. If you set the Mode parameter in step 4 to Network, or if you did not configure the Mode parameter, go
to step 11.
Configure access parameters
9. Click Next. The Configure Access Parameters step displays.
10. Configure the required parameters.
If you are creating a LAG for HSMDA, the QoS Adaptation parameter must be set to Link, otherwise the LAG
will not be created.
Configure LACP parameters
11. Click Next. The Configure LACP form opens.
12. Configure the required parameters.
The LACP Mode, LACP Transmit Interval, Actor Administration Key, LACP System ID, and LACP System
Priority parameters are configurable when the LACP Enabled parameter is enabled.
When the Standby Signalling parameter is set to Power Off, you must set the Active SubGroup Selection
Criteria parameter to Best Port.
Configure LAG members
13. Click Next. The Configure LAG Members step displays.
14. Click Create. The Only Show Compatible Ports wizard opens.
15. Configure the Show Only Compatible Ports and Class parameters.
16. Click Next. The Select Ports step displays.
17. Choose compatible ports to construct the LAG:
i. Choose one or more ports. The maximum number of ports you can choose depends on the NE type.
Note If there are no compatible ports to choose from and you want to edit some of the
existing ports to be compatible, disable the Show Only Compatible Ports parameter in
step 15.
For ports to appear as compatible ports, ensure no SAPs or services are configured on them.
You must use the same load balance algorithm for the ports associated with the LAG.
All ports added to a LAG must have the Enable DEI parameter set to the same configuration.
For HSMDAv2 ports in a LAG, you must set the Autonegotiate parameter to False or Limited. See
Procedure 171 for more information on configuring Ethernet ports.
If you are creating a LAG containing ports on an XMDA card in the 7705 SAR18, then the following
conditions apply to the ports:
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 134/269
06.07.2017 Device management
The Encapsulation Type must be set to either Dot1Q or Null.
The Mode parameter must be set to Access.
The Autonegotiate parameter must be set to False or Limited.
ii. Click Next. The Specify the Member Properties step displays.
iii. Configure the Priority and SubGroup ID parameters.
iv. If required, perform step 33 of Procedure 171 to add Egress Secondary Shapers to a port member of
an HSMDA LAG. The following devices support this function:
7450 ESS6 7750 SR7
7450 ESS7 7750 SR12
7450 ESS12
The add/delete/modify functions for Egress Secondary Shapers apply only to the primary port.
There can be a total of 64 egress secondary shapers per MDA, including the default shaper.
The Egress Secondary Shapers on the primary port of the LAG are propagated to each nonprimary port
member of the LAG, with a maximum 8 ports per LAG. These propagated shapers cannot be deleted.
For adding any new port to the LAG, the user must configure each Egress Secondary Shaper as per the
primary port, otherwise the addition of the port is blocked.
When adding a port member to a LAG, the primary port and each selected port (maximum 8 ports)
secondary shapers must have the same name and rate.
Ports with Egress Secondary Shapers cannot be added to a configured LAG which do not match the
Egress Secondary Shapers of the primary port.
Shapers are not removed from the port when the port is removed from a LAG.
The SAP reference to the Egress Secondary Shapers within a LAG is supported. Only the primary port
of the SAP on the LAG is used to determine the list of Egress Secondary Shapers for the SAP.
Note When port members are removed from the LAG, care must be taken to ensure
that the last port member is not removed if the LAG is referenced to a SAP. Shapers
must exist on a LAG to be referenced on a SAP. See chapters 68 to 83 for more
information.
18. Click Finish.
Configure BFD parameters
19. Click Next. The Configure BFD step displays.
20. Select the IPv4 or IPv6 entry and click Properties. The BFD Configuration on LAG form appears.
21. Configure the required parameters.
22. Save your changes and close the form.
23. Click Finish. Save your changes and close the wizard.
Procedure 1513 To modify a LAG
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 135/269
06.07.2017 Device management
This procedure applies to 7210 SAS, 7450 ESS, 7705 SAR, 7710 SR, 7750 SR, and 7950 XRS NEs. See Procedure
1516 for information about configuring a LAG on an OmniSwitch. See the 5620 SAM MPR User Guide for
information about configuring a LAG on a 9500 MPR.
1. Choose Equipment from the navigation tree view selector.
3. Rightclick on the LAG n object and choose Properties. The LAG (Edit) form opens.
Configure general parameters
4. Configure the required parameters.
The Weighted parameter is configurable only if the PerLink Hashing parameter is enabled, and the Auto
Rebalance parameter is only configurable if the Weighted parameter is enabled.
Consider the following when you configure the Enable DEI parameter on a hybrid LAG.
When the Enable DEI parameter is selected, the Enable DEI parameter for the ports in the LAG must
also be selected. See Procedure 171.
Network policies assigned to the ports in the LAG must be configured to use DEI as the profile. The
Default FC Profile parameter and the Profile parameter on the Ingress Dot1p tab must be set to the DEI
option. See Procedures 1716 and 498.
5. If you are configuring a LAG on a 7210 SAS NE that supports split horizon groups, you can select an SHG in
the Split Horizon Group panel. See Procedure 1717 for information about creating a 7210 SAS SHG.
Note 1 A LAG cannot be added to or deleted from an SHG if it has a SAP configured on it.
Note 2 A LAG cannot belong to more than one SHG; you must remove all SHGs from the
LAG before you can add the LAG to a different SHG.
6. If you are configuring a LAG on a 7850 VSG, you can select a port profile and an operational group in the
OperGroup and ServiceProfle panel.
Configure other LAG parameters
7. Click on the Link Aggregation Group tab and configure the required parameters.
You must set the Port Threshold parameter to zero when the Standby Signalling parameter is set to Power Off
in step 10.
To add a mix of 10G and 100G ports to the LAG, set the Port Weight Speed (gbps) to 10.
8. Click on the States tab and configure the Administrative State parameter.
9. If you are configuring a LAG in Access or Hybrid mode, click on the Access tab and configure the required
parameters.
If you are configuring a LAG for HSMDA, the QoS Adaptation parameter must be set to Link.
10. Click on the LACP tab and configure the required parameters.
The LACP Mode, LACP Transmit Interval, and Actor Administration Key parameters are configurable when the
LACP Enabled parameter is enabled.
When the Standby Signalling parameter is set to Power Off, you must set the Active SubGroup Selection
Criteria parameter to Best Port
11. Click on the LAG Members tab.
You can also add LAG members by rightclicking on an existing LAG object and choosing Create LAG
Members from the contextual menu.
To add LAG members, perform steps 14 to 18 of Procedure 1512.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 136/269
06.07.2017 Device management
12. Perform one of the following steps:
a. If the LAG that you are configuring is in Network mode, the Network Interfaces tab is displayed. Click
Create. The Create Network Interface form opens. See Procedure 2810 for information on creating a
network interface. Otherwise go to step 17.
b. If the LAG that you are configuring is in access mode or hybrid mode with dot1q or QinQ encapsulation,
or in network mode with dot1q encapsulation, the MEPs tab is displayed. Go to step 13.
13. Add a facility MEP to the LAG:
Note Only one facility MEP can be configured on a LAG.
i. Click on the MEPs tab and click Create. The MEP (Create) form opens.
ii. Select a global MEG.
iii. Configure the required parameters.
Note 1 You cannot enable the collection of LMM statistics on a facility MEP if a service
MEP is already configured to collect the LMM statistics information.
Note 2 The CCM Padding Packet Size (Bytes) parameter cannot be configured when
the CCM interval parameter is set to 10 ms or 100 ms.
Note 3 To enable fault propagation on a LAG facility MEP, the Facility Fault Notify
parameter must be enabled.
iv. If the MD for the MEP has a Name Type of None, the Y.1731 Tests tab is configurable; click on the
Y.1731 Tests tab and configure the required parameters.
The Eth Test Pattern parameter is configurable when the Eth Test Enabled parameter is enabled.
v. Save your changes and close the form.
14. To add a tunnel facility MEP to the LAG, perform the following steps.
The LAG that you are configuring must be in Access mode or Hybrid mode and must have an encapsulation
type of QinQ.
i. Click on the MEPs tab.
ii. Click Create. The MEP (Create) form opens.
iii. Select a global MEG.
iv. Configure the required parameters.
Note 1 The CCM Padding Packet Size (Bytes) parameter cannot be configured when
the CCM interval parameter is set to 10 ms or 100 ms.
Note 2 To enable the fault propagation on a tunnel facility MEP, Facility Fault Notify
must be enabled.
Note 3 To link the tunnel facility status to the SAP, Facility VLAN ID must match the
outer encapsulation value of the SAP.
Note 4 To accept the fault notification from a facility MEP on the site where the SAP is
located and on the SAP, Tunnel Fault Management must be set to Accept.
v. If the MD for the MEP has a Name Type of None the Y.1731 Tests tab is configurable; click on the
Y.1731 Tests tab and configure the required parameters.
The Eth Test Pattern parameter is configurable when the Eth Test Enabled parameter is enabled.
vi. Save your changes and close the form.
15. Configure EthernetCFM redundancy on a facility MEP.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 137/269
06.07.2017 Device management
You must enable Ethernet CFM redundancy globally on a device before it can function on child objects such
as LAGs. See chapter 14 for information about device object configuration.
The tunnel MEP must be part of an MCLAG with Ethernet CFM redundancy configured.
i. Click on the MEPs tab.
ii. Choose the facility MEP for which you need to configure EthernetCFM redundancy and click
Properties. The MEP (Edit) form opens.
iii. On the Facility MEPS panel, enable the Create Redundant MEP parameter.
iv. Click OK to confirm. A redundant tunnel MEP with the same ID and Operational MAC address is
created on the peer LAG. The redundant MEP has the same state as the MCLAG in which that MEP
resides.
16. Configure BFD parameters:
i. Select the IPv4 or IPv6 entry and click Properties. The BFD Configuration on LAG form appears.
ii. Configure the required parameters.
iii. Save your changes and close the form.
17. Save your changes and close the form.
Procedure 1514 To manually rebalance LAG subscribers
Perform this procedure to force a manual subscriber load balance function on a LAG that is configured for weighted
perlink hashing.
1. Choose Equipment from the navigation tree view selector.
3. Rightclick on the LAG n object and choose Properties. The LAG (Edit) form opens.
4. Click the Load Balance button. The LAG Load Balance form opens.
5. Configure the Class ID parameter.
6. Click OK to perform the load balance function.
7. Close the form.
Procedure 1515 To configure an OmniSwitch LAG
Note 1 You can configure MVRP fixed ports/LAGs, 802.1 Q ports/LAGs, aggregate ports/LAGs, and
VLAN Stacking Network ports/LAGs.
Note 2 When a port is assigned to a LAG member, you cannot modify the port properties using the
5620 SAM.
1. Choose Equipment from the navigation tree view selector.
3. Rightclick on LAGs and choose Create LAG. The Create LAG wizard opens.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 138/269
06.07.2017 Device management
Configure general parameters
4. Configure the required parameters.
The Automatic VLAN Binding parameter can only be configured for network LAGs and Stacked VLANs.
Configure LAG parameters
5. Click Next. The Create LAG Configure LAG Parameters step displays.
6. Configure the required parameters.
7. Perform one of the following:
a. If you set the Type parameter to Static, go to step 11.
b. If you set the Type parameter to Dynamic, go to step 8.
Configure LACP parameters
8. Click Next. The Create LAG Configure LACP step displays.
9. Configure the required parameters.
10. Go to step 16.
See Procedure 1516 for more information about adding members to a dynamic LAG.
Configure LAG members
11. Click Next. The Create LAG Configure LAG Members step displays.
12. Click Create to add ports to the LAG. The Create LAG Member Only show compatible ports wizard opens.
13. Configure the Show Only Compatible Ports and Class parameters.
14. Click Next. The Create LAG Member Select Ports step displays.
15. Choose up to the maximum number of ports you require from the list of ports to create the LAG. You can
select more than one port at a time from the list.
Note 1 If there are no compatible ports to choose from and you want to edit some of the
existing ports to be compatible, then disable the Show Only Compatible Ports parameter. Click
Next. Choose ports to edit from the list and click Properties.
Note 2 Mobile, UNI, and NNI ports cannot be members of a LAG.
Note 3 Only network ports can be members of a network LAG and only access ports can be
members of an access LAG.
16. Click Finish. Save your changes and close the forms.
Procedure 1516 To configure OmniSwitch dynamic LAG members
Note 1 LAG members are not added during the creation of the dynamic LAG, as they are with static
LAGs. When a new dynamic LAG member is created it is placed into the Unassigned Dynamic LAG
Members object. The new dynamic LAG members remain under the Unassigned Dynamic LAG
Members object until the system identifies a LAG with matching properties. When an unassigned LAG
member joins a LAG, the member is removed from the Unassigned Dynamic LAG Members object and
added to the appropriate LAG object.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 139/269
06.07.2017 Device management
Note 2 When a port is assigned to a LAG member, you cannot modify the port properties using the
5620 SAM.
1. Choose Equipment from the navigation tree view selector.
3. Rightclick on the Unassigned Dynamic LAG Members object and choose Create LAG Members. The Create
LAG Member wizard opens.
4. Configure the Show Only Compatible Ports and Class parameters.
5. Click Next. The Create LAG Member Select Ports step displays.
6. Choose up to the maximum number of ports you require from the list of ports to create the LAG. You can
select more than one port at a time from the list.
Note 1 If there are no compatible ports to choose from and you want to edit some of the
existing ports to be compatible, then disable the Show Only Compatible Ports parameter. Click
Next. Choose ports to edit from the list and click Properties.
Note 2 For all ports in an LAG, you must disable autonegotiation, configure the same speed,
and set the ports to full duplex. Mobile ports cannot be part of a LAG.
7. Configure the required parameters.
8. Click Finish. Save your changes and close the form.
Procedure 1517 To create a LAG link mapping profile
Note You can only use LAG link mapping profiles on an NE that is in chassis mode D or higher.
1. Choose Equipment from the navigation tree view selector.
3. Rightclick on the LAG n object and choose Properties. The LAG (Edit) form opens.
Table 151 describes the required parameter values that must be set in order to use LAG link mapping profiles.
Table 151 LAG link mapping prerequisites
Tab Parameter Required values
General Port Type Access or Hybrid
Access QoS Adaptation Link
LAG Members SubGroup ID All LAG members must be in the same subgroup.
4. Click on the Link Mapping Profiles tab and click Create. The Link Mapping Profile (New Instance) form opens.
Configure general profile parameters
5. Configure the required parameters on the General tab.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 140/269
06.07.2017 Device management
Create mapping profile links
6. Click on the Mapping Profile Links tab and click Create. The Link Mapping Profile Link (New Instance) form
opens.
7. Click Select and specify a port. The selected port will be used for egress traffic for interfaces assigned to this
LAG link mapping profile.
8. Configure the Type parameter.
9. Save your changes and close the form.
10. Configure a secondary port by repeating steps 6 to 9, if required.
Assign the link mapping profile to an interface or MSAP policy, if required
11. Assign the LAG link mapping profile to a network interface, access interface, or SAP, if required:
i. Click on the Network Interface, L2 Access Interface, L3 Access Interface, or Service Access Points
tab. A list of interfaces that terminate on the LAG appears.
ii. Select an interface from the list and click Properties. The Interface (Edit) form appears.
iii. Click on the Port tab.
iv. Select a LAG link mapping profile.
v. Save your changes and close the form.
12. Assign the LAG link mapping profile to an MSAP policy, if required:
i. From the 5620 SAM main menu, select Policies Residential Subscriber. The Residential Subscriber
Policies form opens.
ii. Select an MSAP policy from the list and click Properties. The MSAP Policy (Edit) form opens.
iii. Click on the Local Definitions tab.
iv. Select the local definition for the site where the LAG link mapping profile is configured, and click
Properties. The MSAP Policy (Local Policy) form opens.
v. If the Distribution Mode parameter is set to Sync With Global, click Switch Mode.
vi. Set the LAG Link Map Profile parameter to the ID of the LAG link mapping profile you need to assign to
the MSAP policy.
vii. Save your changes and close the forms.
Procedure 1518 To view microBFD sessions on a LAG
1. Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view.
3. Rightclick on the LAG n icon and choose Properties. The LAG (Edit) form opens.
4. Click on the BFD tab.
5. Select the IPv4 or IPv6 entry and click Properties. The BFD Configuration on LAG form opens.
6. Click on the Micro BFD Session tab.
7. Select a BFD session and click Properties to view information about the selected session.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 141/269
06.07.2017 Device management
8. 16 — Shelf object configuration
16.1 Shelf object configuration overview
16.2 Working with shelf objects
16.3 Working with card and card slot objects
16.4 Working with daughter card objects
16.5 Working with bundle objects
16.6 Workflow to manage shelf objects
16.7 Shelf object configuration procedures
16.8 Card and card slot object configuration procedures
16.9 Daughter card slot object configuration procedures
16.10 Bundle configuration procedures
16.1 Shelf object configuration overview
In the equipment navigation tree, shelf objects are children of device objects. They appear below logical group
objects in the navigation tree. Card slot objects are children of shelf objects, and as such appear below the shelf
object in the navigation tree. Daughter card slot objects are created in the navigation tree as children of the card slot
object, after the card slot object is configured. APS bundle objects appear below the shelf object and Bundle objects
appear below daughter card objects that are configured as channelized MDAs.
This chapter contains the procedures to configure shelf, card slot, daughter card slot, and bundle objects using the
navigation tree. See chapter 5 for more information about using the navigation tree. See chapter 40 for more
information about APS bundles.
16.2 Working with shelf objects
Shelf objects represent the hardware that is configured on a shelf. When you choose the shelf object in the
navigation tree and click on Properties in the contextual menu, you can view the states and conditions of the shelf
including:
general information timing
fan tray state and speed statistics
power supply tray statuses dry contacts
LED statuses faults
card slots port segregation
hardware environment information software control module
CCM properties software bank information
PoE cross connects
The Display tab displays a graphical representation of the device’s shelf and its equipment components, such as the
empty card slots and the cards that are installed on the device. You can doubleclick on an object under this tab to
open its Properties configuration form. Rightclick on the object and you have full access to the contextual menus for
the object and any child objects, for example the ports of a card (dynamic graphical representation only).
Chassis modes
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 142/269
06.07.2017 Device management
The chassis mode of a device indicates the minimum IOM or IMM card type that is initialized by the device and
determines the scaling numbers and features that are available to the system. The chassis mode can be configured
on the following device types:
7450 ESS4, 7450 ESS6, 7450 ESS7, and 7450 ESS12
7450 ESS6v
7750 SR7 and 7750 SR12
See the appropriate device Release Notice for scaling information.
Note Chassis modes are not supported on the 7950 XRS.
Table 161 lists IOM and IMM cards and the compatibile 7750 SR chassis modes.
Table 161 Chassis mode compatibility, 7750 SR IOM and IMM cards
Card Chassis mode
2 x 10Gig MDA IOM A
2 x 10Gig MDA IOM Card, B A and B
2 x 10Gig MDA IOM 2 A, B, and C
2 x XP MDA IOM 3 A, B, C, and D
2 x XP MDA IOM 3, B A, B, C, and D
4Port 10 GE XFP IMM A, B, C, and D
8Port 10 GE XFP IMM
48Port GIGE SFP IMM
48Port GIGE SFP IMM, B
48Port GIGE TX IMM
48Port GIGE TX IMM, B
12Port 10GE SFP IMM
1Port 100GE CFM IMM
3Port 40GE QSFP possibly oversubscribed IMM
Table 162 lists IOM and IMM cards and the compatibile 7450 ESS chassis modes.
Table 162 Chassis modes and 7450 ESS IOM card compatibility
Card Chassis mode
2 x 10Gig MDA IOM A
2 x 10Gig MDA IOM Card, B A and B
2 x 10Gig MDA Oversubscribed IOM A and B
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 143/269
06.07.2017 Device management
2 x XP MDA IOM 3 A, B, and B
2 x XP MDA IOM 3, B A, B, C, and D
48Port GIGE SFP IMM
48Port GIGE SFP IMM, B
48Port GIGE TX IMM
48Port GIGE TX IMM, B
3Port 40GE QSFP possibly oversubscribed IMM
Timing synchronization
Timing synchronization parameters can be configured on 7210 SAS, 7450 ESS, 7705 SAR, 7710 SR, 7750 SR, 7750
SRc4, 7750 SR12E, 7750 SRc12, and 7950 XRS shelves that contain the following daughter cards:
10 Gigabit Ethernet with 2 and 4port configurations
10 × 1GigE SFP + 1 × 10GigE XFP
10 × 1GigE SFP
10/100/1000 Ethernet SFP with 20 ports
10 Gigabit Ethernet XFP with 4, 8, and 48port configurations
10port Gigabit Ethernet SFP HA
16 × Channelized DS1/E1 ASAP
16 × Channelized DS1/E1 ASAP v2
8port Ethernet
8port Ethernet v2
4port OC3/STM1 ASAP SFP
4 × MWA Gig Ethernet (2 TX, 2 SFP) + 4 × Gig Ethernet SFP
8port GIGE SPF card V2 (48/+24 VDC)
2port 100 Gigabit Ethernet CFP CXMA
20port 10 Gigabit Ethernet SFP + CXMA
40port 10 GE SFP+ XMA
4port 100 GE CXP XMA
2port OC192c/STM64c XFP MDA
See Procedure 168 for more information about configuring timing synchronization.
IEEE 1588 PTP clock
The 5620 SAM supports IEEE 1588 PTP clocks for packetbased timing synchronization from a master clock to one
or more slave clocks in a network.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 144/269
06.07.2017 Device management
Depending on the device, NEs can be configured with an ordinary master, ordinary slave, or boundary clock. The
7705 SARA, 7705 SARH, 7705 SARHc, 7705 SARM/ME, 7705 SARW, and 7705 SARWx can also be
configured with a transparent clock.
Synchronization management
You can use the 5650 CPAM to manage synchronization domains and assign IP path monitors to PTP peers. See
“Synchronization management” in the 5650 CPAM User Guide for more information.
SCADA on the 7705 SAR
The 5620 SAM supports SCADA on the 7705 SAR8 and 7705 SAR18, Release 6.1 R1 or later. SCADA is an
industrial data management system that monitors and controls IEDs. SCADA systems use a master and slave
architecture with a single master supporting multiple slaves, or RTUs. The master sends a broadcast to query all
slave IEDs, and only the addressed slave responds to the query.
SCADA MDDB
A SCADA MDDB system uses a central data bridge to broadcast queries from the master to all slaves using serial
RS232 links. Only the addressed slave responds by sending data back to the bridge. In an inactive state, all slaves
transmit all ones back to the master. As the slaves normally transmit all ones, when a slave responds to a master
request and transmits valid data, the valid data is transmitted to the master through the bridge.
In a SCADA MDDB network using 7705 SAR devices, each remote location has a 7705 SAR8 or 7705 SARH with
an RS232 asynchronous link connected to a slave IED. The RS232 traffic is converted to a 64 kb/s Cpipe using
HCM subrate multiplexing. All slaves are connected to a central SCADA ISC. The SCADA ISC terminates on the
Cpipe and recovers the data from the HCM frame before sending the data to the bridge. The SCADA master is
connected to the bridge by an RS232 link. This link can be local, or remote with a second 7705 SAR SDI card. See
section 9.8 for information about the ISC. See Procedure 1614 for more information about configuring SCADA on the
7705 SAR.
The SCADA MDDB system supports 16 bridges per card, and up to 30 slaves per bridge, with up to 480 slaves per
ISC. Larger bridges can be built by cascading bridges within a single ISC or by cascading up to ten ISCs.
Redundancy
Most SCADA systems have redundant masters where both masters monitor all traffic but only one master transmits
at a time. The 7705 SAR SCADA system supports duplicated linksone to each master. Each bridge has two
branches that connect to the master. During creation, the bridge supports two master links with only one being
active. If redundancy is required, the second link can be manually configured and activated by forcing a switchover.
Data from the bridge to the master is broadcast to both masters. The switchover allows only one master to access
the bridge at a time. The 7705 SAR does not support automatic switchover capability.
Branch squelch
During SCADA system operations, it is not uncommon for a single slave to lock up and continue to send data after
the allotted response time and to lock up the bridge so no other slaves can respond. To resolve this issue, the bridge
monitors the incoming HCM frames for valid data. After a userselectable period of up to 2 min, selectable in 1 s
increments, incoming data from the slave is overridden, all ones are transmitted to the bridge, and an alarm is raised.
This operation frees the bridge to continue to monitor the other slaves. To put the bridge into the normal state, you
must configure a squelch reset because automatic reset is not available. If the slave is still locked up and sending
data, the same sequence is followed and continues until the issue is resolved. The squelch functionality is
configurable on a perbridge basis with thedefault state being squelch disabled. See Procedure 1614 for more
information about configuring a squelch reset.
Power management on the 7950 XRS
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 145/269
06.07.2017 Device management
The 5620 SAM supports configuring power management zones on 7950 XRS nodes, and power priority values on
MDA cards installed on 7950 XRS nodes. Each MDA and APEQ provisioned on 7950 XRS nodes is associated with
a power management zone, and during startup MDAs with higher power priority values are started first. You can view
information and collect statistics about power availability and shedding using the 5620 SAM.
See Procedure 1625 for information about configuring a power management zone. See Procedure 1640 for
information about configuring power priority values on an MDA. See the 5620 SAM Statistics Management Guide for
information about gathering power statistics using the 5620 SAM.
Detailed information about power usage is available on the power management zone, shelf, card slot, and daughter
card slot configuration forms for 7950 XRS nodes. Use the Hardware Environment tab to view information about
power usage.
Reboot hold
The Reboot Hold option in a contextual menu instructs the selected standby SF or CPM module to gracefully shut
down. The module remains shut down until instructed to reboot by another operation, such as the Reboot option.
16.3 Working with card and card slot objects
When you click on the plus sign beside a shelf object, the card slots in the shelf appear in the navigation tree. They
can appear as empty card slots when a card is not provisioned for the slot.
Card slot objects for the OS 6250, OS 6400, OS 6450, OS 6850, OS 6850E, and OS 6855 appear automatically
when a physical device exists because the entire device is represented by a card slot object and no daughter cards
are associated with these devices.
Card slots can be configured with CMM or Ethernet card types for the OS 9600, OS 9700, OS 9800, OS 9700E, and
OS 9800E devices, but there are no daughter cards associated with these devices.
When the 5620 SAM discovers a 7210 SAS or 7705 SARF, the integrated IOM and daughter card objects appear
automatically in the navigation tree.
When the 5620 SAM discovers a supported PAC FP3 IMM in a card slot, the daughter cards and ports appear
automatically in the navigation tree. Daughter cards and ports that are discovered in this way cannot be manually
deleted.
Choose Configure Card from the contextual menu of the object and assign a supported card type for the slot. The
Assigned Card Type parameter lists the card types can be assigned to the card slots.
Some card types can be preprovisioned in a slot before the card is installed in the chassis. A card and daughter card
must be provisioned before a port can be configured.
When a card is first configured, the administrative state can be down. The resource is not operationally up until the
card is equipped and the administrative state is up. A card can only be provisioned in a slot that is vacant, and no
other card can be provisioned (configured) for that specific slot.
The Remove Card option in a contextual menu deletes the card from the slot when the slot and everything contained
in the slot is changed to administratively down.
To reconfigure a slot position, delete the card currently in the slot and configure the new card type added to the slot.
A card can only be provisioned in a slot when the card type is allowed in the slot.
Note You can also reconfigure a slot position by changing the chassis mode. The chassis mode
determines the minimum card requirements. See section 16.2 for more information about chassis
modes.
For example, if a 2 x 10Gig MDA IOM 2 card is installed in the chassis that is running in chassis
mode B, the card behaves as a 2 x 10Gig MDA IOM Card, B. You can upgrade the chassis mode to
C to make the IOM card behave as a 2 x 10Gig MDA IOM 2 card.
You can configure forwarding plane properties on the properties forms for IOM 3, IMM, and XCM cards. IOM 3 and
IMM cards support one forwarding plane, and XCM cards support two forwarding planes — one for each XMA card
slot.
Note 1 You cannot configure a forwarding plane on an XCM card until you have provisioned the
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 146/269
06.07.2017 Device management
corresponding XMA card.
Note 2 You cannot remove a provisioned XMA card when any of the following is true on the
corresponding XCM forwarding plane:
Egress WRED queue control is administratively enabled
Access ingress queue groups are configured
Network ingress queue groups are configured
The Dynamic Enforcement Policer Pool Size parameter is configured with a nonzero value
Card provisioning and chassis modes
The behavior of the installed card depends on the chassis mode that has been configured on the device. Table 163
describes the behavior of the provisioned (configured) card types and installed cards in each chassis mode.
Table 163 Behavior of installed IOM cards
Provisioned Installed Behavior
card type card type
2 x 10Gig 2 x 10Gig The IOM card appears and behaves at the scaling limits of the 2 x 10Gig
MDA IOM MDA IOM MDA IOM.
2 x 10Gig The IOM card appears and behaves as a 2 x 10Gig MDA IOM. The
MDA IOM 2 x 10Gig MDA IOM Card, B is fully backwardcompatible with the 10
Card, B Gig MDA IOM.
2 x 10Gig The IOM card appears and behaves as a 2 x 10Gig MDA IOM. The
MDA IOM 2 x 10Gig MDA IOM 2 is fully backwardcompatible with the 10Gig
2 MDA IOM.
2 × XP The IOM card appears and behaves as a 2 x 10Gig MDA IOM. The
MDA IOM 2 x XP MDA IOM is fully backwardcompatible with the 10Gig MDA
3 (1) IOM.
2 x 10Gig 2 x 10Gig The IOM card fails because the minimum card requirements are not met.
MDA IOM MDA IOM
Card, B
2 x 10Gig The IOM card appears and behaves at the scaling limits of the 2 x 10Gig
MDA IOM MDA IOM Card, B.
Card, B
2 x 10Gig The IOM card appears and behaves as a 2 x 10Gig MDA IOM Card, B.
MDA IOM The 2 x 10Gig MDA IOM 2 is fully backwardcompatible with the 10Gig
2 MDA IOM Card, B.
2 × XP The IOM card appears and behaves as a 2 x 10Gig MDA IOM Card, B.
MDA IOM The 2 x XP MDA IOM 3 is fully backwardcompatible with the 10Gig
3 (1) MDA IOM Card, B.
2 x 10Gig 2 x 10Gig The IOM card fails because the minimum card requirements are not met.
MDA IOM 2 MDA IOM
2 x 10Gig The IOM card fails because the minimum card requirements are not met.
MDA IOM
Card, B
2 x 10Gig The behavior of the card depends on the operational chassis mode:
MDA IOM 2 x 10Gig MDA IOM in chassis mode A
2 2 x 10Gig MDA IOM Card, B in chassis mode B
2 x 10Gig MDA IOM 2 in chassis mode C and D
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 147/269
06.07.2017 Device management
2 × XP The behavior of the card depends on the operational chassis mode:
MDA IOM 2 x 10Gig MDA IOM in chassis mode A
3 (1) 2 x 10Gig MDA IOM Card, B in chassis mode B
2 x 10Gig MDA IOM 2 in chassis mode C and D
2 × XP MDA 2 x 10Gig The IOM card fails because the minimum card requirements are not met.
IOM 3 MDA IOM
card (1)
2 x 10Gig The IOM card fails because the minimum card requirements are not met.
MDA IOM
Card, B
2 x 10Gig The IOM card fails because the minimum card requirements are not met.
MDA IOM
2
2 × XP The behavior of the card depends on the operational chassis mode:
MDA IOM 2 x 10Gig MDA IOM in chassis mode A
3 (1) 2 x 10Gig MDA IOM Card, B in chassis mode B
2 x 10Gig MDA IOM 2 in chassis mode C
2 x XP MDA IOM 3 in chassis mode D. With mixed mode enabled
for 7750 SR, only the IPv6 features of the IOM3 card are enabled,
but no other IOM3 features are available.
2 × XP MDA 2 x 10Gig The IOM card fails because the minimum card requirements are not met.
IOM 3, B MDA IOM
card (1)
2 x 10Gig The IOM card fails because the minimum card requirements are not met.
MDA IOM
Card, B
2 x 10Gig The IOM card fails because the minimum card requirements are not met.
MDA IOM
2
2 × XP The behavior of the card depends on the operational chassis mode:
MDA IOM 2 x 10Gig MDA IOM in chassis mode A
3 (1) 2 x 10Gig MDA IOM Card, B in chassis mode B
2 x 10Gig MDA IOM 2 in chassis mode C
2 x XP MDA IOM 3 in chassis mode D. With mixed mode enabled
for 7750 SR, only the IPv6 features of the IOM3 card are enabled,
but no other IOM3 features are available.
Note
1. Also applies to any IMM
16.4 Working with daughter card objects
After the card is created in the card slot you can create and configure MDAs, also known as daughter card objects, in
the daughter card slot that appears when you click on the plus sign beside the card object. The daughter card slots in
the card appear in the navigation tree. They appear as empty daughter card slots when a daughter card is not
provisioned for the slot. When a daughter card is provisioned for the slot, it is identified.
See the appropriate device section in chapter 9 for devicespecific daughter card information.
A 5620 SAM license allows the management of a specific number of MDAs for each device type. You can purchase
additional MDA capacity as required. MDAs fall into two licensing categories: premium and standard. Generally, non
highperformance MDA cards are considered standard. All IMM, HSMDA, XMDA, and XP MDA cards are premium.
Each IMM card is associated with a platform, and counts towards the licensed IMMs for that platform regardless of
where it is installed. For example, a 7750 SR IMM installed on a 7450 ESS is counted as a premium 7750 SR MDA
for the purposes of licensing. Enabling or disabling mixed mode does not change the associated platform type of a
card.
Note After the 5620 SAM discovers the number of premium MDAs allowed by the license, the 5620
SAM can no longer discover 7705 SAR8, 7705 SAR18, 7710 SR, and 7450 ESS devices.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 148/269
06.07.2017 Device management
SAM can no longer discover 7705 SAR8, 7705 SAR18, 7710 SR, and 7450 ESS devices.
IMM daughter cards
The IMM card integrates IOM 3 and high bandwidth MDA functionality on a single card that fits into existing IOM
slots. When you configure the IMM the integrated MDAs are automatically configured. The 5620 SAM equipment tree
displays the IMM with two daughter cards, each having half of the total number of ports supported by the IMM.
Each daughter card object contains a number of ports that are specific to the type of service required. The port
objects are created automatically under the daughter card but they must be configured based on the function served
by the port; for example, as an access interface for a VPRN service.
You can associate policies to daughter cards. Network buffer policies are used to create and edit QoS buffer pool
resources on egress network ports, channels, and ingress ports. Ingress and egress network ports and channels
have a dedicated buffer pool for egress queuing. The ingress and egress network traffic is handled by a buffer pool at
the ingress and a buffer pool at the egress.
You can also configure multicast path management on an IMM daughter card. See chapter 51 for more information.
MDA modes for the 7705 SAR
The 5620 SAM allows you to configure the MDA mode of some MDA types on the 7705 SAR. The MDA mode on a
channelized ASAP determines the capabilities that are available to the MDA. The MDA mode on an XMDA
determines the number of ports that are available to the MDA. See the MDA Mode parameter description for more
information.
16.5 Working with bundle objects
Bundle objects can be configured as multilink PPP, IMA group, or FR group bundles. Multilink PPP, IMA group, and
FR group bundles appear as Bundle objects under the daughter card object if the daughter card has been configured
as a channelized MDA.
APS Bundle objects appear in the navigation tree as children of the shelf object. APS Bundle objects are configured
to protect multilink PPP and IMA bundles on channelized ASAP MDAs. See chapter 40 for more information on APS
and APS bundles.
Multilink PPP bundles
You can create MLPPP bundles to:
bundle DS0 channels together to be used as a SAP
provide a mechanism to distribute data across multiple links to achieve higher bandwidth
The following general rules apply to multilink bundles.
Table 164 lists the maximum number of multilink bundles that can be created on each MDA.
DS0 channels can be aggregated on a single MDA only.
Up to 8 members can be added to a bundle.
The Encap Type parameter of a member cannot be set to FR.
A DS0 channel can host only one SAP.
If a channel is being used as a SAP, it cannot be added to a bundle.
Table 164 Multilink bundle configuration maximum
MDA Bundle maximum
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 149/269
06.07.2017 Device management
MDA Bundle maximum
4 x Channelized OC3/OC12 ASAP SFP MDA 32
All MDAs other than Channelized ASAP MDAs 56
1 x OC12 Deep Channel 56
4 x OC3 Deep Channel
12 x DS3/E3 Deep Channel
4 x DS3/E3 Deep Channel
8 x DS1/E1 Channel CMA (7710 SR)
4 x Channelized DS3/E3 ASAP MDA 112
4 x Channelized OC3 ASAP 256
1 x Channelized OC12 ASAP
12 x Channelized DS3/E3 ASAP
See Procedure 1648 to create an MLPPP bundle.
IMA group bundles
IMA group bundles combine ATMencapsulated DS0 channel groups into a single ATM interface. The following
general rules apply to IMA group bundles.
IMA group bundles can only be created on:
channelized ASAP MDAs with SDH or SONET framing the 7750 SR or 7710 SR
ATM DS1/E1 CMA on the 7710 SR
channelized DS1/E1 ASAP daughter cards on the 7705 SAR
The encapsulation type of the DS0 group channel must be ATM.
The Clock Source parameter of the DS1 channel must be set to NodeTimed.
Table 165 lists the maximum number of IMA group bundles that can be created on each MDA.
IMA group members must be on the same MDA.
Table 165 IMA group bundle configuration maximums
Device MDA Bundle maximum
7750 SR All MDAs other than channelized ASAP MDAs 56
7750 SR 4 x Channelized DS3/E3 ASAP MDA 112
7710 SR
7750 SR 4 x Channelized OC3 ASAP 256
7710 SR 1 x Channelized OC12 ASAP
12 x Channelized DS3/E3 ASAP
7710 SR 8 x ATM DS1/E1 CMA 8
7705 SAR 16 x Channelized DS1/E1 ASAP 8
7705 SAR 2 x Channelized OC3/STM1 ASAP 16
See Procedure 1646 to create an IMA group bundle.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 150/269
06.07.2017 Device management
FR group bundles
FR group bundles are used to fragment lower priority DLCI frames to minimize jitter and delay on higher priority DLCI
frames. The following general rules apply to FR group bundles.
FR group bundles can only be created on channelized ASAP MDAs.
FRF12 cannot be enabled on a SAP that is using an FR group bundle.
DS0 channel groups must have all their timeslots selected and have their encapsulation type set to FR to be
configured as bundle members.
Note You can configure a maximum of 128 FR group bundles on an MDA.
See Procedure 1644 to create an FR group bundle.
16.6 Workflow to manage shelf objects
The following workflow describes the sequence of highlevel tasks required to manage and configure shelf objects
and shelf object children. This workflow assumes that the physical devices have been installed, commissioned, and
discovered. See chapter 10 for more information about device commissioning. See chapter 11 for more information
about device discovery.
Note Shelf objects and shelf object children can be accessed using the equipment navigation tree.
See chapter 5 for more information about using the equipment navigation tree.
1. As required, perform the following procedures to configure shelf objects.
a. Configure the chassis mode of a device. See Procedure 161.
b. Configure a VWM shelf for a 7210 SAS device. See Procedure 162.
c. Configure drycontact sensor monitoring. See Procedure 163.
d. Configure the IMM card type on a 7210 SASR. See Procedure 164.
e. Configure switch fabric multicast ingress replication rates. See Procedure 165.
f. Configure IMPM overrides. See Procedure 166.
g. Enable mixed mode on a 7450 ESS or 7750 SR device. See Procedure 167.
h. Configure timing synchronization. See Procedure 168.
i. Configure an IEEE 1588 clock on a 7705 SAR. See Procedure 169.
j. Configure an IEEE 1588 PTP port on a 7705 SAR. See Procedure 1610.
k. Configure system time on a 7705 SAR. See Procedure 1611.
l. Configure SNTP on a 7705 SAR. See Procedure 1612.
m. Configure NTP on supported device types. See Procedure 1613.
n. Configure SCADA on a 7705 SAR. See Procedure 1614.
o. Configure a 7705 SAR microwave link. See Procedure 1615.
p. Configure a 7705 SAR MW link member. See Procedure 1616.
q. Configure auxiliary alarm definitions on a 7705 SAR. See Procedure 1617.
r. Configure the IEEE 1588 PTP clock on supported devices. See Procedure 1618.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 151/269
06.07.2017 Device management
s. Configure the IEEE 1588 PTP peer on supported devices. See Procedure 1619.
t. Manage OmniSwitch running configuration. See Procedure 1620.
u. Configure OmniSwitch health monitoring. See Procedure 1621.
v. Configure a CCM on a 7950 XRS20. See Procedure 1622.
w. Configure power supply trays. See Procedure 1624.
x. Configure power management zones on a 7950 XRS. See Procedures 1625, 1626, and 1627.
2. Assign a card type to a chassis slot. See Procedure 1628.
3. As required, configure the card and card slot objects as follows:
a. Configure an egress WRED queue control on an IOM 3 or IMM forwarding plane. See Procedure 1629.
b. Configure IMPM on a 2 × XP MDA IOM 3 or IMM forwarding plane. See Procedure 1630.
c. Enable named pool mode. See Procedure 1633.
d. Configure OmniSwitch stacks. See Procedure 1637.
e. Configure an OmniSwitch CPU temperature threshold. See Procedure 1638.
f. Configure a CPM on a 7950 XRS. See Procedure 1639.
4. As required, configure daughter card objects as follows:
a. Configure an MDA. See Procedure 1640.
b. Configure IMPM on an MDA. See Procedure 1641.
c. View operational multicast channel properties on an MDA. See Procedure 1642.
d. Configure a module card on the 7705 SARM/ME. See Procedure 1643.
5. As required, create or modify bundle objects as follows:
a. FR group bundle. See Procedures 1644 and 1645.
b. IMA group bundle. See Procedures 1646 and 1647.
c. MLPPP bundle. See Procedures 1648 and 1649.
d. MLPPP bundle for multiclass service transmission. See Procedure 1650.
e. MLPPP bundle as a network interface on a channelized ASAP MDA. See Procedure 1651.
16.7 Shelf object configuration procedures
Use the following procedures to configure shelf objects using the navigation tree.
Procedure 161 To configure the device chassis mode
The device chassis mode must be set to indicate the minimum IOM or IMM card type that is initialized by the NE.
This also determines other features available to the system. The behavior of the installed card depends on the
chassis mode configured on the device. See Sections 16.2 and 16.3 for more information about chassis modes and
card types.
1. On the equipment tree, expand Network NE Shelf.
2. Rightclick on the Shelf object and choose Properties. The Shelf (Edit) form opens.
3. Configure the parameters:
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 152/269
06.07.2017 Device management
Administrative Mode
If you downgrade the administrative chassis mode, the device must be rebooted to change the
operational chassis mode.
Force Mode
Forcing a chassis mode change does not change the operational chassis mode unless there is a
compatible card type equipped on the device. See Section 16.2 for more information about the minimum
card type that must be installed for each chassis mode.
4. Save your changes and close the form.
Procedure 162 To configure a VWM shelf for a 7210 SAS
The 1830 VWM is an addon optical module that provides WDM capability to 7210 SAS devices. The 7210 SASE,
7210 SASM, and 7210 SASX support one 1830 VWM module attached to the USB port. The 7210 SASMxp, 7210
SASR, and 7210 SAST support up to four 1830 VWM modules connected to the OMC port. See the 7210 SAS
documentation for more information.
1. On the equipment tree, expand Network NE VWM Shelves.
2. Rightclick on VWM Shelves and choose Configure VWM Shelf. The VWM Shelf (Create) form opens.
3. Configure the required parameters.
Configure the Shelf ID parameter to match the hardware shelf ID value that is preset on the rotary dial of the
1830 VWM module. If the Shelf ID parameter does not match the hardware shelf ID, the correct manufacturer
details will not appear on the VWM Shelf form.
Some chassis types support a value of zero for the Shelf ID parameter. When a value of zero is configured,
the VWM Type parameter is set to DWDMA (DWDMactive) by default and is not configurable.
4. On the equipment tree, expand the VWM Shelves object to the VWM Card Slot level.
5. Rightclick on a VWM Card Slot object and choose Configure Card. The Configure VWM Card Slot form
opens.
6. Configure the Assigned VWM Card Type parameter.
The Assigned VWM Card Type parameter provides a way to check if the equipped card type is acceptable. An
alarm is raised when the equipped VWM card type in the module does not match the Assigned VWM Card
Type.
7. Save your change and close the form.
8. Repeat steps 5 to 7 for each additional card slot that you need to configure.
9. Save your changes and close the form.
Procedure 163 To configure 7210 SAS dry contact sensors
You can enable dry contact sensors on the alarm interface port of the 7210 SASE, 7210 SASM, 7210 SASMxp,
7210 SASR, 7210 SAST, and 7210 SASX, or the console port of the 7210 SASD and 7210 SASK. When an
external alarm condition is present, the 7210 SAS NE sends an alarm with a userconfigured message to the 5620
SAM. See the NE documentation for more information about dry contact sensors.
1. If you are configuring a 7210 SASD or 7210 SASK, perform the following steps. Otherwise, go to step 2.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 153/269
06.07.2017 Device management
i. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form
opens.
ii. Enable the Console Alarm Input parameter.
Note The console port is not available for other purposes when the Console Alarm Input
parameter is enabled.
iii. Save your change and close the form.
2. On the equipment tree, expand Network NE Shelf.
3. Rightclick on the Shelf object and choose Properties. The Shelf (Edit) form opens.
4. Click on the External Alarms tab. A list of dry contacts is displayed.
5. Choose one of the dry contacts and click Properties. The Dry Contact (Edit) form opens.
6. Configure the required parameters and click OK. The Dry Contact (Edit) form closes.
7. Repeat steps 5 and 6 as required to configure additional dry contacts.
Note You can configure only one dry contact for the 7210 SASD and 7210 SASK.
8. Save your changes and close the form.
Procedure 164 To configure the IMM card type on a 7210 SASR
2. Rightclick on the Shelf object and choose Properties. The Shelf (Edit) form opens.
3. Configure the Allow IMM Family Type parameter.
The Allow IMM Family Type parameter requires an NE reboot to take effect. The Operational IMM Family Type
parameter displays the card type currently in effect for the shelf.
4. Save your changes and close the form.
Procedure 165 To configure switch fabric multicast ingress replication rates
Perform this procedure to configure the total multicast replication rates for primary and secondary ingress paths for
each switch fabric multicast plane.
1. On the equipment tree, expand Network NE Shelf.
2. Rightclick on the Shelf object and choose Properties. The Shelf (Edit) form opens.
3. Click on the Multicast tab.
4. Configure the required parameters.
5. Save your changes and close the form.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 154/269
06.07.2017 Device management
Procedure 166 To configure IMPM overrides
See Procedure 1630 to configure IMPM on an IOM or XCM. See chapter 51 for more information on multicast path
management.
1. On the equipment tree, expand Network NE Shelf.
2. Rightclick on the Shelf object and choose Properties. The Shelf (Edit) form opens.
3. Click on the Multicast tab.
4. Configure the required parameters in the MMRP Ingress Multicast Path Management Override panel.
Note The Operational Mode parameter is not configurable. If the Administrative Mode
parameter is changed, the value of the Operational Mode parameter changes to indicate the
same as the Administrative Mode, after the system is rebooted.
5. Save your changes and close the form.
Procedure 167 To enable mixed mode
Enabling mixed mode only applies to 7450 ESS and 7750 SR devices.
Enabling mixed mode on a 7450 ESS6, 7450 ESS6v, 7450 ESS7, or 7450 ESS12 device allows the support of
features on the IOM3XP and associated MDAXPs or IMMs.
7750 SR7 and 7750 SR12 devices also support mixed mode, which allows you to enable IPv6 in chassis mode A or
B, without having to upgrade an entire chassis. Slots with network ports, and ports that require IPv6 support, can
then be selectively upgraded for IOM3XPs or IMMs.
Note You cannot enable mixed mode on a 7750 SR7 or 7750 SR12 that has a provisioned ISA TMS
MDA.
2. Rightclick on the Shelf object and choose Properties. The Shelf (Edit) form opens.
3. Enable the Mixed Mode State on Chassis Enabled parameter.
4. Save your change and close the form.
Procedure 168 To configure timing synchronization
2. Rightclick on the Shelf object and choose Properties. The Shelf (Edit) form opens.
3. Click on the Timing tab and configure the required parameters.
Note The displayed parameters vary depending on the NE type, release, and the settings of
other parameters.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 155/269
06.07.2017 Device management
You must enable the Synchronous Ethernet parameter on the daughter card in order to configure the Timing
Reference One and Timing Reference Two panels for SyncE. See Procedure 1640.
When you select a port as a timing reference for SyncE, the Port Clock Mode parameter for the port must be
set to Manual Slave. See Procedure 171. Other restrictions may also apply for SyncE port selection,
depending on the device. See the NE documentation for more information.
You can enable the Administrative State parameter in the PTP panel only when the Frequency Source and
Oper Frequency Source parameters are both set to Ptp on the IEEE 1588 PTP Clock form; see Procedure 16
18.
For the 7210 SASD ETR, 7210 SASM, and 7210 SASX, PTP and SyncE are mutually exclusive. Consider
the following when configuring timing synchronization on these 7210 SAS NEs:
You can only choose PTP as an option for First Timing Reference Input when the Administrative State
parameter in the PTP panel is set to Up.
You cannot configure the Second Timing Reference Input parameter when the First Timing Reference
Input parameter is set to PTP.
You can only set the Administrative State parameter in the PTP panel to Up when the Administrative
State parameter in both the Timing Reference One and Timing Reference Two panels is set to Down.
You can only set the Administrative State parameter in the Timing Reference One and Timing
Reference Two panels to Up when the Administrative State parameter in the PTP panel is set to Down.
4. Save your changes and close the form.
Procedure 169 To configure an IEEE 1588 PTP clock on a 7705 SAR
You can only configure the IEEE 1588 PTP clock on a 7705 SAR that is configured as an IEEE 1588 PTP client. See
Procedure 168 for information about how to configure the NE as a PTP client.
1. On the equipment tree, expand Network NE.
2. Rightclick on the NE and choose Properties. The Network Element (Edit) form opens.
3. Click on the IEEE PTP Clock tab and click Create. The IEEE 1588 PTP Clock (Create) form opens.
4. Configure the required parameters.
5. Select a clock MDA for the PTP clock.
6. Select a source interface for the PTP clock.
7. Click Apply to save your changes.
8. To turn up PTP ports on the IEEE 1588 PTP clock:
i. Choose a PTP port from the PTP Port panel and click Properties. The IEEE 1588 PTP Port (Edit) form
opens.
ii. Configure the Admin State parameter and click OK.
9. Save your changes and close the forms.
Procedure 1610 To configure an IEEE 1588 PTP port on a 7705 SAR
You can configure the IEEE 1588 PTP port on a 7705 SAR that is configured as an IEEE 1588 PTP client. See
Procedure 168 for information about how to configure a 7705 SAR as a PTP client.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 156/269
06.07.2017 Device management
2. Rightclick on the Shelf object and choose Properties. The Shelf (Edit) form opens.
3. Click on the Timing tab and click on PTP Port Properties. The PTP Port (Edit) form opens.
4. Configure the required parameters.
Note The Master 1 and 2 clock recovery statistics are available on the Recovered Clock
History Master tabs.
5. Save your changes and close the forms.
Procedure 1611 To configure system time on a 7705 SAR
You can configure system time updates, based on priority values. There are five system time reference types: PTP,
GPS, NTP, SNTP, and the default value, Holdover. PTP is supported on the 7705 SARA, 7705 SARA T1/E1, 7705
SARH, 7705 SARHc, 7705 SARM, 7705 SARM ASAP, 7705 SARW, and 7705 SARWx. GPS is supported on
the 7705 SARH and 7705 SARWx GPS variants.
Time references become qualified for use when they provide a valid input into system time. Of the qualified time
references, the highest priority, which is the lowest numerical priority value, becomes the selected time reference. If
all five time references are operationally up, the order of priority for the selected time reference is PTP or GPS,
depending on which one has the lowest numerical priority value, then NTP, SNTP, and Holdover. When PTP or GPS
is the selected time reference, the operational states of NTP and SNTP are automatically down.
1. Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view.
2. Rightclick on the 7705 SAR on which you need to configure system time, and choose Properties.
3. Click on the Time tab and on the Input References tab.
4. Click Create. The Time References (Create) form opens.
5. Configure the required parameters.
If you configure the Ref Type parameter as PTP, a PTP clock and priority value must be assigned. If you
configure GPS, a GPS port and priority value must be assigned. See Procedure 169 for more information
about configuring a PTP clock on a 7705 SAR.
6. Save your changes and close the form.
Procedure 1612 To configure SNTP on a 7705 SAR
SNTP is a compact, clientonly version of NTP. The 7705 SAR supports SNTP in both unicast client modes and
broadcast client modes. SNTP can only receive the time from SNTP or NTP servers and cannot be used to provide
time services to other systems.
1. Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view.
2. Rightclick on the 7705 SAR on which you need to configure SNTP, and choose Properties.
3. Click on the SNTP tab and configure the required parameters on the General tab.
4. Configure an SNTP server.
i. Click on the Server tab.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 157/269
06.07.2017 Device management
ii. Click Create or select a server and click Properties. The SNTP Server (Create|Edit) form opens.
iii. Configure the required parameters.
5. Save your changes and close the form.
Procedure 1613 To configure NTP on supported devices
NEs can act as NTP servers, clients, or peers.
The 7705 SAR acts only as an NTP client and not as an NTP server. The 7705 SAR does not support NTP on a
VPRN service.
Note 1 For the 9500 MPR, if the main and spare NTP servers are defined with the same IP address
in NEtO, only the IP address for the main server will be displayed in the 5620 SAM. Main and primary
NTP servers with the same IP address should be avoided.
Note 2 For any failed operation related to NTP server addition or modification, you must close the
current GUI session on the NTP tab and reopen it before proceeding. This action removes the failed
entry from the GUI cache so that it is not applied again.
Note 3 The tabs and parameters that are configurable vary depending on the NE.
1. Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view.
3. Rightclick on the NE and choose Properties. The Network Element (Edit) form opens.
4. If you are configuring a 7705 SAR, Release 6.2 R1 or earlier, or a 9500 MPR, click on the NTP tab and
configure the NTP State parameter, go to step 7. If you are configuring a 7705 SAR, Release 7.0 or later, go
to step 5.
You must set the NTP State parameter to Enabled in order to configure the remaining NTP parameters.
5. Configure the NTP State parameters on the General tab.
You must set the NTP State parameter to Enabled in order to configure the remaining NTP parameters.
When you change the NTP State parameter from Disabled to Enabled, you must click Apply and confirm the
action in order to activate the NTP tab.
6. Click on the NTP tab. The General tab is displayed.
7. Configure the required parameters.
8. Click on the Authentication tab and perform the following:
i. Click Create. The Network Time Protocol Authentication (Create) form opens.
ii. Configure the required parameters.
The values of the Authentication Key Id and Authentication Key parameters must be the same on the
reference clock server and the NE.
iii. Click OK and confirm to close the form.
9. Click on the Server tab and perform the following:
i. Click Create. The Network Time Protocol Server (Create) form opens.
ii. Configure the required parameters.
Note When the PTP Server parameter is enabled, the IP Address parameter becomes
nonconfigurable. The address that is displayed in that field is not the PTP server
address, it is an internal reference.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 158/269
06.07.2017 Device management
The Authentication Key Id and NTP Version parameters are only displayed when the PTP Server
parameter is not enabled.
iii. Click OK and confirm to close the form.
If you are configuring a 9500 MPR, go to step 15.
10. Click on the Peer tab and perform the following:
i. Click Create. The Network Time Protocol Peer (Create) form appears.
ii. Configure the required parameters.
iii. Click OK and confirm to close the form.
11. Click on the Broadcast tab and perform the following:
i. Click Create. The NTP Broadcast (Create) form opens.
ii. Configure the Router Instance parameter.
iii. Click Select beside the Interface Name parameter and select a source interface.
iv. Configure the required parameters.
A warning message is displayed if the Direction parameter is set to transmit when the NTP Server
parameter is not enabled in step 7.
When the value of the Direction parameter is set to transmit, the Authentication Key Id, NTP Version,
and Time to Live parameters are displayed.
v. Click OK and confirm to close the form.
12. Click on the Multicast tab and perform the following:
i. Click Create. The NTP Multicast (Create) form opens.
ii. Configure the required parameters.
When the value of the Direction parameter is set to transmit, the Authentication Key Id and NTP
Version parameters are displayed.
iii. Click OK and confirm to close the form.
13. Click on the Associations tab and perform the following to view the properties of the NTP associations, if
required:
i. Click Search. A list of NTPassociated NEs appears.
ii. Choose an NE and click Properties. The Network Time Protocol Associations (View) form opens. You
can view information about the status and mode of the NTP server.
iii. Close the Network Time Protocol Associations (View) form.
14. Click on the Clients tab and perform the following to view the properties of the NTP clients, if required:
i. Click Search. A list of NTP clients appears.
ii. Choose an NTP client and click Properties. The Network Time Protocol Clients (View) form opens. You
can view information about the status and mode of the NTP client.
iii. Close the Network Time Protocol Clients (View) form.
15. Save and close the forms.
Procedure 1614 To configure SCADA on a 7705 SAR
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 159/269
06.07.2017 Device management
Perform this procedure to configure SCADA on a 7705 SAR8 or 7705 SAR18, Release 6.1 R1 or later. To configure
SCADA, an ISC must be installed in the daughter card slot. See section 9.8 for more information about the ISC.
1. Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view.
3. Rightclick on the Shelf object and choose Properties. The Shelf (Edit) form opens.
4. Click on the SCADA tab.
5. Select one or more ports that you want to configure as a SCADA bridge, and click Properties. The SCADA
MDDB (Edit) form opens.
6. Configure the required parameters.
The Squelch Timeout (seconds) parameter only appears when you enable the Squelch Enable parameter.
7. Configure SCADA branches. You can create up to 32 branches per bridge.
i. Click on the Branches tab.
ii. Click Create. The SCADA Branch (Create) form opens.
iii. Configure the required parameters.
iv. Click OK and confirm to close the form.
v. Configure more SCADA branches, as required.
You can add SCADA branches as SAPs on an L2 access interface on a VLL Cpipe or Epipe service
site. See Procedure 7420 for more information.
8. Click OK to save the configuration.
9. To activate or deactivate a SCADA bridge, select one or more SCADA bridges listed on the Shelf (Edit) form.
a. Click Turn Up and confirm to activate the SCADA bridge.
b. Click Shut Down and confirm to deactivate the SCADA bridge.
10. Save and close the form.
Procedure 1615 To configure a 7705 SAR MW link
Perform this procedure to configure a microwave link on a 7705 SAR8 or 7705 SAR18. To support an MW link, the
NE must be configured with 4 × MWA Gig Ethernet (2 TX, 2 SFP) + 4 × Gig Ethernet SFP daughter cards. See
Procedure 1640 for information about how to configure daughter cards.
Note The 5620 SAM supports the creation of an MW link in 1+0 protection mode and 1+1 protection
mode. You can only configure 1+1 protection on an NE in network mode.
1. Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view.
3. Click on the shelf object to expand the tree view.
4. Rightclick on the MW Links item and choose Create MW Link. The Create MW Link (Create) form opens,
with the General tab displayed.
5. Configure the Description parameter, if required.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 160/269
06.07.2017 Device management
6. Click on the MW Link tab.
7. Configure the required parameters in the Hold Time panel.
8. Click on the States tab and configure the Administrative State parameter.
9. Click on the Protection tab and configure the Protection Scheme parameter.
If you choose the value One Plus One Hsb, the Protection form displays additional panels.
10. To configure 1+1 radio protection, configure the required parameters in the Equipment Protection Scheme,
Radio Protection Scheme, and Transmission Protection Scheme panels.
11. Click OK. The MW Link (Create) form closes and the new MW link appears under the MW Links item in the
navigation tree.
12. To modify the MW Link properties, rightclick on the MW link and choose Properties. The MW Link (Edit) form
appears with the General tab displayed.
13. Click on the MW Link tab and configure the required parameters in the Hold Time panel.
Note The Peer IP Address parameter in the Peer Info panel is readonly and is displayed as
follows:
When a 9500 MPRe is in standalone mode, the Peer IP Address displays 0.0.0.0.
When the 9500 MPRe is in single NE mode, the Peer IP Address displays the IP
address of the other end 9500 MPRe if the other end of the radio link terminates on a
9500 MPRe in standalone mode.
When the 9500 MPRe is in single NE mode, the Peer IP Address displays the IP
address of the other end 7705 SAR if the other end of the radio link terminates on a 9500
MPRe in single NE mode.
The Peer IP Address changes only when the 7705 SAR discovers a new peer after the
radio link is operationally up between both 9500 MPRes or when the 7705 SAR reboots.
14. Configure the Peer Discovery parameter in the Peer Discovery panel.
15. Click on the Statistics tab to view statistical information, if required.
16. Save and close the form.
Procedure 1616 To configure a 7705 SAR MW link member
Perform this procedure to configure a 7705 SAR MW link member on the 7705 SAR8 or 7705 SAR18. To support an
MW link and an MW link member, the NE must be configured with 4 × MWA Gig Ethernet (2 TX, 2 SFP) + 4 × Gig
Ethernet SFP daughter cards. See Procedure 1640 for information about how to configure daughter cards.
If you configured 1+1 HSB protection in Procedure 1615, you can configure a main radio and a spare radio for each
MW link. By default, the main radio assumes the active status and the spare radio assumes the standby status.
If you configured 1+1 HSB protection and you want to revert back to 1+0 protection, you must delete the spare radio.
You cannot delete the main radio.
1+1 HSB protection is displayed on the 5620 SAM physical topology map. The protection state is shown on the links,
and 1+1 links are grouped in a common link group. The expansion of links on the physical map displays eight links.
See section 6.2 for more information about the 5620 SAM physical topology maps.
1. Choose Network NE Shelf Card Slot n Daughter Card Slot n Port n/n/n where the port object is the
port that you need to use for the MW link.
Note 1 Only the first four ports on the MDA are microwaveaware.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 161/269
06.07.2017 Device management
Note 2 If a port is associated with an MW link, the port cannot be used as a timing reference.
Also, if a port is already being used as a timing reference, the port cannot be associated with an
MW link member.
2. Rightclick on a port and choose Properties. The Physical Port (Edit) form opens.
3. Configure the Encapsulation Type parameter to be Dot1 Q.
4. Configure the Mode parameter.
Note 1 Setting the Mode parameter to Access allows you to later associate the MW link with
an L2 or L3 access interface for services. Setting the Mode parameter to Access is the typical
setting. Setting the parameter to Network allows you to associate the MW link with a network
interface.
Note 2 1+1 HSB radio protection can only be configured on a port in Network mode.
5. Click OK and confirm to close the form.
6. Create an MW link member:
a. If you configured 1+0 radio protection in Procedure 1615, rightclick on the MW link you created and
choose Create MW Link Member. The Create MW Link Member step form opens.
b. If you configured 1+1 HSB radio protection in Procedure 1615, rightclick on the MW link you created
and choose Create MW Link Main Radio. The Create MW Link Member step form opens.
7. Configure the required parameters on the Specify the Member Properties form.
The Database Filename parameter must be the same name as the database file in the config file of the cflash
directory and must be in a *.tar format.
8. Click Next. The Select Ports form opens.
9. Choose the port from the list and click Finish. Only eligible ports are displayed in the list and only one port per
link is supported.
To configure a main radio, you must choose a port in an odd numbered slot.
10. Select the View the newly created Port Termination check box if you need to view the MW link member
properties, and click Close.
11. To configure a spare radio, rightclick on the MW link where you created the main radio, and choose Create
MW Link Spare Radio. Repeat steps 7 to 10.
To configure a spare radio, you must choose a port in an even numbered slot.
12. Click on the Radio tab. The tab displays information about MPT hardware and the software state of the
connected radio.
13. Associate the MW link with an L2/L3 access interface or a network interface, if required.
i. If you set the MW Link Member port Mode to Access in step 4, you can associate the MW link with a
service, if required.
The MW links can be used in the L2 Access Interfaces of the following service types:
VLL Epipe (see Procedure 7420)
VLL Ipipe (see Procedure 7420)
VPLS (see Procedure 7528)
MVPLS (see Procedure 7528)
The MW links can also be used in the L3 Access Interfaces of the following service types:
VPRN (see Procedure 7769)
IES (see Procedure 7625)
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 162/269
06.07.2017 Device management
The created access interface appears in the list on the L2 Access Interface or L3 Access Interface tab
of the MW Link (Edit) form, as appropriate.
See the specific service chapter and forms when you create the required L2 or L3 access interfaces.
Specify the MW Link Member as the Terminating Port.
ii. If you set the MW Link Member port Mode setting to Network in step 4, the Network Interface tab is
displayed. Click on the tab and then the Create button to create a network interface. The network
interface that you create appears in the list. See Procedure 2810 for more information.
14. Click on the Statistics tab to view radio analog statistical information, if required.
15. Click on the Faults tab to view alarm information, if required.
16. Save and close the form.
Procedure 1617 To configure 7705 SAR auxiliary alarm definitions
Perform this procedure to configure auxiliary alarm definitions for the auxiliary alarms daughter card on a 7705 SAR.
1. Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view.
2. Navigate to the shelf object on which you want to configure auxiliary alarm definitions. The path is Network
NE Shelf.
3. Rightclick on the Shelf object and choose Properties. The Shelf (Edit) form opens.
4. Click on the External Alarms tab.
5. As required, configure auxiliary alarm digital inputs.
i. Click on the Auxiliary Alarm Digital Inputs tab.
ii. Select a digital input from the list and click Properties. The Auxiliary Alarm Digital (Edit) form opens.
iii. Configure the required parameters.
iv. Click OK. The Auxiliary Alarm Digital (Edit) form closes.
v. Repeat steps i to iv to configure more auxiliary alarm digital inputs, as required.
6. As required, configure auxiliary alarm port inputs.
i. Click on the Auxiliary Alarm Port Inputs tab.
ii. Click Create. The Auxiliary Alarm Ports (Create) form opens.
iii. Click Select beside the CLI Name parameter and select a port reference. Only Ethernet ports can be
selected.
iv. Configure the required parameters.
v. Click OK and confirm to close the form.
vi. Repeat steps i to v to configure more auxiliary alarm port inputs, as required.
7. Click on the Auxiliary Alarm Definitions tab on the Shelf (Edit) form.
8. Click Create. The Auxiliary Alarm Definition (Create) form opens.
9. Configure the required parameters.
10. Click on the Inputs tab and configure the required parameters.
11. Click on the Outputs tab and configure the required parameters.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 163/269
06.07.2017 Device management
12. Save and close the forms.
Procedure 1618 To configure the IEEE 1588 PTP clock on a 7210 SAS, 7450
ESS, or 7750 SR
Perform this procedure to configure the IEEE 1588 PTP clock on a device that is configured as an IEEE 1588 PTP
client. See Procedure 168 for information about how to configure a device as a PTP client.
1. Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view.
2. Rightclick on the device where you want to configure the IEEE 1588 PTP clock and choose Properties. The
Network Element (Edit) form opens.
3. Click on the IEEE PTP Clock tab.
4. Select an IEEE 1588 PTP Clock from the list and click Properties. The IEEE 1588 PTP Clock (Edit) form
opens.
5. Configure the required parameters.
At least one IEEE PTP peer must be created before you can set the Admin State parameter to Enabled. See
Procedure 1619.
When the Admin State parameter is set to Enabled, you cannot change the Clock Type, PTP Profile, Domain
or Log sync interval parameters.
For the 7210 SASD ETR, 7210 SASK, 7210 SASM, 7210 SAST, 7210 SAST ETR, and 7210 SASX:
when the Clock Type parameter is set to Boundary, you must set the PTP Profile parameter to IEEE1588
2008.
6. Save and close the forms.
Procedure 1619 To configure the IEEE 1588 PTP peer of a 7210 SAS, 7450
ESS, or 7750 SR
Perform this procedure to configure IEEE 1588 PTP peers for a device that has the IEEE 1588 PTP clock configured.
See Procedure 1618 for information about how to configure the IEEE 1588 PTP clock on a device.
1. Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view.
2. Rightclick on the device where you want to configure the IEEE 1588 PTP clock and choose Properties. The
Network Element (Edit) form opens.
3. Click on the IEEE PTP Clock tab.
4. Choose an entry from the list and click Properties. The IEEE 1588 PTP Clock (Edit) form opens.
5. Click on the IEEE PTP Peers tab.
6. Click Create, or choose an IEEE 1588 PTP peer from the list and click Properties. The IEEE 1588 PTP Peer
(Create|Edit) form opens.
The number of peers that you can create varies depending on the NE. When the limit is reached, the Create
button is not available.
7. Configure the required parameters.
8. Save and close the forms.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 164/269
06.07.2017 Device management
Procedure 1620 To manage an OmniSwitch running configuration
Caution When you reboot an OmniSwitch that is in service it is serviceaffecting. Ensure that the
reboot activity occurs during a maintenance window.
1. Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view.
2. Expand the OmniSwitch object.
3. Rightclick on a device and choose Properties. The Network Element (Edit) form opens.
4. Click on a shelf object. The Shelf (Edit) form opens.
5. Click on the Software Control Module tab.
6. Configure the Command to Apply parameter.
a. If you specify Copy certified to working, configure the Active Timeout parameter.
b. If you specify Reload from working, configure the Delayed Activation Timer parameter.
7. Save and close the form.
Procedure 1621 To configure OmniSwitch health monitoring
The health monitoring function monitors the consumable resources, such as bandwidth and CPU usage of the
OmniSwitch at fixed intervals and collects the current values for each resource being monitored. You can specify the
resource threshold limits. If a resource value is greater or less than the threshold, traps are sent to the 5620 SAM.
1. On the equipment tree, rightclick on the OmniSwitch device for which you want to configure health monitoring
and choose Properties. The Network Element (Edit) form opens.
2. On the Network Element (Edit) form navigation tree, click on a shelf object. The Shelf (Edit) form opens.
3. Click on the Health Monitoring tab and configure the required parameters.
4. Click on the Statistics tab and search for Card Health Stats (Physical Equipment) or Device Health Stats
(Physical Equipment) to view card statistics or chassis statistics. Statistics can also be viewed from the card
level statistics tab.
5. Click on the Faults tab to view alarm information.
6. Save your changes and close the forms.
Procedure 1622 To configure a CCM on a 7950 XRS20
1. On the equipment tree, rightclick on the 7950 XRS20 device for which you want to configure CCM properties
and choose Properties. The Network Element (Edit) form opens.
2. On the Network Element (Edit) form navigation tree, expand the Shelf object.
3. Rightclick on a CCM object and choose Properties. The CCM (Edit) form opens.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 165/269
06.07.2017 Device management
Alternatively, you can open a CCM properties form by rightclicking on the associated CPM object and
choosing View CCM from the contextual menu.
4. To configure a flash memory module:
i. Click on the Flash Memory Modules tab.
ii. Select a flash memory module in the list and click Properties. The Flash Memory (Edit) form opens.
iii. Configure the Administrative State parameter.
iv. Save your changes and close the form.
5. On the CCM Shelf (Edit) form, click View CPM to open the properties form of the associated CPM.
See Procedure 1639 for more information about the CPM properties form.
6. Close the forms.
Procedure 1623 To manage the internal fan on a 7210 SASD
Perform this procedure to change the administration mode and view the fan operational state for the 7210 SASD 128
Mbyte variant, Release 5.0 R2 or later.
1. On the equipment tree, expand Network NE Shelf Fans Fan Tray.
2. Rightclick on Fan Tray and choose Properties. The Fan Tray (Edit) form opens.
3. Click on the Fans tab. A list form opens.
4. Choose a fan from the list. The Fan (Edit) form opens.
5. Configure the Admin Mode parameter. The operational state of the fan (On or Off) is displayed in the Oper
Mode field.
6. Save your changes and close the forms.
Procedure 1624 To configure a power supply tray
2. Rightclick on a power supply tray and choose Properties. The Power Supply Tray (Edit) form opens.
3. Configure the required parameters.
4. Save your changes and close the form.
Procedure 1625 To configure a power management zone on a 7950 XRS
1. On the equipment tree, rightclick on a 7950 XRS and choose Properties. The Network Element (Edit) form
opens.
2. Click on the Power Management Zones tab. A list of power management zones is displayed.
3. Select a power management zone and click Properties. The Power Management Zone (Edit) form opens.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 166/269
06.07.2017 Device management
4. Configure the power management parameters.
5. Click on the Utilization and Requirements tab to view information about power usage in the power
management zone. Click on the ellipsis button (...) for detailed information about each entry.
6. Save your changes and close the forms.
Procedure 1626 To provision an APEQ on a 7950 XRS
2. Rightclick on a power supply tray and choose Configure PEQ. The Power Supply Tray (Create) form opens
with the General tab displayed.
3. Configure the required parameters.
4. Save your changes and close the form.
Procedure 1627 To configure a variable power supply APEQ on a 7950 XRS
2. Rightclick on a power supply tray and choose Properties. The Power Supply Tray form opens with the
General tab displayed.
3. Click on the Power Supply tab and configure the Input Power Mode in the Power Details panel.
4. Save your changes and close the form.
16.8 Card and card slot object configuration procedures
Use the following procedures to configure card and card slot objects using the navigation tree.
Procedure 1628 To assign a card type
Perform this procedure to assign a card type to an empty card slot or SFM slot.
1. On the equipment tree, rightclick on the device where you want to assign a card type and choose Properties.
The Network Element (Edit) form opens.
2. On the Network Element (Edit) form navigation tree, expand the Shelf object.
3. Rightclick on an empty Card Slot object or SFM Slot object and choose Configure Card. The Card Slot
(Create) or SFM Slot (Create) form opens.
4. Configure the required parameters.
Note The correct chassis mode must be configured for the assigned card types. The chassis
mode determines the behavior of the card and establishes the scaling limits and available
features. See Procedure 161 and 167 for more information.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 167/269
06.07.2017 Device management
5. Configure the required parameters in the Virtual Scheduler and OLC panels.
6. Save your changes and close the form.
The card and slot appear in the navigation tree and in the equipment inventory list.
Procedure 1629 To configure egress WRED queue control on an XCM, IOM 3
or IMM forwarding plane
Note You cannot configure a forwarding plane on an XCM card until you have provisioned the
corresponding XMA card.
2. Rightclick on the Card Slot object and choose Properties. The Card Slot (Edit) form opens.
3. Click on the Forwarding Plane tab.
4. Choose an entry in the list and click Properties. The Forwarding Plane (Edit) form opens.
5. Configure the required parameters in the Egress WRED Queue Control panel.
6. Select a slope policy for the forwarding plane.
7. Save your changes and close the forms.
Procedure 1630 To configure IMPM on an XCM, 2 x XP MDA IOM 3, or IMM
forwarding plane
Note 1 See Procedure 1641 for information about configuring IMPM on an MDA that is not installed
in an XCM, 2 × XP MDA IOM 3, or in an IMM.
Note 2 You cannot configure a forwarding plane on an XCM card until you have provisioned the
corresponding XMA card.
1. On the equipment tree, expand Network NE Shelf Card Slot n.
2. Rightclick on the Card Slot object and choose Properties. The Card Slot (Edit) form opens.
3. Click on the Forwarding Plane tab.
4. Choose an entry in the list and click Properties. The Forwarding Plane (Edit) form opens.
5. Click Clear in the Ingress Multicast Path Management panel to remove the selected BW policy. The Select
button is enabled.
6. Select a BW policy.
7. Configure the Administrative State parameter.
8. Configure the required bandwidth parameters.
9. Save your changes and close the forms.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 168/269
06.07.2017 Device management
Procedure 1631 To configure an ingress queue group on a forwarding plane
Note 1 You can configure ingress queue groups only on the forwarding planes of XCM, IOM3, and
IMM cards.
Note 2 You cannot configure a forwarding plane on an XCM card until you have provisioned the
corresponding XMA card.
1. On the equipment tree, expand Network NE Shelf Card Slot n.
2. Rightclick on the Card Slot object and choose Properties. The Card Slot (Edit) form opens.
3. Click on the Forwarding Plane tab.
4. Choose an entry in the list and click Properties. The Forwarding Plane (Edit) form opens with the General tab
displayed.
5. Perform one of the following:
a. Click on the Access Ingress Queue Group tab.
b. Click on the Network Ingress Queue Group tab.
6. Click Create. The Forwarding Plane Access|Ingress Queue Group (Create) form opens.
7. Select a Queue Group Template Policy in the Queue Group Instance panel.
Note If you select a policy that contains queues, a configuration error message appears when
you try to apply the changes.
8. Configure the Instance ID and Description parameters.
9. Select an Accounting Policy in the Accounting Policy panel.
Note 1 Only accounting policies with Queue Group Packets as record type are supported.
Note 2 You can also choose to create an accounting policy from this form by clicking the
Create button instead of the Search button. See Procedure 8510 for information on creating an
accounting policy and the 5620 SAM Statistics Management Guide for general information about
configuring and collecting accounting statistics.
10. Configure the Collect Accounting Statistics parameter.
11. Select a Policer Control Policy in the Policer Control Policy panel.
12. Click Create in the Ingress Policer Control Override panel. The Ingress Policer Control Override (Create) form
opens, with the General tab displayed.
13. Configure the required parameters and save your changes.
14. Click on the Level Override Policy Items tab.
15. Select an item from the list and click OK. The FP Ingress Policer Level Override form opens, with the General
tab displayed.
16. Click on the Override tab and configure the Maximum Cumulative Buffer Space (bytes) parameter.
17. Save your changes.
18. Click on the Override Policy Items tab and click Create. The Forwarding Plane Ingress Queue Group Policer
Override (Create) form opens.
19. Select a policer.
20. Click on the Override tab and configure the required parameters in the Overridden Queue Group Template
Policer panel.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 169/269
06.07.2017 Device management
The parameters are configurable when the associated override check box is enabled.
21. Save your changes and close the forms.
Procedure 1632 To configure NE DDoS protection on a forwarding plane
Perform this procedure to configure the maximum number of enforcement policers for a DDoS protection
configuration on a forwarding plane. See “DDoS protection” in the 5620 SAM System Administrator Guide for more
information.
Note You cannot configure a forwarding plane on an XCM card until you have provisioned the
corresponding XMA card.
2. Rightclick on the Card Slot object and choose Properties. The Card Slot form opens.
3. Click on the Forwarding Plane tab, choose an entry in the list, and click Properties. The Forwarding Plane
form opens.
4. Configure the NE DDoS Protection Dynamic Enforcement Policer Pool Size parameter. Enable the Default
check box to specify a default value.
5. Save your changes and close the forms.
Procedure 1633 To enable named pool mode
Perform this procedure to allow named pools to be created for an MDA. Set the Pool Mode parameter when you are
configuring the card. Enabling the Named Pool mode is mutually exclusive with enabling Stable Pool sizing.
Caution The Pool Mode parameter can be enabled and disabled at anytime, however changing the
pool mode resets the IOM when MDAs are provisioned on the slot. If MDAs are not provisioned the
IOM is not reset.
2. Rightclick on the Card Slot object and choose Properties. The Card Slot form opens.
3. Click on the IO Card tab and configure the Pool Mode parameter.
4. Click OK and confirm your actions. The form closes.
Procedure 1634 To enable Stable Pool Sizing
Perform this procedure to enable an even split of buffering amongst all possible MDAs.
When Stable Pool sizing is enabled, then for each MDA, the buffering is split between all ports based on the port
maximum bandwidth and adjusted by the port’s modify buffer allocation rate percentages. You cannot enable Stable
Pool Sizing on any forwarding plane on a card while the card is either administratively or operationally in Named Pool
mode.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 170/269
06.07.2017 Device management
2. Rightclick on the Card Slot object and choose Properties. The Card Slot form opens.
3. Click on the Forwarding Plane tab, select a forwarding plane, and click Properties. The Forwarding Plane form
opens.
4. Configure the Stable Pool Sizing parameter and click OK. The form closes.
5. Save your changes and close the forms.
Procedure 1635 To enable Ingress Buffer Allocation
Perform this procedure to enable the allocation of an ingress buffer percentage on a given forwarding plane. The
allocation you specify will be set aside for use only by the ingress pools.
1. On the equipment tree, expand Network NE Shelf Card Slot n.
2. Rightclick on the Card Slot object and choose Properties. The Card Slot form opens.
3. Click on the Forwarding Plane tab, select a forwarding plane, and click Properties. The Forwarding Plane form
opens.
4. Configure the Ingress Buffer Allocation (%) parameter and click OK. The form closes.
5. Save your changes and close the forms.
Procedure 1636 To select system resource profile policies for the 7210 SASR
For the 7210 SASR, system resource allocations are configured in a system resource profile policy. See Procedure
1434.
Perform the following procedure to assign a policy to the card slot of a 7210 SASR. You must distribute the policy to
the device first.
Note When the policy is assigned to a card slot and the SAP Aggregate Meter parameter is modified,
you must reboot the card or the node for the modified value to take effect.
2. Rightclick on the card slot object and choose Properties. The Card Slot form opens.
3. Click on the IO Card tab and select a policy in the System Resource Profile Policy panel.
4. To view the currently effective resource profile for the card slot, click on the Active Resource Profile tab.
5. Click OK and confirm your changes. The form closes.
Procedure 1637 To configure OmniSwitch stacks
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 171/269
06.07.2017 Device management
2. Rightclick on the OmniSwitch object and choose Properties. The Network Element form opens.
3. On the Network Element tree, expand the Shelf object.
4. Click on a slot object. The Card Slot form opens.
5. Click on the Stack Configuration tab and configure the required parameters.
6. Save your changes and close the forms.
Procedure 1638 To configure an OmniSwitch CPU temperature threshold
2. Rightclick on the OmniSwitch object and choose Properties. The Network Element form opens.
3. On the Network Element tree, expand the Shelf object.
4. Click on a slot object. The Card Slot form opens.
5. Click on the Hardware Environment tab and configure the Temperature Threshold (Celsius) parameter.
6. Save your changes and close the forms.
Procedure 1639 To configure a CPM on a 7950 XRS
2. Rightclick on the 7950 XRS device and choose Properties. The Network Element form opens.
3. On the Network Element tree, expand the Shelf object.
4. Rightclick on Card Slot A or Card Slot B and choose Properties. The Card Slot form opens.
Alternatively, you can open a CPM Card Slot properties form by rightclicking on the associated CCM object
and choosing View CPM from the contextual menu.
Note Card Slot A and Card Slot B are automatically configured with CPMs. The CPMs cannot
be removed, and they cannot be configured in any other card slot.
5. Configure the required parameters.
6. If you are configuring a CPM on a 7950 XRS16c, the Flash Memory Modules tab is available. If required,
perform the following steps to configure a flash memory module on a 7950 XRS16c.
i. Click on the Flash Memory Modules tab, select a flash memory module, and click Properties. The
Flash Memory form opens.
ii. Configure the Administrative State parameter and click OK. The form closes.
Note You can configure flash memory modules on the 7950 XRS20 from the CCM
properties form. See Procedure 1622 for more information.
7. If you are configuring a CPM on a 7950 XRS20, the View CCM button is available. If required, click View
CCM to open the properties form of the associated CCM.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 172/269
06.07.2017 Device management
See Procedure 1622 for more information about the CCM properties form.
8. Save your changes and close the forms.
16.9 Daughter card slot object configuration procedures
Use the following procedures to configure daughter card slot objects using the navigation tree.
Procedure 1640 To configure an MDA
1. On the equipment tree, rightclick on a device and choose Properties. The Network Element form opens.
3. Perform one of the following:
a. To add a daughter card to an empty daughter card slot, rightclick on the daughter card slot and choose
Configure Daughter Card. The Daughter Card Slot form opens.
b. To modify an existing daughter card, click on the daughter card slot. The Daughter Card Slot (Edit) form
opens.
Note If a daughter card in your configuration is managed by 5620 SAM but becomes no
longer supported by 5620 SAM (for instance, an obsoleted MDA), it will be displayed
under the equipment tree as type Unspecified. To delete such a card from 5620 SAM,
you must remove the MDA from the device. Once a card is removed from the device, it
is also automatically deleted from 5620 SAM.
4. Configure the required parameters.
The Clock Mode parameter value must be set to Differential in order to configure the Differential Timestamp
Frequency (kHz) parameter.
The Assigned Daughter Card Type and In MDA Carrier Module Slot parameters are configurable only during
daughtercard creation.
Note The ATM Mode parameter must be set to a value of max16kvc for PPPoA and
PPPoEoA to be supported.
5. To create a daughter card on a 7710 SR, click on the MDA Carrier Module tab and configure the Assigned
MCM Card Type parameter. Click Apply.
6. Click on the Daughter Card tab and configure the required parameters.
Note 1 The MDA Mode parameter can only be configured on a 16 × Channelized DS1/E1
ASAP v2, 32 × Channelized DS1/E1 ASAP v2, 4 × Channelized DS1/E1 ASAP, 4 ×
Channelized OC3/OC12 ASAP SFP, or XMDA 1p × 10GigE/10p × 1GigE SFP.
Note 2 Before you configure the MDA Mode parameter, you must shut down all of the ports
and remove all of the subchannels and bundles from the MDA.
7. To configure named buffer pools:
Note You must enable pool mode on the parent I/O card to enable named buffer pool support.
See Procedure 1633 for more information.
i. Select a policy in the Ingress Pool Policy panel.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 173/269
06.07.2017 Device management
ii. If you are configuring an HSMDA daughter card, go to step 11.
Note HSMDA daughter cards support only ingress named buffer pool policies, and not
egress named buffer pool policies.
iii. Select a policy in the Egress Pool Policy panel.
8. If required, select a policy in the Network Queue Policy panel.
9. If required, select a Network Ingress Fabric Profile and an Access Ingress Fabric Profile in the Fabric Profiles
panel.
10. If required, select a Network Ingress Security Queue and an Access Ingress Security Queue in the Security
Queue Policies panel.
11. If required, select a policy in the Egress HSMDA Pool Policy panel.
Note You must enable pool mode on the parent I/O card to enable HSMDA pool support. See
Procedure 1633 for more information.
12. Configure the required parameters in the HSMDA Aggregate Queue Burst panel.
13. To assign a network queue policy and network policy of ring type for a 7705 SAR:
i. Select a network queue policy in the Ring Policies panel.
ii. Select a network policy in the Network Policy panel.
Note To assign a network policy of ring type to a 7705 SAR8 or 7705 SAR18 MDA,
you must set the Network Policy Type for 7705 parameter to Ring when you configure a
network policy on the MDA. See Procedure 497 for more information.
14. To configure MAC management:
i. Click on the MAC Operation tab and configure the required parameters.
ii. To create an FDB Mac entry, click on the FDB Entries tab. The MDA MAC FDB Management form
opens.
iii. Configure the required parameters.
iv. Select a port in the Port panel.
Note You can only bind a ring port to an FDB Mac entry.
v. Click OK.
15. If required, click on the Network Interfaces tab to add a network interface card.
16. Click Add. The Create Network Interface Routing Instance form opens. See Procedure 2810 for information
on creating a network interface.
17. If required, perform Procedure 1641 to configure IMPM on the daughter card.
18. If you configured named buffer pools in step 7, perform the following steps to configure the associated Q1
pools. Otherwise, go to step 19.
Note You cannot use this step to configure 7710 SR QoS policies.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 174/269
06.07.2017 Device management
i. Click on the QoS Pool tab, choose a pool, and click Properties. The QoS Pool form opens.
ii. Configure the required parameters.
iii. Select a policy in the Slope Policy panel.
19. To configure ATM:
i. Click on the ATM tab, select an ATM configuration, and click Properties. The ATM Configuration form
opens.
ii. Click on the VP Shaping tab and click Create. The ATM VP Shaper form opens.
iii. Configure the VP ID parameter.
iv. Select an ATM QoS Policy in the ATM QoS Policy panel.
v. Click on the QoS tab and configure the VP Shaping Weight parameter.
vi. Save your changes and close the forms.
vii. If required, repeat steps i to vi to create additional ATM VP shapers.
20. Save your changes and close the forms.
Procedure 1641 To configure IMPM on an MDA
Perform this procedure to configure IMPM on an MDA that is not installed in an XCM, 2 x XP MDA IOM 3 or an IMM.
Note See Procedure 1630 for information about configuring IMPM on an XCM, 2 × XP MDA IOM 3
or IMM.
1. Perform steps 1 to 7 of Procedure 1640.
2. Configure the required parameters.
3. Select a policy in the BW policy panel.
Note The multicast bandwidth policy named “default” cannot be modified or deleted.
4. Click OK and confirm your actions. The form closes.
Procedure 1642 To view the operational multicast channel properties of an
MDA
Perform this procedure to view specific information about an operational multicast channel on an MDA that is
configured to use an Ingress Multicast Bandwidth policy.
Note You can also view operational multicast channel information in the following locations:
the Mcast Path Mgmt tab on the properties form of a VPLS or VPRN service site
the Mcast Path Mgmt Channels tab on the properties form of a routing instance.
Each properties form contains information about the ingress MDA of each operational channel.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 175/269
06.07.2017 Device management
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
3. Click the Daughter Card Slot object. The Daughter Card Slot form opens.
4. Click on the Mcast Path Mgmt Channels tab.
5. Search for channels, choose a channel from the list and click Properties.
6. View the channel information, which includes the service site or routing instance associated with the channel,
and the following properties:
Note Channel information is displayed only when the MDA receives multicast traffic for a
previously configured multicast group.
Group Address—the operational channel multicast group address
Source Address—the operational channel multicast source address
Bandwidth—the operational bandwidth of the channel
Administrative Bandwidth—the administrative bandwidth of the channel
Last Highest Bandwidth—the value of the multicast bandwidth that is currently allocated to the channel
forwarding path on the MDA. This value is calculated based on periodic statistics polls and represents
the highest recorded bandwidth value since the most recent restart of the bandwidth update timer for
the channel.
Second Highest Bandwidth—the secondhighest recorded bandwidth value for the channel since the
most recent restart of the bandwidth update timer. The value is calculated based on periodic statistics
polls and is reset to zero every time the bandwidth update timer for the channel is restarted.
BW Update Timer expiration—the time that remains before the bandwidth update timer for the channel
expires
Current Path—the path that the channel traffic uses to reach the switching fabric; the path value is
primary, secondary, or ancillary
Explicit Path—indicates whether the current path is explicitly specified by a Multicast Info Policy
Preference Level—the preference level of the channel
BlackHole—whether the channel is in the BlackHole state
BlackHole Rate—specifies the bandwidth rate, in kb/s, at which the channel enters the BlackHole
state
7. Close the form.
Procedure 1643 To configure a module card on a 7705 SARM/ME or 7705
SARH
1. On the equipment tree, rightclick on a 7705 SARM/ME or 7705 SARH NE and choose Properties. The
Network Element (Edit) form opens.
Note 1 For the 7705 SARM and 7705 SARME, only the third daughter card slot can be
configured with module cards. The first two daughter card slots are configured with integrated
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 176/269
06.07.2017 Device management
cards.
Note 2 For the 7705 SARH, only the second and third daughter card slots can be configured
with module cards. The first daughter card slot is configured with an integrated card.
3. Configure the Assigned Daughter Card Type parameter and the required parameters in the OLC panel.
4. Click Apply. The Daughter Card Slot form refreshes.
5. Click on the Daughter Card tab and configure the required parameters.
6. To add a fabric profile:
i. Select a fabric profile in the Network Ingress Fabric Profile panel.
ii. Select a fabric profile in the Access Ingress Fabric Profile panel.
If you are configuring a 1 Colour Optical Add/Drop Mux card, go to step 21.
7. Select a network queue policy in the Network Policy Queue panel, if required.
8. Click on the Ports tab.
9. Click on a port and choose Properties. The Physical Port (Edit) form opens.
Note The first port on the DCM includes four SHDSL lines. The second port includes two
XDSL lines.
10. Configure the required parameters.
11. Click on the States tab and configure the Administrative State parameter. If you are configuring a DSL or DCM
module, go to step 13.
12. Click on the GPON tab and configure the required parameters. Go to step 21.
13. Click on the DSL tab and configure the required parameters.
14. To configure XDSL or SHDSL lines:
i. Click on the XDSL or SHDSL tab, as required.
ii. Choose an XDSL or SHDSL line and click Properties. The XDSL Line (Edit) or SHDSL Line (Edit) form
opens.
iii. Configure the Administrative State parameter.
iv. Save the configuration and close the form.
v. To configure more lines, repeat steps i to iv.
15. Click on the Ethernet tab and configure the required parameters on the General tab.
16. Click on the EFMOAM tab. To configure the parameters on this tab, perform the steps provided in Procedure
8850.
17. Click on the LLDP tab and configure the required parameters on the Nearest Bridge, Nearest Customer, and
Nearest Non TPMR tabs.
18. Click on the Remote Peers tab under the LLDP tab to search for and display LLDP remote peers associated
with the port. These remote peers are used to determine the physical topology of the network.
19. Click on the 802.1x Port and 802.1x Port Authenticator tabs, and configure the required parameters.
20. If you are configuring a 6 port Ethernet module card, click on the PoE tab and configure the required
parameters.
21. Save your changes and close the forms.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 177/269
06.07.2017 Device management
16.10 Bundle configuration procedures
Use the following procedures to configure a bundle. You can configure bundles only on channelized MDAs.
Procedure 1644 To create an FR group bundle
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
3. Configure the general property parameters and click Next. The Configure Bundle Parameters form opens.
4. Set the Bundle Type parameter to FR and configure the rest of the required parameters, then click Next. The
Configure Bundle Members form opens.
Note 1 To create a PPP group bundle, perform Procedure 1648.
Note 2 To create an IMA group bundle, perform Procedure 1646
5. Perform one of the following:
a. To create the multilink bundle without adding any members, go to step 6.
b. To add DS0 channel groups to the bundle:
i. Click Create. The Add Bundle Member form opens.
ii. Configure the Show Only Compatible Channels parameter, as required.
iii. Click Next. The Select Channels configuration form opens.
iv. Search for channels, and then choose up to 8 channel groups from the list of channels to
construct the bundle.
Note The channel group with the lowest Port ID is chosen as the primary
member for the bundle. The Encap Type of the primary member is used for all
other members. When adding members to a bundle at a later time, choose
members with the same Encap Type as the primary member.
v. Click Finish. The form closes and the Create Multilink Bundle form reappears.
6. Click Finish to close the form.
Procedure 1645 To modify an FR group bundle
Perform the following procedure to modify an FR group bundle already configured on a channelized MDA in the NE.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
3. Configure the required parameters on the following tabs:
General
Multilink Bundle
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 178/269
06.07.2017 Device management
States
MLFR
Bundle Members (where you can create and add new bundle members)
4. To configure the FR interface:
i. Click Edit FR. The FR Interface Bundle form opens.
ii. Configure the required parameters.
iii. Save your changes and close the form.
5. Save your changes and close the form.
Procedure 1646 To create an IMA group bundle
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
3. Configure the general property parameters and click Next. The Configure Bundle Parameters form opens.
4. Set the Bundle Type parameter to IMA and configure the rest of the required parameters, then click Next. The
Configure Bundle Parameters form opens.
Note 1 To create a PPP group bundle, perform Procedure 1648.
Note 2 To create an FR group bundle, perform Procedure 1644.
5. Perform one of the following:
a. To create the multilink bundle without adding any members, go to step 6.
b. To add DS0 channel groups to the bundle:
i. Click Create. The Add Bundle Member form opens.
ii. Configure the Show Only Compatible Channels parameter, as required.
iii. Click Next. The Select Channels configuration form opens.
iv. Search for channels, and then choose up to 8 channel groups from the list of channels to
construct the bundle.
Note The channel group with the lowest Port ID is chosen as the primary
member for the bundle. The Encap Type of the primary member is used for all
other members. When adding members to a bundle at a later time, choose
members with the same Encap Type as the primary member.
v. Click Finish. The form closes and the Create Multilink Bundle form reappears.
6. Click Finish to close the form.
Procedure 1647 To modify an IMA group bundle
Perform the following procedure to modify an IMA group bundle already configured on a channelized MDA in the NE.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 179/269
06.07.2017 Device management
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
3. Configure the required parameters on the following form tabs:
General
Multilink Bundle
States
Bundle Members (where you can create and add new bundle members)
4. Save your changes and close the form.
Procedure 1648 To create an MLPPP bundle
1. On the equipment tree, rightclick on the NE on which you need to create an MLPP group bundle and choose
Properties. The Network Element (Edit) form opens.
3. Configure the general property parameters and click Next. The Configure Bundle Parameters form opens.
4. Set the Bundle Type parameter to PPP and configure the rest of the required parameters, then click Next. The
Configure Bundle Members form opens.
Note 1 To create an FR group bundle, perform Procedure 1644
Note 2 To create an IMA group bundle, perform Procedure 1646.
Note 3 If you create an MLPPP bundle and the DS1 BER exceeds a threshold, the PPP link
is automatically removed from the MLPPP bundle.
5. Perform one of the following:
a. To create the multilink bundle without adding any members, go to step 6.
Note If you need to configure the MLPPP group bundle for multiclass service
transmission, do not add any bundle members. See Procedure 1650 for information
about how to configure the MLPPP bundle for multiclass service transmission.
b. To add DS0 channel groups to the bundle:
i. Click Create. The Add Bundle Member form opens.
ii. Configure the Show Only Compatible Channels parameter, as required.
iii. Click Next. The Select Channels configuration form opens.
iv. Search for channels, and then choose up to 8 compatible channel groups from the list of
channels to construct the bundle.
Note 1 If there are no compatible channels to choose from, edit some of the
existing channels that are not compatible to make them compatible:
Click Back and disable the Show Only Compatible Channels parameter.
Click Next.
Choose channels to edit from the list and click Properties.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 180/269
06.07.2017 Device management
Note 2 The channel group with the lowest Port ID is chosen as the primary
member for the bundle. The Encap Type of the primary member is used for all
other members. When adding members to a bundle at a later time, choose
members with the same Encap Type as the primary member.
v. Click Finish. The form closes and the Create Multilink Bundle form reappears.
6. Save your changes and close the form.
Procedure 1649 To modify an MLPPP bundle
Perform the following procedure to modify an MLPPP group bundle already configured on a channelized MDA in the
NE.
1. In the Equipment view of the navigation tree, rightclick on an NE and choose Properties. The Network
Element (Edit) form opens.
3. Rightclick on an MLPPP group bundle object and choose Properties. The Multilink Bundle (Edit) form opens.
4. Configure the required parameters on the following form tabs:
General
Multilink Bundle
States
MLPPP
Bundle Members (where you can create and add new bundle members)
Note If you need to configure the MLPPP group bundle for multiclass service
transmission, do not add any bundle members. See Procedure 1650 for information
about how to configure the MLPPP bundle for multiclass service transmission.
5. Save your changes and close the form.
Procedure 1650 To configure an MLPPP bundle for multiclass service
transmission
Perform the following procedure to configure an existing MLPPP group bundle for multiclass service transmission.
Consider the following before you start to configure an MLPPP bundle for multiclass service transmission.
Only channelized ASAP MDAs on the 7705 SAR, 7710 SR, and 7750 SR support multiclass MLPPP.
You need to configure multiclass MLPPP before you add bundle members to the multilink bundle.
Ports configured in network mode do not support multiclass MLPPP.
Multiclass MLPPP is not supported when LFI is enabled.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
3. Rightclick on an MLPPP group bundle object and choose Properties. The Multilink Bundle (Edit) form opens.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 181/269
06.07.2017 Device management
4. Click on the MLPPP tab and configure the required parameters.
Note 1 The Magic Number parameter is configurable only on channelized ASAP MDAs on
7710 SR and 7750 SR NEs.
Note 2 You can apply QoS profiles to an MLPPP bundle only if the Class Count parameter is
set to 4.
5. Save your changes and close the form.
Procedure 1651 To configure an MLPPP bundle as a network interface on a
channelized ASAP MDA
Perform the following procedure if you need to configure an existing MLPPP group bundle as a network interface; see
Procedure 1648 for details.
Consider the following when configuring an MLPPP as a network interface.
Only channelized ASAP MDAs on the 7705 SAR, 7710 SR, and 7750 SR support MLPPP group bundles.
The MLPPP network interfaces do not support LFI.
The MLPPP network interfaces do not support MC MLPPP.
IPv6 network interfaces are not supported.
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
3. Rightclick on an MLPPP group bundle object and choose Properties. The Multilink Bundle (Edit) form opens.
4. Click on the Bundle Members tab and configure the port mode:
i. Search for bundle members, choose a member from the list and click Properties. The Bundle Member
(Edit) form opens.
ii. Click on the Port tab.
iii. Click Properties beside the port name. The DS0 Channel Group (Edit) form opens.
iv. Set the Mode parameter to Network.
v. Save your changes and close the form.
5. Save your changes and close the form. The form refreshes with new tabs.
6. Click on the Network Interfaces tab and configure a network interface:
i. Click Create. The Create Network Interface Routing Instance form opens.
ii. See Procedure 2810 for information about creating a network interface on the DS0 channel.
Note The port in step 5 of Procedure 2810 is set to the DS0 channel by default. Go to
step 7 of Procedure 2810.
The L3 interface appears on the Network Interfaces tab.
7. Save your changes and close the form.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 182/269
06.07.2017 Device management
9. 17 — Port and channel object configuration
17.1 Port and channel object configuration overview
17.2 Working with port and channel objects
17.3 SONET and SDH subchannel applications and structure
17.4 Workflow to manage port objects
17.5 Workflow to manage channel objects
17.6 Port configuration procedures
17.7 Channel and framing link configuration procedures
17.1 Port and channel object configuration overview
Port objects are children of daughter card slot objects. They appear below the daughter card slot after the daughter
card is configured. Channel objects are children of port objects. They appear on the navigation tree below the port
object after the channel is configured.
Properties forms for port objects and channel objects are accessed using the 5620 SAM navigation tree.
This chapter contains the procedures to configure devices using the navigation tree. See chapter 5 for more
information about using the navigation tree.
17.2 Working with port and channel objects
The types of ports that are available depend on the daughter cards that are configured in the chassis. For some
OmniSwitch devices, the ports that are available depend on the chassis type, for others the type of card that is
configured for the card slot. Ethernet ports cannot be channelized. SONET/SDH and TDM ports can be channelized.
The following types of ports are supported:
Fast Ethernet (10/100/1000 BaseT)
Gigabit Ethernet (1000BaseT)
10 Gigabit Ethernet (10000BaseT)
10 Gigabit Ethernet (10GBaseT)
40 Gigabit Ethernet (10GBaseT)
Ethernet combo
PoE
OC3/STM1, OC12/STM4, OC48/STM16, and OC192/STM64 SONET/SDH
channelized OC3 and DS3/E3
channelized ASAP OC3/STM1, OC12/STM4, DS1/E1, and DS3/E3
The port syntax for most devices that support daughter cards is card slot/daughtercard/port. For example, Port 1/1/1
represents port 1 of daughter card 1 in slot 1. The port syntax for the OmniSwitch is card slot/port. In every case,
ports are created automatically when the daughter card is created. You must select one port object at a time and
configure the properties of the port for the service that you need the port to provide. The properties vary depending on
whether the port type is one of the Ethernet ports, SONET/SDH ports, TDM ports, or microwave ports. Channel
objects are created on SONET/SDH or TDM ports for any type of channelization on the port whether it is a clear
channel application or a subchannel application.
Use the properties forms from the contextual menus in the navigation tree to configure port and channel parameters.
You can configure the port mode as network, access, or hybrid.
Network ports pass networklevel traffic.
Access ports are customerfacing and pass servicelevel traffic.
Hybrid ports can pass networklevel and accesslevel traffic.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 183/269
06.07.2017 Device management
Note 1 By default, a port is in network mode.
Note 2 See Procedure 172 to change the port mode.
Clear channel ports (OC192/OC48c/OC12c/OC3c) are network or access ports. Channelized ports (CHOC
12/CHOC3c/ DS3/E3) are always in access mode, however, the ASAP CHOC3 supports both access and network
modes. The ASAP DS1/E1 ports support:
access mode for ATM/IMA and TDM
network mode for PPP/MLPPP
Network ports are used in the service provider transport or infrastructure network, such as an IP/MPLSenabled
backbone network or uplink ports for rings using L2 Ethernet switches. A port that is in network mode can be
assigned an IP address and host an L3 interface that can perform IP routing functions.
Access ports are associated with a SAP, a subscriber, and a service to provide connectivity. Access ports and
channels are configured with encapsulation values to differentiate the service on the port or channel. When a port is
access mode, one or more services can be configured on the port. A channelized port that is to act as an endpoint
must be in access mode. You can convert access ports to hybrid ports and migrate any existing SAPs. See
Procedure 173 for more information.
Hybrid ports are ports that can host SAPs and network interfaces simultaneously. This enables a customer to use
one uplink port for enterprise and enduser traffic. A hybrid port preserves the existing network and access port
functionality, and uses the same QoS, scheduler, and port scheduler resources as other ports, but requires the
configuration of weight values that allocate buffer percentages to the access and network traffic on the port.
The 5620 SAM supports hybrid mode configuration for Ethernet ports on the following devices:
7210 SASM (in network mode), Release 6.0 R1 or later
7210 SASMxp
7210 SASR, Release 6.1 R1 or later
7210 SAST (in network mode), Release 7.0 R1 or later
7210 SASX, Release 6.0 R1 or later
7450 ESS
7705 SAR, Release 6.1 R1 or later
7750 SR7
7750 SR12
7950 XRS
Note Singleslot chassis such as the 7450 ESS1 and 7750 SR1 do not support hybrid port mode.
You can configure a hybrid port on an Ethernet MDA in an IOM3XP, or on a CMA in an IOMXP. The 7750 SR
supports hybrid port configuration on an IMM in addition to an IOM3XP.
Note Hybrid port configuration is not supported on an HSMDA or a VSM MDA.
A hybrid port supports dot1q and QinQ encapsulation, but does not support null encapsulation, in order to
accommodate singleSAP operation. The available VLAN tags are shared among the VLAN SAPs and VLAN network
IP interfaces. When you create a SAP or L3 interface on a hybrid port, the outer VLAN tag must not be in use by
another SAP or L3 interface on the port.
By default, the MTU of a hybrid port is set to the larger of the network and access MTUs to accommodate the
creation of L3 interfaces and SAPs.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 184/269
06.07.2017 Device management
Note 1 A hybrid port can participate in a singlechassis LAG.
Note 2 A hybrid port cannot participate in an MCLAG or MC ring.
See the appropriate device documentation for more information about hybrid ports.
When working with a TDM port, you must specify the Line Buildout as either short or long. That is, for a DS3 port the
Line Buildout parameter must be configured. If the TDM port is in the context of a SONET STS1 subchannel, for
example, the DS3 channel is built on the STS1 channel of a SONET port, the line buildout parameter is not required.
At the connection termination points, you are required to configure the Encap Type as required, the MTU size as
required, and the configured MAC address as required when configuring the port or channel.
Policies can be added or deleted as required using the manage policy forms.
You can associate policies to ingress and egress access and network ports. Buffer policies are used to create and
edit QoS buffer pool resources on network ports, access ports, and access channels. Egress network ports, access
ports, and access channels have a dedicated buffer pool for queuing. The traffic is handled by a single buffer pool,
one at the ingress, and one at the egress.
You can configure the amount of egress buffer space to be allocated to the port or channel. By default, all egress
buffers are allocated fairly among the egress ports and channels based on their relative egress bandwidth.
The egress buffers for egress network ports and channels are put into perport or perchannel egress buffer pools and
are used by the egress network forwarding class queues on that port or channel. The ingress buffers allocated to
network ports and channels are summed into a single pool and are used by the ingress network forwarding class
queues (defined by the network ingress buffer policy).
The egress and ingress buffers allocated to access ports and channels are put into an egress buffer pool and ingress
buffer pool for the port or channel. The access buffer pools are used by egress and ingress service queues created
by the SAPegress and SAPingress policies in use by services on the port or channel.
Changing the size of an egress buffer pool should be carefully planned. By default, there are no free buffers to
increase the size of a pool. In order to increase a pool on one port or channel, the same amount of buffers must be
freed from other egress buffer pools on the same daughter card.
Digital diagnostics monitoring
The 5620 SAM displays the following digital diagnostics monitoring data and alarm and warning information for ports
on CFPs, QSFPs, SFPs and XFPs optical modular transceivers:
temperature
supply voltage (SFP)
TX bias
TX output power
RX received optical power
external calibration
The transceiver is programmed with warning and alarm thresholds for low and high conditions that can generate
system events. The thresholds for CFPs, QSFPs, SFPs, and XFPs are programmed by the transceiver
manufacturer. The 5620 SAM raises an alarm when these thresholds are exceeded.
You can view digital diagnostics monitoring information from the DDM tab and the Lane DDM tab on the property
form of supported ports. The External Calibration tab is available if the ports on CFPs, QSFPs, SFPs, and XFPs
optical modular transceivers support the external calibration functionality.
Tagged and untagged VLAN ports
The 5620 SAM supports tagged and untagged ports as VLAN access ports.
Table 171 describes the behavior when ingress tagged or untagged traffic enters and then exits a VLAN.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 185/269
06.07.2017 Device management
Table 171 Tagged and untagged traffic behavior
Ingress Ingress Action Egress VLAN port
traffic VLAN port configuration and action
configuration configuration
Untagged Untagged The VLAN allows the traffic and If the egress VLAN port is
passes it based on the default untagged, the traffic remains
VLAN ID. untagged.
The MAC address of the
destination is learned. If the egress VLAN port is
tagged, a tag is added to the
traffic.
Tagged If the egress VLAN port is
untagged, the traffic remains
untagged.
If the egress VLAN port is
tagged, a tag is added to the
traffic.
Tagged Untagged The VLAN allows the traffic if If the egress VLAN port is
the tag matches the default untagged, the tag of the traffic
VLAN ID. is removed.
The MAC address of the
destination is learned.
If the egress VLAN port is
If the tag does not match the tagged, the traffic remains
default VLAN ID, the traffic is tagged.
dropped.
Tagged The VLAN allows the traffic: If the egress VLAN port is
if the tag matches the untagged, the tag of the traffic
default VLAN ID is removed.
if the tag matches
another VLAN ID
The MAC address of the If the egress VLAN port is
destination is learned. tagged, the traffic remains
If the tag does not meet either tagged.
condition, the traffic is dropped.
Figures 171 and 172 show how tagged and untagged traffic is handled on the devices, based on the VLAN ID.
Figure 171 Untagged traffic and VLANs
Figure 172 Tagged traffic and VLANs
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 186/269
06.07.2017 Device management
Connection termination points for services and interfaces
Connection termination points are objects that represent terminating endpoints for a service, for example the endpoint
of a VLL service. Connection termination points can be Layer 2 or Layer 3 interfaces, depending on the type of
service being created. At the connection termination points you must configure the mode as Access or Network, the
Encap Type as required, the MTU size as required, and the configured MAC address as required when configuring
the port or channel. The following objects can be used for connection termination points:
STS3 to STS192 clear channels
DS3 clear channel
DS0 groups
ports
bundle
STS3 to STS192 clear channel
STS3 to STS192 clear channel SONET/SDH ports can be used to create SAPs or IP interfaces with one clear
channel on each port that operates at the rate of the parent object. Clear channel SONET applications can be
performed on any OCn card. SONET channel termination for 1 × 10Gig MDAs are not supported. See "SONET
clear channel applications" in this section for more information.
DS3 clear channel
A DS3 clear channel can be a connection termination point when it is explicitly configured as unchannelized, that is,
when the Configuration Type is set to None, which is the default setting for a DS3. DS3 clear channel connections
cannot be channelized to a lower level than the one full DS3 channel. See "TDM channelization and clear channel
applications" in this section for more information.
DS0 channel groups
A TDM channel group connects a group of DS0s by allocating a specific number of spans or interfaces and channels
to a group of channels. The DS0 channel group defines the incoming and outgoing parameters for a group of channels
such as IP profiles, routing tables, and translation tables to be assigned during the configuration of the specific
channel group.
To use a DS1 or E1, you must create at least one DS0 group for the DS1 or E1. The 5620 SAM supports the
automatic configuration of subchannels and assignment of timeslots on the ports within DS0 groups. Depending on
the TDM port selected, the 5620 SAM automatically creates the DS0 channel groups with the appropriate type of
timeslots. For example, you can assign timeslots to a DS0 channel group as follows:
For DS1 channel types: Use four timeslots per channel group, which results in six DS0 channel groups with
IDs from 1 to 6. Each contains four timeslots.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 187/269
06.07.2017 Device management
For E1 channel types: Use five timeslots per channel group, which results in six DS0 channel groups with IDs
from 1 to 6. Each contains five timeslots, with one timeslot not assigned.
You can view the channels that are assigned in DS0 groups using the associate properties form. You can also
disable, enable, or reassign the assignment of timeslots as required, in a DS0 group.
See "TDM channelization and clear channel applications" in this section for more information about DS0 channel
groups. See Procedure 1727 for information about creating channels on ports for card types that support multiple
subchannels. See Procedure 1732 for information about creating TDM DS1 or E1 channels and DS0 channel
groups.
SONET STS1 subchannels
Only the DS0 group level can be used as a connection termination point for SONET STS1 subchannels.
Channelization on the 1 × OC12 can be used to create up to 12 SONET STS1 subchannels. Each STS1 channels
can be used to create a DS3 frame on which you can build DS1 or E1 channels that can be configured to the DS0
channel group level. You can configure the DS0s of a DS0 group in any sequence and you do not need to use all
DSOs. For example, you can use DS0 1, 3, 5, and 9. See "SONET VT1.5 and VT2 payloads" in this section for more
information.
Only the DS0 group level can be used as an endpoint on the channelized 12 × DS3 card. Channelization can be used
on each DS3 port of the card to create independent TDM channels in the form of DS1 or E1 data channels that
handle DS0 groups. The DS0s of a DS0 group can be configured in any sequence and you do not need to use all
DS0s. For example, you can use DS0 1, 3, 5, and 9. See "SONET and SDH subchannel applications and structure"
in this section for more information.
Ethernet ports
Ethernet ports can be configured as connection termination points in SAPs and IP interfaces. They cannot be
channelized.
You must configure the class of port, such as fast Ethernet, GigE, or 10G Ethernet. You must also configure the port
encapsulation at the connection termination point. Ethernet access ports use:
dot1q—supports multiple services on the port; the outer encapsulation value that distinguishes services is the
VLAN ID in the IEEE 802.1Q header
QinQ—supports multiple services on the port/channel; the inner and outer encapsulation values that
distinguish services is the VLAN ID in the IEEE 802.1Q header
null—supports a single service on the port
You must configure the duplex parameter from the Ethernet tab if the port is to be added to a LAG. Configure the
Dot1 Q Ethertype and Q in Q Ethertype parameters from the Ethernet tab, if required. The range is 1536 to 65 535.
You must also configure the speed parameter from the General tab. The options are 10, 100, 1000, or 10 000,
depending on the speed of the Ethernet interface.
Most OmniSwitch chassis offer four hybrid or combo ports. These ports consist of four paired 10/100/1000BaseT
ports and four 1000 SFP ports. Preferences for these ports are configurable and, depending on the configuration,
redundancy can be provided if a link fails.
OmniSwitch learned port security
LPS provides a mechanism to control network device access on one or more OmniSwitch ports. Configurable LPS
parameters allow you to restrict the source learning of host MAC addresses to:
a specific amount of time in which the switch allows source learning to occur on all LPS ports
a maximum number of learned MAC addresses allowed on the port
a list of configured authorized source MAC addresses allowed on the port
The following options allow you to specify how the LPS port handles unauthorized traffic.
Block only traffic that violates LPS port restrictions; authorized traffic is forwarded on the port.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 188/269
06.07.2017 Device management
Disable the LPS port when unauthorized traffic is received; all traffic is stopped and a port reset is required to
return the port to normal operation.
See Procedure 2969 for information about enabling LPS on Ethernet ports and configuring LPS properties. See
Procedure 1724 for information about configuring static MAC addresses on LPS enabled Ethernet ports.
Note A deployment error is displayed in 5620 SAM while creating a LAG with ports. This deployment
failure occurs if there is an LPS/VLAN configuration done on a specific port, using CLI.
MTU size and port configuration
You must specify the MTU size for an Ethernet port using the MTU (bytes) parameter on the General tab at the
connection termination endpoint.
Consider the following when you configure MTU parameters.
The managed devices must handle MTU limitations at many service points. The physical (access and
network) ports, service, and service tunnel MTU values must be individually defined.
The ports to be designated as network ports and the ports to be designated as access ports intended to carry
service traffic must be identified.
MTU values should not be frequently modified.
Service MTU values must be less than or equal to the service tunnel MTU.
Service MTU values must be less than or equal to the access port MTU.
The MTU value for an inband management port should be less than or equal to the MTU value for the peer
port connected to the inband management port.
See the device specific documentation for endtoend considerations for configuring maximum MTU size throughout
the managed network.
The Ethernet port MTU parameter indirectly defines the largest physical packet that the port can transmit or that the
farend Ethernet port can receive. Packets received that are larger than the MTU are discarded. Packets that cannot
be fragmented at egress and that exceed the MTU are discarded.
The parameters for MTU configuration include the destination MAC address, source MAC address, Ethernet
encapsulation type, length field, and complete Ethernet payload.
The MTU value for a port is associated with the port mode, such as access or network, and the port encapsulation
type. If you change the mode or encapsulation type value for a port, the 5620 SAM adjusts the MTU value to a
default value. If you do not want the MTU values for ports to revert to the defaults, you can configure the 5620 SAM
to retain the currently configured MTU values for ports regardless of a mode or encapsulation type change. See
Procedure 174 for more information.
HSMDA Egress Secondary Shapers
The egress port scheduler combines all subscriber queues of the same scheduling class and services the queues in
a byte fair round robin fashion. This results in more packets being forwarded into the aggregation network towards a
DSLAM than the DSLAM can accept. If the HSMDA egress port is congested, the egress bandwidth represented by
the downstream discarded packets to the DSLAM may be allocated packets destined to other DSLAMs.
The HSMDA supports egress secondary shapers to provide a control mechanism to prevent downstream overruns
without affecting the classbased scheduling behavior on the port. All subscribers destined to the same DSLAM have
their queue groups mapped to the same egress secondary shaper. As the scheduler services the queues within the
groups according to scheduler class, the destination shaper is updated.
After the shapers rate threshold is exceeded, scheduling for all queues associated with the shaper is stopped. When
the dynamic rate drops below the threshold, the queues are allowed to be placed back on the scheduler service lists.
By removing the queues from their scheduling context for a downstream congested DSLAM, the port scheduler is
allowed to fill the egress port with packets destined to other DSLAMs without affecting class behavior on the port.
Egress secondary shapers are configured per port.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 189/269
06.07.2017 Device management
PoE
The 5620 SAM supports PoE on the following devices:
7210 SASMxp ETR and 7210 SAST ETR; see Procedure 1719
7705 SARH, 7705 SARHc, 7705 SARW, 7705 SARWx; see Procedure 1720
OmniSwitch (except for the Metro version of the OS 6250); see Procedure 1725
PoE provides power directly from the Ethernet ports. Powered devices such as IP phones, wireless LAN stations,
Ethernet hubs, and other access points can be plugged directly into PoEenabled Ethernet ports. The 5620 SAM
supports PoE and PoE+ on supporting devices.
Moving and copying SAPs between ports
You can move and copy SAPs between physical Ethernet ports, logical ports, or a combination of both. You can also
move and copy SAPs between endpoints configured with ATM encapsulation. For example, you can move a SAP on
an IMA bundle to another bundle or to a TDM channel configured with ATM encapsulation. The function is typically
used in redundancy scenarios, or to recover from a hardware failure.
Consider the following before you attempt to copy or move a SAP:
Ports:
The source and destination ports can be on the same or on a different chassis. Interchassis copy or
move is supported only when both NEs are of the same type, in the same chassis mode or from a
lower chassis mode (source NE) to a higher chassis mode (destination NE), and at the same major
software release, for example, 10.0 R1 and 10.0 R3.
The source and destination ports can be the same. This configuration allows you to change the
encapsulation values for a group of SAPs on the same port using outer and inner encapsulation offset
values. These values can be positive or negative, depending on whether the encapsulation values must
increase or decrease.
The physical Ethernet ports can be of different types; for example, Fast Ethernet (10/100/1000 BaseT),
Gigabit Ethernet (1000 BaseT), and 10 Gigabit Ethernet (10 GBaseT).
The source and destination ports must be configured as access ports.
The encapsulation type must be the same on the source and destination ports.
You cannot copy or move a SAP between an HSMDA port and a nonHSMDA port.
The copy and move operations fail if the encapsulation value for a SAP on the source port is used by a
SAP on the destination port. You can modify the SAP encapsulation values used on the destination
port, if required.
The selected L2 access interface SAPs on the source port can be moved only to another service, and
not within the same service.
If a SAP on the source port belongs to a service not supported on the destination port, the SAP is not
copied or moved.
The maximum number of SAPs varies for ports and MDAs. The SAP copy or move operation fails if the
SAP capacity is exceeded for the destination port.
For L2 and L3 access interfaces, you can move all SAPs or a subset of the SAPs on a port. You can
also copy all SAPs or a subset of the SAPs on a port for L2 access interfaces.
All SAPs associated with a specific port within a group interface contained in an L3 subscriber interface
can be moved at the same time.
SAPs:
SAPs can be associated with either L2 access interfaces on services such as Apipes, Cpipes, Epipes,
Hpipes, Fpipes, Ipipes, VPLS, and MVPLS, or L3 access interfaces or subscriber interfaces that are
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 190/269
06.07.2017 Device management
associated with services such as IES and VPRN.
L2 access interface SAPs can be copied or moved from one service to another service of the same
service type. The source and target service must be on the same site, and the source and destination
service site types must be the same, for example Bsite, Isite.
MEPs are copied or moved with the L2 SAP copy/move operation only if the Follow Service Topology
Changes parameter is not enabled on the global MEG service. If the Follow Service Topology Changes
parameter is enabled, the MEPs are automatically created by the OAM framework when the new SAP
is created. See Procedure 892.
For an L2 SAP copy/move operation, only MEP CFM tests that are manually created are moved to the
new SAP. MEP CFM tests created by Test Suite are not moved to the new SAP.
For a SAP copy, the MEP ID is autoassigned. For a SAP move, the MEP ID is copied only if the Node
Wide MEP ID is not set on the destination NE. Otherwise the MEP ID will be autoassigned based on
the configured MEP ID. See Procedure 891.
Endpoints associated with the specified SAPs are copied during an L2 SAP copy/move operation, but
other objects associated with the endpoints such as other SAPs or spokes are not copied/moved. If the
destination already has an endpoint with the same name, the endpoint associated with the source SAP
will not be copied/moved with the source SAP.
You cannot change SAP encapsulation from bridged to routed if ARP and DHCP options have been
configured.
SAP attributes:
VPLS and MVPLS dynamic FIB entries that are associated with copied or moved SAPs are discarded.
Static FIB entries are transferred to the destination port after a successful SAP copy or move.
All SAP redundancy relationships at the source port, such as those provided by an MVPLS, are
discarded during a copy or move operation.
All alarms, statistics, or OAM test results that are associated with a copied or moved SAP are
discarded.
When a source SAP belongs to an SHG, the 5620 SAM attempts to preserve the SHG membership.
The destination SHG must have the same name as the source SHG, and must have the same
residential SHG status. If an SHG with the same name does not exist on the destination service site,
the 5620 SAM creates it.
When a source SAP uses an aggregation scheduler, the scheduler is copied to the destination. The
aggregation scheduler must be unique to the destination NE and must have the same scope, for
example, MDA or port.
See Procedures 175, 176, 177, and 178 to move access interface SAPs between services or ports.
SONET/SDH and TDM port encapsulation
SONET/SDH and TDM ports can be configured as connection termination points in SAPs and IP interfaces. They
can be channelized.
An access port is used for customerfacing traffic on which services are configured. SAPs can only use an access
port. When a port is configured for access mode, the appropriate encapsulation type must be specified to distinguish
the services on the port.
You must configure the Encap Type parameter from the General tab at the connection termination point.
SONET/SDH or TDM ports or channels support the following encapsulation types, depending on the MDA type:
BCP Null
IPCP
BCP Dot1 Q
FR — Support multiple services using the DLCI header to distinguish services
ATM — Support multiple services using the VCI or VPI of the PVC
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 191/269
06.07.2017 Device management
PPP Auto
CEM
MTU size considerations apply to SONET/SDH and TDM channels. See "MTU size and port configuration" in
section 17.2 for more information.
SONET clear channel applications
Ports on OCn cards can be used for SONET clear channel applications. SONET or TDM clear channel applications
allow you to create a full channel on a port which can be configured as access or network mode for SONET and
access only for TDM. For example, when you create a 16 × OC3 SFP card, 16 ports are created. You can create one
full channel on each of these ports. For more information about the 4port OC3/STM1 ASAP SFP card for clear
channel support on the 7705 SAR8, see OC3/STM1 clear channel support on the 7705 SAR8 and 7705 SAR18 in
this section.
STS192/48/12/3 clear channel applications use the following syntax:
card slot/daughtercard/port.STSType
For example, the clear channel STS12 on slot 4, MDA 1, port 1 is named 4/1/1.sts12
Table 172 lists available SONET channel applications and parameters for clear channel, subchannel, and TDM
applications.
Table 172 SONET channel parameters
Applications Channel ranges
STS STS STS STS DS3 DS1 DS0 E1 DS0
192 48 3 1
SONET Clear 1 1 1 1
channel
SONET Sub 1 to 1 to 1 1 to 1 to 1 to 2 to
channel 4 3 28 24 21 32
TDM 1 1 to 1 to 1 to 2 to
28 24 21 32
OC3/STM1 clear channel support on the 7705 SAR8 and 7705 SAR18
The 7705 SAR8 and 7705 SAR18 support the 4port OC3/STM1 ASAP SFP card. The 4port OC3/STM1 ASAP
SFP card has four SFPbased ports that can be independently configured for ATM in access mode or for Packet over
SONET/SDH (POS) in network mode. Each port can be independently configured to be SONET (OC3) or SDH
(STM1) framing. See ATM encapsulation in this section for more information. The interface must be configured as
UNI. The transmit clock rate for a port can be device or looptimed.
The section trace (J0) byte can be configured by the operator to check the physical cabling. The port can activate
and deactivate local line and internal loopbacks. The MTU size for a 4port OC3/STM1 ASAP SFP access port is
fixed at 1572 for ATM encapsulation.
CSM activity switches for a 4port OC3/STM1 ASAP SFP card on the 7705 SAR8 and 7705 SAR18 are hitless on
the data path.
The 7705 SAR8 and 7705 SAR18 support the 2port OC3/STM1 ASAP SFP card. The 2port OC3/STM1 ASAP
SFTP card has two SFPbased ports (optical or electrical) that can be configured for ATM/IMA or TDM in access
mode or for MLPPP in access or network mode. The port type must be configured to be either SONET (OC3) or SDH
(STM1).
Note Channels on the 4port OC3/STM1 ASAP SFP adapter card cannot be configured as IES
SAPs.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 192/269
06.07.2017 Device management
TDM channelization and clear channel applications
When you create a 4 or 12 ×DS3/E3 card, 4 or 12 DS3/E3 ports are created. You can then create DS3/E3 channels
using the 5620 SAM, one per port. Each DS3/E3 channel can be channelized into 28 independent DS1 or 21
independent E1 data channels or, in clear channel applications, the DS3 can be the connection termination point. For
channelized DS3 connections, each DS1 channel can be channelized to 24 DS0 groups and each E1 channel can be
channelized to 31 DS0 groups. To use a DS1 or E1, you must create at least one DS0 group for the DS1 or E1.
By default, DS3 ports are automatically created for clear channel connections. To create a channelized DS3, you
must configure the DS3 channel type as E3 or DS3 on the port. To channelize the DS3 to the DS0 level, you must
set the Channelization Type to Channelized DS1 or E1. Figure 173 shows the channelized DS3 port structure for
DS1 channels.
Figure 173 Channelized 12 × DS3 port structure for DS1 Channels
The channelized DS3 port structure for E1 channels has the following parameter values:
each DS3 port supports 21 E1 channels
each E1 channel supports 31 DS0 channel groups
TDMbased DS3 channelization uses the following syntax:
DS3 channel configured for TDM:
card slot/daughtercard/port.DS3
DS1 channel from a TDMbased DS3 channel:
slot/daughtercard/port.DS1[DS3#].[DS1#]
E1 channel from a TDMbased DS3 channel:
slot/daughtercard/port.DS1[DS3#].[E1#]
DS0 group channel from the DS1 channel:
slot/daughtercard/port.DS0Grp[STS3#].[STS1#].[DS1#/E1#].[Group#]
Table 173 provides an example of the naming conventions for a 12 × DS3 port.
Table 173 Example of TDM channel naming convention
Syntax Description Additional information
Channel 1/1/1 is the slot Because DS3s are unchannelized by default,
1/1/1.ds3 number/daughtercard number/port you must configure the Channelization Type as
number Channelized.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 193/269
06.07.2017 Device management
.ds3 identifies the channel as DS3
Channel .ds1 identifies the channel as DS1 Identifies the DS1 channel and shows how the
1/1/1.ds11.2 1 is the DS3 number DS3 level acts as a place holder for the DS1s.
.2 is the DS1 number (1 to 28)
Channel .e1 identifies the channel as E1 Identifies the E1 channel and shows how the
1/1/1.e11.2 1 is the DS3 number DS3 level acts as a place holder for the E1s.
.2 is the E1 number (1 to 21)
Channel .ds0Grp identifies the channel as The DS0 group is configured on the DS1 or E1
1/1/1.ds0Grp a DS0 group channel. Only a DS0 can be used as a CTP.
1.2.23 1 is the DS3 number
.2 is the DS1 number (1 to 28) or
E1 number (1 to 21)
.23 identifies the DS0 channel
group (1 to 24) on the DS1 or (2 to
32) on the E1
ATM encapsulation
SONET/SDH clear channels can be provisioned so that ATM cells are encapsulated in SONET/SDH frames. The
entire SONET/SDH path of the port is then used to carry ATM cells. The channel of the port becomes the ATM
interface. ATM encapsulation is supported on the following daughter cards:
16 × ATM OC3 SFP
16 × ATM OC3 SFP B
4 × ATM OC12/OC3 SFP
4 × ATM OC12/OC3 SFP B
4 × OC3/STM1 ASAP SFP
4 × Any Service Channelized OC3
16 × Any Service Channelized DS1/E1
SONET/SDH clear channel applications with ATM encapsulation use the following syntax:
Daughter Card Slot 3 (16 × ATMOC3), OK
Port 3/1/1 Speed: OC3, State: OK
Channel 3/1/1.sts3, Mode: Access, Encap: ATM, State: Ok
Customer devices with ATM interfaces are connected directly or using the ATM access network to a 7750 SR that
offers IES or VPRN services.
A SONET/SDH clear channel with ATM encapsulation can carry multiple ATM PVCs. ATM PVCs cannot be created
from the 5620 SAM. They are created automatically by the router when a new Layer 3 interface over ATM is created.
Figure 174 shows an example of ATM PVCs on a SONET/SDH clear channel.
Figure 174 ATM PVCs on a SONET/SDH clear channel
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 194/269
06.07.2017 Device management
ILMI links between ATM interfaces
ILMI links can be configured between ATM interfaces. ILMI is a protocol that sets and sends physical layer, ATM
layer, virtual path, and virtual channel parameters that are exchanged by ATM interfaces.
When ILMI is run between two ATM interfaces, the interfaces exchange ILMI packets that consist of SNMP
messages across the physical connection. An ILMI link allows ILMI to run on an available virtual channel. When an
ILMI link is created to carry ILMI messages, a PVC is automatically created with default PVC attributes. The PVC is
deleted when the ILMI link is removed.
IMA
IMA is supported on channelized ASAP MDAs on the 7750 SR, 7710 SR, 7705 SAR, and ATM DS1/E1 CMA on the
7710 SR. For 9500 MPR/9500 MPRe device IMA support, see the 5620 SAM MPR User Guide.
IMA group bundles aggregate E1 or DS1 ATM paths into a single logical ATM interface. Each IMA group bundle can
have from 1 to 8 members, or links. Up to 56 IMA group bundles can be configured on a single 7750 SR or 7710 SR
MDA. Up to 8 IMA group bundles can be configured on a single 7705 SAR daughter card.
Each ATM Interface supports up to 48 VP/VC connection points. Each 16 × E1 ASAP Access (ETSI) board supports
up to 128 VP/VC connection points.
An IMA group bundle has the following common interface properties:
ATM encapsulation type is displayed on the ATM Interface properties form by clicking on the “Edit ATM
button”.
MTU value (of the primary link)
Member links inherit the common properties of the IMA group to which they belong. Only the properties of the primary
link can be changed. The primary link is the member with the lowest interface index or initialization sequence. The
primary link may change as member links are added and deleted from the IMA group.
Consider the following when you create a multilink IMA group bundle.
When a path becomes a member of an IMA group bundle, it is no longer a physical ATM path interface.
The members of the IMA group bundle inherit all of the properties of the primary link, such as the SONET
configuration and MTU. If you modify the configuration of the primary link, the configuration of the bundle
members is also modified.
Member links that are added after the primary link has been added to the IMA group bundle must match the
configuration of the primary link.
You cannot configure services on a member link.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 195/269
06.07.2017 Device management
17.3 SONET and SDH subchannel applications and
structure
SONET subchannel applications allow you to create multiple STS1 channels on deep channelized OC12 and OC3
ports, and to configure multiple DS0 connection termination points.
An STS1 subchannel is configured, or channelized, to carry one of the following payload types:
DS3
VT1.5
VT2
Because of the differences between SONET and SDH in multiplexing and mapping of tributary payloads into higher
digital levels, some building blocks of SDH have no SONET equivalent and therefore the containment hierarchy and
terminology for SDH is different from SONET. See "Comparison of SONET and SDH hierarchies" and "SDH AU4
and AU3 subchannel applications" in this section.
SONET DS3 payload
The following example, illustrated in Figure 175, shows the channelization sequence for a DS3 payload on a 1 ×
OC12 Deep Channel card.
1. One OC12 port is created when you create a channelized 1 × OC12 Deep Channel card.
2. This port can be channelized into 12 SONET STS1 subchannels from the four STS3s available on the port.
3. You can then configure each of these STS1s to carry a DS3 frame
4. Each DS3 frame can be channelized into 28 independent DS1 data channels or 21 independent E1 data
channels. Each channel must be created one at a time.
Figure 175 Channelized 1 × OC12 port structure using STS1/DS3 subchannels
SONET VT1.5 and VT2 payloads
The following example, illustrated in Figure 176, shows the channelization sequence for a VT1.5 or VT2 payload on a
1 × OC12 Deep Channel card.
1. One OC12 port is created when you create a channelized 1 × OC12 Deep Channel card.
2. This port can be channelized into 12 SONET STS1 subchannels from the four STS3s available on the port.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 196/269
06.07.2017 Device management
3. You can then configure each of these STS1s to be channelized to carry up to 28 DS1. For SONET sub
channel configuration you must select payload type VT1.5 or VT2. When you choose VT1.5 payload type,
seven VTG are implicitly created.
4. Each VTG is channelized into four independent VT1.5 channels or three VT2 channels, each of which can
carry an independent DS1 data channel. Each channel must be created one at a time.
5. Each VT1.5 DS1 channel can be configured to handle up to 24 DS0 groups. Each VT2 DS1 channel can be
configured to handle up to 32 DS0 groups. To use a DS1, you must create at least one DS0 group for the DS1
or E1.
Figure 176 Channelized 4 × OC3 port structure using VT subchannels
SONET subchannel syntax
The 5620 SAM uses the following SONET syntax for the STS1 subchannel:
card slot/daughtercard/port.STS1[STS3#].[STS1#]
DS3 channels from an STS1 subchannel use the following syntax:
slot/daughtercard/port.DS3[STS3#].[STS1#]
DS1 channels from a DS3 channel use the following syntax:
slot/daughtercard/port.DS1[STS3#].[STS1#].[DS1#]
E1 channels from a DS3 channel use the following syntax:
slot/daughtercard/port.DS1[STS3#].[STS1#].[E1#]
VT15 or VT2 from a VT group use the following syntax:
slot/daughtercard/port.VTG#[STS3#].[STS1#]
DS1 channels from a VT15 or VT2 use the following syntax:
slot/daughtercard/port.DS1[STS3#].[STS1#].[VT15#] or [VT2#}.[VTG#].[DS1#]
Table 174 shows an example of the SONET subchannel syntax.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 197/269
06.07.2017 Device management
Table 174 Example of SONET subchannel syntax for an OC12 port
Syntax Description Additional information
Channel 1/1/1 is the slot The sts1 parameter is 2.2 which means that it is the fifth
1/1/1.sts12.2 number/daughtercard STS1. There are four STS3s for an OC12 and each
number/port number STS3 has three STS1s such that the fifth STS1 is the
2 is the STS3 number second STS1 of the second STS3.
(1 to 4)
.2 is the STS1 number
(1 to 3)
Channel .ds32 is the STS3 Identifies the DS3 channel and shows how the sts1 level
1/1/1.ds32.2 number (1 to 4) acts as a place holder for the DS3
.2 identifies the STS1
number (1 to 3)
Channel .ds12.2.25 identifies a The DS1 is configured on the DS3.
1/1/1.ds1 DS1 channel (1 to 28)
2.2.25 on the DS3
Channel .e12.2.21 identifies a The E1 is configured on the DS3.
1/1/1.e1 E1 channel (1 to 21) on
2.2.21 the DS3
Channel .DS0Grp2.2.20.5 The DS0 is configured on the DS1 or E1 channel.
1/1/1.DS0Grp identifies one of the
2.2.20.5 DS0 channel groups: 1
to 28 for DS1; 2 to 32
for E1
Channel ds1 2.2.3.18 identifies a —
1/1/1.ds1 DS1 channel on the
2.2.3.18 VT15 or VT2 payload,
where 3 is the VT group.
Comparison of SONET and SDH hierarchies
SONET and SDH are compatible digital hierarchies that support identical transmission rates with similar framing
structures. However, SONET and SDH standards differ in the way they multiplex and map tributary payloads into
higher digital levels. Because of these differences, some SDH framing blocks do not have equivalent blocks in
SONET.
SONET provides one STS subchannel, the STS1, for mapping lowercapacity, deepchannel payloads while SDH
provides two alternative subchannels, the AU3 and the AU4. After an AU3 subchannel is created, an AU4 cannot
be created on that port in the case where the port is an OC3 (STM1). Conversely, if an AU4 subchannel is created,
an AU3 cannot be created on that port in the case where the port is an OC3 (STM1).
SONET and SDH transmission rates converge at 155.520 Mb/s where the SONET STS3c is equivalent to the SDH
STM1 bit rate. For lowercapacity payloads, such as DS1, E1, DS3, and E3, SONET provides one unique mapping
path for each payload while SDH permits two alternative paths for each payload as shown Figure 177.
Figure 177 Supported SONET/SDH multiplexing structures
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 198/269
06.07.2017 Device management
SDH AU4 and AU3 subchannel applications
SDH subchannel applications allow you to create AU4 or AU3 channels on deep channelized OC12 (STM4) and
OC3 (STM1) ports, and to configure multiple DS0 connection termination points.
After an AU4 subchannel is created, it implicitly contains three TUG3 groups. A TUG3 is channelized to carry one
of the following payload types:
TU3
TU11
TU12
After an AU3 subchannel is created, it is channelized to carry one of the following payload types:
DS3, E3
TU11
TU12
SDH TU3 payload
The following example, illustrated in Figure 178, shows the channelization sequence for a TU3 payload on a 4 ×
OC3 Deep Channel card.
1. Four OC3 ports are created when you create a channelized 4 × OC3 Deep Channel card.
2. The user creates each required AU4 subchannel.
3. Each AU4 subchannel implicitly contains three TUG3 groups.
4. You can then configure each TUG3 to carry a TU3 frame
5. Each TU3 frame is channelized into an independent E3 data channel and cannot be changed.
Figure 178 Channelized 4 × OC3 port structure using AU4/TU3 subchannels
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 199/269
06.07.2017 Device management
SDH E3 or DS3 payload
The following example, illustrated in Figure 179, shows the channelization sequence for an E3 or DS3 payload on a
4 × OC3 Deep Channel card using AU3 subchannels.
1. Four OC3 ports are created when you create a channelized 4 × OC3 Deep Channel card.
2. Each port can be channelized into up to three AU3 subchannel.
3. Each AU3 frame can be channelized into an independent E3 or DS3 data channel.
Figure 179 Channelized 4 × OC3 port structure using AU3/E3 subchannels
SDH TU11 and TU12 payloads
TU11 and TU12 payloads can be channelized using an AU4 subchannel or an AU3 subchannel. An AU4 sub
channel implicitly contains three TUG3 groups. A TUG3 and an AU3 channelized to carry TU11 or TU12 payloads
implicitly contain seven TUG2 tributary groups.
The following example, illustrated in Figure 1710, shows the channelization sequence for a TU11or a TU12 payload
on a 4 × OC3 Deep Channel card.
1. Four OC3 ports are created when you create a channelized 4 × OC3 Deep Channel card.
2. Each port can be channelized into one AU4 subchannel or three AU3 subchannels.
3. Each AU4 subchannel implicitly contains three TUG3 groups.
4. You can then configure each TUG3 group or each AU3 subchannel to carry a TU11 or TU12 payload.
5. Each TUG3 group or AU3 subchannel implicitly contains seven TUG2 tributary groups.
6. Each TUG2 group can be channelized into three independent TU12 channels or four independent TU11
channels.
7. Each TU12 can contain an E1 or DS1 data signal. Each TU11 can contain a DS1 data signal. Each E1 can be
configured to handle up to 31 DS0 groups. Each DS1 can be configured to handle up to 24 DS0 groups. To
use an E1 or a DS1, you must create at least one DS0 group for the DS1 or E1.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 200/269
06.07.2017 Device management
Note On the same TUG3 or AU3, you cannot mix TU1X with DS1 and E1 payload types. Every TU
1X on the same TUG3 or AU3 must use the same payload type, either E1 or DS1, not a mix of both.
The mix is shown in for illustrating the structure.
Figure 1710 Channelized 4 × OC3 port structure using AU4/TU subchannels
17.4 Workflow to manage port objects
The following workflow describes the sequence of highlevel tasks required to manage and configure port objects.
This workflow assumes that the physical devices have been installed, commissioned, and discovered. See chapter
10 for more information about device commissioning. See chapter 11 for more information about device discovery.
Note After they are configured, port objects can be accessed using the equipment navigation tree.
See chapter 5 for more information about using the equipment navigation tree. for more information.
1. As required, configure Ethernet ports; see Procedure 171.
2. As required, change the port mode; see Procedure 172.
3. As required, migrate SAPs from access mode to hybrid mode; see Procedure 173.
4. As required, configure the 5620 SAM to retain nondefault port MTU values; see Procedure 174.
5. As required, copy or move L2 access interface SAPs between ports; see Procedure 175.
6. As required, move L3 access interface SAPs within or between ports on the same NE; see Procedure 177.
7. As required, move L3 subscriber interface SAPs between ports on the same NE; see Procedure 178.
8. As required, add a queue group to an Ethernet port; see Procedure 179.
9. As required, configure SONET ports; see Procedure 1710.
10. As required, configure an HSMDA port scheduler override; see Procedure 1711.
11. As required, configure TDM DS3 ports; see Procedure 1712.
12. As required, configure serial ports; see Procedure 1713.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 201/269
06.07.2017 Device management
13. As required, configure PW ports; see Procedure 1714.
14. As required, configure ports on 7210 SAS devices, as follows:
a. Configure a 7210 SASM channelized TDM DS1 or E1 port; see Procedure 1715.
b. Assign policies to a 7210 SAS Ethernet port; see Procedure 1716.
c. Configure an SHG for 7210 SAS NEs; see Procedure 1717.
d. Configure PoE ports on supporting 7210 SAS NEs; see Procedure 1719.
15. As required, configure ports on 7705 SAR devices, as follows:
a. virtual Ethernet ports on a 7705 SAR 2port ring MDA; see Procedure 1718.
b. PoE ports on a 7705 SAR; see Procedure 1720.
c. GPS on a 7705 SAR; see Procedure 1721.
d. 7705 SAR ASAP channelized TDM port; see Procedure 1722.
16. As required, configure a 7710 SR channelized TDM DS1 or E1 port; see Procedure 1723.
17. As required, configure the following on OmniSwitch devices:
a. OmniSwitch Ethernet ports; see Procedure 1724.
b. OmniSwitch PoE ports; see Procedure 1725.
17.5 Workflow to manage channel objects
The following workflow describes the sequence of highlevel tasks required to manage and configure channel objects.
This workflow assumes that the physical devices have been installed, commissioned, and discovered, and that the
port objects have been configured. See chapter 10 for more information about device commissioning. See chapter 11
for more information about device discovery.
Note After they are configured, channel objects can be accessed using the equipment navigation
tree. See chapter 5 for more information about using the equipment navigation tree.
1. As required, configure SONET clear channels; see Procedure 1726.
2. As required, create channels on ports for card types that support multiple subchannels; see Procedure 1727.
3. As required, configure SONET subchannels; see Procedure 1728.
4. As required, configure SDH subchannels; see Procedure 1729.
5. As required, create VT15 (TU11) or VT2 (TU12) subchannels; see Procedure 1730.
6. As required, create TDM DS1 channels; see Procedure 1733.
7. As required, configure TDM DS1 or E1 channels; see Procedure 1732.
8. As required, configure serial channels; see Procedure 1733.
9. As required, create TDM DS3 channels; see Procedure 1734.
10. As required, configure TDM DS3 channels; see Procedure 1735.
11. As required, configure a DS3 or E3 channel as a network interface on a channelized ASAP MDA; see
Procedure 1736.
12. As required, configure an L3 interface on a DS3 or E3 channel on a channelized ASAP MDA; see Procedure
1737.
13. As required, configure a PVC; see Procedure 1738.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 202/269
06.07.2017 Device management
14. As required, create an ILMI link; see Procedure 1739.
15. As required, modify an ILMI link; see Procedure 1740.
17.6 Port configuration procedures
Use the following procedures to manage ports using the navigation tree.
Procedure 171 To configure Ethernet ports
Note Before you can configure 802.1X on an Ethernet access port, 802.1X must be enabled on the
device and an 802.1X policy must be created and distributed to the device.
See Procedure 1411 for information about enabling 802.1X on a device. See chapter 58 for information
about creating and distributing 802.1X policies.
2. Rightclick on the Port icon and choose Properties. The Physical Port (Edit) form opens.
3. Configure the required general parameters.
Only one MAC address can be assigned to a port. When a new MAC address is configured while the port is
operational, IP issues an ARP, if appropriate, and BPDUs are sent with the new MAC address. A default MAC
address is assigned by the system.
If the port is a LAG member, the Hold Time Up (seconds) parameter is configurable only if the port is the
primary member. The Hold Time Down (seconds) parameter is not configurable when the port is a LAG
member.
The DDM Event Suppression parameter is configurable only on ports on SFPs and XFPs optical modular
transceivers.
You cannot change the Mode parameter when the Enable DEI parameter is selected.
When you set the Mode parameter to Hybrid, you cannot set the Encapsulation Type parameter to Null.
The MTU value for a port is associated with the port mode and the port encapsulation type. By default, the
MTU of a hybrid port is set to the larger of the network and access MTUs.
You cannot deselect the Enable DEI parameter on a port when SAPs on that port are configured with color
aware meters. If you deselect the Enable DEI parameter, the ingress policies assigned to SAPs on the port
must be configured with meters whose Color Mode parameter is set to Color Blind. See Procedure 492.
Consider the following when you configure the Enable DEI parameter on a hybrid port.
When the Enable DEI parameter is selected, the network policy assigned to the port must be
configured to use DEI as the profile. The Default FC Profile parameter and the Profile parameter on the
Ingress Dot1p tab in the policy must be set to the DEI option. See Procedure 498.
You cannot select Enable DEI and assign a DEIconfigured network policy in the same configuration
process. You must first assign the network policy with the Default FC Profile and Profile parameters
set to the DEI option, and apply the change. Then you can subsequently select the Enable DEI
parameter.
4. If you set the Mode parameter to Hybrid, configure the required parameters in the Hybrid Ingress Buffer
Allocation and the Hybrid Egress Buffer Allocation panels, as required.
5. If you change the Mode parameter from Access to Hybrid and there are SAPs on the port, perform Procedure
173 to migrate the SAPs.
6. If you are configuring a 7210 SAS Ethernet port, you can add the port to an SHG on supporting NEs. See
Procedure 1717 for information about creating an SHG.
Note 1 A port cannot be added to or deleted from an SHG if it has a SAP configured on it or is
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 203/269
06.07.2017 Device management
a member of a LAG.
Note 2 A port cannot belong to more than one SHG; you must remove any SHGs from the
port before you can add the port to a different SHG.
7. Configure the Named Pool Buffer Policy for the port in the Named Buffer Pool panel.
i. Select an Ingress Pool Policy.
ii. Select an Egress Pool Policy.
iii. Configure the required parameters.
Note Ensure that the named pool mode is enabled. See Procedure 1633 in chapter 16
for more information.
8. Click on the States tab and configure the required parameters.
9. Click on the Policies tab.
Note The types of policies that you can choose depend on the type of NE, daughter card, and
the mode type of the port you are configuring.
The Network Queue and Accounting Policies panel are only displayed for network and
hybrid ports.
The Port Scheduler panel is only displayed for ports on nonHSMDA daughter cards.
The HSMDA Egress Scheduler panel is only displayed for ports on HSMDA daughter
cards.
10. Select an accounting policy for the port, if applicable.
11. Configure the Collect Accounting Statistics parameter, if required.
12. If you are configuring an access port on a 7210 SASE for the collection of packet forwarding statistics on
egress queues, configure the required parameters in the Egress Packets Forwarding panel.
For the 7210 SASE, access ports always contain eight queues. You can enable up to eight queues on any
port for the collection of packet forwarding statistics. However, only eight counters can be enabled for each
7210 SASE device. If no queues are enabled on a port, no accounting statistics are collected for that port.
13. If you are configuring a 7210 SAS Ethernet port, perform Procedure 1716, then go to step 19.
14. Select a network queue policy for the port, if applicable.
15. Select a port scheduler policy for the port, if applicable.
16. Select a port scheduler policy override for the port, if applicable.
i. Click Create in the Port Scheduler Policy Override panel. The Port Scheduler Policy Override form
opens.
ii. Click on the Override tab.
iii. Configure the Override, MAX, CIR, and PIR parameters for each required level.
iv. Save your changes and close the form.
17. Configure the Collect Stats parameter in the Port Scheduler Monitor panel, if required.
18. Select a scheduler policy for the port, if applicable.
19. Click on the DDM tab to view digital diagnostics monitoring information, if required.
20. Click on the Media Adaptor tab to view information about the SFP, if required.
21. If you are configuring a 7705 SARWx and the port supports DSL, the DSL tab is displayed. Configure DSL.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 204/269
06.07.2017 Device management
i. Click on the DSL tab.
ii. Configure the required parameters.
iii. Click on the XDSL Line tab.
iv. Choose an XDSL line and click Properties. The XDSL Line (Edit) form opens.
v. Configure the Administrative State parameter.
vi. Save your changes and close the form.
vii. Repeat steps ii to vi to configure more lines, if required.
22. Click on the Ethernet tab.
23. Configure the required parameters.
On the 7210 SASX, configure the SAP QoS Marking parameter to enable or disable SAPbased remarking.
On the 7210 SASX, configure the Egress Scheduler Mode parameter to choose FCbased or SAPbased
scheduling for access ports.
For 7210 SAS NEs, ports can forward multicast data packets to either L2 or L3 interfaces, but not both.
Configure the Multicast Ingress parameter according to your forwarding requirements.
Management connectivity between the 5620 SAM and the 7705 SAR may be lost if a line loopback is applied
to an Ethernet port that is carrying inband management traffic. The line loopback remains in effect until the
timer expires and the 7705 SAR removes the loopback.
Statistics are collected for IEEE 1588 PTP timestamps only when the Timestamp Capable parameter is
enabled on the 7705 SARA and 7705 SARW.
If you are configuring a 7705 SARWx and the port supports DSL, the EFMOAM tab appears. Perform the
required steps in Procedure 8850 to configure the EFMOAM tab.
24. Configure a port loopback on a 7210 SAS device.
i. If you are configuring a port loopback with MAC swap, you must first configure a noservice loopback
port. See Procedure 1429.
ii. Set the Type parameter to Internal. See step 23.
iii. Select a SAP in the SAP panel.
iv. In the MAC panel, configure the required parameters.
25. For supported 7210 SAS devices, associate the port with an operational group. See Procedure 146 for
information about 7210 SAS operational groups.
Perform one of the following:
a. For an L2 uplink port, assign the port to an operational group. Select an operational group in the Oper
Group panel.
b. For an access port, choose an operational group to monitor. Select an operational group in the Oper
Group panel.
26. If you are configuring an Ethernet port on a 2port ring MDA on a 7705 SAR8 or 7705 SAR18, select a VLAN
filter.
27. If you are configuring an Ethernet port on a 7705 SAR, Release 6.1 R1 or later, and you set the Mode
parameter to Hybrid in step 3, select a shaper policy, as required.
28. If the port is an access or hybrid port with QinQ or dot1q encapsulation, or a network port with dot1q
encapsulation, the MEPs tab is displayed. Add a facility MEP, if required.
Note Only one facility MEP can be configured on a port.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 205/269
06.07.2017 Device management
i. Click on the MEPs tab.
ii. Click Create. The MEP (Create) form opens.
iii. Select a global MEG for the MEP.
Note For portbased facility MEPs, the Maintenance Domain must be set for a Level of
0 or 1. See Procedure 892 for information on creating the MD.
iv. Configure the required parameters.
Only the parameters that are supported on the NE, daughter card, or port are displayed.
You cannot enable the collection of LMM statistics on a LAG facility MEP or on a tunnel facility MEP if
a service MEP is already configured to collect the LMM statistics information.
To enable fault propagation on a LAG facility MEP or on a tunnel facility MEP, the Facility Fault Notify
parameter must be enabled.
To link the facility tunnel status to the SAP, the Facility VLAN ID parameter must match the outer
encapsulation value of the SAP.
The CCM Padding Packet Size (Bytes) parameter cannot be configured when the CCM interval
parameter is set to 10 ms or 100 ms.
v. If the MD for the MEP has a Name Type of none the Y.1731 Tests tab is configurable. Click on the
Y.1731 Tests tab and configure the required parameters.
vi. Save your changes and close the form.
29. Click on the EFMOAM tab to configure and initiate the 802.3ah EFM OAM diagnostic as described in
Procedure 8850. Otherwise, continue to step 31.
30. To configure Ethernet link monitoring on the port, perform Procedure 8852.
31. Click on the 802.1x Port and 802.1x Port Authenticator tabs, and configure the required parameters.
You can enable the Tunneling parameter only when:
the port is in access mode
the Controlled Port Control parameter is set to Force Authorized
the port is not used as a SAP (except in an Epipe service)
32. Go to Procedure 179 to add a queue group to the port.
33. If the port is an HSMDA access port, the Egress Secondary Shapers tab is present. Add an egress secondary
shaper, if required.
Note 1 An HSMDA port is initially created with a default egress secondary shaper. The default
shaper cannot be deleted, but it can be modified.
Note 2 Nondefault egress secondary shapers can only be created if the port’s Mode
parameter is not set to the network option.
Note 3 You cannot switch the Mode of an HSMDA port to network if there are nondefault
egress secondary shapers on that port. An error message will be issued. You must delete any
nondefault egress secondary shapers from the port before switching its Mode to network.
i. Click on the Egress Secondary Shapers tab.
ii. Click Create. The HSMDA Egress Secondary Shaper (Create) form opens.
iii. Configure the required parameters.
iv. Click on the Classes tab.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 206/269
06.07.2017 Device management
v. Configure the Class Rate (kbps), Class Monitor Threshold (Kbytes) and Class Burst Threshold (bytes)
parameters for Classes 1 through 8, as required.
vi. Save your changes and close the form.
34. Click on the LLDP tab and configure the required parameters on the Nearest Bridge, Nearest Customer, and
Nearest Non TPMR subtabs.
35. Click on the Remote Peers subtab under the LLDP tab to search for and display LLDP remote peers
associated with the port. These remote peers are used to determine the physical topology of the network.
36. Configure a QoS pool, if required.
i. Click on the QoS Pool tab.
ii. Choose a QoS pool from the list and click Properties. The QoS Pool (Edit) form opens.
iii. Select a slope policy for the QoS pool.
iv. Configure the required parameters.
v. Save your changes and close the form.
37. Click on the Override Policy Items tab to configure HSMDA overrides, if required. See Procedure 1711 for
more information.
38. To configure a tunable optic DWDM MDA or IMM on a 7750 SR or 7450 ESS, click on the Optical Transport
Channel Unit tab and configure the required parameters.
39. Click on the OTU Alarms tab and select the OTU alarms for the Configured Alarms parameter.
40. Select a DWDM channel.
41. Click on the Optical tab and configure the required parameters.
42. Click on the Optical Amplifier tab and configure the Configured Alarms parameter.
43. Click on the Optical Tunable Dispersion Compensation Module tab and configure the required parameters.
44. Save your changes and close the form.
45. To configure coherent optics options for a 1Port 100GE OTU4 DWDM tunable optic IMM on a 7750 SR or
7450 ESS, click on the Coherent Optics tab and configure the required parameters.
46. Click on the Operational Status tab to view information about the state of the optical port.
47. Save your changes and close the form.
Procedure 172 To change the port mode
Note Save the device configuration before you perform this procedure. See the appropriate NE
documentation for more information.
2. Rightclick on the Port icon and choose Properties. The Physical Port (Edit) form opens.
3. Change the Mode parameter as required and click Apply.
4. If you are changing the mode from Access to Network and services are configured on the port, warnings are
displayed in a dialog box, depending on the permissions that are associated with your user role. Perform one
of the following:
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 207/269
06.07.2017 Device management
a. The default warning dialog indicates that the object has dependencies that will be deleted if you apply
the port mode change.
i. Click on View Dependencies button to see the dependencies (services and interfaces)
associated with the port.
ii. Click OK to confirm the configuration change.
Any services and interfaces associated with the port, including SAPs, are deleted, and the mode
for the port is changed to Network.
Note Changing the port mode from Access to Network without first removing the
dependencies results in a TopologyMisconfigured alarm.
b. For users who have the port.RestrictNodeConfigModify permission associated with their role, a warning
form appears, indicating that the object has dependencies that must be removed before proceeding.
i. Click on View Dependencies button to see the dependencies (services and interfaces)
associated with the port.
ii. Click OK to confirm the configuration change.
iii. Remove the services or interfaces associated with the port. You can manually delete them or
move them to other ports as described in this chapter.
iv. Repeat steps 2 and 3 to change the port mode to Network.
5. Save your changes and close the form.
Procedure 173 To migrate SAPs from access mode to hybrid mode
Note Save the device configuration before you perform this procedure. See the appropriate NE
documentation for more information.
2. Rightclick on an Ethernet port or SCLAG port icon and choose Properties. The Physical Port (Edit) form
opens.
3. Change the Mode parameter from Access to Hybrid. A dialog box opens.
4. Click OK to confirm the configuration change.
5. Perform an admin save.
6. Save your changes and close the form.
Procedure 174 To configure the 5620 SAM to retain nondefault port MTU
values
The MTU value for a port is associated with the port mode, such as access or network, and the port encapsulation
type. If you change the mode or encapsulation type of a port, the MTU value changes to the associated default. If
you do not want the port MTU values to change, you can use this procedure to configure the 5620 SAM to retain
each port MTU value, regardless of a mode or encapsulation type change.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 208/269
06.07.2017 Device management
Note You must perform this procedure on each main server in a redundant 5620 SAM deployment.
1. Log in to the 5620 SAM main server station as the samadmin user.
2. Navigate to the /opt/5620sam/server/nms/config directory.
3. Open the nmsserver.xml file using a plaintext editor.
Caution Contact your AlcatelLucent technical support representative before you attempt to
modify the nmsserver.xml file. Modifying the nmsserver.xml file can have serious
consequences that can include service disruption.
4. Add the following line to the end of the file:
<customMTURefresh refresh="true"/>
5. Save and close the nmsserver.xml file.
6. Open a console window.
7. Navigate to the /opt/5620sam/server/nms/bin directory.
8. If the main server is a standalone server, or the primary server in a redundant deployment, enter the following:
bash$ ./nmsserver.bash read_config
The main server reads the nmsserver.xml file and puts the configuration change into effect.
9. If the main server is the standby server in a redundant deployment, enter the following:
bash$ ./nmsserver.bash force_restart
The main server restarts and puts the configuration change into effect.
10. Close the console window.
Procedure 175 To copy or move L2 SAPs between ports
Note 1 If the source SAP has a MEP configured, and a CFM test is running on the service that has
the new MEP, the test must be stopped and executed again to make the new MEP active.
Note 2 Before you perform a SAP move operation, archive all existing test results associated with
the source SAP MEP.
You can also use the 5620 SAM clipboard to copy or move SAPs. See chapter 3 for information about using the 5620
SAM clipboard.
1. For the source NE, disable automatic configuration backup if it is enabled in the backup policy assigned to the
NE. Configure the Auto Backup Scheme parameter appropriately. See Procedure 241 for configuration
information.
2. On the source NE, use a CLI to back up the device configuration to a file. Ensure that you use a unique name
for the backup file to ensure that it is not accidentally overwritten. Enter the following at the CLI prompt:
admin save file_name
where file_name is a name that differs from the existing configuration file names on the NE and identifies this as the configuration in
effect before the copy or move operation
Caution An unsuccessful SAP copy or move may result in the deletion of one or more source
SAPs from the source NE. The backedup configuration file is required to restore the
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 209/269
06.07.2017 Device management
configuration on the source NE if a SAP copy or move operation fails.
See the appropriate device documentation for more information about saving the device configuration to a file.
3. For the destination NE, disable automatic configuration backup if it is enabled in the backup policy assigned to
the NE. Configure the Auto Backup Scheme parameter appropriately. See Procedure 241 for configuration
information.
4. On the destination NE, use a CLI to back up the device configuration to a file. Ensure that you use a unique
name for the backup file to ensure that it is not accidentally overwritten. Enter the following at the CLI prompt:
admin save file_name
where file_name is a name that differs from the existing configuration file names on the NE and identifies this as the configuration in
effect before the copy or move operation
See the appropriate device documentation for more information about saving the device configuration to a file.
5. Open the Deployment form to monitor deployments as they occur during the SAP copy or move operation.
Choose Administration NE Maintenance Deployment from the 5620 SAM main menu. The Incomplete
Deployments tab is displayed.
Caution AlcatelLucent strongly recommends that you monitor the NE deployments and the
alarm window during a SAP copy or move operation to ensure that faults that may arise during
the operation are immediately detected.
The Incomplete Deployments tab of the Deployment form notifies the 5620 SAM operator of
configuration changes that are not successfully deployed to the NE, and the 5620 SAM alarm
window alerts the operator to object failures on the NE that are related to the copy or move
operation.
7. Arrange the forms on the GUI so that the SAP Copy/Move form, the Deployment form, and the alarm window
are all shown.
8. On the SAP Copy/Move form, click on the Result tab and then click Result Export Path. The Result Export
Path form opens.
9. Specify the file name and location in which to save a text file that contains the results of the SAP copy or
move operation.
10. Click Set. The Result Export Path form closes.
11. On the SAP Copy/Move form, click on the General tab.
12. Configure the Current Mode parameter as L2 Access Interface.
13. Configure the Service Type parameter.
14. Select a source node and a source port in the Source panel.
15. Configure the Outer Encap Value Start and Outer Encap Value End parameters, and the Inner Encap Value
Start and Inner Encap Value End parameters, if applicable.
16. Select a destination node and a destination port in the Destination panel.
17. Configure the required parameters in the Execution Details panel.
18. Click Execute to begin the copy or move operation. The Execution Result panel displays the execution state
of the copy or move operation and the number of successful and failed operations based on the input criteria.
Note 1 When you copy or move a SAP on an L2 interface and there is a nonzero value
assigned to the PIM Snooping parameter Maximum Number of Groups, the value is not copied
or moved to the new location. You must manually configure the Maximum Number of Groups
parameter in the new location.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 210/269
06.07.2017 Device management
Note 2 The Succeeded state only specifies that the SAP copy or move operation is
successfully committed to the database. After the SAP copy or move operation is executed,
you must monitor the Deployment form for any deployment errors.
19. Monitor the Deployments form and the alarm window for any deployment failures and faults related to the SAP
copy or move operation. Click Refresh on the Deployments form to update the list, if required.
20. Click on the Result tab to view a list of the successful and failed operations as identified by the 5620 SAM.
You can double click the result to open it in a new window and view the details.
21. Click Refresh Result to view the most recent results.
22. To view the information for an individual SAP copy or move operation, move the mouse pointer over the
Message field of the operation.
23. If a copy or move operation fails, you can restore the previous source NE configuration using the backup
configuration file created in step 2.
i. Open a CLI on the source NE.
ii. Enter the following at the command prompt to load the saved configuration file:
exec file_name
where file_name is the name of the configuration file that was specified in step 2
The SAPs that were deleted during the unsuccessful copy or move operation are restored on the NE.
iii. Enter the following at the command prompt to save the NE configuration:
admin save
24. If a copy or move operation partially fails, you can restore the previous destination NE configuration using one
of the following methods.
Note If the copy or move operation fails completely, there is no need to restore the previous
configuration because no SAPs are created on the destination NE.
a. Restore the backedup configuration file.
i. Open a CLI on the destination NE.
ii. Enter the following at the command prompt to load the saved configuration file:
exec file_name
where file_name is the name of the configuration file specified in step 4
The previous configuration is restored on the NE.
iii. Enter the following at the command prompt to save the NE configuration:
admin save
b. Manually delete the SAPs that the copy or move operation created on the destination NE.
25. Restore the previous automatic configuration backup setting in the backup policy of the source NE by
configuring the Auto Backup Scheme parameter appropriately. See Procedure 241 for configuration
information.
26. Restore the previous automatic configuration backup setting in the backup policy of the destination NE by
configuring the Auto Backup Scheme parameter appropriately. See Procedure 241 for configuration
information.
27. Close the form.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 211/269
06.07.2017 Device management
Procedure 176 To copy or move L2 access interface SAPs between services
You can move L2 access interface SAPs between VPLS, MVPLS and VLL services. You can move the source SAP
only to another service, and not within the same service. You cannot move the source SAP to a different site; it can
be moved only to a different service on the same site.
The source and destination service types must be the same. The source and destination site types (Site, BSite or I
Site) must be the same.
VPLS L2 access interfaces can be used for MSAPs, access interfaces for SPB in control mode, and throughput
tests. When you move an L2 interface, the 5620 SAM deletes the SAP from the source site. The 5620 SAM does not
check that the source site has consistent configuration after the move, and for example, a throughput test might
reference nonexistent SAPs.
1. Choose Manage Services from the 5620 SAM main menu. The Manage Services form opens.
2. Choose a VPLS, MVPLS, or VLL service and click Properties. The Service_Type Service (Edit) form opens.
4. Rightclick on the L2 access interface that you want to move and choose Move to Another Service. The
Select Services form opens with a list of eligible target services.
5. Select a service. The 5620 SAM moves the L2 access interface SAP to the selected service and removes the
service from the from the source service.
6. Close the forms.
Procedure 177 To move L3 SAPs within or between ports on the same NE
To copy or move L3 access interface SAPs from one port to another on different NEs, see “XML API template
administration” in the 5620 SAM Scripts and Templates Developer Guide for information about the administrative
tasks associated with service templates.
You can also use the 5620 SAM clipboard functionality to move SAPs. See chapter 3 for information about using the
5620 SAM clipboard.
Note L3 access interfaces are not bound to a port; for example, loopback interfaces cannot be
moved.
1. For the NE, disable automatic configuration backup if it is enabled in the backup policy assigned to the NE.
Configure the Auto Backup Scheme parameter appropriately. See Procedure 241 for configuration information.
2. On the NE, use a CLI to back up the device configuration to a file. Ensure that you use a unique name for the
backup file to ensure that it is not accidentally overwritten. Enter the following at the CLI prompt:
admin save file_name
where file_name is a name that differs from the existing configuration file names on the NE and identifies this as the configuration in
effect before the move operation
See the appropriate device documentation for more information about saving the device configuration to a file.
3. Open the Deployment form to monitor deployments as they occur during the SAP move operation. Choose
Administration NE Maintenance Deployment from the 5620 SAM main menu. The Incomplete Deployments
tab is displayed.
Caution AlcatelLucent strongly recommends that you monitor the NE deployments and the
alarm window during a SAP move operation to ensure that faults that may arise during the
operation are immediately detected.
The Incomplete Deployments tab of the Deployment form notifies the 5620 SAM operator of
configuration changes that are not successfully deployed to the NE, and the 5620 SAM alarm
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 212/269
06.07.2017 Device management
window alerts the operator to object failures on the NE that are related to the move operation.
5. Arrange the forms on the GUI so that the SAP Copy/Move form, the Deployment form, and the alarm window
are all shown.
6. Click on the Result Export Path tab.
7. Specify the file name and location in which to save a text file that contains the results of the SAP move
operation.
8. Click Set. The Result Export Path form closes.
9. Configure the Current Mode parameter as L3 Access Interface.
10. Configure the Service Type parameter.
11. Select a source node and a source port in the Source panel.
12. Configure the Outer Encap Value Start and Outer Encap Value End parameters, and the Inner Encap Value
Start and Inner Encap Value End parameters, if applicable.
13. Select a destination port in the Destination panel.
14. Configure the required parameters in the Execution Details panel.
15. Click Execute to start the move operation. The Execution Result panel displays the execution state of the
move operation and the number of successful and failed operations based on the input criteria.
16. Monitor the Deployments form and the alarm window for any deployment failures and faults related to the SAP
move operation. Click Refresh on the Deployments form to update the list, if required.
17. Click on the Result tab to view a list of the successful and failed operations as identified by the 5620 SAM.
You can double click the result to open it in a new window and view the details.
18. Click Refresh Result to view the most recent results.
19. To view the information for an individual SAP move operation, move the mouse pointer over the Message field
of the operation.
20. If a move operation fails, you can restore the previous NE configuration using the backup configuration file
created in step 2.
i. Open a CLI on the NE.
ii. Enter the following at the command prompt to load the saved configuration file:
exec file_name
where file_name is the name of the configuration file specified in step 2
The SAPs that were deleted during the unsuccessful move operation are restored on the NE.
iii. Enter the following at the command prompt to save the NE configuration:
admin save
21. Restore the previous automatic configuration backup setting in the backup policy of the NE by configuring the
Auto Backup Scheme parameter appropriately. See Procedure 241 for configuration information.
22. Close the forms.
Procedure 178 To move L3 subscriber interface SAPs between ports on the
same NE
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 213/269
06.07.2017 Device management
To copy or move L3 subscriber interface SAPs from one port to another on different NEs, see “XML API template
administration” in the 5620 SAM Scripts and Templates Developer Guide for more information about the
administrative tasks associated with service templates.
You can also use the 5620 SAM clipboard functionality to move SAPs. However, you can only move all of the SAPs
in a group interface; you cannot move a subset of SAPs. See chapter 3 for information about using the 5620 SAM
clipboard.
1. For the NE, disable automatic configuration backup if it is enabled in the backup policy assigned to the NE.
Configure the Auto Backup Scheme parameter appropriately. See Procedure 241 for configuration information.
2. On the NE, use a CLI to back up the device configuration to a file. Ensure that you use a unique name for the
backup file to ensure that it is not accidentally overwritten. Enter the following at the CLI prompt:
admin save file_name
where file_name is a name that differs from the existing configuration file names on the NE and identifies this as the configuration in
effect before the move operation
See the appropriate device documentation for more information about saving the device configuration to a file.
3. Open the Deployment form to monitor deployments as they occur during the SAP move operation. Choose
Administration NE Maintenance Deployment from the 5620 SAM main menu. The Incomplete Deployments
tab is displayed.
Caution AlcatelLucent strongly recommends that you monitor the NE deployments and the
alarm window during a SAP move operation to ensure that any faults that arise during the
operation are immediately detected.
The Incomplete Deployments tab of the Deployment form notifies the 5620 SAM operator of
configuration changes that are not successfully deployed to the NE, and the 5620 SAM alarm
window alerts the operator to object failures on the NE that are related to the move operation.
5. Arrange the forms on the GUI so that you can view the entire SAP Copy/Move form, the Deployment form,
and the alarm window.
6. Click on the Result Export Path tab. The Result Export Path form opens.
7. Specify the file name and location in which to save a text file that contains the results of the SAP move
operation.
8. Click Set. The Result Export Path form closes.
9. Configure the Current Mode parameter as L3 Subscriber Interface SAP.
10. Configure the Service Type parameter.
11. Select a source node and a source port in the Source panel.
12. Select a destination port in the Destination panel.
13. Configure the required parameters in the Execution Details panel.
14. Click Execute to start the move operation. The Execution Result panel displays the state of the move
operation, and the number of successful and failed operations based on the input criteria.
15. Monitor the Deployments form and the alarm window for any deployment failures and faults related to the SAP
move operation. Click Refresh on the Deployments form to update the list, if required.
16. Click on the Result tab to view a list of the successful and failed operations, as identified by the 5620 SAM.
You can double click the result to open it in a new window and view the details.
17. Click Refresh Result to view the most recent results.
Note If one SAP fails, all SAPs under the same group interface fail because the SAPs can
only move together. In this case, there is insufficient information to determine which SAP
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 214/269
06.07.2017 Device management
caused the problem using the 5620 SAM.
18. To view information about an individual SAP move operation, move the mouse pointer over the Message field
of the operation.
19. If a move operation fails, you can restore the previous NE configuration using the backup configuration file
created in step 2.
i. Open a CLI on the source NE.
ii. Enter the following at the command prompt to load the saved configuration file:
exec file_name
where file_name is the name of the configuration file specified in step 2
The SAPs that were deleted during the unsuccessful move operation are restored on the NE.
iii. Enter the following at the command prompt to save the NE configuration:
admin save
20. Restore the previous automatic configuration backup setting in the backup policy of the NE by configuring the
Auto Backup Scheme parameter appropriately. See Procedure 241 for configuration information.
21. Close the forms.
Procedure 179 To add a queue group to an Ethernet port
You can create a port queue group on an Ethernet port after creating an Ingress/Egress Queue Group Template policy.
Note You must use the same name for the port queue group and Ingress/Egress Queue Group
Template policy.
1. On the equipment tree, navigate to the port object where you want to add a queue group. The path is Network
NE Shelf Card Slot n Daughter Card Slot n Port n/n/n.
2. Rightclick on an Ethernet port icon and choose Properties. The Physical Port (Edit) form opens.
3. Click on the Ethernet tab.
4. Perform one of the following:
a. Click on the Network Egress Queue Group tab.
b. Click on the Access Egress Queue Group tab.
c. Click on the Access Ingress Queue Group tab.
Note The Network Egress Queue Group tab is available if queue groups are supported
on the port, depending on the NE release and IOM type. See section "Port queue groups"
in chapter 69 for more information about supported devices and IOM types.
5. Click Create. The Queue Group (Create) form opens.
6. Select a queue group template policy.
7. Configure the required parameters.
8. If you are adding a network egress queue group, go to step 9. Otherwise, continue to step 10.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 215/269
06.07.2017 Device management
9. Select a policer control policy.
10. Select an accounting policy.
Note Only the accounting policies with the Type parameter configured to one of the following
options are listed:
Queue Group Octets
Queue Group Packets
Combined Queue Group
11. Configure the Collect Accounting Statistics parameter, if required.
12. Select a scheduler policy.
13. If you are adding an access ingress queue group, go to step 20. Otherwise, continue to step 14.
14. Configure the required parameters.
The Aggregate Rate Limit (kbps) and FrameBased Accounting parameters are configurable only if you did not
select a scheduler policy. The FrameBased Accounting parameter is configurable only if you configure
the Aggregate Rate Limit (kbps) parameter.
15. If you are adding a network egress queue group (including queue groups for HSMDA), go to step 20.
Otherwise, continue to step 16.
16. Click on the Host Matching tab.
Note The Host Matching tab is available only if the Instance ID is set to 1.
17. Click Create. The Host String (Create) form opens.
18. Configure the Host String parameter.
19. Click OK. The Host String (Create) form closes and the information on the Host Matching tab is updated.
20. Click on the Overrides: Type Queue tab, where Type will be Network Egress, Access Egress, or Access
Ingress, depending on your selection in step 4.
21. Click Create. The Queue Override (Create) form opens.
22. Select a Queue ID.
23. Click on the Override tab.
24. If you are configuring an access egress queue group queue override for HSMDA, then go to step 28.
25. Configure the required override parameters.
The Weight and CIR Weight parameters are only applicable to access egress queue group overrides.
The parameters are configurable when the Override check box is enabled.
26. Configure the Monitor Queue Depth parameter, as required. If you enable this parameter, then a Statistics sub
tab will be displayed when all the changes are applied. The queue depth statistics collected at the port level
will be available here.
27. Go to step 30.
28. Configure the required parameters.
The parameters are configurable when the associated Override check box is enabled.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 216/269
06.07.2017 Device management
29. If you need to configure an override for a Slope Policy, enable the associated Override check box and select a
slop policy.
30. Save your changes and close the forms.
Procedure 1710 To configure SONET ports
1. On the equipment tree, navigate to the port object where you want to configure a SONET port. The path is
Network NE Shelf Card Slot n Daughter Card Slot n Port n/n/n.
2. Rightclick on a port icon and choose Properties. The Physical Port (Edit) form opens.
3. Configure the required parameters.
The DDM Event Suppression parameter is configurable only on ports on SFPs and XFPs optical modular
transceivers.
4. Click on the States tab and configure the Administrative State parameter.
5. Click on the Channels tab to configure the SONET/SDH channel.
a. Click Create to create a new channel.
b. Choose a channel from the list and click Properties to view and edit the channel parameters.
c. Choose a channel from the list and click Delete to remove a channel from the port.
6. Click on the SONET tab and configure the required parameters.
7. Click on the SONET Monitoring tab and configure the required parameters.
8. Click on the SONET Overhead tab and configure the required parameters.
Enter a J0 byte that identifies the circuit. This byte is inserted continuously at source. This can be checked
against the expected value by the receiver. If no byte is entered, then null is used. The parameter is
configurable when the SONET Section Trace Mode is set to Byte.
The J0 String parameter is configurable when the SONET Section Trace Mode is set to String.
9. Save your changes and close the form.
Procedure 1711 To configure an HSMDA override
1. On the equipment tree, navigate to the port object where you want to configure a SONET port. The path is
Network NE Shelf Card Slot n Daughter Card Slot n Port n/n/n.
Select an HSMDA card.
2. Click on the Override Policy Items tab.
3. Click Create. The Port Egress HSMDA Scheduler Policy Override (Create) form opens.
4. Click on the Override tab and configure the required parameters.
The Rate (Mbps) parameter is configurable when a Group is not specified for the applied HSMDA scheduler
policy. The Weight in Group parameter is only configurable when Group 1 or Group 2 is specified for the
HSMDA scheduler policy.
5. Save your changes and close the forms.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 217/269
06.07.2017 Device management
Procedure 1712 To configure TDM DS3 ports
1. On the equipment tree, navigate to the port object where you want to configure a TDM DS3 port. The path is
Network NE Shelf Card Slot n Daughter Card Slot n Port n/n/n.
2. Rightclick on a port icon and choose Properties. The Physical Port (Edit) form opens.
3. Configure the required parameters on the General tab.
4. Click on the States tab and configure the Administrative State parameter.
5. Click on the DS3/E3 tab and configure the required parameters.
6. Save your changes and close the form.
Procedure 1713 To configure serial ports
You can configure serial ports on a 12 × Serial Data card on the 7705 SAR.
1. On the equipment tree, navigate to the port object where you want to configure a serial port. The path is
Network NE Shelf Card Slot n Daughter Card Slot n Port n/n/n.
2. Rightclick on a port icon and choose Properties. The Physical Port (Edit) form opens.
3. Configure the required parameters.
4. Click on the States tab and configure the Administrative State parameter.
5. Save your changes and close the form.
Procedure 1714 To configure PW ports
1. On the equipment tree, rightclick on an NE and choose Properties. The Network Element (Edit) form opens.
2. Click on the PW Ports tab. A list of existing PW ports is displayed.
3. Click Create to create a PW port or choose a port and click Properties. The PW Port (Create|Edit) form opens.
4. Configure the required general parameters.
5. Configure node redundancy for the PW port, if required.
i. Click Node Redundancy. The Manage Node Redundancy form appears, preconfigured for MC peer
groups.
ii. Click Search and configure an existing MC peer group, or click Create and configure a new MC peer
group. See Procedure 421.
The Node Redundancy button allows you to access the MC sync group configuration within the MC
peer group in order to add PW port sync tags.
6. Save the changes and close the forms.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 218/269
06.07.2017 Device management
Procedure 1715 To configure a 7210 SASM channelized TDM DS1 or E1 port
1. On the equipment tree, navigate to the port object where you want to configure a 7210 SASM channelized
TDM DS1 or E1 port. The path is Network NE Shelf Card Slot n Daughter Card Slot n Port n/n/n.
2. Rightclick on a 7210 SASM port object that contains a channelized DS1 or E1 and choose Properties. The
Physical Port (Edit) form opens.
3. Configure the required parameters.
4. Select a split horizon group.
Note To create or delete a 7210 SAS SHG, see Procedure 1717.
5. Click on the DS1/E1 tab and configure the required parameters.
The Line Impedance parameter only appears when the Port Type parameter is set to E1.
6. Click on the QoS Pool tab.
7. Choose a QoS pool from the list and click Properties. The QoS Pool (Edit) form opens.
8. Select a slope policy.
9. Save your changes and close the form.
10. Click on the States tab and configure the Administrative State parameter.
11. Save your changes and close the forms.
Procedure 1716 To assign QoS policies to a 7210 SAS Ethernet port
The policies that can be assigned to a 7210 SAS Ethernet port vary depending on the port mode. See Table 175.
Table 175 7210 SAS QoS policies and port modes
7210 SAS QoS policy Supported port mode
Port scheduler policy All port modes
Port access egress policy Access
Network policy (of port type) L2 uplink, network, hybrid
Network queue policy L2 uplink, network, hybrid
Support for port modes and policies also varies depending on the chassis type. For more information see "7210 SAS
QoS policies" and the NE documentation.
Note 1 Slope policies for Ethernet ports are assigned to QoS pools (buffer pools) on the port; see
Procedure 171.
Note 2 Network policies of network interface type are assigned to L3 network interfaces; see
Procedures 2810 and 2811.
1. On the equipment tree, navigate to a configured Ethernet port object on a 7210 SAS device. The path is
Network NE Shelf Card Slot n Daughter Card Slot n Port n/n/n.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 219/269
06.07.2017 Device management
2. Rightclick on a configured Ethernet port object and choose Properties. The Physical Port (Edit) form opens.
3. Click on the Policies tab, then click on the 7210 Specific tab.
Note The policies that can be assigned vary depending on the chassis type and port mode.
4. Select a port scheduler policy.
For information about how to create a 7210 and 1830 Port Scheduler policy, see Procedure 4920.
5. Select an access egress policy.
For information about how to create a 7210 and 1830 Port Access Egress policy, see Procedure 494.
6. Select a network policy.
For information about how to create a 7210 and 1830 Network policy, see Procedure 498.
When the Enable DEI parameter is selected on a hybrid port, the network policy assigned to the port must be
configured to use DEI as the profile. The Default FC Profile parameter and the Profile parameter on the
Ingress Dot1p tab in the policy must be set to the DEI option. See Procedure 498.
7. Select a network queue policy.
For information about how to create a 7210 and 1830 Network Queue policy, see Procedure 4914.
8. Save your changes and close the forms.
Procedure 1717 To create a 7210 SAS SHG
Traffic that arrives on a access or access uplink port or LAG within an SHG is not copied to other ports and LAGs in
the same SHG; the traffic is copied to ports and LAGs in other SHGs if they exist within the same VPLS. Ports and
LAGs are added to an SHG when you configure a port or LAG on a 7210 SAS. SHGs are not supported for a VPLS
instance.
1. On the equipment tree, rightclick on the device where you want to configure the SHG and select Properties.
The Network Element (Edit) form opens.
2. Click on the Split Horizon Groups tab.
3. Click Create. The Split Horizon Group (Create) form opens.
4. Configure the required parameters and click OK.
Note 1 Only one SHG can be configured per service.
Note 2 A SHG and a Mesh SDP Binding cannot exist simultaneously on a single service.
5. Repeat steps 3 to 4 to add another SHG, if required.
6. Save your changes and close the form.
Procedure 1718 To configure a virtual Ethernet port on a 7705 SAR 2port ring
MDA
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 220/269
06.07.2017 Device management
Perform this procedure to configure a virtual Ethernet port on a 7705 SAR 2 × 10Gig Bridged Ethernet XFP + 1 ×
2.5G Virtual Ethernet card on a 7705 SAR8 and 7705 SAR18. See Procedure 497 for information about configuring
a network policy of ring type for a 7705 SAR. See Procedure 1640 for information about configuring a ring port on a
7705 SAR 2 × 10Gig Bridged Ethernet XFP + 1 × 2.5G Virtual Ethernet card.
1. On the equipment tree, choose Network NE Shelf Card Slot n Daughter Card Slot n Virtual Port n/n/n,
where the virtual port is the port object you need to configure.
2. Rightclick on the Virtual Port icon and choose Properties. The Virtual Port (Edit) form opens.
3. Configure the required parameters.
4. Click on the States tab and configure the Administrative State parameter.
5. Click on the Policies tab.
6. Select a network queue policy.
7. Click on the Ethernet tab and configure the required parameters.
You must configure the Down When Looped parameter value as Enabled to see the Down When Looped
Configuration panel parameters.
8. Click on the Network Interfaces tab to create a network interface on the virtual Ethernet port.
9. Click Add. The Create Network Interface Routing Instance form opens. See Procedure 2810 for information
on creating a network interface.
Note You can only bind a virtual Ethernet port to a network interface.
10. Save your changes and close the form.
Procedure 1719 To configure PoE ports on a 7210 SAS
The 7210 SASMxp ETR and 7210 SAST ETR support PoE on specific ports. See the NE documentation for more
information about 7210 SAS support of PoE.
You can view information about power consumption and availability on the PoE tab of the shelf properties form for
supporting 7210 SAS NEs.
1. On the equipment tree, navigate to the port object on the required 7210 SAS NE. The path is Network NE
Shelf Card Slot n Daughter Card Slot n Port n/n/n.
2. Rightclick on the required port and choose Properties. The Physical Port (Edit) form opens.
3. Click on the PoE tab and configure the PoE Mode parameter.
4. View the information about the PoE connection.
5. Save your changes and close the form.
Procedure 1720 To configure PoE ports on a 7705 SAR
You can configure PoE on a 7705 SARH, 7705 SARHc, 7705 SARW, and 7705 SARWx.
Note You can view information about power consumption and availability on the PoE tab of the shelf
properties form.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 221/269
06.07.2017 Device management
1. On the equipment tree, navigate to the port object where you want to configure PoE. The path is Network
NE Shelf Card Slot Daughter Card Slot Port n/n/n.
2. Rightclick on the port on which you want to configure PoE and choose Properties. The Physical Port (Edit)
form opens.
3. Click on the PoE tab and configure the PoE Mode parameter.
4. Save your changes and close the form.
5. If you are configuring a 7705 SARH, perform the following steps to configure the PoE power supply source. If
you are configuring a 7705 SARHc, 7705 SARW, or 7705 SARWx, go to step 1.
i. On the equipment tree, rightclick on the 7705 SARH device on which you want to configure PoE and
choose Properties. The Network Element (Edit) form opens.
ii. On the Network Element (Edit) form navigation tree, expand the Shelf object and the Card Slot object.
iii. If you are configuring a 7705 SARH, Release 6.1 or later, rightclick on the Daughter Card Slot object
and choose Properties. The Daughter Card Slot (Edit) form opens.
If you are configuring an earlier release 7705 SARH, rightclick on the Shelf object and choose
Properties. The Shelf (Edit) form opens.
iv. Configure the PoE Power Supply Source parameter in the PoE panel.
v. Save your changes and close the form.
Procedure 1721 To configure GPS on a 7705 SAR
You can configure GPS on the 7705 SARH and on the following 7705 SARWx variants:
4 GigE 4port xDSL GPS Rx
5 GigE GPS Rx
5 GigE PoE+ GPS Rx
On the 7705 SARH, the GPS receiver is pluggable, but on the 7705 SARWx, the GPS receiver is integrated.
1. On the equipment tree, navigate to the port object where you want to configure GPS. The path is Network
NE Shelf Card Slot Daughter Card Slot Port 1/3/1.
2. Rightclick on the port on which you want to configure GPS and choose Properties. The Physical Port (Edit)
form opens.
3. Click on the GPS tab and configure the required parameters.
4. Save your changes and close the form.
Procedure 1722 To configure a 7705 SAR ASAP channelized TDM port
This procedure applies to 7705 SAR channelized TDM DS1/E1 ports and channelized TDM DS3/E3 ports.
1. On the equipment tree, navigate to the port object where you want to configure a 7705 SAR ASAP
channelized TDM port. The path is Network NE Shelf Card Slot n Daughter Card Slot n Port n/n/n.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 222/269
06.07.2017 Device management
2. Rightclick on a port object that contains a channelized port (DS1/E1 or DS3/E3) and choose Properties. The
Physical Port (Edit) form opens.
3. Configure the required parameters.
4. Click on the DS1/E1 or DS3/E3 tab and configure the required parameters.
All ports of the ASAP daughter card are automatically configured to the same port type when the first port is
configured. A mix of DS1 and E1 ports or DS3 and E3 ports is not supported. The Port Type parameter can
only be modified when no channels are configured on any port of the daughter card. If all of the channels are
deleted on the daughter card, the port type is automatically set to DS1 or DS3 for all ports.
5. Click on the States tab and configure the Administrative State parameter.
6. Save your changes and close the form.
Procedure 1723 To configure a 7710 SR channelized TDM DS1 or E1 port
1. On the equipment tree, rightclick on the device where you need to configure a 7710 SR channelized TDM
DS1 or E1 port and select Properties. The Network Element (Edit) form opens.
2. On the Network Element (Edit) form navigation tree, expand to the port level and click on a 7710 SR port
object that contains a channelized DS1 or E1. The Physical Port (Edit) form opens.
3. Configure the required parameters.
4. Click on the DS1/E1 tab and configure the required parameters.
5. Click on the States tab and configure the Administrative State parameter.
6. Save your changes and close the form.
Procedure 1724 To configure OmniSwitch Ethernet ports
Note You can configure MVRP fixed ports, 802.1 Q ports, aggregate ports, and VLAN Stacking
Network ports.
1. On the equipment tree, navigate to the port object where you want to configure an OmniSwitch Ethernet port.
The path is Network NE Shelf Card Slot n Port n/n/n.
2. Rightclick on a port object and choose Properties. The Physical Port (Edit) form opens.
3. Configure the required parameters.
An access port is used for customerfacing VLAN service traffic.
A network port or channel is used for network access in the service provider transport or infrastructure
network. Typically, only one OmniSwitch network port is required for tree topology; ring topology requires two
ports.
The Automatic VLAN Binding parameter is only supported on Stacked VLANs.
The Automatic VLAN Binding parameter is only supported on Stacked VLANs.
4. Click on the States tab and configure the Administrative State parameter.
5. Click on the Policies tab.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 223/269
06.07.2017 Device management
Note A port must have a service access point associated with it before you can apply a UNI
policy to the port.
6. Select a UNI policy.
7. Click on the Ethernet tab and configure the required parameters.
The InterFrame Gap (bytes) parameter is only configurable on Gigabit Ethernet ports.
The Default VLAN Restore, Default VLAN Enable, Ignore BPDU, Authenticate, and Ingress Filtering
parameters are only configurable when the Enable Port Mobility parameter is set to Enable.
8. Click on the LLDP tab and configure the required parameters.
9. Click on the Remote Peers subtab under the LLDP tab to search for and display LLDP remote peers that are
associated with the port. The remote peers are used to determine the physical topology of the network.
10. Click on the MVRP tab and configure the required parameters.
11. Configure VLAN restrictions, if required.
i. Click on the VLAN Restrictions tab.
ii. Click Create. The MVRP VLAN Registration form appears.
iii. Configure the required parameters.
iv. Save your changes and close the form.
12. Click on the QoS tab, and configure the required parameters.
The Servicing Mode parameter does not apply to OS 6900 and OS 10K devices.
13. If you are configuring a port on an OS 6900 or OS 10K device, click on the Queue tab and configure the
required parameters.
14. Click on the DHCP Snooping tab, and configure the required parameters. The tab is only available when the
port is associated with a VLAN that has DHCP snooping enabled or DHCP snooping is enabled at the switch
level.
15. Click on the Ethernet Hybrid tab, and configure the required parameters. The tab is only available for hybrid
Ethernet ports.
16. Click on the PoE tab, and configure the required parameters. The tab is only available for PoE ports.
17. Click on the LPS Learned MAC Entries tab to view the MAC addresses learned on the port. LPS must be
enabled on the port. See Procedure 2969 for information about configuring LPS on an Ethernet port.
18. Click Create to add static MAC address entries, if required. The MAC Entries (Create) form opens.
Note A port must be LPSenabled and belong to a VLAN before you can add static MAC
addresses to the port.
19. Select a VLAN Site.
20. Configure the MAC Address parameter.
21. Save your changes and close the form.
22. Repeat steps 18 to 21 to add another MAC address, if required.
23. Save your changes and close the forms.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 224/269
06.07.2017 Device management
Procedure 1725 To configure OmniSwitch PoE Ports
1. On the equipment tree, navigate to the card object where you want to configure an OmniSwitch PoE port. The
path is Network NE Shelf Card Slot n. The Card Slot (Edit) form opens.
2. Click on the PoE tab and configure the required parameters.
3. Save your changes and close the forms.
17.7 Channel and framing link configuration procedures
Use the following procedures to manage channels and framing links using the navigation tree.
Procedure 1726 To configure SONET clear channels
Perform this procedure to configure SONET clear channels on OC3 to OC192 ports that provide clear channel
services. Each port supports one clear channel.
1. Choose Equipment from the navigation tree view selector.
2. Rightclick on the device on which you want to create a clear channel port and select Properties. The Network
Element (Edit) form opens.
3. On the Network Element (Edit) form navigation tree, expand the Shelf icon.
4. Expand to the port level and click on a clear channel port object. The Physical Port (Edit) form opens. SONET
is the default framing scheme.
Note A clear channel port is a port on a card that is not designated Deep Channelized.
5. Configure the required parameters and click Apply.
6. In the navigation tree, rightclick on the port and choose Create Channel. The Channel (Create) form opens. If
there are no channels available on that port, the Create Channel menu option menu is dimmed.
7. Configure the required parameters.
The Encapsulation Type parameter is configurable when the Mode parameter is set to Access.
The DDM Event Suppression parameter is configurable only on ports on SFPs and XFPs optical modular
transceivers.
8. Click Apply.
a. If the Encapsulation Type parameter of the port is ATM, the form is refreshed.
b. If the Encapsulation Type parameter of the port is not ATM, go to step 11.
9. Click Edit ATM. If the Edit ATM button is not visible, click More Actions and choose Edit ATM to configure the
ATM interface. The ATM interface form opens.
10. Configure the required parameters.
11. To create an ILMI link, see Procedure 1739.
12. Click OK and close the forms.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 225/269
06.07.2017 Device management
Procedure 1727 To perform a bulk channel creation on ports that support
multiple subchannels
Perform this procedure to create the maximum number of channels on ports that support multiple subchannels. Table
176 lists the port types that support bulk channel creation.
Table 176 Bulk channel creation support
Node OC3 OC12 DS3 E3 APS common APS SONET
ASAP ASAP port VTG
7450 ESS X X X X X X
7705 SAR8 X X — — — —
7705 SAR
8v2
7705 SAR18
7710 SR X X X X X X
7750 SR MG X X X X X X
Note This procedure assumes you have preconfigured an NE with an appropriate daughter card that
supports multiple subchannels.
1. Choose Equipment from the view selector in the navigation tree.
2. Locate and expand the device on which you need to perform a bulk channel creation.
3. Perform one of the following:
a. For OC3, OC12, DS3 ASAP, and E3 ASAP ports, rightclick on a port icon and choose Create
Maximum # of Channels. The Create Maximum # of Channels form opens.
b. For APS common ports and APS SONET VTGs, right click on an APS Common Config SONET
channel icon and choose Create Maximum # of Channels. The Create Maximum # of Channels form
opens.
Note APS common ports and APS SONET VTGs are created when you create APS
groups. See Procedure 401 for more information.
4. Configure the required parameters.
5. Click Execute.
Procedure 1728 To configure SONET subchannels
SONET subchannels are available on deep channelized OC12 and OC3 ports. SONET STS1 channels support the
following payload types:
DS3
VT15
VT2
1. Choose Equipment from the navigation tree view selector.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 226/269
06.07.2017 Device management
2. Rightclick on the device on which you want to configure SONET subchannels and select Properties. The
Network Element (Edit) form opens.
3. On the Network Element (Edit) form navigation tree, expand the Shelf icon.
4. Expand to the port level, rightclick on a port object, and choose Create Channel. The Create Channel form
opens.
Note If there are no channels available on that port, the Create Channel menu option menu is
dimmed
5. Configure the required parameters.
For an OC3 port, use a value from 1 to 3. For an OC12 port, use a value in the format <1 to 4>.<1 to 3>.
The DDM Event Suppression parameter is configurable only on ports on SFPs and XFPs optical modular
transceivers.
6. Click Apply.
7. Create the STS1 (AU3) subchannels according to the payload type configured:
a. To create VT15 (Sdh TU11) subchannels, go to Procedure 1730.
b. To create VT2 (Sdh TU12) subchannels, go to Procedure 1730.
c. To create a DS3 or E3 (SDH framing only) clear channel, go to step 8.
8. To create a DS3 or E3 clear channel, perform the following steps:
i. From the navigation tree, select an STS1 or AU3 channel and choose Create Channel. The DS3/E3
Channel (Create) form opens.
For AU3 channels, DS3 and E3 channelization is available.
For STS1 channels, only DS3 channelization is available.
ii. Configure the Description parameter.
iii. Configure the Channelized parameter.
Choose Ds1 to channelize the DS3 to carry up to 28 DS1 channelized to the DS0 level.
Choose E1 to channelize the DS3 to carry up to 21 E1 channelized to the DS0 level.
Choose None to create a DS3 or E3 clear channel. Configure the required parameters.
iv. Click OK.
If you set the Channelized parameter to None, a DS3 clear channel in Access mode is created under
the STS1 or the AU3 in the navigation tree.
If you set the Channelized parameter to DS1, a DS3 channelized for DS1 is created under the STS1
(AU3). Go to step 10 in Procedure 1734 to create the DS1 channels.
If you set the Channelized parameter to E1, a DS3 channelized for E1 is created under the STS1 (AU3)
in the navigation tree. Go to step 10 in Procedure 1734 to create the E1 channels.
Procedure 1729 To configure SDH subchannels
SDH subchannels are available on deep channelized OC12 and OC3 ports. SDH AU4 channels support the
following payload types:
TU3
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 227/269
06.07.2017 Device management
TU11
TU12
SDH AU3 channels support the following payload types:
DS3
E3
TU11
TU12
Perform this procedure to configure SDH subchannels on ports that provide channelized services. You must first
configure port framing to SDH since default framing on SONET/SDH ports is SONET.
1. Choose Equipment from the navigation tree view selector.
2. Rightclick on the device on which you want to configure SDH subchannels and select Properties. The
Network Element (Edit) form opens.
3. On the Network Element (Edit) form navigation tree, expand the Shelf icon.
4. Expand to the port level and click on a deep channelized port. The Physical Port (Edit) form opens.
5. Click on the SONET tab and set the Framing parameter to SDH.
6. Click OK.
7. Rightclick on the port again and choose Create Channel. The Channel Type Selection form opens.
8. Choose one of the following channel types and click OK:
a. SONET STS1 channelization and SDH AU3 channelization are equivalent. Go to step 5 of Procedure
1728.
b. The Sts3 SONET Channel (Create) form opens. If there are no channels available on that port, the
Create Channel menu option menu is dimmed.
The Payload Type parameter for SDH STM1 (AU4) is set to TUG3. There is no SONET framing
equivalent. Go to step 9.
9. Configure the required parameters.
10. Click on the States tab and configure the Administrative State.
11. Click OK. The STM1 (AU4) channel appears in the navigation tree under the port of the daughter card. It
contains three TUG3 groups.
12. Rightclick on a TUG3 group and choose Properties. The Sdh Tug3 (Edit) form opens.
13. Choose one of the following options to configure the Payload Type parameter:
a. PDH Tu3. Click Cancel and go to step 14 to create a TU3 channel.
b. SONET VT15 (SDH Tu11). Click Apply and go to Procedure 1730.
c. SONET VT2 (SDH Tu12). Click Apply and go to Procedure 1730.
14. To create a TU channel, rightclick on the TUG3 group and choose Create Channel. The TU3 Channel
(Create) form opens.
15. Configure the required parameters.
16. Click on the States tab and configure the Administrative State.
17. Click OK. A TU3 channel is created under the TUG3 group in the navigation tree.
18. Rightclick on the Tu3 and choose Create Channel. The DS3/E3 Channel (Create) form opens.
The E3 is the only payload type available.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 228/269
06.07.2017 Device management
19. Configure the required parameters.
20. Click on the States tab and configure the Administrative State.
21. Click OK. An E3 clear channel is created under the AU4/TUG3 in the navigation tree.
Procedure 1730 To create VT15 (TU11) or VT2 (TU12) subchannels
A SONET VTG and an SDH TUG2 are equivalent groups. A VTG contains four VT15 channels or three VT2. A
TUG2 contains four TU11 channels or three TU12. An SDH TUG 3 has no SONET equivalent, however, it contains
seven TUG2. (An STM1/AU4 contains three TUG3). See "Comparison of SONET and SDH hierarchies" in
section 17.3.
An STS1 channelized to carry a VT15 or VT2 payload type contains seven VTG. An AU3 or a TUG3 channelized to
carry a TU11 or TU12 payload type contain seven TUG2. STS1 and AU3 channelization are shown in Figure 1711.
Figure 1711 SONET VTG and SDH TUG2 in navigation tree
Each VTG (TUG2) supports up to four VT15 (TU11) channels or three VT2 (TU12) channels. Create each VTG/TUG2
channel one at time.
1. Complete Procedure 1728 or Procedure 1729 to carry a VT15 (TU11) or VT2 (TU12) payload type.
a. Go to step 2 to create a VT15 (TU11) channel.
b. Go to step 3 to create a VT2 (TU12) channel.
2. To create a VT15 (TU11) channel, perform the following steps:
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 229/269
06.07.2017 Device management
i. Choose Equipment from the navigation tree view selector.
ii. Rightclick on the device where you want to create a VT15 (TU11) channel and select Properties. The
Network Element (Edit) form opens.
iii. On the Network Element (Edit) form navigation tree, expand the Shelf icon.
iv. Expand to the channel level, rightclick on a VTG or TUG2 channel group that is to carry a VT15 (TU11)
payload and choose Create Channel. The SONET VT (SDH Tu) Channel (Create) form opens.
v. Configure the required parameters.
Set the Local Channel ID to a value in the range 1 to 4 since there are four VT15 (TU11) in a VTG
(TU2).
The default payload type for a VT15 (TU11) channel is PDH DS1. There is no other available payload
type.
vi. Click OK. A VT15 channel is created under the VTG or a TU11 channel is created under the TUG2 in
the navigation tree.
vii. Rightclick on a VT15 or TU11 channel and choose Create Channel. The DS1/E1 Channel (Create)
form opens.
The Local Channel ID is equal to the VT15 channel Local Channel ID parameter and the channel type
is set to DS1 since a VT15 or TU11 channel supports one DS1.
viii. Click OK A DS1 channel is created under the VT15 or the TU11 in the navigation tree.
You can create up to 28 VT15 (TU11) channels on a VTG (TUG2).
ix. Repeat steps 1 and 2 for each VT15 (TU11) channel that you want to create.
x. Since a DS1 channel is not used as a SAP, create a DS0 group for each DS1 channel created. Go to
step 11 of Procedure 1734.
3. To create a VT2/TU12 channel, complete these steps:
i. From the navigation tree, select a VTG or TUG2 channel group to carry a VT2 (TU12) payload and
choose Create Channel. The SONET VT (SDH Tu) Channel (Create) form opens.
ii. Configure the required parameters.
Set the Local Channel ID to a value in the range 1 to 3 since there are three VT2 (TU12) in a VTG
(TUG2).
PDH E1 is not available for SONET framing.
iii. Click OK. A VT2 channel is created under the VTG, or a TU12 channel is created under the TUG2 in
the navigation tree.
iv. Rightclick on the VT2 or TU12 channel and choose Create Channel. The DS1/E1 Channel (Create)
form opens.
The Local Channel ID is equal to the VT2 channel Local Channel ID parameter, since a VT2 channel
supports one E1 or DS1.
v. Click on the States tab and configure the Administrative State parameter.
vi. Click OK. A DS1 channel is created under the VT2 in the navigation tree. An E1 or DS1 is created
under the TU12. You can create up to 21 VT2 (TU12) channels on a VTG (TUG2).
vii. Repeat steps 1 and 2 for each VT2 (TU12) that you want to create.
viii. Since a DS1/E1 channel is not used as a SAP, create a DS0 group for each DS1 or E1 channel
created. Go to step 11 of Procedure 1734.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 230/269
06.07.2017 Device management
Procedure 1731 To create TDM DS1 or E1 channels
Note If you are using OSSI to create a DS1 or E1 channel, the create request creates a channel with
a G704 CRC framing type for E1 channels and ESF for DS1 channels. To modify the channel framing
type requires a second request.
Perform this procedure to create DS1/E1 channels and child objects on a channelized DS1/E1 port.
1. On the equipment tree, rightclick on the device where you want to configure TDM DS1 or E1 channels and
select Properties. The Network Element (Edit) form opens.
2. On the Network Element navigation tree, expand to the port level.
3. Click on a port. The Port form opens.
4. Configure the required general parameters.
5. Click on the DS1/E1 tab and configure the required parameters.
6. Click OK.
7. Rightclick on the port and choose Create Channel. The DS1/E1 Channel (Create) form opens. If there are no
channels available on that port, the Create Channel menu option is dimmed.
8. Click OK.
9. To create DS0 channel groups:
i. On the navigation tree, rightclick on a DS1 or E1 channel under the required port and choose Create
Channel. The DS0 Channel Group (Create) form opens.
ii. Configure the required parameters.
For the Local Channel ID parameter, for a DS0 group from a DS1 channel, choose from 1 to 24. For a
DS0 group from an E1 channel, choose from 2 to 32.
Note 1 All channel groups on a 7705 SAR ASAP port must have the same mode
configured. When the first channel group is configured, all other channel groups on the
port must be set to the same mode.
Note 2 The default encapsulation type for the 7705 SAR is N/A. The encapsulation
type must be changed from N/A to a valid type. For instance, to support CAS signaling,
the encapsulation type must be set to CEM. After a valid encapsulation type is
configured for a channel group, the encapsulation type cannot be changed for that
channel group. To change the encapsulation type, the channel group must be deleted and
recreated.
Note 3 On a 16/32x Channelized ASAP, you must configure the MDA mode in order to
use certain encapsulation types. See Procedure 1640 for more information on
configuring the MDA mode.
iii. Click on the Channel Group tab and configure the required parameters.
10. Save your changes and close the forms.
Procedure 1732 To configure TDM DS1 or E1 channels
Perform this procedure to configure DS1/E1 channel parameters and child objects on a channelized DS1/E1 port, add
a DS0 channel group, collect and view performance statistics, or view alarm information.
1. Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 231/269
06.07.2017 Device management
2. Rightclick on the device you need to configure TDM DS1 or E1 channels and choose Properties. The
Network Element (Edit) form opens.
3. Expand the Shelf icon to the channel level and choose a DS1 or E1 channel. The DS1/E1 Channel (Edit) form
opens.
4. Click on the States tab and configure the Administrative State parameter.
5. Click on the Channel tab. The DS1/E1 Channel (Edit) form opens.
6. Configure the required parameters.
The Synchronous Status Messages, E1 Tx DUS/DNU, and E1 SSMBit parameters are configurable only on
E1 channels on a 7705 SAR.
The Clock Source parameter value Differential is only supported on the following 7705 SAR cards:
16/32 × Channelized DS1/E1 ASAP v2 on a 7705 SAR8, 7705 SAR8 v2, or 7705 SAR18
4 × Channelized DS3/E3 ASAP on a 7705 SAR8, 7705 SAR8 v2, or 7705 SAR18, Release 6.1 R3 or
later
4 × Channelized OC3/OC12 ASAP SFP on a DS1/E1 channel, on a 7705 SAR8, 7705 SAR8 v2, or
7705 SAR18, Release 6.2 R1 or later
ASAP channelized card on a 7705 SARA, Release 6.0 R2 or later
Note If you create an MLPPP bundle and the DS1 BER exceeds a threshold, the PPP link is
automatically removed from the MLPPP bundle.
7. Add a DS0 channel group, if required.
i. Click on the SubChannels tab.
ii. Click on the Create Cha... tab. The DS0 Channel Group (Create) form opens.
iii. Configure the required parameters.
Note 1 On a 16/32x Channelized ASAP, you must configure the MDA mode in order to
specify the encapsulation type. See Procedure 1640 for more information about
configuring the MDA mode.
Note 2 You must set the value of the Encapsulation Type parameter to CEM if you are
configuring an MDA card of type 16 × Channelized DS1/E1 ASAP v2 or 32 ×
Channelized DS1/E1 ASAP v2 on a 7705 SAR8 or 7705 SAR18.
iv. Click OK.
v. Click OK.
8. Perform one of the following:
a. Click Collect to collect performance statistics data on demand. The collected statistics are listed on the
form.
b. Click Collect All to collect one ondemand statistics record for each statistic type that the object
supports. The collected statistics are listed on the form.
9. Click on the Faults tab to view alarm information, if required.
Note If are configuring a 7705 SAR and selected a clock source of adaptive, you can click on
the Adaptive Clock History tab to view channel adaptive clock performance data for the
preceding 15 min.
10. Save your changes and close the forms.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 232/269
06.07.2017 Device management
Procedure 1733 To create serial channels
Perform this procedure to create serial channel and child objects from a Serial Data Interface port.
1. Choose Equipment from the navigation tree view selector.
2. Navigate to the device where you want to configure serial channels and expand to the port level.
3. Rightclick on the port and choose Create Channel. The Serial Channel (Create) form opens. If there are no
channels available on that port, the Create Channel menu option is dimmed.
4. Click on the States tab and configure the Administrative State parameter. Click Apply.
5. Click on the Channel tab and configure the required parameters.
Depending on the serial type of the configured port, different parameters are configurable in the Control Leads
panel.
6. Create DS0 channel groups:
i. Click on the SubChannels tab.
ii. Click on the Create Cha... button. The DS0 Channel Group (Create) form opens.
iii. Configure the required parameters.
Note 1 The default encapsulation type for the 7705 SAR is N/A. The encapsulation
type must be changed from N/A to a valid type. After a valid encapsulation type is
configured for a channel group, the encapsulation type cannot be changed for the channel
group. To change the encapsulation type, the channel group must be deleted and re
created.
Note 2 On an SDI MDA, you must configure the serial type to X.21 or V.35 to use the
FR, HDLC, or cHDLC encapsulation types. See Procedure 1713 for more information.
iv. Click OK.
7. Ave your changes and close the form.
Procedure 1734 To create TDM DS3 channels
Perform this procedure to create DS3 channel and children objects from a channelized DS3 port.
1. Choose Equipment from the navigation tree view selector.
2. Rightclick on the device on which you want to create a TDM DS3 channel and select Properties. The
Network Element (Edit) form opens.
3. On the Network Element (Edit) form navigation tree, expand the Shelf icon.
4. Expand to the port level and click on a port. The Physical Port (Edit) form opens.
5. Configure the required parameters.
6. Choose the DS3/E3 tab and configure the required parameters. Click OK.
7. Rightclick on the port again and choose Create Channel. The DS3/E3 Channel (Create) form opens. If there
are no channels available on that port, the Create Channel menu option is dimmed.
8. To create the DS3/E3 channel, complete these steps:
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 233/269
06.07.2017 Device management
a. Configure the Channelized parameter to DS1 or E1, if you want to channelize to the DS0 level.
b. Configure the Channelized parameter to None if this is a clear channel application.
Configure the required parameters.
The Local Channel ID parameter is configured automatically and the Mode parameter is always Access
for TDM.
Note 1 On a 4x Channelized ASAP, you must configure the MDA mode in order to use
certain encapsulation types. See Procedure 1640 for more information on configuring the
MDA mode.
Note 2 If you want to configure a DS3/E3 channel as a network interface on a
channelized ASAP MDA, see Procedure 1736.
9. Click OK.
If this is a Channelized DS1 or E1 application, continue to step 10.
10. To create DS1 or E1 channels, complete these steps:
i. From the navigation tree, select a DS3 channel and choose Create Channel. The Create DS1/E1
Channel form opens.
ii. Configure the Local Channel ID parameter.
For DS1 choose from 1 to 28.
For E1 choose from 1 to 21.
iii. Click OK. The DS1 or E1 channels are created under the DS3 in the navigation tree.
11. To create DS0 channel groups, complete these steps:
i. From the navigation tree, select a DS1 or E1 channel and choose Create Channel from the contextual
menu to create DS0 groups. The DS0 Channel (Create) form opens.
ii. Configure the required parameters.
For a DS0 group from a DS1 choose from 1 to 24 for the Local Channel ID parameter. For a DS0 group
from an E1, choose from 2 to 32.
Note On a 4x Channelized ASAP, you must configure the MDA mode in order to use
certain encapsulation types. See Procedure 1640 for more information on configuring the
MDA mode.
iii. Click on the Channel Group tab and configure the required parameters.
iv. Click OK. The timeslot is assigned to the DS0 channel group in the navigation tree.
Procedure 1735 To configure TDM DS3 channels
Perform this procedure to configure DS3 channels and children objects from a channelized DS3 port.
1. Choose Equipment from the navigation tree view selector.
2. Rightclick on the device where you want to configure TDM DS3 channels and select Properties. The Network
Element (Edit) form opens.
3. On the Network Element (Edit) form navigation tree, expand the Shelf icon.
4. Expand to the channel level and click on a DS3 channel. The DS3/E3 Channel (Edit) form opens. Configure
the required parameters.
5. Configure the Channelized parameter and click Apply.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 234/269
06.07.2017 Device management
If you choose DS1 or E1, perform steps 10 to 21.
6. Configure the Encapsulation Type parameter and click Apply.
a. If you choose BCP Null, BCP DOT1 Q, or IPCP, go to step 7.
b. If you choose FR, go to step 8.
c. If you choose Cisco HDLC, go to step 9.
d. If you choose WAN Mirror, perform steps 11 to 14.
7. Configure the PPP interface for the channel, if required.
i. Click Edit PPP. The PPP Interface form opens. Configure the required parameters.
ii. Click OK.
iii. Perform steps 11 to 14.
8. Configure the FR interface, if required.
i. Click Edit FR. The FR Interface form opens. Configure the required parameters.
ii. Click on the Frf12 tab and configure the required parameters. Set the Mode parameter to Enabled.
iii. Click Select beside the MCFR Egress QoS Profile parameter. The Select MCFR Egress Qos Profile
FR Configuration form opens.
iv. Choose a profile from the list and click OK. The Select MCFR Egress Qos Profile FR Configuration
form closes and the FR Interface form is refreshed with the MCFR Egress QoS Profile information.
v. Click OK.
vi. Perform steps 11 to 14.
9. Configure the Cisco HDLC information.
i. Click on the Cisco HDLC tab and configure the required parameters.
ii. Perform steps 11 to 14.
10. Configure the DS1 and DS0 channels. Perform the following steps:
i. Click on the SubChannels tab.
ii. Click Create. The DS1/E1 Channel (Create) form opens. Configure the required parameters.
iii. Click on the States tab and configure the required parameters.
iv. Click OK.
11. Click on the States tab and configure the required parameters.
12. Click on the Channel tab. The DS3/E3 Channel (Edit) form opens. Configure the required parameters.
The Clock Source parameter value Differential is supported on a 4 × channelized DS3/E3 ASAP MDA for a
DS3/E3 channel, on a 7705 SAR8, 7705 SAR8 v2, or 7705 SAR18, Release 7.0 R1 or later.
13. Click on the Message Data Link tab and configure the required parameters.
The MDL Message Type parameter specifies the Line Message Data Link message for a DS3 and specifies
the transmission method of a message over a channelized interface. The parameter is only applicable if the
DS3 is using Cbit framing. The default is disabled. Click on the check boxes to enable transmission methods
and enter text strings to choose the message options for this parameter as required. The transmission options
are:
Test Signal
DS3 Path
Idle Signal
Table 177 describes the MDL message options.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 235/269
06.07.2017 Device management
Table 177 MDL message options
Option String Description
Length
Port Number String 0 to 38 specifies the port ID code
characters
Generator Number 0 to 38 specifies the generator number to send in the MDL test
String characters signal message
Equipment ID 0 to 10 specifies the Equipment ID code
Code characters
Location ID Code 0 to 11 specifies the Location ID code
characters
Frame ID Code 0 to 10 specifies the Frame ID code
characters
Unit ID Code 0 to 6 specifies the unit ID code
characters
Facility ID Code 0 to 38 specifies the facility ID code
characters
14. Click OK.
15. Rightclick on a DS1 channel in the navigation tree and choose Properties. The property form for the channel
opens.
16. Click on the States tab and configure the required parameters.
17. Add a DS0 channel group, if required. Perform the following steps:
i. Click on the SubChannels tab.
ii. Click Create. The DS0 Channel Group (Create) form opens.
iii. Configure the required parameters.
Note On a 4x Channelized ASAP, you must configure the MDA mode in order to use
certain encapsulation types. See Procedure 1640 for more information on configuring the
MDA mode.
iv. Click OK.
18. Click on the Channel tab and configure the required parameters.
19. Click OK.
20. Configure timeslots for the DS0 channel group. Perform the following steps.
i. Choose a DS0 channel in the navigation tree and choose Properties. The property form for the channel
opens.
ii. Configure the required parameters.
iii. Click on the States tab and configure the required parameters.
iv. Click on the Channel Group tab and configure the required parameters.
Choose one or more timeslots. You can use the Select All and Deselect All buttons.
v. If you set the Encapsulation Type parameter to BCP Null, BCP DOT1 Q, or IPCP in step ii, you can
configure the PPP for the timeslot on the Channel Groups tab.
Click Edit PPP. The PPP Interface form opens. Configure the required parameters.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 236/269
06.07.2017 Device management
The Compression parameter is configurable when the DS1 or E1 channel group is on an ASAP
MDA in a 7710 SR or 7750 SR.
Click OK.
21. Click OK.
Procedure 1736 To configure a DS3/E3 channel as a network interface on a
channelized ASAP MDA
1. Choose Equipment from the navigation tree view selector.
2. Rightclick on the device where you want to configure a DS3/E3 channel and select Properties. The Network
Element (Edit) form opens.
3. On the Network Element (Edit) form navigation tree, expand the Shelf icon to the port level.
4. Perform one of the following.
a. If you are configuring an OCn channelized ASAP MDA, rightclick on an available port and choose
Create Channel. The Sts SONET Channel (Create) form opens; go to step 5.
b. If you are configuring a DS3/E3 channelized ASAP MDA, rightclick on an available port and choose
Create Channel. The DS3/E3 Channel (Create) form opens; go to step 9.
5. Configure the required parameters.
6. Click on the States tab and configure the required parameters.
7. Click OK.The Sts SONET Channel (Create) form closes and the STS1 channel appears in the navigation tree
under the port of the channelized ASAP daughter card.
8. Rightclick on the STS1 channel and choose Create Channel. The DS3/E3 Channel (Create) form opens.
9. Configure the required parameters.
10. Click on the States tab and configure the required parameters.
11. Click Apply. The form displays additional tabs.
12. Click on the Channel tab and configure the required parameters.
13. Click on the Message Data Link tab and configure the required parameters.
The MDL Message Type parameter specifies the Line Message Data Link message for a DS3 and specifies
the transmission method of a message over a channelized interface. The parameter is only applicable if the
DS3 is using Cbit framing. The default is disabled. Click on the check boxes to enable transmission methods
and enter text strings to choose the message options for this parameter as required. The transmission options
are:
Test Signal
DS3 Path
Idle Signal
Table 178 describes the MDL message options.
Table 178 MDL message options
Option String Description
Length
Port Number String 0 to 38 specifies the port ID code
characters
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 237/269
06.07.2017 Device management
14. Click OK. The DS3/E3 channel appears in the navigation tree under the port on the channelized ASAP MDA.
Procedure 1737 To configure an L3 interface on a DS3/E3 channel on a
channelized ASAP MDA
1. Choose Equipment from the navigation tree view selector.
2. Rightclick on the device on which you want to configure an L3 interface and select Properties. The Network
Element (Edit) form opens.
3. On the Network Element (Edit) form navigation tree, expand the Shelf icon.
4. Expand to the channel level and click on a DS3/E3 channel on a channelized ASAP MDA port. The DS3/E3
Channel (Edit) form opens.
5. Click on the Policies tab to configure the policies for the DS3/E3 channel. Perform the following steps.
i. Click Select beside the Network Queue Policy Name parameter. The Select Network Queue Policy
DS3/E3 Channel list form opens.
ii. Select a network queue policy from the list and click OK. The Select Network Queue Policy DS3/E3
Channel list form closes and the DS3/E3 Channel (Edit) form reappears.
iii. Click Select beside the ID parameter in the Accounting Policy panel. The Select Accounting Policy
DS3/E3 Channel list form opens.
iv. Select an accounting policy from the list and click Ok. The Select Accounting Policy DS3/E3 Channel
list form closes and the DS3/E3 Channel (Edit) form refreshes with the accounting policy information.
v. Configure the Collect Accounting Statistics parameter.
vi. Click Select in the Port Scheduler Policy panel to assign a port scheduler policy to the port. The Select
Port Scheduler Policy Physical Port form opens.
vii. Select a port scheduler policy from the list and click OK. The Select Port Scheduler Policy Physical
Port form closes.
6. Click on the Network Interfaces tab.
7. Click Create. The Create Network Interface Routing Instance form opens.
8. See Procedure 2810 to create a network interface on the DS3/E3 channel.
The port is set to the DS3/E3 channel by default.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 238/269
06.07.2017 Device management
9. The L3 interface appears on the Network Interfaces tab. Close the DS3/E3 Channel (Edit) form.
Procedure 1738 To configure a PVC
PVCs are automatically created by the device when a new L3 interface over ATM is created on the 5620 SAM, and
when a new ILMI link is created between ATM interfaces. See Procedure 1739 for more information about creating
ILMI links.
1. Choose Equipment from the navigation tree view selector.
2. Rightclick on the device where you want to configure a PVC and select Properties. The Network Element
(Edit) form opens.
3. On the Network Element (Edit) form navigation tree, expand the Shelf icon.
4. Expand to the channel level and click on a SONET/SDH ATM clear channel. The property form for the channel
opens.
5. Click on the L3 Interfaces tab. Choose the appropriate interface from the list and click Properties. The L3
Interface form opens.
6. Click on the ATM tab and configure the required parameters.
7. Click Apply.
8. To view more information about the PVC:
i. Click View PVC Connection. The ATM PVC Connection form opens.
ii. Click on the tabs to view information for the ATM PVC connection.
9. Click Cancel to close the ATM PVC Connection form, the L3 Interface form, and the channel form.
Procedure 1739 To create an ILMI link
Perform this procedure to create an ILMI link between device ATM interfaces. This functionality is supported on the
7750 SR and 7710 SR. Ensure that ATM QoS policies are configured before you create the ILMI link. See chapter 48
for more information about creating ATM QoS policies.
1. Perform one of the following to open the ATM interface properties form.
a. Use the navigation tree
i. Choose Equipment from the navigation tree view selector.
ii. Rightclick on the device on which you want to create an ILMI link and select Properties. The
Network Element (Edit) form opens.
iii. On the Network Element (Edit) form navigation tree, expand the Shelf icon.
iv. Expand to the port level and click on a clear channel port. The Physical Port (Edit) form opens.
Note A clear channel port is a port on a card that is not designated Deep
Channelized.
v. Click on the Channels tab.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 239/269
06.07.2017 Device management
vi. Choose the appropriate channel from the list and click Properties. The Channel (Edit) form
opens.
vii. Click Edit ATM. The ATM Interface form opens.
b. Use the Manage Equipment list form to search for a clear channel port with an ATM interface.
i. Choose Manage Equipment Equipment from the 5620 SAM main menu. The Manage
Equipment form opens.
ii. Choose Port.
iii. Configure the filter criteria to search for ATM encapsulation types.
iv. Click Search and select an entry by doubleclicking. Alternatively, select an entry and click
Properties. The Select form closes and the Channel (Edit) form opens.
v. Click Edit ATM. The ATM Configuration (Edit) form opens.
2. Click Create ILMI Link. The Configure ILMI Link form opens.
3. Configure the required parameters.
The Restore KeepAlive Defaults parameter restores the default values of the KeepAlive Polling Frequency
(seconds), KeepAlive Polling Count, and KeepAlive Test Frequency (seconds) parameters.
The KeepAlive Test Frequency (seconds) parameter is configurable when the Protocol Version parameter is
set to 4.0.
4. Choose an ingress ATM QoS policy by clicking Select. The Select ATM Policy ATM ILMI Link Configuration
list form opens. Click Search and choose an ingress ATM policy from the list to associate with the ILMI link.
Click OK. The Select ATM Policy ATM ILMI Link Configuration list form closes.
5. Choose an egress ATM QoS policy by clicking Select. The Select ATM Policy ATM ILMI Link Configuration
list form opens. Click Search and choose an egress ATM policy from the list to associate with the ILMI link.
Click OK. The Select ATM Policy ATM ILMI Link Configuration list form closes.
6. Click Finish and close the forms.
Procedure 1740 To configure an ILMI link
1. Perform step 1 of Procedure 1739 to open the ATM Configuration (Edit) form.
2. Click Edit ILMI Link. The ILMI Link form opens.
3. Configure the required parameters.
The Restore KeepAlive Defaults parameter restores the default values of the KeepAlive Polling Frequency
(seconds), KeepAlive Polling Count, and KeepAlive Test Frequency (seconds) parameters.
The KeepAlive Test Frequency (seconds) parameter is configurable when the Protocol Version parameter is
set to 4.0.
4. Choose an ingress ATM QoS policy by clicking Select. The Select ATM Policy ATM ILMI Link Configuration
list form opens. Click Search and choose an ingress ATM policy from the list to associate with the ILMI link.
Click OK. The Select ATM Policy ATM ILMI Link Configuration list form closes.
5. Choose an egress ATM QoS policy by clicking Select. The Select ATM Policy ATM ILMI Link Configuration
list form opens. Click Search and choose an egress ATM policy from the list to associate with the ILMI link.
Click OK. The Select ATM Policy ATM ILMI Link Configuration list form closes.
6. Click on the Peer Interface Configuration tab to view ILMI properties of the peer interface of the link.
7. Click OK to close the Configure ILMI Link form. The ATM Configuration (Edit) form opens.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 240/269
06.07.2017 Device management
8. To remove an ILMI link, click Remove ILMI Link. Removing the ILMI link also removes the PVC.
Note An ILMI link can be removed only if its Administrative Status parameter is set to
Disabled.
9. Click Cancel to close the forms.
10. 18 — Inventory management
18.1 Inventory management overview
18.2 Sample inventory management workflow
18.3 Workflow to manage inventory
18.4 Inventory management procedures
18.1 Inventory management overview
You can use a 5620 SAM GUI or OSS client to inventory the managed network equipment. The inventory information
is available to GUI clients on equipment list, properties, and management forms. For information about using the
5620 SAMO interface to perform inventory management, see the “Inventory management” chapter of the 5620 SAM
XML OSS Interface Developer Guide.
Inventory information may be required for the following purposes:
spare equipment management
SLA audits
license capacity tracking
For licensed equipment, an inventory list includes the following fields:
Licensed Product
Licenses Consumed
The Licensed Product field indicates the type of license that the equipment consumes; if a piece of equipment
requires no license, the value is None.
Using the 5620 SAM Equipment Manager, you can list the license information for the following object types:
cards, using Card (Physical Equipment) as the search criterion
card child objects:
Blade
IO Card
IO Card Base Card
IO Card Daughter Card
IO Card MCM Card
Processor Card
chassis, using Network Element (Network) as the search criterion
VWM shelves, using VWM Shelf (Physical Equipment) as the search criterion
You can use a GUI client to retrieve the inventory information for equipment objects in the following contexts:
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 241/269
06.07.2017 Device management
one managed NE
entire managed network
Note Not all columns in an inventory list apply to all equipment types. For example, not all card types
have an associated CLEI code. In such a case, an inventory list column displays N/A.
Figure 181 shows how to use the Manage Equipment form to list and filter inventory data for all managed NEs.
Figure 181 Generating inventory data for all managed NEs
Figure 182 shows how to use an object properties form to obtain inventory data.
Figure 182 Generating inventory data for a managed NE
You can save the inventory data in various formats, for example, CSV and HTML.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 242/269
06.07.2017 Device management
Figure 183 shows an inventory list saved in CSV format.
Figure 183 CSV inventory output
Figure 184 shows an inventory list saved in HTML format.
Figure 184 HTML inventory output
18.2 Sample inventory management workflow
The following is a workflow example that describes the highlevel tasks required to generate a spare parts inventory
using the 5620 SAM. Each step corresponds to a labeled action in Figure 185.
1. Determine the part needs based on business requirements and network growth.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 243/269
06.07.2017 Device management
2. Based on the business requirements, use the 5620 SAM to generate one or more filtered inventory lists that
contain only the objects for which spare parts may be required.
3. Save the lists of required spare parts in a format that is compatible with your backoffice systems; for
example, CSV or HTML. Move the lists to another system, for example, an order management or data
management system, for processing.
4. Correlate inventory lists with data from other backoffice systems.
Figure 185 Example of an inventory management workflow
18.3 Workflow to manage inventory
1. Determine the inventory management requirements.
2. Provide inventory list requirements to NOC operators.
3. As required, list and sort inventory data for a managed NE or the entire network; see Procedure 181.
4. As required, save an inventory list to a file; see Procedure 182.
5. As required, save search filters; see Procedure 326.
6. As required, generate an inventory of objects on one managed NE:
CLEI codes; see Procedure 183
card software versions; see Procedure 184
port types; see Procedure 185
shelf data; see Procedure 186
7. As required, generate a networkwide inventory of all managed objects:
cards; see Procedure 187
CCMs; see Procedure 188
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 244/269
06.07.2017 Device management
fan trays; see Procedure 189
flash memory; see Procedure 1810
physical links; see Procedure 1811
ports; see Procedure 1812
power supply trays; see Procedure 1813
processors; see Procedure 1814
shelves; see Procedure 1815
management ports; see Procedure 1816
8. Generate an inventory list for NE SLA audits; see Procedure 1817.
9. Move inventory lists to other systems for further processing, as required.
18.4 Inventory management procedures
Use the following procedures to manage the network inventory using a GUI client.
Procedure 181 To list and sort equipment information
2. Perform one of the following to generate a list of equipment.
a. List the equipment on one NE.
i. Choose Network Element (Network) and click Search. A list of NEs is displayed.
ii. Select an NE and click Properties. The Network Element (Edit) form opens.
iii. Click on the Inventory tab and choose an object. A list of objects is displayed.
b. List the equipment in the entire network.
i. Choose a network object.
ii. Configure the filter criteria and click Search. A list of objects is displayed.
3. Perform one or more of the following to format the results.
a. To display the number of items in the list, rightclick on the list heading and view the Count value.
b. To sort the list, click on a column heading. The column heading displays an arrow that indicates the
sort order.
c. To move a column, drag and drop the column to a different position.
d. To remove a column, perform the following steps.
i. Rightclick on the column heading and choose Column Display. The Column Display form
opens.
ii. Select the columns to remove in the Displayed on Table list, and then click on the left arrow. The
columns move to the Available for Table list.
iii. Click OK. The columns are removed from the table.
e. To sort multiple columns, perform the following steps.
i. Rightclick on a column heading and choose Show Sorting. The Show Sorting form opens.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 245/269
06.07.2017 Device management
ii. Select one or more properties in the Available for Sorting panel, and then click on the right arrow
button. The properties move to the Used for Sorting panel.
iii. Click Sort Ascending or Sort Descending, as required.
iv. Close the Show Sorting form.
4. Save the inventory output, as required. see Procedure 182.
5. Close the form.
Procedure 182 To save an inventory list
You can save an inventory list in CSV or HTML format.
1. Rightclick on a column heading of the inventory output and choose Save to File. The Save As file browser
form opens.
2. Navigate to the directory in which you want save the file.
3. Configure the File Name and Files of Type parameters.
4. Click Save. The 5620 SAM saves the inventory list.
Procedure 183 To inventory the CLEI codes of NE objects
2. Perform one of the following to generate a list of network objects.
a. List the CLEI codes for objects on one NE.
i. Choose Network Element (Network) and click Search. A list of NEs is displayed.
ii. Select an NE and click Properties. The Network Element (Edit) form opens.
iii. Click on the Inventory tab and choose a network object. The form displays a list of network
objects.
b. List the CLEI codes for all network objects of a specific type. Choose a network object.
3. Remove all columns from the list except for object ID, object type, and CLEI code. See Procedure 181 for
information.
4. Save the information to a file. See Procedure 182.
5. Close the forms.
Procedure 184 To inventory the card software versions of one NE
2. Choose Network Element (Network) and click Search. A list of NEs is displayed.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 246/269
06.07.2017 Device management
3. Select an NE in the list and click Properties. The Network Element (Edit) form opens.
4. Click on the Inventory tab and choose Card (Physical Equipment). A list of cards is displayed.
5. Remove all columns from the list except for Slot ID and Software Version. See Procedure 181.
6. Save the inventory output. See Procedure 182.
7. Close the forms.
Procedure 185 To inventory the port types of one NE
2. Choose Network Element (Network) and click Search. A list of NEs is displayed.
3. Select an NE in the list and click Properties. The Network Element (Edit) form opens.
4. Click on the Inventory tab and choose Port (Physical Equipment). A list of cards is displayed.
5. To display more detailed port inventory information, expand the Port (Physical Equipment) object and choose
one of the following objects:
SONET Channels
Link Aggregation Groups
TDM Channels
Multilink Bundles
APS Groups
6. Sort the inventory output. See Procedure 181.
7. Save the inventory output. See Procedure 182.
8. Close the forms.
Procedure 186 To inventory the shelf data for one NE
Note You can generate an inventory of shelf data for the managed network, but not for an individual
NE; see Procedure 1815 for more information.
2. Choose Network Element (Network) and click Search. A list of NEs is displayed.
3. Select an NE in the list and click Properties. The Network Element (Edit) form opens.
4. Click on the Inventory tab and choose Shelf (Physical Equipment). A list of cards is displayed.
5. Select a shelf in the list and click Properties. The Shelf (Edit) form opens.
6. Click on the Display tab. A picture of the selected shelf is displayed.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 247/269
06.07.2017 Device management
7. Use screen capture software to record the screen image, or otherwise copy the shelf information to a file for
further processing.
8. Close the open forms, as required.
Procedure 187 To inventory all cards
2. Choose Card (Physical Equipment).
3. Configure the filter criteria and click Search. A list of cards is displayed.
4. Remove all columns from the list except for the following. See Procedure 181 for information.
Manufacture Date
Part Number
Serial Number
CLEI Code
5. Save the inventory output. See Procedure 182.
6. Close the form.
Procedure 188 To inventory all CCMs
2. Choose CCM (Physical Equipment).
3. Configure the filter criteria and click Search. A list of CCMs is displayed.
4. Remove all columns from the list except for the following. See Procedure 181 for information.
Manufacture Date CLEI Code
Part Number CCM Index
Serial Number CCM Equipped Type
5. Save the inventory output. See Procedure 182.
6. Close the form.
Procedure 189 To inventory all fan trays
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 248/269
06.07.2017 Device management
2. Choose Fan Tray (Physical Equipment).
3. Configure the filter criteria and click Search. A list of fan trays is displayed.
4. Remove all columns from the list except for the following. See Procedure 181 for information.
Operational State
Administrative State
Device State
5. Save the inventory output. See Procedure 182.
6. Close the form.
Procedure 1810 To inventory all flash memory units
2. Choose Flash Memory (Physical Equipment).
3. Configure the filter criteria and click Search. A list of flash memory units is displayed.
4. Remove all columns from the list except for the following. See Procedure 181 for information.
Serial Number
Firmware Revision
Model Number
Capacity (sectors)
Amount Used (sectors)
5. Save the inventory output. See Procedure 182.
6. Close the form.
Procedure 1811 To inventory all physical links
2. Choose Physical Link (Network).
3. Configure the filter criteria and click Search. A list of physical links is displayed.
4. Remove all columns from the list except for the following. See Procedure 181 for information.
Endpoint A Type
Endpoint A Port
Endpoint B Type
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 249/269
06.07.2017 Device management
Endpoint B Port
5. Save the inventory output. See Procedure 182.
6. Close the form.
Procedure 1812 To inventory all ports
2. Choose Port (Physical Equipment).
3. Configure the filter criteria and click Search. A list of ports is displayed.
4. Remove all columns from the list except for the following. See Procedure 181 for information.
Name
CLI Name
MTU (bytes)
State
5. Save the inventory output. See Procedure 182.
6. Close the form.
Procedure 1813 To inventory all power supply trays
2. Choose Power Supply Tray (Physical Equipment).
3. Configure the filter criteria and click Search. A list of power supply trays is displayed.
4. Remove all columns from the list except for the following. See Procedure 181 for information.
Administrative State
Operational State
AC Voltage Status
DC Voltage Status
Assigned Type
5. Save the inventory output. See Procedure 182.
6. Close the form.
Procedure 1814 To inventory all processors
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 250/269
06.07.2017 Device management
2. Choose Processor (Physical Equipment).
3. Configure the filter criteria and click Search. A list of processors is displayed.
4. Remove all columns from the list except for the following. See Procedure 181 for information.
Operational State Manufacture Date
Administrative State Part Number
CLEI Code Serial Number
Manufacturer
5. Save the inventory output. See Procedure 182.
6. Close the form.
Procedure 1815 To inventory all shelves
2. Choose Shelf (Physical Equipment).
3. Configure the filter criteria and click Search. A list of shelves is displayed.
4. Remove all columns from the list except for the following. See Procedure 181 for information.
Operational State Manufacture Date
Administrative State CLLI Code
CLEI Code Part Number
Manufacturer Serial Number (Manufacturer Details)
5. Save the inventory output. See Procedure 182.
6. Close the form.
Procedure 1816 To inventory all management ports
Perform this procedure to list all NE management ports.
1. Choose Manage Equipment Equipment from the 5620 SAM main menu. The Manage Equipment form
opens.
2. Choose Network Element (Network).
3. Configure the filter criteria and click Search. A list of ports is displayed.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 251/269
06.07.2017 Device management
4. Remove all columns from the list except for the following. See Procedure 181 for information.
System ID Software Version
Management IP Address Descriptor Version (software release)
Location Resource Group ID
Chassis Type
Sys Object ID
5. Save the inventory output. See Procedure 182.
6. Close the form.
Procedure 1817 To collect inventory data for NE SLA audits
Note 1 SLA inventory collection requirements differ. Ensure that you collect the required data for your
SLA.
Note 2 Inventory data collection can be resourceintensive; perform inventory collection during a
maintenance period or a period of low network activity.
1. Choose Manage Equipment Equipment from the 5620 SAM main menu. The Manage Equipment form
opens.
2. Collect the required SLA audit data.
a. For card SLA audits, choose Card (equipment).
b. For shelf SLA audits, choose Shelf (equipment).
c. For power supply tray SLA audits, choose Power Supply Tray (equipment).
3. Click Search. The SLA audit information is listed.
4. Typically, only a subset of data is required for SLA audits. Remove all columns from the list except for the
required columns. See Procedure 181 for information.
Required information typically includes the following:
Identification information, such as Site ID, Site Name, Slot ID, and Slot Name
SLA audit and ordering information, such as Manufacture Date, Part Number, Serial Number, CLEI
Code, and Card Type
5. Save the inventory output. See Procedure 182.
6. Close the form.
11. 19 — Card migration
19.1 Card migration management overview
19.2 Workflow to manage card migration
19.3 Card migration management procedures
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 252/269
06.07.2017 Device management
19.1 Card migration management overview
You can use a 5620 SAM GUI utility called the Card Migration Event Manager to facilitate the transition to an IOM 3
on one or more 7450 ESS or 7750 SR NEs. The Card Migration Event Manager transfers the existing IOM and MDA
configurations to new modules with minimal service interruption.
The 5620 SAM Card Migration Event Manager can do the following:
Upgrade from an IOM 1 or IOM 2 to an IOM3 while retaining the same MDAs.
Upgrade from one MDA type to a newer MDA type that has compatible features.
Upgrade an IOM and the associated MDAs in one operation.
You can perform an immediate migration, or preconfigure one or more migration events for later execution. A
migration event can include an NE reboot to put the new hardware configuration into effect immediately after the
migration. You can upgrade multiple IOMs and MDAs in one operation to limit the number of required NE reboots to
one.
During a migration event, the 5620 SAM identifies the configured objects that are bound to the IOM or MDA, deletes
the objects, and then creates the objects on the new IOM or MDA. The old and new configurations are saved in the
5620 SAM database until the migration completes successfully. The 5620 SAM preserves the statistics data and
alarm information that is associated with each object.
Restrictions
The following restrictions apply to 5620 SAM card migration event management:
General
Only the 5620 SAM admin user, or a user with an assigned administrator scope of command role, can
create, modify, or execute a migration event.
The migration functions are not available to 5620 SAM OSS clients.
You may need to reenable SNMP on an NE after the NE reboots following a migration event.
The description of a SAP associated with the card cannot contain a numerical value.
IOMspecific
An IOM downgrade, for example, a migration from an IOM 3 to an IOM 2, is not supported.
MDAspecific:
You cannot migrate an empty MDA slot to an MDA.
MDA migration is limited to MDAs of the same physical transmission type; for example, migration from
a SONET MDA to an Ethernet MDA is not supported.
You cannot upgrade an MDA that is integrated with an IOM, for example, an IMM.
For MDAs, you can migrate only to an MDA of similar capacity that has the same or a greater number
of ports.
The 5620 SAM raises an alarm during a migration event if a target NE is unreachable. After a migration event, the
5620 SAM raises an alarm to indicate migration success or failure.
Table 191 lists the supported MDA migration types.
Table 191 Supported MDA migration types
Current MDA MDAs supported by migration
10 x 1Gig Ethernet SFP 10 x 1Gig Extended Performance SFP
20 x 10/100/1000 Ethernet Extended Performance SFP
20 x 10/100/1000 Ethernet Extended Performance TX
5 x 1Gig Ethernet SFP 10 x 1Gig Extended Performance SFP
20 x 10/100/1000 Ethernet Extended Performance SFP
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 253/269
06.07.2017 Device management
20 x 10/100/1000 Ethernet Extended Performance TX
1 x 10Gig Ethernet 4 x 10Gig Extended Performance XFP
2 x 10Gig Extended Performance XFP
1 x 10Gig Extended Performance SFP
20 x 100 Ethernet Fx 20 x 10/100/1000 Ethernet Extended Performance SFP
20 x 10/100/1000 Ethernet Extended Performance TX
20 x 10/100/1000 Ethernet Tx 20 x 10/100/1000 Ethernet Extended Performance SFP
20 x 10/100/1000 Ethernet Extended Performance TX
2 x 10Gig Ethernet XFP 2 x 10Gig Extended Performance XFP
4 x 10Gig Extended Performance XFP
20 x 10/100/1000 Ethernet SFP 20 x 10/100/1000 Ethernet Extended Performance SFP
20 x 10/100/1000 Ethernet Extended Performance TX
1 x 10gig Ethernet XFP 4 x 10GigExtended Performance XFP
2 x 10Gig Extended Performance XFP
1 x 10Gig Extended Performance XFP
5 x 10/100/1000 10 x 1Gig Extended Performance SFP
20 x 10/100/1000 Ethernet Extended Performance SFP
20 x 10/100/1000 Ethernet Extended Performance TX
10 x 10/100/1000 Ethernet SFP 10 x 1Gig Extended Performance SFP
20 x 10/100/1000 Ethernet Extended Performance SFP
20 x 10/100/1000 Ethernet Extended Performance TX
60 x 10/100 Ethernet 48 x 10/100/1000 Ethernet Extended Performance TX
19.2 Workflow to manage card migration
The following is the sequence of highlevel actions required to manage card migration.
1. Use the 5620 SAM to back up the device configuration of each target NE.
Note When you attempt a migration on an NE that does not have a recent configuration
backup in the 5620 SAM database, the 5620 SAM raises an alarm and the migration fails.
A recent configuration backup is a backup that occurs after the latest configuration save on the
NE.
See chapter 24 for information about performing NE backups.
2. Create a card migration event and execute or save it, as required. See Procedure 191 for more information.
3. Execute a saved card migration event, as required. See Procedure 192 for more information.
19.3 Card migration management procedures
Use the following procedures to perform card migration event management tasks.
Procedure 191 To create a card migration event
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 254/269
06.07.2017 Device management
2. Click Create. The Card Migration Event (Create) form opens with the General tab displayed.
3. Configure the general parameters.
4. Click on the NE Migration Candidates tab and click Add. The Select Network Elements Card Migration
Event form opens.
5. Select one or more NEs and click OK. The Select Network Elements Card Migration Event form closes and
the NEs are listed on the Card Migration Event (Create) form.
6. Select one or more NEs and click Properties. The Network Element Migration Candidates form opens.
7. Configure the Auto Reboot parameter and click OK.
8. Click on the Card Migration Candidates tab and click Add. The Select Cards Card Migration Event form
opens.
9. Select one or more cards and click OK. The Select Cards Card Migration Event form closes and the cards
are listed on the Card Migration Event (Create) form.
10. Select one or more cards and click Properties. The Migration Details (Create) form opens.
11. Configure the New Type parameter in the IOM, MDA 1, or MDA 2 panels, as required, and click OK.
12. To execute the migration event immediately, perform the following steps. Otherwise, you can execute the
migration later by performing Procedure 192.
i. Use the 5620 SAM to back up the device configuration of each target NE.
Note When you attempt a migration on an NE that does not have a recent configuration
backup in the 5620 SAM database, the 5620 SAM raises an alarm and the migration
fails.
A recent configuration backup is a backup that occurs after the latest configuration save
on the NE.
ii. Click Apply. The 5620 SAM saves the card migration event configuration.
iii. Click on the General tab to display the Status indicator.
iv. Click Initiate Migration and click Yes. The 5620 SAM starts to migrate the specified cards.
v. Monitor the card migration as it progresses by viewing the Status indicator on the form. The status can
be one of the following:
Awaiting manual reboot to complete migration
Failed Latest configuration not available
Failed Unable to migrate configuration
Failed Unable to reboot network element
Failed Unable to transfer migrated configuration
Migration completed
Not Started
Rebooted network element
Started
Swap failed
Swap failed on some network elements
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 255/269
06.07.2017 Device management
13. Save your changes and close the form.
Procedure 192 To execute a saved card migration event
1. Use the 5620 SAM to back up the device configuration of each target NE.
Note When you attempt a migration on an NE that does not have a recent configuration
backup in the 5620 SAM database, the 5620 SAM raises an alarm and the migration fails.
A recent configuration backup is a backup that occurs after the latest configuration save on the
NE.
3. Select a card migration event and click Properties. The Card Migration Event (Edit) form opens with the
General tab displayed.
4. Click Initiate Migration and click Yes. The 5620 SAM starts to migrate the specified cards.
5. Monitor the card migration as it progresses by viewing the Status indicator on the form. The status can be one
of the following:
Awaiting manual reboot to complete migration
Failed Latest configuration not available
Failed Unable to migrate configuration
Failed Unable to reboot network element
Failed Unable to transfer migrated configuration
Migration completed
Not Started
Rebooted network element
Started
Swap failed
Swap failed on some network elements
6. Save your changes and close the form.
12. 20 — TCA
20.1 TCA overview
20.2 Workflow to configure TCA
20.3 TCA management procedures
20.1 TCA overview
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 256/269
06.07.2017 Device management
You can create policies to raise 5620 SAM alarms based on managedobject statistics. When a statistic counter of
an object such as an interface reaches a specified threshold, the 5620 SAM alerts GUI operators using a threshold
crossing alarm, or TCA, based on policy specifications.
A TCA policy includes the following:
a list of objects to monitor
a traffic flow direction to monitor
rules that define the rising and falling thresholds, and the alarm severity
optional custom rules to monitor statistics based on userdefined formulas
Note A TCA is not selfclearing. The 5620 SAM clears a TCA only when the TCA policy contains a
fallingthreshold rule in addition to a risingthreshold rule, and the alarm severity in the fallingthreshold
rule is set to cleared.
TCA operation
To enable TCA on an object, you must enable performance statistics collection on the object. See “Performance
statistics collection” in the 5620 SAM Statistics Management Guide for information about enabling performance
statistics collection.
The 5620 SAM compares the object counter values at each statistics collection to the threshold values in the
associated TCA policy. When a value initially crosses a threshold, the 5620 SAM raises an alarm. Rather than raise
new alarms for successive thresholdcrossing events associated with the policy, the 5620 SAM adjusts the alarm
severity based on the policy rules.
In the 5620 SAM client GUI, you can associate a TCA policy with a managed object from the TCA policy
configuration form, or from the object properties form. You can associate one TCA policy with multiple objects.
TCA policy rules
Depending on the object type, you can use rules to monitor the following:
object utilization
errored packets
dropped packets
custom values; see
A rule can apply to an absolute counter value or to a delta value, which is the difference between the current value
and the previous value.
Custom profile TCAs
You can optionally create custom profile TCAs that contain rules that you specify using one or more counter values,
numerical constants, and mathematical operators. A custom profile TCA is associated with a TCA policy.
TCA configuration example
The following example describes the 5620 SAM configuration required to raise a TCA, adjust the alarm severity, and
clear the alarm, based on the following utilization specifications:
Raise a minor alarm if utilization is between 60% and 69%.
Change the alarm severity to major if utilization rises to between 70% and 79%.
Change the alarm severity to critical if utilization rises to 80% or higher.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 257/269
06.07.2017 Device management
Change the alarm severity to major if utilization falls below 80%.
Change the alarm severity to minor if utilization falls below 70%.
Clear the alarm if utilization falls below 60%.
The following are the TCA rules and associated parameter values required to implement the example alarm behavior:
Rule to raise minor alarm for 60% or higher utilization:
Alarm Severity—minor
Threshold (%)—60
Threshold Direction—Rising Above
Rule to change alarm severity to major for 70% or higher utilization:
Alarm Severity—major
Threshold (%)—70
Threshold Direction—Rising Above
Rule to change alarm severity to critical for 80% or higher utilization:
Alarm Severity—critical
Threshold (%)—80
Threshold Direction—Rising Above
Rule to change alarm severity to major if utilization falls below 80%:
Alarm Severity—major
Threshold (%)—80
Threshold Direction—Falling Below
Rule to change alarm severity to minor if utilization falls below 70%:
Alarm Severity—minor
Threshold (%)—70
Threshold Direction—Falling Below
Rule to clear alarm if utilization falls below 60%:
Alarm Severity—cleared
Threshold (%)—60
Threshold Direction—Falling Below
20.2 Workflow to configure TCA
The following is the sequence of highlevel actions required to configure TCA and enable the TCA function on a
monitored object.
1. Enable performance statistics collection on the object to monitor. Table 201 lists the port statistics policy
objects required to enable TCA on a network interface or physical link.
Table 201 Port statistics policy objects for TCA
Statistics policy type MIB MIB entry Monitored class
NE MIB IFMIB ifEntry —
Specific MIB equipment.PhysicalPort
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 258/269
06.07.2017 Device management
2. If you require custom TCA rules, configure a custom profile TCA; see Procedure 201.
3. Configure a TCA policy; see Procedure 202.
i. Configure utilization, error, and drop TCA rules.
ii. Optionally, associate a custom profile TCA with the policy.
4. Apply the TCA policy to an object; see Procedure 203.
5. If required, customize the TCA system preferences, such as specifying the default TCA severity or the
maximum TCA limit; see “System preferences configuration procedures” in the 5620 SAM System
Administrator Guide.
20.3 TCA management procedures
The following procedures describe how to configure and manage 5620 SAM TCA.
Procedure 201 To configure a custom profile TCA
2. Choose Custom Profile TCA (TCA Policy) and click Create. The Custom Profile TCA (Create) form opens.
3. Configure the general parameters.
4. Select a monitored object type.
5. Configure the Stats Type parameter.
6. Click Build Formula. The Build Formula form opens.
7. Choose a statistic counter from the Counter Field dropdown menu and click Add.
8. Add as many expressions to the formula as required.
a. Add a statistic counter to the formula.
i. Click on one of the mathematical operator buttons.
ii. Choose a counter from the Counter Field dropdown menu and click Add.
b. Add a constant value to the formula.
i. Click on one of the mathematical operator buttons.
ii. Enter a number in the Constant Value field and click Add.
9. Click OK to save your changes and close the Build Formula form.
10. Click OK to save your changes and close the Custom Profile TCA (Create) form.
11. Close the TCA Policies form.
Procedure 202 To configure a TCA policy
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 259/269
06.07.2017 Device management
2. Choose TCA Policy (TCA Policy) and click Create. The TCA Policy (Create) form opens.
3. Configure the general parameters.
4. Select a monitored object and click Apply.
Note The panels displayed on the General tab vary, depending on the type of monitored object.
5. To configure utilization TCA rules:
i. Configure the parameters in the Utilization panel.
ii. Click Create in the Rules panel. The PercentageTCARule, tca.UtilizationTCA0 (Create) form opens.
iii. Configure the parameters and click OK.
Note You cannot create two rules that have the same Threshold (%) and Threshold
Direction values.
6. To configure error TCA rules:
i. Configure the parameters in the Error panel.
ii. Click Create in the Rules panel. The PercentageTCARule, tca.ErrorTCA0 (Create) form opens.
iii. Configure the parameters and click OK.
Note You cannot create two rules that have the same Threshold (%) and Threshold
Direction values.
7. To configure drop TCA rules:
i. Configure the parameters in the Drop panel.
ii. Click Create in the Rules subpanel. The PercentageTCARule, tca.DropTCA0 (Create) form opens.
iii. Configure the parameters and click OK.
Note You cannot create two rules that have the same Threshold (%) and Threshold
Direction values.
8. To configure custom TCA rules:
i. In the Custom panel, click Create. The CustomTCA (Create) form opens.
ii. Configure the parameters.
iii. Select a Custom TCA Profile.
iv. Click Create in the Rules panel. The CustomTCARule, tca.CustomTCA0 (Create) form opens.
v. Configure the parameters and click OK.
9. Apply the TCA Policy to one or more monitored objects:
i. Click on the Monitored Objects tab.
ii. Click Add. The Select form opens.
iii. Select the required objects and click OK.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 260/269
06.07.2017 Device management
10. Click OK to save your changes and close the TCA Policy (Edit) form.
11. Close the TCA Policies form.
Procedure 203 To apply a TCA policy to objects using the object properties
forms
2. Select an object type and click Search. A list of equipment objects is displayed.
3. Select an object and click Properties. The object properties form opens.
4. If the object is a Physical Link, assign a TCA policy to End Point A and End Point B. Go to step 7.
5. Click on the TCA tab and click Assign. The Select TCAPolicy form opens.
6. Select a TCA policy and click OK
7. Click OK to save your changes and close the object properties form.
8. Close the Manage Equipment form.
13. 21 — Bulk operations
21.1 Bulk operations overview
21.2 Workflow to manage bulk operations
21.3 Bulk operations procedures
21.1 Bulk operations overview
The 5620 SAM bulk operations function allows you to create bulk changes to modify a large amount of information.
Bulk changes may be deployed to NEs or restricted to the 5620 SAM.
A bulk change can contain thousands of target objects. These objects, referred to as batch items, are grouped into
batches for efficient bulk change execution. An operator can execute an entire bulk change or individual batches.
You should regenerate batches each time you execute a bulk change to ensure that each target object that matches
the bulk change filter is modified.
If one or more of the batch items fail to change during a bulk change operation, the Batch Status and the Batch
Status Summary parameters help identify the items. You can also use the Task Manager to view information about a
batch.
The 5620 SAM displays a confirmation message before executing bulk change operations. You can configure user
preferences to disable confirmation messages for bulk change operations; see Procedure 316.
21.2 Workflow to manage bulk operations
1. Create a bulk change. See Procedure 211.
2. Generate batches for a bulk change. See Procedure 213.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 261/269
06.07.2017 Device management
3. Execute one or more batches in a bulk change. See Procedure 213.
4. As required, stop a bulk change. See Procedure 215.
5. View the bulk change execution results to verify that the bulk change was successful and to identify any
items that failed to change. See Procedure 214.
21.3 Bulk operations procedures
Use the following procedures to manage 5620 SAM bulk operations.
Procedure 211 To create a bulk change
2. Open the Create Bulk Change form by performing one of the following steps.
a. Click Create.
b. To create a bulk change by copying values from an existing bulk change:
i. Choose an existing bulk change and click Properties. The Bulk Change (Edit) form opens.
ii. Click Copy.
3. Configure the general parameters and click Next. The Specify the filter form opens.
4. To specify a filter, perform one of the following.
a. Create a filter.
i. Click on the Attribute dropdown menu and select an option.
ii. Click on the Function dropdown menu and select an option.
iii. Click on the Value dropdown menu and select or enter an option.
iv. Click Add. The options are displayed in the filter panel.
v. Select AND or OR from the Operators dropdown menu. Repeat steps i to iv to add more
options.
vi. Click Save. The Save Filter form opens.
vii. Configure the general parameters.
viii. Click Save. The Save Filter form closes.
b. Load a filter.
i. Click Saved Filters. The Saved Filters form opens.
ii. Select a saved filter and click Load. The Saved Filters form closes and the loaded filter is
displayed in the filter panel.
5. Configure the filter criteria. Creating a filter that contains the attributes that you want to change can limit the
number of objects generated for the bulk change.
6. Click Count to determine the number of network objects that are affected, based on the filter.
7. Click View to list the target objects. The Filtered List form opens.
8. Click Search. A list of target objects is displayed.
9. Click Next. The Specify the attributes form opens.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 262/269
06.07.2017 Device management
10. Doubleclick on the attribute or attribute group in the attribute tree panel that you want to include in the bulk
change. The attribute or attribute group appears in the display panel.
If you included an attribute or attribute group that you want to exclude from the bulk change, you can remove it
by clicking the Remove X icon in the display panel.
11. Perform one of the following for each listed attribute, as required.
a. Enter a value in the attribute field. The dropdown menu changes from Unchanged to Set, which means
that the attribute changes to the new value when you execute the bulk change.
b. Choose Default from the dropdown menu to specify that the attribute is to change to the default value
when you execute the bulk change.
c. Choose Clear from the dropdown menu. Depending on the object type, the attribute value is cleared or
set to the default value when you execute the bulk change.
12. Click Next. The Change review form opens.
13. Configure the required parameters and click Finish.
14. Select the View the newly created Bulk Change check box to view the bulk change after closing the form, if
required.
15. Click Close.
16. To create more Bulk Changes, repeat steps 2 to 15.
Procedure 212 To modify a bulk change
2. Choose a bulk change and click Properties. The Bulk Change (Edit) form opens with the General tab
displayed.
3. Modify the required parameters.
4. Click on the Spans tab and specify a span, if required.
5. Save your changes and close the form.
Procedure 213 To execute a bulk change
Note 1 You can only execute one bulk change at a time. All other bulk changes are queued.
Note 2 You can only generate batches for one bulk change at a time.
Note 3 You cannot generate batches when a bulk change is executing.
1. Choose Tools Bulk Operations from the 5620 SAM main menu. The Bulk Operations form opens.
2. Choose a bulk change from the list and perform one of the following.
a. If the bulk change contains batches, click Execute to execute all of the batches.
Note Changes made to the network after the batches are generated are not affected by
the bulk change batches.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 263/269
06.07.2017 Device management
b. If the bulk change does not contain batches, or you want to regenerate the batches, perform the
following.
i. Click Properties. The Bulk Change (Edit) form opens with the General tab displayed.
ii. Click on the Batch Control tab.
If the Generate Batches button is dimmed, set the Admin State parameter on the General tab to
Enable.
iii. Click Generate Batches. The batches are generated and listed on the form.
iv. To execute only specific batches, choose one or more batches and click Execute Selected.
v. To execute all of the batches, click Execute All.
3. Click Yes. The 5620 SAM executes the bulk change.
4. Close the forms.
Procedure 214 To view executed batch information
Note You can also use the 5620 SAM Task Manager to view information about a batch.
2. Choose a bulk change and click Properties. The Bulk Change (Edit) form opens with the General tab
displayed.
3. Click on the Batch Control tab.
4. Choose a batch and click Properties. The Bulk Change Batch form opens with the General tab displayed.
View general information about the executed batch.
5. Click on the Batch Items tab and click Search. A list of items that were changed in the batch appears with the
status of each batch item.
6. To view the parameters for each batch item, choose a batch item and click Properties.
7. Close the forms.
Procedure 215 To stop one or more bulk changes
2. Perform one of the following:
a. Choose one or more bulk change to stop.
b. Choose one or more batches to stop by performing the following:
i. Choose a bulk change from the list and click Properties. The Bulk Change (Edit) form opens
with the Batch Control tab displayed.
ii. Choose one or more batches.
3. Click Stop and click Yes. The bulk change execution stops.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 264/269
06.07.2017 Device management
4. Close the forms.
14. 22 — Autoprovision
22.1 Autoprovision overview
22.2 Workflow to configure network devices using autoprovision
22.3 Autoprovision procedures
22.1 Autoprovision overview
Autoprovision provides a way to reuse a proven configuration and apply the configuration to multiple NEs of the
same type. This functionality is useful when a large number of similar NEs must be configured. Autoprovision
reduces configuration errors and the time to configure each NE. Autoprovision takes advantage of the validations
that are executed for every 5620 SAM configuration. When you configure a source NE from a 5620 SAM, the need to
troubleshoot configuration problems is reduced.
After a source NE is configured and backed up, an operator can import the source script to the source profile.
Alternatively, an operator can add the source script manually to the source profile. From the source profile, a target
template can be generated. An operator can import the target template, enter any required changes and deploy the
configuration template on a target NE.
Note To ensure that the CLI syntax remains intact, the target NE must be of the same device and
chassis type, and at the same release, as the source NE.
Autoprovision extends configuration to an adjacent 7750 SR to ensure a prompt and reliable exchange of traffic
between the devices. When the configuration profile is successfully deployed to a 7705 SAR target device, the
operator can generate configuration modules to configure interactions between the target device and the adjacent
devices. An operator can make minor changes to some of the attributes on the configuration modules and deploy the
configuration modules to create objects on the selected 7750 SR. When modules are configured, the operator can
deploy the modules to configure the connection. A VLL service site is created on the 7705 SAR and the adjacent
7750 SR. The 5620 SAM automatically creates SAPs and SDP bindings.
The 5620 SAM supports the generation of SAP and SDP configuration modules. Configuration between the 7705
SAR and the adjacent 7750 SR requires the following:
Base configuration of the 7750 SR is complete and the 7705 SAR is autoprovisioned.
Interfacelevel configuration is sent to the adjacent 7750 SR.
The uplink port of the autoprovisioned 7705 SAR is configured to communicate with the network interface of
the 7750 SR. Only Ethernet network interfaces are supported.
The 7750 SR must be able to communicate with the adjacent 7705 SAR.
A LDP interface is created on the same interface.
A MPLS interface is created when MPLS is enabled. Choose either RSVP hop by hop or TE.
MLPPP is configured on the 7750 SR when MLPPP is configured on the adjacent 7705 SAR.
A LSP is configured between the 7750 SR and the 7705 SAR.
An Ethernet, TDM or ATM endpoint is created on the 7750 SR that corresponds to the SAP on the 7705 SAR.
The velocity script generator parses a validated source NE configuration so that the NE is compatible with the
velocity script management tool that is available in the 5620 SAM. After the layers are identified, the velocity script
generator identifies attributes that require configuration before they can be applied to a target NE. Table 221 lists the
layers that are identified by the velocity script generator. An operator can add, remove, modify, or hide any of the
attributes that are listed. The layers must be configured to deploy together.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 265/269
06.07.2017 Device management
Table 221 Layers and attributes identified by the velocity script generator
Layer Attributes
Base Equipment layer SNMP packet size and daughter cards
Channelization layer SONET SDH paths and channel groups
Policies layer QoS and ACL related policies
Routing layer Routing interface configurations and static routes
Routing Protocols Routing Protocol configurations
layer
MPLS layer Targeted LDP, MPLS interfaces, and LSPs
Service layer VLL services including Apipe, Cpipe, Epipe, Ipipe, VPRN, SAP, and SDP
bindings
Warning Scripts that are modified and saved must be applied to devices with the same vendor and
release.
Access to the script management is controlled by the administration, script management and script execution scope
of command roles. Access to autoprovision is controlled by the auto config permissions that are defined in the scope
of command roles. Users that are assigned the administration or script management role can create, modify, delete,
and execute scripts. Users that are assigned the script execution role can view and run scripts, view and save
results, configure script targets and sources, and view historical results.
In addition to the scope of command access roles and profiles, access to the Scripts tool is further defined by span
of control. Span of control profiles determine where a user can apply scope of command access roles and profiles.
For example, a user may have privileges to execute scripts. However, a span of control profile defines the scripts
that the user can execute.
Autoprovision requires a Mobile Services Package license key to operate. See chapter 3 for more information about
obtaining and installing software license keys.
22.2 Workflow to configure network devices using auto
provision
1. Configure the source template. See Procedure 221 for more information.
i. Determine the NE configuration that you need to use for the source.
ii. Import a source configuration file from the router, or create a source file by performing a backup of the
source configuration and naming the backup file a unique name.
iii. Generate a template from the source script.
2. Configure the target template. See Procedure 222 for more information.
i. Import the template file to the autoprovision profiles tool.
ii. As required, configure the source script.
iii. Use the GUI builder to customize attributes in the source template. See the 5620 SAM Scripts and
Templates Developer Guide for more information.
3. Apply a target template to an unprovisioned NE. See Procedure 223.
Note Typically, step 1 is performed on one 5620 SAM, and steps 2 and 3 are performed on another
5620 SAM. Step 1 is typically performed in a lab or testing environment.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 266/269
06.07.2017 Device management
22.3 Autoprovision procedures
Use the following procedures to perform autoprovision operations.
Procedure 221 To configure a source template
2. Choose AutoConfig Source Node Profile (Automatic Configuration) from the dropdown menu.
3. Click Create. The AutoConfig Source Node Profile (Create) form opens.
4. Configure the parameters.
5. Click Select and choose an NE to specify the Source Node Name.
6. Click Apply. The Backup State parameter displays the status of the last backup operation on the NE, and the
Script tab is enabled.
7. Perform one of the following to create a backup of the source NE configuration and import the configuration:
a. Back up and import from the NE.
i. Click Backup. The Backup State parameter displays the status of the backup.
ii. When the status is Success, click Attach Source Node Config. The backedup configuration is
attached to the source profile and can be viewed from the Script tab.
b. Back up and export the device configuration to a file.
i. See Procedure 247 for information about saving a 7705 SAR configuration to a backup file.
ii. Click on the Script tab and click Create. The Script Editor window opens.
iv. Use the form to specify the backup file location and click Import. The script is displayed in the
Script Editor workspace.
Warning Scripts that are not correctly applied or created can cause serious
damage to the network. AlcatelLucent recommends that system administrators
clearly define the user responsibilities for script usage, and ensure that scripts are
verified before they are executed on devices in a live network.
Note To run a script, you require read, write, and execute permissions on the
following directory, where install_dir is the client installation location, typically
/opt/5620sam/client on RHEL, and C:\5620sam\client on Windows:
install_dir/client/nms/bin, on a RHEL station
install_dir\client\nms\bin\clientCache, on a Windows station
8. Click Generate Template.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 267/269
06.07.2017 Device management
Template generation can take several minutes to complete, depending on the size of the source configuration
file and server resources. When the process is complete, the Template tab lists the new template.
9. Click on the Template tab, select the template and click Properties. The script is displayed in the Script Editor
workspace.
See “Velocity GUI builder” in the 5620 SAM Scripts and Templates Developer Guide for information about
using the GUI builder tool to generate and customize a UI.
12. Use the form to specify the location and name of the exported text file and click Export. The file is exported
and the Script Editor window reappears.
13. Close the Script Editor window and click OK to save the script changes.
14. Close the AutoConfig Source Node Profile (Edit) form.
Procedure 222 To configure a target template
Note Before you can apply a source configuration to a target NE, you must configure and
export the source configuration template. See Procedure 221 for more information about
configuring and exporting a source template.
2. Choose AutoConfig Target Node Profile (Automatic Configuration) from the dropdown menu and click Create.
The AutoConfig Target Node Profile (Create) form opens.
3. Configure the parameters.
4. Click Apply. The Template and Targeted Nodes tabs are enabled.
5. Click on the Template tab and click Add. A Script Editor window opens.
7. Use the form to specify the exported file created using Procedure 221.
8. Click Import. The script is displayed in the Script Editor workspace.
See “Velocity GUI builder” in the 5620 SAM Scripts and Templates Developer Guide for more information
about using the GUI builder tool to generate and customize a UI.
11. Close the AutoProvision Target Node Profile (Edit) form.
Procedure 223 To apply a target template to an unprovisioned NE
1. Choose the Equipment view in the network navigation tree.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 268/269
06.07.2017 Device management
Note You can also access the function from an NE properties form.
2. Rightclick on an NE and choose AutoProvision. The AutoProvision Managed Node Wizard form opens.
Note The AutoProvision option is dimmed for a previously configured NE.
3. Click Select beside the Script ID parameter to choose a template configured using Procedure 222.
4. Perform one of the following:
a. Select the Adjacent NE Managed parameter if the 5620 SAM manages the adjacent NE, and then go to
step 7.
b. Deselect the Adjacent NE Managed parameter if the 5620 SAM does not manage the adjacent NE.
5. Click Next. The Adjacent Node step is displayed.
6. Configure the Adjacent Site ID parameter, and then go to step 9.
7. Click Next. The Adjacent 7750 Node step is displayed.
8. Click Select to specify an adjacent NE. The form displays the NE name beside the Name parameter.
9. Click Finish. A dialog box appears.
10. Click OK. A dialog box appears.
11. If required, select the View the newly created AutoProvisioning parameter to display the autoprovision
configuration after you close the form.
12. Click Close. The AutoProvisionSite (Edit) form opens, and displays the provisioning for the adjacent NE.
13. Click Deploy Profile. The Target Configuration form opens. The form displays the target NE and configurable
parameters.
14. Configure the parameters.
15. Select the NE to which you need to deploy the configuration profile and click Execute. The autoprovisioning
execution status is displayed in the Detailed Status/Error panel. When the NE configuration using the
configuration profile is complete, the status of the NE changes to Configured.
16. Click on the Modules tab.
Note You must deploy the 7750 SR configuration modules after the 7705 SAR auto
provisioning is successfully deployed and resynchronized.
17. Click Generate Modules to display the interaction between the source and adjacent NEs.
18. Click Properties of a generated module to configure the created modules. The default values for some
modules are valid. However, for other modules, for example SAP modules, you must select a 7750 SR port
before you continue.
19. Click Deploy Modules to configure the connection.
20. To view the modified services, click on the Service Associations tab.
21. Close the Target Configuration form.
https://infocenter.alcatellucent.com/public/5620SAM130R5A/advanced/print.jsp?topic=/SAM_UG/html/sam_volume_device.html&cp=17_1_1 269/269