03-23-2005 03:13 AM - edited 03-02-2019 10:14 PM
We have a Main Campus and a Remote Site approx 400 meters apart.
Previously the Remote Site was linked by a wireless connection and shared a common LAN with the Main Campus. Servers at the Main Campus provide DNS, DHCP, Email, Internet & data storage to clients depending VLAN membership configured on a Cisco 3550 Layer 3 switch.. The Cisco 3550 is the gateway to all services provided by the servers. A network of layer 2 switches connected clients to the Cisco 3550.
Last week we leased a fiber cable channel to replace the Wireless Link that connected the 2 sites. The channel service provider has cabinets at the Main Campus and Remote Site with a Cisco 1601 Router in each one (Router A & Router B). The Routers have serial connection to fiber cable.
At the Main Campus Router A is connected via Ethernet0 10.2.0.249/16 to the Cisco 3550 Layer 3 switch that has VLANs and provides access to Main Servers. Serial0 192.168.15.253/30 is connected to the fiber cable via a MUX HDLC is encapsulated on Serial 0, RIP is enabled. Both interfaces are up
At the remote site Router B is connected via Ethernet0 10.3.0.254/16 D-Link Layer 2 switch. Serial 0 192.168.15.254/30 is connected to the fiber cable via a MUX - HDLC is encapsulated on Serial0, RIP is enabled. Both interfaces are up
This is where my problem lies:
All clients at the Remote site share the VLAN 200 subnet 10.2.0.0/16 range with clients and services at the Main Campus. The Routed link has effectively split the VLAN and stopped the clients at the Remote Site from accessing services.
Can anyone advise what the best solutions is?
Do I need to put a layer 3 switch at the remote site?
Do I need to set the Routers up to Bridge? If so how do I do this?
Any other ideas?
Thanks
03-29-2005 07:37 AM
I would suggest to go for a layer 3 switch at the remote site
03-29-2005 08:12 AM
Are you saying that the clients at the remote site can't access services or the nodes period on the main site VLAN?
Can you post your output from "show ip route" on the two routers?
Scott
03-29-2005 03:27 PM
03-30-2005 12:42 AM
This might be a long shot but try this.
Change the IP address on the Ethernet interface on the remote router (router b). You have the address in the 10.3.0.0 /16 subnet with the VLAN on the switch in the 10.2.0.0 /16 subnet. Put the ethernet interface on the remote router in the 10.2.0.0 /16 subnet and it should communicate with the 10.2.0.0 /16 subnet devices.
Let me know if this helps
Scott
03-30-2005 03:05 AM
Scott,
In that case he has to configure NAT overlapping on either of the router otherwise it will not work. The best possible way for this would be changing the clients on the remote router to 10.3.0.0 subnet and this will work perfectly.
This is not working because the Layer 3 interface for 10.2.0.0 is not defined on the router, so it will not route the packet through that ethernet interface.
HTH
Amit Singh
03-30-2005 07:34 AM
Amit,
Thank you for the clarification.
Scott
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide