- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- vlan Tagging not working?
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
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
тАО02-17-2009 09:09 AM
тАО02-17-2009 09:09 AM
vlan Tagging not working?
I'm setting up a DL360 with a single NIC and need to setup vlan tagging on to two networks, one vlan, 10 is our internal network where the device needs to go to a SQL server on 192.168.0.5, and the other vlan 100 is our web dmz with a gateway of 192.168.100.10.
The adapter is plugged in to a Cisco Catalyst.
having setup the hp network configuration utility with the two vlans
internal network 10
web dmz 100
I get two new network connections in network connections
I have setup the web DMZ vlan adapter with a ip, subnet and default gateway and have left the other vlan with just the IP and subnet
I can ping 192.168.100.10, however i cannot ping 192.168.0.5 through the other "port"
The cat is set to
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,100
so i should be able to see both vlans, however is just not working.
I don't think i should set a default gateway on the internal nic as i'm not happy with having two default gateways and looking at the routing table it seems to show that traffic for 192.168.0.5 goes out of 192.168.0.4 (the servers internal vlan 10 ip) but i just cannot do anything from this route, any ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2009 10:38 AM
тАО02-17-2009 10:38 AM
Re: vlan Tagging not working?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-18-2009 01:27 AM
тАО02-18-2009 01:27 AM
Re: vlan Tagging not working?
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 100
switchport trunk allowed vlan 10,100
switchport mode trunk
spanning-tree portfast edge
Thanks for your help on this
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-18-2009 08:46 AM
тАО02-18-2009 08:46 AM
Re: vlan Tagging not working?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-19-2009 12:55 AM
тАО02-19-2009 12:55 AM
Re: vlan Tagging not working?
The line "switchport trunk native vlan 100
" should be changed!
Result of this line is that vlan-tag is stripped from the packet before it is sent to the connected host.
Packets incomming to the host accepts vlan10 and vlan100, but unless the hpncu also has a "native" vlan setting untagged packets probably are ignored.
So if you keep the native vlan as "1" (or any other vlan-id you don't really use) you'll get better results.
---------------
As for routing setting a default-gateway on both nic's gives unpredictable results.
the host will use the gateway last set, or of the first interface up at boottime. Also when a networkcable is unplugged and plugged in again, it will switch to the default-gateway of the connected nic.
better configure only one "default" gateway (route 0.0.0.0) and other routes as "static"
(route add n.n.n.n mask m.m.m.m g.g.g.g /p)