VLAN/IPRouting Question

[JohnPtrs]

If I have multiple vlans configured on a switch with iprouting enabled is it necessary to apply all vlans to a port before they will work properly??

Because I have a weird situation going on here with a switch that has a vlan with an IP address assigned to it and I can ping IP addresses on that vlan however the vlan is not yet applied to any particular interface... I wondered if iprouting being enabled had anything to do with that... it seemed like it shouldn't be able to do that...

Thanks in advance...
-JP

 

[burtsbees]

The vlan that has the IP address assigned to it is probably the management vlan, and by default it (and all other ports) belong to VLAN 1, unless otherwise configured. So it actually does belong to a vlan.
You can verify this by
switch#sh vlan

Burt

 

[Minue]

Hello
That Vlan could be acting as the layer 3 management Vlan,or it's trunking.Can you post a show conf.
Regards

 

[burtsbees]

I would also say to post a sh vlan

Burt

 

[JohnPtrs]

Vlan 62 is the one in question-

interface Vlan62
description firewall
ip address 192.168.62.1 255.255.255.0


Here is the config of the port that it is physically plugged into- I went there this morning to verify so I think it is misconfigured... Just not sure why then I can still ping the 192.168.62.254 address but there is a web app that goes over that route that isn't working... I think I should apply vlan62 to that port...

interface GigabitEthernet0/5
description pc + phone
switchport access vlan 126
switchport mode access


Here is show vlan-
WS-132-S1#sho vlan

VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Gi0/52
10 VLAN0010 active Gi0/41, Gi0/47, Gi0/48
62 VLAN0062 active
116 VLAN0116 active Gi0/42
126 VLAN0126 active Gi0/5, Gi0/6, Gi0/7, Gi0/8, Gi0/9, Gi0/10, Gi0/11, Gi0/12, Gi0/13
Gi0/14, Gi0/15, Gi0/16, Gi0/17, Gi0/18, Gi0/19, Gi0/20, Gi0/21
Gi0/22, Gi0/23, Gi0/24, Gi0/25, Gi0/26, Gi0/27, Gi0/28, Gi0/29
Gi0/30, Gi0/31, Gi0/32, Gi0/33, Gi0/34, Gi0/35, Gi0/36, Gi0/37
Gi0/38, Gi0/39, Gi0/40
180 VLAN0180 active
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
10 enet 100010 1500 - - - - - 0 0
62 enet 100062 1500 - - - - - 0 0
116 enet 100116 1500 - - - - - 0 0
126 enet 100126 1500 - - - - - 0 0
180 enet 100180 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
------- --------- ----------------- ------------------------------------------

WS-132-S1#

 

[JohnPtrs]

I made a mistake... this is the config for the port the device is plugged into not Gi0/5

interface GigabitEthernet0/3
description firewall
switchport trunk encapsulation dot1q
switchport trunk native vlan 62
switchport trunk allowed vlan 1,62,126,180
switchport mode trunk
service-policy input voip-policy

 

[Minue]

Hello
The VLAN 62 is acting as a layer 3 virtual interface.It doesn't have to be associated with a port.If you have a trunk port configured on the switch.The other device can speak with it if they have the same VLAN and subnet.It was confusing to me as well,when I first got into layer 3 switching.
Regards

 

[JohnPtrs]

Thanks for the help... problem solved... it turned out to be a misconfigured route statement on another device on the WAN... I appreciate your time...

-JP