This module provides a subtree to define OIDs so that
various routing 'policies' used by Cisco routers can be
expressed. This module defines only this 'policy' OID
space and doesn't define any other object.
As an example, these OIDs are required by at least the
following MIB objects: inetCidrRoutePolicy
( IP-FORWARD-MIB, RFC4292 ) and
mplsL3VpnVrfRteInetCidrPolicy ( MPLS-L3VPN-STD-MIB
RCS4382). Both of these objects are defined as OBJECT
IDENTIFIERs without any defined semantics, to
differentiate between multiple entries to the same
destination in the tables inetCidrRoutePolicyTable and
mplsL3VpnVrfRteInetCidrTable. These two objects
utilise a generalised notion of 'policy' defined in
this module.
The table inetCidrRouteTable of IP-FORWARD-MIB may list
multiple paths pointing out of (either):
* different interfaces with the same next-hop
ipv6 route 2003::/64 interface gig0/0 2222::1
ipv6 route 2003::/64 interface gig0/1 2222::1
* different interfaces with no next-hop
ipv6 route 2003::/64 interface gig0/0
ipv6 route 2003::/64 interface gig0/1
2003::/64 and 2222::1 represent an IPv6 route-prefix
and IPv6 next-hop respectively.
If these interfaces were in different zones, then the
'InetAddressIPv6z' type next-hop could distinguish
them. If they are in the same zone, then the two
interfaces refer to the same link.
The indices of inetCidrRouteTable are:
inetCidrRouteDestType
inetCidrRouteDest
inetCidrRoutePfxLen
inetCidrRoutePolicy
inetCidrRouteNextHopType
inetCidrRouteNextHop
The inetCidrRoutePolicy object, when instantiated with a
value from crpPolicyIfIndex, allows us to distinguish
the routing table entries mentioned in the examples
above.
REFERENCE
[1] IP-FORWARD-MIB (RFC4292)
[2] MPLS-L3VPN-STD-MIB (RFC4382)
[3] ifIndex, IF-MIB
[4] RFC 4291 IP Version 6 Addressing Architecture,
Section 2.2, Text Representation of Addresses.
Parsed from file CISCO-ROUTE-POLICIES-MIB.mib
Module: CISCO-ROUTE-POLICIES-MIB
This module provides a subtree to define OIDs so that
various routing 'policies' used by Cisco routers can be
expressed. This module defines only this 'policy' OID
space and doesn't define any other object.
As an example, these OIDs are required by at least the
following MIB objects: inetCidrRoutePolicy
( IP-FORWARD-MIB, RFC4292 ) and
mplsL3VpnVrfRteInetCidrPolicy ( MPLS-L3VPN-STD-MIB
RCS4382). Both of these objects are defined as OBJECT
IDENTIFIERs without any defined semantics, to
differentiate between multiple entries to the same
destination in the tables inetCidrRoutePolicyTable and
mplsL3VpnVrfRteInetCidrTable. These two objects
utilise a generalised notion of 'policy' defined in
this module.
The table inetCidrRouteTable of IP-FORWARD-MIB may list
multiple paths pointing out of (either):
* different interfaces with the same next-hop
ipv6 route 2003::/64 interface gig0/0 2222::1
ipv6 route 2003::/64 interface gig0/1 2222::1
* different interfaces with no next-hop
ipv6 route 2003::/64 interface gig0/0
ipv6 route 2003::/64 interface gig0/1
2003::/64 and 2222::1 represent an IPv6 route-prefix
and IPv6 next-hop respectively.
If these interfaces were in different zones, then the
'InetAddressIPv6z' type next-hop could distinguish
them. If they are in the same zone, then the two
interfaces refer to the same link.
The indices of inetCidrRouteTable are:
inetCidrRouteDestType
inetCidrRouteDest
inetCidrRoutePfxLen
inetCidrRoutePolicy
inetCidrRouteNextHopType
inetCidrRouteNextHop
The inetCidrRoutePolicy object, when instantiated with a
value from crpPolicyIfIndex, allows us to distinguish
the routing table entries mentioned in the examples
above.
REFERENCE
[1] IP-FORWARD-MIB (RFC4292)
[2] MPLS-L3VPN-STD-MIB (RFC4382)
[3] ifIndex, IF-MIB
[4] RFC 4291 IP Version 6 Addressing Architecture,
Section 2.2, Text Representation of Addresses.
Parsed from file CISCO-ROUTE-POLICIES-MIB.my.txt
Company: None
Module: CISCO-ROUTE-POLICIES-MIB
This module provides a subtree to define OIDs so that
various routing 'policies' used by Cisco routers can be
expressed. This module defines only this 'policy' OID
space and doesn't define any other object.
As an example, these OIDs are required by at least the
following MIB objects: inetCidrRoutePolicy
( IP-FORWARD-MIB, RFC4292 ) and
mplsL3VpnVrfRteInetCidrPolicy ( MPLS-L3VPN-STD-MIB
RCS4382). Both of these objects are defined as OBJECT
IDENTIFIERs without any defined semantics, to
differentiate between multiple entries to the same
destination in the tables inetCidrRoutePolicyTable and
mplsL3VpnVrfRteInetCidrTable. These two objects
utilise a generalised notion of 'policy' defined in
this module.
The table inetCidrRouteTable of IP-FORWARD-MIB may list
multiple paths pointing out of (either):
* different interfaces with the same next-hop
ipv6 route 2003::/64 interface gig0/0 2222::1
ipv6 route 2003::/64 interface gig0/1 2222::1
* different interfaces with no next-hop
ipv6 route 2003::/64 interface gig0/0
ipv6 route 2003::/64 interface gig0/1
2003::/64 and 2222::1 represent an IPv6 route-prefix
and IPv6 next-hop respectively.
If these interfaces were in different zones, then the
'InetAddressIPv6z' type next-hop could distinguish
them. If they are in the same zone, then the two
interfaces refer to the same link.
The indices of inetCidrRouteTable are:
inetCidrRouteDestType
inetCidrRouteDest
inetCidrRoutePfxLen
inetCidrRoutePolicy
inetCidrRouteNextHopType
inetCidrRouteNextHop
The inetCidrRoutePolicy object, when instantiated with a
value from crpPolicyIfIndex, allows us to distinguish
the routing table entries mentioned in the examples
above.
REFERENCE
[1] IP-FORWARD-MIB (RFC4292)
[2] MPLS-L3VPN-STD-MIB (RFC4382)
[3] ifIndex, IF-MIB
[4] RFC 4291 IP Version 6 Addressing Architecture,
Section 2.2, Text Representation of Addresses.
ciscoRoutePoliciesMIB MODULE-IDENTITY LAST-UPDATED "200608180000Z" 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 "This module provides a subtree to define OIDs so that various routing 'policies' used by Cisco routers can be expressed. This module defines only this 'policy' OID space and doesn't define any other object. As an example, these OIDs are required by at least the following MIB objects: inetCidrRoutePolicy ( IP-FORWARD-MIB, RFC4292 ) and mplsL3VpnVrfRteInetCidrPolicy ( MPLS-L3VPN-STD-MIB RCS4382). Both of these objects are defined as OBJECT IDENTIFIERs without any defined semantics, to differentiate between multiple entries to the same destination in the tables inetCidrRoutePolicyTable and mplsL3VpnVrfRteInetCidrTable. These two objects utilise a generalised notion of 'policy' defined in this module. The table inetCidrRouteTable of IP-FORWARD-MIB may list multiple paths pointing out of (either): * different interfaces with the same next-hop ipv6 route 2003::/64 interface gig0/0 2222::1 ipv6 route 2003::/64 interface gig0/1 2222::1 * different interfaces with no next-hop ipv6 route 2003::/64 interface gig0/0 ipv6 route 2003::/64 interface gig0/1 2003::/64 and 2222::1 represent an IPv6 route-prefix and IPv6 next-hop respectively. If these interfaces were in different zones, then the 'InetAddressIPv6z' type next-hop could distinguish them. If they are in the same zone, then the two interfaces refer to the same link. The indices of inetCidrRouteTable are: inetCidrRouteDestType inetCidrRouteDest inetCidrRoutePfxLen inetCidrRoutePolicy inetCidrRouteNextHopType inetCidrRouteNextHop The inetCidrRoutePolicy object, when instantiated with a value from crpPolicyIfIndex, allows us to distinguish the routing table entries mentioned in the examples above. REFERENCE [1] IP-FORWARD-MIB (RFC4292) [2] MPLS-L3VPN-STD-MIB (RFC4382) [3] ifIndex, IF-MIB [4] RFC 4291 IP Version 6 Addressing Architecture, Section 2.2, Text Representation of Addresses. " REVISION "200608180000Z" DESCRIPTION "Initial version of this MIB module. " ::= { ciscoMgmt 578 }
ciscoRoutePoliciesMIB OBJECT IDENTIFIER ::= { ciscoMgmt 578 }
Vendor: Cisco
Module: CISCO-ROUTE-POLICIES-MIB
[Automatically extracted from oidview.com]
ciscoRoutePoliciesMIB MODULE-IDENTITY LAST-UPDATED "200608180000Z" 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 "This module provides a subtree to define OIDs so that various routing 'policies' used by Cisco routers can be expressed. This module defines only this 'policy' OID space and doesn't define any other object. As an example, these OIDs are required by at least the following MIB objects: inetCidrRoutePolicy ( IP-FORWARD-MIB, RFC4292 ) and mplsL3VpnVrfRteInetCidrPolicy ( MPLS-L3VPN-STD-MIB RCS4382). Both of these objects are defined as OBJECT IDENTIFIERs without any defined semantics, to differentiate between multiple entries to the same destination in the tables inetCidrRoutePolicyTable and mplsL3VpnVrfRteInetCidrTable. These two objects utilise a generalised notion of 'policy' defined in this module. The table inetCidrRouteTable of IP-FORWARD-MIB may list multiple paths pointing out of (either): * different interfaces with the same next-hop ipv6 route 2003::/64 interface gig0/0 2222::1 ipv6 route 2003::/64 interface gig0/1 2222::1 * different interfaces with no next-hop ipv6 route 2003::/64 interface gig0/0 ipv6 route 2003::/64 interface gig0/1 2003::/64 and 2222::1 represent an IPv6 route-prefix and IPv6 next-hop respectively. If these interfaces were in different zones, then the 'InetAddressIPv6z' type next-hop could distinguish them. If they are in the same zone, then the two interfaces refer to the same link. The indices of inetCidrRouteTable are: inetCidrRouteDestType inetCidrRouteDest inetCidrRoutePfxLen inetCidrRoutePolicy inetCidrRouteNextHopType inetCidrRouteNextHop The inetCidrRoutePolicy object, when instantiated with a value from crpPolicyIfIndex, allows us to distinguish the routing table entries mentioned in the examples above. REFERENCE [1] IP-FORWARD-MIB (RFC4292) [2] MPLS-L3VPN-STD-MIB (RFC4382) [3] ifIndex, IF-MIB [4] RFC 4291 IP Version 6 Addressing Architecture, Section 2.2, Text Representation of Addresses. " REVISION "200608180000Z" DESCRIPTION "Initial version of this MIB module. " ::= { ciscoMgmt 578 }
ciscoRoutePoliciesMIB MODULE-IDENTITY LAST-UPDATED "200608180000Z" 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 "This module provides a subtree to define OIDs so that various routing 'policies' used by Cisco routers can be expressed. This module defines only this 'policy' OID space and doesn't define any other object. As an example, these OIDs are required by at least the following MIB objects: inetCidrRoutePolicy ( IP-FORWARD-MIB, RFC4292 ) and mplsL3VpnVrfRteInetCidrPolicy ( MPLS-L3VPN-STD-MIB RCS4382). Both of these objects are defined as OBJECT IDENTIFIERs without any defined semantics, to differentiate between multiple entries to the same destination in the tables inetCidrRoutePolicyTable and mplsL3VpnVrfRteInetCidrTable. These two objects utilise a generalised notion of 'policy' defined in this module. The table inetCidrRouteTable of IP-FORWARD-MIB may list multiple paths pointing out of (either): * different interfaces with the same next-hop ipv6 route 2003::/64 interface gig0/0 2222::1 ipv6 route 2003::/64 interface gig0/1 2222::1 * different interfaces with no next-hop ipv6 route 2003::/64 interface gig0/0 ipv6 route 2003::/64 interface gig0/1 2003::/64 and 2222::1 represent an IPv6 route-prefix and IPv6 next-hop respectively. If these interfaces were in different zones, then the 'InetAddressIPv6z' type next-hop could distinguish them. If they are in the same zone, then the two interfaces refer to the same link. The indices of inetCidrRouteTable are: inetCidrRouteDestType inetCidrRouteDest inetCidrRoutePfxLen inetCidrRoutePolicy inetCidrRouteNextHopType inetCidrRouteNextHop The inetCidrRoutePolicy object, when instantiated with a value from crpPolicyIfIndex, allows us to distinguish the routing table entries mentioned in the examples above. REFERENCE [1] IP-FORWARD-MIB (RFC4292) [2] MPLS-L3VPN-STD-MIB (RFC4382) [3] ifIndex, IF-MIB [4] RFC 4291 IP Version 6 Addressing Architecture, Section 2.2, Text Representation of Addresses. " REVISION "200608180000Z" DESCRIPTION "Initial version of this MIB module. " ::= { ciscoMgmt 578 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.578.0 | ciscoRoutePoliciesMIBNotifs | 0 | 0 | None |
| 1.3.6.1.4.1.9.9.578.1 | ciscoRoutePoliciesMIBObjects | 1 | 2 | None |
| 1.3.6.1.4.1.9.9.578.2 | ciscoRoutePoliciesMIBConform | 0 | 0 | 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.529 | ciscoItpMsuRatesMIB | 3 | 61 | This MIB provides information used to manage the number of MTP3 MSUs transmitted and received per processor. Many of the higher … |
| 1.3.6.1.4.1.9.9.530 | ciscoNacTcMIB | 0 | 0 | This module defines the textual conventions for Cisco Network Admission Control(NAC) system. The Cisco Network Admission Control … |
| 1.3.6.1.4.1.9.9.532 | ciscoNATExtMIB | 3 | 13 | This MIB is an extension to the NAT-MIB. This MIB module includes objects for providing the NAT related statistics. Acronyms: NAT… |
| 1.3.6.1.4.1.9.9.533 | ciscoCbpTargetMIB | 3 | 25 | This MIB module defines the managed objects for representing targets which have class-based policy mappings. A target can be any… |
| 1.3.6.1.4.1.9.9.543 | ciscoLicenseMgmtMIB | 3 | 131 | The MIB module for managing licenses on the system. The licensing mechanism provides flexibility to enforce licensing for various… |
| 1.3.6.1.4.1.9.9.548 | ciscoErrDisableMIB | 3 | 43 | This MIB module provides the ability for a Network Management Station (NMS) to configure and monitor the error-disable feature vi… |
| 1.3.6.1.4.1.9.9.572 | ciscoRttMonIPExtMIB | 2 | 38 | This MIB contains extensions to tables in CISCO-RTTMON-MIB to support IP-layer extensions, specifically IPv6 addresses and other … |
| 1.3.6.1.4.1.9.9.573 | ciscoQosTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Qos MIBs. |
| 1.3.6.1.4.1.9.9.576 | ciscoLwappMobilityMIB | 3 | 60 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.577 | ciscoLwappAclMIB | 3 | 26 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.580 | ciscoSwitchQosMIB | 3 | 295 | This MIB module extends the CISCO-CLASS-BASED-QOS-MIB by defining configuration and statistics information specific to the qualit… |
| 1.3.6.1.4.1.9.9.583 | ciscoGslbTcMIB | 0 | 0 | This MIB module defines Textual Conventions and OBJECT-IDENTITIES for use in documents defining management information base (MIBs… |
| 1.3.6.1.4.1.9.9.584 | ciscoEntityDiagTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Entity Diag MIB. |
| 1.3.6.1.4.1.9.9.585 | ciscoIpSlaEthernetMIB | 3 | 194 | This MIB module consists of two parts. 1) Auto-Ethernet-CFM Control: | | 2) ethernetJitter Stats: | | The first part defines a mechani… |
| 1.3.6.1.4.1.9.9.586 | ciscoNotificationControlMIB | 2 | 28 | This MIB provides network management support to regulate the transmission of notifications generated by a system providing networ… |
| 1.3.6.1.4.1.9.9.589 | ciscoGslbSystemMIB | 3 | 103 | This MIB module defines objects for network and system information of Global Server Load Balancer(GSLB) as a network device. A G… |
| 1.3.6.1.4.1.9.9.590 | ciscoCvpMIB | 3 | 255 | The Cisco Unified Customer Voice Portal (CVP) application integrates with both traditional time-division multiplexing (TDM) and I… |
| 1.3.6.1.4.1.9.9.592 | ciscoPrefPathMIB | 3 | 56 | The MIB module for the management of preferred path. This MIB enables managers to configure and monitor Preferred Path parameters.… |
| 1.3.6.1.4.1.9.9.593 | ciscoFcSdvMIB | 3 | 28 | This MIB instrumentation is for managing Fibre Channel (FC) SAN Device Virtualization (SDV) solution on Cisco Fibre Channel devic… |
| 1.3.6.1.4.1.9.9.594 | ciscoApplicationAccelerationMIB | 3 | 37 | This is a MIB for managing Application Acceleration System(s). This MIB includes instrumentation for providing the performance st… |
| 1.3.6.1.4.1.9.9.595 | ciscoGslbDnsMIB | 3 | 165 | The MIB defines objects for status and statistics information of DNS related operations of Global Server Load Balancer(GSLB). Th… |
| 1.3.6.1.4.1.9.9.597 | ciscoContentServicesMIB | 3 | 349 | Content Service is a capability to examine IP/TCP/UDP headers, payload and enable billing based on the content being provided. Ab… |
| 1.3.6.1.4.1.9.9.598 | ciscoLwappAAAMIB | 3 | 73 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC), that terminate the Light Weigh… |
| 1.3.6.1.4.1.9.9.599 | ciscoLwappDot11ClientMIB | 4 | 49 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.600 | ciscoGslbHealthMonMIB | 3 | 90 | The MIB defines objects related to global keepalive properties in GSLB devices. It contains the tables for keep alive configurat… |
| 1.3.6.1.4.1.9.9.601 | ciscoResilientEthernetProtocolMIB | 3 | 77 | This MIB module defines objects required for managing Resilient Ethernet Protocol (REP). Resilient Ethernet Protocol (REP) is a C… |
| 1.3.6.1.4.1.9.9.602 | ciscoPacketCaptureMIB | 3 | 103 | The MIB module for the management of packet capture feature. |
| 1.3.6.1.4.1.9.9.603 | ciscoThreatMitigationServiceMIB | 3 | 68 | This MIB provides management information about the Threat Mitigation Service(TMS) entity named 'Consumer'. TMS is part of Cisco's… |
| 1.3.6.1.4.1.9.9.604 | cdot1CfmMIB | 3 | 166 | Connectivity Fault Management module for managing IEEE 802.1ag |
| 1.3.6.1.4.1.9.9.606 | ciscoLwappMeshLinkTestMIB | 3 | 46 | ciscoLwappMeshLinkTestMIB MODULE-IDENTITY LAST-UPDATED "200702050000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO "Cisco Sy… |
| 1.3.6.1.4.1.9.9.607 | ciscoDot11HtPhyMIB | 3 | 71 | This MIB is intended to be implemented on Cisco's WLAN devices that provide the wired uplink to wireless clients through the high… |
| 1.3.6.1.4.1.9.9.610 | ciscoLwappRogueMIB | 3 | 78 | This MIB is intended to be implemented on all those devices operating as Central Controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.611 | ciscoLwappDot11ClientCCXTextualConventions | 0 | 0 | This module defines the textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Cont… |
| 1.3.6.1.4.1.9.9.612 | ciscoLwappDot11MIB | 3 | 17 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.613 | ciscoEvcMIB | 3 | 156 | Metro Ethernet services can support a wide range of applications and subscriber needs easily, efficiently and cost-effectively. … |
| 1.3.6.1.4.1.9.9.614 | ciscoLwappDot11LdapMIB | 3 | 33 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.615 | ciscoLwappRrmMIB | 3 | 28 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.616 | ciscoLwappMeshMIB | 3 | 121 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.617 | ciscoLwappMeshStatsMIB | 4 | 98 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.618 | ciscoLwappSysMIB | 3 | 163 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.619 | ciscoLwappLocalAuthMIB | 3 | 53 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.620 | ciscoLwappMeshBatteryMIB | 3 | 34 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.621 | ciscoH324DialControlMIB | 2 | 34 | This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing H.324 call information over a telephony network. ITU-T R… |
| 1.3.6.1.4.1.9.9.622 | ciscoLwappDot11ClientTsMIB | 3 | 34 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.623 | ciscoLwappCdpMIB | 3 | 51 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.624 | ciscoIpSlaTCMIB | 0 | 0 | This MIB contains textual conventions used by CISCO IPSLA MIBs. Acronyms: FEC: Forward Equivalence Class LPD: Label Path Discovery L… |
| 1.3.6.1.4.1.9.9.626 | ciscoDot11HtMacMIB | 3 | 40 | This MIB is intended to be implemented on Cisco's WLAN devices that provide the wired uplink to wireless clients through the high… |
| 1.3.6.1.4.1.9.9.627 | ciscoDot11RadarMIB | 3 | 25 | This MIB module is for IEEE 802.11a/h Root device, i.e. Access Point (AP) or Root Bridge. This MIB allows dynamic frequency selec… |
| 1.3.6.1.4.1.9.9.628 | ciscoServiceControlSubscribersMIB | 3 | 37 | This MIB provides global and specific information on subscribers managed by a service control entity, which is a network element … |
| ... | ||||