Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Monitoring Router Outside Interfaces

Okay, we have multiple Cisco routers throughout our organization and up to this point have been tightening up the monitoring on all devices. On our routers I currently monitor the ethernet 'Inside Interfaces', however I would like to instead monitor the 'Outside Interfaces' which have public IP addresses.

When I add the node to discover using the public IP and select the proper version of snmp and community string it will not detect, it simply times out. Why can I traverse the serial interface with public IP and successfully monitor the ethernet interface but not monitor the outside interface, is there a command I need or is it a access-list issue?

Find more posts tagged with

Accepted answers

All comments

dedwards

Most likely an ACL issue (could also be the ISP ACL's though, I know of at least 1 ISP that blocks SNMP to WAN interface addresses and even blocks SNMP pasthrough unless your monitoring station is on their network...)

bleearg13

With Orion, you monitor an IP address on the device and that IP will give you access to all interfaces on that router. When you right-click on a router in System Manager and go to 'List Resources', you should see a list of all the interfaces on that router - both 'inside' and 'outside'. Or maybe I'm misunderstanding what you are trying to do.

If what you are trying to do is use the 'outside' IP as the address to monitor, I have to ask if you are running NAT and/or any VPNs between the sites? If you are running NAT, and in particular, NAT overload, on the serial IP address (example: ip nat inside source list 5 interface Serial0/0 overload), you will not be able to ping the Serial0/0 address from inside your router. This is because, at least as far as I know, Cisco NAT does not allow traffic to 'loop back' once translation has occurred. Furthermore, if you are in fact running VPNs between the sites, there's a possibility that a similar issue is occurring when trying to contact the other router.

sedmo

Another possibility is that your serial interface addresses are not routed throughout your network. Are you able to ping the addresses on the serial interfaces from your Solarwinds server? If at all possible, I would highly recommend creating loopback interfaces on your routers and use the loopback ip address for monitoring purposes.

reno8a

Actually my purpose of wanting to monitor the serial interfaces is because most of our sites are connected via IPSec Tunnels and although currently I am monitoring just the nodes, I would like to monitor when my ipsec tunnel goes down which doesnt happen if i just monitor the node.