Quote:
Originally Posted by zohar123
Hi
I am trying to communicate with laptop via IP switch or even directly to the management port of Linux server without success,
|
I think you mean an
Ethernet switch.
Quote:
there is no Ping reply.
The IP manag. port of the server has configured before with success, shipped to other location and not communicate.
Connecting console and using the following command:
> ifconfig bond0
return back the known good IP manag. port, Bcast 0.0.0.0
|
Give us a little more information. See Eric Raymond's "how to ask questions the smart way", in particular
the part about being precise and informative.
There are many reasons why you can't access a network interface. A few ideas:
- Cable not plugged in or broken.
- You are using the wrong IP address.
- Subnet misconfiguration (wrong netmask or prefix).
- Firewalls.
- VLAN misconfiguration on the server or the switch.
Your description contains gaps. I assume but am not certain:
- By "management port" you mean a port that allows managing the server when the operating system is down
- The laptop can connect to other devices on the same subnet but not the server's management port
- The laptop can connect to the server itself but not its management port
- No other device on the subnet can connect to the management port
Can you confirm that?
Also, as a minimum, tell us your operating systems and what server this is (
see again Eric Raymond's article).
I also wonder how you can "see" the management port via
ifconfig. It should normally not be visible from the operating system.
Finally, you seem to be using a bond. Could it be that the switch can't deal with bonds? Can you undo the bond and try again?
I consider it unlikely, by the way, that your management processor has two NICs that can be bonded.