ok Adding the Vlan didnt seem to do it but once I added it to a port as
access on the main switch everything came to life
On 4/12/2017 1:21 PM, Eric Muehleisen wrote:
You may have to add it to the VLAN global config.
switch(config)# vlan 1066
switch(config-vlan)# name my_vlan_description
On Wed, Apr 12, 2017 at 1:03 PM, Cassidy B. Larson <[email protected]
<mailto:[email protected]>> wrote:
check your spanning-tree for that VLAN on both switches.
# sho spanning-tree vlan 1066
Gotta make sure it’s also created on the 2nd switch, but the above
command will clue you into that if there isnt any spanning tree
instances for that VLAN.
> On Apr 12, 2017, at 11:51 AM, Dave <[email protected]
<mailto:[email protected]>> wrote:
>
> Ok,
> I am not sure where I went wrong but I have 2 vlans coming over
a trunk to another switch
> I configured both trunk interfaces on each switch to allow the 2
vlans I need.
> I configure 2 ports 1 with each access to the vlans I need to
have access to.
>
> one vlan passes with no issue and the other will not pass
traffic at all. VLAN1066 is the one with issue.
> The other switch has the same trunk config on its interface with
another trunk port to the router.
>
>
> here is a partial config of the main switch
> lan internal allocation policy ascending
> !
> vlan 2,10,28,50,106,1000,1066,1100
> !
> !
> !
> interface FastEthernet0/1
> switchport access vlan 1066
> switchport mode access
> !
> interface FastEthernet0/2
> switchport access vlan 1100
> switchport mode dynamic desirable
> !
> interface GigabitEthernet0/2
> switchport trunk encapsulation dot1q
> switchport trunk allowed vlan 1,1000,1066,1100
> switchport mode trunk
> !
>
>
> Here is the main switch to router
> !
> interface GigabitEthernet1/0/1
> switchport trunk encapsulation dot1q
> switchport trunk allowed vlan
1000,1001,1066,1100,2000,2001,2400,2801,2825
> switchport trunk allowed vlan add 3065
> switchport mode trunk
> !
>
> Any ideas or guidance would be great
>
>
> --
> <Vcard.jpg>
--
