Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

Different VTP domains...can do's and can't do's

I am trying to set the following VTP domains up and get them able to communicate and route.

I have a main site we will call main and it has a VTP domain called main. Next we have a site called DR and it has a VTP domain called DR.

Here are the VLANS defined in the VTP domain called main...

interface Vlan1

ip address 10.10.1.3 255.255.255.0

interface Vlan3

ip address 10.10.3.1 255.255.255.0

ip pim sparse-dense-mode

interface Vlan5

ip address 10.10.5.1 255.255.255.0

ip pim sparse-dense-mode

Here are the VLANS defined in the VTP domain called DR....

interface Vlan1

ip address 10.99.1.3 255.255.255.0

interface Vlan93

ip address 10.99.3.1 255.255.255.0

ip pim sparse-dense-mode

interface Vlan95

ip address 10.99.5.1 255.255.255.0

ip pim sparse-dense-mode

The switch that is in the DR VTP domain is a 3750 and has a trunked 802.1q connection to a 6509 in the main vtp domain. What I would like to be able to do is have a physical server at the DR site with an IP address of 10.99.3.3 and then have virtual servers on that box that have IP addresses in the main VTP domain such as 10.10.3.X and be able to communicate with both the VTP domains. Is this possible?

Thanks,

Mike

1 REPLY
New Member

Re: Different VTP domains...can do's and can't do's

VTP is Vlan Trunking Protocal - This is a management that allowed for the sharing of vlan information - Has nothing to do with Interface information. If you setup your Physical Server (with the Virtuals on it) as a trunk port, native vlan 93 since you want the physical server to have the IP address of 10.99.3.3. Then you would build you Viryual machine, give it the Ip address of 10.10.3.x with an 802.1q tag of 3. Since they are in differnet VTP domains, you might have to create the VLAN 3, but you would not have to create an interface for vlan 3. I think the switch would create vlan 3 automatically if it starts passing traffic for vlan 3. If you Physical server is not capable of being configured as a trunk, it will not work. It wont work because VLAN 93 does not know how to route Addresses int he subnet 10.10.3.x. I hope this makes sense and helps some.

122
Views
3
Helpful
1
Replies
CreatePlease to create content