Notification Log entries

The Notification Log includes two general types of entries: event notifications from the Domain Managers and alarm (problem) notifications forwarded from the Alcatel-Lucent 5620 SAM EMS. Global Console notifications describes some of the Smarts notification entries generated by the Domain Managers, their meanings, and possible indicated actions. This table is organized by Element and Notification.

Table 1. Global Console notifications
Element	Notification	Event, problem, or impact	Description
ASA (the Adapter)	AlcatelConnectionLost-<AdapterName>	Event	Indicates that the connection with the EMS has been lost.
BGPSession	Disconnected	Event	This event is based on a BGPSession's two BGPProtocolEndpoints. If neither of the endpoints are administratively down and at least one of them does not have PeerState = ESTABLISHED, then the BGPSession is considered to be Disconnected. An endpoint's PeerState is set from the Alcatel-Lucent 5620 SAM EMS's report of the connectionState of the endpoint (it should show as ESTABLISHED in 5620 SAM). This leads directly to the BGPSession Down problem.
BGPSession	Down	Problem	Results directly from a BGPSession Disconnected event unless there is another explanation for the Disconnected event.
Card	Down	Problem	Determined when the operational state of a card is CRITICAL (that is, down). The operational state of a card in Smarts is taken from the 5620 SAM’s report of operational state for it, which can include UNKNOWN, OK, and CRITICAL. Note that 5620 SAM reports cards as down (CRITICAL) if the card slot is provisioned but no card is present. Additionally, a Base card being Down will consume DaughterCard Down diagnoses. DaughterCard Down diagnoses will consume physical port Interfaces being Down.
ForwarderEndpoint	Down	Problem	Indicates that the operational or administrative status of the ForwarderEndpoint is down. This event is implemented only for Juniper devices.
IGMPInterface	Unreachable	Problem	Results when the InterfaceStatus of the IGMPInterface is NOTINSERVICE or NOTREADY. Such InterfaceStatus values occur when the 5620 SAM reports that the operational state or administrative state of the IGMPInterface is Down. In the case of IGMPInterfaces that are based on VPLS-mode Multicast configurations, these InterfaceStatuses are based on the states of the underlying Interfaces. Note that even when the IGMPInterface is deemed unreachable, specific multicast groups are not shown as impacted.
Interface	Down	Problem	Detected when a Physical Port Interface or a Service Interface has an operational state of DOWN and an administrative state of UP. These are values reported directly by 5620 SAM and inserted by the adapter into IP AM. For Network Interfaces, if they are not Network Connected to other Network Interfaces, the same conditions (Oper Down, Admin Up) will conclude they are Down. The presence of a Network Connection will cause a different diagnosis to be concluded. Note that an Interface Down does not by itself impact objects that use the Interface. For example, OSPF Services will be Impacted if the OSPFInterfaces are Down, not the network or physical interfaces. Presumably if either of the latter were truly Down, the OSPFInterface would also be reported Down by the 5620 SAM.
ISISAdjacency	Down	Problem	Results from ISISAdjacency NeighborStateAlarm event If the neighbor ISISInterface on both side of ISISAdjacency are POINT_TO_POINT type, and at least one side of ISISInterface is down, the NPM IS-IS manager will send NeighborStateAlarm event to the Notification log.
LSP	Impacted	Impact	LSP impacts may have reported Caused Bys such as Router Down. In the 5620 SAM environment there are scenarios where these Impacts can be notified without Caused By being present. This will happen when the 5620 SAM reports an LSP's operational state to be Down. When this happens, the LSP's IsDownInRemote attribute is set to True. If the user navigates to the LSP in question then it will be IsDownInRemote.
OSPFService	ABRNotInBackbone	Event	By default, NPM Manager for OSPF sends this event to the Notification Log. This event recognizes that there is an OSPFService that is an Area Border Router, it is not in the backbone (area 0.0.0.0), and it has associated OSPFInterfaces.
PIMInterface	PIMInterfaceUnreachable	Problem	Results when the InterfaceStatus of the PIMInterface is NOTINSERVICE or NOTREADY. Such InterfaceStatus values occur when the 5620 SAM reports the operational state or administrative state of the PIMInterface is Down. In the case of PIMInterfaces which are based on VPLS-mode Multicast configurations, these InterfaceStatuses are based on the states of the underlying Interfaces. Note that even when the PIMInterface is deemed unreachable, specific multicast groups are not shown as impacted.
Router	Down	Problem	A Router Down problem is diagnosed when a router is unresponsive and there is no better explanation. If an Interface outage or SNMPAgent outage might explain the router's being unresponsive, those are concluded. Router Down is a precondition for a number of impacts in various Smarts servers, particularly impacts in the Multicast domain. The diagnosis of Router Down does not eliminate the Interface Down notifications.
Router	Unresponsive	Event	An Unresponsive event is triggered when a Router's IP Statuses and SnmpManager are all set to Unresponsive. This happens when the Alcatel-Lucent 5620 SAM EMS emits an alarm-243 (SnmpReachabilityProblem) for a given Router. These attributes are reset to OK when the alarm clears.
VPN	Impacted	Impact	VPN impacts may have reported Caused By diagnoses such as Router Down. In the 5620 SAM environment, there are scenarios where these Impacts can notified without Caused By being present. This will happen when 5620 SAM reports an LSP's operational state to be Down. When this happens, the LSP's IsDownInRemote attribute is set to True. However, the user cannot see this relationship from the information in the Notification Log. To find the specific LSP causing the impact, you must navigate through the VPN's VRFs; for each VRF, examine the LSPs it is LayeredOver to see which one of them will be IsDownInRemote.
VRF	Down	Problem	A VRF is determined to be Down when 1) it is operationally Down, and 2) it is not LayeredOver any Interfaces or if all the Interfaces that it is Layered Over are Down.
	Impacted	Impact	VRF impacts may have reported Caused By diagnoses such as Router Down. In the 5620 SAM environment there are scenarios where these Impacts can notified without Caused By being present. This will happen when 5620 SAM reports an LSP's operational state to be Down. When this happens, the LSP's IsDownInRemote attribute is set to True. However, the user cannot see this relationship from the information in the Notification Log. The solution to this is navigating to the VRF in question and then examining the LSPs it is LayeredOver; one of them will be IsDownInRemote.
	NoRoutes	Event	Event is triggered when the NumberOfRoutes attribute in the VRF is 0. This value is supplied by the 5620 SAM rtr.RouteStats <routesInVrf> attribute. Note that the 5620 SAM will only provide data on the number of routes in a VRF if the VRF’s Route Distinguisher type is set to Type0 or Type1.
	WarningThresholdCrossed	Event	You can set values in the MPLS Manager for a warning threshold and a max value, as described in the Smarts MPLS Management Suite User Guide . These events are triggered when a VRF's NumberOfRoutes reaches these respective values. As with the NoRoutes event, the NumberOfRoutes is set by the Adapter based on information kept in the 5620 SAM. The 5620 SAM will only track this information for VRFs that are configured to have Route Distinguishers.
	MaxRoutesReached	Event