To accomplish this type of routing, you would configure an IP address for each VLAN on the 6024. This would be the gateway address for the clients/servers. The 5324 and 5212 would then trunk the VLANs on the uplink to the 6024.
Example:
6024 Config:
console(config)# interface vlan 2
console(config-if)# ip address 192.168.2.1 /24
console(config-if)# exit
console(config)# interface vlan 3
console(config-if)# ip address 192.168.3.1 /24
console(config-if)# exit
console(config)# interface vlan 4
console(config-if)# ip address 192.168.4.1 /24
console(config)# interface ethernet g1 (uplink to the 5212)
Thanks for the reply. I already have the switches setup this way. All Vlans have IP address on the 6024. All PCs/Servers are able to communicate with eachother. I can ping back and forth. Browse to them using their UNC but when I try to use Network Neighborhood I can only see what is on the same subnet. All servers can only see the servers, all pcs can only see the pcs.
Network Neighborhood uses NetBIOS, which uses broadcast traffic. By default, broadcasts do not cross routers. You would need to use the "helper-address" command to forward NetBIOS traffic. See the following link to the online CLI Guide for more information:
The helper-address command should be used to forward the broadcasts from one network to the address of the server providing the service on another network.
GregG1
2 Intern
•
812 Posts
0
November 12th, 2004 12:00
Danks
8 Posts
0
November 12th, 2004 16:00
Greg,
Thanks for the reply. I already have the switches setup this way. All Vlans have IP address on the 6024. All PCs/Servers are able to communicate with eachother. I can ping back and forth. Browse to them using their UNC but when I try to use Network Neighborhood I can only see what is on the same subnet. All servers can only see the servers, all pcs can only see the pcs.
J
GregG1
2 Intern
•
812 Posts
0
November 12th, 2004 17:00
Danks
8 Posts
0
November 12th, 2004 18:00
GregG1
2 Intern
•
812 Posts
0
November 15th, 2004 11:00