Stacking cable support for X440-G2 (correction to documentation)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
08-15-2016 04:55 PM
In the Summit Hardware Installation Guide for EXOS 21, the "Stacking Cables" table is incorrect with respect to stacking-cable support on the X440-G2 switch.
http://documentation.extremenetworks.com/summit/Summit_Family_HW_Install/Stacking/r_stacking-cables....
At the bottom of the table, the stated limitation -- 10G stacking ports on ExtremeSwitching X440-G2 (48-port switches only), Summit X450-G2 10G, and ExtremeSwitching X620 switches -- should apply only to the 10 meter cable (model no. 10307). The shorter cable lengths (model nos. 10304, 10305, and 10306) are supported for all models of the X440-G2 as well as for the X450-G2 (10G models) and the X620.
I'll be sure to correct the table in the next update to the document.
Larry Kunz
Information Development
Extreme Networks
http://documentation.extremenetworks.com/summit/Summit_Family_HW_Install/Stacking/r_stacking-cables....
At the bottom of the table, the stated limitation -- 10G stacking ports on ExtremeSwitching X440-G2 (48-port switches only), Summit X450-G2 10G, and ExtremeSwitching X620 switches -- should apply only to the 10 meter cable (model no. 10307). The shorter cable lengths (model nos. 10304, 10305, and 10306) are supported for all models of the X440-G2 as well as for the X450-G2 (10G models) and the X620.
I'll be sure to correct the table in the next update to the document.
Larry Kunz
Information Development
Extreme Networks
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
11-23-2017 03:59 PM
Hello All,
what is the reason for this limitation?
Thanks and regards
Ángel
what is the reason for this limitation?
Thanks and regards
Ángel
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
08-19-2016 10:32 AM
I informed our team about this issue.
