Table Of Contents
DLPs C200 to C299
DLP-C200 Provision OSI Routing Mode
DLP-C201 Provision or Modify TARP Operating Parameters
DLP-C202 Add a Static TID to NSAP Entry to the TARP Data Cache
DLP-C203 Remove a Static TID to NSAP Entry from the TARP Data Cache
DLP-C204 Add a TARP Manual Adjacency Table Entry
DLP-C205 Provision OSI Routers
DLP-C206 Provision Additional Manual Area Addresses
DLP-C207 Enable the OSI Subnet on the LAN Interface
DLP-C208 Create an IP-Over-CLNS Tunnel
DLP-C209 Remove a TARP Manual Adjacency Table Entry
DLP-C210 Change the OSI Routing Mode
DLP-C211 Edit the OSI Router Configuration
DLP-C212 Edit the OSI Subnetwork Point of Attachment
DLP-C213 Edit an IP-Over-CLNS Tunnel
DLP-C214 Delete an IP-Over-CLNS Tunnel
DLP-C215 View IS-IS Routing Information Base
DLP-C216 View ES-IS Routing Information Base
DLP-C217 Manage the TARP Data Cache
DLP-C218 Soft-Reset the 15310-CL-CTX Using CTC
DLP-C219 Hard-Reset the 15310-CL-CTX Using CTC
DLP-C220 Soft-Reset an Ethernet Card Using CTC
DLP-C221 Hard-Reset an Ethernet Card Using CTC
DLP-C222 Print CTC Data
DLP-C223 Export CTC Data
DLP-C224 Change Optics Thresholds Settings for Optical Ports
DLP-C225 Set Up SNMP for a GNE
DLP-C226 Set Up SNMP for an ENE
DLP-C227 Format and Enter NMS Community String for SNMP Command or Operation
DLPs C200 to C299
DLP-C200 Provision OSI Routing Mode
Purpose
|
This task provisions the Open System Interconnection (OSI) routing mode. Complete this task when the ONS 15310-CL is connected to networks with third party network elements (NEs) that use the OSI protocol stack for data communications network (DCN) communication.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
C18 Verify Ethernet Card and SFP Installation
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite
|
Security Level
|
Provisioning or higher
|
Caution 
Do not complete this task until you confirm the role of the node within the network. It will be either an ES or IS Level 1. This decision must be carefully considered. For additional information about OSI provisioning, refer to the "Management Network Connectivity" chapter of the
ONS 15310-CL Reference Manual.
Caution Link State Protocol (LSP) buffers must be the same at all NEs within the network, or loss of visibility might occur. Do not modify the LSP buffers unless you confirm that all NEs within the OSI have the same buffer size.
Caution LSP buffer sizes cannot be greater than the LAP-D maximum transmission unit (MTU) size within the OSI area.
Note The ONS 15310-CL primary NSAP address is also the Router 1 primary manual area address. To edit the primary NSAP, you must edit the Router 1 primary manual area address. After you enable Router 1 on the Routers subtab, the Change Primary Area Address button is available to edit the address.
Step 1 Complete the "DLP-C29 Log into CTC" task at the node where you want to provision the OSI routing mode. If you are already logged in, continue with Step 2.
Step 2 In node view, click the Provisioning > OSI tabs.
Step 3 Choose a routing mode:
•End System—The ONS 15310-CL performs OSI end system (ES) functions and relies upon an intermediate system (IS) for communication with nodes that reside within its OSI area.
Note The End System routing mode is not available if more than one virtual router is enabled.
•Intermediate System Level 1—The ONS 15310-CL performs OSI IS functions. It communicates with IS and ES nodes that reside within its OSI area. It depends upon an IS L1/L2 node to communicate with IS and ES nodes that reside outside its OSI area.
Step 4 If needed, change the L1 LSP Buffer Size. This adjusts the Level 1 link state protocol data unit (PDU) buffer size. The default is 512. It should not be changed.
Step 5 Return to your originating procedure (NTP).
DLP-C201 Provision or Modify TARP Operating Parameters
Purpose
|
This task provisions or modifies the Target Identifier Address Resolution Protocol (TARP) operating parameters including TARP PDU propagation, timers, and loop detection buffer (LDB).
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Superuser
|
Step 1 In node view, click the Provisioning > OSI > TARP > Config tabs.
Step 2 Provision the following parameters, as needed:
•TARP PDUs L1 Propagation—If checked (default), TARP Type 1 PDUs that are received by the node and are not excluded by the LDB are propagated to other NEs within the Level 1 OSI area. (Type 1 PDUs request a protocol address that matches a target identifier [TID] within a Level 1 routing area.) The propagation does not occur if the NE is the target of the Type 1 PDU, and PDUs are not propagated to the NE from which the PDU was received.
Note This parameter is not used when the Node Routing Area (Provisioning > OSI > Main Setup tab) is set to End System.
•TARP PDUs Origination—If checked (default), the node performs all TARP origination functions including:
–TID to Network Service Access Point (NSAP) resolution requests (originate TARP Type 1 and Type 2 PDUs)
–NSAP to TID requests (originate Type 5 PDUs)
–TARP address changes (originate Type 4 PDUs)
Note TARP Echo is not supported.
•TARP Data Cache—If checked (default), the node maintains a TARP data cache (TDC). The TDC is a database of TID to NSAP pairs created from TARP Type 3 PDUs received by the node and modified by TARP Type 4 PDUs (TID to NSAP updates or corrections). TARP 3 PDUs are responses to Type 1 and Type 2 PDUs. The TDC can also be populated with static entries entered on the TARP > Static TDC tab.
Note This parameter is only used when the TARP PDUs Origination parameter is enabled.
•LDB—If checked (default), enables the TARP loop detection buffer. The LDB prevents TARP PDUs from being sent more than once on the same subnet.
Note The LDP parameter is not used if the Node Routing Mode is provisioned to End System or if the TARP PDUs L1 Propagation parameter is not enabled.
•LAN TARP Storm Suppression—If checked (default), enables TARP storm suppression. This function prevents redundant TARP PDUs from being unnecessarily propagated across the LAN network.
•Send Type 4 PDU on Startup—If checked, a TARP Type 4 PDU is originated during the initial ONS 15310 startup. Type 4 PDUs indicate that a TID or NSAP change has occurred at the NE. (The default setting is not enabled.)
•Type 4 PDU Delay—Sets the amount of time that will pass before the Type 4 PDU is generated when Send Type 4 PDU on Startup is enabled. 60 seconds is the default. The range is 0 to 255 seconds.
Note The Send Type 4 PDU on Startup and Type 4 PDU Delay parameters are not used if TARP PDUs Origination is not enabled.
•LDB Entry—Sets the TARP loop detection buffer timer. The LDB buffer time is assigned to each LDB entry for which the TARP sequence number (tar-seq) is zero. The default is 5 minutes. The range is 1 to 10 minutes.
•LDB Flush—Sets the frequency period for flushing the LDB. The default is 5 minutes. The range is 0 to 1440 minutes.
•T1—Sets the amount of time to wait for a response to a Type 1 PDU. Type 1 PDUs seek a specific NE TID within an OSI Level 1 area. The default is 15 seconds. The range is 0 to 3600 seconds.
•T2—Sets the amount of time to wait for a response to a Type 2 PDU. TARP Type 2 PDUs seek a specific NE TID value within OSI Level 1 and Level 2 areas. The default is 25 seconds. The range is 0 to 3600 seconds.
•T3—Sets the amount of time to wait for an address resolution request. The default is 40 seconds. The range is 0 to 3600 seconds.
•T4—Sets the amount of time to wait for an error recovery. This timer begins after the T2 timer expires without finding the requested NE TID. The default is 20 seconds. The range is 0 to 3600 seconds.
Note Timers T1, T2, and T4 are not used if TARP PDUs Origination is not enabled.
Step 3 Click Apply.
Step 4 Return to your originating procedure (NTP).
DLP-C202 Add a Static TID to NSAP Entry to the TARP Data Cache
Purpose
|
This task adds a static TID to NSAP entry to the TDC. The static entries are required for NEs that do not support TARP and are similar to static routes. For a specific TID, you must force a specific NSAP.
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioner or higher
|
Step 1 In node view, click the Provisioning > OSI > TARP > Static TDC tabs.
Step 2 Click Add Static Entry.
Step 3 In the Add Static Entry dialog box, enter the following:
•TID—Enter the TID of the NE. (For ONS nodes, the TID is the Node Name parameter on the node view Provisioning > General tab.)
•NSAP—Enter the OSI NSAP address in the NSAP field or, if preferred, click Use Mask and enter the address in the Masked NSAP Entry dialog box.
Step 4 Click OK to close the Masked NSAP Entry dialog box, if used, and then click OK to close the Add Static Entry dialog box.
Step 5 Return to your originating procedure (NTP).
DLP-C203 Remove a Static TID to NSAP Entry from the TARP Data Cache
Purpose
|
This task removes a static TID to NSAP entry from the TDC.
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioner or higher
|
Step 1 In node view, click the Provisioning > OSI > TARP > Static TDC tabs.
Step 2 Click the static entry that you want to delete.
Step 3 Click Delete Static Entry.
Step 4 In the Delete TDC Entry dialog box, click Yes.
Step 5 Return to your originating procedure (NTP).
DLP-C204 Add a TARP Manual Adjacency Table Entry
Purpose
|
This task adds an entry to the TARP manual adjacency table (MAT). Entries are added to the MAT when the ONS 15310-CL must communicate across routers or non-SONET NEs that lack TARP capability.
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 In the node view, click the Provisioning > OSI > TARP > MAT tabs.
Step 2 Click Add.
Step 3 In the Add TARP Manual Adjacency Table Entry dialog box, enter the following:
•Level—Sets the TARP Type Code that will be sent:
–Level 1—Indicates that the adjacency is within the same area as the current node. The entry generates Type 1 PDUs.
–Level 2—Indicates that the adjacency is in a different area than the current node. The entry generates Type 2 PDUs.
•NSAP—Enter the OSI NSAP address in the NSAP field or, if preferred, click Use Mask and enter the address in the Masked NSAP Entry dialog box.
Step 4 Click OK to close the Masked NSAP Entry dialog box, if used, and then click OK to close the Add Static Entry dialog box.
Step 5 Return to your originating procedure (NTP).
DLP-C205 Provision OSI Routers
Purpose
|
This task enables the OSI virtual router and edits its primary manual area address.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
C18 Verify Ethernet Card and SFP Installation
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Note The Router 1 manual area address, System ID, and Selector "00" create the node NSAP address. Changing the Router 1 manual area address changes the node's NSAP address.
Note The System ID for Router 1 is the node MAC address.
Step 1 Complete the "DLP-C29 Log into CTC" task at the node of the OSI routers that you want to provision.
Step 2 Click the Provisioning > OSI > Routers > Setup tabs.
Step 3 Chose the router you want provision and click Edit.
Step 4 In the OSI Router Editor dialog box:
a. Check Enable Router to enable the router and make its primary area address available for editing.
b. Click the manual area address, then click Edit.
c. In the Edit Manual Area Address dialog box, edit the primary area address in the Area Address field. If you prefer, click Use Mask and enter the edits in the Masked NSAP Entry dialog box. The address (hexadecimal format) can be 8 to 24 alphanumeric characters (0-9, a-f) in length.
d. Click OK successively to close the following dialog boxes: Masked NSAP Entry (if used), Edit Manual Area Address, and OSI Router Editor.
Step 5 Return to your originating procedure
DLP-C206 Provision Additional Manual Area Addresses
Step 1 Click the Provisioning > OSI > Routers > Setup tabs.
Step 2 Chose the router where you want provision an additional manual area address and click Edit. The OSI Router Editor dialog box () appears.
Step 3 In the OSI Router Editor dialog box:
a. Check Enable Router to enable the router and make its primary area address available for editing.
b. Click the manual area address, then click Add.
c. In the Add Manual Area Address dialog box, enter the primary area address in the Area Address field. If you prefer, click Use Mask and enter the address in the Masked NSAP Entry dialog box. The address (hexadecimal format) can be 2 to 24 alphanumeric characters (0-9, a-f) in length.
d. Click OK successively to close the following dialog boxes: Masked NSAP Entry (if used), Add Manual Area Address, and OSI Router Editor.
Step 4 Return to your originating procedure
DLP-C207 Enable the OSI Subnet on the LAN Interface
Purpose
|
This task enables the OSI subnetwork point of attachment on the LAN interface.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
C18 Verify Ethernet Card and SFP Installation
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Note OSI subnetwork points of attachment are enabled on DCCs when you create DCCs. See the "DLP-C52 Provision Section DCC Terminations" task and the "DLP-C53 Provision Line DCC Terminations" task.
Note The OSI subnetwork point of attachment cannot be enabled for the LAN interface if the OSI routing mode is set to ES (end system).
Note If Secure Mode is on, the OSI Subnet is enabled on the backplane LAN port, not the front TCC2P port.
Step 1 Complete the "DLP-C29 Log into CTC" task at the node whose OSI routers you want to provision.
Step 2 Click the Provisioning > OSI > Routers > Subnet tabs.
Step 3 Click Enable LAN Subnet.
Step 4 In the Enable LAN Subnet dialog box, complete the following fields:
•ESH—Sets the End System Hello (ESH) propagation frequency. End system NEs transmit ESHs to inform other ESs and ISs about the NSAPs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.
•ISH—Sets the Intermediate System Hello PDU propagation frequency. Intermediate system NEs send ISHs to other ESs and ISs to inform them about the IS NETs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.
•IIH—Sets the Intermediate System to Intermediate System Hello PDU propagation frequency. The IS-IS Hello PDUs establish and maintain adjacencies between ISs. The default is 3 seconds. The range is 1 to 600 seconds.
•IS-IS Cost—Sets the cost for sending packets on the LAN subnet. The IS-IS protocol uses the cost to calculate the shortest routing path. The default IS-IS cost for LAN subnets is 20. It normally should not be changed.
•DIS Priority—Sets the designated intermediate system (DIS) priority. In IS-IS networks, one router is elected to serve as the DIS (LAN subnets only). Cisco router DIS priority is 64. For the ONS 15454 LAN subnet, the default DIS priority is 63. It normally should not be changed.
Step 5 Click OK.
Step 6 Return to your originating procedure (NTP).
DLP-C208 Create an IP-Over-CLNS Tunnel
Purpose
|
This task creates an IP-over-CLNS tunnel to allow ONS 15310-CL nodes to communicate across equipment and networks that use the OSI protocol stack.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
C18 Verify Ethernet Card and SFP Installation
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Caution IP-over-CLNS tunnels require two end points. You will create one point on an ONS 15310-CL. The other end point is generally provisioned on non-ONS equipment including routers and other vendor NEs. Before you begin, verify that you have the capability to create an IP-over-CLNS tunnel on the other equipment location.
Step 1 Complete the "DLP-C29 Log into CTC" task at the node of the OSI routers that you want to provision.
Step 2 Click the Provisioning > OSI > Tunnels tabs.
Step 3 Click Create.
Step 4 In the Create IP Over CLNS Tunnel dialog box, complete the following fields:
•Tunnel Type—Choose a tunnel type:
–Cisco—Creates the proprietary Cisco IP tunnel. Cisco IP tunnels add the CLNS header to the IP packets.
–GRE—Creates a Generic Routing Encapsulation tunnel. GRE tunnels add the CLNS header and a GRE header to the IP packets.
The Cisco proprietary tunnel is slightly more efficient than the GRE tunnel because it does not add the GRE header to each IP packet. The two tunnel types are not compatible. Most Cisco routers support the Cisco IP tunnel, while only a few support both GRE and Cisco IP tunnels. You generally should create Cisco IP tunnels if you are tunneling between two Cisco routers or between a Cisco router and an ONS node.
Caution Always verify that the IP-over-CLNS tunnel type you choose is supported by the equipment at the other end of the tunnel.
•IP Address—Enter the IP address of the IP-over-CLNS tunnel destination.
•IP Mask—Enter the IP address subnet mask of the IP-over-CLNS destination.
•OSPF Metric—Enter the Open Shortest Path First (OSPF) metric for sending packets across the IP-over-CLNS tunnel. The OSPF metric, or cost, is used by OSPF routers to calculate the shortest path. The default is 110. Normally, it is not be changed unless you are creating multiple tunnel routes and want to prioritize routing by assigning different metrics.
•NSAP Address—Enter the destination NE or OSI router NSAP address.
Step 5 Click OK.
Step 6 Provision the other tunnel end point using the documentation
Step 7 Return to your originating procedure (NTP).
DLP-C209 Remove a TARP Manual Adjacency Table Entry
Purpose
|
This task removes an entry from the TARP manual adjacency table.
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Caution If TARP manual adjacency is the only means of communication to a group of nodes, loss of visibility will occur when the adjacency table entry is removed.
Step 1 In node view, click the Provisioning > OSI > TARP > MAT tabs.
Step 2 Click the MAT entry that you want to delete.
Step 3 Click Remove.
Step 4 In the Delete TDC Entry dialog box, click OK.
Step 5 Return to your originating procedure (NTP).
DLP-C210 Change the OSI Routing Mode
Purpose
|
This task changes the OSI routing mode.
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Caution Do not complete this procedure until you confirm the role of the node within the network. It will be either an ES or IS Level 1. This decision must be carefully considered. For additional information about OSI provisioning, refer to the "Management Network Connectivity" chapter of the
ONS 15310-CL Reference Manual.
Caution LSP buffers must be the same at all NEs within the network, or loss of visibility could occur. Do not modify the LSP buffers unless you are sure that all NEs within the OSI have the same buffer size.
Caution LSP buffer sizes cannot be greater than the LAP-D MTU size within the OSI area.
Step 1 Verify the following:
•For OSI L1 to ES routing mode changes, only one L1 virtual router and no more than one subnet can be configured.
Step 2 In node view, click the Provisioning > OSI tabs.
Step 3 Choose one of the following routing modes:
•End System—The ONS 15310-CL performs OSI IS functions. It communicates with IS and ES nodes that reside within its OSI area. It depends upon an IS L1/L2 node to communicate with IS and ES nodes that reside outside its OSI area.
Note Changing a routing mode should be carefully considered. Additional information about OSI ESs and ISs and the ES-IS and IS-IS protocols are provided in the "Network Connectivity" chapter of the ONS 15310-CL Reference Manual.
Step 4 Although Cisco does not recommend changing the LSP (Link State Protocol Data Unit) buffer sizes, you can change the L1 LSP Buffer Size field to change the Level 1 link state PDU buffer size.
Step 5 Return to your originating procedure (NTP).
DLP-C211 Edit the OSI Router Configuration
Purpose
|
This task edits the OSI router configuration, including enabling and disabling OSI routers, editing the primary area address, and creating or editing additional area addresses.
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 Click the Provisioning > OSI > Routers > Setup tabs.
Step 2 Choose the router you want provision and click Edit.
Step 3 In the OSI Router Editor dialog box ():
a. Check or uncheck the Enabled box to enable or disable the router.
Note Router 1 must be enabled before you can enable Routers 2 and 3.
b. For enabled routers, edit the primary area address, if needed. The address can be between 8 and 24 alphanumeric characters in length.
c. If you want to add or edit an area address to the primary area, enter the address at the bottom of the Multiple Area Addresses area. The area address can be 2 to 26 numeric characters (0-9) in length. Click Add.
d. Click OK.
Step 4 Return to your originating procedure (NTP).
DLP-C212 Edit the OSI Subnetwork Point of Attachment
Purpose
|
This task allows you to view and edit the OSI subnetwork point of attachment parameters. The parameters are initially provisioned when you create a Section DCC (SDCC), Line DCC (LDCC), generic communications channel (GCC), or optical service channel (OSC), or when you enable the LAN subnet.
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 In the node view, click the Provisioning > OSI > Routers > Subnet tabs.
Step 2 Choose the subnet you want to edit, then click Edit.
Step 3 In the Edit <subnet type> Subnet <slot/port> dialog box, edit the following fields:
•ESH—The End System Hello PDU propagation frequency. An end system NE transmits ESHs to inform other ESs and ISs about the NSAPs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.
•ISH—The Intermediate System Hello PDU propagation frequency. An intermediate system NE sends ISHs to other ESs and ISs to inform them about the NETs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.
•IIH—The Intermediate System to Intermediate System Hello PDU propagation frequency. The IS-IS Hello PDUs establish and maintain adjacencies between ISs. The default is 3 seconds. The range is 1 to 600 seconds.
Note The IS-IS Cost and DIS Priority parameters are provisioned when you create or enable a subnet. You cannot change the parameters after the subnet is created. To change the DIS Priority and IS-IS Cost parameters, delete the subnet and create a new one.
Click OK.
Step 4 Return to your originating procedure (NTP).
DLP-C213 Edit an IP-Over-CLNS Tunnel
Purpose
|
This task edits the parameters of an IP-over-CLNS tunnel.
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
C208 Create an IP-Over-CLNS Tunnel
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Caution Changing the IP or NSAP addresses or an IP-over-CLNS tunnel can cause loss of NE visibility or NE isolation. Do not change network addresses until you verify the changes with your network administrator.
Step 1 Click the Provisioning > OSI > Tunnels tabs.
Step 2 Click Edit.
Step 3 In the Edit IP Over OSI Tunnel dialog box, complete the following fields:
•Tunnel Type—Edit the tunnel type:
–Cisco—Creates the proprietary Cisco IP tunnel. Cisco IP tunnels add the CLNS header to the IP packets.
–GRE—Creates a Generic Routing Encapsulation tunnel. GRE tunnels add the CLNS header and a GRE header to the IP packets.
The Cisco proprietary tunnel is slightly more efficient than the GRE tunnel because it does not add the GRE header to each IP packet. The two tunnel types are not compatible. Most Cisco routers support the Cisco IP tunnel, while only a few support both GRE and Cisco IP tunnels. You generally should create Cisco IP tunnels if you are tunneling between two Cisco routers or between a Cisco router and an ONS node.
Caution Always verify that the IP-over-CLNS tunnel type you choose is supported by the equipment at the other end of the tunnel.
•IP Address—Enter the IP address of the IP-over-CLNS tunnel destination.
•IP Mask—Enter the IP address subnet mask of the IP-over-CLNS destination.
•OSPF Metric—Enter the OSPF metric for sending packets across the IP-over-CLNS tunnel. The OSPF metric, or cost, is used by OSPF routers to calculate the shortest path. The default is 110. Normally, it is not be changed unless you are creating multiple tunnel routes and want to prioritize routing by assigning different metrics.
•NSAP Address—Enter the destination NE or OSI router NSAP address.
Step 4 Click OK.
Step 5 Return to your originating procedure (NTP).
DLP-C214 Delete an IP-Over-CLNS Tunnel
Purpose
|
This task allows you to delete an IP-over-CLNS tunnel.
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Caution Deleting an IP-over-CLNS tunnel might cause the nodes to loose visibility or cause node isolation. If node isolation occurs, onsite provisioning might be required to regain connectivity. Always confirm tunnel deletions with your network administrator.
Step 1 Click the Provisioning > OSI > Tunnels tabs.
Step 2 Choose the IP-over-CLNS tunnel that you want to delete.
Step 3 Click Delete.
Step 4 Click OK.
Step 5 Return to your originating procedure (NTP).
DLP-C215 View IS-IS Routing Information Base
Purpose
|
This task allows you to view the Intermediate System-to-Intermediate-System (IS-IS) protocol routing information base (RIB). IS-IS is an OSI routing protocol that floods the network with information about NEs on the network. Each NE uses the information to build a complete and consistent picture of a network topology. The IS-IS RIB shows the network view from the perspective of the IS node.
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 In node view, click the Maintenance > OSI > IS-IS RIB tabs.
Step 2 View the following RIB information for Router 1:
•Subnet Type—Indicates the OSI subnetwork point of attachment type used to access the destination address. Subnet types include SDCC, LDCC, GCC, OSC, and LAN.
•Location—Indicates the OSI subnetwork point of attachment. For DCC subnets, the slot and port are displayed. LAN subnets are shown as LAN.
•Destination Address—The destination network service access point (NSAP) of the IS.
•MAC Address—For destination NEs that are accessed by LAN subnets, the NE's MAC address.
Step 3 If additional routers are enabled, you can view their RIBs by choosing the router number in the Router field and clicking Refresh.
Step 4 Return to your originating procedure (NTP).
DLP-C216 View ES-IS Routing Information Base
Purpose
|
This task allows you to view the End-System-to-Intermediate-System (ES-IS) protocol RIB. ES-IS is an OSI protocol that defines how end systems (hosts) and intermediate systems (routers) learn about each other. For ESs, the ES-IS RIB shows the network view from the perspective of the ES node. For ISs, the ES-IS RIB shows the network view from the perspective of the IS node.
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 In node view, click the Maintenance > OSI > ES-IS RIB tabs.
Step 2 View the following RIB information for Router 1:
•Subnet Type—Indicates the OSI subnetwork point of attachment type used to access the destination address. Subnet types include SDCC, LDCC, GCC, OSC, and LAN.
•Location—Indicates the subnet interface. For DCC subnets, the slot and port are displayed. LAN subnets are shown as LAN.
•Destination Address—The destination IS NSAP.
•MAC Address—For destination NEs that are accessed by LAN subnets, the NE's MAC address.
Step 3 If additional routers are enabled, you can view their RIBs by choosing the router number in the Router field and clicking Refresh.
Step 4 Return to your originating procedure (NTP).
DLP-C217 Manage the TARP Data Cache
Purpose
|
This task allows you to view and manage the TARP data cache (TDC). The TDC facilitates TARP processing by storing a list of TID to NSAP mappings.
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 In node view, click the Maintenance > OSI > TDC tabs.
Step 2 View the following TARP data cache information:
•TID—The target identifier of the originating NE. For ONS 15454s, the TID is the name entered in the Node Name/TID field on the Provisioning > General tab.
•NSAP/NET—The NSAP or Network Element Title (NET) of the originating NE.
•Type—Indicates how the TDC entry was created:
–Dynamic—The entry was created through the TARP propagation process.
–Static—The entry was manually created and is a static entry.
Step 3 If you want to query the network for an NSAP that matches a TID, complete the following steps. Otherwise, continue with Step 4.
Note The TID to NSAP function is not available if the TDC is not enabled on the Provisioning > OSI > TARP subtab.
a. Click the TID to NSAP button.
b. In the TID to NSAP dialog box, enter the TID that you want to map to an NSAP.
c. Click OK, then click OK in the information message.
d. On the TDC tab, click Refresh.
If TARP finds the TID in its TDC, it returns the matching NSAP. If not, TARP sends PDUs across the network. Replies will return to the TDC later, and a "check TDC later" message is displayed.
Step 4 If you want to delete all the dynamically generated TDC entries, click the Flush Dynamic Entries button. If not, continue with Step 5.
Step 5 Return to your originating procedure (NTP).
DLP-C218 Soft-Reset the 15310-CL-CTX Using CTC
Purpose
|
This task resets the 15310-CL-CTX card using a soft reset. A soft reset reboots the card and reloads the operating system and the application software.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
C29 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Maintenance or higher
|
Caution Soft-resetting the 15310-CL-CTX card causes a traffic hit only if a provisioning change or firmware update has occurred. Otherwise, the soft reset is errorless.
Note Before you reset the 15310-CL-CTX, you should wait at least 60 seconds after the last provisioning change to avoid losing any changes to the database.
Note 15310-CL-CTX does not support a real time clock with battery backup. Hence, during a card reset, the time is reset to default and the date starts at 1970 till you set the time/date again.
Note A software reset causes a standard Telcordia protection switch of less than 50 ms.
Step 1 In node view, right-click the 15310-CL-CTX card to reveal a drop-down list.
Step 2 Click Soft-Reset Card.
Step 3 Click Yes when the "Are You Sure?" dialog box appears.
Step 4 Return to your originating procedure (NTP).
DLP-C219 Hard-Reset the 15310-CL-CTX Using CTC
Purpose
|
This task resets the 15310-CL-CTX card using a hard reset. A hard reset temporarily removes power from the card and clears all buffer memory.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
C29 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Maintenance or higher
|
Caution Hard-resetting the 15310-CL-CTX card causes a traffic hit.
Note Before you reset the 15310-CL-CTX, you should wait at least 60 seconds after the last provisioning change to avoid losing any changes to the database.
Note 15310-CL-CTX does not support a real time clock with battery backup. Hence, during a card reset, the time is reset to default and the date starts at 1970 till you set the time/date again.
Note A software reset causes a standard Telcordia protection switch of less than 50 ms.
Step 1 In node view, click the Inventory tab. Locate the 15310-CL-CTX in the inventory pane.
Step 2 Click the Admin State drop-down list and select OOS-MT. Click Apply.
Step 3 Click Yes in the "Action may be service affecting. Are you sure?" dialog box.
Step 4 The service state of the card becomes OOS-MA,MT. The card faceplate appears blue in CTC.
Step 5 Right-click the card to reveal a shortcut menu.
Step 6 Click Hard-reset Card.
Step 7 Click Yes in the "Are you sure you want to hard-reset this card?" dialog box.
Step 8 Return to your originating procedure (NTP).
DLP-C220 Soft-Reset an Ethernet Card Using CTC
Purpose
|
This task resets the ML1000-T or CE-100T-8 card using a soft reset. A soft reset reboots the card and reloads the operating system and the application software.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
C29 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Maintenance or higher
|
Note Soft-resetting an Ethernet card causes a traffic hit. However, soft-resetting a traffic card is errorless in most cases. If there is a provisioning change during the soft reset, or if the firmware is replaced during the software upgrade process, the reset is not errorless.
Step 1 In node view, right-click the card to reveal a shortcut menu.
Step 2 Click Soft-reset Card.
Step 3 Click Yes in the "Are you sure you want to soft-reset this card?" dialog box.
Step 4 Return to your originating procedure (NTP).
DLP-C221 Hard-Reset an Ethernet Card Using CTC
Purpose
|
This task resets the ML1000-T or CE-100T-8 card using a hard reset. A hard reset temporarily removes power from the card and clears all buffer memory before it is physically reseated.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
C29 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Maintenance or higher
|
Caution Hard-resetting a traffic card causes a traffic hit.
Note The hard-reset option is enabled only when the card is placed in the OOS-MA,MT service state.
Step 1 In node view, click the Inventory tab. Locate the appropriate card in the inventory pane.
Step 2 Click the Admin State drop-down list and select OOS-MT. Click Apply.
Step 3 Click Yes in the "Action may be service affecting. Are you sure?" dialog box.
Step 4 The service state of the card becomes OOS-MA,MT. The card faceplate appears blue in CTC and the SRV LED turns amber.
Step 5 Right-click the card to reveal a shortcut menu.
Step 6 Click Hard-reset Card.
Step 7 Click Yes in the "Are you sure you want to hard-reset this card?" dialog box.
Step 8 Return to your originating procedure (NTP).
DLP-C222 Print CTC Data
Purpose
|
This task prints CTC card, node, or network data in graphical or tabular form on a Windows-provisioned printer.
|
Tools/Equipment
|
Printer connected to the CTC computer by a direct or network connection
|
Prerequisite procedures
|
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 Click the CTC tab (and subtab, if present) containing the information you want to print. For example, click the Alarms tab to print Alarms window data.
The print operation is available for all network, node (default login), and card view windows.
Step 2 From the File menu, choose Print.
Step 3 In the Print dialog box, click a a printing option (Figure 17-1).
•Entire Frame—Prints the entire CTC window including the graphical view of the card, node, or network. This option is available for all windows.
•Tabbed View—Prints the lower half of the CTC window containing tabs and data. The printout includes the selected tab (on top) and the data shown in the tab window. For example, if you print the History window Tabbed View, you print only history items appearing in the window. This option is available for all windows.
•Table Contents—Prints CTC data in table format without graphical representations of shelves, cards, or tabs. This option applies to all windows except:
–Provisioning > General window
–Provisioning > Network > General window
–Provisioning > Security > Policy, Access, or Legal Disclaimer windows
–Provisioning > SNMP window
–Provisioning > Timing > General, BITS Facilities windows
–Provisioning> OSI > Main Setup window
–Maintenance > Database window
–Maintenance > Diagnostic window
–Maintenance > Protection window
–Maintenance > Timing > Source window
The Table Contents option prints all the data contained in a table with the same column headings. For example, if you print the History window Table Contents view, you print all data included in the table whether or not items appear in the window.
Tip When you print using the Tabbed View option, it can be difficult to distinguish whether the printout applies to the network, node, or card view. Look at the tabs to determine which view you are printing. Network, node, and card views are identical except that network view does not contain an Inventory tab; node view and card view contain a Performance tab.
Figure 17-1 Selecting CTC Data For Print
Step 4 Click OK.
Step 5 In the Windows Print dialog box, click a printer and click OK.
Step 6 Repeat this task for each window that you want to print.
Step 7 Return to your originating procedure (NTP).
DLP-C223 Export CTC Data
Purpose
|
This task exports CTC table data as delineated text to view or edit the data in text editor, word processing, spreadsheet, database management, or web browser applications.
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
C29 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve or higher
|
Step 1 Click the CTC tab containing the information you want to export (for example, the Alarms tab or the Circuits tab).
Step 2 From the File menu choose Export.
Step 3 In the Export dialog box (Figure 17-2), click a data format:
•As HTML—Saves data as a simple HTML table file without graphics. The file must be viewed or edited with applications such as Netscape Navigator, Microsoft Internet Explorer, or other applications capable of opening HTML files.
•As CSV—Saves the CTC table as comma-separated values (CSV). This option does not apply to the Maintenance > Timing > Report window.
•As TSV—Saves the CTC table as tab-separated values (TSV).
Step 4 If you want to open a file in a text editor or word processor application, procedures may vary; typically you can use the File > Open command to display the CTC data, or you can double-click the file name and choose an application such as Notepad.
Text editor and word processor applications display the data exactly as it is exported, including comma or tab separators. All applications that open the data files allow you to format the data.
Step 5 If you want to open the file in spreadsheet and database management applications, procedures may vary; typically you need to open the application and choose File > Import, then choose a delimited file to display the data in cells.
Spreadsheet and database management programs also allow you to manage the exported data.
Note An exported file cannot be opened in CTC.
The export operation applies to all tabular data except:
•Provisioning > General window
•Provisioning > Network > General window
•Provisioning > Security > Policy, Access, or Legal Disclaimer windows
•Provisioning > SNMP window
•Provisioning > Timing > General, BITS Facilities windows
•Provisioning > OSI > Main Setup window
•Provisioning > OSI > TARP > Config window
•Maintenance > Database window
•Maintenance > Diagnostic window
•Maintenance > Protection window
•Maintenance > Timing > Source, window
Figure 17-2 Selecting CTC Data For Export
Step 6 Click OK.
Step 7 In the Save dialog box, enter a name in the File name field using one of the following formats:
•[filename].html—for HTML files
•[filename].csv—for CSV files
•[filename].tsv—for TSV files
Step 8 Navigate to a directory where you want to store the file.
Step 9 Click OK.
Step 10 Repeat the task for each window that you want to export.
Step 11 Return to your originating procedure (NTP).
DLP-C224 Change Optics Thresholds Settings for Optical Ports
Purpose
|
This task changes the optics thresholds settings on optical ports. Optical ports on the ONS 15310-CL are provided through Small Form-factor Pluggables (SFPs) installed on the 15310-CL-CTX.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
C29 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 In node view, double-click the 15310-CL-CTX card.
Step 2 Click the Provisioning > Optical > Optics Thresholds tab.
Step 3 Modify any of the settings described in Table 17-1.
Note You must set the OPR value whenever you replace or insert an SFP. After you click Set for the port you are observing, the LBC OPT and the OPR PM value should be close to 100%. Only Cisco-approved SFPs should be used. See Chapter 1 "Install Hardware" for more information about installing SFPs and fiber-optic cable.
Table 17-1 Optics Thresholds Settings
Parameter
|
Description
|
Options
|
Port
|
(Display only) Port number.
|
•1-1, 2-1
|
LBC-LOW
|
Laser bias current-minimum.
|
Default (15 min/1 day): 50 percent
|
LBC-HIGH
|
Laser bias current-maximum.
|
Default (15 min/1 day): 150 percent
|
OPT-LOW
|
Optical power transmitted-minimum.
|
Default (15 min/1 day): 80 percent
|
OPT-HIGH
|
Optical power transmitted-maximum.
|
Default (15 min/1 day): 120 percent
|
OPR-LOW
|
Optical power received-minimum.
|
Default (15 min/1 day): 50 percent
|
OPR-HIGH
|
Optical power received-maximum.
|
Default (15 min/1 day): 200 percent
|
Set OPR
|
Setting the optical power received establishes the received power level as 100 percent. If the receiver power decreases, then the OPR percentage decreases to reflect the loss in receiver power. For example, if the receiver power decreases by 3 dBm, the OPR decreases 50 percent.
|
Click SET.
|
Types
|
Sets the type of alert that occurs when a threshold is crossed. To change the type of threshold, choose one and click Refresh.
|
•TCA (threshold cross alert)
•Alarm
|
Intervals
|
Sets the time interval for collecting parameter counts. To change the time interval, choose the desired interval and click Refresh.
|
•15 Min
•1 Day
|
Step 4 Click Apply.
Step 5 Return to your originating procedure (NTP).
DLP-C225 Set Up SNMP for a GNE
Purpose
|
This procedure provisions simple network management protocol (SNMP) parameters so that you can use SNMP network management software with the ONS 15310.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
C29 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite
|
Security Level
|
Provisioning or higher
|
Step 1 In node view, click the Provisioning > SNMP tabs.
Step 2 In the Trap Destinations area, click Create.
Step 3 On the Create SNMP Trap Destination dialog box, complete the following fields:
•Destination IP Address—Enter the IP address of your network management system (NMS).
•Community—Enter the SNMP community name. (For more information about SNMP, refer to the "SNMP" chapter in the Cisco ONS 15310-CL Troubleshooting Guide.)
Note The community name is a form of authentication and access control. The community name assigned to the ONS 15310 is case-sensitive and must match the community name of the NMS.
•UDP Port—The default User Datagram Protocol (UDP) port for SNMP traps is 162.
•Trap Version—Choose either SNMPv1 or SNMPv2. Refer to your NMS documentation to determine whether to use SNMPv1 or SNMPv2.
Step 4 Click OK. The node IP address of the node where you provisioned the new trap destination appears in the Trap Destinations area.
Step 5 Click the node IP address in the Trap Destinations area. Verify the SNMP information that appears in the Selected Destination list.
Step 6 If you want the SNMP agent to accept SNMP SET requests on certain MIBs, click the Allow SNMP Sets check box. If the box is not checked, SET requests are rejected.
Step 7 If you want to set up the SNMP proxy feature to allow network management, message reporting, and performance statistic retrieval across ONS firewalls, click the Enable SNMP Proxy check box on the SNMP tab.
Note The ONS firewall proxy feature only operates on nodes running releases 4.6 and later. Using this information effectively breaches the ONS firewall to exchange management information.
For more information about the SNMP proxy feature, refer to the "SNMP" chapter of the Cisco ONS 15310-CL Troubleshooting Guide.
Step 8 Click Apply.
Step 9 Return to your originating procedure (NTP).
DLP-C226 Set Up SNMP for an ENE
Purpose
|
This procedure provisions the SNMP parameters for an ONS 15310 configured to be an ENE if you use SNMP proxy on the GNE.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
C29 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite
|
Security Level
|
Provisioning or higher
|
Step 1 In node view, click the Provisioning > SNMP tabs.
Step 2 In the Trap Destinations area, click Create.
Step 3 On the Create SNMP Trap Destination dialog box, complete the following fields:
•Destination IP Address—Enter the IP address of your NMS.
•Community—Enter the SNMP community name. (For more information about SNMP, refer to the "SNMP" chapter in the Cisco ONS 15310 Troubleshooting Guide.)
Note The community name is a form of authentication and access control. The community name assigned to the ONS 15310 is case-sensitive and must match the community name of the NMS.
•UDP Port—The default UDP port for SNMP traps is 162.
•Trap Version—Choose either SNMPv1 or SNMPv2. Refer to your NMS documentation to determine whether to use SNMPv1 or SNMPv2.
Step 4 Click OK. The node IP address of the node where you provisioned the new trap destination appears in the Trap Destinations area.
Step 5 Click the node IP address in the Trap Destinations area. Verify the SNMP information that appears in the Selected Destination list.
Step 6 If you want the SNMP agent to accept SNMP SET requests on certain MIBs, click the Allow SNMP Sets check box. If the box is not checked, SET requests are rejected.
Step 7 If you want to set up the SNMP proxy feature to allow network management, message reporting, and performance statistic retrieval across ONS firewalls, click the Enable SNMP Proxy check box on the SNMP tab.
Note The ONS firewall proxy feature only operates on nodes running releases 4.6 and later. Using this information effectively breaches the ONS firewall to exchange management information.
For more information about the SNMP proxy feature, refer to the "SNMP" chapter of the Cisco ONS 15310-CL Troubleshooting Guide.
Step 8 Click Apply.
Step 9 If you are setting up SNMP proxies, you can set up to three relays for each trap address to convey SNMP traps from the NE to the NMS. To do this, complete the following substeps:
a. Click the first trap destination IP address. The address and its community name appear in the Destination fields.
b. If the node you are logged into is an ENE, set the Relay A address to the GNE and type its community name in the community field. If there are NEs between the GNE and ENE, you can enter up to two SNMP proxy relay addresses and community names in the fields for Relay and Relay C. When doing this, consult the following guidelines:
•If the NE is directly connected to the GNE, enter the address and community name of the GNE for Relay A.
•If this NE is connected to the GNE through other NEs, enter the address and community name of the GNE for Relay A and the address and community name of NE 1 for Relay B and NE 2 for Relay C.
The SNMP proxy directs SNMP traps in the following general order: ENE > RELAY A > RELAY B > RELAY C > NMS. For example:
•If there is are 0 intermediate relays, the order is ENE > RELAY A (GNE) > NMS
•If there is 1 intermediate relay, the order is ENE > RELAY A (NE 1) > RELAY B (GNE) > NMS
•If there is are 0 intermediate relays, the order is ENE > RELAY A (NE 1) > RELAY B (NE 2) > RELAY C (GNE) > NMS
Step 10 Click Apply.
Step 11 Repeat Step 2 through Step 10 for all NEs between the GNE and ENE.
Step 12 Return to your originating procedure (NTP).
DLP-C227 Format and Enter NMS Community String for SNMP Command or Operation
Purpose
|
This procedure describes how to format a network management system (NMS) community string to execute the following SNMP commands for GNEs and ENEs: Get, GetBulk, GetNext, and Set.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
C29 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite
|
Security Level
|
Provisioning or higher
|
Step 1 If the SNMP "Get" (or other operation) is enabled on the ONS 15310 configured as a GNE, enter the community name assigned to the GNE in community name field on the MIB browser.
Note The community name is a form of authentication and access control. The community name of the NMS must match the community name assigned to the ONS 15310.
Step 2 If the SNMP "Get" (or other operation) is enabled for the ENE through a SOCKS proxy-enabled GNE, create a formatted string to enter in the MIB browser community name field. Refer to the following examples when constructing this string for your browser:
•Formatted community string input example 1:
allviews{192.168.7.4,,,net7node4}
If "allviews" is a valid community name value at the proxy-enabled SNMP agent (the GNE), the GNE is expected to forward the PDU to 192.168.7.4 at Port 161. The outgoing PDU will have "net7node4" as the community name. This is the valid community name for the ENE with address 192.168.7.4.
•Formatted community string input example 2:
allviews{192.168.7.99,,,enter7{192.168.9.6,161,,net9node6}}
If "allviews" is a valid community name value at the proxy-enabled GNE, the GNE is expected to forward the PDU to 192.168.7.99 at the default port (Port 161) with a community name of "enter7{192.168.9.6,161,,net9node6}". The system with the address 192.168.7.99 (the NE between the GNE and ENE) forwards this PDU to 192.168.9.6 at Port 161 (at the ENE) with a community name of "net9node6". The community name "enter7" is valid for the NE between the GNE and the ENE and "net9node6" is a valid community name for the ENE.
Step 3 Log into the NMS where the browser is installed to retrieve the network information from the ONS 15310.
Step 4 On this computer, go to Start and click the SNMP MIB browser application.
Step 5 In the Host and Community areas, enter the IP address of the GNE through which the ONS 15310 with the information to be retrieved can be reached.
Step 6 In the Community area, enter the community string as explained in Step 2.
Step 7 Return to your originating procedure (NTP).
Feedback
