This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Monitoring Metro Ethernet Circuits with Network Atlas

Hi , 
We have a number of Metro Ethernet circuits running between our devices via a carrier cloud.  These are configured with a /30 address.  In the event of a circuit failure in the carrier cloud we would like to create a map in Network Atlas which will make the circuit go red.
With a Metro Ethernet service, if there is an outage in the carrier cloud the physical interfaces on each side will remain up. If these interfaces are terminating on a Juniper Device, they will prevent the remote end of the circuit from being pingable, even if there is another route to this address.  So adding a Node for ICMP only for the remote end and then assigning this to the link on the map will cause this to go red in the event of a circuit failure. 
With cisco this is not the case. If there is another route to the interface, the cisco interface will respond to ICMP via the other route.  In this case if we add a node for ICMP of the remote end device, and there is another route to the IP address then the interface will still be pingable, which in turn will keep the link green on Network Atlas. This is are problem.
Is this a way around this using Orion Network Atlas?
Thanks in Advance,