|
|
This chapter describes the components required for operation, administration, and maintenance of the Cisco ONS 15200.
The Network Control Board (NCB) supervises, administers, and monitors the ONS 15200. In addition to controlling all of the ONS 15200 system Client Layer Interface Port (CLIP) modules, the NCB module collects information about system status, alarms, parameters, and actions on the internal data bus. See the "Alarms" section for a description of NCB alarms.
You can manage an ONS 15200 network using three different connection interfaces:
Figure 4-1 illustrates the three network management interface connections.
You can control the ONS 15200 system using the Subnetwork Manager (SNM) software package running on the NCB module located in the ONS 15252 MCU. Access the SNM through either the EIA/TIA-232 port or the Ethernet port on the front of the NCB module. Additionally, you can manage the ONS 15200 system externally using the Command Line Interface (CLI) software package described in the "Command Line Interface" section or using the Maintenance Manager (MM) software package described in the "Maintenance Manager" section. With the Internet, you can view the ONS 15200 system using the web-based interface described in the "Web-Based Interface" section. In addition, you can use SNMP and the Cisco Transport Manager (CTM) to have read-only access to the ONS 15200.
An internal data bus, also called a controller area network (CAN) bus, connects an NCB module to different CLIP modules of the ONS 15252 MCU. You can extend this data bus over several co-located network elements (ONS 15252 MCUs or ONS 15201 SCUs) to a larger logical unit. The ONS 15201 SCU uses the same data bus as the MCU. Normally one CAN bus connects all ONS 15200 equipment located at one site.
An overhead channel exists and is implemented as a base band modulation on the individual DWDM optical channels. Two end-points of a channel communicate using this low frequency signal, called QPP (Qeyton Proprietary Protocol). The QPP specification defines the physical and link layer protocols for communication.
Any CLIP module controlled by an NCB must not be more than two QPP hops away from that NCB. If the CLIP is further away from the NCB, you must install additional NCB modules.
Release 1.1 allows you to configure up to two active NCBs as managers of any CLIP in a network. To manage the CLIP, it must be no further than two CAN and two QPP hops away from the NCB. Any NCB in a network that is not provisioned as an active manager of a CLIP can still inventory the CLIP.
The EIA/TIA-232 port, located at the ONS 15252 MCU management access (MA) interface connector on the CIM, provides access to the SNM software running on the NCB module.
You only need the EIA/TIA-232 interface when you are setting the initial IP address of the NCB module. Two pins of the MA interface host the EIA/TIA-232 port; therefore, access the EIA/TIA-232 using the EIA/TIA-232 cable that is included with the ONS 15252 MCU. After you have set the IP address, you can communicate with the NCB module through the Ethernet port located on the front of the NCB.
Figure 4-2 illustrates EIA/TIA-232 interface access and Ethernet access to the ONS 15252 MCU.
After you have assigned an IP address to the NCB module, you can also send information to the NCB module by file transfer protocol (FTP). Set the EIA/TIA-232 interface to the parameters listed in Table 4-1. Set the terminal settings to ASCII (send line end with line feed).
The SNM software package Command Line Interface (CLI) is a simple, interactive tool that manages the ONS 15200 system.
The CLI interface resides on the NCB module and operates on the database server for the ONS 15200 system. The CLI interface has two modes of access for users—read-and-write access and read-only access. Users are separated into three categories: administrator, operator, and guest. Each category has different privileges:
To access the CLI interface, use the Ethernet port on the NCB module or the MA interface on the CIM module. MA interface access requires a EIA/TIA-232 cable.
The Maintenance Manager (MM) interactive software tool, installed on a laptop or PC, provides a local craft interface for the ONS 15200 system. The MM software provides access to the internal data bus at ONS 15252 MCUs or ONS 15201 SCUs. It also facilitates access to data from isolated ONS 15201 SCUs in the ONS 15200 network.
In addition to the required cabling, a laptop must have a controller area network (CAN) Personal Computer Memory Card International Association (PCMCIA) board to use the MM software package as a local craft interface.
Connect your MM-equipped computer to the ONS 15200 system through the MA port as shown in the following figures. Figure 4-2 shows the management access connection to an ONS 15252 MCU. Figure 4-3 shows the management access connection to an ONS 15201 SCU.
The web-based interface allows read-and-write access to the ONS 15200 system data from any valid IP address. The NCB module must have a defined IP address and you must log into the SNM software package running on the NCB module before accessing the web-based interface.
 |
Note The web-based interface does not function with Internet Explorer 4.0 or 5.0, Netscape Communicator 6.x, or Opera. |
The controller area network (CAN) bus is a serial communications protocol interface bus that allows you to connect several ONS 15200 systems to create a more powerful network element. The CAN bus supports distributed real-time, secure control. Figure 4-4 shows the two data bus extension ports on the ONS 15252 MCU. Figure 4-5 shows the two data bus extension ports located on the ONS 15201 SCU.
The simple network management protocol (SNMP) interface allows read-only access to the ONS 15200 system data. For SNMP access, the NCB module must have an assigned IP address and a valid community name. The SNMP interface supports simple network management protocol versions 1and 2c.
The Cisco Transport Manager (CTM) allows read-only access to the ONS 15200 system data. CTM Release 3.1 supports ONS 15200 Release 1.1.
In the ONS 15200 web-based interface, the Alarms screen shows all the active alarms recorded for each module installed in the network. Table 4-2 describes the CLIP module alarms, Table 4-3 describes alarm status parameters, and Table 4-4 defines the on-screen colors displayed next to the alarm status.
Table 4-2 Environment Parameter Definitions for Protected Channels
Table 4-3 Alarm Status Parameters
| Alarm Name | Definition |
|---|---|
| Miscellaneous alarms | |
Software attempted to write to an invalid location (autoclears after two seconds) |
|
Posted: Thu Apr 17 12:31:54 PDT 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
