- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- gbe2c NCU VLAN trunk external switch
BladeSystem - General
1752794
Members
6355
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
05-02-2009 03:12 AM
05-02-2009 03:12 AM
gbe2c NCU VLAN trunk external switch
Hi
I am trying to trunk VLAN information to a BL460 blade in a C7000 chassis. We have a gbe2c switch. Not used the C7000 or gbe2c before so pls bear with me
Need to allow untagged traffic (VLAN1) and two tagged VLANs (101 and 102) which are also defined on an external switch (a Powerconnect 6224).
I have port 21 from each gbe2c uplinked to a trunk port on the Powerconnect. Blade 5 needs to see untagged (VLAN1), vlan 101 and vlan 102 traffic. So I have added ports 5,17,18 and 21 as a member of VLAN 1, 101 and 102. The VLANs are each in a seperate STP group (I have tried turning off STP).
Config:
/* Enclosure: 403320-B21, EnclosureName: ENCLOSURE1
/* Slot: 2
/c/port 5
tag ena
/c/port 17
tag ena
/c/port 18
tag ena
/c/port 21
tag ena
/c/l2/vlan 101
ena
name "Storage1"
def 5 17 18 21
/c/l2/vlan 102
ena
name "Storage2"
def 5 17 18 21
/c/l2/stp 1/port 5/on
/c/l2/stp 2/clear
/c/l2/stp 2/add 101
/c/l2/stp 3/clear
/c/l2/stp 3/add 102
/c/l3/if 1
* ena
* addr
/c/l3/gw 1
* ena
* addr
/c/l3/dns
* prima
* secon
/
script end /**** DO NOT EDIT THIS LINE!
I have added three VLANs in NCU on the blade: 1, 101 and 102. VLAN 1 works fine although I think this is just the PVID working.
Does anything jump out above as incorrect? Currently I can't see VLAN 101 or 102, i.e. I can't ping the IP address set for either of these VLANs on the Powerconnect from the virtual NIC created by NCU with above config.
Any help appreciated - like I said above first experience with a HP Blade chassis.
TIA
Zee
I am trying to trunk VLAN information to a BL460 blade in a C7000 chassis. We have a gbe2c switch. Not used the C7000 or gbe2c before so pls bear with me
Need to allow untagged traffic (VLAN1) and two tagged VLANs (101 and 102) which are also defined on an external switch (a Powerconnect 6224).
I have port 21 from each gbe2c uplinked to a trunk port on the Powerconnect. Blade 5 needs to see untagged (VLAN1), vlan 101 and vlan 102 traffic. So I have added ports 5,17,18 and 21 as a member of VLAN 1, 101 and 102. The VLANs are each in a seperate STP group (I have tried turning off STP).
Config:
/* Enclosure: 403320-B21, EnclosureName: ENCLOSURE1
/* Slot: 2
/c/port 5
tag ena
/c/port 17
tag ena
/c/port 18
tag ena
/c/port 21
tag ena
/c/l2/vlan 101
ena
name "Storage1"
def 5 17 18 21
/c/l2/vlan 102
ena
name "Storage2"
def 5 17 18 21
/c/l2/stp 1/port 5/on
/c/l2/stp 2/clear
/c/l2/stp 2/add 101
/c/l2/stp 3/clear
/c/l2/stp 3/add 102
/c/l3/if 1
* ena
* addr
/c/l3/gw 1
* ena
* addr
/c/l3/dns
* prima
* secon
/
script end /**** DO NOT EDIT THIS LINE!
I have added three VLANs in NCU on the blade: 1, 101 and 102. VLAN 1 works fine although I think this is just the PVID working.
Does anything jump out above as incorrect? Currently I can't see VLAN 101 or 102, i.e. I can't ping the IP address set for either of these VLANs on the Powerconnect from the virtual NIC created by NCU with above config.
Any help appreciated - like I said above first experience with a HP Blade chassis.
TIA
Zee
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2009 01:23 PM
05-06-2009 01:23 PM
Re: gbe2c NCU VLAN trunk external switch
Zee:
the GBE2 config looks fine here. I would doublecheck your PowerConnect config.
Also, check your version of NCU. There have been a lot of bugs with NCU VLAN tagging that have been cleared up in recent NCU versions i.e. NCU v9.50 and later. (If you update NCU, you also need to update NIC drivers)
the GBE2 config looks fine here. I would doublecheck your PowerConnect config.
Also, check your version of NCU. There have been a lot of bugs with NCU VLAN tagging that have been cleared up in recent NCU versions i.e. NCU v9.50 and later. (If you update NCU, you also need to update NIC drivers)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP