All MIBs › RAPID-CITY › rcCfmL2IpPingReplyPortNum
rcCfmL2IpPingReplyPortNum
Module: RAPID-CITY
OID (symbolic): RAPID-CITY::rcCfmL2IpPingReplyPortNum
OID (numeric): 1.3.6.1.4.1.2272.1.69.38.1.7
Node type: OBJECT-TYPE
Type: InterfaceIndex
Access: read-only
Description:
Either the value '0', or the port number of the port used for the l2ping.
What is rcCfmL2IpPingReplyPortNum?
This object contains either zero or the port number on which a Layer 2 ping reply was received during Connectivity Fault Management testing. The value tells you which port responded to your diagnostic ping. An operator would read this when troubleshooting L2 connectivity: a ping returning port 0 means no response (link down), while a specific port number confirms bidirectional L2 reachability on that port.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2272.1.69.38.1.7 snmpwalk -v2c -c public <target> RAPID-CITY::rcCfmL2IpPingReplyPortNum
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.2272.1.69.38.1.7.1 snmpget -v2c -c public <target> RAPID-CITY::rcCfmL2IpPingReplyPortNum.1
OID Breakdown
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | BIANCA-BRICK-PPP-MIB |
| 1.3.6 | dod | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1 | internet | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.4 | private | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.4.1 | enterprises | ANIROOT-MIB |
| 1.3.6.1.4.1.2272 | rapidCity | RAPID-CITY |
| 1.3.6.1.4.1.2272.1 | rcMgmt | RAPID-CITY |
| 1.3.6.1.4.1.2272.1.69 | rcCfm | RAPID-CITY |
| 1.3.6.1.4.1.2272.1.69.38 | rcCfmL2IpPingReplyTable | RAPID-CITY |
| 1.3.6.1.4.1.2272.1.69.38.1 | rcCfmL2IpPingReplyEntry | RAPID-CITY |
| 1.3.6.1.4.1.2272.1.69.38.1.7 | rcCfmL2IpPingReplyPortNum | RAPID-CITY |