Are the switches in vtp and are they vtp client or vtp transparent ? Ive seen an issue before where when you have 3 switches in a line defining vlans manually outside of vtp traffic wont pass.
In that instance we had to make the middle switch a vtp client. Odd but true... Sent from Samsung Mobile -------- Original message -------- From: Joseph Mays <[email protected]> Date: 11/09/2013 17:50 (GMT+00:00) To: [email protected] Subject: Re: [c-nsp] VLAN Trunking Question > * Have you defined the vlans? Yes, they are defined in both the vlan database and the config on all the switches. > * Why have a dirty net and have all vlans tagged on all ports, and not only > on the ports you want them on? At the moment I’m just trying to make it work. If I don’t specifically allow certain vlans on the trunk then (my understanding is) all the vlans should be allowed and passed by the trunk by default. I thought that should work. If and when it does, I intend to lock it down so only vlan 808 is allowed on the trunk. But there is not much point in applying filters to a trunk that is not working even when it’s wide open. From: Peter Persson Sent: Tuesday, September 10, 2013 6:21 PM To: Joseph Mays Subject: Re: [c-nsp] VLAN Trunking Question Hey, This would be right. But i got a few questions. * Have you defined the vlans? * Why have a dirty net and have all vlans tagged on all ports, and not only on the ports you want them on? /Peter 2013/9/10 Joseph Mays <[email protected]> Okay, so I am trying to set up a single VLAN to go through a series of catalyst switches. What I need, effectively, is one long ethernet connection between two routers. I thought this should work but since it is not, clearly, I've fundamentally misunderstood something. Cisco 7206A(vlan 808 subinterface)>>--<<(vlan trunk Fe0/1)CatalystA(vlan trunk FE0/10)>>-... ...-<<(vlan trunk FE0/4)CatalystB(vlan trunk FE0/1)>>--<<(vlan trunk FE0/17)CatalystC(vlan trunk FE0/1)>>-... ...-<<(vlan 808 subinterface)Cisco 7206B The configs on each port, for the curious. Cisco 7206 A interface FastEthernet1/0.808 description HN-808 interconnect to armplc via sw1.armplc encapsulation dot1Q 808 ip address 216.24.2.202 255.255.255.252 Catalyst A interface FastEthernet0/1 description to gw1.armplc duplex full speed 100 switchport trunk encapsulation dot1q switchport mode trunk no cdp enable interface FastEthernet0/10 description Hatteras 1 - HN408-U switchport trunk encapsulation dot1q switchport mode trunk no cdp enable Catalyst B interface FastEthernet0/4 description HN-808 interconnect to Armory Place switchport trunk encapsulation dot1q switchport mode trunk interface FastEthernet0/1 description 802.1q trunk to core-sw1.noc (Heyburn 911) FE0/17 load-interval 30 duplex full speed 100 switchport trunk encapsulation dot1q switchport mode trunk Catalyst C interface FastEthernet0/17 description 802.1q trunk to core-sw3.noc.win.net (in Heyburn 513) FastEthernet0/0 load-interval 30 duplex full speed 100 switchport trunk encapsulation dot1q switchport mode trunk no cdp enable interface FastEthernet0/1 description 802.1q trunk to core-gw1.noc.win.net port FastEthernet0/0 load-interval 30 duplex full speed 100 switchport trunk encapsulation dot1q switchport mode trunk no cdp enable Cisco 7206 B interface FastEthernet0/0.808 description HN-808 interconnect to armplc via core-sw3 encapsulation dot1Q 808 ip address 216.24.2.201 255.255.255.252 no cdp enable _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
