The C7kM class model has four distinct parts for: Chassis, Module and Interface. These correspond to the typical physical anatomy of a Cisco device, as shown in the figure below.
Figure 2-1 7507 Chassis View
There is always a Chassis, which is the frame or housing unit
The Chassis is usually contained in a Shelf (or rack)
The Chassis contains plug-in modules that perform various functions such as routing
Modules may contain sub-modules or interfaces that carry network traffic
Interfaces model the physical ports present on the modules (for example, ATM 5/0)
These classes are used to build up a representation of the topology and inventory of the specific device being modelled.
Chassis
C7kM supports three series of chassis:
7200
7400
7500 ( includes 7505, 7507, 7513 )
These chassis inherit from the CiscoERChassis. The most important class in the model is CiscoERChassis, shown in the figure below. The inheritance is shown here:
Figure 2-2 Chassis Class Hierarchy
These classes represent the actual physical Chassis belonging to the device, thereby allowing functionality most logically associated with the Chassis to be placed here.
It also defines an abstract base class for all C7kM chassis. This provides a convenient abstraction for clients to use in queries. For example, if a client wanted to perform an inventory of all managed CiscoERChassis, then the presence of this abstraction negates the need to know which actual chassis types are present.
CiscoERChassis inherits from the CiscoChassis that models the associated Fault, Configuration, Accounting, Performance and Security (FCAPS) functions available on a Chassis object. There is a very definite pattern to this class model. Each FCAPS categories is essentially encapsulated into a specific class which is then mixed-in to the CiscoChassis class. For example, CiscoStatus encapsulates all the Status properties of a Chassis, such as "System Up Time."
Note From an integration perspective, the mix-in classes are not relevant: functions of a CiscoERChassis can
be obtained without referring to these mix-in classes.
Abstract Chassis Classes
CiscoChassis—This grouping class provides the implementation for the state machines. This class does not define any types or attributes. The CiscoERChassis inherits from this class.
All concrete ER chassis classes must inherit from the CiscoERChassis.
Concrete Chassis Classes
Cisco7206Chassis—This class does not define any type or attributes. Objects of this class are deployed when 7206 chassis has to be managed.
Cisco7204VXRChassis—This class does not define any type or attributes. Objects of this class are deployed when 7204 VXR chassis has to be managed.
Cisco7206VXRChassis—This class does not define any type or attributes. Objects of this class are deployed when 7206 VXR chassis has to be managed.
Cisco7401Chassis—This class does not define any type or attributes. Objects of this class are deployed when 7401 chassis has to be managed.
Cisco7505Chassis—This class does not define any type or attributes. Objects of this class are deployed when 7505 chassis has to be managed.
Cisco7507Chassis—This class does not define any type or attributes. Objects of this class are deployed when 7507 chassis has to be managed.
Cisco7507ZChassis—This class does not define any type or attributes. Objects of this class are deployed when 7505Z chassis has to be managed.
Cisco7513Chassis—This class does not define any type or attributes. Objects of this class are deployed when 7513 chassis has to be managed.
Cisco7513ZChassis—This class does not define any type or attributes. Objects of this class are deployed when 7513Z chassis has to be managed.
Cisco7513MXChassis—This class does not define any type or attributes. Objects of this class are deployed when 7513MX chassis has to be managed.
Module
C7kM supports the following technology modules:
ATM
POS
Ethernet
Voice
DS3
SONET
IP
The supporting modules are:
CSC
AC/DC Power supply
Blower Module
The module class model allows generic management of module/card network components within the chassis:
Figure 2-3 Class Model of Abstract Module Classes
Figure 2-4 Class Model of Concrete Module Classes
Abstract Module Classes
Classes derived from CiscoERBladeModule model linecard/modules of a 7k. This includes traffic carrying Line Cards like ATM, POS, Ethernet, SRP and DS3 and supporting modules such as Power Supplies and AC/DC Power Supply that inherit from the CiscoERBladeModule.
The following is a brief description of each mix class in the module class hierarchy:
CiscoStatus—Encapsulates fault/status properties of a module.
CiscoIOSHost—Encapsulates Cisco IOS related functionality such as image download, configuration backup and restore, passwords.
CiscoManagedObject—Encapsulates non device related functionality, required within the C7kM Infrastructure. For example, command attributes for changing state, initiating discovery, and denoting performance logging.
CiscoModulePerformance—This models performance data collection capabilities at the module level. At present, only processor performance data is supported. This means that if a non-processing unit is queried for performance data, then the values associated with the main processor unit will be returned. It is intended to add to this class in future when more Module specific data becomes available.
snmpProxy—This class reflects the fact that Modules do not generally have a local SNMP Agent and are effectively proxied by the Agent running on the Chassis. (See CEMF Developer documentation)
In effect this means that retrieving data against an individual module will result in the data coming from the chassis level. This means that individual modules in the same chassis may return the same values. The performance data is related to module CPU usage and the data for all modules under a chassis will retrieve the same values.
Concrete Module Classes
CiscoERISDNBRIModule—Encapsulates ISDN and BRI features of a module
CiscoERVoiceModule—Encapsulates Voice features of a module
CiscoERAsyncSerialModule—Encapsulates Asynchronous Serial features of a module
CiscoERIPoverEthernetModule—Encapsulates IP and Ethernet features of a module
CiscoERIPoverATMoverSonetModule—Encapsulates IP, ATM and Sonet features of a module
CiscoERIPoverPOSoverSonetModule—Encapsulates Ip, POS and Sonet features of a module
CiscoERTokenRingWANModule—Encapsulates Token Ring WAN features of a module
CiscoERGenericModule—Encapsulates generic features of 7000 series module
CiscoERChannelizedModule—Encapsulates Channelized features of a module
CiscoERIPoverATMoverDS3Module—Encapsulates IP, ATM and DS3 features of module
CiscoERIPoverATMoverEthernetModule—Encapsulates IP, ATM and Ethernet featurs of a module
CiscoERVIPModule—Encapsulates VIP module features
CiscoERSRPoverSonetModule—Encapsulates SRP and Sonet features of module
CiscoERMCoverDS3Module—Encapsulates MC and DS3 features of a module
CiscoERChannelizedoverDS3Module—Encapsulates Channelized and DS3 features of a module
CiscoERMCoverDS1Module—Encapsulates MC and DS1 features of a module
Interface
Physical interfaces are modeled as objects below the parent line card. As mentioned before, the type of a linecard 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 support the following technologies:
Internet Protocol (IP)
ATM
SONET
Interfaces supported by C7kM
The interfaces supported by C7kM are as follows:
ATM over SONET
ATM over DS3
POS
Ethernet
Voice
The following table shows the classes corresponding to interface.
Table 2-1 Interfaces and Classes
Interface
Corresponding Interface Class
Voice
CiscoMCDS1Interface
ATM over SONET
CiscoIPOverATMEndpointOverSONETInterface
DS3
CiscoIPOverATMEndpointOverDS3Interface
POS
CiscoIPoverPOSoverSONETInterface
Ethernet
CiscoIPoverEthernetInterface
Abstract Interface Classes
CiscoMultiChanFunctionality—This concrete class encapsulates all the attributes related to Multi Channel technology.
CiscoGenericFunctionality—This abstract class encapsulates attributes related to the generic functionality of the interface.
CiscoGenericInterface—This concrete class encapsulates all the attributes related to Generic Interface.
Concrete Interface Classes
CiscoIPOverATMEndpointOverSONETInterface—This is a concrete class that represents all ATM interface objects in C7kM
CiscoIPOverATMEndpointOverDS3Interface—This is a concrete class that represents all DS3 interface objects in C7kM
CiscoIPoverPOSoverSONETInterface—This is a concrete class that represents all POS interface objects in C7kM
CiscoERIPoverEthernetInterface—This is a concrete class that represents all Ethernet interface objects in C7kM
CiscoIPoverEthernetInterface—This is a concrete class that represents all Ethernet interface objects in C7kM
CisoMCDS1Interface—This is a concrete class that represents all Voice interface objects in C7kM.
Note When the user deploys and commissions an Voice linecard, the interfaces that are discovered are of type
CiscoMCDS1Interface.
