A network technician is troubleshooting a switch-to-switch trunk link that is dropping traffic. Reviewing the switch console logs reveals a native VLAN mismatch error, while interface statistics report high numbers of late collisions. Which TWO configuration actions should the technician take to resolve these issues? (Select TWO.)
- Reconfigure both ends of the trunk link to use the same native VLAN ID.Cevap
- Configure matching duplex settings (or enable auto-negotiation on both ends) for the trunk interfaces.Cevap
- CSet the Spanning Tree Protocol (STP) priority to 0 on both switches to clear the interface block.
- DAssign IP addresses from different subnets to the two switch interfaces without a Layer 3 router.
Cevap
The technician should configure identical native VLAN IDs on both switch trunk ports and ensure matching duplex settings across the link.
To resolve native VLAN mismatch errors, both ends of the 802.1Q trunk must be configured with the exact same native VLAN ID so untagged frames are correctly directed. To resolve late collisions, both switch ports must agree on duplex settings (either both forced to full-duplex or both using auto-negotiation), eliminating collision detection conflicts.
Adım Adım Çözüm
Anahtar Kavram
Troubleshooting 802.1Q native VLAN mismatches and interface duplex mismatches on switch trunks.