Hi everyone. I have this Baystack, with the latest code, and I can't achieve any form of connectivity while I have two of the ports in trunk mode, and the ports are connected to an IBM RS/6000 with a 4-port NIC using EtherChannel or "Fat channel" or "Fat Ethernet, or something like that. I'm not the Unix admin and he's not present right now, but I've talked to him at length and he said it is setup right, and he even got IBM tech support to confirm that.
If I "un-trunk" the ports, I still cannot communicate with the server (4-port NIC setup to load balance using a single IP) regardless of which port I plug the cables into on the NIC.
However, while the ports are untrunked, if I plug one of the cables into a laptop, it gets an IP from our DHCP server no problem. Here is the interesting part. If I plug the laptop into one cable, while leaving the other cable plugged into the Server and assign the laptop the same IP as the server I get an IP conflict. Yet I cannot ping the server from any location (all local) or establish any other communication (of course this is when the laptop with the conflicting IP is taken offline).
I have called Nortel and am waiting for them to either get back to me with a resolution or bump me up to 2nd level support, and the guy I talked too said it is configured correctly. Assuming the IBM side is right as well, my gut feeling is telling me there is a compatibility issue. I've had similiar problems between switches.
Lastly, I have a 3 switch stack and I've tried trunking other ports on the same switch as well as the others and I get the exact same problem. With that said, we have others servers (Compaqs running Windows 2000) using trunked ports in these very switches working just fine.
Thanks for everyone's help.
If I "un-trunk" the ports, I still cannot communicate with the server (4-port NIC setup to load balance using a single IP) regardless of which port I plug the cables into on the NIC.
However, while the ports are untrunked, if I plug one of the cables into a laptop, it gets an IP from our DHCP server no problem. Here is the interesting part. If I plug the laptop into one cable, while leaving the other cable plugged into the Server and assign the laptop the same IP as the server I get an IP conflict. Yet I cannot ping the server from any location (all local) or establish any other communication (of course this is when the laptop with the conflicting IP is taken offline).
I have called Nortel and am waiting for them to either get back to me with a resolution or bump me up to 2nd level support, and the guy I talked too said it is configured correctly. Assuming the IBM side is right as well, my gut feeling is telling me there is a compatibility issue. I've had similiar problems between switches.
Lastly, I have a 3 switch stack and I've tried trunking other ports on the same switch as well as the others and I get the exact same problem. With that said, we have others servers (Compaqs running Windows 2000) using trunked ports in these very switches working just fine.
Thanks for everyone's help.
