- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
M4250 auto-trunking failure
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
M4250 auto-trunking failure
New installation, 10G copper SFP connected between 2 switches. Configured via auto-trunk, link was up and stable for 1 week then failed when no changes were being made. Testing confirmed the SFP slot on both switches stopped responding. Moving the SFP instantly restored the trunk, but moving it back showed the original slot still dead. All port configurations match. Any insight?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: M4250 auto-trunking failure
@reisley wrote:
Moving the SFP instantly restored the trunk, but moving it back showed the original slot still dead.
Moving == moved the SFP module to an alternate (different) slot?
Dead is not really a useful information.
LED status when the trunk is not workable?
Port Status ?
Logs Monitoring > Logs > Memory Log ?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: M4250 auto-trunking failure
Sorry, original submission was through a link that only allowed 150 words.
Interconnecting M4250-40G8XF-POE+ switches with AXM765v2 SFP+ modules.
Configured both switches as entirely vlan 10, including the PVID of the SFP slots, and left ports 41-48 otherwise at default settings.
When connected to port 41, the auto-trunk feature initially linked up properly and established necessary trunk settings. Full communication was possible between endpoints on either switch. After 7 days, with no changes made to the switch settings, the trunk suddenly failed.
Upon examination, the trunk had no LEDs, a port status of "down", and all auto-trunk settings had reverted to default -- "general" port type with no associated VLANs, and so forth -- on both switches. Tested by relocating both modules to port 42, trunk immediately came back up and settings were as left originally. Moved only one module (either one) back to port 41 and trunk again went down, reverted (at both ends) to "general" type with no auto-trunk configurations.
It is as if -- without alarm or error -- ports at both ends of the trunk had hardware failures. Trunk is now working successfully on port 42.
I am remote and have limited access to the switch. Besides the memory log, what else might provide useful information to troubleshoot this issue? Do these switches have a full console interface, to see if somehow the port was shut down? Would a port shutdown port be reflected in the web interface?