Integration between two entities having different Core switches

[LMAZ]

Edited For explanation:

Hi , We were trying to integrate two entity having different Core switches at both sites. Demo Network Diagram Attached.

The vlans for site A is as vlan 10,20,30 with intervlan routing enabled and have there default route to internet router.

Site B with Vlan 40,50,60 with intervlan routing and default route to their internet router.

In order to create a link between these to sites a layer 2 trunk is created.

Issue is from site A server it cant reach site B server or vice-versa.

If i create a site B vlan as Layer three interface in Site A , i will be able to ping site B Switch from site A,  still Server will not be accessible.

Ex: In site A ,  Create SVI as 10.10.40.2 for vlan 40 , in Site B it will be 10.10.40.1 as SVI . Like that for all vlans.

Target is Site A server needs to be moved to Site B with same Site A IP address and it should take SITE A default route to internet for internet. And able to communicate with site B servers as well as Site A.

Tried layer 3 trunk also without success. Appreciate any community support. Thankyou.

[balaji.bandi]

Can you show us the example config and what results were not expected as per your expectation (can we have more details around to understand the problem)

[LMAZ]

Hi, thanks for the reply, please find the edited post explaining.

[balaji.bandi]

Ok good to see some diagram to understand -

High level

Ex: In site A ,  Create SVI as 10.10.40.2 for vlan 40 , in Site B it will be 10.10.40.1 as SVI . Like that for all vlans.

But you do not have vlans created same vlan bot the side as per your diagram. So you need  VLAN on Site A switch Site B Switch

2 Options

Option 1 :

1. 10.....60 VLAN need to exists both the sides.

2. in the Trunk have you allowed all vlan or only certain vlan ( if so you need to have 10...60 allowed both the side ) - list see the Trunk config.

3. ip routing enabled both the sides ?

Option 2 :

1. Instead of Trunk you can have point to point L3 interface.

2. check point to point interface able to ping each other.

3. for the Internal IP address from Site A  network reach to Site B make static route point towards Site B interface

4. Same from Site B pointing towards Site A .

hope this make sense ? if still have issue kindly post full config of Site A and Site B 3560 config to review.

[LMAZ]

Hi , I am following option A and all the three points are already done. Moved servers at site A, to B can reach site A and B servers as The gateway remains on site A only.

But the site B servers can't reach site A servers as its gateway is on site B. If we change the gateway of site B server to same svi subnet at site A , it is reachable. That was only for testing. Site B gateway we cant change in production.

[Georg Pauwen]

Hello,

on a side note, are you trying to do this in Packet Tracer, or is Packet Tracer just being used to show the topology ? If it is a PT project, post the project (.pkt) file...ZIP it first before uploading.

[FanuelMahembe]

Dear LMAZ

looks like there is no routing configured between the two sites. You can configure EIGRP between the two sites and you will be able to ping the two sites.

Regards,

[LMAZ]

We need to move servers from site A to site B with maintaining site A ip address and gateway. After which the moved servers must be reachable from site A and Site B.
The trunk link between two sites is layer 2.
We are able to reach  site A servers after it is moved to site B by creating same subnet svi at both ends.
Ex: vlan 1 svi at site A: 192.168.1.1
Vlan 1 svi at site B : 192.168.1.2
The gateway and ip address still will be of Site A,
In this way Site A servers now at site B can communicate with other Site A servers which is not moved and still at site A . 

But here the moved servers of site A now at site B can't communicate with the subnets of site B as the gateway is still of Site A. 

[Joseph W. Doherty]

At either site A or B (or some mixture), loop VLANs locally and they trunk just the far side across link bedtween between sites.

For example, at Site A define VLANs 40, 50, 60 and define one access port for each. Define an additional three access ports, one for VLANs 10, 20, and 30. Connect VLAN access port 10 to 40, 20 to 50, 30 to 60. Define your trunk to only send VLANs 40, 50 and 60.

NB: CDP will complain about VLAN mismatch on these eix access port. So, disable CDP on those ports.