C H A P T E R 1
Concepts
The Cisco 10000 series router offers a single solution for
The Cisco 10000 Series Manager application supports the Cisco 10005 Edge Services Router (ESR) and the Cisco 10008 ESR.
The following figure shows a typical Cisco 10000 deployment.
Figure
89823
The Concepts chapter describes EM concepts and covers the following information:
???Cisco EMF Software Features
???Views
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
EM Documentation Set
EM Documentation Set
This guide is one part of the Cisco 10000 Series Manager EM documentation set. The following figure displays all of the guides in the EM documentation set and details the contents of each.
Figure
Cisco Element Management
Framework Installation and
Administration Guide (Release 3.2)
Cisco Element Management
Framework User Guide
(Version 3.2)
Cisco 10000 Series
Manager Installation Guide
(Release 1.0)
Cisco 10000 Series
Manager User Guide
(Release 1.0)
Describes how to install the Cisco Element Management Framework application and provides additional setup and licensing information.
Describes how to use the Cisco Element Management Framework application.
Describes how to install the Cisco 10000 Series Manager application and provides additional setup information.
Describes how to use the Cisco 10000 Series Manager application.
89785
The guides identified in the preceding figure are available from Cisco Systems. For further information on obtaining Cisco documentation, see the ???Obtaining Documentation??? section on page
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
Cisco EMF Software Features
Cisco EMF Software Features
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:
???Map
???Deployment
???Auto
???Event
???Object Group
???Performance
???User Access
???Query
???Notification
???Thresholding
???Event
???Database
For further information on Cisco EMF and the tools it provides, see the following items:
???The ???Cisco EMF Launchpad??? section on page
???The Cisco Element Management Framework User Guide Release 3.2
???Cisco EMF help windows available through the Help button or menu on the Cisco EMF Launchpad
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
EM Software Features
EM Software Features
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 10000 Series Manager supports the Cisco 10005 ESR and Cisco 10008 ESR chassis, as well as various modules which can accommodate ethernet, ATM, POS, SONET, and E3/DS3 interfaces. Element management capabilities for these items are provided in windows and wizards, eliminating the need for operators to have detailed Cisco IOS software and
The following features highlight the capabilities of the EM:
???
???IOS
???Deployment and
???
???Auto
???
???Fault
???
???
???
???
???
???
???
???
???
???Alarm
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
EM Objects and Interfaces
EM Objects and Interfaces
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
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.
Figure
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:
???Object
???Object
???Object
???Event unacknowledged count
???Event unacknowledged state
???Event outstanding state
The following figure shows an example of a chassis map displaying a few of the TGO icons that could appear.
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
EM Objects and Interfaces
Figure
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:
???Modules
???Physical Interfaces and Logical Interface Technologies
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
EM Objects and Interfaces
Physical Objects
The following table lists all physical objects created in the EM and the management functions that can be performed on each object.
Table
The physical objects and interfaces in the preceding table are organized as follows:
???The chassis contains the modules, including supporting modules (e.g., processors, power supplies, and fan trays);
???The modules contain the physical interfaces.
For further details on hierarchies within Cisco EMF and the EM, see the ???Views??? section on page
Tip Physical objects contained within a chassis are often referred to as subchassis objects or modules.
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
EM Objects and Interfaces
Cisco 10000 Router Chassis
The Cisco 10000 Series Manager supports the Cisco 10005 Edge Services Routers (ESR) and Cisco 10008 ESR. The supported Cisco 10000 series routers include a performance routing engine
(PRE), a
The following figures display the Cisco 10005 ESR and Cisco 10008 ESR chassis.
Figure
The Cisco 10005 ESR chassis contains seven slots total, accommodating up to five line cards in the upper compartment and up to two PRE cards in the lower compartment. The blower, located on the side of the chassis (not identified in the preceding depiction), allows for
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
EM Objects and Interfaces
Figure
The Cisco 10008 ESR chassis contains ten slots overall. Two centrally located slots accommodate PRE cards and eight slots accommodate line cards, four on either side of the PRE slots. Area for dual PEMs provide redundant power supplies. The blower, located at the top of the chassis??? front view, allows for
Supporting Modules
The EM supports the following types of supporting modules within a chassis. Some modules only apply to certain chassis types.
???SFC (Switch Fabric Card)
???AC or DC Power Supply
???Fan
The EM does not provide for management of supporting modules.
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
EM Objects and Interfaces
Modules
The EM supports the following types of modules:
???
???
???ATM (Asynchronous Transfer
???Ethernet (Fast or
Table
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
EM Objects and Interfaces
Physical Interfaces and Logical Interface Technologies
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:
???Ethernet
???SONET
???DS1
???DS3
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 Appendix B, ???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:
???ATM
???IP
???POS
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
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
Chapter 1 Concepts
EM Objects and Interfaces
Although not
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
Views
Views
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
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.
Figure
The number in parenthesis next to a view indicates how many
The Views section covers the following areas:
???Network View
???RME View
???VLAN View
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
Views
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
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.
Component Managed 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.
Figure
Site
Logical connections (PVC and SPVCs)
Logical connections (PVC and SPVCs)
Logical connections (PVC and SPVCs)
80564
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
Views
Cisco 10000 Series Manager does not support ATM connection management, therefore logical ATM connection objects associated with the supported devices are not apparent in the Component Managed view.
Layer 3 QoS View
The Layer 3 QoS view displays only Layer 3 QoS objects within the EM, such as the following:
???Access Lists
???Committed Access Rate (CAR) objects
???Weighted Random Early Detection (WRED) objects
You can work within this view to create and configure Access Lists or CAR or WRED objects by accessing the respective EM menus.
This version of the EM does not provide Layer 3 QoS support. Neither the Layer 3 QoS view nor the respective menus are applicable.
Network View
This view displays all network devices within their relevant networks and subnets. The
Physical View
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
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.
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
Views
Figure
RME View
All objects managed by the RME server display beneath the RME view. Objects are organized by RME server objects.
Self Management View
This view allows you to monitor network elements which are part of the Cisco EMF system. The Self Management view is
VLAN View
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
Object States
Object States
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.
Figure
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 on page
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.
Normal State
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.
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
Object States
Decommissioned State
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 decomissioned 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:
???Active management stops
???All sub objects also decommission
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.
Errored
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.
Performance Logging On
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 Chapter 8, ???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
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.
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
Object States
Lost Comms
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).
Lost Comms No Poll
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.
Discovery Lost Comms
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.
Mismatched
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
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
Cisco 10000 Series Manager User Guide
Chapter 1 Concepts
Object States
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
Preprovisioned
Module preprovisioning is available within the EM and device. Module preprovisioning essentially serves as a way to establish place holders for anticipated or expected hardware modules.
Using the EM, modules may be preprovisioned on the chassis map by way of predeployment and commissioning. Module predeployment occurs through manual deployment where the module type and slot number are indicated. Representative objects display within the EM, allowing for module configuration before the physical module is present in the device. Module preprovisioning occurs on the device when manually deployed, or predeployed, modules which are not yet present in the device are commissioned. Modules can also be preprovisioned upon predeployment if the card is not present and the object is in a given state (normal, performance logging on, or synchronizing.)
Preprovisioned modules allow for configuration to occur in advance of the module being physically
Predeployed modules not yet commissioned (i.e., unprovisioned) remain in the decommissioned state. Once preprovisioned modules are present within the device, all configuration parameters entered through the EM or via IOS commands are applied to the card during discovery. Should the module which was preprovisioned be different from that found in the device, the module moves to the mismatched state.
See the ???Mismatched??? section on the preceding page for additional information.
Transient Object States
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:
???
???
???
Cisco 10000 Series Manager User Guide