Question 190
During an independent network handover at the Meadow Junction branch of Ionfield Logistics, the monitored service is air-quality sensor reporting for clients in 10.77.12.0/24; incident reference is DC-8416. The on-duty analyst documents this symptom before proposing any configuration: An Eth-Trunk bundle forms with one member, but a second link does not join while its speed and peer negotiation differ. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which ongoing operational check is most relevant to recognizing recurrence of this failure?
Answer and explanations
Trend CRC, discards, optical power and link renegotiations. This alternative addresses a different issue (ethernet interface error counters). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: An Eth-Trunk bundle forms with one member, but a second link does not join while its speed and peer negotiation differ. The decisive distinction is: Monitor LACP partner IDs, selected-port counts and per-member error rates.
The decisive evidence is: The on-duty analyst documents this symptom before proposing any configuration: An Eth-Trunk bundle forms with one member, but a second link does not join while its speed and peer negotiation differ. Monitor LACP partner IDs, selected-port counts and per-member error rates.
Trend unknown-unicast rates, MAC table capacity and frequent address aging. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: An Eth-Trunk bundle forms with one member, but a second link does not join while its speed and peer negotiation differ. This alternative addresses a different issue (unknown unicast flooding). The decisive distinction is: Monitor LACP partner IDs, selected-port counts and per-member error rates.
This alternative addresses a different issue (vlan pruning during migration). The option would address: Audit VLAN path dependencies before trunk pruning and monitor outage reports afterward. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: An Eth-Trunk bundle forms with one member, but a second link does not join while its speed and peer negotiation differ.