|
|
The Cisco 7200/7400 Series Manager software builds upon the Cisco Element Management Framework (CEMF) using the CEMF Software Development Toolkit (SDK). CEMF is the element management layer of the Cisco Service Management (CSM) system and provides a highly scalable framework designed to support carrier-class element managers across Cisco service-provider product lines with network event management.
Element management tasks can include equipment provisioning, fault monitoring, interface configuration, and the gathering and display of interface performance statistics.
This chapter covers the following information:
Cisco 7200/7400 Series Manager manages two types of objects:
Fault, Configuration, Accounting, Performance, and Security (FCAPS) windows are accessible on both physical and logical Cisco 7200/7400 Series Manager objects, in the form of FCAPS menu options that appear when you right-click any Cisco 7200/7400 Series Manager object. FCAPS functionality provides you with a complete management interface for all Cisco 7200/7400 Series Manager features.
This section covers the following topics:
Table 1-1 lists all physical objects created in Cisco 7200/7400 Series Manager and the management functions performed on each object.
Table 1-1 Physical Objects and Management Functions
| Physical Object | Management Functions |
|---|---|
No management can be performed on a shelf. Provides access to chassis management functions. |
|
Chassis—The Cisco Edge Router hardware frame, which houses all subchassis objects (modules). |
|
Processor—There can be only one or two processors in a Cisco Edge Router chassis. The primary processor is the CPU or "brains" of the Cisco Edge Router. The second GRP is redundant. |
|
Port adapters—There are various types of port adapters (ATM, Ethernet, POS, DS3) within a Cisco chassis. Each holds a given number of physical interfaces (ports). |
|
Physical Interfaces—Each port adapter has one or more physical interfaces (ports), whose type is equivalent to the type of port adapter the interface resides on. Each physical interface can support multiple technologies (see "Physical Interfaces and Technologies" section). The port adapter type determines what specific technologies are on the interfaces. |
|
Supporting Modules—Additional subchassis cards and modules: I/O cards, and AC or DC power supply modules. |
The physical objects and interfaces in the preceding table can be traced as follows:
For more details on hierarchies within CEMF and Cisco 7200/7400 Series Manager, see the "Views" section.
 |
Note Physical objects contained within a chassis are often referred to as subchassis objects or modules. |
Figure 1-1 through Figure 1-7 provide examples of each Cisco 7200/7400 Series Manager supported chassis and the physical objects within each chassis.
The Cisco 7206 and 7206 VXR chassis support the following components:
The rear of the Cisco 7204 VXR router provides access to the network processing engine and up to two power supplies (see Figure 1-6).
The Cisco 7204 VXR chassis supports the following components:
The 7401 chassis contains only one port adapter slot.
A Cisco 7200/7400 chassis contains three types of supporting modules:
 |
Tip No supporting modules appear in the Cisco 7200/7400 Series Manager view. To see these objects, and to launch any management menus for them, you must be in the Physical view. |
Cisco 7200/7400 Series Manager supports five types of port adapters:
Each of these port adapters has respectively named physical interfaces (or ports). For example, the ATM port adapter has ATM physical interfaces, the POS port adapter has POS physical interfaces, and so on. Each physical interface type can support multiple layered technologies.
A physical interfaces is modeled as an object below the parent port adapter.1-8
As mentioned before, the type of port adapter characterizes the type of physical interface; for example, an ATM port adapter supports only ATM interfaces. However, multiple technologies can be supported on that physical interface. For example, ATM physical interfaces can support the following technologies:
Table 1-2 outlines each physical interface and the technologies it supports. Also included are the various FCAPS-based windows that are applicable to each physical interface and technology. For example, if you want to configure an ATM interface, look in the table under ATM, and you will notice that four technologies apply: Generic, ATM, SONET, and IP. This means that to completely configure an ATM interface, you must open the configuration windows for each of these four technologies and configure the fields.
Table 1-2 Physical Interfaces, Technologies Supported, and Related Windows
| Physical Interfaces | Technologies Supported and Related Windows |
|---|---|
Generic—Configuration, Status, Performance |
|
Generic—Configuration, Status, Performance |
There are two types of logical objects:
Table 1-3 describes the management functions for Layer 3 QoS logical objects, and Table 1-4 describes the management functions for ATM logical objects.
Table 1-3 Layer 3 QoS Logical Objects
Cisco 7200/7400 Series Manager views can be accessed by clicking the Viewer icon in the CEMF launchpad. These views appear in the frame on the left side of the window when you open the Viewer.
Cisco 7200/7400 Series Manager views (see the "Cisco 7200/7400 Series Manager View" section) model hierarchical relationships between objects, both physical and logical. Objects are organized into different views and can exist in multiple views simultaneously by reference. Each object can have a number of parent and child objects. You can access Cisco 7200/7400 Series Manager objects by navigating through one of the views to find the object. You can navigate through views by expanding text. Click the plus sign (+) next to any object to expand text. A minus sign (-) next to an object indicates there is no more text to expand. Each view represents a different way of containing and grouping objects.
Cisco 7200/7400 Series Manager adds specific views to the standard views supplied by CEMF. The standard CEMF views are the Physical, Network, and Generic Object views (for more information on these views, refer to the Cisco Element Management Framework User Guide).
When objects are contained underneath a particular view, a number in parenthesis appears to the right of the view, indicating the number of top-level objects contained in it. In Figure 1-8, there are no top-level objects underneath any view.
Use the CiscoERManager view for most management functions, because it is the only view that provides a chassis map.
This section covers the following topics:
The Cisco 7200/7400 Series Manager view provides chassis maps, which are graphical representations of the chassis and its contents. You can access management menus on objects within chassis maps. To display a chassis map, click on the shelf object for the chassis you want to view.
The Component Managed view contains all objects within the CEMF system. For example, if you have two types of element management software installed in CEMF—Cisco Gigabit Switch Router (GSR) and the Cisco 7200/7400 Series Manager software—information for both GSR and Cisco 7200/7400 Series Manager is displayed in the Component Managed view.
It is not recommended that you work within the Component Managed view, unless you have multiple element management software (EMS) installed.
The Component Managed view and Physical view have the same basic hierarchical structure.
The Layer 3 Qos view displays only Layer 3 QoS objects within Cisco 7200/7400 Series Manager, such as the following:
You can work within this view to create and configure access lists, and CAR, by accessing the respective Cisco 7200/7400 Series Manager menus. All of these objects are then listed within this view.
The Network view displays all network devices within their relevant networks and subnets. The CEMF auto-discovery system uses this view to calculate which devices have already been added to the system to prevent it from trying to discover the same device multiple times. For details on auto-discovery, see the "Auto Discovery" section.
Objects in the Physical view are ordered according to their relative physical location. The relationships defined in this view are physical containment relationships, meaning that each object is defined according to which object it is contained within. For example, a shelf is located under a site; a chassis is contained under a shelf; and GRPs, port adapters, and supporting modules are contained within a chassis. See Figure 1-1 for an overview of the structure of the Physical view.
The Generic Objects view contains all deployed CEMF generic objects, such as sites, regions, and bays. This view is used primarily to find any CEMF generic objects. This view also contains all Simple Network Management Protocol (SNMP) objects, such as SNMP agents and SNMP proxied objects.
Cisco 7200/7400 Series Manager object states reflect the life cycle of an object. Whatever stage the object is in at any given time is reflected in the state type. The state of an object can change frequently, depending on what actions are being performed on the object. Cisco 7200/7400 Series Manager assigns a state to all objects. This state appears at the bottom left corner of each FCAPS window for a selected object. The two most common object states are:
For example, when you deploy a port adapter in Cisco 7200/7400 Series Manager, the initial state of the port adapter is decommissioned. You would then commission the port adapter to begin active management (for details on how to commission a module, see the "Commissioning or Decommissioning a Module" section). When you commission the port adapter, it goes through two transitory states: discovery, and then commissioning. The commissioning process determines which state to move the object into (typically Normal). This example reflects the basic process of deploying and commissioning an object.
Certain states ripple down from one object to all objects under it. For example, if you decommission a chassis, all subchassis objects are also decommissioned. If you enable performance logging on a port adapter, all interfaces on the port adapter are also enabled.
By default, FCAPS windows refresh at a rate dependent on the window type. For example, inventory windows are refreshed at a rate lower than that of performance windows. The average refresh rate is every 30 seconds.
This section covers the following topics:
The normal state indicates that an object is operational. When an object enters the normal state, Cisco 7200/7400 Series Manager performs heartbeat polling on the object to determine whether or not it is present and to determine its current state.
The decommissioned state indicates that an object is not managed. When you manually deploy an object, it is placed into a decommissioned state.
|
Tip Initially, deployed objects are decommissioned to give you the option to manage the object or not. If you want to manage the object, you need to commission it. |
The following occur on a decommissioned object:
Decommission buttons are located in chassis, module, and interface configuration windows. When you decommission an object, the state of any children of that object also changes to decommissioned. For example, if you decommission a chassis, all objects within that chassis (GRP card, port adapters, interfaces, connections) are decommissioned. If you decommission a port adapter, all interfaces and connections on that port adapter are decommissioned as well, and so on.
Certain object states in Cisco 7200/7400 Series Manager are temporary and exist only for a short time while a process is being performed. The following states are transient:
Additional states that Cisco 7200/7400 Series Manager can apply to objects are:
If a module becomes nonoperational, it moves into the errored state. In the errored state, performance polling (if activated) is stopped; however, heartbeat polling (which polls an object every five minutes to verify its existence and current state) continues, until the device responds positively to a heartbeat request. When the module is contactable again, it responds positively to heartbeat requests, and then moves back into the previously held state.
Enabling performance logging on an object in the normal state moves the object into the performance logging on state. This means that performance data is collected on the object and can be viewed in the Performance windows or the Performance Manager windows. Performance logging collects data only for GRPs and interfaces. You can enable performance logging on a global scale or on an individual object basis. Enabling global performance logging puts all subchassis objects into the performance logging on state. However, remember that only GRPs and interfaces actually collect performance data. (For more information on global performance logging, see the "Starting or Stopping Global Performance Logging" section.)
Performance logging occurs every 15 minutes. This means that when you initially enable performance logging or global performance logging on an object, it takes 15 minutes for the data to be collected and displayed in Cisco 7200/7400 Series Manager performance menus.
Heartbeat polling is performed on an object in the performance logging on state. If the object moves into the errored state, it is returned to the performance logging on state when the error is rectified. For example, if a port adapter is in the performance logging on state and it becomes nonoperational, it moves into the errored state. When heartbeat polling finds that the port adapter is operational again, it restores the port adapter to the performance logging on state.
The lost comms (lost communications) state indicates that the object is not contactable. Cisco 7200/7400 Series Manager can apply this state to a chassis, module, or interface. During this state, heartbeat polling is performed on the object. When the object becomes contactable again, it moves out of the lost comms state.
Assume that an ATM port adapter in Cisco 7200/7400 Series Manager was predeployed. When you perform device synchronization (commissioning a chassis), the ATM port adapter is not yet physically present in the hardware. In this situation, Cisco 7200/7400 Series Manager places the ATM port adapter into a lost comms state, where it continues to poll for the presence of the port adapter. When the ATM port adapter is inserted into the chassis, Cisco 7200/7400 Series Manager detects its presence and moves the port adapter out of the lost comms state and into the appropriate state (typically normal).
The lost comms (lost communications) no poll state occurs when a device (Cisco 7200/7400 Series Manager) cannot be contacted.
When Cisco 7200/7400 Series Manager loses connectivity with a device, the representative chassis object remains in the lost comms state, so that heartbeat polling continues on the chassis. However, all modules and interfaces within that chassis move into a lost comms no poll state. There is no point in polling modules and interfaces within a device that is not contactable. If the connection with the device is lost, all module and interface connections will also be lost. When the device becomes contactable again, the chassis, modules, and interfaces are moved out of the lost comms no poll state.
The discovery lost comms (lost communications) state is similar to the lost comms no poll state; however, this state occurs only during subchassis discovery. For example, if you commission a chassis (which begins the process of subchassis discovery), and a port adapter with a faulty connection is discovered, the port adapter is placed into the discovery lost comms state. When connectivity with the corresponding object in the device is established, subchassis discovery is resumed, and the object is moved out of the discovery lost comms state.
The mismatched state occurs when a mismatch is found between what is in the hardware and what is deployed in Cisco 7200/7400 Series Manager.
For example, if you are expecting to find an ATM OC-3 port adapter, you might predeploy and perform offline configuration in Cisco 7200/7400 Series Manager to prepare for that type of port adapter. However, when the port adapter becomes available and is placed into the chassis, it is not an ATM OC-3 port adapter, but a POS OC-3 port adapter. When Cisco 7200/7400 Series Manager detects the new port adapter, it finds a mismatch. The port adapter is placed into the mismatch state, and a major alarm is raised against the port adapter.
To rectify a mismatch problem, you must first assess the source of the problem. If an incorrect port adapter was predeployed, delete the predeployed port adapter and predeploy the correct port adapter. If the mismatch occurred because the wrong type of port adapter was inserted into the chassis, remove the port adapter. When you remove a port adapter, Cisco 7200/7400 Series Manager moves that port adapter into a lost comms state. Insert the correct port adapter. Cisco 7200/7400 Series Manager finds the new port adapter and downloads the correct predeployment and offline configuration information, then places the port adapter into its appropriate state (typically normal).
Mismatch can also occur on a chassis. If, during predeployment of a chassis, an incorrect IP address is entered, Cisco 7200/7400 Series Manager will detect the problem. The chassis predeployment can still be performed normally; however, when the chassis is physically present and the commissioning process is initiated, starting subchassis discovery, Cisco 7200/7400 Series Manager then detects the mismatch. A major alarm is raised against the chassis.
To rectify this problem, you can either delete the predeployed chassis and deploy the correct one, or enter the correct IP address in the chassis Management Information window.
This state applies only to voice cards. It indicates that the voice card has been discovered but is not configured.
To commission a voice card, it must be configured as a T1 or E1 card. This is not possible until the card is discovered, which occurs during chassis commissioning. When the voice card is initially discovered, it is placed in the Card Type Not Set state until the configuration is saved, and the card is recommissioned. After the card is configured and recommissioned, it is moved to the appropriate state (typically Normal).
Posted: Wed Jul 2 23:29:58 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
