Event Name | Change |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
sharedConfigSessionError | Removed |
ipSubinterfaceDown | Removed |
New | |
ipSubinterfaceUp | Removed |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New | |
New |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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. |
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 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. |
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. |
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 |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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 |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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 |
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 |
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 |
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. |
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. |
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. |
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 |
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 |
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 |
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. |
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. |
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 |
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 |
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. |
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. |
Property name | Value |
Application name | chassis |
Event name | platformIpMplsFwdResourceHighUtilization |
Default severity | warning |
Message format string | The forwarding 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 forwarding resource has increased to a level that may warrant concern if futher resources are consumed |
Effect | None |
Property name | Value |
Application name | chassis |
Event name | platformIpMplsFwdResourceHighUtilizationLowered |
Default severity | notice |
Message format string | The forwarding 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 forwarding resource has decreased to a level that may no longer warrant concern |
Effect | None |
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 futher resources are consumed |
Effect | None |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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. |
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. |
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. |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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 levellevel 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. |
Property name | Value |
Application name | isis |
Event name | isisAdjacencyChange |
Default severity | warning |
Message format string | In network-instance network_instance, the levellevel 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. |
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 levellevel IS-IS adjacency with system sys_id changed, moving to new state restart_status. |
Cause | This event is generated when the graceful restart status of a neighbor changes. |
Effect | None |
Property name | Value |
Application name | isis |
Event name | isisAreaMismatch |
Default severity | warning |
Message format string | In network-instance network_instance, a LAN Level 1 Hello PDU was received from system sys_id on interface subinterface with no Area Addresses matching the areas to which this IS router belongs. |
Cause | This event is generated to alert of a possible area-id misconfiguration inside a L1 area. |
Effect | L1 adjacency cannot form |
Property name | Value |
Application name | isis |
Event name | isisAuthDataFail |
Default severity | warning |
Message format string | In network-instance network_instance, a PDU was received from system sys_id on interface subinterface with unexpected or incorrect data in the Authentication TLV. |
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 |
Property name | Value |
Application name | isis |
Event name | isisAuthTypeMismatch |
Default severity | warning |
Message format string | In network-instance network_instance, a PDU was received from system sys_id on interface subinterface with an unrecognized or unsupported authentication type in TLV 10. |
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 |
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 |
Property name | Value |
Application name | isis |
Event name | isisCircuitMtuTooLow |
Default severity | warning |
Message format string | In network-instance network_instance, an LSP PDU or SNP PDU could not be transmitted on interface subinterface because the operational MTU of the interface is too small. 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 |
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 levellevel database has become corrupted. |
Cause | Memory corruption or other. |
Effect | LSP is removed |
Property name | Value |
Application name | isis |
Event name | isisLspBufferSizeMismatch |
Default severity | warning |
Message format string | In network-instance network_instance, the LSP with id lsp_id in the levellevel database could not be flooded because the configured lsp-mtu-size of conf_lsp_mtu bytes does not match the value of received_lsp_buffer bytes in the received LSPBufferSize TLV. |
Cause | Network misconfiguration of the maximum LSP buffer size |
Effect | LSP PDU is not flooded |
Property name | Value |
Application name | isis |
Event name | isisLspFragmentTooLarge |
Default severity | warning |
Message format string | In network-instance network_instance, the LSP PDU fragment lsp_id could not be flooded because the configured LSP MTU size is too small. An MTU size of at least required_lsp_mtu bytes is required. |
Cause | Misconfiguration of LSP MTU size |
Effect | LSP PDU is not flooded |
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 levellevel database has been purged by purge_originator. |
Cause | LSP lifetime expired or other reason |
Effect | The PDU is removed |
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 levellevel 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 |
Property name | Value |
Application name | isis |
Event name | isisMaxAreaAddressesMismatch |
Default severity | warning |
Message format string | In network-instance network_instance, a PDU was received from system sys_id on interface subinterface with an unexpected Max Area Addresses value in the IS-IS PDU header. |
Cause | Misconfiguration of max area addresses in the neighbor |
Effect | The PDU is dropped |
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 levellevel 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 |
Property name | Value |
Application name | isis |
Event name | isisOverloadChange |
Default severity | warning |
Message format string | In network-instance network_instance, the IS-IS instance has entered or exited from overload state. |
Cause | Overload bit configuration |
Effect | No transit traffic is routed through the overloaded router. |
Property name | Value |
Application name | isis |
Event name | isisOwnLspPurge |
Default severity | warning |
Message format string | In network-instance network_instance, a levellevel 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 |
Property name | Value |
Application name | isis |
Event name | isisSystemIdLengthMismatch |
Default severity | warning |
Message format string | In network-instance network_instance, a PDU was received from system sys_id on interface subinterface with an unexpected System ID length in the IS-IS PDU header. |
Cause | Misconfiguration of system ID length in the neighbor |
Effect | The PDU is dropped |
Property name | Value |
Application name | isis |
Event name | isisVersionMismatch |
Default severity | warning |
Message format string | In network-instance network_instance, a hello PDU was received from system sys_id on interface subinterface with IS-IS protocol version not matching the expected value. |
Cause | Unsupported IS-IS version |
Effect | PDUs cannot be exchanged |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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. |
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. |
Property name | Value |
Application name | platform |
Event name | componentFailed |
Default severity | critical |
Message format string | Component type slot has failed |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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 |
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 |