The On-Board Management Interface (OBMI) provides an
out-of-band communications channel (in Cisco terms:
a console port), that is capable of running on various
low-speed to high-speed satellite telemetry busses,
such as the m500 bus.
OBMI is similar to SNMP in principle and function, in
that it allows 'getting' data from or 'setting'
configurations in a device, however, OBMI is functional
regardless of the software state of the device. It
must be so, because OBMI is the primary control mechanism
for a device operating in the harsh environment of space.
OBMI transports command messages that originate from the
ground to a device in space and transports telemetry
messages that originate from that device in space to the
ground.
The OBMI application is divided into three conceptual layers:
1. The OBMI application layer which concerns operating system
subsystems and their associated command and telemetry
messages.
2. A FRAMING layer which formats the OBMI messages into
frames that are suitable for transport over a specific
spacecraft bus.
3. The PHY (physical) layer which handles sending and
receiving the frames over the physical media.
Counts associated with the success or failure of these
various transport layers are reported by this MIB.
GLOSSARY
command : data that goes from the ground to the device
in space
frame : OBMI messages are broken into frames to be
sent by the physical bus or reassembled from
the bus to be sent to the OBMI subsystem
m500 : A particular space command/telemetry bus
message : fully assembled set of frames that make up
commands or telemetry. The topmost OBMI
layer of the OBMI subsystem operates with
messages
OBMI : On-board Management Interface
telemetry : data that goes from the device in space to the
ground
word : a collection of bits, sized for the particular
bus
Parsed from file CISCO-OBMI-MIB.mib
Module: CISCO-OBMI-MIB
The On-Board Management Interface (OBMI) provides an
out-of-band communications channel (in Cisco terms:
a console port), that is capable of running on various
low-speed to high-speed satellite telemetry busses,
such as the m500 bus.
OBMI is similar to SNMP in principle and function, in
that it allows 'getting' data from or 'setting'
configurations in a device, however, OBMI is functional
regardless of the software state of the device. It
must be so, because OBMI is the primary control mechanism
for a device operating in the harsh environment of space.
OBMI transports command messages that originate from the
ground to a device in space and transports telemetry
messages that originate from that device in space to the
ground.
The OBMI application is divided into three conceptual layers:
1. The OBMI application layer which concerns operating system
subsystems and their associated command and telemetry
messages.
2. A FRAMING layer which formats the OBMI messages into
frames that are suitable for transport over a specific
spacecraft bus.
3. The PHY (physical) layer which handles sending and
receiving the frames over the physical media.
Counts associated with the success or failure of these
various transport layers are reported by this MIB.
GLOSSARY
command : data that goes from the ground to the device
in space
frame : OBMI messages are broken into frames to be
sent by the physical bus or reassembled from
the bus to be sent to the OBMI subsystem
m500 : A particular space command/telemetry bus
message : fully assembled set of frames that make up
commands or telemetry. The topmost OBMI
layer of the OBMI subsystem operates with
messages
OBMI : On-board Management Interface
telemetry : data that goes from the device in space to the
ground
word : a collection of bits, sized for the particular
bus
Parsed from file CISCO-OBMI-MIB.my.txt
Company: None
Module: CISCO-OBMI-MIB
The On-Board Management Interface (OBMI) provides an
out-of-band communications channel (in Cisco terms:
a console port), that is capable of running on various
low-speed to high-speed satellite telemetry busses,
such as the m500 bus.
OBMI is similar to SNMP in principle and function, in
that it allows 'getting' data from or 'setting'
configurations in a device, however, OBMI is functional
regardless of the software state of the device. It
must be so, because OBMI is the primary control mechanism
for a device operating in the harsh environment of space.
OBMI transports command messages that originate from the
ground to a device in space and transports telemetry
messages that originate from that device in space to the
ground.
The OBMI application is divided into three conceptual layers:
1. The OBMI application layer which concerns operating system
subsystems and their associated command and telemetry
messages.
2. A FRAMING layer which formats the OBMI messages into
frames that are suitable for transport over a specific
spacecraft bus.
3. The PHY (physical) layer which handles sending and
receiving the frames over the physical media.
Counts associated with the success or failure of these
various transport layers are reported by this MIB.
GLOSSARY
command : data that goes from the ground to the device
in space
frame : OBMI messages are broken into frames to be
sent by the physical bus or reassembled from
the bus to be sent to the OBMI subsystem
m500 : A particular space command/telemetry bus
message : fully assembled set of frames that make up
commands or telemetry. The topmost OBMI
layer of the OBMI subsystem operates with
messages
OBMI : On-board Management Interface
telemetry : data that goes from the device in space to the
ground
word : a collection of bits, sized for the particular
bus
ciscoObmiMIB MODULE-IDENTITY LAST-UPDATED "200905280000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The On-Board Management Interface (OBMI) provides an out-of-band communications channel (in Cisco terms: a console port), that is capable of running on various low-speed to high-speed satellite telemetry busses, such as the m500 bus. OBMI is similar to SNMP in principle and function, in that it allows 'getting' data from or 'setting' configurations in a device, however, OBMI is functional regardless of the software state of the device. It must be so, because OBMI is the primary control mechanism for a device operating in the harsh environment of space. OBMI transports command messages that originate from the ground to a device in space and transports telemetry messages that originate from that device in space to the ground. The OBMI application is divided into three conceptual layers: 1. The OBMI application layer which concerns operating system subsystems and their associated command and telemetry messages. 2. A FRAMING layer which formats the OBMI messages into frames that are suitable for transport over a specific spacecraft bus. 3. The PHY (physical) layer which handles sending and receiving the frames over the physical media. Counts associated with the success or failure of these various transport layers are reported by this MIB. GLOSSARY command : data that goes from the ground to the device in space frame : OBMI messages are broken into frames to be sent by the physical bus or reassembled from the bus to be sent to the OBMI subsystem m500 : A particular space command/telemetry bus message : fully assembled set of frames that make up commands or telemetry. The topmost OBMI layer of the OBMI subsystem operates with messages OBMI : On-board Management Interface telemetry : data that goes from the device in space to the ground word : a collection of bits, sized for the particular bus " REVISION "200905280000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 698 }
ciscoObmiMIB OBJECT IDENTIFIER ::= { ciscoMgmt 698 }
Vendor: Cisco
Module: CISCO-OBMI-MIB
[Automatically extracted from oidview.com]
ciscoObmiMIB MODULE-IDENTITY LAST-UPDATED "200905280000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The On-Board Management Interface (OBMI) provides an out-of-band communications channel (in Cisco terms: a console port), that is capable of running on various low-speed to high-speed satellite telemetry busses, such as the m500 bus. OBMI is similar to SNMP in principle and function, in that it allows 'getting' data from or 'setting' configurations in a device, however, OBMI is functional regardless of the software state of the device. It must be so, because OBMI is the primary control mechanism for a device operating in the harsh environment of space. OBMI transports command messages that originate from the ground to a device in space and transports telemetry messages that originate from that device in space to the ground. The OBMI application is divided into three conceptual layers: 1. The OBMI application layer which concerns operating system subsystems and their associated command and telemetry messages. 2. A FRAMING layer which formats the OBMI messages into frames that are suitable for transport over a specific spacecraft bus. 3. The PHY (physical) layer which handles sending and receiving the frames over the physical media. Counts associated with the success or failure of these various transport layers are reported by this MIB. GLOSSARY command : data that goes from the ground to the device in space frame : OBMI messages are broken into frames to be sent by the physical bus or reassembled from the bus to be sent to the OBMI subsystem m500 : A particular space command/telemetry bus message : fully assembled set of frames that make up commands or telemetry. The topmost OBMI layer of the OBMI subsystem operates with messages OBMI : On-board Management Interface telemetry : data that goes from the device in space to the ground word : a collection of bits, sized for the particular bus " REVISION "200905280000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 698 }
ciscoObmiMIB MODULE-IDENTITY LAST-UPDATED "200905280000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The On-Board Management Interface (OBMI) provides an out-of-band communications channel (in Cisco terms: a console port), that is capable of running on various low-speed to high-speed satellite telemetry busses, such as the m500 bus. OBMI is similar to SNMP in principle and function, in that it allows 'getting' data from or 'setting' configurations in a device, however, OBMI is functional regardless of the software state of the device. It must be so, because OBMI is the primary control mechanism for a device operating in the harsh environment of space. OBMI transports command messages that originate from the ground to a device in space and transports telemetry messages that originate from that device in space to the ground. The OBMI application is divided into three conceptual layers: 1. The OBMI application layer which concerns operating system subsystems and their associated command and telemetry messages. 2. A FRAMING layer which formats the OBMI messages into frames that are suitable for transport over a specific spacecraft bus. 3. The PHY (physical) layer which handles sending and receiving the frames over the physical media. Counts associated with the success or failure of these various transport layers are reported by this MIB. GLOSSARY command : data that goes from the ground to the device in space frame : OBMI messages are broken into frames to be sent by the physical bus or reassembled from the bus to be sent to the OBMI subsystem m500 : A particular space command/telemetry bus message : fully assembled set of frames that make up commands or telemetry. The topmost OBMI layer of the OBMI subsystem operates with messages OBMI : On-board Management Interface telemetry : data that goes from the device in space to the ground word : a collection of bits, sized for the particular bus " REVISION "200905280000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 698 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.698.0 | ciscoObmiMIBNotifs | 0 | 0 | None |
| 1.3.6.1.4.1.9.9.698.1 | ciscoObmiMIBObjects | 4 | 52 | None |
| 1.3.6.1.4.1.9.9.698.2 | ciscoObmiMIBConform | 2 | 5 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.648 | ciscoVirtualInterfaceMIB | 2 | 32 | The MIB module for creation and deletion of Virtual Interfaces and Virtual Interface Groups. In addition to this MIB, interface … |
| 1.3.6.1.4.1.9.9.650 | ciscoL4L7moduleRedundancyMIB | 3 | 71 | The L4-7 SLB devices are used for scaling websites, building web enabled applications, and migrating to web services. The followin… |
| 1.3.6.1.4.1.9.9.651 | ciscoCommonRolesExtMIB | 3 | 37 | A MIB Module for managing the roles that are common between access methods like Command Line Interface (CLI), SNMP and XML interf… |
| 1.3.6.1.4.1.9.9.652 | ciscoSwitchStatsMIB | 3 | 106 | The MIB module provides management information for configuration and monitoring of traffic statistics on Cisco's switching device… |
| 1.3.6.1.4.1.9.9.653 | ciscoAdmissionPolicyMIB | 3 | 36 | This MIB module defines managed objects that facilitate the management of policies upon host(s) admission to a network. The inform… |
| 1.3.6.1.4.1.9.9.654 | ciscoMabMIB | 3 | 20 | MIB module for monitoring and configuring MAC Authentication Bypass (MAB) feature in the system. MAC Auth Bypass feature provides… |
| 1.3.6.1.4.1.9.9.655 | ciscoDigitalMediaSystemsMIB | 3 | 195 | Acronyms and Definitions The following acronyms and terms are used in this document: DMS: Digital Media Systems DAM: Digital As… |
| 1.3.6.1.4.1.9.9.656 | ciscoAuthFrameworkMIB | 3 | 117 | MIB module for Authentication Framework in the system. Authentication Framework provides generic configurations for authenticatio… |
| 1.3.6.1.4.1.9.9.657 | ciscoSbcCallStatsMIB | 3 | 201 | The main purpose of this MIB is to define the statistics information for Session Border Controller application. The statistics ar… |
| 1.3.6.1.4.1.9.9.658 | ciscoSessBorderCtrlrEventMIB | 3 | 208 | The main purpose of this MIB is to define the SNMP notifications and alarms generated by Session Border Controller application an… |
| 1.3.6.1.4.1.9.9.660 | ciscoNportVirtualizationMIB | 3 | 19 | The MIB module for the management of N_port Virtualization or NPV within the framework of Cisco's N_port virtualization (NPV) Arc… |
| 1.3.6.1.4.1.9.9.661 | ciscoWan3gMIB | 3 | 378 | This MIB module provides network management support for Cisco cellular 3G WAN products. *** ABBREVIATIONS, ACRONYMS, AND SYMBOLS … |
| 1.3.6.1.4.1.9.9.662 | ciscoCbpTcMIB | 0 | 0 | This MIB module defines textual conventions used by the CISCO-CBP-BASE-CFG-MIB, CISCO-CBP-BASE-MON-MIB, and any MIB modules exten… |
| 1.3.6.1.4.1.9.9.663 | ciscoSwitchHardwareCapacityMIB | 3 | 141 | This MIB module defines the managed objects for hardware capacity of Cisco switching devices. The hardware capacity information c… |
| 1.3.6.1.4.1.9.9.664 | ciscoMmodalContactAppsMIB | 3 | 359 | The Cisco Unified Multi-Modal Contact Applications (MMCA) platform is a highly scalable, modular, extensible, open and secure pl… |
| 1.3.6.1.4.1.9.9.667 | ciscoServiceControllerMIB | 2 | 31 | This MIB module defines objects describing traffic controllers used by a service control entity. A service control entity is a ne… |
| 1.3.6.1.4.1.9.9.668 | ciscoP2PIfMIB | 3 | 16 | The Point to Point Interface MIB module. This MIB manages the generic objects for Serial link or SONET/SDH like point to point ne… |
| 1.3.6.1.4.1.9.9.669 | ciscoCdmaPdsnExtMIB | 3 | 178 | This MIB is an extension to the CISCO-CDMA-PDSN-MIB. A CDMA network supports wireless data communication through 3G CDMA radio acc… |
| 1.3.6.1.4.1.9.9.670 | ciscoReportIntervalTcMIB | 0 | 0 | CISCO-REPORT-INTERVAL-TC-MIB |
| 1.3.6.1.4.1.9.9.672 | ciscoMobilityTapMIB | 3 | 24 | This module manages Cisco's intercept feature for Mobility Gateway Products. This MIB is used along with CISCO-TAP2-MIB MIB to int… |
| 1.3.6.1.4.1.9.9.673 | ciscoFCoEMIB | 2 | 45 | This MIB module is for configuring and monitoring Fibre Channel over Ethernet (FCoE) related entities. This MIB defines the Virtu… |
| 1.3.6.1.4.1.9.9.679 | ciscoIeee8021CfmExtMIB | 3 | 55 | A MIB module for extending the IEEE8021-CFM-MIB and IEEE8021-CFM-V2-MIB to add objects which provide additional information about… |
| 1.3.6.1.4.1.9.9.680 | ciscoNhrpExtMIB | 3 | 36 | This MIB module is an extension of the NHRP MIB module as defined in RFC 2677. It defines notifications associated with critical … |
| 1.3.6.1.4.1.9.9.683 | ciscoEnergywiseMIB | 3 | 162 | The MIB is used to manage and optimize power usage in networks. Cisco EnergyWise is a specification of data, discovery and protoco… |
| 1.3.6.1.4.1.9.9.686 | ciscoLwappInterfaceMIB | 3 | 27 | ciscoLwappInterfaceMIB MODULE-IDENTITY LAST-UPDATED "200901090000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO "Cisco Syste… |
| 1.3.6.1.4.1.9.9.688 | ciscoFlowMonitorTcMIB | 0 | 0 | This MIB module defines textual conventions used by the MIB modules defining objects describing flow monitoring. GLOSSARY ========… |
| 1.3.6.1.4.1.9.9.689 | ciscoSlbDfpMIB | 3 | 22 | This MIB reports the congestion status of the real server. A server can be in congested state due to high memory consumption, hig… |
| 1.3.6.1.4.1.9.9.690 | ciscoMobilePolicyChargingControlMIB | 3 | 143 | Mobile PCC Infrastructure built on top of Policy Shim Layer, is a common interface to send and receive PCC related messages for a… |
| 1.3.6.1.4.1.9.9.691 | ciscoEthernetFabricExtenderMIB | 3 | 23 | The MIB module for configuring one or more fabric extenders to connect into a core switch. Since fabric extenders might not be m… |
| 1.3.6.1.4.1.9.9.692 | ciscoFlowMonitorMIB | 4 | 195 | This MIB module defines objects that describe flow monitoring. A typical application of this MIB module will facilitate monitorin… |
| 1.3.6.1.4.1.9.9.693 | ciscoServiceControlAttackMIB | 3 | 55 | This MIB provides data related to different types of attacks detected by a service control entity. A service control entity is a … |
| 1.3.6.1.4.1.9.9.694 | ciscoCtsTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Trusted Security framework. |
| 1.3.6.1.4.1.9.9.695 | ciscoGtcapMIB | 3 | 194 | The MIB for Transaction Capabilities(TCAP) messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Transfer P… |
| 1.3.6.1.4.1.9.9.696 | ciscoBootHwDiagsMIB | 3 | 22 | This MIB is used to configure those devices that support boot-time hardware diagnostics. It provides the reports about the respe… |
| 1.3.6.1.4.1.9.9.697 | ciscoIpCbrMetricsMIB | 4 | 42 | This MIB module defines objects that describe the a set of metrics used to measure the quality of a IP CBR traffic flow. An IP CB… |
| 1.3.6.1.4.1.9.9.699 | ciscoMdiMetricsMIB | 4 | 46 | This MIB module defines objects that describe the Media Delivery Index (MDI). The MDI [RFC4445] measurement describes the qualit… |
| 1.3.6.1.4.1.9.9.700 | ciscoCableL2vpnMIB | 3 | 28 | This MIB module defines managed objects that facilitate the management of Cisco devices complying to the DOCSIS L2VPN Feature for… |
| 1.3.6.1.4.1.9.9.701 | ciscoSeuMitigationMIB | 3 | 51 | This MIB reports the status of non-automatic and automatic, rate-adaptive Single Event Upset (SEU) mitigation algorithms and adju… |
| 1.3.6.1.4.1.9.9.702 | ciscoSanBaseSvcMIB | 3 | 57 | Common MIB module to manage services in Storage Area Network (SAN). Service is deployed on service nodes on multiple switches fo… |
| 1.3.6.1.4.1.9.9.703 | ciscoRtpMetricsMIB | 4 | 61 | This MIB module defines objects that describe the quality metrics of RTP streams, similar to those described by an RTCP Receiver … |
| 1.3.6.1.4.1.9.9.706 | ciscoInterfaceXcvrMonitorMIB | 3 | 33 | A MIB module that provides monitoring information about the transceivers plugged into interface on a system. |
| 1.3.6.1.4.1.9.9.708 | ciscoContentDeliveryStreamingMIB | 2 | 30 | This MIB instrumentation is for managing the Content Delivery and Streaming functionality on Cisco devices. Contents are ingested… |
| 1.3.6.1.4.1.9.9.709 | ciscoVlanGroupMIB | 3 | 18 | MIB module for monitoring and configuring VLAN Group Mapping information. |
| 1.3.6.1.4.1.9.9.710 | ciscoVirtualNicMIB | 3 | 36 | This MIB module defines MIB objects which provide mechanisms to manage the parameters used by or related to Virtual NIC. Virtual s… |
| 1.3.6.1.4.1.9.9.711 | ciscoVrfMIB | 3 | 48 | The MIB module for provisioning and managing network virtualization features. This module provides manageability for VRF, VRF-Lit… |
| 1.3.6.1.4.1.9.9.712 | ciscoWirelessNotificationMIB | 3 | 30 | This MIB is intended to be implemented on those Network Management applications that manage a network of wireless devices through… |
| 1.3.6.1.4.1.9.9.713 | ciscoTrustSecPolicyMIB | 3 | 204 | This MIB module defines managed objects that facilitate the management of various policies within the Cisco Trusted Security (Tru… |
| 1.3.6.1.4.1.9.9.714 | ciscoHwModuleControlMIB | 3 | 27 | The MIB module providing configuration and control information for management of hardware modules and components on Cisco devices… |
| 1.3.6.1.4.1.9.9.715 | ciscoEntityQfpMIB | 3 | 82 | This MIB module defines managed objects that facilitate the management of Quantum Flow Processors (QFP), which are listed in the … |
| 1.3.6.1.4.1.9.9.716 | ciscoVoIpTapMIB | 3 | 18 | This module manages Cisco's intercept feature for Voice over IP (VoIP). This MIB is used along with CISCO-TAP2-MIB to intercept V… |
| 1.3.6.1.4.1.9.9.718 | ciscoCuicappsMIB | 3 | 130 | The Cisco Unified Intelligence Center (CUIC) is a scalable robust and secure reporting solution for contact center applications. T… |
| 1.3.6.1.4.1.9.9.719 | ciscoUnifiedComputingMIB | 5 | 13463 | This MIB module defines the managed objects for Unified Computing System (UCS) Manager. Cisco UCS Manager provides centralized m… |
| 1.3.6.1.4.1.9.9.720 | ciscoTrustSecSxpMIB | 3 | 140 | This MIB module is for the configuration and status query of SGT Exchange Protocol over TCP (SXPoTCP) feature of the device on th… |
| 1.3.6.1.4.1.9.9.721 | ciscoMldSnoopingMIB | 3 | 215 | This MIB module defines objects that describe IGMP/MLD snooping. It provides remote network management system the ability to manag… |
| 1.3.6.1.4.1.9.9.724 | cggsnGeoMIB | 2 | 12 | This MIB provide additional information for passive interface configured for each OSPF process, independent of object creation in… |
| 1.3.6.1.4.1.9.9.725 | ciscoSmartInstallMIB | 3 | 101 | This MIB module defines managed objects that facilitate the management of Smart Install feature. Smart Install is a plug-and-pla… |
| 1.3.6.1.4.1.9.9.729 | ciscoCdstvServicesMIB | 3 | 21 | This MIB module defines service monitoring objects that faciliate the management of the Cisco Content Delivery System for TV (CDS… |
| 1.3.6.1.4.1.9.9.730 | ciscoTrustSecMIB | 3 | 128 | This MIB module is for the configuration of a network device on the Cisco Trusted Security (TrustSec) system. TrustSec secures a … |
| 1.3.6.1.4.1.9.9.731 | ciscoEpcGatewayMIB | 3 | 130 | This MIB module manages the features and configuration for PDN Gateway(PGW) and Serving Gateway(SGW) in Evolved Packet Core(EPC) … |
| 1.3.6.1.4.1.9.9.732 | ciscoDeviceLocationMIB | 3 | 49 | This MIB is used for managing location information of end point devices(Telepresence, IP Camera, Digital media player etc) connec… |
| 1.3.6.1.4.1.9.9.733 | ciscoMeetingPlaceMIB | 3 | 70 | This MIB allows management of Cisco Unified MeetingPlace (CUMP) features, CUMP is the key conferencing solution component for Cis… |
| 1.3.6.1.4.1.9.9.734 | ciscoGtpv2MIB | 2 | 160 | This MIB module manages the GPRS Tunneling Protocol version 2(GTPv2) statistics for the Evolved Packet Core(EPC) architecture. SGW… |
| 1.3.6.1.4.1.9.9.735 | ciscoCdstvFsiMIB | 3 | 25 | This MIB module defines FSI configurartion objects that faciliate the management of the Cisco Content Delivery System for TV (CDS… |
| 1.3.6.1.4.1.9.9.736 | ciscoRadiusExtMIB | 2 | 51 | This MIB module defines objects describing RADIUS (Remote Access Dialin User Service), serving as an extension of the following M… |
| 1.3.6.1.4.1.9.9.737 | ciscoSwitchNetflowMIB | 3 | 40 | This MIB module defines management objects for the Netflow features on Cisco Layer 2 and Layer 3 devices. |
| 1.3.6.1.4.1.9.9.738 | cmplsTeStdExtMIB | 3 | 72 | This MIB module contains Cisco specific managed object definitions for MPLS Traffic Engineering (TE), not contained in MPLS-TE-ST… |
| 1.3.6.1.4.1.9.9.739 | ciscoCdstvIngestmgrMIB | 3 | 69 | This MIB module defines ingest manager configuration objects that faciliate the management of the Cisco Content Delivery System f… |
| 1.3.6.1.4.1.9.9.740 | ciscoTrustSecIfMIB | 3 | 143 | This MIB module defines management objects for configuration and monitoring of the interfaces in Cisco Trusted Security environme… |
| 1.3.6.1.4.1.9.9.741 | ciscoTrustSecServerMIB | 3 | 85 | This MIB module defines management objects for configuration and monitoring of the AAA servers in Cisco Trusted Security environm… |
| 1.3.6.1.4.1.9.9.742 | ciscoIpAddressPoolTcMIB | 0 | 0 | This MIB module defines textual conventions used by MIB modules defining objects describing IP address pools. |
| 1.3.6.1.4.1.9.9.743 | ciscoCdstvCsStatsMIB | 3 | 83 | This MIB module defines objects describing the caching and streaming statistics objects that facilitate the management of the Cis… |
| 1.3.6.1.4.1.9.9.744 | ciscoIpslaVideoMIB | 3 | 73 | IP SLA is a capability which utilizes active monitoring for network performance. It can be used for network troubleshooting, net… |
| 1.3.6.1.4.1.9.9.745 | ciscoEntitySensorExtMIB | 3 | 21 | This MIB is extension to ENTITY-SENSOR-MIB(RFC 3433). This MIB also defines the notifications applicable for sensors reported in … |
| 1.3.6.1.4.1.9.9.748 | ciscoIpAddressPoolMIB | 3 | 96 | This MIB modules defines objects that describe common aspects of IP address pools. IP Address Pool Manager =======================… |
| ... | ||||