Unable to communicate outside of subnet on VLAN

[Mike Whorley]

Hi Guys,

I'm new to VLANS but have had to use one for an Ianium Blade server running 11.31.

After much digging i established how to set up the VLAN and have a virtual nic LAN5000. The server can ping other servers, resolve names etc but cannot communicate with any servers on another subnet.

Is there anything specific in the VLAN config i need to do allow traffic to pass to & from other subnets ?

Here's some output that may be out use :-

# nwmgr

Name/ Interface Station Sub- Interface Related
ClassInstance State Address system Type Interface
============== ========= ============== ======== ============== =========
lan2 UP 0x001E0BFCCE02 igelan 1000Base-SX
lan0 UP 0x001E0BFCCE04 igelan 1000Base-SX
lan5000 UP 0x001E0BFCCE04 vlan vlan lan0
lan1 UP 0x001E0BFCCE05 igelan 1000Base-SX
lan3 UP 0x001E0BFCCE03 igelan 1000Base-SX
lan900 DOWN 0x000000000000 hp_apa hp_apa
lan901 DOWN 0x000000000000 hp_apa hp_apa
lan902 DOWN 0x000000000000 hp_apa hp_apa
lan903 DOWN 0x000000000000 hp_apa hp_apa
lan904 DOWN 0x000000000000 hp_apa hp_apa

# ifconfig lan5000
lan5000: flags=4000000000001843
inet 10.2.65.113 netmask fffffc00 broadcast 10.2.67.255

# lanadmin -x 1
Speed = 1000 Full-Duplex.
Autonegotiation = On.

# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/2/2/0 0x001E0BFCCE02 2 UP lan2 snap2 1 ETHER Yes 119
0/1/1/0 0x001E0BFCCE04 0 UP lan0 snap0 2 ETHER Yes 119
VLAN5000 0x001E0BFCCE04 5000 UP lan5000 snap5000 56 ETHER Yes 119
0/1/1/1 0x001E0BFCCE05 1 UP lan1 snap1 3 ETHER Yes 119
0/2/2/1 0x001E0BFCCE03 3 UP lan3 snap3 4 ETHER Yes 119
LinkAgg0 0x000000000000 900 DOWN lan900 snap900 6 ETHER Yes 119
LinkAgg1 0x000000000000 901 DOWN lan901 snap901 7 ETHER Yes 119
LinkAgg2 0x000000000000 902 DOWN lan902 snap902 8 ETHER Yes 119
LinkAgg3 0x000000000000 903 DOWN lan903 snap903 9 ETHER Yes 119
LinkAgg4 0x000000000000 904 DOWN lan904 snap904 10 ETHER Yes 119

Many thanks
Mike.

[Eric SAUBIGNAC]

Bonjour Mike,

what about routing (netstat -rn) ?

Eric

[Mike Whorley]

Thanks Eric - I was checking routing myself when your reply came through and I believe you are correct. If looks like the default route I added might be the problem. I've just forced it to be correct in netconf (didn't know how to manually remove a default root) and rebooted so lets see if that does the trick.

Isn't it always the case when you work with a new technology that by default you assume that is where the problems lies...

I'll update when the server comes back if it was routing.

tia,
Mike.

[Mike Whorley]

It was a routing problem - thanks for pointing me in the correct direction.