user manual

4-3
Cisco Active Network Abstraction Fault Management User Guide, Version 3.6 Service Pack 1
OL-14284-01
Chapter 4 Advanced Correlation Scenarios
IP Interface Failure Scenarios
Figure 4-2 Device Unreachable Example 2
Note If the device has a single link and it is being managed through that link (in-band management), there is
no way to determine if the device is unreachable due to a link down, or the link is down because the
device is unreachable. In this case, Cisco ANA shows that the device is unreachable due to link down.
In this case the system will provide the following report:
• Root cause—Device Unreachable (R1)
• Correlated events:
– L2 down
– Device Unreachable (R2)
– L4 down
IP Interface Failure Scenarios
This section includes:
• IP Interface Status Down Alarm
• All IP Interfaces Down Alarm
• IP Interface Failure Examples
IP Interface Status Down Alarm
Alarms related to subinterfaces, for example, line-down trap, line-down syslog, and so on, are reported
on IP interfaces configured above the relevant subinterface. This means that in the system, subinterfaces
are represented by the IP interfaces configured above them. All events sourcing from subinterfaces
without a configured IP are reported on the underlying Layer 1.
An “ip interface status down” alarm is generated when the status of the IP interfaces (whether it is over
an interface or a subinterface) changes from up to down or any other non-operational state. All events
sourced from the subinterfaces correlate to this alarm. In addition an “All ip interfaces down” alarm is
generated when all the IP interfaces above a physical port change state to down.
L2
Management connectivity
Physical links
ANA Unit
L1
L3 L4
R1
R2 SW2
SW1
154608