- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Broadcom BCM 5722 don't ping the gateway
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
тАО01-17-2010 04:16 AM
тАО01-17-2010 04:16 AM
Broadcom BCM 5722 don't ping the gateway
I have a Proliant DL 120 G5 with CentOS 5.4 and I have installed a Brodcom Corporation Netxtrem BCM 5722 Gigabit Ethernet PCI.
So I have two interfaces:
eth0 broadcom
eth1 Intel
The eth1 works, instead eth0 don't work.
I can ping itself and 127.0.0.1 but I can't ping the gateway.
What could be the problem?
Thankx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2010 04:26 AM
тАО01-17-2010 04:26 AM
Re: Broadcom BCM 5722 don't ping the gateway
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2010 12:14 AM
тАО01-18-2010 12:14 AM
Re: Broadcom BCM 5722 don't ping the gateway
I show you the results of the command that you ask me.
[root@serverhost ~]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:26:55:57:B1:AF
inet addr:192.168.0.205 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::226:55ff:fe57:b1af/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:646 errors:0 dropped:0 overruns:0 frame:0
TX packets:236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:193781 (189.2 KiB) TX bytes:23686 (23.1 KiB)
Interrupt:177
[root@serverhost ~]# mii-diag eth0
Basic registers of MII PHY #1: 1000 796d 0143 bed0 05e1 45e1 0065 2001.
The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
Basic mode control register 0x1000: Auto-negotiation enabled.
You have link beat, and everything is working OK.
Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT, w/ 802.3X flow control.
End of basic transceiver information.
[root@serverhost ~]# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Current message level: 0x000000ff (255)
Link detected: yes
[root@serverhost ~]# netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.87.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.60.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 192.168.0.133 0.0.0.0 UG 0 0 0 eth0
[root@serverhost ~]# ping 192.168.0.133
PING 192.168.0.133 (192.168.0.133) 56(84) bytes of data.
From 192.168.0.205 icmp_seq=10 Destination Host Unreachable
From 192.168.0.205 icmp_seq=11 Destination Host Unreachable
From 192.168.0.205 icmp_seq=12 Destination Host Unreachable
From 192.168.0.205 icmp_seq=14 Destination Host Unreachable
From 192.168.0.205 icmp_seq=15 Destination Host Unreachable
From 192.168.0.205 icmp_seq=16 Destination Host Unreachable
--- 192.168.0.133 ping statistics ---
17 packets transmitted, 0 received, +6 errors, 100% packet loss, time 15998ms
, pipe 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2010 01:29 AM
тАО01-18-2010 01:29 AM
Re: Broadcom BCM 5722 don't ping the gateway
eth0 intel
eth1: device eht1 has a MAC address different from the expected, operation ignored.
Now it doesn't work anything..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2010 08:14 AM
тАО01-18-2010 08:14 AM
Re: Broadcom BCM 5722 don't ping the gateway
The two nics were exchanged...
And the subnet for the two interfaces must be different..