Routing anomalous between VLAN

[Visconti]

You can not understand why a PC (IP 192.168.10.130) of a vlan31 pings another PC (IP 192.168.4.66) of a vlan40

We all have enterasys switches series B5 and extreme networks and in theory there is one of these switches that acts as a routing but if I analyze the configuration of the switch I don't detect connection between the different vlan ...

the section of the routing configuration file of the routing switch 10.254 it's the following:

#vlan

set vlan create 30

set vlan create 31

set vlan create 40

set vlan create 50

set vlan name 30 "VL-AUTOMAZIONE-PLC-AQ"

set vlan name 31 "VL-AUTOMAZIONE-MGT"

set vlan name 40 "VL-AUTOMAZIONE-PC-AQ"

set vlan name 50 "VL-BADGE-AQ"

clear vlan egress 1 ge.1.1-44

set vlan egress 30 ge.1.45-48 tagged

set vlan egress 30 ge.1.1-22 untagged

set vlan egress 31 ge.1.45-48 tagged

set vlan egress 40 ge.1.45-48 tagged

set vlan egress 40 ge.1.23-44 untagged

set vlan egress 50 ge.1.45-48 tagged

set host vlan 31

!


#Router Configuration

router

enable

configure

interface vlan 30

ip address 192.168.0.254 255.255.255.0

no shutdown

exit

interface vlan 31

ip address 192.168.10.254 255.255.255.0

no shutdown

exit

interface vlan 40

ip address 192.168.2.254 255.255.255.0

ip address 192.168.4.254 255.255.255.0 secondary

ip address 192.168.6.254 255.255.255.0 secondary

no shutdown

exit

interface vlan 50

ip address 192.168.50.254 255.255.255.0

no shutdown

exit

exit

[Tomasz]

Hi Visconti,

If I understand your question, when you set up routing interfaces on a 'switch' (we should say 'router' at this point  ), it will route between those interfaces without hesitation. There is no need to 'connect' those interfaces, router will have all directly connected networks (VLANs with IP addresses that are up, i.e. at least one interface in that VLAN is active) in its routing table so it can route. You could limit that with Policy on B5 or Policy/ACL on EXOS.

Hope that helps,
Tomasz