Quantcast
Viewing all articles
Browse latest Browse all 2954

62xx - routing or vlan config error ?

hi,

I have 4 vlans and a number of hosts connected to it - and one oddity, well, it boggles my mind and I cannot see - most likely obvious - reason for this weird situation.

Very last Vlan I created for the moment has no connections to any port, but! - as soon as any one member port goes up - physical link on - then one of the hosts/nodes becomes unavailable to some some part of the network, let me call it hostXX

Vlans:

1        vlan 1          192.168.2.1      255.255.255.0  

2        vlan 2          192.168.3.1      255.255.255.0  

3        vlan 3          172.25.12.201    255.255.255.0  # here is Vlan which when a port is active then ...

4        vlan 4          10.5.6.1         255.255.255.0  

and that hostXX's routing:

Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

0.0.0.0         10.5.6.1        0.0.0.0         UG    100    0        0 p3p1

0.0.0.0         192.168.2.100   0.0.0.0         UG    110    0        0 em2

0.0.0.0         131.111.42.62   0.0.0.0         UG    199    0        0 em3

one difference between hostXX and other hosts which remain accessible & unaffected is, other hosts have:

Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

0.0.0.0         192.168.2.100   0.0.0.0         UG    100    0        0 enp2s0f0

That 192.168.2.100 gateway is a host(not the switch) that connects to external Intranet and switch's 192.168.2.0/24 is the Default Vlan as above.

My wild guess is that hostXX's gateway - 10.5.6.1 is switch's Vlan 4 - being first on kernel routing list, does not do something to manage that traffic from hostXX's 10.5.6.100.

But why would this only happen when there is a link on any member port of Vlan 3 and problem does not exist when no port is active/connected?

many thanks.


Viewing all articles
Browse latest Browse all 2954

Trending Articles