- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: GbE2c Ethernet Blade Switch Trunk Numbering Is...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2009 10:24 AM
тАО12-30-2009 10:24 AM
Here is a sample config output:
>> Main# info/l2/trunk
Trunk group 1: Enabled
Protocol - Static
port state:
17: STG 1 forwarding
18: STG 1 forwarding
Trunk group 13: Enabled
Protocol - LACP
port state:
20: STG 1 forwarding
Trunk group 14: Enabled
Protocol - LACP
port state:
21: STG 1 forwarding
Trunk group 15: Enabled
Protocol - LACP
port state:
22: STG 1 forwarding
Trunk group 16: Enabled
Protocol - LACP
port state:
23: STG 1 forwarding
You can see that there are trunk groups 1, 13, 14, 15 and 16 defined. The issue is that the switch only allows trunk numbers 1-12 to be modified.
>> Main# cfg/l2/trunk 13
Error: bad trunk group number 13; must be between 1 and 12
If you try to modify trunk group 1, there's no problem:
>> Main# cfg/l2/trunk 1
------------------------------------------------------------
[Trunk group 1 Menu]
add - Add port to trunk group
rem - Remove port from trunk group
ena - Enable trunk group
dis - Disable trunk group
del - Delete trunk group
cur - Display current Trunk Group configuration
We don't know how these trunk groups higher than 12 ever happened, but the real question is what we can do to get rid of them and recreate them with a number 12 or lower.
Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2009 03:15 PM
тАО12-30-2009 03:15 PM
Re: GbE2c Ethernet Blade Switch Trunk Numbering Issues
to get rid of them, turn off lacp on the ports.
then you can create a static port trunk if that is what is desired.
make sure that the upstream switch config matches, i.e. is it running dynamic LACP or a static port trunk?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2009 04:59 PM
тАО12-30-2009 04:59 PM
Re: GbE2c Ethernet Blade Switch Trunk Numbering Issues
How would we go about making a single LACP trunk group with ports 20-24 included?
Right now, all of our 8 switches has a different configuration. Some have each port in its own trunk group, some have three ports in one trunk group, and one of the switches has it more or less correct, such as the following:
>> Main# info/l2/trunk
Trunk group 13: Enabled
Protocol - LACP
Port State:
21: STG 1 forwarding
22: STG 1 forwarding
23: STG 1 forwarding
24: STG 1 forwarding
How do we add port 20 to that, and then make it the same on all the switches?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2009 05:35 PM
тАО12-30-2009 05:35 PM
Solution/c/l2/lacp/port 20/mode active
/c/l2/lacp/port 20/adminkey 20
/c/l2/lacp/port 21/mode active
/c/l2/lacp/port 21/adminkey 20
/c/l2/lacp/port 22/mode active
/c/l2/lacp/port 22/adminkey 20
/c/l2/lacp/port 23/mode active
/c/l2/lacp/port 23/adminkey 20
/c/l2/lacp/port 24/mode active
/c/l2/lacp/port 24/adminkey 20
apply
save
then assuming the proper lacp channel config on the upstream switch, a 5 port channel will be formed and trunk 13 will be created on the gbe2c.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2010 09:19 AM
тАО01-04-2010 09:19 AM