HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: vlan tagging issue
Operating System - Linux
1830133
Members
2783
Online
109999
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
Forums
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
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
04-30-2009 04:53 AM
04-30-2009 04:53 AM
vlan tagging issue
I am trying to setup VLAN tagging on a server for the first time...
I was told by network that the VLAN ID's were:
192.168.131.129 VLAN ID 868
155.90.164.4 VLAN ID 922
When I try to restart the network I am receiving the following errors:
Bringing up interface eth0.868: SIOCGIFFLAGS: No such device
ERROR: Trying to add VLAN #868 to IF -:eth0:- error: Invalid Argument [ FAILED ]
Bringing up interface eth0.922: SIOCGIFFLAGS: No such device
ERROR: Trying to add VLAN #922 to IF -:eth0:- error: Invalid Argument [ FAILED ]
My ifcfg-eth0 files are setup as follows:
=> cat ifcfg-eth0
DEVICE=eth0
ONBOOT=yes
=> cat itcfg-eth0.868
DEVICE=eth0.868
BOOTPROTO=static
BROADCAST=192.168.131.191
HWADDR=00:22:19:2C:2F:17
IPADDR=192.168.131.129
NETMASK=255.255.255.192
NETWORK=192.168.131.128
ONBOOT=yes
TYPE=Ethernet
VLAN=yes
=> cat itcfg-eth0.922
DEVICE=eth0.922
BOOTPROTO=static
BROADCAST=155.90.164.61
HWADDR=00:22:19:2C:2F:17
IPADDR=155.90.164.4
NETMASK=255.255.255.192
NETWORK=155.90.164.0
ONBOOT=yes
TYPE=Ethernet
VLAN=yes
Any ideas as to the issue ??
I was told by network that the VLAN ID's were:
192.168.131.129 VLAN ID 868
155.90.164.4 VLAN ID 922
When I try to restart the network I am receiving the following errors:
Bringing up interface eth0.868: SIOCGIFFLAGS: No such device
ERROR: Trying to add VLAN #868 to IF -:eth0:- error: Invalid Argument [ FAILED ]
Bringing up interface eth0.922: SIOCGIFFLAGS: No such device
ERROR: Trying to add VLAN #922 to IF -:eth0:- error: Invalid Argument [ FAILED ]
My ifcfg-eth0 files are setup as follows:
=> cat ifcfg-eth0
DEVICE=eth0
ONBOOT=yes
=> cat itcfg-eth0.868
DEVICE=eth0.868
BOOTPROTO=static
BROADCAST=192.168.131.191
HWADDR=00:22:19:2C:2F:17
IPADDR=192.168.131.129
NETMASK=255.255.255.192
NETWORK=192.168.131.128
ONBOOT=yes
TYPE=Ethernet
VLAN=yes
=> cat itcfg-eth0.922
DEVICE=eth0.922
BOOTPROTO=static
BROADCAST=155.90.164.61
HWADDR=00:22:19:2C:2F:17
IPADDR=155.90.164.4
NETMASK=255.255.255.192
NETWORK=155.90.164.0
ONBOOT=yes
TYPE=Ethernet
VLAN=yes
Any ideas as to the issue ??
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2009 03:33 AM
05-01-2009 03:33 AM
Re: vlan tagging issue
Shalom,
In this context you may need a GATEWAY statement in each VLAN.
Nothing stands out in the configuration files.
There may be an external issue preventing communication with the VLAN.
you might want to run tcpdump or wireshark on another host to see if you can detect the packets moving across the lan.
SEP
In this context you may need a GATEWAY statement in each VLAN.
Nothing stands out in the configuration files.
There may be an external issue preventing communication with the VLAN.
you might want to run tcpdump or wireshark on another host to see if you can detect the packets moving across the lan.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP