HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- vlan tagging with bonding not reaching gateway
Operating System - Linux
1827889
Members
1620
Online
109969
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
01-28-2011 07:04 AM
01-28-2011 07:04 AM
vlan tagging with bonding not reaching gateway
I have a DL380 G5 running RHEL5.3. I have two NICs that are bonded and want to use vlan tagging. i have my network-scripts set up for bond0. for both vlans and I can ping the devices but it fails when I try to ping the gateway. I can only access this via the ILO so cutting and pasting output is not possible(unless you can tell me how to do so). i can retype info if needed. thanks.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2011 07:27 AM
01-31-2011 07:27 AM
Re: vlan tagging with bonding not reaching gateway
output of ifconfig -a:
bond0
link encap:ethernet hwaddr 00:23:7d:e5:cb:a6
inet addr:10.142.61.30 bcast 10.142.61.255 mask:255.255.255.0
up broadcast running master multicast mtu:1500 metric:1
rx packets:8482 errors:0 dropped:0 overruns:0 frame:0
tx packets:828 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
rx bytes:609338 (595.0 kib) tx bytes:52992 (51.7 kib)
bond0.171
link encap:ethernet hwaddr 00:23:7d:e5:cb:a6
inet addr:10.142.61.30 bcast 10.142.61.255 mask:255.255.255.0
up broadcast running master multicast mtu:1500 metric:1
rx packets:4239 errors:0 dropped:0 overruns:0 frame:0
tx packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
rx bytes:211275 (206.3 kib) tx bytes:252 (252.0 b)
bond0.2205
link encap:ethernet hwaddr 00:23:7d:e5:cb:a6
inet addr:192.168.1.211 bcast 192.168.1.255 mask:255.255.255.0
up broadcast running master multicast mtu:1500 metric:1
rx packets:0 errors:0 dropped:0 overruns:0 frame:0
tx packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
rx bytes:0 (0.0 kib) tx bytes:252 (252.0 b)
eth0
link encap:ethernet hwaddr 00:23:7d:e5:cb:a6
up broadcast running slave multicast mtu:1500 metric:1
rx packets:4238 errors:0 dropped:0 overruns:0 frame:0
tx packets:828 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
rx bytes:304465 (297.3 kib) tx bytes:52992 (51.7 kb)
interrupt:169 memory:f8000000-f8012100
eth1
link encap:ethernet hwaddr 00:23:7d:e5:cb:a6
up broadcast running slave multicast mtu:1500 metric:1
rx packets:7190 errors:0 dropped:0 overruns:0 frame:0
tx packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
rx bytes:507580 (495.6 kib) tx bytes:0 (0 kb)
interrupt:177 memory:fa000000-fa012100
lo
link encap:local loopback
inet addr:127.0.0.1 mask:255.0.0.0
up loopback running mtu:16436 metric:1
rx packets:1567 errors:0 dropped:0 overruns:0 frame:0
tx packets:1567 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
rx bytes:262313 (256.1 kib) tx bytes:262313 (256.1 kb)
I don't know why both eth0 and eth1 have the same mac address. I tried hardcoding it in the network-scripts/ifcfg-ethX but it won't take.
output from netstat -rn:
destination gateway genmask flags mss window irtt iface
192.168.1.0 0.0.0.0 255.255.255.0 u 0 0 0 bond0.2205
10.142.61.0 0.0.0.0 255.255.255.0 u 0 0 0 bond0
10.142.61.0 0.0.0.0 255.255.255.0 u 0 0 0 bond0.171
169.254.0.0 0.0.0.0 255.255.0.0 u 0 0 0 bond0.2205
0.0.0.0 10.142.61.1 0.0.0.0 ug 0 0 0 bond0
Unfortunately I can't access any switch settings. Out network dept handles that and I was assured that they have it set up correctly.
Is there anything that stands out as being wrong? or does it look right and does in fact need to be checked on the switch side?
thanks.
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP