All MIBs › CME-MIB › cinStatusString
cinStatusString
Module: CME-MIB
OID (symbolic): CME-MIB::cinStatusString
OID (numeric): 1.3.6.1.4.1.2.3.51.2.4.11.4.1.1.2
Node type: OBJECT-TYPE
Type: OCTET STRING
Access: read-only
Description: Status of a Chassis Internal Network (CIN) connection. For example:
Index:1 VLANID:4094 IPADDR:192.168.70.100 MAC:01:0A:0B:00:01:01 Type:Learned Status:Operational
Index is the status entry number in the status table. Followed by the VLAN ID, IP address, and MAC address that the Management Module is communicating with on the CIN connection.
Type is either 'Configured' or 'Learned'. Learned implies that the Management Module dynamically discovered the IP address. Configured means that the address was explicitly configured in the Management Module.
Status can be 'Operational', 'Not Operational', or 'Disabled'.
'Operational' means the Management Module can ping the CIN IP address.
'Not Operational' means that the Management Module cannot ping the CIN IP address. Verify that the blade and I/O Module are configured properly and that their configurations are compatible with the Management Module. The blade OS also needs to have an IP host route defined (e.g. route add -host 192.168.70.100 eth0.4094). I/O Modules need to have a VLAN defined containing the blade's and the MM's port. Blade and I/O Modules need to be powered up and operational.
'Disabled' means that the CIN configuration has been disabled by a Management Module administrator.
For consistent results, view as a table and not as individual entries.
What is cinStatusString?
This read-only octet string reports a human-readable status line for a Chassis Internal Network connection, formatted like 'Index:1 VLANID:4094 IPADDR:192.168.70.100 MAC:01:0A:0B:00:01:01 Type:Learned Status:Operational', combining the VLAN ID, IP, and MAC the MM is communicating with, plus whether that peer was manually 'Configured' or dynamically 'Learned'. It matters as the quickest way for an admin to see, at a glance, exactly which device the MM has discovered on a given CIN VLAN and whether that connection is currently operational. An admin troubleshooting a blade that can't reach its internal management network would check this string for that VLAN to confirm whether the expected MAC/IP pairing is even showing as Operational.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.4.11.4.1.1.2 snmpwalk -v2c -c public <target> CME-MIB::cinStatusString
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.4.11.4.1.1.2.1 snmpget -v2c -c public <target> CME-MIB::cinStatusString.1
Start monitoring Cisco Communications Manager Express (CME) router/gateway with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CME-MIB::cinStatusString OID value, configure state conditions and alerts, and monitor any Cisco Communications Manager Express (CME) router/gateway from a single console.
OID Breakdown
Upper-level ancestors (11 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.2 | ibm | BLADE-MIB |
| 1.3.6.1.4.1.2.3 | ibmAgents | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51 | netfinitySupportProcessorAgent | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2 | bladeCenterSnmpMIB | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2.4 | configureSP | BLADE-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2.3.51.2.4.11 | chassisInternalNetwork | CME-MIB |
| 1.3.6.1.4.1.2.3.51.2.4.11.4 | cinStatus | CME-MIB |
| 1.3.6.1.4.1.2.3.51.2.4.11.4.1 | cinStatusTable | CME-MIB |
| 1.3.6.1.4.1.2.3.51.2.4.11.4.1.1 | cinStatusEntry | CME-MIB |
| 1.3.6.1.4.1.2.3.51.2.4.11.4.1.1.2 | cinStatusString | CME-MIB |