2. Log Events

2.1. Changes

Table 4:  Event Changes 

Event Name

Change

airflowCorrected

New

airflowMismatch

New

dhcp6ClientRenewSuccess

Updated

dhcpv4RelayAdminDisable

New

dhcpv4RelayAdminEnable

New

dhcpv4RelayAllDhcpv4ServersUnreachable

New

dhcpv4RelayOperDown

New

dhcpv4RelayOperUp

New

dhcpv6RelayAdminDisable

New

dhcpv6RelayAdminEnable

New

dhcpv6RelayAllDhcpv6ServersUnreachable

New

dhcpv6RelayOperDown

New

dhcpv6RelayOperUp

New

ethernetsegmentNetworkInstanceBgpInstance DfStatusChanged

New

evpnAutoDiscoveryEviRouteWithdrawnDueTo UnexpectedVni

New

evpnInclMcastRouteWithdrawnDueToUnexpected Vni

New

evpnIpPrefixRouteNotImportedDueToUnexpected Vni

New

evpnIpPrefixRouteWithdrawnDueToNoGwMac

New

evpnIpPrefixRouteWithdrawnDueToUnexpected GwIp

New

evpnMacRouteWithdrawnDueToUnexpectedVni

New

giAddressMismatch

New

isisLspBufferSizeMismatch

Removed

isisLspFragmentTooLarge

Updated

isisOverloadChange

Removed

isisOwnLspPurge

Removed

isisOverloadEntry

New

isisOverloadExit

New

lagMemberOperDown

New

lagMemberOperUp

New

ospIfAuthDataFailure

New

ospfAdjacencyBfdSessionSetupFailed

New

ospfAdjacencyChange

New

ospfAdjacencyRestartStatusChange

New

ospfAsMaxAgeLSA

New

ospfExportLimitReached

New

ospfExportLimitWarning

New

ospfFailure

New

ospfIfRxBadPacket

New

ospfIfStateChange

New

ospfLsdbApproachingOverflow

New

ospfLsdbOverflow

New

ospfNbrMtuMismatch

New

ospfOverloadEntry

New

ospfOverloadExit

New

ospfSpfRunRestarted

New

ospfSpfRunsStopped

New

platformDatapathResourceHighUtilization

New

platformDatapathResourceHighUtilizationLowered

New

platformDatapathResourceLimitCleared

New

platformDatapathResourceLimitReached

New

platformIpMplsFwdResourceHighUtilization

Removed

platformIpMplsFwdResourceHighUtilizationLowered

Removed

platformPipelineResourceHighUtilization

New

platformPipelineResourceHighUtilizationLowered

New

platformPipelineResourceLimitCleared

New

platformPipelineResourceLimitReached

New

sFlowAgentChange

New

sFlowCollectorUnreachable

New

sourceAddressMismatch

New

vxlanInterfaceBridgeTableMulticastDestinations LimitHighUtilization

New

vxlanInterfaceBridgeTableMulticastDestinations LimitHighUtilizationLowered

New

vxlanInterfaceBridgeTableMulticastDestinations LimitLowered

New

vxlanInterfaceBridgeTableMulticastDestinations LimitReached

New

2.2. aaa

2.2.1. serverDown

Table 5:  serverDown properties 

Property name

Value

Application name

aaa

Event name

serverDown

Default severity

error

Message format string

Server server_address in group server_group is down

Cause

The specified server is down, either via being unreachable, or a timeout.

Effect

The specified server can no longer be used for authentication, authorization, or accounting transactions.

2.2.2. serverGroupDown

Table 6:  serverGroupDown properties 

Property name

Value

Application name

aaa

Event name

serverGroupDown

Default severity

critical

Message format string

All servers in server group server_group are down

Cause

All servers within the specified server group are no longer available.

Effect

The specified server group can no longer be used for authentication, authorization, or accounting transactions.

2.2.3. serverRouteUnavailable

Table 7:  serverRouteUnavailable properties 

Property name

Value

Application name

aaa

Event name

serverRouteUnavailable

Default severity

error

Message format string

No route available to reach remote server server_address in server group server_group via network instance network_instance

Cause

No routes are available in the specified network instance to reach the remote server.

Effect

The specified server can no longer be used for authentication, authorization, or accounting transactions.

2.2.4. serverTimeout

Table 8:  serverTimeout properties 

Property name

Value

Application name

aaa

Event name

serverTimeout

Default severity

error

Message format string

Server server_address in group server_group has timed out

Cause

The connection between the AAA manager and the remote server has timed out. The server will be tried again in 30 seconds, or immediately if a valid response is received.

Effect

The specified server can no longer be used for authentication, authorization, or accounting transactions.

2.2.5. sessionClosed

Table 9:  sessionClosed properties 

Property name

Value

Application name

aaa

Event name

sessionClosed

Default severity

notice

Message format string

Closed session for user user_name from host remote_host

Cause

The specified user has closed a session on the system.

Effect

None.

2.2.6. sessionDisconnected

Table 10:  sessionDisconnected properties 

Property name

Value

Application name

aaa

Event name

sessionDisconnected

Default severity

notice

Message format string

Session for user user_name from remote host remote_host disconnected by administrative action

Cause

The specified user has been disconnected from the system by an administrators action.

Effect

The specified user is disconnected.

2.2.7. sessionOpened

Table 11:  sessionOpened properties 

Property name

Value

Application name

aaa

Event name

sessionOpened

Default severity

notice

Message format string

Opened session for user user_name from host remote_host

Cause

The specified user has opened a session on the system.

Effect

None.

2.2.8. userAuthenticationFailed

Table 12:  userAuthenticationFailed properties 

Property name

Value

Application name

aaa

Event name

userAuthenticationFailed

Default severity

warning

Message format string

User user_name authentication failed from host remote_host

Cause

The specified user has failed authentication.

Effect

None.

2.2.9. userAuthenticationSucceeded

Table 13:  userAuthenticationSucceeded properties 

Property name

Value

Application name

aaa

Event name

userAuthenticationSucceeded

Default severity

notice

Message format string

User user_name successfully authenticated from host remote_host

Cause

The specified user has successfully authenticated.

Effect

None.

2.3. acl

2.3.1. aclCpmIpv4MatchedPacket

Table 14:  aclCpmIpv4MatchedPacket properties 

Property name

Value

Application name

acl

Event name

aclCpmIpv4MatchedPacket

Default severity

notice

Message format string

An IPv4 packet, len packet-length, protocol ip-protocol, received by linecard incoming-linecard was action by entry sequence-id of the IPv4 cpm-filter. source-ip(source-port) -> dest-ip(dest-port)

Cause

This event is generated when an IPv4 packet matches an entry of the CPM IPv4 filter and that entry specifies a log action

Effect

None

2.3.2. aclCpmIpv6MatchedPacket

Table 15:  aclCpmIpv6MatchedPacket properties 

Property name

Value

Application name

acl

Event name

aclCpmIpv6MatchedPacket

Default severity

notice

Message format string

An IPv6 packet, len packet-length, protocol last-next-header, received by linecard incoming-linecard was action by entry sequence-id of the IPv6 cpm-filter. source-ip(source-port) -> dest-ip(dest-port)

Cause

This event is generated when an IPv6 packet matches an entry of the CPM IPv6 filter and that entry specifies a log action

Effect

None

2.3.3. aclInterfaceInputIpv4MatchedPacket

Table 16:  aclInterfaceInputIpv4MatchedPacket properties 

Property name

Value

Application name

acl

Event name

aclInterfaceInputIpv4MatchedPacket

Default severity

notice

Message format string

An IPv4 packet, len packet-length, protocol ip-protocol, received on incoming-interface was action by entry sequence-id of filter filter-name. source-ip(source-port) -> dest-ip(dest-port)

Cause

This event is generated when an IPv4 packet matches an entry of an IPv4 filter applied to ingress traffic on a subinterface and that entry specifies a log action

Effect

None

2.3.4. aclInterfaceInputIpv6MatchedPacket

Table 17:  aclInterfaceInputIpv6MatchedPacket properties 

Property name

Value

Application name

acl

Event name

aclInterfaceInputIpv6MatchedPacket

Default severity

notice

Message format string

An IPv6 packet, len packet-length, protocol last-next-header, received on incoming-interface was action by entry sequence-id of filter filter-name. source-ip(source-port) -> dest-ip(dest-port)

Cause

This event is generated when an IPv6 packet matches an entry of an IPv6 filter applied to ingress traffic on a subinterface and that entry specifies a log action

Effect

None

2.3.5. aclInterfaceOutputIpv4MatchedPacket

Table 18:  aclInterfaceOutputIpv4MatchedPacket properties 

Property name

Value

Application name

acl

Event name

aclInterfaceOutputIpv4MatchedPacket

Default severity

notice

Message format string

An IPv4 packet, len packet-length, protocol ip-protocol, intended for transmit on outgoing-interface was action by entry sequence-id of filter filter-name. source-ip(source-port) -> dest-ip(dest-port)

Cause

This event is generated when an IPv4 packet matches an entry of an IPv4 filter applied to egress traffic on a subinterface and that entry specifies a log action

Effect

None

2.3.6. aclInterfaceOutputIpv6MatchedPacket

Table 19:  aclInterfaceOutputIpv6MatchedPacket properties 

Property name

Value

Application name

acl

Event name

aclInterfaceOutputIpv6MatchedPacket

Default severity

notice

Message format string

An IPv6 packet, len packet-length, protocol last-next-header, intended for transmit on outgoing-interface was action by entry sequence-id of filter filter-name. source-ip(source-port) -> dest-ip(dest-port)

Cause

This event is generated when an IPv6 packet matches an entry of an IPv6 filter applied to egress traffic on a subinterface and that entry specifies a log action

Effect

None

2.3.7. aclTcamProgComplete

Table 20:  aclTcamProgComplete properties 

Property name

Value

Application name

acl

Event name

aclTcamProgComplete

Default severity

notice

Message format string

All TCAM banks on all linecards have been reprogrammed with the latest ACL configuration changes.

Cause

This event is generated when all TCAM banks on all linecards have been reprogrammed with the latest ACL configuration changes.

Effect

None

2.3.8. platformAclHighUtilization

Table 21:  platformAclHighUtilization properties 

Property name

Value

Application name

acl

Event name

platformAclHighUtilization

Default severity

warning

Message format string

The ACL resource called resource-name has reached threshold% or more utilization on linecard linecard, forwarding complex forwarding-complex. Only free-entries entries are remaining.

Cause

This event is generated when the utilization of an ACL resource has increased to a level that may warrant concern if futher resources are consumed

Effect

None

2.3.9. platformAclHighUtilizationLowered

Table 22:  platformAclHighUtilizationLowered properties 

Property name

Value

Application name

acl

Event name

platformAclHighUtilizationLowered

Default severity

notice

Message format string

The ACL resource called resource-name has decreased back to threshold% or less utilization on linecard linecard, forwarding complex forwarding-complex.

Cause

This event is generated when the utilization of an ACL resource has decreased to a level that may no longer warrant concern

Effect

None

2.3.10. platformTcamHighUtilization

Table 23:  platformTcamHighUtilization properties 

Property name

Value

Application name

acl

Event name

platformTcamHighUtilization

Default severity

warning

Message format string

The TCAM resource called resource-name has reached threshold% or more utilization on linecard linecard, forwarding complex forwarding-complex. Only free-entries entries are remaining.

Cause

This event is generated when the utilization of a TCAM resource has increased to a level that may warrant concern if futher resources are consumed

Effect

None

2.3.11. platformTcamHighUtilizationLowered

Table 24:  platformTcamHighUtilizationLowered properties 

Property name

Value

Application name

acl

Event name

platformTcamHighUtilizationLowered

Default severity

notice

Message format string

The TCAM resource called resource-name has decreased back to threshold% or less utilization on linecard linecard, forwarding complex forwarding-complex.

Cause

This event is generated when the utilization of a TCAM resource has decreased to a level that may no longer warrant concern

Effect

None

2.4. arpnd

2.4.1. ipArpEntryUpdated

Table 25:  ipArpEntryUpdated properties 

Property name

Value

Application name

arpnd

Event name

ipArpEntryUpdated

Default severity

informational

Message format string

The ARP entry for ipv4-address has been updated.

Cause

This event is generated whenever an existing static or dynamic ARP entry for an IPv4 address is overwritten. This could be a triggered by a change of entry type (static vs dynamic) or a change of MAC address or a change of the subinterface binding.

Effect

None

2.4.2. ipSubinterfaceDuplicateIpv4Address

Table 26:  ipSubinterfaceDuplicateIpv4Address properties 

Property name

Value

Application name

arpnd

Event name

ipSubinterfaceDuplicateIpv4Address

Default severity

notice

Message format string

The IPv4 address ipv4-address assigned to interface.subinterface-index is being used by another host or router on the same subnet.

Cause

This event is generated when ARP detects that another system is using the same IPv4 address

Effect

Unreliable communications

2.4.3. ipSubinterfaceDuplicateIpv6Address

Table 27:  ipSubinterfaceDuplicateIpv6Address properties 

Property name

Value

Application name

arpnd

Event name

ipSubinterfaceDuplicateIpv6Address

Default severity

notice

Message format string

The IPv6 address ipv6-address assigned to interface.subinterface-index is being used by another host or router on the same subnet.

Cause

This event is generated when IPv6 DAD detects that another system is using the same IPv6 address

Effect

Unreliable communications

2.4.4. ipSubinterfaceDuplicateMacAddress

Table 28:  ipSubinterfaceDuplicateMacAddress properties 

Property name

Value

Application name

arpnd

Event name

ipSubinterfaceDuplicateMacAddress

Default severity

notice

Message format string

The MAC address mac-address used by interface.subinterface-index is being used by another host or router on the same subnet.

Cause

This event is generated when ARP or IPv6 Neighbor Discovery detects that another system is using the same MAC address

Effect

Unreliable communications

2.4.5. ipSubinterfaceInvalidArp

Table 29:  ipSubinterfaceInvalidArp properties 

Property name

Value

Application name

arpnd

Event name

ipSubinterfaceInvalidArp

Default severity

notice

Message format string

An ARP request for ipv4-address was received on interface.subinterface-index and there is no matching IPv4 subnet.

Cause

This event is generated when ARP receives an ARP request for an invalid IPv4 address

Effect

None

2.4.6. ipSubinterfaceInvalidIpv6NeighborSolicitation

Table 30:  ipSubinterfaceInvalidIpv6NeighborSolicitation properties 

Property name

Value

Application name

arpnd

Event name

ipSubinterfaceInvalidIpv6NeighborSolicitation

Default severity

notice

Message format string

An IPv6 neighbor solicitation for ipv6-address was received on interface.subinterface-index and there is no matching IPv6 subnet.

Cause

This event is generated when IPv6 neighbor discovery receives a NS message for an invalid IPv6 address

Effect

None

2.4.7. ipv6NeighborEntryUpdated

Table 31:  ipv6NeighborEntryUpdated properties 

Property name

Value

Application name

arpnd

Event name

ipv6NeighborEntryUpdated

Default severity

informational

Message format string

The IPv6 neighbor discovery entry for ipv6-address has been updated.

Cause

This event is generated whenever an existing static or dynamic neighbor entry for an IPv6 address is overwritten. This could be a triggered by a change of entry type (static vs dynamic) or a change of MAC address or a change of the subinterface binding.

Effect

None

2.5. bfd

2.5.1. bfdDownEvent

Table 32:  bfdDownEvent properties 

Property name

Value

Application name

bfd

Event name

bfdDownEvent

Default severity

warning

Message format string

BFD: Network-instance network-instance - Session from local-address:local-discriminator to remote-address:remote-discriminator has transitioned to the down-state state with local-diagnostic code: local-diagnostic-str (local-diagnostic-code) and remote-diagnostic code: remote-diagnostic-str (remote-diagnostic-code)

Cause

This notification is generated when a BFD sessions transitions to the Down or Admin Down state from an Up state.

Effect

The specified BFD sessions is now down. If the new state is Down, the session is down due to a failure see the local or remote diagnostic code. If the new state is Admin-Down the session is down due to administrative reasons.

2.5.2. bfdMaxSessionActive

Table 33:  bfdMaxSessionActive properties 

Property name

Value

Application name

bfd

Event name

bfdMaxSessionActive

Default severity

warning

Message format string

BFD: Network-instance network-instance - Session from local-address to remote-address requested by client-protocol could not be created because the maximum number of BFD sessions bfd-max-session are active.

Cause

This notification is generated when a BFD session cannot be created because the maximum number of BFD sessions are already active.

Effect

No more BFD sessions can be created until some existing sessions are removed.

2.5.3. bfdProtocolClientAdd

Table 34:  bfdProtocolClientAdd properties 

Property name

Value

Application name

bfd

Event name

bfdProtocolClientAdd

Default severity

notice

Message format string

BFD: Network-instance network-instance - The protocol client-protocol is now using BFD session from local-address:local-discriminator to remote-address:remote-discriminator

Cause

This notification is generated when a new protocol begins to use a BFD session to track liveliness.

Effect

The specified protocol will be notified by BFD if the associated sessions transitions from an Up to a Down state. It will be up to the receiving protocol to determine the course of action.

2.5.4. bfdProtocolClientRemove

Table 35:  bfdProtocolClientRemove properties 

Property name

Value

Application name

bfd

Event name

bfdProtocolClientRemove

Default severity

notice

Message format string

BFD: Network-instance network-instance - The protocol client-protocol using BFD session from local-address:local-discriminator to remote-address:remote-discriminator has been cleared

Cause

This notification is generated when a protocol stops using a BFD session to track liveliness.

Effect

The specified protocol will no longer be notified by BFD if the associated sessions transitions from an Up to a Down state

2.5.5. bfdSessionDeleted

Table 36:  bfdSessionDeleted properties 

Property name

Value

Application name

bfd

Event name

bfdSessionDeleted

Default severity

notice

Message format string

BFD: Network-instance network-instance - Session from local-address:local-discriminator to remote-address:remote-discriminator has been deleted

Cause

This notification is generated when a BFD session has been removed from the configuration.

Effect

The BFD session has been removed.

2.5.6. bfdSessionUp

Table 37:  bfdSessionUp properties 

Property name

Value

Application name

bfd

Event name

bfdSessionUp

Default severity

notice

Message format string

BFD: Network-instance network-instance - Session from local-address:local-discriminator to remote-address:remote-discriminator is UP

Cause

This notification is generated when a BFD sessions transitions to the up state.

Effect

The BFD session is now operational.

2.5.7. microbfdDownEvent

Table 38:  microbfdDownEvent properties 

Property name

Value

Application name

bfd

Event name

microbfdDownEvent

Default severity

warning

Message format string

BFD: LAG lag-interface member member-interface - Session from local-address:local-discriminator to remote-address:remote-discriminator has transitioned to the down-state state with local-diagnostic code: local-diagnostic-str (local-diagnostic-code) and remote-diagnostic code: remote-diagnostic-str (remote-diagnostic-code)

Cause

This notification is generated when a BFD sessions transitions to the Down or Admin Down state from an Up state.

Effect

The specified BFD sessions is now down. If the new state is Down, the session is down due to a failure see the local or remote diagnostic code. If the new state is Admin-Down the session is down due to administrative reasons.

2.5.8. microbfdMaxSessionActive

Table 39:  microbfdMaxSessionActive properties 

Property name

Value

Application name

bfd

Event name

microbfdMaxSessionActive

Default severity

warning

Message format string

BFD: LAG lag-interface member member-interface - Session from local-address to remote-address could not be created because the maximum number of BFD sessions bfd-max-session are active.

Cause

This notification is generated when a BFD session cannot be created because the maximum number of BFD sessions are already active.

Effect

No more BFD sessions can be created until some existing sessions are removed.

2.5.9. microbfdSessionDeleted

Table 40:  microbfdSessionDeleted properties 

Property name

Value

Application name

bfd

Event name

microbfdSessionDeleted

Default severity

notice

Message format string

BFD: LAG lag-interface member member-interface - Session from local-address:local-discriminator to remote-address:remote-discriminator has been deleted

Cause

This notification is generated when a BFD session has been removed from the configuration.

Effect

The BFD session has been removed.

2.5.10. microbfdSessionUp

Table 41:  microbfdSessionUp properties 

Property name

Value

Application name

bfd

Event name

microbfdSessionUp

Default severity

notice

Message format string

BFD: LAG lag-interface member member-interface - Session from local-address:local-discriminator to remote-address:remote-discriminator is UP

Cause

This notification is generated when a BFD sessions transitions to the up state.

Effect

The BFD session is now operational.

2.6. bgp

2.6.1. bgpIncomingDynamicPeerLimitReached

Table 42:  bgpIncomingDynamicPeerLimitReached properties 

Property name

Value

Application name

bgp

Event name

bgpIncomingDynamicPeerLimitReached

Default severity

notice

Message format string

In network-instance network-instance, an incoming BGP connection from peer-address was rejected because the limit for the maximum number of incoming dynamic peers, max-sessions, has been reached.

Cause

The configured limit on the number of incoming sessions associated with dynamic peers has been reached.

Effect

The incoming connection attempt is rejected.

2.6.2. bgpInstanceConvergenceStateTransition

Table 43:  bgpInstanceConvergenceStateTransition properties 

Property name

Value

Application name

bgp

Event name

bgpInstanceConvergenceStateTransition

Default severity

notice

Message format string

In network-instance network-instance, the BGP convergence state for the address-family address family transitioned from the previous-state state to the new-state state

Cause

This event is generated when the BGP convergence process is being tracked and a state transition occurs

Effect

Dependent on the new state

2.6.3. bgpLowMemory

Table 44:  bgpLowMemory properties 

Property name

Value

Application name

bgp

Event name

bgpLowMemory

Default severity

critical

Message format string

In network-instance network-instance, the BGP session with peer-address was terminated immediately because BGP has out of memory.

Cause

BGP has run out of memory and this peer has been shutdown to reclaim some memory.

Effect

No routes can be exchanged with this peer.

2.6.4. bgpNeighborBackwardTransition

Table 45:  bgpNeighborBackwardTransition properties 

Property name

Value

Application name

bgp

Event name

bgpNeighborBackwardTransition

Default severity

warning

Message format string

In network-instance network-instance, the BGP session with peer-address moved from higher state last-state to lower state session-state due to event last-event

Cause

This event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state.

Effect

No routes can be exchanged with this peer.

2.6.5. bgpNeighborClosedTCPConn

Table 46:  bgpNeighborClosedTCPConn properties 

Property name

Value

Application name

bgp

Event name

bgpNeighborClosedTCPConn

Default severity

warning

Message format string

In network-instance network-instance, the BGP session with peer-address was closed because the neighbor closed the TCP connection.

Cause

The router received a TCP FIN message from its peer.

Effect

No routes can be exchanged with this peer.

2.6.6. bgpNeighborEstablished

Table 47:  bgpNeighborEstablished properties 

Property name

Value

Application name

bgp

Event name

bgpNeighborEstablished

Default severity

notice

Message format string

In network-instance network-instance, the BGP session with peer-address moved into the ESTABLISHED state

Cause

The BGP session entered the ESTABLISHED state.

Effect

Routes of negotiated address families can now be exchanged with this peer.

2.6.7. bgpNeighborGRHelpingStarted

Table 48:  bgpNeighborGRHelpingStarted properties 

Property name

Value

Application name

bgp

Event name

bgpNeighborGRHelpingStarted

Default severity

notice

Message format string

In network-instance network-instance, the router has started providing GR helper service to the neighbor peer-address

Cause

GR helper is activated

Effect

Routes previously received from the peer, prior to its restart, are retained as stale until the stale-routes-time expires.

2.6.8. bgpNeighborGRHelpingStopped

Table 49:  bgpNeighborGRHelpingStopped properties 

Property name

Value

Application name

bgp

Event name

bgpNeighborGRHelpingStopped

Default severity

notice

Message format string

In network-instance network-instance, the router has stopped providing GR helper service to the neighbor peer-address

Cause

GR helper is deactivated

Effect

Any remaining stale routes are immediately removed.

2.6.9. bgpNeighborHoldTimeExpired

Table 50:  bgpNeighborHoldTimeExpired properties 

Property name

Value

Application name

bgp

Event name

bgpNeighborHoldTimeExpired

Default severity

warning

Message format string

In network-instance network-instance, the BGP session with peer-address was terminated because a KEEPALIVE message was not received before the holdtime limit of negotiated-hold-time was reached.

Cause

BGP did not receive a KEEPALIVE message from the peer before the negotiated holdtime expired.

Effect

No routes can be exchanged with this peer.

2.6.10. bgpNeighborInvalidLocalIP

Table 51:  bgpNeighborInvalidLocalIP properties 

Property name

Value

Application name

bgp

Event name

bgpNeighborInvalidLocalIP

Default severity

warning

Message format string

In network-instance network-instance, an incoming BGP connection from peer-address was rejected because the destination IP address does not match the allowed local-address, local-address.

Cause

BGP configuration does not allow an incoming BGP connection to this IP address.

Effect

No routes can be exchanged with this peer.

2.6.11. bgpNeighborNoOpenReceived

Table 52:  bgpNeighborNoOpenReceived properties 

Property name

Value

Application name

bgp

Event name

bgpNeighborNoOpenReceived

Default severity

warning

Message format string

In network-instance network-instance, the BGP session with peer-address was terminated because an OPEN message was not received before the configured holdtime limit was reached.

Cause

BGP did not receive an OPEN message from the peer before the configured holdtime expired.

Effect

No routes can be exchanged with this peer.

2.6.12. bgpNeighborPrefixLimitReached

Table 53:  bgpNeighborPrefixLimitReached properties 

Property name

Value

Application name

bgp

Event name

bgpNeighborPrefixLimitReached

Default severity

notice

Message format string

In network-instance network-instance, the number of family routes received from the neighbor peer-address has exceeded the configured limit.

Cause

The number of received routes from the peer has exceeded the configured limit for the associated address family.

Effect

No effect. Routes above the limit are still received and processed.

2.6.13. bgpNeighborPrefixLimitThresholdReached

Table 54:  bgpNeighborPrefixLimitThresholdReached properties 

Property name

Value

Application name

bgp

Event name

bgpNeighborPrefixLimitThresholdReached

Default severity

notice

Message format string

In network-instance network-instance, the number of family routes received from the neighbor peer-address has exceeded the configured threshold, which is warning-threshold-pct% of the limit.

Cause

The number of received routes from the peer has exceeded the configured threshold for the associated address family.

Effect

No effect. Routes above the threshold are still received and processed.

2.6.14. bgpNeighborUnknownRemoteIP

Table 55:  bgpNeighborUnknownRemoteIP properties 

Property name

Value

Application name

bgp

Event name

bgpNeighborUnknownRemoteIP

Default severity

warning

Message format string

In network-instance network-instance, an incoming BGP connection from peer-address was rejected because the source IP address does not match the address of any configured neighbor or any dynamic-neighbor block.

Cause

BGP configuration does not allow an incoming BGP connection from this IP address.

Effect

No routes can be exchanged with this peer.

2.6.15. bgpNLRIInvalid

Table 56:  bgpNLRIInvalid properties 

Property name

Value

Application name

bgp

Event name

bgpNLRIInvalid

Default severity

warning

Message format string

In network-instance network-instance, a route for NLRI nlri was received from neighbor peer-address and it was ignored because it is considered an invalid NLRI.

Cause

The router received an UPDATE with an invalid NLRI

Effect

The route associated with the NLRI is not added or removed from the BGP RIB.

2.6.16. bgpNotificationReceivedFromNeighbor

Table 57:  bgpNotificationReceivedFromNeighbor properties 

Property name

Value

Application name

bgp

Event name

bgpNotificationReceivedFromNeighbor

Default severity

warning

Message format string

In network-instance network-instance, the BGP session with peer-address was closed because the neighbor sent a NOTIFICATION with code last-notification-error-code and subcode last-notification-error-subcode

Cause

The router received a NOTIFICATION message from its peer.

Effect

No routes can be exchanged with this peer.

2.6.17. bgpNotificationSentToNeighbor

Table 58:  bgpNotificationSentToNeighbor properties 

Property name

Value

Application name

bgp

Event name

bgpNotificationSentToNeighbor

Default severity

warning

Message format string

In network-instance network-instance, the BGP session with peer-address was closed because the router sent this neighbor a NOTIFICATION with code last-notification-error-code and subcode last-notification-error-subcode

Cause

The router sent a NOTIFICATION message to its peer.

Effect

No routes can be exchanged with this peer.

2.6.18. bgpOutgoingDynamicPeerLimitReached

Table 59:  bgpOutgoingDynamicPeerLimitReached properties 

Property name

Value

Application name

bgp

Event name

bgpOutgoingDynamicPeerLimitReached

Default severity

notice

Message format string

In network-instance network-instance, no session was initiated towards the LLDP-discovered address peer-address because the limit for the maximum number of outgoing dynamic peers, max-sessions, has been reached.

Cause

The configured limit on the number of outgoing sessions associated with dynamic peers has been reached.

Effect

No connection attempt is made by the router.

2.6.19. bgpPathAttributeDiscarded

Table 60:  bgpPathAttributeDiscarded properties 

Property name

Value

Application name

bgp

Event name

bgpPathAttributeDiscarded

Default severity

warning

Message format string

In network-instance network-instance, a path attribute of type attribute-type and length attribute-length was discarded in a route received from the neighbor peer-address.

Cause

The path attribute was malformed and the attribute-discard approach is used for this type of attribute.

Effect

The intended meaning of that path attribute is not applied but the UPDATE message is still processed for new reachabiity information.

2.6.20. bgpPathAttributeMalformed

Table 61:  bgpPathAttributeMalformed properties 

Property name

Value

Application name

bgp

Event name

bgpPathAttributeMalformed

Default severity

warning

Message format string

In network-instance network-instance, a path attribute of type attribute-type and length attribute-length that was received in a route from the neighbor peer-address was considered malformed.

Cause

The router considers a path attribute to be malformed, for example not the expected length. The UPDATE message can still be parsed though.

Effect

Dependent on the type of the malformed path attribute. Either the malformed attribute is discarded or else the entire UPDATE message is considered to have unreachable NLRI.

2.6.21. bgpRouteWithdrawnDueToError

Table 62:  bgpRouteWithdrawnDueToError properties 

Property name

Value

Application name

bgp

Event name

bgpRouteWithdrawnDueToError

Default severity

warning

Message format string

In network-instance network-instance, a route for NLRI nlri was received from neighbor peer-address and it was considered withdrawn because of a recoverable error in the UPDATE message.

Cause

The router received a malformed UPDATE and the malformed path attribute(s) require as a treat-as-withdraw error handling behavior for the included set of routes.

Effect

There is no reachability for the NLRI in the malformed UPDATE message.

2.6.22. bgpUpdateInvalid

Table 63:  bgpUpdateInvalid properties 

Property name

Value

Application name

bgp

Event name

bgpUpdateInvalid

Default severity

warning

Message format string

In network-instance network-instance, an UPDATE message received from neighbor peer-address was considered invalid and caused the connection to be closed because the NLRI could not be parsed correctly.

Cause

The router received a malformed UPDATE which made it is impossible to identify all of the NLRI correctly.

Effect

The session is shutdown.

2.7. bridgetable

2.7.1. l2SubinterfaceBridgeTableDuplicateMacAddress Deleted

Table 64:  l2SubinterfaceBridgeTableDuplicateMacAddressDeleted properties 

Property name

Value

Application name

bridgetable

Event name

l2SubinterfaceBridgeTableDuplicateMacAddressDeleted

Default severity

notice

Message format string

A duplicate MAC address mac-address detected on sub-interface interface.subinterface-index is now deleted.

Cause

This event is generated when a duplicate MAC address is deleted.

Effect

The duplicate mac-address is now deleted.

2.7.2. l2SubinterfaceBridgeTableDuplicateMacAddress Detected

Table 65:  l2SubinterfaceBridgeTableDuplicateMacAddressDetected properties 

Property name

Value

Application name

bridgetable

Event name

l2SubinterfaceBridgeTableDuplicateMacAddressDetected

Default severity

notice

Message format string

A duplicate MAC address mac-address was detected on sub-interface interface.subinterface-index.

Cause

This event is generated when a duplicate MAC address is detected, qualified by the bridge-table mac-duplication configuration under the network-instance and the sub-interfaces configured under the network-instance.

Effect

depending on the mac-duplication configuration, traffic destined to the duplicate mac-address maybe blackholed or not reprogrammed against any other sub-interface on the network-instance

2.7.3. l2SubinterfaceBridgeTableMacLimitHighUtilization

Table 66:  l2SubinterfaceBridgeTableMacLimitHighUtilization properties 

Property name

Value

Application name

bridgetable

Event name

l2SubinterfaceBridgeTableMacLimitHighUtilization

Default severity

warning

Message format string

The number of MAC addresses in the bridge table for sub-interface interface.subinterface-index has reached pct-threshold% of the allowed limit of maximum-entries.

Cause

This event is generated when the number of MAC addresses in the bridge table for a sub-interface reaches the configured warning threshold percentage of the allowed limit.

Effect

None

2.7.4. l2SubinterfaceBridgeTableMacLimitHighUtilization Lowered

Table 67:  l2SubinterfaceBridgeTableMacLimitHighUtilizationLowered properties 

Property name

Value

Application name

bridgetable

Event name

l2SubinterfaceBridgeTableMacLimitHighUtilizationLowered

Default severity

notice

Message format string

The number of MAC addresses in the bridge table for sub-interface interface.subinterface-index is below pct-threshold% (minus 5%) of the allowed limit of maximum-entries.

Cause

This event is generated when the number of MAC addresses in the bridge table for a sub-interface is below 5% minus the warning threshold percentage of the allowed limit, after having exceeded the maximum percentage threshold of the allowed limit.

Effect

None

2.7.5. l2SubinterfaceBridgeTableMacLimitLowered

Table 68:  l2SubinterfaceBridgeTableMacLimitLowered properties 

Property name

Value

Application name

bridgetable

Event name

l2SubinterfaceBridgeTableMacLimitLowered

Default severity

notice

Message format string

The number of MAC addresses in the bridge table for the sub-interface interface.subinterface-index is below the allowed limit of maximum-entries.

Cause

This event is generated when the number of MAC addresses in the bridge table for a sub-interface is below the allowed limit, after being above the allowed limit

Effect

new mac-addresses for the sub-interface can now be added to the bridge table.

2.7.6. l2SubinterfaceBridgeTableMacLimitReached

Table 69:  l2SubinterfaceBridgeTableMacLimitReached properties 

Property name

Value

Application name

bridgetable

Event name

l2SubinterfaceBridgeTableMacLimitReached

Default severity

warning

Message format string

The number of MAC addresses in the bridge table for the sub-interface interface.subinterface-index has reached the allowed limit of maximum-entries.

Cause

This event is generated when the number of MAC addresses in the bridge table for the sub-interface is at the allowed limit.

Effect

new mac-addresses for the sub-interface cannot be added in the bridge table.

2.7.7. networkInstanceBridgeTableDuplicateMacAddress Deleted

Table 70:  networkInstanceBridgeTableDuplicateMacAddressDeleted properties 

Property name

Value

Application name

bridgetable

Event name

networkInstanceBridgeTableDuplicateMacAddressDeleted

Default severity

notice

Message format string

A duplicate MAC address mac-address detected on network-instance is now deleted.

Cause

This event is generated when a duplicate MAC address is deleted.

Effect

The duplicate mac-address is now deleted.

2.7.8. networkInstanceBridgeTableDuplicateMacAddress Detected

Table 71:  networkInstanceBridgeTableDuplicateMacAddressDetected properties 

Property name

Value

Application name

bridgetable

Event name

networkInstanceBridgeTableDuplicateMacAddressDetected

Default severity

notice

Message format string

A duplicate MAC address mac-address was detected on network-instance.

Cause

This event is generated when a duplicate MAC address is detected, qualified by the bridge-table mac-duplication configuration under the network-instance and the sub-interfaces configured under the network-instance.

Effect

depending on the mac-duplication configuration, traffic destined to the duplicate mac-address maybe blackholed or not reprogrammed against any other sub-interface on the network-instance

2.7.9. networkInstanceBridgeTableMacLimitHighUtilization

Table 72:  networkInstanceBridgeTableMacLimitHighUtilization properties 

Property name

Value

Application name

bridgetable

Event name

networkInstanceBridgeTableMacLimitHighUtilization

Default severity

warning

Message format string

The number of MAC addresses in the bridge table of network-instance network-instance has reached pct-threshold% of the allowed limit of maximum-entries.

Cause

This event is generated when the number of MAC addresses in the bridge table of a network-instance reaches the configured warning threshold percentage of the allowed limit.

Effect

None

2.7.10. networkInstanceBridgeTableMacLimitHigh UtilizationLowered

Table 73:  networkInstanceBridgeTableMacLimitHighUtilizationLowered properties 

Property name

Value

Application name

bridgetable

Event name

networkInstanceBridgeTableMacLimitHighUtilizationLowered

Default severity

notice

Message format string

The number of MAC addresses in the bridge table of network-instance network-instance is now at pct-threshold% minus 5% of the allowed limit of maximum-entries.

Cause

This event is generated when the number of MAC addresses in the bridge table of the network-instance is at 5% minus the warning threshold percentage of the allowed limit, after having exceeded the maximum percentage threshold of the allowed limit.

Effect

None

2.7.11. networkInstanceBridgeTableMacLimitLowered

Table 74:  networkInstanceBridgeTableMacLimitLowered properties 

Property name

Value

Application name

bridgetable

Event name

networkInstanceBridgeTableMacLimitLowered

Default severity

notice

Message format string

The number of MAC addresses in the bridge table of network-instance network-instance is now below the allowed limit of maximum-entries.

Cause

This event is generated when the number of MAC addresses in the bridge table of a network-instance goes below the allowed limit, after being above the allowed limit

Effect

new mac-addresses can now be added to the bridge table.

2.7.12. networkInstanceBridgeTableMacLimitReached

Table 75:  networkInstanceBridgeTableMacLimitReached properties 

Property name

Value

Application name

bridgetable

Event name

networkInstanceBridgeTableMacLimitReached

Default severity

warning

Message format string

The number of MAC addresses in the bridge table of network-instance network-instance is at the allowed limit of maximum-entries.

Cause

This event is generated when the number of MAC addresses in the bridge table of a network-instance is at the allowed limit.

Effect

new mac-addresses cannot be added in the bridge table.

2.7.13. systemBridgeTableMacLimitHighUtilization

Table 76:  systemBridgeTableMacLimitHighUtilization properties 

Property name

Value

Application name

bridgetable

Event name

systemBridgeTableMacLimitHighUtilization

Default severity

warning

Message format string

The number of MAC addresses in the bridge table of the system has reached pct-threshold% of the allowed limit of maximum-entries.

Cause

This event is generated when the number of MAC addresses in the bridge table of the system reaches the configured warning threshold percentage of the allowed limit.

Effect

None

2.7.14. systemBridgeTableMacLimitHighUtilizationLowered

Table 77:  systemBridgeTableMacLimitHighUtilizationLowered properties 

Property name

Value

Application name

bridgetable

Event name

systemBridgeTableMacLimitHighUtilizationLowered

Default severity

notice

Message format string

The number of MAC addresses in the bridge table of the system is now at pct-threshold% minus 5% of the allowed limit of maximum-entries.

Cause

This event is generated when the number of MAC addresses in the bridge table of the system is at 5% minus the warning threshold percentage of the allowed limit, after having exceeded the maximum percentage threshold of the allowed limit.

Effect

None

2.7.15. systemBridgeTableMacLimitLowered

Table 78:  systemBridgeTableMacLimitLowered properties 

Property name

Value

Application name

bridgetable

Event name

systemBridgeTableMacLimitLowered

Default severity

notice

Message format string

The number of MAC addresses in the bridge table of the system is now below the allowed limit of maximum-entries.

Cause

This event is generated when the number of MAC addresses in the bridge table of the system goes below the allowed limit, after being above the allowed limit

Effect

new mac-addresses can now be added to the bridge table.

2.7.16. systemBridgeTableMacLimitReached

Table 79:  systemBridgeTableMacLimitReached properties 

Property name

Value

Application name

bridgetable

Event name

systemBridgeTableMacLimitReached

Default severity

warning

Message format string

The number of MAC addresses in the bridge table of the system is at the allowed limit of maximum-entries.

Cause

This event is generated when the number of MAC addresses in the bridge table of the system is at the allowed limit.

Effect

new mac-addresses cannot be added in any bridge table in the system.

2.7.17. vxlanInterfaceBridgeTableMulticastDestinations LimitHighUtilization

Table 80:  vxlanInterfaceBridgeTableMulticastDestinationsLimitHighUtilization properties 

Property name

Value

Application name

bridgetable

Event name

vxlanInterfaceBridgeTableMulticastDestinationsLimitHighUtilization

Default severity

warning

Message format string

The number of Vxlan Multicast Destinations in the bridge table for the vxlan-interface tunnel-interface.vxlan-interface has reached pct-threshold% of the allowed limit of maximum-entries.

Cause

This event is generated when the number of Vxlan Multicast Destinations in the vxlan-interface reaches the warning threshold percentage of the allowed limit.

Effect

None

2.7.18. vxlanInterfaceBridgeTableMulticastDestinations LimitHighUtilizationLowered

Table 81:  vxlanInterfaceBridgeTableMulticastDestinationsLimitHighUtilizationLowered properties 

Property name

Value

Application name

bridgetable

Event name

vxlanInterfaceBridgeTableMulticastDestinationsLimitHighUtilizationLowered

Default severity

notice

Message format string

The number of Vxlan Multicast Destinations in the bridge table for the vxlan-interface tunnel-interface.vxlan-interface is now below a pct-threshold% minus 5% of the allowed limit of maximum-entries.

Cause

This event is generated when the number of Vxlan Multicast Destinations in the vxlan-interface is 5% below the warning threshold percentage of the allowed limit, after having exceeded the maximum percentage threshold of the allowed limit.

Effect

None

2.7.19. vxlanInterfaceBridgeTableMulticastDestinations LimitLowered

Table 82:  vxlanInterfaceBridgeTableMulticastDestinationsLimitLowered properties 

Property name

Value

Application name

bridgetable

Event name

vxlanInterfaceBridgeTableMulticastDestinationsLimitLowered

Default severity

notice

Message format string

The number of Vxlan Multicast Destinations in the bridge table for the vxlan-interface tunnel-interface.vxlan-interface is now below the allowed limit of maximum-entries.

Cause

This event is generated when the number of Vxlan Multicast Destinations in a vxlan-interface goes below the allowed limit, after being above the allowed limit

Effect

New Vxlan Multicast Destinations can be added to the vxlan-interface.

2.7.20. vxlanInterfaceBridgeTableMulticastDestinations LimitReached

Table 83:  vxlanInterfaceBridgeTableMulticastDestinationsLimitReached properties 

Property name

Value

Application name

bridgetable

Event name

vxlanInterfaceBridgeTableMulticastDestinationsLimitReached

Default severity

warning

Message format string

The number of Vxlan Multicast Destinations in the bridge table for the vxlan-interface tunnel-interface.vxlan-interface is at the allowed limit of maximum-entries.

Cause

This event is generated when the number of Vxlan Multicast Destinations in a vxlan-interface is at the allowed limit.

Effect

New Vxlan Multicast Destinations cannot be added to the vxlan-interface.

2.8. chassis

2.8.1. platformDatapathResourceHighUtilization

Table 84:  platformDatapathResourceHighUtilization properties 

Property name

Value

Application name

chassis

Event name

platformDatapathResourceHighUtilization

Default severity

warning

Message format string

The datapath resource called resource-name has reached threshold% or more utilization on linecard linecard, forwarding complex forwarding-complex

Cause

This event is generated when the utilization of a datapath resource has increased to a level that may warrant concern if further resources are consumed

Effect

None

2.8.2. platformDatapathResourceHighUtilizationLowered

Table 85:  platformDatapathResourceHighUtilizationLowered properties 

Property name

Value

Application name

chassis

Event name

platformDatapathResourceHighUtilizationLowered

Default severity

notice

Message format string

The datapath resource called resource-name has decreased back to threshold% or less utilization on linecard linecard, forwarding complex forwarding-complex

Cause

This event is generated when the utilization of a datapath resource has decreased to a level that may no longer warrant concern

Effect

None

2.8.3. platformDatapathResourceLimitCleared

Table 86:  platformDatapathResourceLimitCleared properties 

Property name

Value

Application name

chassis

Event name

platformDatapathResourceLimitCleared

Default severity

notice

Message format string

The datapath resource called resource-name has decreased from 100% utilization back to 95% or less utilization on linecard linecard, forwarding complex forwarding-complex

Cause

This event is generated when the utilization of a datapath resource has decreased to a level such that resource exhaustion is no longer imminent

Effect

None

2.8.4. platformDatapathResourceLimitReached

Table 87:  platformDatapathResourceLimitReached properties 

Property name

Value

Application name

chassis

Event name

platformDatapathResourceLimitReached

Default severity

warning

Message format string

The datapath resource called resource-name has reached 100% utilization on linecard linecard, forwarding complex forwarding-complex

Cause

This event is generated when the utilization of a datapath resource has exhausted the resource

Effect

None

2.8.5. platformMtuHighUtilization

Table 88:  platformMtuHighUtilization properties 

Property name

Value

Application name

chassis

Event name

platformMtuHighUtilization

Default severity

warning

Message format string

The MTU resource called resource-name has reached threshold% or more utilization on linecard linecard, forwarding complex forwarding-complex. Only free-entries entries are remaining.

Cause

This event is generated when the utilization of an MTU resource has increased to a level that may warrant concern if further resources are consumed

Effect

None

2.8.6. platformMtuHighUtilizationLowered

Table 89:  platformMtuHighUtilizationLowered properties 

Property name

Value

Application name

chassis

Event name

platformMtuHighUtilizationLowered

Default severity

notice

Message format string

The MTU resource called resource-name has decreased back to threshold% or less utilization on linecard linecard, forwarding complex forwarding-complex.

Cause

This event is generated when the utilization of an MTU resource has decreased to a level that may no longer warrant concern

Effect

None

2.8.7. platformPipelineResourceHighUtilization

Table 90:  platformPipelineResourceHighUtilization properties 

Property name

Value

Application name

chassis

Event name

platformPipelineResourceHighUtilization

Default severity

warning

Message format string

The pipeline resource called resource-name has reached threshold% or more utilization on linecard linecard, forwarding complex forwarding-complex, pipeline pipeline

Cause

This event is generated when the utilization of a pipeline resource has increased to a level that may warrant concern if futher resources are consumed

Effect

None

2.8.8. platformPipelineResourceHighUtilizationLowered

Table 91:  platformPipelineResourceHighUtilizationLowered properties 

Property name

Value

Application name

chassis

Event name

platformPipelineResourceHighUtilizationLowered

Default severity

notice

Message format string

The pipeline resource called resource-name has decreased back to threshold% or less utilization on linecard linecard, forwarding complex forwarding-complex, pipeline pipeline

Cause

This event is generated when the utilization of a pipeline resource has decreased to a level that may no longer warrant concern

Effect

None

2.8.9. platformPipelineResourceLimitCleared

Table 92:  platformPipelineResourceLimitCleared properties 

Property name

Value

Application name

chassis

Event name

platformPipelineResourceLimitCleared

Default severity

notice

Message format string

The pipeline resource called resource-name has decreased from 100% utilization back to 95% or less utilization on linecard linecard, forwarding complex forwarding-complex, pipeline

Cause

This event is generated when the utilization of a pipeline resource has decreased to a level such that resource exhaustion is no longer imminent

Effect

None

2.8.10. platformPipelineResourceLimitReached

Table 93:  platformPipelineResourceLimitReached properties 

Property name

Value

Application name

chassis

Event name

platformPipelineResourceLimitReached

Default severity

warning

Message format string

The pipeline resource called resource-name has reached 100% utilization on linecard linecard, forwarding complex forwarding-complex, pipeline

Cause

This event is generated when the utilization of a pipeline resource has exhausted the resource

Effect

None

2.8.11. portDown

Table 94:  portDown properties 

Property name

Value

Application name

chassis

Event name

portDown

Default severity

warning

Message format string

Interface interface_name is now down for reason: oper_down_reason

Cause

The interface has transitioned from the up state to the down state

Effect

The interface is now down

2.8.12. portUp

Table 95:  portUp properties 

Property name

Value

Application name

chassis

Event name

portUp

Default severity

notice

Message format string

Interface interface_name is now up

Cause

The interface has transitioned from the down state to the up state

Effect

The interface is now up

2.8.13. subinterfaceDown

Table 96:  subinterfaceDown properties 

Property name

Value

Application name

chassis

Event name

subinterfaceDown

Default severity

warning

Message format string

The subinterface subinterface_name is now down for reason: oper_down_reason

Cause

This event is generated when the subinterface has transitioned from the up state to the down state

Effect

The subinterface is now down

2.8.14. subinterfaceUp

Table 97:  subinterfaceUp properties 

Property name

Value

Application name

chassis

Event name

subinterfaceUp

Default severity

notice

Message format string

The subinterface subinterface_name is now up

Cause

This event is generated when the subinterface has transitioned from the down state to the up state.

Effect

The subinterface is now up

2.8.15. transceiverChannelHighInputPowerAlarm

Table 98:  transceiverChannelHighInputPowerAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelHighInputPowerAlarm

Default severity

critical

Message format string

The input power measured for channel channel_num of the transceiver associated with interface interface_name has increased to high_threshold dBm or more

Cause

The input power of the optical channel has increased

Effect

High input power may affect transceiver performance

2.8.16. transceiverChannelHighInputPowerAlarmClear

Table 99:  transceiverChannelHighInputPowerAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelHighInputPowerAlarmClear

Default severity

informational

Message format string

The input power measured for channel channel_num of the transceiver associated with interface interface_name has decreased below high_threshold dBm

Cause

The input power of the optical channel has decreased

Effect

High input power may affect transceiver performance

2.8.17. transceiverChannelHighInputPowerWarning

Table 100:  transceiverChannelHighInputPowerWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelHighInputPowerWarning

Default severity

warning

Message format string

The input power measured for channel channel_num of the transceiver associated with interface interface_name has increased to high_threshold dBm or more

Cause

The input power of the optical channel has increased

Effect

High input power may affect transceiver performance

2.8.18. transceiverChannelHighInputPowerWarningClear

Table 101:  transceiverChannelHighInputPowerWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelHighInputPowerWarningClear

Default severity

informational

Message format string

The input power measured for channel channel_num of the transceiver associated with interface interface_name has decreased below high_threshold dBm

Cause

The input power of the optical channel has decreased

Effect

High input power may affect transceiver performance

2.8.19. transceiverChannelHighLaserBiasCurrentAlarm

Table 102:  transceiverChannelHighLaserBiasCurrentAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelHighLaserBiasCurrentAlarm

Default severity

critical

Message format string

The laser bias current supplied to channel channel_num of the transceiver associated with interface interface_name has increased to high_threshold mA or more

Cause

Laser bias increases with temperature and age. Consider lowering the ambient temperature or replacing the laser.

Effect

High laser bias may affect transceiver performance

2.8.20. transceiverChannelHighLaserBiasCurrentAlarm Clear

Table 103:  transceiverChannelHighLaserBiasCurrentAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelHighLaserBiasCurrentAlarmClear

Default severity

informational

Message format string

The laser bias current supplied to channel channel_num of the transceiver associated with interface interface_name has decreased below high_threshold mA

Cause

Laser bias current has decreased

Effect

High laser bias may affect transceiver performance

2.8.21. transceiverChannelHighLaserBiasCurrentWarning

Table 104:  transceiverChannelHighLaserBiasCurrentWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelHighLaserBiasCurrentWarning

Default severity

warning

Message format string

The laser bias current supplied to channel channel_num of the transceiver associated with interface interface_name has increased to high_threshold mA or more

Cause

Laser bias increases with temperature and age. Consider lowering the ambient temperature or replacing the laser.

Effect

High laser bias may affect transceiver performance

2.8.22. transceiverChannelHighLaserBiasCurrentWarning Clear

Table 105:  transceiverChannelHighLaserBiasCurrentWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelHighLaserBiasCurrentWarningClear

Default severity

informational

Message format string

The laser bias current supplied to channel channel_num of the transceiver associated with interface interface_name has decreased below high_threshold mA

Cause

Laser bias current has decreased

Effect

High laser bias may affect transceiver performance

2.8.23. transceiverChannelHighOutputPowerAlarm

Table 106:  transceiverChannelHighOutputPowerAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelHighOutputPowerAlarm

Default severity

critical

Message format string

The output power measured for channel channel_num of the transceiver associated with interface interface_name has increased to high_threshold dBm or more

Cause

The output power of the optical channel has increased

Effect

High output power may affect transceiver performance

2.8.24. transceiverChannelHighOutputPowerAlarmClear

Table 107:  transceiverChannelHighOutputPowerAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelHighOutputPowerAlarmClear

Default severity

informational

Message format string

The output power measured for channel channel_num of the transceiver associated with interface interface_name has decreased below high_threshold dBm

Cause

The output power of the optical channel has decreased

Effect

High output power may affect transceiver performance

2.8.25. transceiverChannelHighOutputPowerWarning

Table 108:  transceiverChannelHighOutputPowerWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelHighOutputPowerWarning

Default severity

warning

Message format string

The output power measured for channel channel_num of the transceiver associated with interface interface_name has increased to high_threshold dBm or more

Cause

The output power of the optical channel has increased

Effect

High output power may affect transceiver performance

2.8.26. transceiverChannelHighOutputPowerWarning Clear

Table 109:  transceiverChannelHighOutputPowerWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelHighOutputPowerWarningClear

Default severity

informational

Message format string

The output power measured for channel channel_num of the transceiver associated with interface interface_name has decreased below high_threshold dBm

Cause

The output power of the optical channel has decreased

Effect

High output power may affect transceiver performance

2.8.27. transceiverChannelLowInputPowerAlarm

Table 110:  transceiverChannelLowInputPowerAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelLowInputPowerAlarm

Default severity

critical

Message format string

The input power measured for channel channel_num of the transceiver associated with interface interface_name has decreased to low_threshold dBm or less

Cause

The input power of the optical channel has decreased

Effect

Low input power may affect transceiver performance

2.8.28. transceiverChannelLowInputPowerAlarmClear

Table 111:  transceiverChannelLowInputPowerAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelLowInputPowerAlarmClear

Default severity

informational

Message format string

The input power measured for channel channel_num of the transceiver associated with interface interface_name has increased above low_threshold dBm

Cause

The input power of the optical channel has increased

Effect

Low input power may affect transceiver performance

2.8.29. transceiverChannelLowInputPowerWarning

Table 112:  transceiverChannelLowInputPowerWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelLowInputPowerWarning

Default severity

warning

Message format string

The input power measured for channel channel_num of the transceiver associated with interface interface_name has decreased to low_threshold dBm or less

Cause

The input power of the optical channel has decreased

Effect

Low input power may affect transceiver performance

2.8.30. transceiverChannelLowInputPowerWarningClear

Table 113:  transceiverChannelLowInputPowerWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelLowInputPowerWarningClear

Default severity

informational

Message format string

The input power measured for channel channel_num of the transceiver associated with interface interface_name has increased above low_threshold dBm

Cause

The input power of the optical channel has increased

Effect

Low input power may affect transceiver performance

2.8.31. transceiverChannelLowLaserBiasCurrentAlarm

Table 114:  transceiverChannelLowLaserBiasCurrentAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelLowLaserBiasCurrentAlarm

Default severity

critical

Message format string

The laser bias current supplied to channel channel_num of the transceiver associated with interface interface_name has decreased to low_threshold mA or less

Cause

The laser bias current of the optical channel has decreased

Effect

Low laser bias current may affect transceiver performance

2.8.32. transceiverChannelLowLaserBiasCurrentAlarmClear

Table 115:  transceiverChannelLowLaserBiasCurrentAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelLowLaserBiasCurrentAlarmClear

Default severity

informational

Message format string

The laser bias current supplied to channel channel_num of the transceiver associated with interface interface_name has increased above low_threshold mA

Cause

The laser bias current of the optical channel has increased

Effect

Low laser bias current may affect transceiver performance

2.8.33. transceiverChannelLowLaserBiasCurrentWarning

Table 116:  transceiverChannelLowLaserBiasCurrentWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelLowLaserBiasCurrentWarning

Default severity

warning

Message format string

The laser bias current supplied to channel channel_num of the transceiver associated with interface interface_name has decreased to low_threshold mA or less

Cause

The laser bias current of the optical channel has decreased

Effect

Low laser bias current may affect transceiver performance

2.8.34. transceiverChannelLowLaserBiasCurrentWarningClear

Table 117:  transceiverChannelLowLaserBiasCurrentWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelLowLaserBiasCurrentWarningClear

Default severity

informational

Message format string

The laser bias current supplied to channel channel_num of the transceiver associated with interface interface_name has increased above low_threshold mA

Cause

The laser bias current of the optical channel has increased

Effect

Low laser bias current may affect transceiver performance

2.8.35. transceiverChannelLowOutputPowerAlarm

Table 118:  transceiverChannelLowOutputPowerAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelLowOutputPowerAlarm

Default severity

critical

Message format string

The output power measured for channel channel_num of the transceiver associated with interface interface_name has decreased to low_threshold dBm or less

Cause

The output power of the optical channel has decreased

Effect

Low output power may affect transceiver performance

2.8.36. transceiverChannelLowOutputPowerAlarmClear

Table 119:  transceiverChannelLowOutputPowerAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelLowOutputPowerAlarmClear

Default severity

informational

Message format string

The output power measured for channel channel_num of the transceiver associated with interface interface_name has increased above low_threshold dBm

Cause

The output power of the optical channel has increased

Effect

Low output power may affect transceiver performance

2.8.37. transceiverChannelLowOutputPowerWarning

Table 120:  transceiverChannelLowOutputPowerWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelLowOutputPowerWarning

Default severity

warning

Message format string

The output power measured for channel channel_num of the transceiver associated with interface interface_name has decreased to low_threshold dBm or less

Cause

The output power of the optical channel has decreased

Effect

Low output power may affect transceiver performance

2.8.38. transceiverChannelLowOutputPowerWarningClear

Table 121:  transceiverChannelLowOutputPowerWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverChannelLowOutputPowerWarningClear

Default severity

informational

Message format string

The output power measured for channel channel_num of the transceiver associated with interface interface_name has increased above low_threshold dBm

Cause

The output power of the optical channel has increased

Effect

Low output power may affect transceiver performance

2.8.39. transceiverHighInputPowerAlarm

Table 122:  transceiverHighInputPowerAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverHighInputPowerAlarm

Default severity

critical

Message format string

The input power measured for the transceiver associated with interface interface_name has increased to high_threshold dBm or more

Cause

The input power of the optics has increased

Effect

High input power may affect transceiver performance

2.8.40. transceiverHighInputPowerAlarmClear

Table 123:  transceiverHighInputPowerAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverHighInputPowerAlarmClear

Default severity

informational

Message format string

The input power measured for the transceiver associated with interface interface_name has decreased below high_threshold dBm

Cause

The input power of the optics has decreased

Effect

High input power may affect transceiver performance

2.8.41. transceiverHighInputPowerWarning

Table 124:  transceiverHighInputPowerWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverHighInputPowerWarning

Default severity

warning

Message format string

The input power measured for the transceiver associated with interface interface_name has increased to high_threshold dBm or more

Cause

The input power of the optics has increased

Effect

High input power may affect transceiver performance

2.8.42. transceiverHighInputPowerWarningClear

Table 125:  transceiverHighInputPowerWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverHighInputPowerWarningClear

Default severity

informational

Message format string

The input power measured for the transceiver associated with interface interface_name has decreased below high_threshold dBm

Cause

The input power of the opticsl has decreased

Effect

High input power may affect transceiver performance

2.8.43. transceiverHighLaserBiasCurrentAlarm

Table 126:  transceiverHighLaserBiasCurrentAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverHighLaserBiasCurrentAlarm

Default severity

critical

Message format string

The laser bias current supplied to the transceiver associated with interface interface_name has increased to high_threshold mA or more

Cause

Laser bias increases with temperature and age. Consider lowering the ambient temperature or replacing the laser.

Effect

High laser bias may affect transceiver performance

2.8.44. transceiverHighLaserBiasCurrentAlarmClear

Table 127:  transceiverHighLaserBiasCurrentAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverHighLaserBiasCurrentAlarmClear

Default severity

informational

Message format string

The laser bias current supplied to the transceiver associated with interface interface_name has decreased below high_threshold mA

Cause

Laser bias current has decreased

Effect

High laser bias may affect transceiver performance

2.8.45. transceiverHighLaserBiasCurrentWarning

Table 128:  transceiverHighLaserBiasCurrentWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverHighLaserBiasCurrentWarning

Default severity

warning

Message format string

The laser bias current supplied to the transceiver associated with interface interface_name has increased to high_threshold mA or more

Cause

Laser bias increases with temperature and age. Consider lowering the ambient temperature or replacing the laser.

Effect

High laser bias may affect transceiver performance

2.8.46. transceiverHighLaserBiasCurrentWarningClear

Table 129:  transceiverHighLaserBiasCurrentWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverHighLaserBiasCurrentWarningClear

Default severity

informational

Message format string

The laser bias current supplied to the transceiver associated with interface interface_name has decreased below high_threshold mA

Cause

Laser bias current has decreased

Effect

High laser bias may affect transceiver performance

2.8.47. transceiverHighOutputPowerAlarm

Table 130:  transceiverHighOutputPowerAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverHighOutputPowerAlarm

Default severity

critical

Message format string

The output power measured for the transceiver associated with interface interface_name has increased to high_threshold dBm or more

Cause

The output power of the optics has increased

Effect

High output power may affect transceiver performance

2.8.48. transceiverHighOutputPowerAlarmClear

Table 131:  transceiverHighOutputPowerAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverHighOutputPowerAlarmClear

Default severity

informational

Message format string

The output power measured for the transceiver associated with interface interface_name has decreased below high_threshold dBm

Cause

The output power of the optics has decreased

Effect

High output power may affect transceiver performance

2.8.49. transceiverHighOutputPowerWarning

Table 132:  transceiverHighOutputPowerWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverHighOutputPowerWarning

Default severity

warning

Message format string

The output power measured for the transceiver associated with interface interface_name has increased to high_threshold dBm or more

Cause

The output power of the optics has increased

Effect

High output power may affect transceiver performance

2.8.50. transceiverHighOutputPowerWarningClear

Table 133:  transceiverHighOutputPowerWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverHighOutputPowerWarningClear

Default severity

informational

Message format string

The output power measured for the transceiver associated with interface interface_name has decreased below high_threshold dBm

Cause

The output power of the optics has decreased

Effect

High output power may affect transceiver performance

2.8.51. transceiverLowInputPowerAlarm

Table 134:  transceiverLowInputPowerAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverLowInputPowerAlarm

Default severity

critical

Message format string

The input power measured for the transceiver associated with interface interface_name has decreased to low_threshold dBm or less

Cause

The input power of the optics has decreased

Effect

Low input power may affect transceiver performance

2.8.52. transceiverLowInputPowerAlarmClear

Table 135:  transceiverLowInputPowerAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverLowInputPowerAlarmClear

Default severity

informational

Message format string

The input power measured for the transceiver associated with interface interface_name has increased above low_threshold dBm

Cause

The input power of the optics has increased

Effect

Low input power may affect transceiver performance

2.8.53. transceiverLowInputPowerWarning

Table 136:  transceiverLowInputPowerWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverLowInputPowerWarning

Default severity

warning

Message format string

The input power measured for the transceiver associated with interface interface_name has decreased to low_threshold dBm or less

Cause

The input power of the optics has decreased

Effect

Low input power may affect transceiver performance

2.8.54. transceiverLowInputPowerWarningClear

Table 137:  transceiverLowInputPowerWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverLowInputPowerWarningClear

Default severity

informational

Message format string

The input power measured for the transceiver associated with interface interface_name has increased above low_threshold dBm

Cause

The input power of the optics has increased

Effect

Low input power may affect transceiver performance

2.8.55. transceiverLowLaserBiasCurrentAlarm

Table 138:  transceiverLowLaserBiasCurrentAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverLowLaserBiasCurrentAlarm

Default severity

critical

Message format string

The laser bias current supplied to the transceiver associated with interface interface_name has decreased to low_threshold mA or less

Cause

The laser bias current of the optics has decreased

Effect

Low laser bias current may affect transceiver performance

2.8.56. transceiverLowLaserBiasCurrentAlarmClear

Table 139:  transceiverLowLaserBiasCurrentAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverLowLaserBiasCurrentAlarmClear

Default severity

informational

Message format string

The laser bias current supplied to the transceiver associated with interface interface_name has increased above low_threshold mA

Cause

The laser bias current of the optics has increased

Effect

Low laser bias current may affect transceiver performance

2.8.57. transceiverLowLaserBiasCurrentWarning

Table 140:  transceiverLowLaserBiasCurrentWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverLowLaserBiasCurrentWarning

Default severity

warning

Message format string

The laser bias current supplied to the transceiver associated with interface interface_name has decreased to low_threshold mA or less

Cause

The laser bias current of the optics has decreased

Effect

Low laser bias current may affect transceiver performance

2.8.58. transceiverLowLaserBiasCurrentWarningClear

Table 141:  transceiverLowLaserBiasCurrentWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverLowLaserBiasCurrentWarningClear

Default severity

informational

Message format string

The laser bias current supplied to the transceiver associated with interface interface_name has increased above low_threshold mA

Cause

The laser bias current of the optics has increased

Effect

Low laser bias current may affect transceiver performance

2.8.59. transceiverLowOutputPowerAlarm

Table 142:  transceiverLowOutputPowerAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverLowOutputPowerAlarm

Default severity

critical

Message format string

The output power measured for the transceiver associated with interface interface_name has decreased to low_threshold dBm or less

Cause

The output power of the optics has decreased

Effect

Low output power may affect transceiver performance

2.8.60. transceiverLowOutputPowerAlarmClear

Table 143:  transceiverLowOutputPowerAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverLowOutputPowerAlarmClear

Default severity

informational

Message format string

The output power measured for the transceiver associated with interface interface_name has increased above low_threshold dBm

Cause

The output power of the optics has increased

Effect

Low output power may affect transceiver performance

2.8.61. transceiverLowOutputPowerWarning

Table 144:  transceiverLowOutputPowerWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverLowOutputPowerWarning

Default severity

warning

Message format string

The output power measured for the transceiver associated with interface interface_name has decreased to low_threshold dBm or less

Cause

The output power of the optics has decreased

Effect

Low output power may affect transceiver performance

2.8.62. transceiverLowOutputPowerWarningClear

Table 145:  transceiverLowOutputPowerWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverLowOutputPowerWarningClear

Default severity

informational

Message format string

The output power measured for the transceiver associated with interface interface_name has increased above low_threshold dBm

Cause

The output power of the optics has increased

Effect

Low output power may affect transceiver performance

2.8.63. transceiverModuleDown

Table 146:  transceiverModuleDown properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleDown

Default severity

warning

Message format string

The transceiver associated with the interface interface_name is now down

Cause

The transceiver oper-state has transitioned from the up state to any lower state

Effect

The transceiver is not operational

2.8.64. transceiverModuleHighTemperatureAlarm

Table 147:  transceiverModuleHighTemperatureAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleHighTemperatureAlarm

Default severity

critical

Message format string

The temperature of the transceiver associated with the interface interface_name has increased to high_threshold degrees C or more

Cause

The temperature of the transceiver module has increased

Effect

High temperatures may affect transceiver performance

2.8.65. transceiverModuleHighTemperatureAlarmClear

Table 148:  transceiverModuleHighTemperatureAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleHighTemperatureAlarmClear

Default severity

informational

Message format string

The temperature of the transceiver associated with the interface interface_name has decreased below high_threshold degrees C

Cause

The temperature of the transceiver module has decreased

Effect

High temperatures may affect transceiver performance

2.8.66. transceiverModuleHighTemperatureWarning

Table 149:  transceiverModuleHighTemperatureWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleHighTemperatureWarning

Default severity

warning

Message format string

The temperature of the transceiver associated with the interface interface_name has increased to high_threshold degrees C or more

Cause

The temperature of the transceiver module has increased

Effect

High temperatures may affect transceiver performance

2.8.67. transceiverModuleHighTemperatureWarningClear

Table 150:  transceiverModuleHighTemperatureWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleHighTemperatureWarningClear

Default severity

informational

Message format string

The temperature of the transceiver associated with the interface interface_name has decreased below high_threshold degrees C

Cause

The temperature of the transceiver module has decreased

Effect

High temperatures may affect transceiver performance

2.8.68. transceiverModuleHighVoltageAlarm

Table 151:  transceiverModuleHighVoltageAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleHighVoltageAlarm

Default severity

critical

Message format string

The voltage of the transceiver associated with the interface interface_name has increased to high_threshold Volts or more

Cause

The voltage supplied to the transceiver module has increased

Effect

High voltages may affect transceiver performance

2.8.69. transceiverModuleHighVoltageAlarmClear

Table 152:  transceiverModuleHighVoltageAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleHighVoltageAlarmClear

Default severity

informational

Message format string

The voltage of the transceiver associated with the interface interface_name has decreased below high_threshold Volts

Cause

The voltage supplied to the transceiver module has decreased

Effect

High voltages may affect transceiver performance

2.8.70. transceiverModuleHighVoltageWarning

Table 153:  transceiverModuleHighVoltageWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleHighVoltageWarning

Default severity

warning

Message format string

The voltage of the transceiver associated with the interface interface_name has increased to high_threshold Volts or more

Cause

The voltage supplied to the transceiver module has increased

Effect

High voltages may affect transceiver performance

2.8.71. transceiverModuleHighVoltageWarningClear

Table 154:  transceiverModuleHighVoltageWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleHighVoltageWarningClear

Default severity

informational

Message format string

The voltage of the transceiver associated with the interface interface_name has decreased below high_threshold Volts

Cause

The voltage supplied to the transceiver module has decreased

Effect

High voltages may affect transceiver performance

2.8.72. transceiverModuleLowTemperatureAlarm

Table 155:  transceiverModuleLowTemperatureAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleLowTemperatureAlarm

Default severity

critical

Message format string

The temperature of the transceiver associated with the interface interface_name has decreased to low_threshold degrees C or less

Cause

The temperature of the transceiver module has decreased

Effect

Low temperatures may affect transceiver performance

2.8.73. transceiverModuleLowTemperatureAlarmClear

Table 156:  transceiverModuleLowTemperatureAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleLowTemperatureAlarmClear

Default severity

informational

Message format string

The temperature of the transceiver associated with the interface interface_name has increased above low_threshold degrees C

Cause

The temperature of the transceiver module has increased

Effect

Low temperatures may affect transceiver performance

2.8.74. transceiverModuleLowTemperatureWarning

Table 157:  transceiverModuleLowTemperatureWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleLowTemperatureWarning

Default severity

warning

Message format string

The temperature of the transceiver associated with the interface interface_name has decreased to low_threshold degrees C or less

Cause

The temperature of the transceiver module has decreased

Effect

Low temperatures may affect transceiver performance

2.8.75. transceiverModuleLowTemperatureWarningClear

Table 158:  transceiverModuleLowTemperatureWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleLowTemperatureWarningClear

Default severity

informational

Message format string

The temperature of the transceiver associated with the interface interface_name has increased above low_threshold degrees C

Cause

The temperature of the transceiver module has increased

Effect

Low temperatures may affect transceiver performance

2.8.76. transceiverModuleLowVoltageAlarm

Table 159:  transceiverModuleLowVoltageAlarm properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleLowVoltageAlarm

Default severity

critical

Message format string

The voltage of the transceiver associated with the interface interface_name has decreased to low_threshold Volts or less

Cause

The voltage supplied to the transceiver module has decreased

Effect

Low voltages may affect transceiver performance

2.8.77. transceiverModuleLowVoltageAlarmClear

Table 160:  transceiverModuleLowVoltageAlarmClear properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleLowVoltageAlarmClear

Default severity

informational

Message format string

The voltage of the transceiver associated with the interface interface_name has increased above low_threshold Volts

Cause

The voltage supplied to the transceiver module has increased

Effect

Low voltages may affect transceiver performance

2.8.78. transceiverModuleLowVoltageWarning

Table 161:  transceiverModuleLowVoltageWarning properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleLowVoltageWarning

Default severity

warning

Message format string

The voltage of the transceiver associated with the interface interface_name has decreased to low_threshold Volts or less

Cause

The voltage supplied to the transceiver module has decreased

Effect

Low voltages may affect transceiver performance

2.8.79. transceiverModuleLowVoltageWarningClear

Table 162:  transceiverModuleLowVoltageWarningClear properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleLowVoltageWarningClear

Default severity

informational

Message format string

The voltage of the transceiver associated with the interface interface_name has increased above low_threshold Volts

Cause

The voltage supplied to the transceiver module has increased

Effect

Low voltages may affect transceiver performance

2.8.80. transceiverModuleUp

Table 163:  transceiverModuleUp properties 

Property name

Value

Application name

chassis

Event name

transceiverModuleUp

Default severity

notice

Message format string

The transceiver associated with the interface interface_name is now up

Cause

The transceiver oper-state has transitioned from any other state to the up state

Effect

The transceiver is now operational

2.9. debug

2.9.1. setAllConfigLevels

Table 164:  setAllConfigLevels properties 

Property name

Value

Application name

debug

Event name

setAllConfigLevels

Default severity

informational

Message format string

App config debug log levels set to: new_level.

Cause

Configuration of debug log levels that can be received by program parameter or via idb.

Effect

Sticky levels are losable only to another configuration setting.

2.9.2. setAllStartupLevels

Table 165:  setAllStartupLevels properties 

Property name

Value

Application name

debug

Event name

setAllStartupLevels

Default severity

informational

Message format string

App debug startup log levels set to: new_level (configuration can override).

Cause

Restrain of logging verbosity internal to some programs

Effect

If configuration is set, and goes away, the startup levels are respected.

2.9.3. setHighBaselineLogLevels

Table 166:  setHighBaselineLogLevels properties 

Property name

Value

Application name

debug

Event name

setHighBaselineLogLevels

Default severity

informational

Message format string

Default (startup), and runtime app debug log levels set to: new_level. Except for modules: {configured_list}

Cause

Boot phase time is up, and verbose messages are suppressed in a beta build with .

Effect

Internal setting to all levels. If module levels are configured, they restore to the setting.

2.10. dhcp

2.10.1. dhcp6ClientAddressDeclined

Table 167:  dhcp6ClientAddressDeclined properties 

Property name

Value

Application name

dhcp

Event name

dhcp6ClientAddressDeclined

Default severity

notice

Message format string

DHCPv6 client running on subinterface_name was given a duplicate IPv6 address by the DHCP server server_ip

Cause

The DHCP server assigned an IPv6 address that is already in use on the same subnet

Effect

The subinterface will try to acquire a new IPv6 address

2.10.2. dhcp6ClientIpv6AddressValidLifetimeExpired

Table 168:  dhcp6ClientIpv6AddressValidLifetimeExpired properties 

Property name

Value

Application name

dhcp

Event name

dhcp6ClientIpv6AddressValidLifetimeExpired

Default severity

warning

Message format string

The IPv6 address assigned_ip obtained by the DHCPv6 client running on subinterface_name has become invalid

Cause

The DHCPv6 client was not successful in renewing or rebinding the IA_NA lease before the valid lifetime of the IPv6 address expired

Effect

The subinterface has no DHCP-assigned IPv6 address

2.10.3. dhcp6ClientRebindAttempted

Table 169:  dhcp6ClientRebindAttempted properties 

Property name

Value

Application name

dhcp

Event name

dhcp6ClientRebindAttempted

Default severity

informational

Message format string

DHCPv6 client running on subinterface_name is attempting to rebind its IA_NA lease for the IPv6 address requested_ip

Cause

The DHCPv6 client could not renew its assigned IPv6 address before the timer T2 expired

Effect

The IPv6 address may become deprecated and then invalid if the rebind is not successful

2.10.4. dhcp6ClientReconfigureMsgDropped

Table 170:  dhcp6ClientReconfigureMsgDropped properties 

Property name

Value

Application name

dhcp

Event name

dhcp6ClientReconfigureMsgDropped

Default severity

notice

Message format string

The DHCPv6 client running on subinterface_name dropped a RECONFIGURE message received from the server server_ip

Cause

The DHCPv6 client received a message that it was not supposed to receive (because it did not include a Reconfigure Accept option in its SOLICIT msg)

Effect

None

2.10.5. dhcp6ClientRenewSuccess

Table 171:  dhcp6ClientRenewSuccess properties 

Property name

Value

Application name

dhcp

Event name

dhcp6ClientRenewSuccess

Default severity

informational

Message format string

DHCPv6 client running on subinterface_name successfully renewed the IPv6 address requested_ip for a new lease duration of new_lease_time seconds from server server_ip

Cause

The DHCPv6 client received a success REPLY in response to its RENEW

Effect

The subinterface remains operational with its existing DHCP-assigned IPv6 address

2.10.6. dhcpClientAddressDeclined

Table 172:  dhcpClientAddressDeclined properties 

Property name

Value

Application name

dhcp

Event name

dhcpClientAddressDeclined

Default severity

notice

Message format string

DHCP client running on subinterface_name was given a duplicate IPv4 address by the DHCP server server_ip

Cause

The DHCP server assigned an IPv4 address that is already in use on the same subnet

Effect

The subinterface will try to acquire a new IPv4 address after a 10s delay

2.10.7. dhcpClientLeaseExpired

Table 173:  dhcpClientLeaseExpired properties 

Property name

Value

Application name

dhcp

Event name

dhcpClientLeaseExpired

Default severity

warning

Message format string

The DHCP lease for address assigned_ip obtained by the DHCP client running on subinterface_name and obtained from server server_ip has expired

Cause

The DHCP client was not successful in renewing or rebinding the lease

Effect

The subinterface has no DHCP-assigned IPv4 address

2.10.8. dhcpClientRebindAttempted

Table 174:  dhcpClientRebindAttempted properties 

Property name

Value

Application name

dhcp

Event name

dhcpClientRebindAttempted

Default severity

informational

Message format string

DHCP client running on subinterface_name is attempting to rebind its lease for the IP address requested_ip

Cause

The DHCP client could not renew its assigned IPv4 address before the timer T2 expired

Effect

The lease may expire if the rebind is not successful

2.10.9. dhcpClientRenewSuccess

Table 175:  dhcpClientRenewSuccess properties 

Property name

Value

Application name

dhcp

Event name

dhcpClientRenewSuccess

Default severity

informational

Message format string

DHCP client running on subinterface_name successfully renewed the IP address requested_ip for a new lease duration of new_lease_time seconds from server server_ip

Cause

The DHCP client received a DHCPACK response to its DHCPREQUEST

Effect

The subinterface remains operational with its existing DHCP-assigned IPv4 address

2.10.10. dhcpv4RelayAdminDisable

Table 176:  dhcpv4RelayAdminDisable properties 

Property name

Value

Application name

dhcp

Event name

dhcpv4RelayAdminDisable

Default severity

warning

Message format string

DHCPv4 Relay on sub-interface subinterface_name has changed to administrative disable state

Cause

The DHCPv4 Relay admin state has changed from enable to disable due to configuration change

Effect

The DHCPv4 Relay admin state is disable on the mentioned sub-interface

2.10.11. dhcpv4RelayAdminEnable

Table 177:  dhcpv4RelayAdminEnable properties 

Property name

Value

Application name

dhcp

Event name

dhcpv4RelayAdminEnable

Default severity

warning

Message format string

DHCPv4 Relay on sub-interface subinterface_name has changed to administrative enable state

Cause

The DHCPv4 Relay admin state has changed from disable to enable due to configuration change

Effect

The DHCPv4 Relay admin state is enable on the mentioned sub-interface

2.10.12. dhcpv4RelayAllDhcpv4ServersUnreachable

Table 178:  dhcpv4RelayAllDhcpv4ServersUnreachable properties 

Property name

Value

Application name

dhcp

Event name

dhcpv4RelayAllDhcpv4ServersUnreachable

Default severity

critical

Message format string

All DHCPv4 Servers dhcpv4_server_list configured under DHCPv4 Relay on sub-interface subinterface_name are unreachable for network instance network_instance

Cause

All The DHCPv4 Servers configured under DHCPv4 Relay are unreachable

Effect

The DHCPv4 Relay oper state is down on the mentioned sub-interface

2.10.13. dhcpv4RelayOperDown

Table 179:  dhcpv4RelayOperDown properties 

Property name

Value

Application name

dhcp

Event name

dhcpv4RelayOperDown

Default severity

critical

Message format string

DHCPv4 Relay on sub-interface subinterface_name has changed to operational down state

Cause

The DHCPv4 Relay oper state has changed from up to down

Effect

The DHCPv4 Relay oper state is down on the mentioned sub-interface

2.10.14. dhcpv4RelayOperUp

Table 180:  dhcpv4RelayOperUp properties 

Property name

Value

Application name

dhcp

Event name

dhcpv4RelayOperUp

Default severity

warning

Message format string

DHCPv4 Relay on sub-interface subinterface_name has changed to operational up state

Cause

The DHCPv4 Relay oper state has changed from down to up

Effect

The DHCPv4 Relay oper state is up on the mentioned sub-interface

2.10.15. dhcpv6RelayAdminDisable

Table 181:  dhcpv6RelayAdminDisable properties 

Property name

Value

Application name

dhcp

Event name

dhcpv6RelayAdminDisable

Default severity

warning

Message format string

DHCPv6 Relay on sub-interface subinterface_name has changed to administrative disable state

Cause

The DHCPv6 Relay admin state has changed from enable to disable due to configuration change

Effect

The DHCPv6 Relay admin state is disable on the mentioned sub-interface

2.10.16. dhcpv6RelayAdminEnable

Table 182:  dhcpv6RelayAdminEnable properties 

Property name

Value

Application name

dhcp

Event name

dhcpv6RelayAdminEnable

Default severity

warning

Message format string

DHCPv6 Relay on sub-interface subinterface_name has changed to administrative enable state

Cause

The DHCPv6 Relay admin state has changed from disable to enable due to configuration change

Effect

The DHCPv6 Relay admin state is enable on the mentioned sub-interface

2.10.17. dhcpv6RelayAllDhcpv6ServersUnreachable

Table 183:  dhcpv6RelayAllDhcpv6ServersUnreachable properties 

Property name

Value

Application name

dhcp

Event name

dhcpv6RelayAllDhcpv6ServersUnreachable

Default severity

critical

Message format string

All DHCPv6 Servers dhcpv6_server_list configured under DHCPv6 Relay on sub-interface subinterface_name are unreachable for network instance network_instance

Cause

All The DHCPv6 Servers configured under DHCPv6 Relay are unreachable

Effect

The DHCPv6 Relay oper state is down on the mentioned sub-interface

2.10.18. dhcpv6RelayOperDown

Table 184:  dhcpv6RelayOperDown properties 

Property name

Value

Application name

dhcp

Event name

dhcpv6RelayOperDown

Default severity

critical

Message format string

DHCPv6 Relay on sub-interface subinterface_name has changed to operational down state

Cause

The DHCPv6 Relay oper state has changed from up to down

Effect

The DHCPv6 Relay oper state is down on the mentioned sub-interface

2.10.19. dhcpv6RelayOperUp

Table 185:  dhcpv6RelayOperUp properties 

Property name

Value

Application name

dhcp

Event name

dhcpv6RelayOperUp

Default severity

warning

Message format string

DHCPv6 Relay on sub-interface subinterface_name has changed to operational up state

Cause

The DHCPv6 Relay oper state has changed from down to up

Effect

The DHCPv6 Relay oper state is up on the mentioned sub-interface

2.10.20. giAddressMismatch

Table 186:  giAddressMismatch properties 

Property name

Value

Application name

dhcp

Event name

giAddressMismatch

Default severity

critical

Message format string

Gi-Address for DHCPv4 Relay on sub-interface subinterface_name does not match any of the configured IPv4 addresses under sub-interface

Cause

The gi-address for DHCPv4 Relay does not match any of the configured IPv4 addresses under sub-interface

Effect

The DHCPv4 Relay oper state is down on the mentioned sub-interface

2.10.21. sourceAddressMismatch

Table 187:  sourceAddressMismatch properties 

Property name

Value

Application name

dhcp

Event name

sourceAddressMismatch

Default severity

critical

Message format string

source-address for DHCPv6 Relay on sub-interface subinterface_name does not match any of the configured IPv6 addresses under sub-interface

Cause

The source-address for DHCPv6 Relay does not match any of the configured IPv6 addresses under sub-interface

Effect

The DHCPv6 Relay oper state is down on the mentioned sub-interface

2.11. evpn

2.11.1. ethernetsegmentNetworkInstanceBgpInstance DfStatusChanged

Table 188:  ethernetsegmentNetworkInstanceBgpInstanceDfStatusChanged properties 

Property name

Value

Application name

evpn

Event name

ethernetsegmentNetworkInstanceBgpInstanceDfStatusChanged

Default severity

notice

Message format string

BGP-EVPN attachment circuit on ethernet segment ethernet-segment on network instance network-instance and bgp instance bgp-instance is now a designated-forwarding-status.

Cause

This event is generated when there is a change in the ethernet segment attachment circuit designated forwarder state.

Effect

The forwarding state of the ethernet segment attachment circuit is changed.

2.11.2. evpnAutoDiscoveryEviRouteWithdrawnDueTo UnexpectedVni

Table 189:  evpnAutoDiscoveryEviRouteWithdrawnDueToUnexpectedVni properties 

Property name

Value

Application name

evpn

Event name

evpnAutoDiscoveryEviRouteWithdrawnDueToUnexpectedVni

Default severity

warning

Message format string

BGP-EVPN Auto Discovery Evi route received with route-distinguisher route-distinguisher and ethernet segment identifier ethernet-segment-id on network instance network-instance and bgp instance bgp-instance is withdrawn because the VXLAN Network Identifier received-vni received in the route, does not match locally configured VXLAN Network Identifier local-vni on the bgp-instance

Cause

This event is generated when a received VXLAN Network Identifier does not match the one configured locally on the bgp-instance in the network instance

Effect

The designated forwarder election on this ethernet-segment-id for this EVI will be affected. The mac-address's on this ethernet-segment will not be programmed in the bridge-table

2.11.3. evpnInclMcastRouteWithdrawnDueToUnexpected Vni

Table 190:  evpnInclMcastRouteWithdrawnDueToUnexpectedVni properties 

Property name

Value

Application name

evpn

Event name

evpnInclMcastRouteWithdrawnDueToUnexpectedVni

Default severity

warning

Message format string

BGP-EVPN Inclusive Multicast route received with route-distinguisher route-distinguisher and originating IP originating-ip-address on network instance network-instance and bgp instance bgp-instance is withdrawn because the VXLAN Network Identifier received-vni received in the route, does not match locally configured VXLAN Network Identifier local-vni on the bgp-instance

Cause

This event is generated when a received VXLAN Network Identifier does not match the one configured locally on the bgp-instance in the network instance

Effect

The Virtual Tunnel End Point for the received VXLAN Network Identifier is not programmed in the multicast flood list of bridge-table

2.11.4. evpnIpPrefixRouteNotImportedDueToUnexpected Vni

Table 191:  evpnIpPrefixRouteNotImportedDueToUnexpectedVni properties 

Property name

Value

Application name

evpn

Event name

evpnIpPrefixRouteNotImportedDueToUnexpectedVni

Default severity

warning

Message format string

BGP-EVPN IP-PREFIX ip-prefix LENGTH prefix-length received with route-distinguisher route-distinguisher on network instance network-instance and bgp instance bgp-instance is not imported because the VXLAN Network Identifier received-vni received in the route, does not match the locally configured VXLAN Network Identifier on the bgp-instance

Cause

This event is generated when a received VXLAN Network Identifier does not match the one configured locally on the bgp-instance in the network instance

Effect

The IP-Prefix is not programmed in the route-table

2.11.5. evpnIpPrefixRouteWithdrawnDueToNoGwMac

Table 192:  evpnIpPrefixRouteWithdrawnDueToNoGwMac properties 

Property name

Value

Application name

evpn

Event name

evpnIpPrefixRouteWithdrawnDueToNoGwMac

Default severity

warning

Message format string

BGP-EVPN IP-PREFIX ip-prefix LENGTH prefix-length received with route-distinguisher route-distinguisher on network instance network-instance and bgp instance bgp-instance is withdrawn because the route is received without a Gateway MAC Address and that is not allowed in an EVPN Interface-less bgp instance for VXLAN tunnels

Cause

This event is generated when a received IP Prefix route does not contain the required GW Mac and therefore it is not allowed in the local EVPN Interface-less bgp instance of the network-instance

Effect

The ip-prefix is not programmed in the route table of the network instance

2.11.6. evpnIpPrefixRouteWithdrawnDueToUnexpected GwIp

Table 193:  evpnIpPrefixRouteWithdrawnDueToUnexpectedGwIp properties 

Property name

Value

Application name

evpn

Event name

evpnIpPrefixRouteWithdrawnDueToUnexpectedGwIp

Default severity

warning

Message format string

BGP-EVPN IP-PREFIX ip-prefix LENGTH prefix-length received with route-distinguisher route-distinguisher on network instance network-instance and bgp instance bgp-instance is withdrawn because the non-zero Gateway IP Address gw-ip-address received in the route is not allowed in an EVPN Interface-less bgp instance of the network-instance

Cause

This event is generated when a received Gateway IP Address in the IP Prefix routes is non-zero and therefore not allowed in the local EVPN Interface-less bgp instance of the network-instance

Effect

The ip-prefix is not programmed in the route table of the network instance

2.11.7. evpnMacRouteWithdrawnDueToUnexpectedVni

Table 194:  evpnMacRouteWithdrawnDueToUnexpectedVni properties 

Property name

Value

Application name

evpn

Event name

evpnMacRouteWithdrawnDueToUnexpectedVni

Default severity

warning

Message format string

BGP-EVPN MAC mac-address IP ip-address received with route-distinguisher route-distinguisher on network instance network-instance and bgp instance bgp-instance is withdrawn because the VXLAN Network Identifier received-vni received in the route, does not match locally configured VXLAN Network Identifier local-vni on the bgp-instance

Cause

This event is generated when a received VXLAN Network Identifier does not match the one configured locally on the bgp-instance in the network instance

Effect

The mac-address is not programmed in the bridge-table AND/OR the mac-address/ip-address pair is not programmed in the ARP or Neighbor discovery table

2.12. gnmi

2.12.1. globalConfigUpdate

Table 195:  globalConfigUpdate properties 

Property name

Value

Application name

gnmi

Event name

globalConfigUpdate

Default severity

informational

Message format string

gNMI server global configuration updated.

Cause

A global configuration change has been made, resulting in gNMI configuration being regenerated.

Effect

May result in gNMI server(s) start or stop depending on the configuration change.

2.12.2. gnmiServerStart

Table 196:  gnmiServerStart properties 

Property name

Value

Application name

gnmi

Event name

gnmiServerStart

Default severity

informational

Message format string

gNMI server started for network instance network_instance source address source_address port number gnmi_socket.

Cause

gNMI server has started for the mentioned network instance, source address and port number.

Effect

gNMI server is ready to receive and process requests for the mentioned network instance, source address and port number.

2.12.3. gnmiServerStop

Table 197:  gnmiServerStop properties 

Property name

Value

Application name

gnmi

Event name

gnmiServerStop

Default severity

informational

Message format string

gNMI server stopped for network network_instance source address source_address port number gnmi_socket.

Cause

gNMI server has stopped for the mentioned network instance, source address and port number.

Effect

gNMI server is not ready to receive and process requests for the mentioned network instance, source address and port number.

2.12.4. networkInstanceConfigUpdate

Table 198:  networkInstanceConfigUpdate properties 

Property name

Value

Application name

gnmi

Event name

networkInstanceConfigUpdate

Default severity

informational

Message format string

gNMI server network instance network_instance configuration updated.

Cause

A configuration change has been made in the mentioned network instance, resulting in gNMI server configuration being regenerated.

Effect

May result in gNMI server start or stop depending on the configuration change.

2.12.5. subscriptionEnd

Table 199:  subscriptionEnd properties 

Property name

Value

Application name

gnmi

Event name

subscriptionEnd

Default severity

informational

Message format string

Subscription for path 'path' requested by peer_address:socket has finished.

Cause

A subscription has finished based on the request from mentioned peer.

Effect

none.

2.12.6. subscriptionRequestReceived

Table 200:  subscriptionRequestReceived properties 

Property name

Value

Application name

gnmi

Event name

subscriptionRequestReceived

Default severity

informational

Message format string

Subscription request from peer peer_address:socket is received.

Cause

A subscription request is received from the mentioned peer.

Effect

gNMI server will process the request.

2.12.7. subscriptionStart

Table 201:  subscriptionStart properties 

Property name

Value

Application name

gnmi

Event name

subscriptionStart

Default severity

informational

Message format string

Subscription for path 'path' requested by peer_address:socket has started.

Cause

A subscription has started based on the request from mentioned peer.

Effect

none.

2.12.8. unixSocketGnmiOperDown

Table 202:  unixSocketGnmiOperDown properties 

Property name

Value

Application name

gnmi

Event name

unixSocketGnmiOperDown

Default severity

critical

Message format string

Unix Domain Socket gNMI server is no longer operational.

Cause

The Unix domain socket gNMI server has transitioned from any other operational state to the down state.

Effect

Unix Domain Socket gNMI server is now down.

2.12.9. unixSocketGnmiOperUp

Table 203:  unixSocketGnmiOperUp properties 

Property name

Value

Application name

gnmi

Event name

unixSocketGnmiOperUp

Default severity

warning

Message format string

Unix domain socket gNMI server is operational.

Cause

The Unix domain socket gNMI server has transitioned from any other operational state to the up state.

Effect

Unix domain socket gNMI server is now up.

2.13. isis

2.13.1. isisAdjacencyBfdSessionSetupFailed

Table 204:  isisAdjacencyBfdSessionSetupFailed properties 

Property name

Value

Application name

isis

Event name

isisAdjacencyBfdSessionSetupFailed

Default severity

warning

Message format string

In network-instance network_instance, BFD session setup failed for the level IS-IS adjacency with system sys_id, using interface subinterface. Failure reason: bfd_failure_reason.

Cause

This event is generated when BFD session setup fails with an adjacent neighbor.

Effect

Fast failure detection may not be possible.

2.13.2. isisAdjacencyChange

Table 205:  isisAdjacencyChange properties 

Property name

Value

Application name

isis

Event name

isisAdjacencyChange

Default severity

warning

Message format string

In network-instance network_instance, the level IS-IS adjacency with system sys_id, using interface subinterface, moved to state adj_state.

Cause

This event is generated when an IS-IS adjacency enters or leaves the up state.

Effect

IS-IS traffic can only be forwarded along adjacencies that are up.

2.13.3. isisAdjacencyRestartStatusChange

Table 206:  isisAdjacencyRestartStatusChange properties 

Property name

Value

Application name

isis

Event name

isisAdjacencyRestartStatusChange

Default severity

warning

Message format string

In network-instance network_instance, the graceful restart status for the level IS-IS adjacency on interface subinterface moved to new state restart_status.

Cause

This event is generated when the graceful restart status of a neighbor changes.

Effect

None

2.13.4. isisAreaMismatch

Table 207:  isisAreaMismatch properties 

Property name

Value

Application name

isis

Event name

isisAreaMismatch

Default severity

warning

Message format string

In network-instance network_instance, a level1 PDU was received on interface subinterface with no Area Addresses matching the areas to which this IS router belongs. The PDU starts with: pdu_fragment

Cause

This event is generated to alert of a possible area-id misconfiguration inside a L1 area.

Effect

L1 adjacency cannot form

2.13.5. isisAuthDataFail

Table 208:  isisAuthDataFail properties 

Property name

Value

Application name

isis

Event name

isisAuthDataFail

Default severity

warning

Message format string

In network-instance network_instance, a level PDU was received on interface subinterface with unexpected or incorrect data in the Authentication TLV. The PDU starts with: pdu_fragment

Cause

This event could be caused by incorrect keychain configuration in this router or its neighbor.

Effect

PDUs are dropped, with the effect depending on the PDU type

2.13.6. isisAuthTypeMismatch

Table 209:  isisAuthTypeMismatch properties 

Property name

Value

Application name

isis

Event name

isisAuthTypeMismatch

Default severity

warning

Message format string

In network-instance network_instance, a level PDU was received on interface subinterface with an unrecognized or unsupported authentication type in TLV 10. The PDU starts with: pdu_fragment

Cause

This event could be caused by incorrect keychain configuration in this router or its neighbor.

Effect

PDUs are dropped, with the effect depending on the PDU type

2.13.7. isisCircuitIdsExhausted

Table 210:  isisCircuitIdsExhausted properties 

Property name

Value

Application name

isis

Event name

isisCircuitIdsExhausted

Default severity

warning

Message format string

In network-instance network_instance, the IS-IS interface subinterface is operationally down because the limit of 255 circuit IDs available to LAN interfaces was reached.

Cause

This event is caused by having too many LAN interfaces.

Effect

LAN adjacencies are not formed

2.13.8. isisCircuitMtuTooLow

Table 211:  isisCircuitMtuTooLow properties 

Property name

Value

Application name

isis

Event name

isisCircuitMtuTooLow

Default severity

warning

Message format string

In network-instance network_instance, a level LSP PDU or SNP PDU could not be transmitted on interface subinterface because the IP MTU is only operational_subif_mtu and an MTU of at least required_mtu is required.

Cause

The port MTU is too small and/or the lsp-mtu-size is too large.

Effect

PDUs are dropped

2.13.9. isisCorruptedLspDetected

Table 212:  isisCorruptedLspDetected properties 

Property name

Value

Application name

isis

Event name

isisCorruptedLspDetected

Default severity

warning

Message format string

In network-instance network_instance, the LSP PDU with ID lsp_id in the level database has become corrupted.

Cause

Memory corruption or other.

Effect

LSP is removed

2.13.10. isisLspFragmentTooLarge

Table 213:  isisLspFragmentTooLarge properties 

Property name

Value

Application name

isis

Event name

isisLspFragmentTooLarge

Default severity

warning

Message format string

In network-instance network_instance, the level LSP PDU fragment lsp_id received on interface subinterface could not be accepted because the configured LSP MTU size is too small. An LSP MTU size of at least required_lsp_mtu bytes is required.

Cause

Misconfiguration of LSP MTU size

Effect

LSP PDU is not accepted

2.13.11. isisLspPurge

Table 214:  isisLspPurge properties 

Property name

Value

Application name

isis

Event name

isisLspPurge

Default severity

warning

Message format string

In network-instance network_instance, the LSP PDU with ID lsp_id in the level database has been purged by purge_originator.

Cause

LSP lifetime expired or other reason

Effect

The PDU is removed

2.13.12. isisLspSequenceNumberSkip

Table 215:  isisLspSequenceNumberSkip properties 

Property name

Value

Application name

isis

Event name

isisLspSequenceNumberSkip

Default severity

warning

Message format string

In network-instance network_instance, the LSP with id lsp_id in the level database was re-originated with a sequence number that incremented by more than one.

Cause

There may be another IS router configured with the same system ID.

Effect

None

2.13.13. isisMaxAreaAddressesMismatch

Table 216:  isisMaxAreaAddressesMismatch properties 

Property name

Value

Application name

isis

Event name

isisMaxAreaAddressesMismatch

Default severity

warning

Message format string

In network-instance network_instance, a level PDU was received on interface subinterface with an unexpected Max Area Addresses value in the IS-IS PDU header. The PDU starts with: pdu_fragment

Cause

Misconfiguration of max area addresses in the neighbor

Effect

The PDU is dropped

2.13.14. isisMaxLspSequenceNumberExceeded

Table 217:  isisMaxLspSequenceNumberExceeded properties 

Property name

Value

Application name

isis

Event name

isisMaxLspSequenceNumberExceeded

Default severity

warning

Message format string

In network-instance network_instance, the LSP with id lsp_id in the level database was purged because the sequence number was already at its maximum value and could not be incremented.

Cause

A possible cause could be that the same system-id is configured on multiple systems; when 2 systems have the same system-id they both keep incrementing the LSP sequence number, causing the sequence counter to rollover.

Effect

The PDU is purged and reachability may be temporarily lost

2.13.15. isisOverloadEntry

Table 218:  isisOverloadEntry properties 

Property name

Value

Application name

isis

Event name

isisOverloadEntry

Default severity

warning

Message format string

In the IS-IS instance of network-instance network_instance, the level database has entered the overload state.

Cause

Overload bit configuration

Effect

No transit traffic is routed through the overloaded router.

2.13.16. isisOverloadExit

Table 219:  isisOverloadExit properties 

Property name

Value

Application name

isis

Event name

isisOverloadExit

Default severity

warning

Message format string

In the IS-IS instance of network-instance network_instance, the level database has exited from the overload state.

Cause

Overload bit configuration

Effect

Transit traffic can again be routed through the router.

2.13.17. isisOwnLspPurge

Table 220:  isisOwnLspPurge properties 

Property name

Value

Application name

isis

Event name

isisOwnLspPurge

Default severity

warning

Message format string

In network-instance network_instance, a level LSP PDU was received with the system ID of this IS router and age equal to zero. The purge originator was purge_originator.

Cause

LSP lifetime expired or other reason

Effect

The PDU is removed

2.13.18. isisSystemIdLengthMismatch

Table 221:  isisSystemIdLengthMismatch properties 

Property name

Value

Application name

isis

Event name

isisSystemIdLengthMismatch

Default severity

warning

Message format string

In network-instance network_instance, a level PDU was received on interface subinterface with an unexpected System ID length in the IS-IS PDU header. The PDU starts with: pdu_fragment

Cause

Misconfiguration of system ID length in the neighbor

Effect

The PDU is dropped

2.13.19. isisVersionMismatch

Table 222:  isisVersionMismatch properties 

Property name

Value

Application name

isis

Event name

isisVersionMismatch

Default severity

warning

Message format string

In network-instance network_instance, a level PDU was received on interface subinterface with an IS-IS protocol version not matching the expected value. The PDU starts with: pdu_fragment

Cause

Unsupported IS-IS version

Effect

PDUs cannot be exchanged

2.14. json

2.14.1. authenticationError

Table 223:  authenticationError properties 

Property name

Value

Application name

json

Event name

authenticationError

Default severity

informational

Message format string

No username/password received, authentication needed

Cause

A user has failed to authenticate.

Effect

That user can't establish a configuration session.

2.14.2. globalConfigUpdate

Table 224:  globalConfigUpdate properties 

Property name

Value

Application name

json

Event name

globalConfigUpdate

Default severity

informational

Message format string

JSON RPC server global configuration updated.

Cause

A global configuration change has been made, resulting in json rpc configuration being regenerated.

Effect

May result in json rpc process(es) start or stop depending on the configuration change.

2.14.3. httpJsonRpcOperDown

Table 225:  httpJsonRpcOperDown properties 

Property name

Value

Application name

json

Event name

httpJsonRpcOperDown

Default severity

critical

Message format string

HTTP JSON RPC server for network instance network_instance is no longer operational.

Cause

The httpJsonRpcOperDown event is generated when HTTP JSON RPC server on the mentioned network instance has transitioned from any other operational state to the down state.

Effect

HTTP JSON RPC server on the mentioned network instance is now down.

2.14.4. httpJsonRpcOperUp

Table 226:  httpJsonRpcOperUp properties 

Property name

Value

Application name

json

Event name

httpJsonRpcOperUp

Default severity

warning

Message format string

HTTP JSON RPC server for network instance network_instance is operational.

Cause

The httpJsonRpcOperUp event is generated when HTTP JSON RPC server on the mentioned network instance has transitioned from any other operational state to the up state.

Effect

HTTP JSON RPC server on the mentioned network instance is now up.

2.14.5. httpsJsonRpcOperDown

Table 227:  httpsJsonRpcOperDown properties 

Property name

Value

Application name

json

Event name

httpsJsonRpcOperDown

Default severity

critical

Message format string

HTTPS JSON RPC server for network instance network_instance is no longer operational.

Cause

The httpsJsonRpcOperDown event is generated when HTTPs JSON RPC server on the mentioned network instance has transitioned from any other operational state to the down state.

Effect

HTTPS JSON RPC server on the mentioned network instance is now down.

2.14.6. httpsJsonRpcOperUp

Table 228:  httpsJsonRpcOperUp properties 

Property name

Value

Application name

json

Event name

httpsJsonRpcOperUp

Default severity

warning

Message format string

HTTPS JSON RPC server for network instance network_instance is operational.

Cause

The httpsJsonRpcOperUp event is generated when HTTPs JSON RPC server on the mentioned network instance has transitioned from any other operational state to the up state.

Effect

HTTPS JSON RPC server on the mentioned network instance is now up.

2.14.7. jsonRpcRequestReceived

Table 229:  jsonRpcRequestReceived properties 

Property name

Value

Application name

json

Event name

jsonRpcRequestReceived

Default severity

informational

Message format string

Request received for session id session_id username username.

Cause

A JSON RPC Request is received.

Effect

JSON RPC server processes That Requset.

2.14.8. jsonRpcResponseSent

Table 230:  jsonRpcResponseSent properties 

Property name

Value

Application name

json

Event name

jsonRpcResponseSent

Default severity

informational

Message format string

Response sent for session id session_id username username.

Cause

A JSON RPC Response is sent.

Effect

none.

2.14.9. networkInstanceConfigUpdate

Table 231:  networkInstanceConfigUpdate properties 

Property name

Value

Application name

json

Event name

networkInstanceConfigUpdate

Default severity

informational

Message format string

JSON RPC server network instance network_instance configuration updated.

Cause

A configuration change has been made in the mentioned network instance, resulting in json rpc configuration being regenerated.

Effect

May result in json rpc process(es) start or stop depending on the configuration change.

2.14.10. unixSocketJsonRpcOperDown

Table 232:  unixSocketJsonRpcOperDown properties 

Property name

Value

Application name

json

Event name

unixSocketJsonRpcOperDown

Default severity

critical

Message format string

Unix Domain Socket JSON RPC server is no longer operational.

Cause

The Unix Domain Socket JSON RPC server has transitioned from any other operational state to the down state.

Effect

Unix Domain Socket JSON RPC server is now down.

2.14.11. unixSocketJsonRpcOperUp

Table 233:  unixSocketJsonRpcOperUp properties 

Property name

Value

Application name

json

Event name

unixSocketJsonRpcOperUp

Default severity

warning

Message format string

Unix Domain Socket JSON RPC server is operational.

Cause

The Unix Domain Socket JSON RPC server has transitioned from any other operational state to the up state.

Effect

Unix Domain Socket JSON RPC server is now up.

2.14.12. userAuthenticated

Table 234:  userAuthenticated properties 

Property name

Value

Application name

json

Event name

userAuthenticated

Default severity

informational

Message format string

User username authenticated.

Cause

A user has been successfully authenticated.

Effect

That user is ready to start a configuration session.

2.14.13. userAuthenticationErrorWrongPassword

Table 235:  userAuthenticationErrorWrongPassword properties 

Property name

Value

Application name

json

Event name

userAuthenticationErrorWrongPassword

Default severity

informational

Message format string

User username authentication failure, invalid username or password.

Cause

A user has failed to authenticate.

Effect

That user can't establish a configuration session.

2.15. lag

2.15.1. lagDown

Table 236:  lagDown properties 

Property name

Value

Application name

lag

Event name

lagDown

Default severity

warning

Message format string

LAG Interface interface_name: The operational state has transitioned to Down

Cause

This warning is generated when a LAG transitions to the down state.

Effect

The LAG is now down and any associated subinterfaces will also be brought down.

2.15.2. lagDownMinLinks

Table 237:  lagDownMinLinks properties 

Property name

Value

Application name

lag

Event name

lagDownMinLinks

Default severity

warning

Message format string

LAG Interface interface_name: The active number of member links has fallen below the min-links threshold

Cause

This warning is generated when a LAG transitions to the down state because the number of active links has dropped below the min-link threshold

Effect

The LAG is now down and any associated subinterfaces will also be brought down.

2.15.3. lagMemberLinkAdded

Table 238:  lagMemberLinkAdded properties 

Property name

Value

Application name

lag

Event name

lagMemberLinkAdded

Default severity

notice

Message format string

LAG Interface interface_name: The member-link member-interface has been added

Cause

This notification is generated when a new member-link is added to a LAG.

Effect

A new member link is now available to the LAG bundle.

2.15.4. lagMemberLinkRemoved

Table 239:  lagMemberLinkRemoved properties 

Property name

Value

Application name

lag

Event name

lagMemberLinkRemoved

Default severity

notice

Message format string

LAG Interface interface_name: The member-link member-interface has been removed

Cause

This notification is generated when a new member-link is removed from a LAG.

Effect

The specified interfaces is no longer a member of the LAG bundle.

2.15.5. lagMemberOperDown

Table 240:  lagMemberOperDown properties 

Property name

Value

Application name

lag

Event name

lagMemberOperDown

Default severity

warning

Message format string

LAG Interface interface_name: The member-link member-interface operational state has transitioned to Down

Cause

This notification is generated when a member-link transitions to the down state.

Effect

The member link is now down and will not forward traffic.

2.15.6. lagMemberOperUp

Table 241:  lagMemberOperUp properties 

Property name

Value

Application name

lag

Event name

lagMemberOperUp

Default severity

warning

Message format string

LAG Interface interface_name: The member-link member-interface operational state has transitioned to Up

Cause

This notification is generated when a member-link transitions to the up state.

Effect

The member link is now operational.

2.15.7. lagUp

Table 242:  lagUp properties 

Property name

Value

Application name

lag

Event name

lagUp

Default severity

notice

Message format string

LAG Interface interface_name: The operational state has transitioned to Up

Cause

This notification is generated when a LAG transitions to the up state.

Effect

The LAG is now operational.

2.16. linux

2.16.1. cpuUsageCritical

Table 243:  cpuUsageCritical properties 

Property name

Value

Application name

linux

Event name

cpuUsageCritical

Default severity

critical

Message format string

CPU utilization on component_type module slot is above 90% on average for the last minute, current usage cpu_usage_percentage%

Cause

Applications or other system tasks have consumed more than 90% of available CPU resources on average over the last minute.

Effect

Processes may be scheduled at a slower rate than required, resulting in potential application failures or slow downs.

2.16.2. cpuUsageHigh

Table 244:  cpuUsageHigh properties 

Property name

Value

Application name

linux

Event name

cpuUsageHigh

Default severity

warning

Message format string

CPU utilization on component_type module slot is above 80% on average for the last minute, current usage cpu_usage_percentage%

Cause

Applications or other system tasks have consumed more than 80% of available CPU resources on average over the last minute.

Effect

No immediate effect, if utilization continues to increase, processes may be scheduled at a slower rate than required, resulting in potential application failures or slow downs.

2.16.3. cpuUsageNormal

Table 245:  cpuUsageNormal properties 

Property name

Value

Application name

linux

Event name

cpuUsageNormal

Default severity

notice

Message format string

CPU utilization on component_type module slot is below 70% on average for the last minute, current usage cpu_usage_percentage%

Cause

CPU consumption on the specified slot has returned to normal levels - below 70%, after triggering a cpuUsageHigh/cpuUsageCritical event.

Effect

None.

2.16.4. dateAndTimeChanged

Table 246:  dateAndTimeChanged properties 

Property name

Value

Application name

linux

Event name

dateAndTimeChanged

Default severity

notice

Message format string

System date and time changed to date_and_time

Cause

The system time has been changed either manually, or via NTP, to the specified time.

Effect

Local time on the system has changed.

2.16.5. domainChanged

Table 247:  domainChanged properties 

Property name

Value

Application name

linux

Event name

domainChanged

Default severity

informational

Message format string

System domain name changed to domain_name

Cause

System configuration change to the domain name has been made.

Effect

The system uses the new domain name.

2.16.6. hostnameChanged

Table 248:  hostnameChanged properties 

Property name

Value

Application name

linux

Event name

hostnameChanged

Default severity

informational

Message format string

System host name changed to host_name

Cause

System configuration change to the host name has been made.

Effect

The system uses the new host name.

2.16.7. memoryUsageCritical

Table 249:  memoryUsageCritical properties 

Property name

Value

Application name

linux

Event name

memoryUsageCritical

Default severity

critical

Message format string

Memory utilization on component_type module slot is above 90%, current usage memory_usage_percentage%

Cause

Applications or other in-memory items have consumed more than 90% of the memory on the specified module.

Effect

No immediate effect, if utilization continues to increase, new memory allocations may fail, resulting in potential application failures.

2.16.8. memoryUsageFull

Table 250:  memoryUsageFull properties 

Property name

Value

Application name

linux

Event name

memoryUsageFull

Default severity

emergency

Message format string

Memory utilization on component_type module slot is full

Cause

Applications or other in-memory items have consumed 100% of the memory on the specified module.

Effect

Further memory allocations will fail, likely leading to application failures and eventual module restart.

2.16.9. memoryUsageHigh

Table 251:  memoryUsageHigh properties 

Property name

Value

Application name

linux

Event name

memoryUsageHigh

Default severity

warning

Message format string

Memory utilization on component_type module slot is above 70%, current usage memory_usage_percentage%

Cause

Applications or other in-memory items have consumed more than 70% of the memory on the specified slot.

Effect

No immediate effect, if utilization continues to increase, new memory allocations may fail, resulting in potential application failures.

2.16.10. memoryUsageNormal

Table 252:  memoryUsageNormal properties 

Property name

Value

Application name

linux

Event name

memoryUsageNormal

Default severity

notice

Message format string

Memory utilization on component_type module slot is below 60%, current usage memory_usage_percentage%

Cause

Memory consumption on the specified slot has returned to normal levels - below 60%

Effect

None.

2.16.11. partitionStateChange

Table 253:  partitionStateChange properties 

Property name

Value

Application name

linux

Event name

partitionStateChange

Default severity

alert

Message format string

Partition partition has changed state to current_state

Cause

The specified partition has transitioned to a new state.

Effect

Depending on the state, the partition may now be unusable, read-only, or read-write.

2.16.12. partitionUsageCritical

Table 254:  partitionUsageCritical properties 

Property name

Value

Application name

linux

Event name

partitionUsageCritical

Default severity

critical

Message format string

Partition partition_label usage on component_type module slot is higher than 90%, current usage partition_usage_percentage%

Cause

The specified partition is almost full, and action should be taken to remove unneeded files.

Effect

None.

2.16.13. partitionUsageFull

Table 255:  partitionUsageFull properties 

Property name

Value

Application name

linux

Event name

partitionUsageFull

Default severity

alert

Message format string

Partition partition_label on component_type module slot is full

Cause

The specified partition is full.

Effect

Write actions to this partition will fail.

2.16.14. partitionUsageNormal

Table 256:  partitionUsageNormal properties 

Property name

Value

Application name

linux

Event name

partitionUsageNormal

Default severity

notice

Message format string

Partition partition_label on component_type module slot is below 70%, current usage partition_usage_percentage%

Cause

Utilization of the specified partition is below 70%, after previously being higher than 80%.

Effect

None.

2.16.15. partitionUsageWarning

Table 257:  partitionUsageWarning properties 

Property name

Value

Application name

linux

Event name

partitionUsageWarning

Default severity

warning

Message format string

Partition partition_label usage on component_type module slot is higher than 80%, current usage partition_usage_percentage%

Cause

The specified partition is almost full, and action should be taken to remove unneeded files.

Effect

None.

2.16.16. serviceConfigChanged

Table 258:  serviceConfigChanged properties 

Property name

Value

Application name

linux

Event name

serviceConfigChanged

Default severity

notice

Message format string

Service service_name configuration changed, service reloaded

Cause

The specified service configuration has been changed, and linux_mgr has reloaded the service.

Effect

New configuration for the service is now in effect.

2.16.17. serviceDownInNetworkInstance

Table 259:  serviceDownInNetworkInstance properties 

Property name

Value

Application name

linux

Event name

serviceDownInNetworkInstance

Default severity

warning

Message format string

Service service_name is no longer operational in network instance net_inst

Cause

The specified service has been disabled in the specified network instance.

Effect

Functionality provided by the service is no longer available in the specified network instance.

2.16.18. serviceUpInNetworkInstance

Table 260:  serviceUpInNetworkInstance properties 

Property name

Value

Application name

linux

Event name

serviceUpInNetworkInstance

Default severity

notice

Message format string

Service service_name is now operational in network instance net_inst

Cause

The specified service has been started in the specified network instance.

Effect

Functionality provided by the service is now available in the specified network instance.

2.16.19. tlsProfileExpired

Table 261:  tlsProfileExpired properties 

Property name

Value

Application name

linux

Event name

tlsProfileExpired

Default severity

warning

Message format string

Certificate in TLS profile tls_profile has expired

Cause

The certificate used in the specified TLS profile has an expiration date in the past.

Effect

Authentication using the specified TLS profile may fail.

2.16.20. tlsProfileExpiresSoon

Table 262:  tlsProfileExpiresSoon properties 

Property name

Value

Application name

linux

Event name

tlsProfileExpiresSoon

Default severity

warning

Message format string

Certificate in TLS profile tls_profile expires at expires_at_date_time

Cause

The certificate used in the specified TLS profile will expire in the next 30 days.

Effect

Authentication using the specified TLS profile may fail once the certificate expires.

2.17. lldp

2.17.1. remotePeerAdded

Table 263:  remotePeerAdded properties 

Property name

Value

Application name

lldp

Event name

remotePeerAdded

Default severity

informational

Message format string

LLDP remote peer added on interface interface_name: System remote_system_name with chassis ID remote_chassis_id, port remote_port_id with MAC remote_port_mac

Cause

A new LLDP PDU has been received on the interface, resulting in the creation of an LLDP peer.

Effect

A new peer has been added to LLDP.

2.17.2. remotePeerRemoved

Table 264:  remotePeerRemoved properties 

Property name

Value

Application name

lldp

Event name

remotePeerRemoved

Default severity

informational

Message format string

LLDP remote peer removed on interface interface_name: System remote_system_name with chassis ID remote_chassis_id, port remote_port_id with MAC remote_port_mac

Cause

The TTL for the remote peer has expired without a new LLDP PDU being received.

Effect

The peer has been removed from LLDP.

2.17.3. remotePeerUpdated

Table 265:  remotePeerUpdated properties 

Property name

Value

Application name

lldp

Event name

remotePeerUpdated

Default severity

informational

Message format string

LLDP remote peer updated on interface interface_name: System remote_system_name with chassis ID remote_chassis_id, port remote_port_id with MAC remote_port_mac

Cause

The LLDP peer has sent new information in a LLDP PDU, without the TTL for the peer expiring.

Effect

The peer has been updated in LLDP.

2.18. log

2.18.1. bufferRollover

Table 266:  bufferRollover properties 

Property name

Value

Application name

log

Event name

bufferRollover

Default severity

informational

Message format string

Buffer buffer_name has been rolled over

Cause

The buffer has reached its configured max size, and log manager has rolled it over.

Effect

A new buffer has been opened for writing, and the old buffer has been archived. This may result in older buffers being removed from the system.

2.18.2. configUpdate

Table 267:  configUpdate properties 

Property name

Value

Application name

log

Event name

configUpdate

Default severity

informational

Message format string

Logging configuration updated

Cause

A configuration change has been made, resulting in rsyslogd configuration being regenerated.

Effect

Rsyslogd configuration has been modified, and the process has been restarted.

2.18.3. fileRollover

Table 268:  fileRollover properties 

Property name

Value

Application name

log

Event name

fileRollover

Default severity

informational

Message format string

File file_path/file_name has been rolled over

Cause

The file has reached its configured max size, and log manager has rolled it over.

Effect

A new log file has been opened for writing, and the old log file has been archived. This may result in older logs being removed from the system.

2.18.4. networkNamespaceChanged

Table 269:  networkNamespaceChanged properties 

Property name

Value

Application name

log

Event name

networkNamespaceChanged

Default severity

informational

Message format string

Logging network namespace has changed from old_net_namespace to new_net_namespace

Cause

Configuration has been modified, resulting in the rsyslogd using the new network namespace to reach remote syslog servers.

Effect

Rsyslogd will use the new network namespace for reachability to remote syslog servers.

2.18.5. subsystemFacilityChanged

Table 270:  subsystemFacilityChanged properties 

Property name

Value

Application name

log

Event name

subsystemFacilityChanged

Default severity

informational

Message format string

Logging output facility has changed from old_facility to new_facility

Cause

Configuration has been modified, resulting in the output facility of our subsystems changing.

Effect

Subsystems will now output logs to the newly configured facility.

2.19. mgmt

2.19.1. checkpointGenerated

Table 271:  checkpointGenerated properties 

Property name

Value

Application name

mgmt

Event name

checkpointGenerated

Default severity

informational

Message format string

Generated checkpoint checkpoint_name with comment checkpoint_comment on the following path checkpoint_file_path.

Cause

A configuration checkpoint generated on the mentioned path.

Effect

The mentioned checkpoint is stored to the filesystem.

2.19.2. checkpointRevertRequestReceived

Table 272:  checkpointRevertRequestReceived properties 

Property name

Value

Application name

mgmt

Event name

checkpointRevertRequestReceived

Default severity

warning

Message format string

Configuration is going to be reverted to checkpoint checkpoint_id name checkpoint_name comment checkpoint_comment.

Cause

Configuration revert request was received.

Effect

Configuration is going to be reverted to the specified checkpoint and applied to running datastore.

2.19.3. commitFailed

Table 273:  commitFailed properties 

Property name

Value

Application name

mgmt

Event name

commitFailed

Default severity

warning

Message format string

Error while committing configuration changes for user username session session_id (message).

Cause

Unsuccessful commit due to error(s)

Effect

Configuration changes are not applied to running datastore

2.19.4. commitSucceeded

Table 274:  commitSucceeded properties 

Property name

Value

Application name

mgmt

Event name

commitSucceeded

Default severity

informational

Message format string

All changes have been committed successfully by user username session session_id.

Cause

A successful commit

Effect

Configuration changes applied to running datastore

2.19.5. exclusiveConfigSessionBlockedByOtherSession Error

Table 275:  exclusiveConfigSessionBlockedByOtherSessionError properties 

Property name

Value

Application name

mgmt

Event name

exclusiveConfigSessionBlockedByOtherSessionError

Default severity

informational

Message format string

Cannot start an exclusive configuration session for candidate name candidate_name, there is other configuration session in progress - session id session_id username username candidate name candidate_name.

Cause

Candidate datastore is locked due to other active session in progress

Effect

Exclusive configuration session Error

2.19.6. exclusiveConfigSessionError

Table 276:  exclusiveConfigSessionError properties 

Property name

Value

Application name

mgmt

Event name

exclusiveConfigSessionError

Default severity

informational

Message format string

Cannot start an exclusive configuration session, there is already another exclusive configuration session in progress - session id session_id username username candidate name candidate_name.

Cause

Candidate datastore is locked due to other active session in progress

Effect

Exclusive configuration session Error

2.19.7. privateConfigSessionError

Table 277:  privateConfigSessionError properties 

Property name

Value

Application name

mgmt

Event name

privateConfigSessionError

Default severity

informational

Message format string

Cannot start a configuration session for candidate name candidate_name by user username, the candidate is owned by user candidate_username.

Cause

Candidate datastore is owned by different user

Effect

Private configuration session Error

2.19.8. privateSharedMismatch

Table 278:  privateSharedMismatch properties 

Property name

Value

Application name

mgmt

Event name

privateSharedMismatch

Default severity

informational

Message format string

Cannot start a configuration session for candidate name candidate_name by user username, cannot use private candidate with shared session or vice versa.

Cause

Candidate was created as private and the requested configuration session is shared or vice versa

Effect

Private shared configuration mismatch Error

2.19.9. sharedConfigSessionBlockedByOtherSession Error

Table 279:  sharedConfigSessionBlockedByOtherSessionError properties 

Property name

Value

Application name

mgmt

Event name

sharedConfigSessionBlockedByOtherSessionError

Default severity

informational

Message format string

Cannot start a shared configuration session for candidate name candidate_name, there is other configuration session in progress - session id session_id username username candidate name candidate_name.

Cause

Candidate datastore is locked due to other active session in progress

Effect

Shared configuration session Error

2.20. netinst

2.20.1. networkInstanceInterfaceDown

Table 280:  networkInstanceInterfaceDown properties 

Property name

Value

Application name

netinst

Event name

networkInstanceInterfaceDown

Default severity

warning

Message format string

The interface networkinstance_interface_name in network-instance networkinstance_name is now down for reason: oper_down_reason

Cause

This event is generated when the network instance interface has transitioned from the up state to the down state

Effect

The network instance interface is now down

2.20.2. networkInstanceInterfaceUp

Table 281:  networkInstanceInterfaceUp properties 

Property name

Value

Application name

netinst

Event name

networkInstanceInterfaceUp

Default severity

notice

Message format string

The interface networkinstance_interface_name in network-instance networkinstance_name is now up

Cause

This event is generated when the network instance interface has transitioned from the down state to the up state.

Effect

The network instance interface is now up

2.20.3. networkInstanceStateDown

Table 282:  networkInstanceStateDown properties 

Property name

Value

Application name

netinst

Event name

networkInstanceStateDown

Default severity

warning

Message format string

Network Instance networkinstance_name is now down

Cause

The network instance has transitioned from the up state to the down state

Effect

The network instance is now down

2.20.4. networkInstanceStateUp

Table 283:  networkInstanceStateUp properties 

Property name

Value

Application name

netinst

Event name

networkInstanceStateUp

Default severity

notice

Message format string

Network Instance networkinstance_name is now up

Cause

The network instance has transitioned from the down state to the up state

Effect

The network instance is now up

2.21. ospf

2.21.1. ospfAdjacencyBfdSessionSetupFailed

Table 284:  ospfAdjacencyBfdSessionSetupFailed properties 

Property name

Value

Application name

ospf

Event name

ospfAdjacencyBfdSessionSetupFailed

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: BFD session setup failed for the OSPF neighbor ospfNbrRtrId, using interface subinterface. Failure reason: bfd_failure_reason.

Cause

This event is generated when BFD session setup fails with an adjacent OSPF neighbor.

Effect

Fast failure detection may not be possible.

2.21.2. ospfAdjacencyChange

Table 285:  ospfAdjacencyChange properties 

Property name

Value

Application name

ospf

Event name

ospfAdjacencyChange

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: Adjacency with neighbor ospfNbrRtrId, using interface subinterface, moved to state ospfNbrState due to event ospfNbrEvent.

Cause

This event is generated when an OSPF Neighbor changes state.

Effect

OSPF routing information can only utilized from neighbors in an up state.

2.21.3. ospfAdjacencyRestartStatusChange

Table 286:  ospfAdjacencyRestartStatusChange properties 

Property name

Value

Application name

ospf

Event name

ospfAdjacencyRestartStatusChange

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: The graceful restart status for OSPF neighbor ospfNbrRtrId on interface subinterface moved to new state restart_status.

Cause

This event is generated when the graceful restart status of a neighbor changes.

Effect

None

2.21.4. ospfAsMaxAgeLSA

Table 287:  ospfAsMaxAgeLSA properties 

Property name

Value

Application name

ospf

Event name

ospfAsMaxAgeLSA

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance area ospfAreaId: Max aged LSA ospfLsdbLsid type ospfLsdbType advertising router ospfLsdbRtrId.

Cause

One of the LSAs in the router's link-state database has reached its maximum age limit.

Effect

The Max Age LSA will be flushed from the LSDB.

2.21.5. ospfExportLimitReached

Table 288:  ospfExportLimitReached properties 

Property name

Value

Application name

ospf

Event name

ospfExportLimitReached

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: The export-limit ospfExportLimit is reached, additional routes will not be exported by OSPF.

Cause

This event is generated when OSPF has exported the maximum number of routes.

Effect

OSPF will not export any more routes.

2.21.6. ospfExportLimitWarning

Table 289:  ospfExportLimitWarning properties 

Property name

Value

Application name

ospf

Event name

ospfExportLimitWarning

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: OSPF has reached ospfExportLimitLogPercent% of the export-limit ospfExportLimit.

Cause

This event is generated when OSPF has exported the maximum number of routes.

Effect

OSPF will not export any more routes.

2.21.7. ospfFailure

Table 290:  ospfFailure properties 

Property name

Value

Application name

ospf

Event name

ospfFailure

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: has failed due to ospfFailureReason.

Cause

OSPF encountered an event forcing it to go down.

Effect

OSPF goes down and will restart after a timout.

2.21.8. ospfIfRxBadPacket

Table 291:  ospfIfRxBadPacket properties 

Property name

Value

Application name

ospf

Event name

ospfIfRxBadPacket

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: A bad packet was received on interface subinterface from ospfPacketSrcAddress in packet type ospfPacketType

Cause

This event is generated An OSPF packet has been received on an interface that cannot be parsed.

Effect

Bad packet is discarded

2.21.9. ospfIfStateChange

Table 292:  ospfIfStateChange properties 

Property name

Value

Application name

ospf

Event name

ospfIfStateChange

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: Interface subinterface, moved to state ospfIfState due to event ospfIfEvent

Cause

This event is generated when an OSPF Neighbor changes state.

Effect

OSPF routing information can only utilized from neighbors in an up state.

2.21.10. ospfLsdbApproachingOverflow

Table 293:  ospfLsdbApproachingOverflow properties 

Property name

Value

Application name

ospf

Event name

ospfLsdbApproachingOverflow

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: The number of external LSAs has exceeded 90% of the configured limit ospfExtLsdbLimit.

Cause

The number of external LSAs in the router's link-state database has exceeded ninety percent of the configured limit.

Effect

Warning only, normal behavior will continue.

2.21.11. ospfLsdbOverflow

Table 294:  ospfLsdbOverflow properties 

Property name

Value

Application name

ospf

Event name

ospfLsdbOverflow

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: The number of external LSAs has exceeded the configured limit ospfExtLsdbLimit.

Cause

The number of external LSAs in the router's link-state database has exceeded the configured limit.

Effect

No additional external LSA will be added.

2.21.12. ospfNbrMtuMismatch

Table 295:  ospfNbrMtuMismatch properties 

Property name

Value

Application name

ospf

Event name

ospfNbrMtuMismatch

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: Neighbor ospfNbrRtrId, using interface subinterface, signaled an unacceptable MTU.

Cause

This event is generated when an OSPF Neighbor signals an incorrect MTU.

Effect

An OSPF adjacency cannot be established if there is an MTU mismatch.

2.21.13. ospfOverloadEntry

Table 296:  ospfOverloadEntry properties 

Property name

Value

Application name

ospf

Event name

ospfOverloadEntry

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: the LSDB database has entered the overload state due to ospfOverloadReason.

Cause

Overload bit configuration

Effect

No transit traffic is routed through the overloaded router.

2.21.14. ospfOverloadExit

Table 297:  ospfOverloadExit properties 

Property name

Value

Application name

ospf

Event name

ospfOverloadExit

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: the LSDB database has exited the overload state.

Cause

Overload bit cleared

Effect

The OSPF instance has cleared the overload state.

2.21.15. ospfSpfRunRestarted

Table 298:  ospfSpfRunRestarted properties 

Property name

Value

Application name

ospf

Event name

ospfSpfRunRestarted

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: SPF runs resumed - memory resources available.

Cause

There are sufficient memory resources on the system to run the SPF to completion.

Effect

OSPF stops running SPFs until enough memory resources become availableOSPF will resume running the SPFs as required.

2.21.16. ospfSpfRunsStopped

Table 299:  ospfSpfRunsStopped properties 

Property name

Value

Application name

ospf

Event name

ospfSpfRunsStopped

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: SPF runs stopped - insufficient memory resources.

Cause

There are insufficient memory resources on the system to run the SPF to completion.

Effect

OSPF stops running SPFs until enough memory resources become available.

2.21.17. ospIfAuthDataFailure

Table 300:  ospIfAuthDataFailure properties 

Property name

Value

Application name

ospf

Event name

ospIfAuthDataFailure

Default severity

warning

Message format string

Network-instance network_instance - OSPF instance ospfInstance: A packet received on interface subinterface from ospfPacketSrcAddress and packet type ospfPacketType, failed authentication with ospfAuthError

Cause

This event is caused by interface from a router whose authentication key or authentication type conflicts with this router's authentication key or authentication type.

Effect

PDUs are dropped, with the effect depending on the PDU type

2.22. platform

2.22.1. airflowCorrected

Table 301:  airflowCorrected properties 

Property name

Value

Application name

platform

Event name

airflowCorrected

Default severity

notice

Message format string

The type in slot slot now matches the dominant airflow of other modules in the system

Cause

The specified module is now part of the majority (either front to back, or back to front) fans + PSUs in the system. This clearance is triggered when a module moves from being part of the minority to the majority, typically through other modules being plugged/unplugged.

Effect

The specified module is providing correct airflow to the system.

2.22.2. airflowMismatch

Table 302:  airflowMismatch properties 

Property name

Value

Application name

platform

Event name

airflowMismatch

Default severity

critical

Message format string

The type in slot slot does not match the airflow of other modules in the system

Cause

The inserted module does not match the airflow direction of other modules in the system.

Effect

The system is working with inefficient cooling, and may trigger thermal protection.

2.22.3. componentBooting

Table 303:  componentBooting properties 

Property name

Value

Application name

platform

Event name

componentBooting

Default severity

informational

Message format string

Component type slot has started initialization

Cause

The componentBooting event is generated when the active control module has started initializing the component.

Effect

The specified component has started initializing.

2.22.4. componentDown

Table 304:  componentDown properties 

Property name

Value

Application name

platform

Event name

componentDown

Default severity

critical

Message format string

Component type slot is no longer operational

Cause

The componentDown event is generated when a component has transitioned from any other operational state to the down state.

Effect

The specified component is now down.

2.22.5. componentFailed

Table 305:  componentFailed properties 

Property name

Value

Application name

platform

Event name

componentFailed

Default severity

critical

Message format string

Component type slot has failed, reason reason

Cause

The componentFailed event is generated when a component has transitioned from any other operational state to the failed state.

Effect

The specified component is now failed.

2.22.6. componentInserted

Table 306:  componentInserted properties 

Property name

Value

Application name

platform

Event name

componentInserted

Default severity

notice

Message format string

Component type slot has been inserted into the system

Cause

The componentInserted event is generated when a component has been initially detected by the active control module.

Effect

The specified component is detected.

2.22.7. componentLocatorDisabled

Table 307:  componentLocatorDisabled properties 

Property name

Value

Application name

platform

Event name

componentLocatorDisabled

Default severity

notice

Message format string

Locator LED disabled on type slot

Cause

The componentLocatorDisabled event is generated when the locator LED for the component has been disabled, either via timeout, or via operator action.

Effect

The specified component's LED is no longer flashing with locator functionality.

2.22.8. componentLocatorEnabled

Table 308:  componentLocatorEnabled properties 

Property name

Value

Application name

platform

Event name

componentLocatorEnabled

Default severity

notice

Message format string

Locator LED enabled on type slot for duration seconds

Cause

The componentLocatorEnabled event is generated when the locator LED for the component has been enabled by an operator action.

Effect

The specified component's LED is now flashing with locator functionality.

2.22.9. componentRemoved

Table 309:  componentRemoved properties 

Property name

Value

Application name

platform

Event name

componentRemoved

Default severity

critical

Message format string

Component type slot has been removed from the system

Cause

The componentRemoved event is generated when a component has is no longer detected in the system. This does not necessarily indicate that the component has been physically removed, but indicates that it is no longer detected by the active control module.

Effect

The specified component is no longer detected by the active control module.

2.22.10. componentRestarted

Table 310:  componentRestarted properties 

Property name

Value

Application name

platform

Event name

componentRestarted

Default severity

critical

Message format string

Component type slot has been restarted

Cause

The componentRestarting event is generated when the a component has been restarted.

Effect

The specified component has been restarted.

2.22.11. componentTemperatureExceeded

Table 311:  componentTemperatureExceeded properties 

Property name

Value

Application name

platform

Event name

componentTemperatureExceeded

Default severity

warning

Message format string

Component type slot has exceeded its temperature threshold, current temperature temperatureC

Cause

The componentTemperatureExceeded event is generated when the component has exceeded its temperature threshold.

Effect

The specified component has a temperature sensor that is overheating, the component may shut down by thermal protection.

2.22.12. componentTemperatureFailure

Table 312:  componentTemperatureFailure properties 

Property name

Value

Application name

platform

Event name

componentTemperatureFailure

Default severity

warning

Message format string

Component type slot has exceeded its safe operating temperature, component will be powered down in 10 seconds. Current temperature temperatureC

Cause

The componentTemperatureFailure event is generated when the component has exceeded its maximum temperature.

Effect

The specified component has a temperature sensor that has overheated, the component will shut down in 10 seconds for thermal protection.

2.22.13. componentTemperatureNormal

Table 313:  componentTemperatureNormal properties 

Property name

Value

Application name

platform

Event name

componentTemperatureNormal

Default severity

notice

Message format string

Component type slot temperature is now normal, current temperature temperatureC

Cause

The componentTemperatureNormal event is generated when the component has recovered from a temperature exceeded state.

Effect

The specified component is now within temperature operating limits.

2.22.14. componentUp

Table 314:  componentUp properties 

Property name

Value

Application name

platform

Event name

componentUp

Default severity

notice

Message format string

Component type slot is now operational

Cause

The componentUp event is generated when a component has transitioned from any other operational state to the up state.

Effect

The specified component is now up.

2.22.15. controlModuleActivityChange

Table 315:  controlModuleActivityChange properties 

Property name

Value

Application name

platform

Event name

controlModuleActivityChange

Default severity

critical

Message format string

Control module slot has become activity_state

Cause

The controlModuleActivityChange event is generated when there has been an activity change on either control module.

Effect

The specified control module has transitioned to the specified state.

2.22.16. controlModuleConfigSynchronized

Table 316:  controlModuleConfigSynchronized properties 

Property name

Value

Application name

platform

Event name

controlModuleConfigSynchronized

Default severity

informational

Message format string

Configuration synchronization with standby control module standby_slot has succeeded

Cause

Configuration has been successfully synchronized between the active and standby control modules.

Effect

The standby control module now has the same configuration as the active.

2.22.17. controlModuleImageSynchronized

Table 317:  controlModuleImageSynchronized properties 

Property name

Value

Application name

platform

Event name

controlModuleImageSynchronized

Default severity

informational

Message format string

Image synchronization with standby control module standby_slot has succeeded

Cause

Images have been successfully synchronized between the active and standby control modules.

Effect

The standby control module now has the same images as the active.

2.22.18. controlModuleInSync

Table 318:  controlModuleInSync properties 

Property name

Value

Application name

platform

Event name

controlModuleInSync

Default severity

informational

Message format string

Active and standby control modules are now synchronized

Cause

All synchronization activities have completed between the active and standby control modules.

Effect

The standby control module is now ready for a control module switchover, if necessary.

2.22.19. controlModuleOverlaySynchronized

Table 319:  controlModuleOverlaySynchronized properties 

Property name

Value

Application name

platform

Event name

controlModuleOverlaySynchronized

Default severity

informational

Message format string

Overlay synchronization with standby control module standby_slot has succeeded

Cause

Overlays have been successfully synchronized between the active and standby control modules.

Effect

The standby control module now has the same overlay as the active.

2.22.20. controlModuleSyncLost

Table 320:  controlModuleSyncLost properties 

Property name

Value

Application name

platform

Event name

controlModuleSyncLost

Default severity

critical

Message format string

Active control module has lost visibility of the standby control module

Cause

Connection between the active and standby control modules has been lost.

Effect

The standby control module is no longer capable of taking over in the event of a failure of the active, no configuration or images are being synchronized.

2.22.21. controlModuleSyncStart

Table 321:  controlModuleSyncStart properties 

Property name

Value

Application name

platform

Event name

controlModuleSyncStart

Default severity

informational

Message format string

Active and standby control modules are now synchronizing synchronization_category

Cause

A synchronization has been triggered between the active and standby control modules.

Effect

Configuration, images, or persistent storage is being synchronized between the active and standby control module.

2.22.22. fantrayEmpty

Table 322:  fantrayEmpty properties 

Property name

Value

Application name

platform

Event name

fantrayEmpty

Default severity

critical

Message format string

Component fan-tray slot is not present in the system

Cause

The fantrayEmpty event is generated when a fan-tray has transitioned from any other operational state to the empty state, or is never present.

Effect

The system may have cooling issues.

2.22.23. linecardCapacityDegraded

Table 323:  linecardCapacityDegraded properties 

Property name

Value

Application name

platform

Event name

linecardCapacityDegraded

Default severity

critical

Message format string

Linecard slot fabric capacity degraded

Cause

The specified linecard has insufficient operational fabric links.

Effect

Packets may be dropped if the linecard is sending and receiving significant amounts of traffic to the fabric.

2.22.24. linecardCapacityNormal

Table 324:  linecardCapacityNormal properties 

Property name

Value

Application name

platform

Event name

linecardCapacityNormal

Default severity

informational

Message format string

Linecard slot fabric capacity normal

Cause

The specified linecard has sufficient operational fabric links again.

Effect

Normal behavior is restored for sending and receiving traffic to the fabric.

2.22.25. platformLowPower

Table 325:  platformLowPower properties 

Property name

Value

Application name

platform

Event name

platformLowPower

Default severity

emergency

Message format string

Insufficient power for currently installed components, current_powerW available, required_powerW required

Cause

Available power from operational power supplies is insufficient to power all components in the system.

Effect

Components in the system will be powered down until required power is lower than what is supplied by operational power supplies.

2.22.26. platformLowReservePower

Table 326:  platformLowReservePower properties 

Property name

Value

Application name

platform

Event name

platformLowReservePower

Default severity

critical

Message format string

Insufficient reserve power for currently installed components, current_powerW available, required_powerW required

Cause

Available power is less than one power supply capacity extra to power all components in the system.

Effect

Power will be insufficient if one operational power supply is lost.

2.22.27. platformNormalPower

Table 327:  platformNormalPower properties 

Property name

Value

Application name

platform

Event name

platformNormalPower

Default severity

informational

Message format string

Sufficient power for currently installed components, current_powerW available, required_powerW required

Cause

Available power from operational power supplies is sufficient to power all components in the system.

Effect

Enough power is available.

2.22.28. psuInputDown

Table 328:  psuInputDown properties 

Property name

Value

Application name

platform

Event name

psuInputDown

Default severity

warning

Message format string

Power input on power-supply slot is down

Cause

Input fault on the specified power supply is set.

Effect

The specified power supply can no longer supply power to the system.

2.22.29. psuInputUp

Table 329:  psuInputUp properties 

Property name

Value

Application name

platform

Event name

psuInputUp

Default severity

notice

Message format string

Power input on power-supply slot is up

Cause

Input fault on the specified power supply is clear.

Effect

The specified power supply can now supply power to the system.

2.22.30. psuOutputDown

Table 330:  psuOutputDown properties 

Property name

Value

Application name

platform

Event name

psuOutputDown

Default severity

warning

Message format string

Power output on power-supply slot is down

Cause

Output fault on the specified power supply is set.

Effect

The specified power supply can no longer supply power to the system.

2.22.31. psuOutputUp

Table 331:  psuOutputUp properties 

Property name

Value

Application name

platform

Event name

psuOutputUp

Default severity

notice

Message format string

Power output on power-supply slot is up

Cause

Output fault on the specified power supply is clear.

Effect

The specified power supply can now supply power to the system.

2.22.32. psuTemperatureFault

Table 332:  psuTemperatureFault properties 

Property name

Value

Application name

platform

Event name

psuTemperatureFault

Default severity

warning

Message format string

Component type slot has raised a temperature fault, current temperature temperatureC

Cause

The psuTemperatureFault event is generated when the power supply raises a temperature fault.

Effect

The power supply is overheating, and may shut down by thermal protection.

2.22.33. psuTemperatureNormal

Table 333:  psuTemperatureNormal properties 

Property name

Value

Application name

platform

Event name

psuTemperatureNormal

Default severity

notice

Message format string

Component type slot temperature fault is now clear, current temperature temperatureC

Cause

The psuTemperatureNormal event is generated when the power supply recovered from a temperature fault state.

Effect

The power supply is now within temperature operating limits.

2.22.34. systemReboot

Table 334:  systemReboot properties 

Property name

Value

Application name

platform

Event name

systemReboot

Default severity

critical

Message format string

System going down for reboot

Cause

The systemReboot event is generated when a software triggered reboot has been made.

Effect

The system will go offline for reboot.

2.23. qos

2.23.1. platformQoSProfileHighUtilization

Table 335:  platformQoSProfileHighUtilization properties 

Property name

Value

Application name

qos

Event name

platformQoSProfileHighUtilization

Default severity

warning

Message format string

The QoS resource called resource-name has reached threshold% or more utilization on linecard linecard, forwarding complex forwarding-complex. Only free-entries entries are remaining.

Cause

This event is generated when the utilization of a QoS resource has increased to a level that may warrant concern if futher resources are consumed

Effect

None

2.23.2. platformQoSProfileHighUtilizationLowered

Table 336:  platformQoSProfileHighUtilizationLowered properties 

Property name

Value

Application name

qos

Event name

platformQoSProfileHighUtilizationLowered

Default severity

notice

Message format string

The QoS resource called resource-name has decreased back to threshold% or less utilization on linecard linecard, forwarding complex forwarding-complex.

Cause

This event is generated when the utilization of a QoS resource has decreased to a level that may no longer warrant concern

Effect

None

2.24. sflow

2.24.1. sFlowAgentChange

Table 337:  sFlowAgentChange properties 

Property name

Value

Application name

sflow

Event name

sFlowAgentChange

Default severity

notice

Message format string

SFLOW: The global sFlow Agent has administratively been changed to state

Cause

This notification is generated when a sFlow global process changes administrative state.

Effect

The sFlow global process state has changed.

2.24.2. sFlowCollectorUnreachable

Table 338:  sFlowCollectorUnreachable properties 

Property name

Value

Application name

sflow

Event name

sFlowCollectorUnreachable

Default severity

warning

Message format string

SFLOW: Collector collector-id - IP address: collector-ip is unreachable

Cause

This notification is generated when the specified sFlow collector will no longer receive sflow sample data until reachability is restored

Effect

Restore IP reachability to the sFlow collector.