CISCOSB-rlIP-MIB
The CISCOSB-rlIP-MIB module monitors Cisco Secure Borderless Network (CISCOSB) devices to expose the status and configuration details of IPv6 addresses automatically assigned via stateless address autoconfiguration (SLAAC). It provides visibility into the specific IPv6 address representations generated by the router's auto-configuration mechanisms for operational tracking and troubleshooting.
Imported Objects
Objects
17 total| Object Name |
|---|
rlIpThe private MIB module definition for Auto Configured IPv6 Address representation. MODULE-IDENTITY .1.3.6.1.4.1.9.6.1.101.250 |
rlIpAddressTableThis table contains addressing information relevant to the entity's interfaces. in addition to ipAddressTable defined in standard MIB a represenattion of IPv6 addresses based on additionl address origin such as EUI-64, general prefix etc. In this case the address information is partial address information. Together with the address origin and the general prefix (when needed) user can construct full address information. The index (key) for this table includes this information additionally to the address. SEQUENCE OF RlIpAddressEntry .1.3.6.1.4.1.9.6.1.101.250.1 |
rlIpAddressEntryAn address mapping for a particular interface. RlIpAddressEntry .1.3.6.1.4.1.9.6.1.101.250.1.1 |
rlIpAddressAddrTypeThe address type of rlIpAddressAddr. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.6.1.101.250.1.1.1 |
rlIpAddressAddrThe IP address to which this entry's addressing information pertains. The address type of this object is specified in rlIpAddressAddrType. In case of auto-configure address such as eui-64, general-prefix and others it contains the partial address before appropriate manipulation. Implementors need to be aware that if the size of rlIpAddressAddr exceeds 116 octets, then OIDS of instances of columns in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.6.1.101.250.1.1.2 |
rlIpAddressOriginThe origin of the address. IpAddressOriginTC -- .1.3.6.1.4.1.9.6.1.101.250.1.1.3 |
rlIpAddressGeneralPrefixNameThe name assigned to the prefix. DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.250.1.1.4 |
rlIpAddressIfIndexThe index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.rw InterfaceIndex (IF-MIB) .1.3.6.1.4.1.9.6.1.101.250.1.1.5 |
rlIpAddressExtdTypeExtend standard field ipAddressType to multicastrw Enumeration .1.3.6.1.4.1.9.6.1.101.250.1.1.6 |
rlIpAddressPrefixA pointer to the row in the prefix table to which this address belongs. May be { 0 0 } if there is no such row.ro RowPointer (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.250.1.1.7 |
rlIpAddressStatusThe status of the address, describing if the address can be used for communication. In the absence of other information, an IPv4 address is always preferred(1).rw IpAddressStatusTC (IP-MIB) .1.3.6.1.4.1.9.6.1.101.250.1.1.8 |
rlIpAddressCreatedThe value of sysUpTime at the time this entry was created. If this entry was created prior to the last re- initialization of the local network management subsystem, then this object contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.250.1.1.9 |
rlIpAddressLastChangedThe value of sysUpTime at the time this entry was last updated. If this entry was updated prior to the last re- initialization of the local network management subsystem, then this object contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.250.1.1.10 |
rlIpAddressRowStatusThe status of this conceptual row. The RowStatus TC requires that this DESCRIPTION clause states under which circumstances other objects in this row can be modified. The value of this object has no effect on whether other objects in this conceptual row can be modified. A conceptual row can not be made active until the rlIpAddressIfIndex has been set to a valid index.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.250.1.1.11 |
rlIpAddressStorageTypeThe storage type for this conceptual row. If this object has a value of 'permanent', then no other objects are required to be able to be modified.rw StorageType (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.250.1.1.12 |
rlIpAddressExtdPrefixLengthThe prefix length of this address.rw InetAddressPrefixLength (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.6.1.101.250.1.1.13 |
rlIpAddressCompleteAddrThe Complete IP address to which this entry's addressing information pertains. In case of auto-configure address such as eui-64, general-prefix and others it contains the complete address after appropriate manipulationro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.6.1.101.250.1.1.14 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.