This chapter provides detailed information about the syslogs for third-party devices in Prime Network. Syslogs appear in the Prime Network Event Syslog tab.
•Syslog Tables: A section devoted to the supported syslogs for each NOS platform. Each of these sections contains a table listing the name of each supported syslog, along with a description, the raw format of the syslog string, and a short description. In the syslog tables in this Reference, each syslog's short description is also a link to its corresponding registry parameters.
•Registry Parameter Tables: A section devoted to the event types, event subtypes and Prime Network registry parameters for the supported syslogs. There is one parameter table for every syslog table (e.g., Juniper E-Series Syslogs Registry Parameters). Each syslog can have multiple event subtypes, or states. The parameter tables indicate when each state is generated, and how Prime Network processes them (such as their severity, whether they are ticketable, can be correlated, are autocleared, and so on).
Prime Network 3.10 users can enable an additional IP in the device for traps and syslogs. This new feature is called Multisource Events. When Prime Network 3.10 receives a trap or syslog from that device (from the new IP) it will still recognize the device. For more details on multisource events see Cisco Prime Network 3.10 Release Notes.
1) RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer 80.80.80.8 (Internal AS 65520) changed state from Established to Idle (event Closed) 2) RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer 80.80.80.8 (Internal AS 65520) changed state from OpenConfirm to Established (event RecvKeepAlive)
Sep 5 17:09:10 rpd[3161]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer 80.80.80.8 (Internal AS 65520) changed state from OpenConfirm to Established (event RecvKeepAlive)
Table 12-4 lists the Juniper JCS Control System Syslogs supported in Prime Network.
Table 12-4 Juniper JCS Control SystemSyslogs
Syslog Name
Description
Raw Format
Short Description
RPD_BGP_NEIGHBOR_STATE_CHANGED
During BGP negotiation with the local router, the state of the indicated BGP neighbor (peer) changed as indicated. The ESTABLISHED state is the final state in the neighbor negotiation
Sep 5 17:08:26 rpd[3161]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer 80.80.80.8 (Internal AS 65520) changed state from Established to Idle (event Closed)
During BGP negotiation with the local router, the state of the indicated BGP neighbor (peer) changed as indicated. The ESTABLISHED state is the final state in the neighbor negotiation.
Sep 5 17:09:10 rpd[3161]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer 80.80.80.8 (Internal AS 65520) changed state from OpenConfirm to Established (event RecvKeepAlive)
A Label Distribution Protocol (LDP) adjacency was terminated because the indicated neighbor stopped communicating. If the adjacency was the only one with this neighbor, the routing protocol process (rpd) terminated the associated LDP session.
RPD_LDP_NBRDOWN: LDP neighbor 10.110.1.5 (so-0/3/1.20) is down
A Label Distribution Protocol (LDP) adjacency with the indicated neighbor became active. The routing protocol process (rpd) established an LDP session with the neighbor if one did not already exist.
RPD_LDP_NBRUP: LDP neighbor 10.110.1.5 (so-0/3/1.20) is up
An OSPF adjacency with the indicated neighboring router was terminated. The local router no longer exchanges routing information with, or directs traffic to, the neighboring router.
RPD_OSPF_NBRDOWN: OSPF neighbor 10.111.1.9 (fe-0/0/3.0) state changed from Full to Down due to Kill all neighbors
Table 12-5 lists the Juniper M-Series Syslogs supported in Prime Network.
Table 12-5 Juniper M-Series Syslogs
Syslog Name
Description
Raw Format
Short Description
RPD_BGP_NEIGHBOR_STATE_CHANGED
During BGP negotiation with the local router, the state of the indicated BGP neighbor (peer) changed as indicated. The ESTABLISHED state is the final state in the neighbor negotiation
During BGP negotiation with the local router, the state of the indicated BGP neighbor (peer) changed as indicated. The ESTABLISHED state is the final state in the neighbor negotiation
During BGP negotiation with the local router, the state of the indicated BGP neighbor (peer) changed as indicated. The ESTABLISHED state is the final state in the neighbor negotiation.
During BGP negotiation with the local router, the state of the indicated BGP neighbor (peer) changed as indicated. The ESTABLISHED state is the final state in the neighbor negotiation.
A Label Distribution Protocol (LDP) adjacency was terminated because the indicated neighbor stopped communicating. If the adjacency was the only one with this neighbor, the routing protocol process (rpd) terminated the associated LDP session.
A Label Distribution Protocol (LDP) adjacency was terminated because the indicated neighbor stopped communicating. If the adjacency was the only one with this neighbor, the routing protocol process (rpd) terminated the associated LDP session.
A Label Distribution Protocol (LDP) adjacency with the indicated neighbor became active. The routing protocol process (rpd) established an LDP session with the neighbor if one did not already exist.
A Label Distribution Protocol (LDP) adjacency with the indicated neighbor became active. The routing protocol process (rpd) established an LDP session with the neighbor if one did not already exist.
An OSPF adjacency with the indicated neighboring router was terminated. The local router no longer exchanges routing information with, or directs traffic to, the neighboring router.
An OSPF adjacency with the indicated neighboring router was terminated. The local router no longer exchanges routing information with, or directs traffic to, the neighboring router.
Table 12-6 lists the Juniper MX-Series Syslogs supported in Prime Network.
Table 12-6 Juniper MX-Series Syslogs
Syslog Name
Description
Raw Format
Short Description
RPD_BGP_NEIGHBOR_STATE_CHANGED
During BGP negotiation with the local router, the state of the indicated BGP neighbor (peer) changed as indicated. The ESTABLISHED state is the final state in the neighbor negotiation
During BGP negotiation with the local router, the state of the indicated BGP neighbor (peer) changed as indicated. The ESTABLISHED state is the final state in the neighbor negotiation
During BGP negotiation with the local router, the state of the indicated BGP neighbor (peer) changed as indicated. The ESTABLISHED state is the final state in the neighbor negotiation.
During BGP negotiation with the local router, the state of the indicated BGP neighbor (peer) changed as indicated. The ESTABLISHED state is the final state in the neighbor negotiation.
A Label Distribution Protocol (LDP) adjacency was terminated because the indicated neighbor stopped communicating. If the adjacency was the only one with this neighbor, the routing protocol process (rpd) terminated the associated LDP session.
A Label Distribution Protocol (LDP) adjacency was terminated because the indicated neighbor stopped communicating. If the adjacency was the only one with this neighbor, the routing protocol process (rpd) terminated the associated LDP session.
A Label Distribution Protocol (LDP) adjacency with the indicated neighbor became active. The routing protocol process (rpd) established an LDP session with the neighbor if one did not already exist.
A Label Distribution Protocol (LDP) adjacency with the indicated neighbor became active. The routing protocol process (rpd) established an LDP session with the neighbor if one did not already exist.
An OSPF adjacency with the indicated neighboring router was terminated. The local router no longer exchanges routing information with, or directs traffic to, the neighboring router.
An OSPF adjacency with the indicated neighboring router was terminated. The local router no longer exchanges routing information with, or directs traffic to, the neighboring router.
Juniper T-Series Syslogs supported in Prime Network is the same as the Juniper M-Series Syslogs. For more details on the Juniper M-Series Syslogs see Table 12-5
RAD ACE Syslogs
Table 12-7 lists the RAD ACE Syslogs supported in Prime Network.
Table 12-7 RAD ACE Syslogs
Syslog Name
Description
Raw Format
Short Description
any syslogs
Default pattern to send uncorrelated/unknown syslogs to the vision
Alcatel-Lucent 7705 SAR Syslogs Registry Parameters
Table 12-8 lists the associated event types, event subtypes, and Prime Network registry parameters for the Alcatel-Lucent 7705 SAR Syslogs Registry Parameters shown in Table 12-1.
Table 12-8 Alcatel-Lucent 7705 SAR Syslogs Registry Parameters
Short Description
Event Type
Event Subtype
Subtype Value
Expedites Polling
Event Source (IMO Name)
Activate Flow
Correlate
Is Correlation Allowed
Weight
Auto Clear
Severity
Is Ticketable
Auto Remove
Flapping
Stp port status syslog
Stp Port Status change syslog
Stp Port Status change syslog
F
T
F
0
T
info
F
T
F
Sys gbic removed syslog
GBIC status syslog
GBIC removed syslog
F
T
F
0
T
info
F
T
F
Sys gbic inserted syslog
GBIC status syslog
GBIC inserted syslog
F
T
F
0
T
info
F
T
F
Alcatel-Lucent 7750 SR Syslogs Registry Parameters
Table 12-9 lists the associated event types, event subtypes, and Prime Network registry parameters for the Alcatel-Lucent 7750 SR Syslogs Registry Parameters shown in Table 12-2.
Table 12-9 Alcatel-Lucent 7750 SR Syslogs Registry Parameters
Short Description
Event Type
Event Subtype
Subtype Value
Expedites Polling
Event Source (IMO Name)
Activate Flow
Correlate
Is Correlation Allowed
Weight
Auto Clear
Severity
Is Ticketable
Auto Remove
Flapping
Stp port status syslog
Stp Port Status change syslog
Stp Port Status change syslog
F
T
F
0
T
info
F
T
F
Sys gbic removed syslog
GBIC status syslog
GBIC removed syslog
F
T
F
0
T
info
F
T
F
Sys gbic inserted syslog
GBIC status syslog
GBIC inserted syslog
F
T
F
0
T
info
F
T
F
Juniper E-Series Syslogs Registry Parameters
Table 12-10 lists the associated event types, event subtypes, and Prime Network registry parameters for the Juniper E-Series Syslogs Registry Parameters shown in Table 12-3.
Juniper JCS Control System Syslogs Registry Parameters
Table 12-11 lists the associated event types, event subtypes, and Prime Network registry parameters for the Juniper JCS Control System Syslogs Registry Parameters shown in Table 12-4.
Table 12-11 Juniper JCS Control System Syslog Registry Parameters
Table 12-12 lists the associated event types, event subtypes, and Prime Network registry parameters for the Juniper M-Series Syslogs Registry Parameters shown in Table 12-5.
Table 12-13 lists the associated event types, event subtypes, and Prime Network registry parameters for the Juniper MX-Series Syslogs Registry Parameters shown in Table 12-6.
Juniper T-Series Syslogs Registery Parameters supported in Prime Network is the same as the Juniper M-Series Syslogs Register Parameters. For more details on the Juniper M-Series Syslogs see Table 12-12
RAD ACE Syslogs Registry Parameters
Table 12-14 lists the associated event types, event subtypes, and Prime Network registry parameters for the RAD ACE Syslogs Registry Parameters shown in Table 12-7.