Hi,
I had a question regarding monitoring via snmp for a client who is running a DMVPN scenario. They are using the popular NMS called Orion. We use the following configuration for monitoring statistics on our routers for branches:
logging trap notifications
logging source-interface FastEthernet0/0.1
logging x.x.x.x
snmp-server group xxxxxx v3 priv read xxxxxx write xxxxxx notify xxxxxx
snmp-server view xxxxxx iso included
snmp-server ifindex persist
snmp-server trap-source FastEthernet0/1.1
snmp-server enable traps snmp linkdown linkup
snmp-server enable traps tty
snmp-server enable traps envmon
snmp-server enable traps memory bufferpeak
snmp-server enable traps config
snmp-server enable traps ospf state-change
snmp-server enable traps ospf errors
snmp-server enable traps cpu threshold
snmp-server enable traps ipsla
snmp-server host xxxxxx inform version 3 priv xxxxxx
snmp-server host xxxxxx version 3 priv xxxxxx
snmp-server host xxxxxx version 3 priv xxxxxx
I have been asked by the client that they would like us to monitor any downtime from their ISP end using SNMP. Would it be better to monitor the GRE Tunnels (DMVPN) tunnels on the branches or the physical interfaces that are connecting to the ISPs? I think it would be better to base our results on the uptime of the GRE tunnels since the physical interface does not always end in a down/down state if the ISP's internal routing is messed up the tunnel would go down. Any help in this regard would be helpful.
Thanks very much,
Vick.