via CLI I can do
HUB-DMVPN01#show dmvpn peer nbma x.x.x.x detail
Legend: Attrb --> S - Static, D - Dynamic, I - Incomplete
N - NATed, L - Local, X - No Socket
T1 - Route Installed, T2 - Nexthop-override
C - CTS Capable, I2 - Temporary
# Ent --> Number of NHRP entries with same NBMA peer
NHS Status: E --> Expecting Replies, R --> Responding, W --> Waiting
UpDn Time --> Up or Down Time for a Tunnel
==========================================================================
Interface TunnelYYY is up/up, Addr. is z.z.z.z, VRF "BGPSPOKES"
Tunnel Src./Dest. addr: i.i.i.i/Multipoint, Tunnel VRF ""
Protocol/Transport: "multi-GRE/IP", Protect "IPSEC-PROFILE"
Interface State Control: Disabled
nhrp event-publisher : Disabled
Type:Hub, Total NBMA Peers (v4/v6): 1
# Ent Peer NBMA Addr Peer Tunnel Add State UpDn Tm Attrb Target Network
----- --------------- --------------- ----- -------- ----- -----------------
1 [PEER PUBLIC IP] [PEER TUNNEL IP] UP 6d15h DN [PEER TUNNEL IP]/32 (BGPSPOKES)
Claimed Addr. [PEER INSIDE WAN ADDRESS]
However in SNMP I don't seem to be able to make the connection between PEER PUBLIC IP and PEER TUNNEL IP.
I'm not too much into ipsec/ike/tunnel phases etc. however I have found that I can find the tuple of PUBLIC PEER IP and the public IP of my DMVPN hub, using .1.3.6.1.4.1.9.9.171.1.2.3.1.8.[ID] for the PEER PUBLIC IP - however I cannot figure out how I can map that to the PEER TUNNEL IP?
(1.3.6.1.4.1.9.9.680 is not available on this router - not that I expect it to provide much insight anyways.. is this simply not possible?
I'd hate to resort to CLI scraping, but that's where I'm headed
