cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
8134
Views
0
Helpful
6
Replies

Allowed vlan on trunk are not allowed and active in managemant domain

BinodAyer
Level 1
Level 1

I've created certain vlans and allowed them on trunk but not all the allowed vlans are shown in 'vlans allowed and active in management domain' list because of which I cannot ping the different devices connected to different switch but which are in the same vlan. From below information I am only able to ping the devices within the vlans that are in the list of allowed and active vlans in management domain. What is the reason and how can I communicate with all the devices of respective vlans that are allowed on trunk? Below is 'show interface trunk' result.

 

 

SW-1#sh int trunk

 

Port Mode Encapsulation Status Native vlan

Fa0/2 on 802.1q trunking 1

Fa0/3 on 802.1q trunking 1

 

Port Vlans allowed on trunk

Fa0/2 10,20,30,40,99

Fa0/3 10,20,30,40,50,99

 

Port Vlans allowed and active in management domain

Fa0/2 10,40,99

Fa0/3 10,40,50,99

 

Port Vlans in spanning tree forwarding state and not pruned

Fa0/2 10,40,99

Fa0/3 10,40,50,99

1 Accepted Solution

Accepted Solutions

Thank you for the output that I requested. I notice these things in the output:

- output of show vlan does not have any mention of vlan 20 and 30

- output of show interface status does not show any port assigned to either 20 or 30

- output of show ip interface brief does not show any mention of vlan 20 or 30.

These show that the issue seems to be that vlan 20 and 30 have not been correctly configured and no ports assigned to either vlan.

HTH

Rick

View solution in original post

6 Replies 6

Giuseppe Larosa
Hall of Fame
Hall of Fame

Hello @BinodAyer ,

which switch model is involved ?

and what is the IOS or IOS XE version ?

 

How you have created the new Vlans?

If your switch is in VTP server mode or in VTP transparent mode you should be able to create new Vlans.

However, some low end switches have an upper limit on the number of concurrent Vlans that can exist in the Vlan database.

 

in addition to

show version

post

show vlan

 

and check the state of each Vlans. if the new Vlans are not listed or they listed as inactive you may have a scalability issue.

 

Hope to help

Giuseppe

 

Richard Burts
Hall of Fame
Hall of Fame

In looking at what you have posted it looks like the issue is with vlans 20 and 30. To help us understand the issue would you post the output of these commands

show vlan

show interface status

show ip interface brief

HTH

Rick

Yes, here are the commands and their outputs:

 

SW-1>sh vlan

 

VLAN Name Status Ports

---- -------------------------------- --------- -------------------------------

1 default active Fa0/6, Fa0/7, Fa0/8, Fa0/9

Fa0/10, Fa0/11, Fa0/12, Fa0/13

Fa0/14, Fa0/15, Fa0/16, Fa0/17

Fa0/18, Fa0/19, Fa0/20, Fa0/21

Fa0/22, Fa0/23, Fa0/24, Gig0/1

Gig0/2

10 Sales active Fa0/1

40 IT active Fa0/4

50 Support active Fa0/5

99 Mgmt active

1002 fddi-default active

1003 token-ring-default active

1004 fddinet-default active

1005 trnet-default active

 

VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2

---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------

1 enet 100001 1500 - - - - - 0 0

10 enet 100010 1500 - - - - - 0 0

40 enet 100040 1500 - - - - - 0 0

50 enet 100050 1500 - - - - - 0 0

99 enet 100099 1500 - - - - - 0 0

1002 fddi 101002 1500 - - - - - 0 0

1003 tr 101003 1500 - - - - - 0 0

1004 fdnet 101004 1500 - - - ieee - 0 0

1005 trnet 101005 1500 - - - ibm - 0 0

 

VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2

---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------

 

Remote SPAN VLANs

------------------------------------------------------------------------------

 

Primary Secondary Type Ports

------- --------- ----------------- ------------------------------------------

 

 

SW-1#sh int status

Port Name Status Vlan Duplex Speed Type

Fa0/1 connected 10 auto auto 10/100BaseTX

Fa0/2 connected 1 auto auto 10/100BaseTX

Fa0/3 connected 1 auto auto 10/100BaseTX

Fa0/4 connected 40 auto auto 10/100BaseTX

Fa0/5 connected 50 auto auto 10/100BaseTX

Fa0/6 notconnect 1 auto auto 10/100BaseTX

Fa0/7 notconnect 1 auto auto 10/100BaseTX

Fa0/8 notconnect 1 auto auto 10/100BaseTX

Fa0/9 notconnect 1 auto auto 10/100BaseTX

Fa0/10 notconnect 1 auto auto 10/100BaseTX

Fa0/11 notconnect 1 auto auto 10/100BaseTX

Fa0/12 notconnect 1 auto auto 10/100BaseTX

Fa0/13 notconnect 1 auto auto 10/100BaseTX

Fa0/14 notconnect 1 auto auto 10/100BaseTX

Fa0/15 notconnect 1 auto auto 10/100BaseTX

Fa0/16 notconnect 1 auto auto 10/100BaseTX

Fa0/17 notconnect 1 auto auto 10/100BaseTX

Fa0/18 notconnect 1 auto auto 10/100BaseTX

Fa0/19 notconnect 1 auto auto 10/100BaseTX

Fa0/20 notconnect 1 auto auto 10/100BaseTX

Fa0/21 notconnect 1 auto auto 10/100BaseTX

Fa0/22 notconnect 1 auto auto 10/100BaseTX

Fa0/23 notconnect 1 auto auto 10/100BaseTX

Fa0/24 notconnect 1 auto auto 10/100BaseTX

Gig0/1 notconnect 1 auto auto 10/100BaseTX

Gig0/2 notconnect 1 auto auto 10/100BaseTX

 

 

SW-1#sh ip int brief

Interface IP-Address OK? Method Status Protocol

FastEthernet0/1 unassigned YES manual up up

FastEthernet0/2 unassigned YES manual up up

FastEthernet0/3 unassigned YES manual up up

FastEthernet0/4 unassigned YES manual up up

FastEthernet0/5 unassigned YES manual up up

FastEthernet0/6 unassigned YES manual down down

FastEthernet0/7 unassigned YES manual down down

FastEthernet0/8 unassigned YES manual down down

FastEthernet0/9 unassigned YES manual down down

FastEthernet0/10 unassigned YES manual down down

FastEthernet0/11 unassigned YES manual down down

FastEthernet0/12 unassigned YES manual down down

FastEthernet0/13 unassigned YES manual down down

FastEthernet0/14 unassigned YES manual down down

FastEthernet0/15 unassigned YES manual down down

FastEthernet0/16 unassigned YES manual down down

FastEthernet0/17 unassigned YES manual down down

FastEthernet0/18 unassigned YES manual down down

FastEthernet0/19 unassigned YES manual down down

FastEthernet0/20 unassigned YES manual down down

FastEthernet0/21 unassigned YES manual down down

FastEthernet0/22 unassigned YES manual down down

FastEthernet0/23 unassigned YES manual down down

FastEthernet0/24 unassigned YES manual down down

GigabitEthernet0/1 unassigned YES manual down down

GigabitEthernet0/2 unassigned YES manual down down

Vlan1 unassigned YES manual administratively down down

Vlan99 192.168.99.1 YES manual up up

Thank you for the output that I requested. I notice these things in the output:

- output of show vlan does not have any mention of vlan 20 and 30

- output of show interface status does not show any port assigned to either 20 or 30

- output of show ip interface brief does not show any mention of vlan 20 or 30.

These show that the issue seems to be that vlan 20 and 30 have not been correctly configured and no ports assigned to either vlan.

HTH

Rick

Well, thank you so much for your time. Actually, my issue is solved. It was a silly mistake to not allow vlans in trunk port.

please would you provide me the command helps you to fix the issue, as I faced the same issue?

Review Cisco Networking for a $25 gift card