Hello,
I am new at this and hope someone can give me a pointer for this problem.
I have 2 switches: Alcatel 7700 o/s V5 Alcatel 6850 o/s v6
There are 3 VLANs total with 2 VLANs that span both switches.
The switches are interconnected through VLAN A and VLAN B interfaces.
VLANs with there IP interfaces on the switches are as follows:
7700:
VLAN A: 10.10.1.1/16
VLAN B: 10.20.1.1/16
6850:
VLAN A: 10.10.1.2/16
VLAN B: 10.20.1.2/16
VLAN C: 10.30.1.1/16
RIP is enabled on both switches.
Local routes redistributed into RIP on both switches.
RIP is updating the tables.
No other advanced routing protocols in use.
No VLAN rules in use.
The client on VLAN C on the 6850 (10.30.1.100) can ping the VLAN interface for VLAN A (10.10.1.1) on 7700 but cannot ping server on 7700 at 10.10.2.1/16 and vice versa.
I can hit the last VLAN interface before either individual host, just not host to host.
There are NO hardware or software firewalls.
If I telnet into either switch, I can ping everywhere.
Thanks for any input.
2 Switch client to client VLAN porblem
what are the def. GW of the client and server?
Both switches have interfaces in vlan A and B. No good idea in routed network.... so for both vlans the same switch has to be the def. GW for clients/server and at the connection between the switches you have to activate both vlans (802.1q).
output the following:
show vlan port
show ip route
show ip rip route
silvio
Both switches have interfaces in vlan A and B. No good idea in routed network.... so for both vlans the same switch has to be the def. GW for clients/server and at the connection between the switches you have to activate both vlans (802.1q).
output the following:
show vlan port
show ip route
show ip rip route
silvio
-
Elmo
That's it!
Hello Silvio,
Thank you for your quick response.
It was the Server Gateway that was bad.
Thought I had checked them all but it was the one server GW that was wrong. It was set up for communication through a different switch. Initially I checked every GW on all the other devices, just not this server - what a dumb mistake.
There are other hosts on the system but the ones mentioned are the main concern.
This setup is a Lab test phase for a larger production deployment.
Unfortunately we have to have the VLAN multiple interface structure on the switches - A pre-existing customer condition that we can not change.
Our clients on VLAN C have to authenicate to VLAN A or B.
Thank you very much for your time and help.
elmo
Thank you for your quick response.
It was the Server Gateway that was bad.
Thought I had checked them all but it was the one server GW that was wrong. It was set up for communication through a different switch. Initially I checked every GW on all the other devices, just not this server - what a dumb mistake.
There are other hosts on the system but the ones mentioned are the main concern.
This setup is a Lab test phase for a larger production deployment.
Unfortunately we have to have the VLAN multiple interface structure on the switches - A pre-existing customer condition that we can not change.
Our clients on VLAN C have to authenicate to VLAN A or B.
Thank you very much for your time and help.
elmo
