alleforums
Technical User
Hello,
I have a machine with Solaris 8, and it has multiple interfaces that are connected to the same network which means they all have metric 0 (1 hop) to the default gateway.
assume:
e1000g0 - 10.1.1.70
e1000g2 - 10.1.1.72
e1000g4 - 10.1.1.74
e1000g5 - 10.1.1.76
gateway - 10.1.1.65 (Cisco Router)
However, it seems like despite the fact that they have a direct connection, they seem to be using e1000g0 as their gateway interface to access the 10.1.1.0 network to get to the gateway and then to anywhere else.
This gets even more confusing when I go into the Cisco router and run the command: "show mac address-table" where only the MAC address of e1000g0 is shown for the switch port it's connected to, but not for the other interfaces which are connected to the switch. Yes, all ports are active (no shut) and are pingable.
The routing table inside the machine also looks good and clearly shows each interface itself being the gateway to the 10.1.1.0 network.
When I send a ping to say, 10.1.1.74 (IP of e1000g4) and capture packets on e1000g0, I see the "echo reply" messages going out of it as well as e1000g4. This should not happen and these should be completely independent.
How can I make sure that when the internal software of this machine specifically sends something out of interface e1000g4, it goes directly out of that interface to the 10.1.1.0 network, through the 10.1.1.65 gateway and out into the world?
I need to somehow assign all these interfaces equal priority and make them understand that they're physically connected to the 10.1.1.0 network and there's no need to go through e1000g0 to get to it.
This is causing a lot of problems as eventually all traffic will end up going through the e1000g0 interface and that will become a bottle neck.
Please help
Thanks in advance
I have a machine with Solaris 8, and it has multiple interfaces that are connected to the same network which means they all have metric 0 (1 hop) to the default gateway.
assume:
e1000g0 - 10.1.1.70
e1000g2 - 10.1.1.72
e1000g4 - 10.1.1.74
e1000g5 - 10.1.1.76
gateway - 10.1.1.65 (Cisco Router)
However, it seems like despite the fact that they have a direct connection, they seem to be using e1000g0 as their gateway interface to access the 10.1.1.0 network to get to the gateway and then to anywhere else.
This gets even more confusing when I go into the Cisco router and run the command: "show mac address-table" where only the MAC address of e1000g0 is shown for the switch port it's connected to, but not for the other interfaces which are connected to the switch. Yes, all ports are active (no shut) and are pingable.
The routing table inside the machine also looks good and clearly shows each interface itself being the gateway to the 10.1.1.0 network.
When I send a ping to say, 10.1.1.74 (IP of e1000g4) and capture packets on e1000g0, I see the "echo reply" messages going out of it as well as e1000g4. This should not happen and these should be completely independent.
How can I make sure that when the internal software of this machine specifically sends something out of interface e1000g4, it goes directly out of that interface to the 10.1.1.0 network, through the 10.1.1.65 gateway and out into the world?
I need to somehow assign all these interfaces equal priority and make them understand that they're physically connected to the 10.1.1.0 network and there's no need to go through e1000g0 to get to it.
This is causing a lot of problems as eventually all traffic will end up going through the e1000g0 interface and that will become a bottle neck.
Please help
Thanks in advance
