This chapter provides information on the composition of the Oracle Communications Network Integrity Cisco Router and Switch SNMP cartridge from the Oracle Communications Design Studio perspective.
Table 6-1 shows the MIB-II model collection used in the Cisco Router and Switch SNMP cartridge.
Table 6-1 MIB-II Model Collection
| Specifications | Information Model Entity Type | Intended Usage/ Notes |
|---|---|---|
|
deviceGeneric |
LogicalDevice |
Represents any root object discovered on the network. |
|
interfaceGeneric |
MediaInterface |
Represents any interface discovered under deviceGeneric. |
|
GenericMedia |
DeviceInterfaceConfigurationItem |
Represents IpAddresses that are applied to an interfaceGeneric. |
|
IPAddresses |
DeviceInterfaceConfigurationItem |
Ip Addresses container. |
|
IPAddress |
DeviceInterfaceConfigurationItem |
Ip Address details container. |
Table 6-2 shows the Cisco model collection.
Table 6-2 Cisco Model Collection
| Specifications | Information Model Entity Type | Intended Usage/ Notes |
|---|---|---|
|
physicalDeviceGeneric |
PhysicalDevice |
Represents any Cisco Physical Device discovered on the network. |
|
equipmentHolderGeneric |
EquipmentHolder |
Represents any equipment container. |
|
equipmentGeneric |
Equipment |
Represents any piece of equipment (for example, Chassis, Backplane, Module). |
|
physicalPortGeneric |
PhysicalPort |
Represents any physical port. |
|
AtmMedia |
DeviceInterfaceConfigurationItem |
Represents an ATM media configuration that can be applied to an interface or sub-interface. |
|
VirtualChannelLink |
DeviceInterfaceConfigurationItem |
Represents a single Virtual Channel Link within an ATM Media configuration. |
|
VPI |
DeviceInterfaceConfigurationItem |
Holds the VPI value and is contained within the Virtual Channel Link. |
|
VCI |
DeviceInterfaceConfigurationItem |
Holds the VCI value and is contained within the Virtual Channel Link. |
|
VirtualChannelLinkData |
DeviceInterfaceConfigurationItem |
Contains the Virtual Channel Link characteristics and is contained with the Virtual Channel Link. |
|
AtmInterfaceConfigurationData |
DeviceInterfaceConfigurationItem |
Contains the ATM configuration applied to an interface. |
|
FrameRelayMedia |
DeviceInterfaceConfigurationItem |
Represents a Frame Relay media configuration that can be applied to an interface or sub-interface. |
|
DLCI |
DeviceInterfaceConfigurationItem |
Represents a single DLCI and is contained within a Frame Relay media configuration. |
|
FrameRelayData |
DeviceInterfaceConfigurationItem |
Contains the Frame Relay characteristics. |
|
FrameRelayExtendedData |
DeviceInterfaceConfigurationItem |
Contains additional Frame Relay characteristics. |
|
VlanMembership |
DeviceInterfaceConfigurationItem |
Represent the VLAN Membership media configuration that can be applied to an interface or sub-interface. |
|
Vlan |
DeviceInterfaceConfigurationItem |
Represents a single VLAN and is contained within a VLAN Membership. |
Example 6-1 shows a logical specification lineage. This lineage shows the intended relationship between specifications.
Example 6-1 Logical Specification Lineage
deviceGeneric
[0..*] interfaceGeneric
[0..1] GenericMedia
[0..1] IP Addresses
[0..*] IpAddress
IpAddress (characteristic)
Prefix (characteristic)
IpVersion (characteristic)
[0..1] Atm Media
[0..1] IP Addresses
[0..*] IpAddress
IpAddress (characteristic)
Prefix (characteristic)
IpVersion (characteristic)
[0..1] AtmInterfaceConfigurationData
[0..*] VirtualChannelLink
[0..1] VPI
[0..1] VCI
[0..1] VirtualChannelLinkData
[0..1] FrameRelayMedia
[0..1] IP Addresses
[0..*] IpAddress
IpAddress (characteristic)
Prefix (characteristic)
IpVersion (characteristic)
[0..*] DLCI
[0..1] FrameRelayData
[0..1] FrameRelatExtendedData
[0..1] VlanMembership
[0..1] IP Addresses
[0..*] IpAddress
IpAddress (characteristic)
Prefix (characteristic)
IpVersion (characteristic)
[0..*] Vlan
This section provides an example of a physical specification lineage.
Example 6-2 shows a physical specification lineage.
Table 6-3 shows the discovery action in the Cisco Router and Switch SNMP cartridge.
Table 6-3 Discover Generic Cisco SNMP Action
| Result Category | AddressHandler | Scan Parameters | Model | Processors |
|---|---|---|---|---|
|
Device |
IPAddressHandler |
Note: These scan parameters must be added for the Create Scan web service request even if the values are left empty. |
MIB-II Model and Cisco Model |
|
Figure 6-1 displays the Discover Generic Cisco SNMP action chain.
Table 6-4 shows the processors of the Discover Generic Cisco SNMP action.
Table 6-4 Discover Generic Cisco SNMP Action Processors
| Processor Name | Variable |
|---|---|
|
MIB-II Properties Initializer |
Input: N/A Output:
|
|
Cisco SNMP Properties Initializer |
Input: N/A Output:
|
|
CPU Property Initializer |
Input: N/A Output:
|
|
Cisco CPU Collector |
Input: N/A Output:
|
|
Device CPU Set Processor |
Input: N/A
Output: N/A |
|
CPU Utilization Compare Processor |
Input: N/A
Output: N/A |
|
MIB-II SNMP Collector |
Input: N/A Output:
|
|
MIB-II SNMP Modeler |
Input:
Output:
|
|
Cisco SNMP Logical Collector |
Input: N/A Output:
|
|
Cisco SNMP Physical Collector |
Input: N/A Output:
|
|
Cisco SNMP Logical Modeler |
Input:
Output:
|
|
Cisco SNMP Physical Modeler |
Input:
Output:
|