Load Balancer Events

The following are the events related to Load Balancer.

Event ID: 344

Message
Load Balance Protocol enabled.
Platforms K, KA, KB
Category Load Balancer
Severity Information

Event ID: 345

Message
Load Balance Protocol disabled.
Platforms K, KA, KB
Category Load Balancer
Severity Information

Event ID: 346

Message
<PORT_ID> – established.
Platforms K, KA, KB
Category Load Balancer
Severity Information
Description This log event informs the user that the LDBAL port enters the established state.

Event ID: 347 (Severity: Warning)

Message
<PORT_ID> - not established.
Platforms K, KA, KB
Category Load Balancer
Severity Warning
Description This log event informs the user that the LDBAL port enters the not established state.

Event ID: 348 (Severity: Warning)

Message
<PORT_ID> - detected topology error: <MAC_ADDRESS>.
Platforms K, KA, KB
Category Load Balancer
Severity Warning
Description This log event informs the user that the LDBAL port enters the error state (bad topology has been detected on that port.

Event ID: 349 (Severity: Warning)

Message
Domain size exceeded protocol-imposed limit: <DOMAIN_COUNT>.
Platforms K, KA, KB
Category Load Balancer
Severity Warning
Description This log event informs the user that number of load balance switches in the domain exceeded the protocol-defined limit.

Event ID: 350

Message
<PORT_ID> - Received untagged packet. Packet Type <TYPE_ID>.
Platforms K, KA, KB
Category Load Balancer
Severity Information
Description This log event informs the user that an untagged packet was received on a Load-Balance established port

Event ID: 351

Message
<PORT_ID> - Receivedx Type2 Query NAK.
Platforms K, KA, KB
Category Load Balancer
Severity Debug
Description This log event informs the user that a Type2 Query NAK was received on a Load-Balance established port.

Event ID: 352

Message
<MAC_ADDRESS> moved from <WARNING_STRING> to <WARNING_STRING>, <MAC_ADDRESS>R.
Platforms K, KA, KB
Category Load Balancer
Severity Debug
Description This log event informs the user that a MAC address moved.

Event ID: 353

Message
<PORT_ID> - Received Update Packet from <MAC_ADDRESS>
Platforms K, KA, KB
Category Load Balancer
Severity Debug
Description This log event informs the user that a updated packet received form MAC.

Event ID: 354

Message
Nonexistent address <MAC_ADDRESS> deleted.
Platforms K, KA, KB
Category Load Balancer
Severity Debug
Description This log event informs the user that a MAC address that does not exist in the LdBal tables is being deleted.

Event ID: 355

Message
<WARNING_STRING>: <MAC_ADDRESS> MISMATCH. NUM. Software <MAC_ADDRESS>.
Platforms K, KA, KB
Category Load Balancer
Severity Debug
Description This log event informs the user that a MAC address that exists in the LdBal-S/w address tables does not exist in the H/w Addr Tables

Event ID: 356

Message
<PORT_ID> - ACK failure for packet <COUNT-NUM>.
Platforms K, KA, KB
Category Load Balancer
Severity Debug
Description This log event informs the user that the LDBAL port has been disabled since the retransmit count was exceeded for a packet requiring an ACK

Event ID: 357 (Severity: Warning)

Message
<PORT_ID> load balance version VERSION-ID not supported- update firmware.
Platforms K, KA, KB
Category Load Balancer
Severity Warning
Description This log event informs the user that the received load balance packet contains a version of the protocol not supported by this switch's operating system.

Event ID: 358

Message
<WARNING_STRING>
Platforms K, KA, KB
Category Load Balancer
Severity Debug
Description A generic message descriptor. Used to logging debug messages

Event ID: 444 (Severity: Warning)

Message
<PORT_ID>: received mesh packet on non-mesh port.
Platforms K, KA, KB
Category Load Balancer
Severity Warning
Description This log event informs the user that a port received a mesh packet on a non-mesh port.

Event ID: 445 (Severity: Warning)

Message
Cannot accept switch 1600/24xx/4000/8000 into mesh.
Platforms K, KA, KB
Category Load Balancer
Severity Warning
Description This log event informs the user that the switch is in compatibility mode MODE_M, which means that there are two alphas that have the same mac programmed in on different vlans. If this is the case, a voyager will not be allowed into the mesh.

Event ID: 446 (Severity: Warning)

Message
Max. hop count exceeded. Check your mesh topology.
Platforms K, KA, KB
Category Load Balancer
Severity Warning
Description This log event warns the user that mesh domain has exceeded the maximum hop count. When this happens, cost packets will not propagate furter, resulting in immature mesh domain.

Event ID: 447

Message
<PORT_ID> – initialized.
Platforms K, KA, KB
Category Load Balancer
Severity Information
Description This log event informs the user that the LDBAL port enters the initialization state.

Event ID: 451 (Severity: Warning)

Message
Unsupported protocol. Upgrade <MAC_ADDRESS>R's firmware.
Platforms K, KA, KB
Category Load Balancer
Severity Warning
Description This log event informs the user that the received load balance packet contains a protocol number that is not supported by this switch's operating system.

Event ID: 452 (Severity: Warning)

Message
Inconsistent WARN-STRING config with <MAC_ADDRESS><MAC_ADDRESS>R.
Platforms K, KA, KB
Category Load Balancer
Severity Warning
Description This log event informs the user there is a mismatch in configuration across the mesh. According to the mesh rules, this is not allowed.

Event ID: 453 (Severity: Warning)

Message
Incompatible mesh switch <MAC_ADDRESS><MAC_ADDRESS> detected on <PORT_ID>.
Platforms K, KA, KB
Category Load Balancer
Severity Warning
Description This log event informs the user the switch received a meshing protocol packet on a mesh port that is in a different mode than what the switch is in.

Event ID: 4633 (Severity: Warning)

Message
Configuration entry was removed because MAC-Notify traps cannot be enabled on a port that is a member of a trunk., Mac-notify traps <PORT_ID> MAC-NOTIFY-ID
Platforms K, KA, KB
Category Load Balancer
Severity Warning
Description This log event informs the user the Mac Notify configuration is disabled on port which is part of trunk.