Table Of Contents
DLPs E301 to E399
DLP-E301 Automatically Configure the SNMPv3 Proxy Forwarder Table
DLP-E302 Manually Configure the SNMPv3 Proxy Trap Forwarder Table
DLP-E302 Automatically Configure the SNMPv3 Proxy Trap Forwarder Table
DLP-E304 Repair Server Trails
DLPs E301 to E399
Note 
The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.
DLP-E301 Automatically Configure the SNMPv3 Proxy Forwarder Table
Purpose
|
This procedure creates an entry in the SNMPv3 Proxy Forwarder Table.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
E26 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite
|
Security Level
|
Provisioning or higher
|
Step 1 In network view, click Provisioning > SNMPv3 tabs.
Step 2 In the SNMPv3 Proxy Server area, complete the following:
•Select the GNE to be used as the SNMPv3 proxy server from the drop-down list.
•Select the Enable IPv6 Target/Trap check box if the nodes and the NMS stations are on an IPv6 network.
Step 3 In the SNMPv3 Proxy Forwarder Table area, click Auto Create.
Step 4 In the Automatic Configuration of SNMPv3 Proxy Forwarder dialog box, enter the following information:
•Proxy Type—Select the type of proxies to be forwarded. The options are Read and Write.
•Security Level—Select the security level for the incoming requests that are to be forwarded. The options are:
–noAuthNoPriv—Uses a username match for authentication.
–AuthNoPriv—Provides authentication based on the HMAC-MD5 or HMAC-SHA algorithms.
–AuthPriv—Provides authentication based on the HMAC-MD5 or HMAC-SHA algorithms. Provides DES 56-bit encryption based on the CBC-DES (DES-56) standard, in addition to authentication.
•Target Address List—Select the proxy destination.
•Local User Name—Select the user name from the list of users.
Note When you configure SNMPv3 Proxy Forwarder Table automatically, the default_group is used on the ENE. The default_group does not have write access. To enable write access and allow SNMP sets, you need to edit the default_group on ENE.
Step 5 Click OK to save the settings.
Step 6 Return to your originating procedure (NTP).
DLP-E302 Manually Configure the SNMPv3 Proxy Trap Forwarder Table
Purpose
|
This procedure creates an entry in the SNMPv3 Proxy Trap Forwarder Table.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
E26 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite
|
Security Level
|
Provisioning or higher
|
Step 1 In network view, click Provisioning > SNMPv3 tabs.
Step 2 In the SNMPv3 Proxy Server area, complete the following:
•Select the GNE to be used as the SNMPv3 proxy server from the drop-down list.
•Select the Enable IPv6 Target/Trap check box if the nodes and the NMS stations are on an IPv6 network.
Step 3 In the SNMPv3 Proxy Trap Forwarder Table area, click Manual Create.
Step 4 In the Manual Configuration of SNMPv3 Proxy Trap Forwarder dialog box, enter the following information:
•Remote Trap Source—Select the IP address from which the traps are sent. If the IP address is not listed, enter the IP address manually.
•Context Engine ID—Specify the context engine ID of the ENE from which traps need to be forwarded. This field is automatically populated if the source of trap is selected. If the source of trap is not specified, you need to manually enter the context engine ID.
•Target Tag—Specify the tag name. The tag identifies the list of NMS that should receive the forwarded traps. Traps are forwarded to all GNE Trap destinations whose proxy tags list contains this tag.
•Remote User Details
–User Name—Specify the user name.
–Security Level—Select the security level for the user. The options are noAuthNoPriv, AuthNoPriv, and AuthPriv.
•Authentication—Select the authentication algorithm.
–Protocol—Select the authentication algorithm you want to use. The options are NONE, MD5, and SHA. Default is None.
–Password—Enter the password if you select MD5 or SHA.
•Privacy—Enables the host to encrypt the contents of the message that is sent to the agent.
–Protocol—Select NONE or DES as the privacy authentication algorithm. Encryption is disabled if NONE is selected.
–Password—Enter the password if you select DES. The password should not exceed 64 characters.
Step 5 Click OK to save the information.
Step 6 Return to your originating procedure (NTP).
DLP-E302 Automatically Configure the SNMPv3 Proxy Trap Forwarder Table
Purpose
|
This procedure creates an entry in the SNMPv3 Proxy Trap Forwarder Table automatically.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
E26 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite
|
Security Level
|
Provisioning or higher
|
Step 1 In network view, click Provisioning > SNMPv3 tabs.
Step 2 In the SNMPv3 Proxy Server area, complete the following:
•Select the GNE to be used as the SNMPv3 proxy server from the drop-down list.
•Select the Enable IPv6 Target/Trap check box if the nodes and the NMS stations are on an IPv6 network.
Step 3 In the SNMPv3 Proxy Trap Forwarder Table area, click Auto Create.
Step 4 In the Automatic Configuration of SNMPv3 Proxy Trap Forwarder dialog box, enter the following information:
•Target Tag—Specify the tag name. The tag identifies the list of NMS that should receive the forwarded traps. All GNE Trap destinations that have this tag in their proxy tags list are chosen.
•Source of Trap—The list of ENEs whose traps are forwarded to the SNMPv3 Trap destinations that are identified by the Target Tag.
Step 5 Click OK to save the information.
Step 6 Return to your originating procedure (NTP).
DLP-E304 Repair Server Trails
Purpose
|
This procedure repairs Server Trail terminations in cases where IP address changes for a node connected by a Server Trail link.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
E26 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Note The Server Trail Repair wizard can only fix the IP address changes and cannot fix Server Trail terminations when you migrate from IPv4 to IPv6 addresses.
Note The Server Trail Repair wizard cannot repair the Server Trails when IP address of nodes on both ends of the Server Trail are changed.
Note When Server Trails are created on an IPv4 or IPv6 node and the IP address of the node changes, make sure that the Server Trail Repair wizard is launched on the IP address of the node that changed. For example, if the IP address of Server Trails created on an IPv4 node changes, run the Server Trail Repair wizard on the IPv4 node and not on the IPv6 node.
Step 1 Complete the "DLP-E26 Log into CTC" task at the node where you will repair Server Trails. If you are already logged in, continue with Step 2.
Note The Server Trail Repair wizard works only when nodes at both ends of the Server Trail are added in the CTC. If CTC is launched after the IP address is changed or if the node on any of the sides is not discovered automatically, then the node has to be added manually into the CTC.
Step 2 From the View menu, choose Go to Network View.
Step 3 Choose the Tools > Links > Repair Server Trails option from the tool bar.
The Server Trail Repair wizard appears.
Step 4 Specify the changed IP address.
The Server Trail Repair window provides the following options, as shown in Figure 19-1:
Figure 19-1 Server Trail Repair Wizard—Server Trail Repair Introduction
•Try to discover IP address changes—The wizard searches and displays the list of changed IP addresses.
Note The wizard can discover multiple IP address changes. However, the wizard can repair only one IP address change at a time. To repair multiple IP address changes, run the Server Trail Repair wizard multiple times.
•Apply the following IP change—Allows you to specify the changed IP address.
Select the node with changed IP address and specify old IP address as Original IP Address. The wizard automatically displays the current IP address.
Step 5 Click Next.
If you selected "Try to discover IP address changes" option in Step 4, then the wizard displays all the IP address changes that will be fixed, as shown in Figure 19-2. Click Next.
Figure 19-2 Server Trail Repair Wizard—Discover IP Change
If you selected "Apply the following IP change" option in Step 4, continue with Step 6.
Step 6 The Server Trail Terminations to Repair window appears, as shown in Figure 19-3. Click Finish to repair the Server Trails.
Figure 19-3 Server Trail Repair Wizard—Server Trail Terminations to Repair
Stop. You have completed this procedure.
Feedback
