Multiple VLAN issues

[jxande8]

I am setting up 3 switches in 3 locations that each need 6 ports in 4 different vlans excluding the native vlan. I have set up the ports as access ports in the 4 vlans (ie. vlan 100- ports 1-6, vlan 102- port 7-12, etc.) I have set up a gig ports as a dot1q trunk. These 3 switches connect to a central or "distribution" switch. This switch has the uplinks configured as dot1q trunks and also has 6 access ports for each vlan.
Here is the problem. I can ping anything from an access switch that is connected to the same vlan on the distribution switch. However, I cannot ping anything that is connected to 2 different access switches and has to go through the distribution switch.

Any ideas? Thanks in advance,
J

 

[chipk]

Please post your vlan configs from the central switch. Sounds like your inter-vlan routing might be the problem.

What kind of IP scheme are you using?

 

[jxande8]

Here is the scenario. I have 4 separate VOIP labs that I need to keep separated. I need to be able to display phones at 3 locations in the building from 4 different vendor types (Cisco Call Manager, Nortel BCM, AVAYA IP Office, and Siemens HiPath).

Each of these 3locations has a 356024PS-S with 6 access ports for each vlan of the 4 mentioned product lines. That gives 6 phones I can display of each product line at each location. These 3560s are trunked to a 35438XLEN. The trunk config is basic. Just switchport mode trunk and switchport trunk encapsulation dot1q. Vlans 100 (Cisco), 102 (Nortel), 104 (Avaya), 106 (Siemens) are configured on each switch.

The 3548 also has access ports for each product line configured for the Call control servers or devices needed. I have to keep each product line isolated with no intervlan routing because they have many common components that can't overlap (ie. DHCP server with Option 150 pointing to their own TFTP servers).
From the access port on my 3560, I can ping devices conntected to the 3548 that are on access ports in the same vlan. I cannot ping from an access port on 1 3560 to devices connected to another 3560 through the 3548 even if on access ports that are in the same vlan.
Is this a decent explanation? Is my only answer routing? I thought I may be able to have 4 separate vlans trunked through the 3548 and stick to layer 2!?!?!

 

[helpdeskdan]

I'd do a show vlan to make sure they are all then followed by a show trunk detail to make sure that the vlan's are being trunked correctly. Once you can ping within your own Vlan, we can look at routing issues.

 

[jxande8]

From the Distribution 3548:
DISTRIBUTION#sho vlan
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Fa0/25, Fa0/26, Fa0/27, Fa0/28,
Fa0/29, Fa0/30, Fa0/31, Fa0/32,
Fa0/33, Fa0/34, Fa0/35, Fa0/36,
Fa0/37, Fa0/38, Fa0/39, Fa0/40,
Fa0/41, Fa0/42, Fa0/43, Fa0/44,
Fa0/46, Fa0/47, Fa0/48, Gi0/1,
Gi0/2
100 CISCO active Fa0/1, Fa0/2, Fa0/3, Fa0/4,
Fa0/5, Fa0/6
102 NORTEL active Fa0/7, Fa0/8, Fa0/9, Fa0/10,
Fa0/11, Fa0/12
104 AVAYA active Fa0/13, Fa0/14, Fa0/15, Fa0/16,
Fa0/17, Fa0/18
106 SIEMENS active Fa0/19, Fa0/20, Fa0/21, Fa0/22,
Fa0/23, Fa0/24
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 - - - - - 1002 1003
100 enet 100100 1500 - - - - - 0 0
102 enet 100102 1500 - - - - - 0 0
104 enet 100104 1500 - - - - - 0 0
106 enet 100106 1500 - - - - - 0 0
1002 fddi 101002 1500 - - - - - 1 1003
1003 tr 101003 1500 1005 0 - - srb 1 1002
1004 fdnet 101004 1500 - - 1 ibm - 0 0
1005 trnet 101005 1500 - - 1 ibm - 0 0
DISTRIBUTION#
DISTRIBUTION#sho int f0/45 switchport
Name: Fa0/45
Switchport: Enabled
Administrative mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: Disabled
Access Mode VLAN: 0 ((Inactive))
Trunking Native Mode VLAN: 1 (default)
Trunking VLANs Enabled: 1,100,102,104,106,1002-1005
Trunking VLANs Active: 1,100,102,104,106
Pruning VLANs Enabled: 2-1001

Priority for untagged frames: 0
Override vlan tag priority: FALSE
Voice VLAN: none
Appliance trust: none
DISTRIBUTION#

From one of the 3560:
3560_2#sho vlan

VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Gi0/1
100 VLAN0100 active Fa0/1, Fa0/2, Fa0/3, Fa0/4
Fa0/5, Fa0/6
102 VLAN0102 active Fa0/7, Fa0/8, Fa0/9, Fa0/10
Fa0/11, Fa0/12
104 VLAN0104 active Fa0/13, Fa0/14, Fa0/15, Fa0/16
Fa0/17, Fa0/18
106 VLAN0106 active Fa0/19, Fa0/20, Fa0/21, Fa0/22
Fa0/23, Fa0/24
1002 fddi-default act/unsup
1003 token-ring-default act/unsup
1004 fddinet-default act/unsup
1005 trnet-default act/unsup

VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
1 enet 100001 1500 - - - - - 0 0
100 enet 100100 1500 - - - - - 0 0
102 enet 100102 1500 - - - - - 0 0
104 enet 100104 1500 - - - - - 0 0

VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
106 enet 100106 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

Remote SPAN VLANs
------------------------------------------------------------------------------


Primary Secondary Type Ports
------- --------- ----------------- ------------------------------------------

3560_2#
3560_2#sho int g0/2 trunk

Port Mode Encapsulation Status Native vlan
Gi0/2 on 802.1q trunking 1

Port Vlans allowed on trunk
Gi0/2 1,100,102,104,106

Port Vlans allowed and active in management domain
Gi0/2 1,100,102,104,106

Port Vlans in spanning tree forwarding state and not pruned
Gi0/2 1,100,102,104,106
3560_2#

 

[chipk]

Ah, I misunderstood what the problem was. Good call helpdeskdan.

 

[helpdeskdan]

Is it like this on every switch hooked to Distribution? The vlans are there, so that's not the problem. Do you have any VACL or port ACL's configured? Chip, you got any ideas?

 

[jxande8]

Nope. No restrictions. I think it may be the IOS on the 3548. It is "3500XL-c3h2s-mz-120-5.3.WC.1.bin"
For some reason the 3548 will only sees one vlan interface up/up and puts the other vlan interfaces in admin down status and with a "no shut" it still shows them admin down. It does however show the vlans as active. I may try a newer switch for the distribution switch.

 

[helpdeskdan]

Do you have your vlans configured as interfaces? Make sure they aren't svi's on the 3548. Just off the top of my head, that might work.