Cisco ONS 15327 User Documentation, Release 1.0.1
Chapter 7, Network Management

Table Of Contents

Network Management

7.1 Simple Network Management Protocol

7.1.1 SNMP Basic Components

7.1.2 SNMP Support

7.1.3 SNMP Management Information Bases

7.1.4 SNMP Traps

7.1.5 SNMP Community Names

7.1.6 SNMP Remote Network Monitoring

7.2 Proxy ARP

7.3 IP Addressing and Subnets

7.3.1 Types of IP Addresses

7.3.2 Common IP Addressing Scenarios with the ONS 15327

7.4 IP Troubleshooting

7.5 Static Route Provisioning


7

Network Management


This chapter explains concepts related to network management with the Cisco ONS 15327. It includes Simple Network Management Protocol (SNMP), Proxy Address Resolution Protocol (ARP), IP addressing and subnets, IP troubleshooting, and static route provisioning.

7.1 Simple Network Management Protocol

SNMP is an application-layer communication protocol that allows network devices to exchange management information. SNMP enables network administrators to manage network performance, find and solve network problems, and plan network growth.

The ONS 15327 uses SNMP to provide asynchronous event notification to a Network Management System (NMS). ONS SNMP implementation uses standard Internet Engineering Task Force (IETF) MIBs to convey node-level inventory, fault, and performance management information for generic read-only management of DS-1, DS-3, SONET, and Ethernet technologies. SNMP allows limited management of the ONS 15327 by a generic SNMP manager like HP OpenView Network Node Manager (NNM) or Open Systems Interconnection (OSI) NetExpert.

The Cisco ONS 15327 supports SNMP Version 1 (SNMPv1) and SNMP Version 2c (SNMPv2c). Both versions share many features, but SNMPv2c includes additional protocol operations. This chapter describes both versions and explains how to configure SNMP on the ONS 15327. illustrates a basic network managed by SNMP.

Figure 7-1 Example of a basic network managed by SNMP

7.1.1 SNMP Basic Components

An SNMP-managed network consists of three primary components: managed devices, agents, and management systems. A managed device is a network node that contains an SNMP agent and resides on an SNMP-managed network. Managed devices collect and store management information and use SNMP to make this information available to management systems that use SNMP. Managed devices include routers, access servers, switches, bridges, hubs, computer hosts, and network elements like an ONS 15327.

An agent is a software module that resides in a managed device. An agent has local knowledge of management information and translates that information into a form compatible with SNMP. The SNMP agent gathers data from the MIB, which is the repository for device parameter and network data. The agent can also send traps, or notification of certain events, to the manager. illustrates these SNMP operations.

Figure 7-2 An SNMP agent gathering data from an MIB and sending traps to the manager

A management system, such as HP OpenView executes applications that monitor and control managed devices. Management systems provide the bulk of the processing and memory resources required for network management. One or more management systems must exist on any managed network. illustrates the relationship between the three key SNMP components.

Figure 7-3 Example of the primary SNMP components

7.1.2 SNMP Support

The ONS 15327 supports SNMP v1 and v2c traps and get requests. The SNMP MIBs in the ONS 15327 define alarms, traps, and status. Through SNMP, NMS applications can query a management agent using a supported MIB. The functional entities include Ethernet switches and SONET multiplexers.

Procedure: Set Up SNMP Support


Step 1 Display the CTC node view.

Step 2 Click the Provisioning > SNMP tabs.

Step 3 Click Create at the bottom of the screen.

The Create SNMP Trap Destination dialog box opens ( Figure 7-4).

For a description of SNMP traps, see the "SNMP Traps" section.

Figure 7-4 Setting up SNMP

Step 4 Type the IP address of your NMS in the IP Address field.

Step 5 Type the SNMP community name in the Community Name field.

For a description of SNMP community names, see the "SNMP Community Names" section.


Note   The community name is a form of authentication and access control. The community name assigned to the ONS 15327 is case-sensitive and must match the community name of the NMS.



Note   The default UDP port for SNMP is 162.


Step 6 Set the Trap Version field for either SNMPv1 or SNMPv2.

Refer to your NMS documentation to determine whether to use SNMP v1 or v2.

Step 7 Set your maximum traps per second in the Max Traps per Second field.


Note   The Max traps per second is the maximum number of traps per second that you want sent to the SNMP manager. If the field is set to 0, there is no maximum and all traps are sent.


Step 8 Click OK.

SNMP settings are now configured. To view SNMP information for each node, highlight the node IP address in the Trap Destination area on the Trap Destinations screen
( Figure 7-5).

Figure 7-5 Viewing trap destinations


7.1.3 SNMP Management Information Bases

A management information base (MIB) is a hierarchically-organized collection of information. Network-management protocols, such as SNMP, gain access to MIBs. MIBs consist of managed objects and are identified by object identifiers.

The ONS 15327 SNMP agent communicates with an SNMP management application using SNMP messages. Table 7-1 describes these messages.

Table 7-1 SNMP Message Types

Operation

Description

get-request

Retrieves a value from a specific variable

get-next-request

Retrieves the value following the named variable; this operation is often used to retrieve variables from within a table (1)

get-response

The reply to a get-request, get-next-request, get-bulk-request, or set-request sent by an NMS

get-bulk-request

Similar to get-next-request, but this operation fills the get-response with up to the max-repetition number of get-next interactions

trap

An unsolicited message sent by an SNMP agent to an SNMP manager indicating that an event has occurred


1. With this operation, an SNMP manager does not need to know the exact variable name. The SNMP manager searches sequentially to find the needed variable from within the MIB.

A managed object (sometimes called a MIB object) is one of any specific characteristic of a managed device. Managed objects consist of one or more object instances (variables.)

The ONS 15327 MIBs are included on the software CD that ships with the ONS 15327. Compile these MIBs in the following order. If you do not follow the order, one or more MIB files might not compile.

1 CERENT-GLOBAL-REGISTRY.mib

2 CERENT-TC.mib

3 CERENT-454.mib

4 CERENT-GENERIC.mib

If you cannot compile the ONS 15327 MIBs, call the Technical Assistance Center (TAC) at 1-877-323-7368.

Table 7-2 IETF Standard MIBs Implemented in the ONS 15327 SNMP Agent 

RFC#
Module Name
Title/Comments

1213

+1907

RFC1213-MIB,

SNMPV2-MIB

MIB-II from RFC1213 with enhancement from RFC1907 for v2

1493

BRIDGE-MIB

Bridge/Spanning Tree (SNMPv1 MIB)

1757

RMON-MIB

Remote monitoring Ethernet

2737

ENTITY-MIB

Entity MIB using SMI v2 (version II)

2233

IF-MIB

Interface evolution (enhances MIB-II)

2358

Etherlike-MIB

Ethernet-like interface (SNMPv2 MIB)

2495

DS1-MIB

DS-1/E1

2496

DS3-MIB

DS-3/E3

2558

SONET-MIB

SONET

2674

P-BRIDGE-MIB, Q-BRIDGE-MIB

P-Bridge and Q-Bridge MIB


7.1.4 SNMP Traps

The ONS 15327 can receive SNMP requests from a number of SNMP managers and send traps to ten trap receivers. The ONS 15327 generates all alarms and events as SNMP traps.

The ONS 15327 generates traps containing an object ID that uniquely identifies the alarm. An entity identifier uniquely identifies the entity that generated the alarm (slot, port, STS, VT, BLSR, STP, etc.). The traps give the severity of the alarm (critical, major, minor, event, etc.) and indicate whether the alarm is service affecting or non-service affecting. The traps also contain a date/time stamp that shows the date and time the alarm occurred. The ONS 15327 also generates a trap for each alarm when the alarm condition clears.

Each SNMP trap contains seven variable bindings ( ).

Table 7-3 SNMP Trap Variable Bindings 

Number
Name
Description

1

cerentGenericAlarmTable

This table holds all the current raised alarms. When an alarm is raised, it appears as a new entry in the table. When an alarm is cleared, it is removed from the table and all the subsequent entries move up by one row.

2

cerentGenericAlarmIndex

This variable uniquely identifies each entry in an alarm table. When an alarm in the alarm table clears, the alarm indexes changes for each alarm located subsequent to the cleared alarm.

3

cerentGenericAlarmObjectType

This variable provides the entity type that raised the alarm. The NMS should use this value to decide which table to poll for further information about the alarm.

4

cerentGenericAlarmSlotNumber

This variable indicates the slot of the object that raised the alarm. If a slot is not relevant to the alarm, the slot number is zero.

5

cerentGenericAlarmPortNumber

This variable provides the port of the object that raised the alarm. If a port is not relevant to the alarm, the port number is zero.

6

cerentGenericAlarmLineNumber

This variable provides the object line that raised the alarm. If a line is not relevant to the alarm, the line number is zero.

7

cerentGenericAlarmObjectIndex

Every alarm is raised by an object entry in a specific table. This is the index of the objects in each table; if the alarm is interface related, this is the index of the interfaces in the interface table.

8

cerentGenericAlarmType

This variable provides the exact type of the alarm.

9

cerentGenericAlarmState

This variable specifies alarm severity and service-affecting status. Severities are minor, major and critical. Service- affecting statuses are service-affecting and non-service-affecting.

10

cerentGenericAlarmTimeStamp

This variable gives the time when the alarm occurred. The value is the number of the ticks that has lapsed since 1/1/1970.


The ONS 15327 supports the generic and IETF traps listed in .

Table 7-4 Traps Supported in the ONS 15327

Trap
From RFC#
Description

ColdStart

RFC1213-MIB

Agent up cold start

WarmStart

RFC1213-MIB

Agent up warm start

AuthenticationFailure

RFC1213-MIB

Community string did not match

NewRoot

RFC1493/

BRIDGE-MIB

Sending agent is the new root of the spanning tree

TopologyChange

RFC1493/

BRIDGE-MIB

A port in a bridge has changed from Learning to Forwarding or Forwarding to Blocking

EntConfigChange

RFC2037/

ENTITY-MIB

entLastChangeTime value has changed

ds1xLineStatusChange

RFC2495/

DS1-MIB

A dsx1LineStatusChange trap is sent when the value of an instance dsx1LineStatus changes. The trap can be used by an NMS to trigger polls. When the line status change results from a higher-level line status change (ex. DS-3), no traps for the DS-1 are sent.

dsx3LineStatusChange

RFC2496/

DS3-MIB

A dsx3LineStatusLastChange trap is sent when the value of an instance of dsx3LineStatus changes. It can be used by an NMS to trigger polls. When the line status change results in a lower-level line status change (ex. DS-1), no traps for the lower-level are sent.

risingAlarm

RFC1757/

RMON-MIB

The SNMP trap that is generated when an alarm entry crosses the rising threshold and the entry generates an event that is configured for sending SNMP traps.

fallingAlarm

RFC1757/

RMON-MIB

The SNMP trap that is generated when an alarm entry crosses the falling threshold and the entry generates an event that is configured for sending SNMP traps.


7.1.5 SNMP Community Names

You can provision community names for all SNMP requests from the SNMP Trap Destination window in CTC (see the "Set Up SNMP Support" section). In effect, SNMP considers valid any request that uses a community name matching a community name on the list of provisioned SNMP trap destinations. Otherwise, SNMP considers the request invalid and drops it.

If an SNMP request contains an invalid community name, the request is silently dropped and the MIB variable, snmpInBadCommunityNames, is incremented. All MIB variables managed by the agent grant access to all SNMP requests containing a validated community name.

7.1.6 SNMP Remote Network Monitoring

The ONS 15327 incorporates Remote Network Monitoring (RMON) to allow network operators to monitor the ONS 15327 E10/100-4 cards. This feature is not apparent to the typical CTC user, because RMON interoperates with an NMS. However, with CTC you can provision the RMON alarm thresholds (see the "SNMP Remote Network Monitoring" section). CTC also monitors the five RMON groups implemented by the ONS 15327.

The ONS 15327 RMON implementation is based on the IETF-standard MIB Request for Comment (RFC)1757. The ONS 15327 implements five groups from the standard MIB: Ethernet Statistics, History Control, Ethernet History, Alarm, and Event.

7.1.6.1 Ethernet Statistics Group

The Ethernet Statistics group contains the basic statistics for each monitored subnetwork in a single table named etherstats.

7.1.6.2 History Control Group

The History Control group defines sampling functions for one or more monitor interfaces. RFC 1757 defines the historyControlTable.

7.1.6.3 Ethernet History Group

RFC 1757 defines the etherHistoryTable. The ONS 15327 implements the etherHistoryTable as defined in RFC 1757, within the bounds of the historyControlTable.

7.1.6.4 Alarm Group

The Alarm group consists of a single alarm table. This table provides the network performance alarm thresholds for the network management application. With CTC, you can provision the thresholds in the table.

7.1.6.5 Event Group

The Event group consists of two tables, eventTable and logTable. The eventTable is read-only. The ONS 15327 implements the logTable as specified in RFC 1757.

7.2 Proxy ARP

Proxy Address Resolution Protocol (ARP) enables a LAN-connected gateway ONS 15327 to automatically handle ARP requests for remote non-LAN ONS 15327s connected through the data communications channel (DCC) to the gateway ONS 15327. Proxy ARP requires no manual configuration and eliminates the need for you to set up static host routes for the PC running CTC.

In Proxy ARP, a single LAN-connected ONS 15327 stands in (proxies) for remote ONS 15327s. If a device on the LAN sends an ARP request intended for one of the DCC-connected ONS 15327s, the gateway ONS 15327 proxies or returns its own MAC address to the LAN device. The LAN device then sends the datagram intended for the remote ONS 15327 to the MAC address of the proxy ONS 15327. The proxy ONS 15327 forwards this data to the remote 15327 using its own ARP table. The ARP table matches IP addresses with the MAC IDs of remote ONS 15327s and is built through internal Open Shortest Path First (OSPF) routing protocol. illustrates proxy ARP.

Figure 7-6 An ONS 15327 network using Proxy ARP


Note   Proxy ARP is automatic and requires no user input.


7.3 IP Addressing and Subnets

This section provides IP addressing guidelines for the ONS 15327. The IP addressing information includes IP addressing classes and IP configuration scenarios.

7.3.1 Types of IP Addresses

You usually encounter Class A, B, or C IP addresses. Class D and E exist, but D is used for multicasts and E is experimental. The different classes primarily refer to how the addresses can be used and how many subnets and hosts are available for use in the network.

Each network needs its own, unique network number and each host within a network needs a unique host number.

Subnetting maximizes the number of networks available within a range (class) of addresses. The number of subnets you can configure depends on the address class.

7.3.1.1 Class A Addresses and Subnets

In a Class A IP address, the first eight bits are the network ID, and the last 24 bits are the host ID. The first bit of a network address is 0 when the number is converted to binary, for example, 5.xxx.xxx.xxx = 00000101 (5). The maximum number of network addresses that can be derived in Class A is 126; the maximum number of hosts is 16,777,214. The address 0.0.0.0 is reserved as the default route and 127.xxx.xxx.xxx is reserved as the loopback address. The natural mask is 255.0.0.0 and the available addresses are 1.xxx.xxx.xxx through 126.xxx.xxx.xxx.

7.3.1.2 Class B Addresses and Subnets

In a Class B IP address, the first 16 bits are the network ID and the last 16 bits are the host ID. The first two bits of a network address begin with 10 when the number is converted to binary. For example, 128.x.x.x = 10000000. The maximum number of network addresses that can be derived from Class B is 16,384; the maximum number of hosts is 65,534. The natural mask is 255.255.0.0 and the available addresses are 128.0.xxx.xxx through 191.255.0.0.

7.3.1.3 Class C Addresses and Subnets

In a Class C IP address, the first 24 bits are the network ID and the last eight bits are the host ID. The first two bits of a network address begin with 11 when the number is converted to binary. For example, 192.x.x.x = 11000000. The maximum number of network addresses that can be derived from Class C is 2,097,152; the maximum number of hosts is 254. The natural mask is 255.255.255.0 and the available addresses are 192.0.0.xxx through 223.255.255.xxx.

7.3.2 Common IP Addressing Scenarios with the ONS 15327

ONS 15327 IP addressing generally has seven common IP addressing scenarios or configurations. Refer to the following illustrations and checklists when setting IP addresses and configuring subnets. You must be able to answer yes to each checklist question to be sure that all IP addressing guidelines are met. The following figures illustrate these seven scenarios and provide an IP checklist for each scenario.


Note   LAN devices, do not need host routes to communicate with other ONS 15327s on the same DCC-connected subnet.


7.3.2.1 IP Addressing Scenario 1

In IP addressing scenario 1, the ONS 15327s and CTC are on the same subnets and all of the ONS 15327s attach to LAN A.

A scenario checklist follows the scenario example. If you answer no to any of the questions, see the "IP Troubleshooting" section.

Figure 7-7 IP Addressing Scenario 1

Procedure: IP Checklist for Scenario 1

Are the IP addresses of ONS 15327s #1, #2, and #3 on the same IP subnet?

Are all of the IP addresses unique?

Can the workstation running CTC ping itself?

Is there link integrity between the CTC workstation and the hub/switch?

Does the XTC RJ-45 LAN port have link integrity? Do all ONS 15327s and the hub/switch have link integrity?

Is the hub/switch port for all ONS 15327s set for 10 Mbps half-duplex?

Can you ping ONS 15327 #1, #2, and #3 from the CTC workstation?

Do you have a Netscape Navigator or Internet Explorer browser installed? (A Microsoft Windows environment must run Netscape Navigator version 4.73 or higher, or Microsoft Internet Explorer 4.0 or higher. A Sun Solaris environment needs Netscape Navigator version 4.61 or higher.)

Do you have the Java plug-in installed (version 1.2.2 or higher for both Microsoft Windows and Sun Solaris)?

Do you have the correct Java policy file installed? (The correct Java policy file version is on the CTC software CD that ships with the ONS 15327.)

Are you using the browser to connect to the IP address of the ONS 15327?

Can you log into the ONS 15327?

7.3.2.2 IP Addressing Scenario 2

In IP addressing scenario 2, the ONS 15327s and CTC are on different subnets and all of the ONS 15327s attach to LAN B.

A scenario checklist follows the scenario example. If you answer no to any of the questions, see the "IP Troubleshooting" section.

Figure 7-8 IP Addressing Scenario 2

Procedure: IP Checklist for Scenario 2

Are the IP addresses of the CTC workstation and the router's A interface on the same subnet?

Can the workstation running CTC ping itself?

Is the workstation's default gateway set to the same IP address as the router's A interface?

Are the IP addresses of the ONS 15327 #1, #2, and #3 on the same subnet as the router's B interface?

Are all of the IP addresses unique?

Is the default router of the ONS 15327 #1, #2, and #3 set to the IP address of the router's B interface?

Is there link integrity between the workstation and the hub/switch?

Is there link integrity between the XTC RJ-45 LAN port of all nodes and the hub/switch(es)?

Is there link integrity between the router ports and their hubs/switches?

Are the hub/switch ports on all ONS 15327s set for 10 Mbps half-duplex?

Can you ping ONS 15327 #1, #2, and #3 from the CTC workstation?

Do you have a Netscape Navigator or Internet Explorer browser installed? (A Microsoft Windows environment must run Netscape Navigator version 4.73 or higher, or Microsoft Internet Explorer 4.0 or higher. A Sun Solaris environment needs Netscape Navigator version 4.61 or higher.)

Do you have the Java plug-in installed (version 1.2.2 or higher for both Microsoft Windows and Sun Solaris)?

Do you have the correct version of the Java policy file installed? (The correct version of the Java policy file is on the CTC software CD that ships with the ONS 15327.)

Are you using the browser to connect to the IP address of the ONS 15327?

Can you log into the ONS 15327?

7.3.2.3 IP Addressing Scenario 3

In IP addressing scenario 3, CTC and all the ONS 15327s are on the same subnet. ONS 15327 #1 is attached to LAN A and ONS 15327 #2 and #3 are at remote sites.

A scenario checklist follows the scenario example. If you answer no to any of the questions, see the "IP Troubleshooting" section.

Figure 7-9 IP Addressing Scenario 3

Procedure: IP Checklist for Scenario 3

Are the workstation IP address and the IP addresses of all ONS 15327s on the same IP subnet?

Are all of the IP addresses unique?

Can the workstation running CTC ping itself?

Are host routes configured on the CTC workstation for each remote node (ONS 15327 #2 and #3)?

Is there link integrity between the CTC workstation and the hub/switch?

Is there link integrity between the XTC RJ-45 port and the hub/switch?

Is the hub/switch port set for 10 Mbps half-duplex?

Can you ping ONS 15327 #1 from the CTC workstation?

Are the optical trunk ports in service on all nodes?

Is the DCC enabled for all optical trunk ports that are in service?

Can you ping the remote nodes (ONS 15327 #2 and #3) from the CTC workstation?

Do you have a Netscape Navigator or Internet Explorer browser installed? (A Microsoft Windows environment must run Netscape Navigator version 4.73 or higher, or Microsoft Internet Explorer 4.0 or higher. A Sun Solaris environment needs Netscape Navigator version 4.61 or higher.)

Do you have the Java plug-in installed (version 1.2.2 or higher for both Microsoft Windows and Sun Solaris)?

Do you have the correct Java policy file installed? (The correct Java policy file version is on the CTC software CD that ships with the ONS 15327.)

Are you using the browser to connect to the IP address of the ONS 15327?

Can you log into the ONS 15327?

7.3.2.4 IP Addressing Scenario 4

In IP addressing scenario 4, CTC and ONS 15327 #1 are on the same subnet but ONS 15327 #2 and # 3 are on different subnets. ONS 15327 #1 is attached to LAN A and ONS 15327 #2 and #3 are at remote sites.

A scenario checklist follows the scenario example. If you answer no to any of the questions, see the "IP Troubleshooting" section.

Figure 7-10 IP Addressing Scenario 4

Procedure: IP Checklist for Scenario 4

Are the CTC workstation IP address and the ONS 15327 #1 IP address on the same subnet?

Are the IP addresses of ONS 15327 #1, #2, and #3 on different subnets?

Are all of the IP addresses unique?

Can the workstation running the CTC ping itself?

Is the CTC workstation's default gateway set to the same IP address as ONS 15327 #1?

Is there link integrity between the workstation and the hub/switch?

Is there link integrity between the XTC RJ-45 LAN port and the hub/switch?

Is the hub/switch port set for 10 Mbps half-duplex?

Can you ping ONS 15327 #1 from the CTC workstation?

Are the optical trunk ports in service on all nodes?

Is the DCC enabled for all optical trunk ports that are in service?

Can you ping the remote nodes (ONS 15327 #2 and #3) from the CTC workstation?

Do you have a Netscape Navigator or Internet Explorer browser installed? (A Microsoft Windows environment must run Netscape Navigator version 4.73 or higher, or Microsoft Internet Explorer 4.0 or higher. A Sun Solaris environment needs Netscape Navigator version 4.61 or higher.)

Do you have the Java plug-in installed (version 1.2.2 or higher for both Microsoft Windows and Sun Solaris)?

Do you have the correct Java policy file installed? (The correct Java policy file version is on the CTC software CD that ships with the ONS 15327.)

Are you using the browser to connect to the IP address of the ONS 15327?

Can you log into the ONS 15327?

7.3.2.5 IP Addressing Scenario 5

In IP addressing scenario 5, CTC and each of the ONS 15327s are on different subnets. ONS 15327 #1 is attached to LAN A and ONS 15327 #2 and #3 are at remote sites.

A scenario checklist follows the scenario example. If you answer no to any of the questions, see the "IP Troubleshooting" section.

Figure 7-11 IP Addressing Scenario 5

Procedure: IP Checklist for Scenario 5

Are the IP address of the CTC workstation and the IP address of the router's A interface on the same subnet?

Can the workstation running the CTC ping itself?

Is the workstation's default gateway set to the IP address of the local router A interface?

Are the IP addresses of ONS 15327 #1, #2, and #3 on different subnets?

Are all of the IP addresses unique?

Is the default router of the ONS 15327 #1 set to the same IP address as the router's B interface?

Does ONS 15327 #1 have static routes pointing to the CTC workstation?

Does the router have host routes configured for all the remote ONS 15327s?

Is there link integrity between the workstation and the hub/switch?

Is there link integrity between the XTC RJ-45 LAN ports and the hub/switch?

Is there link integrity between the router ports and their hubs/switches?

Is the hub/switch port for ONS 15327 #1 set for 10 Mbps half-duplex?

Can you ping ONS 15327 #1 from the CTC workstation?

Are the optical trunk ports in service on all nodes?

Is the DCC enabled for all optical trunk ports that are in service?

Can you ping the remote nodes (ONS 15327 #2 and #3) from the CTC workstation?

Do you have a Netscape Navigator or Internet Explorer browser installed? (A Microsoft Windows environment must run Netscape Navigator version 4.73 or higher, or Microsoft Internet Explorer 4.0 or higher. A Sun Solaris environment needs Netscape Navigator version 4.61 or higher.)

Do you have the Java plug-in installed (version 1.2.2 or higher for both Microsoft Windows and Sun Solaris)?

Do you have the correct version of the Java policy file installed? (The correct version of the Java policy file is on the CTC software CD that ships with the ONS 15327.)

Are you using the browser to connect to the IP address of the ONS 15327?

Can you log into the ONS 15327?

7.3.2.6 IP Addressing Scenario 6

In IP addressing scenario 6, all the ONS 15327s are on the same subnet and CTC is on a different subnet. ONS 15327 #1 is attached to LAN A and ONS 15327 #2 and #3 are at remote sites.

A scenario checklist follows the scenario example. If you answer no to any of the questions, see the "IP Troubleshooting" section.

Figure 7-12 IP Addressing Scenario 6

Procedure: IP Checklist for Scenario 6

Is the IP address of the CTC workstation and the router's A interface on the same subnet?

Can the workstation running CTC ping itself?

Is the workstation's default gateway set to the same IP address as the local router's A interface?

Are the IP addresses of ONS 15327 #1, #2, and #3 on the same subnet as the local router B interface?

Are all of the IP addresses unique?

Is the default router of ONS 15327 #1 set to the IP address of the router's B interface?

Is there link integrity between the workstation and the hub/switch?

Is there link integrity between the XTC RJ-45 LAN port and the hub/switch?

Is there link integrity between the router ports and their hubs/switches?

Is the hub/switch port for ONS 15327 #1 set for 10 Mbps half-duplex?

Can you ping ONS 15327 #1 from the CTC workstation?

Are the optical trunk ports in service on all nodes?

Is the DCC enabled for all optical trunk ports that are in service?

Can you ping the remote nodes (ONS 15327 #2 and #3) from the CTC workstation?

Do you have a Netscape Navigator or Internet Explorer browser installed? (A Microsoft Windows environment must run Netscape Navigator version 4.73 or higher, or Microsoft Internet Explorer 4.0 or higher. A Sun Solaris environment needs Netscape Navigator version 4.61 or higher.)

Do you have the Java plug-in installed (version 1.2.2 or higher for both Microsoft Windows and Sun Solaris)?

Do you have the correct Java policy file installed? (The correct version of the Java policy file is on the CTC software CD that ships with the ONS 15327.)

Are you using the browser to connect to the IP address of the ONS 15327?

Can you log into the ONS 15327?

7.3.2.7 IP Addressing Scenario 7

In IP addressing scenario 7, CTC #1 and #2 and all ONS 15327s are on the same IP subnet. ONS 15327 #1 and CTC #1 are attached to LAN A. ONS 15327 #2 and CTC #2 are attached to LAN B.

A scenario checklist follows the scenario example. If you answer no to any of the questions, see the "IP Troubleshooting" section.

Figure 7-13 IP Addressing Scenario 7

Procedure: IP Checklist for Scenario 7

Are the two CTC workstation IP addresses and all the ONS 15327 IP addresses on the same subnet?

Are all of the IP addresses unique?

Does ONS 15327 #1 have static routes pointing to CTC workstation #1?

Does ONS 15327 #2 have static routes pointing to CTC workstation #2?

Can the workstation running CTC ping itself?

Is there link integrity between the workstation and the hub/switch?

Does the XTC RJ-45 LAN port have link integrity to the hub/switch?

Is the hub/switch port set for 10 Mbps half-duplex?

Can you ping ONS 15327 #1 from the CTC workstation?

Are the optical trunk ports in service on all nodes?

Is the DCC enabled for all optical trunk ports that are in service?

Can you ping the remote nodes (ONS 15327 #2 and #3) from the CTC workstation?

Do you have a Netscape Navigator or Internet Explorer browser installed? (A Microsoft Windows environment must run Netscape Navigator version 4.73 or higher, or Microsoft Internet Explorer 4.0 or higher. A Sun Solaris environment needs Netscape Navigator version 4.61 or higher.)

Do you have the Java plug-in installed (version 1.2.2 or higher for both Microsoft Windows and Sun Solaris)?

Do you have the correct version of the Java policy file installed? (The correct version of the Java policy file is on the CTC software CD that ships with the ONS 15327.)

Are you using the browser to connect to the IP address of the ONS 15327?

Can you log into the ONS 15327?

7.4 IP Troubleshooting

Look for solutions in the following section if you answered no to any of the questions in the IP scenarios checklists or you encounter any of the IP problems listed below.

Table 7-5 IP Troubleshooting Solutions 

Problem
Solution

The workstation running CTC cannot ping itself.

Verify the IP address of your workstation.

If the workstation cannot ping itself, a problem exists with the
workstation. Contact the network administrator.

No link integrity exists between the workstation and the hub/switch.

Verify that you are using a straight-through Ethernet cable

Verify that a link-integrity indicator exists for the port on the hub/switch.

Change the Ethernet cable.

Verify that the hub/switch is enabled.

Verify wire-wrap connection.

Contact the network administrator.

Link integrity does not exist between the hub/switch and the ONS 15327 RJ-45 port.

Verify that you are using a cross-over Ethernet cable.

Change the Ethernet cable.

Verify that the hub/switch port is enabled.

Verify wire-wrap connection.

Contact the network administrator.

You do not know if the hub/switch port that connects to the ONS 15327(s) is properly set at 10 Mbps half-duplex

Contact the network administrator.

Although the workstation is capable of pinging other devices successfully, it cannot ping a specific ONS 15327

Check the routing of the workstation, router, and any CTC static routes.

Check that optical card ports are in service and DCC-enabled.

The correct Java policy file was not installed or it was installed before the Java plug-in.

The policy file and installation instructions are on the software CD that ships with the ONS 15327.

Call the Cisco Technical Assistance Center (TAC) at 1-877-323-7368.

You do not know whether the IP addresses of ONS 15327s #X, #Y, and #Z lie on the same or different subnets.

Contact the network administrator.

You do not know if the default router entry for the ONS 15327 correctly matches the IP address of the router interface connected to the ONS 15327 LAN segment.

Using CTC, verify that the default router configuration entered on the ONS 15327 matches the verified IP address of the router's B interface.

See the "Static Route Provisioning" section.

Is there link integrity between the ports on the router and the hubs/switches?

Contact the network administrator to verify the IP address of the router's interface B.

Link integrity does not exist between the router ports and the hub/switches.

Contact the network administrator.

You do not know if the optical trunk ports on the ONS 15327s are in service.

Use CTC to verify that trunk ports are in service:

Click the Provisioning > Line tabs.

Click the Status column.

Verify that the ports are set to In Service.

You do not know if the DCC is enabled on in-service optical trunk ports.

Use CTC to verify that DCC is enabled:

Display the card-level view of the optical card.

Click the Provisioning > Sonet DCC tabs.

Verify that the optical cards are listed.

The web browser will not connect to the ONS 15327, but it connects successfully to other sites.

Verify that the workstation can ping the ONS 15327.

The workstation is unable to ping remote ONS 15327s.

Check the routing of the ONS 15327 and the workstation.


7.5 Static Route Provisioning

The ONS 15327 uses CTC to provision static network routes in ONS 15327 network elements (NE). Static routes make it possible to have multiple CTC sessions, with different destination IP addresses, on a network of ONS 15327s that all lie on the same subnet. For example, a Network Operations Center (NOC) can remotely monitor an ONS 15327 through CTC at the same time that an on-site employee is logged into an ONS 15327 on the network with a separate CTC session. Static routes also allow workstations to connect to ONS 15327s through routers.

To achieve CTC connectivity, interconnected ONS 15327s use the Section Data Communications Channel (SDCC) for communication. SDCC communicates using a combination of the Open Shortest Path First (OSPF) routing protocol and manually-entered static routes.

CTC adds static route entries to the NE's routing table. The NE routing table information is advertised to the other ONS 15327s connected by DCCs.

To add static route provisioning on the ONS 15327, you must change the configuration of CTC workstations. An example is given below. For other typical IP addressing scenarios, see the "Common IP Addressing Scenarios with the ONS 15327" section. These scenarios contain additional details about router and CTC workstation setup that support the example.

Procedure: Static Routing to a Router-Linked Workstation

This procedure provisions a static route to connect an ONS 15327 through a router and to a CTC workstation. All networks in this example use a 24-bit subnet mask. The CTC workstation IP address is 192.168.100.20, the ONS 15327 IP address is 192.168.90.11, and the IP address of the router port on the same segment as the ONS 15327 is 192.168.90.1.


Step 1 Display the CTC node view.

Step 2 Click the Provisioning > Network tabs.

Step 3 Under Static Routes, click Create.

The Create Static Route dialog box opens ( Figure 7-14 ).

Figure 7-14 Creating a static route

Step 4 In the Destination field, enter the IP address of the workstation running CTC (in this example 192.168.100.20.)

Step 5 In the Mask field, enter a 32-bit subnet mask to designate that this is a host route (in this example, 255.255.255.0).

Step 6 In the Next Hop field, enter the IP address of the router port (in this example, 172.20.222.1).

Step 7 In the Cost field enter the number of hops (in this example, 2).

To determine cost, count the number of hops between the ONS 15327 and the CTC workstation. In this example, the count is two, one hop from the ONS 15327 to the router and a second hop from the router to the CTC workstation.

Step 8 Click OK.

Step 9 To confirm that you have successfully completed the procedure, view the static route in the Static Route Window (show in ) or ping the node.

Figure 7-15 Viewing static route information


Note   The Default Router entry for the ONS 15327 should be the router port (in this example, 172.20.222.1).