Cisco Cisco Transport Manager 9.1 Technical References

When setting up an SNMPv1 or SNMPv2 trap destination:

Delete the GNE and ENE’s SNMP trap destinations before performing GNE-ENE role changes. 
After a GNE-ENE role switch is complete, add the new SNMP trap destinations according to the 
new GNE-ENE roles.

If the ENE does not contain the GNE’s SNMP community string, mark the ENE as Out of Service 
and then In Service.

Do not use an ONS 15600 as the GNE and an ONS 15454 as the ENE.

The GNE-ENE SNMP community string must be Public.

CTM supports SNMPv3 on CTC-based release 9.1 NEs. (SNMPv3 is not supported on ONS 15305, 
ONS 15305 CTC, or ONS 15327 NEs.)

As is the case for SNMPv1 and SNMPv2, to support SNMPv3, NEs with ML-series cards must have a 
valid SNMP configuration to guarantee correct initialization and management of Layer 2 parameters. If 
the SNMP configuration is invalid, the Audit Log records a resynchronization failure.

Configuring SNMPv3 is more complex than configuring SNMPv1 or SNMPv2, because the following 
tables must be filled in:

SNMPv3 NE User table—The SNMP users for each NE.

SNMPv3 User Group table—The grouping of NE SNMP users.

SNMPv3 Group View table—A view for any SNMPv3 user grouping.

SNMPv3 NE Trap Destination table—The SNMP trap configuration.

GNE

Enable

Enable

Enable

CTM server IP 
address

Public

162

SNMPv1

—

ENE (with 
relay)

Enable

Enable

Enable

CTM server IP 
address

Public

162

SNMPv1

Active 
GNE’s IP 
address

ENE (without 
relay)

Enable

Enable

Enable

GNE IP 
address

Public

391

SNMPv1

—

GNE

Enable

Enable

Enable

CTM server IP 
address

Public

162

SNMPv2

—

ENE (with 
relay)

Enable

Enable

Enable

CTM server IP 
address

Public

162

SNMPv2

Active 
GNE’s IP 
address

ENE (without 
relay)

Not supported.