Separate VTP domains. Will they still pass traffic ?

Hello,

We have a need to connect a large customer of ours to our core network.*

Obviously we do not want to use the same VTP domain as this customer or share VTP information. I realise that not using the same VTP domain as our customers will prevent sharing of VTP information, but will traffic still be passed between VLANs with the same name/id ? e.g We want traffic on VLAN 23 on our network to be passed over our trunk link to the customer. Documentation I have found doesn't explain the above clearly:

i.e. VTP will not share VTP information between different domains. But will traffic still be passed between different domains over trunk links ?

* We are using transparent LAN over cable, so we need the customer cable modem VLANs to be visible to the customer's core network.

Re: Separate VTP domains. Will they still pass traffic ?

Yes, hopefully you will be able to transmit traffic between two different VTP domain. It's only VTP operation that will be segmented at the boundary.

The only minor problem that you could experience is that I don't think there will be trunking negotiation between different VTP domains (i.e. DTP will not automatically form a trunk at the boundary). You will thus need to statically configure your trunks.

Re: Separate VTP domains. Will they still pass traffic ?

Hi Francois,

Thank you very much for the reply. I just have an additional question in regards to static trunking setup. We are using a 3550, will the below be enough for static trunking configuration from our side of the link ?:

Re: Separate VTP domains. Will they still pass traffic ?

Hi Friend,

Yes the config is perfect but I will also recommend you to configure the interface to stop sending DTP packets.

Use the "switchport nonegotiate" interface configuration command to specify that Dynamic Trunking Protocol (DTP) negotiation packets are not sent on the Layer 2 interface. The switch does not engage in DTP negotiation on this interface

The ProblemEnter EVCsHow It Works (Ingress)How It Works
(Egress)Step-by-Step ExampleFinal Thoughts The ProblemOn traditional
switches whenever we have a trunk interface we use the VLAN tag to
demultiplex the VLANs. The switch needs to determine which MAC ...
view more

The ProblemEnter EVCsHow It Works (Ingress)How It Works
(Egress)Step-by-Step ExampleFinal Thoughts Introduction: Netdr is a tool
available on a RSP720, Sup720 or Sup32 that allows one to capture
packets on the RP or SP inband. The netdr command can be use...
view more

IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...
view more