|
|
The Cisco 7000 Series Manager provides high reliability, availability, serviceability, and performance. The system supports multiprotocol, multimedia routing and bridging with a wide variety of protocols and any combination of Ethernet, Fast Ethernet, Token Ring, Fiber Distributed Data Interface (FDDI), serial, multichannel channel attachment, and High-Speed Serial Interface (HSSI) media. Network interfaces reside on modular interface processors, which provide a direct connection between the high-speed Cisco Extended Bus (CxBus) and the external networks.
The Cisco 7000 Series Manager application supports the following routers:
The following figure shows a typical Cisco 7000 Series deployment.
The Concepts chapter describes EM concepts and covers the following information:
This guide is one part of the Cisco 7000 Series Manager EM documentation set. The following figure displays all of the guides in the EM documentation set and details the contents of each.
The guides identified in the preceding figure are available from Cisco Systems. For further information on obtaining Cisco documentation, see the "Obtaining Documentation" section.
This section contains the following information:
The Cisco 7000 Series Manager application supports seven router models:
Figure 1-1 through Figure 1-7 provide examples of each Cisco 7000 Series Manager supported chassis and the physical objects within each chassis.
The rear of the Cisco 7204 VXR router provides access to the network processing engine and up to two power supplies (see Figure 1-5).
The Cisco 7204 VXR chassis supports the following components:
The Cisco 7206 and 7206 VXR chassis support the following components:
The Cisco 7500 series routers support multiprotocol, multimedia routing, and bridging with a wide variety of protocols and any combination of various media.
The following figure displays the rear view of the Cisco 7505 chassis.
For the Cisco 7505, the network interfaces reside on interface processors that provide a direct connection between the chassis and external networks. The Cisco 7505 has five slots, four interface processor slots (0 through 3) and one slot for the Route Switch Processor (RSP1 or RSP4.) The Cisco 7505 uses a single power supply, with two models available, DC input or AC input.
The following figure displays the rear view of the Cisco 7507Z chassis.
For the Cisco 7507Z, the network interfaces reside on interface processors that provide a direct connection between the chassis and external networks. The Cisco 7507Z has seven slots: interface processor slots 0 and 1, RSP slots 2 and 3, and interface processor slots 4 through 6. There are bays for up to two AC input or DC input power supplies (the second power supply is not required; however, it allows for load sharing and increased system availability.)
The following figure displays the rear view of the Cisco 7513 chassis.
For the Cisco 7513, the network interfaces reside on interface processors that provide a direct connection between the chassis and external networks. The Cisco 7513 has thirteen slots: interface processor slots 0 through 5, RSP slots 6 and 7, and interface processor slots 8 through 12. As with the 7505 chassis, the Cisco 7513 contains bays for up to two AC input or DC input power supplies (the second power supply is not required; however, it allows for load sharing and increased system availability.)
The EM supports the following types of supporting modules within a chassis. Some modules only apply to certain chassis types.
The EM does not provide for management of supporting modules.
The EM supports the following types of modules:
Table 1-1 Supported Processor Modules
Table 1-2 Supported Generic Modules
|
| 1 This module was not fully tested for complete IOS support. A similar or variant card may have been tested instead. |
Table 1-3 Supported ATM/SONET Modules
|
| 1 This module was not fully tested for complete IOS support. A similar or variant card may have been tested instead. |
Table 1-4 Supported Ethernet Modules
|
Table 1-5 Supported Voice Modules
Cisco EMF provides a flexible framework which supports a variety of EMs, making it possible to manage multiple device types within a given network on a single system. Common network management functionality provides for complete management of the logical and physical components of the network. Using a solid base, Cisco EMF provides vital core functionality which allows for optimal network management when combined with EMs. Features include the following:
For further information on Cisco EMF and the tools it provides, see the following items:
The Cisco Element Management Framework User Guide Release 3.2 at the following URL:
http://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps829/products_user_guide_book091 86a00800ffd02.html
Installed with Cisco EMF, the EM allows for precise management of the device(s) it supports through custom GUI windows and modeling behavior. Invoked from the Cisco EMF Map Viewer application, the EM provides Fault, Configuration, Accounting, Performance, and Security (FCAPS) windows on chassis, module, interface, and connection levels as applicable. These windows provide the features which compliment the Cisco EMF capabilities to provide for complete, efficient network management.
Specifically, the Cisco 7000 Series Manager supports 7200, 7400, and 7500 series chassis. Element management capabilities for these items are provided in windows and wizards, eliminating the need for operators to have detailed Cisco IOS software and SNMP-based knowledge for individual interface or system parameter commands.
The following features highlight the capabilities of the EM:
The EM manages both physical and logical objects as follows:
Fault, Configuration, Accounting, Performance, and Security (FCAPS) windows are accessible on both physical and logical EM objects, in the form of FCAPS menu options that appear when you right-click on any object in the EM. FCAPS functionality provides a complete management interface to features of the router.
The EM uses Telecom Graphics Objects (TGO) in the Map Viewer application. TGO is a TeleManagement Forum (TMF) sponsored initiative to provide standard graphical representations for network topology maps.
A TGO displays additional information icons on top of the existing object icons displayed in Map Viewer. The additional icons indicate a variety of information (for example, information on the state of the object or event status information). The following figure provides an example of a TGO.
An object is a representation of a network element. For example, the object could be a node, a shelf, a shelf item, or a link. Each object shown in the right window provides pictorial cues which provide information about its associated network element. The information can be structural information; for example, a network element name or state and event information such as "out of service."
Each object can display the following information about its associated network element:
 |
Note For additional information regarding the type of TGO objects that can appear in the EM, see the Cisco Element Management Framework User Guide. |
This section covers the following areas:
The following table lists all physical objects created in the EM and the management functions that can be performed on each object.
Table 1-6 Physical Objects and Management Functions
|
The physical objects and interfaces in the preceding table are organized as follows:
For further details on hierarchies within Cisco EMF and the EM, see the "Views" section.
 |
Tip Physical objects contained within a chassis are often referred to as subchassis objects or modules. |
Physical interfaces and logical interface technologies are modeled as objects below a parent module. As mentioned before, the type of module characterizes the type of interface. Interface types further break down into two categories, physical interfaces and logical interface technologies.
Physical interfaces are the ports which exist on line cards. This EM supports the following physical interfaces:
The EM handles both SDH and SONET in the same manner. The routers support both SDH and SONET. For a comparison chart of SONET and SDH speeds, see "SONET/SDH Conversion Chart."
Logical interface technologies represent the communication between two network devices. Logical interface technologies allow for virtual connections, such as PVCs and SPVCs. This EM supports the following logical interface technologies:
Physical interfaces and logical interface technologies are classified as "interfaces" within this EM, and, therefore, are referred to as such within this guide. Keep in mind the differences previously described as you manage the interfaces within your network.
|
Tip The technologies an interface supports are accessible within FCAPS-based management windows. It is important to understand that physical interfaces require logical interface technologies in order to fully manage an interface. |
The following table outlines each interface type and the applicable physical and logical interface technologies supported. Also included are the different FCAPS service windows that are applicable to each physical and logical interface technology. For example, if you want to configure an ATM interface type, look in the table under ATM, and you will notice that three physical interface and logical interface technologies apply: ATM, SONET, and IP. This means that to fully configure an ATM over SONET interface, for example, you should open and update the appropriate fields in all the physical and logical configuration windows to completely configure a SONET interface which supports ATM technology. Note that the shaded areas denote logical interface technologies.
Table 1-7 Physical Interfaces, Related Technologies and Windows
Although not technology-specific, physical or logical, generic support is available through Configuration, Status, and Performance windows for each of the interface types in the preceding table.
The EM supports one logical object type, ATM connections. ATM connections may be Permanent Virtual Circuits (PVCs), Soft Permanent Virtual Circuits (SPVCs), or Switched Virtual Circuits (SVCs) that can be applied to ATM interfaces.
The following table describes the management functions for ATM logical objects.
|
Views are accessible by clicking the Viewer icon on the Cisco EMF launchpad. These views appear in the frame at the left of the window when you open the Map Viewer window (see the following figure for an example).
Views 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 EM objects by navigating through one of the views to find specific objects by expanding the text. Click on the plus sign (+) next to any object to expand the view. A minus sign (-) next to an object indicates there are no more levels to expand; you may, however, click on a minus sign (-) to collapse the view to the level of the specific object as necessary. Each view represents a different way of containing and grouping objects.
The EM adds specific views to the standard views supplied by Cisco EMF. The standard Cisco EMF views are the Physical and Network views.
|
Note For further information on views, see the Cisco Element Management Framework User Guide Release 3.2. |
The number in parenthesis next to a view indicates how many top-level objects are contained within the view.
The Views section covers the following areas:
You may or may not see all of these views using this EM (exceptions noted). These views all exist within EMs, however they are not all implemented. If multiple EMs are co-resident, the applicable views are displayed.
As the following sections detail, the views you will use to perform the majority of the EM capabilities are the Physical and Component Managed views. Both are similar in structure and allow you to initiate the EM windows. However it is recommended that you use the Physical view to perform most management functions within the EM. The Physical view provides a graphical representation of the chassis that the Component Managed view does not. It should, however, be noted that you must use the Component Managed view to see representative ATM connection objects within the EM as ATM connection objects are not available through the Physical view.
The Component Managed view displays all objects within the Cisco EMF system. For example, say you have two different EMs installed in Cisco EMF: EM A and EM B. Information for both the EM A and EM B display within the Component Managed view. Additionally, the Component Managed view also displays ATM connections such as PVCs and SPVCs. Connection objects are not visible in any other view. However, it is not recommended to work within this view unless you have multiple EMs installed.
The Component Managed view and Physical view have the same basic hierarchy structure, as shown in the following figure. Note that the Physical view does not display logical ATM connections like the Component Managed view does.
|
Note Logical connections are only present beneath an ATM physical interface. |
Figure 1-15 shows an example of the menu structure of the Component Managed view.
The Layer 3 QoS view displays only Layer 3 QoS objects within the EM, such as the following:
You can work within this view to create and configure Access Lists or CAR or WRED objects by accessing the respective EM menus.
This view displays all network devices within their relevant networks and subnets. The auto-discovery system of Cisco EMF uses this view to determine which devices exist on the system so that it does not try to discover the same device multiple times. For details on auto-discovery, see the "Automatically Discovering Chassis" section.
Objects in the Physical view are ordered according to their relative physical location. The Physical view defines physical containment relationships, meaning that each object is defined according to which object it is contained within. For example, a site is located under the Physical view; a chassis is contained under a site; and sub modules and supporting modules are contained within a chassis.
See Figure 1-14 for an overview of the structure of the Physical view.
The Physical view also 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, simply click on the chassis object for the router you wish to view. Logical connection objects are not apparent under the Physical view.
Figure 1-15 shows an example of the menu structure of the Physical view.
All objects managed by the RME server display beneath the RME view. Objects are organized by RME server objects.
|
Note For more information on RME, refer to the User Guide for Resource Manager Essentials 3.5 at the
following URL: http://www.cisco.com/en/US/products/sw/c iscowork/ps2073/products_user_guide_book09186a00800ca43b.html |
This view allows you to monitor network elements which are part of the Cisco EMF system. The Self Management view is non-propagating.
Object states reflect the life cycle of an object. Whatever stage the object is in at any given time displays in the state type. The state of an object can change frequently, depending upon what actions take place on the object. All objects within the EM are in a specific state which appears at the bottom left corner of each FCAPS window. The following figure highlights an object's state.
The two most common object states are Normal and Decommissioned. For example, when you deploy a module in the EM, the initial state of the module is decommissioned. You can then commission the module to begin active management. (For instruction on how to commission a module, see the "Commissioning Modules" section or on page 5-31.) When you commission the module, it passes through two transitory states: discovery, 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 to objects below. For example, if you decommission a chassis, all subchassis objects also decommission. If you enable performance logging on a module, all interfaces under the module also enable.
By default, FCAPS windows refresh at a rate dependent upon the type of window. For example, inventory windows refresh at a lower rate than performance windows. The average refresh rate is every 30 seconds.
The following sections describe the possible states that an object may be in and provides a description of these states.
The normal state indicates that an object is operational. When an object enters the normal state, the EM performs heartbeat polling on objects at varying intervals to determine their presence and current state. For instance, chassis presence polling occurs every minute while module and interface presence polling occurs every five minutes.
The decommissioned state indicates that an object is not managed. When you manually deploy an object, the object is normally put into the decommissioned state.
|
Tip Manually deployed objects are initially decommissioned so you have the option of managing the object. If you want to manage the object, you must first commission the object. |
The following actions occur on a decommissioned object:
Decommission buttons are located in Chassis, Module, Interface, and Connection Configuration windows. When you decommission an object, any children of that object also change their state to decommissioned. For example, if you decommission a chassis, all objects within that chassis (modules, interfaces, and connections) also decommission. If you decommission a module, all interfaces and connections on that module decommission, and so on.
If the operational status of a module goes down, it moves into the errored state. In the errored state, performance polling (if active) stops; however, heartbeat polling (which polls an object every 5 minutes to verify its existence and current state) continues until the device responds positively to a heartbeat request. When the module responds positively to heartbeat requests, it moves back into the previously held state.
Enabling performance logging on for an object in the Normal state moves the object into the performance logging on state. This means that performance data collection for the object begins and is available for review in the Cisco EMF Performance Manager window. Regardless of whether performance logging is on or off for a particular object, current performance data is available in the EM Performance windows as "Performance", describes.
You can enable performance logging on a global scale or on an individual object basis. Enabling global performance logging puts all subchassis objects into a performance logging on state.
Performance logging occurs every 15 minutes. This means that when you enable performance logging or global performance logging initially on an object, at least one 15-minute increment must pass before data displays in the Performance Manager.
Heartbeat polling occurs on objects in the performance logging on state. If the object moves into the errored state, it returns to the performance logging on state when the error is rectified. For example, if a module is in the performance logging on state and it goes down, it moves into the errored state. When heartbeat polling finds that the module is back up, it restores the module to the performance logging on state.
The lost comms (lost communications) state indicates that the object is not responding to heartbeat polling. The EM can apply this state to a chassis, module, or interface. When an object is in the lost comms state, heartbeat polling occurs on the object. When the object responds to heartbeat polling, it moves out of the lost comms state. For example, say an ATM module in the EM was predeployed. When you perform device synchronization (commissioning a chassis), the ATM module is not yet physically present in the hardware. In this situation, the EM places the ATM module into the lost comms state, where it continues to poll for the presence of the module. When the ATM module is inserted into the chassis, the EM detects its presence and moves the module out of the lost comms state and into a respective state (typically normal).
The lost comms (lost communications) no poll state occurs when the router is not contactable. When the EM 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 down, all modules and interfaces will be down. 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 state occurs only during subchassis discovery. If, for example, you commission a chassis (which begins the process of subchassis discovery) and a module discovers with a faulty connection, the module goes into the discovery lost comms state. When connectivity establishes with the corresponding object in the device, subchassis discovery resumes, and the object moves out of the discovery lost comms state.
The mismatched state occurs when a mismatch is found between what hardware is in the device and that which is deployed in the EM. For example, assume a chassis has been deployed and commissioned. If the chassis cards are switched with a different card type, the EM finds a mismatch. The chassis is put into the mismatch state and a major alarm is raised.
To rectify a mismatch problem, first you must assess the source of the problem. If the operator was at fault and predeployed an incorrect module, the operator should delete the predeployed module and re-deploy the correct module. If the person who inserted the module is at fault because they inserted the wrong type of module into the chassis, the module should be removed. When you remove a module, the EM moves the module into a lost comms state. Inserting the correct module enables the EM to find the new module and download the correct pre-deployment and offline configuration information, then places the module into its respective state (typically normal).
Mismatch can also occur on a chassis. If, during deployment of a chassis, an incorrect IP address is entered, the EM cannot discover the chassis due to an erroneous IP address that was entered during the commissioning process. Because of this, discovery fails, a major alarm is raised against the chassis, and the chassis enters the mismatched state. To rectify this problem, you must either delete the predeployed chassis and deploy the correct one, or fix the IP address by re-entering the correct one in the chassis Management Information window.
The following tables depict the possible state transitions by object type.
Table 1-9 Chassis State Transitions
|
Table 1-10 Power Supply State Transitions
|
Table 1-11 Voice Module State Transitions
|
Table 1-12 Voice Interface State Transitions
|
Certain states in the EM are temporary or transient, that is, they exist only for a short time while a process is underway. The following states are transient:
Posted: Wed Aug 20 12:38:32 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
