Chapter 3 Building the Network
3.5.1 Prerequisites for Adding NEs
Note To add an ONS 15302 or ONS 15305 NE to CTM, its SNMP Users table must contain the following row:
0.0.0.0public true where, public is the community string. In addition, to obtain the trap events from the NE, the CTM Server IP address must be added to the NE. Refer to the Cisco Edge Craft User Documentation for more information.
3.5.1.3Prerequisites for Adding ONS 15310, ONS 15454 SONET, and ONS 15454 SDH NEs
Before adding ONS 15310, ONS 15454 SONET, or ONS 15454 SDH NEs with
•A valid SNMP community string must be given when adding an NE with
•A trap destination with IP address=CTM Server IP address, UDP Port=162, SNMP version=SNMPv2, maximum Traps/second=0, and SNMP community string must be created and must allow SNMP sets to receive traps from
•The Cisco IOS
•Whenever the user changes the trap destination for NE IP address and port=162 in either CTC or CTM, NEs must be out of service to resync the
•If your network contains ML cards, note the following SNMP configuration requirements in a GNE/ENE scenario:
1.SNMPv1 uses the following configurations on GNEs and ENEs for traps: GNE trap destination: CTM server IP address
GNE trap port: 162
GNE community string: public
GNE version: v1
ENEs have two possible configurations: a. First configuration:
–ENE trap destination: GNE IP address
–ENE trap port: 391
–ENE community string: Same as on GNE
–ENE version: v1
b.Second configuration:
–ENE trap destination: CTM server IP address
–Relay A IP address: IP address of the NE that is directly connected to the ENE
–Relay A community string: Same as on all other NEs
–Relay B IP address: IP address of the NE that is directly connected to the Relay A NE
–Relay B community string: Same as on all other NEs
–Relay C IP address: IP address of the NE that is directly connected to the Relay B NE
–Relay C community string: Same as on all other NEs
Cisco Transport Manager Release 6.0 User Guide
|
| ||
|
|