Chapter 4 Advanced Correlation Scenarios
IP Interface Failure Scenarios
The following correlation information is provided:
•device unreachable on the CE:
–The Syslog alarm is correlated by flow to the possible root cause, for example, a device unreachable alarm on CE1
ATM Examples
Similar examples involving ATM technology have the same result, assuming that a failure in an unmanaged network causes the status of the IP interface to change to down (ILMI is enabled).
Ethernet, Fast Ethernet, Giga Ethernet Examples
Interface Example 6
In this example there is an unreachable CE due to a failure in the unmanaged network.
Figure | Interface Example 6 |
|
| |||
CE1 unreachable |
| PE1 | ||||
|
| |||||
|
|
| Etherenet |
|
| |
|
|
| cloud |
|
|
|
Subinterface with |
|
| Subinterface with | |||
|
|
| ||||
IP configured |
|
|
| IP configured | ||
180438
The following failures are identified in the network:
•A device unreachable alarm is generated on the CE.
•A cloud problem alarm is generated.
The following correlation information is provided:
•No alarms are generated on a PE for Layer1, Layer2 or for the IP layers.
•The device unreachable alarm is correlated to the cloud problem alarm.
Interface Example 7
In this example there is a link down on the PE that results in the CE becoming unreachable.
Figure | Interface Example 7 |
|
| |||
CE1 unreachable |
| PE1 | ||||
|
| |||||
|
|
| Etherenet |
|
| |
|
|
| cloud |
|
|
|
|
|
|
| Link is "down" | ||
|
|
|
|
| ||
Subinterface with |
|
|
| Subinterface with | ||
IP configured |
|
|
| IP configured | ||
180439
Cisco Active Network Abstraction Fault Management User Guide, Version 3.6 Service Pack 1
|
| ||
|
|
