All MIBs › RAPID-CITY-VSP › rcCbQe2kSerdesLinkId
rcCbQe2kSerdesLinkId
Module: RAPID-CITY-VSP
OID (symbolic): RAPID-CITY-VSP::rcCbQe2kSerdesLinkId
OID (numeric): 1.3.6.1.4.1.2272.1.204.1.1.1.5.1.1
Node type: OBJECT-TYPE
Type: Integer32
Access: not-accessible
Description: This ID maps to a particular serdes port number for the identified device. Here's the mapping:
rcCbQe2kSerdesLinkId 1 = port 0; Slot 3; QE Device 1 ... rcCbQe2kSerdesLinkId 20 = port 19; Slot 3; QE Device 1 rcCbQe2kSerdesLinkId 21 = port 0; Slot 3; QE Device 2 rcCbQe2kSerdesLinkId 41 = port 0; Slot 3; QE Device 3 rcCbQe2kSerdesLinkId 61 = port 0; Slot 4; QE Device 1 rcCbQe2kSerdesLinkId 121 = port 0; Slot 1; QE Device 1 rcCbQe2kSerdesLinkId 141 = port 0; Slot 1; QE Device 1 rcCbQe2kSerdesLinkId 161 = port 0; Slot 5; QE Device 1 rcCbQe2kSerdesLinkId 221 = port 0; Slot 6; QE Device 1 ... with slots 6-12 in order ... rcCbQe2kSerdesLinkId 640 = port 19; Slot 12; QE Device 3 Note link 15 & 17 are used when QE2k is connected to SF96.
OID Breakdown
Upper-level ancestors (8 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.2272 | rapidCity | RAPID-CITY |
| 1.3.6.1.4.1.2272.1 | rcMgmt | RAPID-CITY |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2272.1.204 | rcCobaltBlue | RAPID-CITY-VSP |
| 1.3.6.1.4.1.2272.1.204.1 | rcCobaltBlueMib | RAPID-CITY-VSP |
| 1.3.6.1.4.1.2272.1.204.1.1 | rcCbObjects | RAPID-CITY-VSP |
| 1.3.6.1.4.1.2272.1.204.1.1.1 | rcCbSwitchFabric | RAPID-CITY-VSP |
| 1.3.6.1.4.1.2272.1.204.1.1.1.5 | rcCbQe2kSerdesLinkTable | RAPID-CITY-VSP |
| 1.3.6.1.4.1.2272.1.204.1.1.1.5.1 | rcCbQe2kSerdesLinkEntry | RAPID-CITY-VSP |
| 1.3.6.1.4.1.2272.1.204.1.1.1.5.1.1 | rcCbQe2kSerdesLinkId | RAPID-CITY-VSP |