-
Cisco 12000/10720 Router Manager User's Guide, 3.0
-
About this Guide
-
C12k/10720M - Overview
-
Concepts
-
Getting Started with C12k/10720M 3.0
-
Managing Chassis
-
Managing Modules
-
Managing Interfaces
-
Interface Profiles
-
Interface Configuration
-
Interface Status
-
Interface Performance
-
Layer 3 QoS
-
Managing ATM Connections
-
Managing VLANs
-
Fault Management
-
Change Management
-
Performance Management
-
SONET/SDH Conversion Chart
-
Table Of Contents
C12k/10720M Objects and Interfaces
Cisco 12000/10700 Series Internet Router Chassis
Physical Interfaces and Technologies
Use of Telecom Graphics Objects
Concepts
This chapter describes Cisco 12000/10720 Manager (C12k/10720M) concepts and covers the following information:
•
C12k/10720M Objects and Interfaces
C12k/10720M Objects and Interfaces
C12k/10720M manages both physical and logical objects, as follows:
•
•
Fault, Configuration, Accounting and Performance (FCAP) windows are accessible on both physical and logical EM objects, in the form of FCAP menu options that appear when you right-click on any object in C12k/10720M. FCAP functionality provides a complete management interface to the features of the Cisco 12000 series and Cisco 10720 internet router.
This section covers the following areas:
•
•
Physical Objects
Table 2-1 lists all physical objects created in C12k/10720M and the management functions that can be performed on each object.
Table 2-1 Physical Objects and Management Functions
Chassis—The hardware frame of the Cisco 12000 series or Cisco 10720 internet router, which houses all subchassis objects (modules).
Command Log
Configuration
Configuration Backup/Restore
Configuration Editor
Fault Management
Initiate Telnet Service
Inventory
IOS Image Download
Launch Web Console
Management Information
SNMP Management
System Log
APS Status
RPR Configuration
RPR StatusGRP (Gigabit Route Processor)—There can be up to two GRPs in a chassis. The primary GRP is the CPU or "brains" of the router. The secondary GRP is redundant.
Configuration
Fault Management
Inventory
PerformanceLine Cards—There are various types of line cards within a chassis (for example, ATM, Ethernet, SRP, POS, E3, DS3 and Modular Ethernet). Each of these line cards holds a given number of physical interfaces (ports).
Configuration
Fault Management
InventoryPhysical Interfaces—Each line card has at least one, if not multiple, physical interfaces (ports). The type of physical interface is equivalent to the type of line card the interface resides on. Each physical interface can support multiple technologies (for details, refer to "Physical Interfaces and Technologies" section) The line card type determines what specific technologies are supported by an interface.
Profile
Configuration
Fault Management
Performance
StatusSupporting Modules—Additional subchassis cards and modules: the switch fabric card (SFC), clock scheduler card (CSC), AC or DC power supply module, blower module, and fan tray module.
Configuration
Fault Management
Inventory
Note
The physical objects and interfaces displayed in Table 2-1 are traced as follows:
•
•
Refer to the "Views" section for further details on hierarchies within Cisco EMF and C12k/10720M.
Tip
Cisco 12000/10700 Series Internet Router Chassis
The C12k/10720M application supports the entire range of Cisco 12000 series internet router chassis like: Cisco 12008, Cisco 12012, Cisco 12016, Cisco 12404, Cisco 12406, Cisco 12410, Cisco 12416 and the Cisco 10720 internet router chassis.
Figure 2-1 displays a Cisco 12016 internet router chassis as an example, and identifies the modules and sub-modules that you would find:
Figure 2-1 Cisco 12016 Chassis
The Cisco 12016 chassis supports the following components:
•
•
•
•
–
–
–
•
–
–
•
–
–
–
Supporting Modules
C12k/10720M supports five types of supporting modules within a Cisco 12000 series internet router chassis. Some modules only apply to certain chassis types.
•
•
•
•
•
Linecards
Refer "Manually Deploying Line Cards" section for details of all the supported technology specific linecards.
Physical Interfaces and Technologies
Physical interfaces are modeled as objects below the parent line card. Some generic properties are supported by all the interfaces. As mentioned before, the type of line card characterizes the type of physical interface; for example, an ATM line card will only support ATM interfaces. However, there can be multiple technologies supported on that physical interface. For example, ATM physical interfaces can support the following:
•
•
•
Note
Tip
Table 2-2 outlines each physical interface and the technologies it supports. Also included are the different FCAP-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 you should open the configuration windows for these four technologies and configure the fields within, in order to completely configure an ATM interface.
Logical Objects
C12k/10720M supports three logical object types:
•
Note
•
•
Table 2-3 describes the management functions for Layer 3 QoS logical configurations.
Table 2-4 describes the management functions for ATM logical objects.
Table 2-5 describes the management functions for VLAN objects.
Use of Telecom Graphics Objects
Cisco EMF 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). Figure 2-2 provides an example of a TGO.
Figure 2-2 Sample Telecom Graphical Object
An object is a representation of a network element. For example, the object could be a node 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:
•
•
•
–
–
–
Figure 2-3 shows an example of a Cisco 12000 chassis map displaying a few of the TGO icons that could appear.
Figure 2-3 Sample Cisco 12000 Chassis Showing Telecom Graphical Objects
Refer to the Cisco Element Management Framework User Guide Release 3.2 for further information on the type of TGO objects that can appear in the Cisco 12000/10720 Manager.
OSI Mappings
Table 2-6 gives the complete list of OSI mappings for all combinations of the Admin and Operational status.
Note
Views
C12k/10720M views can be accessed by clicking on the Viewer icon in the Cisco EMF launchpad. These views appear in the frame at the left of the window when you open the Map Viewer window (see Figure 2-4).
C12k/10720M 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 C12k/10720M objects by navigating through one of the views to find the object. You can navigate through views by expanding text. Click on the + sign next to any object to expand text. A - sign next to an object indicates there is no more text to expand. Each view represents a different way of containing and grouping objects.
C12k/10720M adds specific views to the standard views supplied by Cisco EMF. The standard Cisco EMF views are the Physical and Network views (for further information on these views, refer to the Cisco Element Management Framework User Guide Release 3.2 (78-12536-01)) and the Forsetti documentation.
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:
Component Managed View
The Component Managed view displays all objects within the Cisco EMF system. The Component Managed view displays all the physical objects and most of the logical objects.
Figure 2-4 Hierarchy of Component Managed View
Layer 3 QoS View
The Layer 3 QoS view displays only Layer 3 QoS objects within C12k/10720M, 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 C12k/10720M menus.
Network View
This view displays all network devices within their relevant networks and subnets. The auto-discovery system of Cisco EMF uses this view to calculate which devices have already been added to the system, so that it does not try to discover the same device multiple times. For details on auto-discovery, refer to "IP Auto Discovery of the Cisco Chassis" section.
Physical View
Physical view displays all the physical objects. Objects in the Physical view are ordered according to their relative physical location.
Figure 2-5 Hierarchy of Physical View
VLAN View
The VLAN view displays the VLAN objects in C12k/10720M. The VLAN view can contain one or more domains. A domain is a user-defined grouping of the VLAN objects. This grouping may be done on a customer name basis, on logical groupings like 'Accounting Vlans' or it could be any other user maintained VLAN grouping. There can be mulitple domains in the VLAN view and each domain can contain mulitple VLAN objects. The same VLAN id can be duplicated across different domains. Each VLAN object can have multiple sub-interface objects.
Note
C12k/10720M Object States
C12k/10720M 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 upon what actions are being performed on the object. All objects in C12k/10720M have a state assigned to them which appears at the bottom left corner of each FCAP window for a selected object (see Figure 2-6).
Figure 2-6 C12k/10720M Object States
The two most common object states are Normal and Decommissioned. For example, when you deploy a line card in C12k/10720M, the initial state of the line card is decommissioned. You can then commission the line card to begin active management (for details on how to commission a module, refer to the "Commissioning a Selected Module" section). When you commission the line card, it passes through two transitory states: discovery and 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 any objects below. For example, if you decommission a chassis, all subchassis objects are also decommissioned. If you enable performance logging on a line card, all interfaces on the line card are also transitioned to performance logging.
By default, FCAP windows refresh at a rate dependent upon the type of window. For example, inventory windows are refreshed 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.
Decommissioned State
The decommissioned state indicates that an object is not managed. When you manually deploy an object, it is normally placed into a decommissioned state.
Tip
The following actions occur on a decommissioned object:
•
•
Decommission buttons are located in Chassis, Module, Interface and VLAN 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 (GRP card, line cards, interfaces, connections) are also decommissioned. If you decommission a line card, all interfaces and connections on that line card are decommissioned, and so on.
Normal State
The normal state indicates that an object is operational. When any physical object enters the normal state, C12k/10720M performs heartbeat polling on the objects. The heartbeat polling interval for chassis object is 1 minute and for all modules and interface objects, the heartbeat polling interval is 5 minutes.
Errored
When the object is in a non-operational state, it moves into the errored state. In the errored state, performance polling (if activated) is stopped; however, the heartbeat polling (which polls an object every 5 minutes to verify its existence and current state) continues, until the device responds positively to the heartbeat request. When the module is operational again, it responds positively to the heartbeat requests, and then moves into the state which it previously held.
Performance Logging On
When performance logging is started on an object in the Normal state, the object moves into the Performance Logging On state. This means that the performance data is collected on the object and is viewed in the Performance windows or the Performance Manager windows. Performance logging is enabled for GRPs, interfaces and VLAN sub-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 a performance logging on state. However, remember that only GRPs and interfaces actually collect performance data. (For more information on global performance logging, refer to the "Starting Global Performance Logging" section.
Performance logging occurs every 15 minutes. This means that when you enable performance logging or global performance logging initially on an object, it takes 15 minutes for the data to be collected and displayed in C12k/10720M 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 line card is in the performance logging on state and it goes down in the device, the EM moves the line card into the errored state. When heartbeat polling finds that the line card is operational, the EM restores the line card to the performance logging on state.
Lost Comms
The lost comms (lost communications) state indicates that the object is not contactable. C12k/10720M 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.
Discovery Lost Comms
The discovery lost comms state is quite similar to the lost comms state; however, this state only occurs during subchassis discovery. For example, if you commission a chassis (which begins the process of subchassis discovery), and if a pre-deployed line card is not present then, the line card is moved into the discovery lost comms state. When the linecard is re-inserted in the device, subchassis discovery is resumed, and the object moves out of the discovery lost comms state.
Mismatched
The mismatched state occurs when a mismatch is found between what is in the hardware and what is deployed in C12k/10720M. For example, say you are expecting an ATM OC-3 line card. So you predeploy and perform offline configuration in C12k/10720M to prepare for that type of line card. Now, when the line card becomes available and is placed into the chassis, it is not an ATM OC-3 line card, but a POS OC-3 line card. So when C12k/10720M detects the new line card, it finds a mismatch. The line card gets placed into the mismatch state, and a major alarm is raised against the line card.
Transient Object States
Certain states in C12k/10720M are temporary or transient, that is, they exist only for a short time while a process is being performed. The following states are transient:
•
•
•
•
