Hi folks.
I'm having a problem trying to replicate the MPLS LDP hello adjacencies I see on the CLI by running 'show mpls ldp neighbor' with results from walking mplsLdpHelloAdjacencyType and other related OID's.
Here are some 'show mpls ldp neighbor' snippets:
Peer LDP Ident: 10.7.0.1:0; Local LDP Ident 10.7.2.1:0
TCP connection: 10.7.0.1.646 - 10.7.2.1.43828
State: Oper; Msgs sent/rcvd: 162371/161638; Downstream
Up time: 7w3d
LDP discovery sources:
Targeted Hello 10.7.2.1 -> 10.7.0.1, active, passive
Addresses bound to peer LDP Ident:
10.7.0.1 [etc]
Peer LDP Ident: 10.7.63.1:0; Local LDP Ident 10.7.2.1:0
TCP connection: 10.7.63.1.26327 - 10.7.2.1.646
State: Oper; Msgs sent/rcvd: 163080/163018; Downstream
Up time: 7w3d
LDP discovery sources:
Targeted Hello 10.7.2.1 -> 10.7.63.1, active, passive
Addresses bound to peer LDP Ident:
10.7.63.1 [etc]
In this case I'd like to add monitoring to ensure an adjacency exists between this router and 10.7.0.1 and 10.7.63.1. I walk mplsLdpHelloAdjacencyType:
[fgeueke@dev2:~ 11:53 AM]$ snmpwalk -Ob -v1 -c[snip] 10.7.2.1 mplsLdpHelloAdjacencyType |grep '\.10\.7\.\(0\|63\)\.1'
MPLS-LDP-STD-MIB::mplsLdpHelloAdjacencyType.10.7.2.1.0.0.168230913.10.7.0.1.0.0.1 = INTEGER: targeted(2)
Notice the absences of an entry for 10.7.63.1. The router in this example is a 7604 running c7600s72033-advipservicesk9-mz.122-33.SRE9 but I'm getting similar results for other 7600's and ASR's.
I've had a TAC case open for over a year on this with little success - so I figured I'd post to the group. Has anyone run into something similar? Thanks!
