1849239
Members
2930
Online
104042
Solutions
SOLVED
Being able to put an IP on an interface and ping it procvs nothing beyond physical connectivity.
So you have lan1 and lan3 on the same VLAN yes?
First off you might want to check link level connectivity between lan 1 and lan3.
Get the MAC address for lan3 from lanscan and then try a link level connection using:
linkloop -i 1
I suspect that won't worth either though.
The other point to consider is "how is your VLAN tagging done in your network?" Most network admins tag based on the port on the switch (i.e. if you plug into port 4 you're in VLAN 2 or whatever), but it is also possible to tag packets on a specific VLAN based on what protocol they use (IP, IPX LLC etc.), and even what source IP subnet they use. If you use either of these 2 mechanisms in your network, you'll realise that link-level packets that come from an interface with no IP address are not going to get tagged as being on the correct VLAN and won't find thir way to the other ports in the VLAN.
If this is the case you have 2 choices:
1) Talk to your network team and get them to give you a port based VLAN for lan1 and lan3 on all 4 servers.
2) Configure VLAN tagging on the hosts by creating a virtual interface which tags packets into the correct VLAN before they leave the host. You'll need to know the numeric ID of the VLAN from your network admin and then use either nwmgr or lanadmin (depending on whether you are on 11iv3 or 11iv2) to setup the VLAN. Manuals are here:
http://docs.hp.com/en/netcom.html#Virtual%20LAN
... or of course you could have some other sort of network problem entirely - but this is my guess for your problem.
HTH
Duncan
I am an HPE Employee
So you have lan1 and lan3 on the same VLAN yes?
First off you might want to check link level connectivity between lan 1 and lan3.
Get the MAC address for lan3 from lanscan and then try a link level connection using:
linkloop -i 1
I suspect that won't worth either though.
The other point to consider is "how is your VLAN tagging done in your network?" Most network admins tag based on the port on the switch (i.e. if you plug into port 4 you're in VLAN 2 or whatever), but it is also possible to tag packets on a specific VLAN based on what protocol they use (IP, IPX LLC etc.), and even what source IP subnet they use. If you use either of these 2 mechanisms in your network, you'll realise that link-level packets that come from an interface with no IP address are not going to get tagged as being on the correct VLAN and won't find thir way to the other ports in the VLAN.
If this is the case you have 2 choices:
1) Talk to your network team and get them to give you a port based VLAN for lan1 and lan3 on all 4 servers.
2) Configure VLAN tagging on the hosts by creating a virtual interface which tags packets into the correct VLAN before they leave the host. You'll need to know the numeric ID of the VLAN from your network admin and then use either nwmgr or lanadmin (depending on whether you are on 11iv3 or 11iv2) to setup the VLAN. Manuals are here:
http://docs.hp.com/en/netcom.html#Virtual%20LAN
... or of course you could have some other sort of network problem entirely - but this is my guess for your problem.
HTH
Duncan
I am an HPE Employee
>> but my network team ignored this and connect to lan1 service laptop network links works OK
And presumably that service laptop had an IP address in the 148.1.0.0 subnet? That of course would work if you're doing protocol or subnet based VLAN tagging.
Another point to check is that your NIC is negotiating to a suitable speed with the switch... check using "landamin -x 1"
HTH
Duncan
I am an HPE Employee
Which shows that those interfaces with an IP address on are able to link to another host... again I susepct this s down to how your VLAN is configured in your network. Ask your network admin what "type" of VLAN membership they have configured - the following might help you understand the different types:
http://nislab.bu.edu/nislab/education/sc441/six/VLAN%20types.htm
HTH
Duncan
I am an HPE Employee
http://nislab.bu.edu/nislab/education/sc441/six/VLAN%20types.htm
HTH
Duncan
I am an HPE Employee