1833750 Members
2471 Online
110063 Solutions
New Discussion

Re: LAN problem

 
Ron Irving
Trusted Contributor

Re: LAN problem

Here's the ioscan
Should have been an astronaut.
G V R Shankar
Valued Contributor

Re: LAN problem

Please give me the o/p of lanscan -q and lanadmin -x for (both the interfaces) in lan900

Ravi.
Ron Irving
Trusted Contributor

Re: LAN problem

Hi!! Here's the lanscan -q. Bear in mind we only have 1 lan there until we get the speed sorted out.
Should have been an astronaut.
Ron Irving
Trusted Contributor

Re: LAN problem

and here's the lanadmin -x
Should have been an astronaut.
G V R Shankar
Valued Contributor

Re: LAN problem

Hi,

I am unable to open both the atatchments. Could you please paste the o/p in thread.

Cheers,
Ravi.
Ron Irving
Trusted Contributor

Re: LAN problem

lanadmin -x 1

Speed = 100 Full-Duplex.
Autonegotiation = On.

lanscan -q 1

0
3
4
2
5
900 1
901
902
903
904
Should have been an astronaut.
G V R Shankar
Valued Contributor

Re: LAN problem

hi,

Following are the next steps.

ll /var/adm/net*

If the file (files) have the latest timestamp, run the following command. You can replace the file name if it is diferent.

netfmt -t 5 -f /var/adm/nettl.LOG000

If you see any speed mismatches, take your N/W admin to task.

Initiate a scp or ftp of atleast 100 MB file and make a note of the time.

Change the speed to 1000FD manually.

lanadmin -X 1000FD 1

update /etc/rc.config.d/hpietherconf and upadte lan1 details.

Check the speed

lanadmin -x 1

Initiate a scp and ftp and make a note of the time.

Monitor netstat -ni for 1 hour and see for collisions.

If you see collisions (we see sollisions, if it is HD), tell your network admin the proof taht it has been set to 1000FD auto neg on.

Cheers,

Ravi.
Ron Irving
Trusted Contributor

Re: LAN problem

I tried to change the speed, as you suggested, and I get

The option "1000fd" is not valid
Should have been an astronaut.

Re: LAN problem

Why can't folks read posts before replying?

Pete quite correctly said the following:

> > I belive if you turn off auto negotiation and set it to full duplex FD. This will work perfectly.
>
> In a work: No.
>
> This is not how GB ether works. It is designed to be set to auto-negotiate. Forcing either end of the connection as suggested is how you end up with a situation like Ron is in.

And then Ravi suggests:

> Change the speed to 1000FD manually.
>
> lanadmin -X 1000FD 1

And (unsurprisingly) Ron finds:

> I tried to change the speed, as you suggested, and I get
>
> The option "1000fd" is not valid

If your network switch is *really* set to 1000BaseT & AUTO and you definately have at least CAT5e cable (ideally CAT6), and your end is also set to AUTO, then everything should work...

Confirm everyting is set to auto again and then try resetting the card through lanadmin - that should force a re-negotation with the switch.

One minor point - you mention you cloned from an older system using Ignite - you don't have any hard-coded MAC addresses in your /etc/rc.config/* files that have been carried over from the old box do you?

HTH

Duncan

I am an HPE Employee
Accept or Kudo
Mel Burslan
Honored Contributor

Re: LAN problem

Just curious, do you have a reasonable explanation why you have an aggregate interface (lan900) with a single interface in it, which is lan1 ?

If not, try dissolving the APA interface and then stop and restart your networking, or better, completely power off the server and power it back on to clear possibly hanging register values on the network interface.

I am sorry to say but HP's way of handling the network cards, port aggregation and other aspects leave a lot to be desired. On AIX for instance (which I find myself moving towards lately) you can actually set the interfaces to 1000FD fixed speed/duplex setting, unlike HP. If this functionality was available on HPUX, that would be a great troubleshooting tool if nothing else.

Anyway, just try this and see what happens. If you can not dissolve lan900, at least connect the cable to another lan port, which still is independent, say maybe lan2, and see if you get what you want on that port.

Hope this helps
________________________________
UNIX because I majored in cryptology...
Ron Irving
Trusted Contributor

Re: LAN problem

Good question, Duncan...however, I do not have an easy answer to it. Is there a way to check that wouldn't ivolve me 'cat'ing out each file in the /etc/rc.config.d directory?

thx
Should have been an astronaut.
Ron Irving
Trusted Contributor

Re: LAN problem

Mel,

It only has 1 lan connected as APA would not let me add a lan to the aggregate at a different speed. Kind of like Murphy's law here.

I just passed a maintenance wknd, where I was trying to resolve this issue, but the window ran out before I could come up with an answer. Sigh.
Should have been an astronaut.
Ron Irving
Trusted Contributor

Re: LAN problem

I think I've given out almost as many points as I have myself...keep them answers coming!!

You guys are ALL an indespensable assett!!
Should have been an astronaut.
Pete Randall
Outstanding Contributor

Re: LAN problem

> Good question, Duncan...however, I do not have an easy answer to it. Is there a way to check that wouldn't ivolve me 'cat'ing out each file in the /etc/rc.config.d directory?

Ron - try "grep -l STATION /etc/rc.config.d/hp*conf". That will show you which files will be checked - should be six, I think. Then run "grep STATION /etc/rc.config.d/hp*conf" to see if there are any that aren't blank.


Pete

Pete
Ron Irving
Trusted Contributor

Re: LAN problem

ok...ran it through, and they're all blank.
Should have been an astronaut.
Ron Irving
Trusted Contributor

Re: LAN problem

Now what?
Should have been an astronaut.

Re: LAN problem

going back to Pete's post about being totally sure the network guys are looking at the right thing... when this has happened to me before I get the MAC address of my lan card, then go sit at the network admins desk and get him to log into the switch in question, find the port in question, confirm it sees my MAC adress and then eye-balled his AUTO setting with my own eyes... you'd be surprised the number of times it turned out he was looking at the wrong port...

one more comment - him having his end set to AUTO ain't gonna help if the port on the switch will only go to 100BaseT - everyone has confirmed that this is a 1000BaseT (GbE) capable switch port right?

HTH

Duncan

I am an HPE Employee
Accept or Kudo
Mel Burslan
Honored Contributor

Re: LAN problem

I second Duncan's point. 99% of the time I have a suspicious network problem, it turs out to be something network administrators have done in bulk causing all the headache. Make sure that they can see your MAC accross from the switch port that they are claiming to be set to 1000 AutoNeg.

Also, in your answer to my question above, you said, APA can not be formed because speeds of the two interfaces are not the same. So, from this statement, I understand that the other member of this APA interface, (switch port wise) is already set to 1000 Auto and working fine. If this is a valid assumption, the simplest test would be to disconnect lan1 and connect the cable from the secondary network adapter into the lan1 and see if it alleviates the problem. Since the two ports should be on the same network and everything, you should not have any IP address conflict because of the wrong subnets. I am hoping this server with lost redundancy and operating at a much slower network rate than it is designed for, is not in production in its current shape, so maintenance window should not be a problem. But if so, there is not much you can do until you get yourself a few minutes of maintenance time here and there to test these cable swap game.

Good luck
________________________________
UNIX because I majored in cryptology...
Andrew Rutter
Honored Contributor

Re: LAN problem

hi,

I encountered a similar problem, which after weeks of going through everything possible to think of, and a 500mile round trip to prove to the customer that the cable was the only thing left to try.
I was lucky the server had 2 gbit cards in it, so a quick cable between the two proved they were ok to run at 1000

network guys provided reluctently to prove the cisco switch was at auto, everything configured ok.

cat5 cable was just that cat5 not cat5e or cat6!

I would physically check the cable, and what is written on it.

Andy
Tingli
Esteemed Contributor

Re: LAN problem

I remember a couple of days ago someone mentioned that when using GigaNic card, the system should be set to auto-neg while the Cisco box should set to 1 gig and auto should be off. Also, in your network configuration file, the speed should be blank while the auto-neg should be set to on.

For that case, you might need to check the network collision. If there are many collisions, then the setting is wrong.
Patrick Wallek
Honored Contributor

Re: LAN problem

>>I remember a couple of days ago someone >>mentioned that when using GigaNic card, the >>system should be set to auto-neg

TRUE

>>while the Cisco box should set to 1 gig and
>>auto should be off.

FALSE.

The switch should also be set to AUTO.

For Gigabit speeds to work properly, BOTH ends MUST be set to AUTO!
Torsten.
Acclaimed Contributor

Re: LAN problem

I'm quite sure your problem is somewhere around the APA configuration.

What is in
/etc/rc.config.d/hp_apaconf
/etc/rc.config.d/hp_apaportconf
/etc/lanmon/lanconfig.ascii ?

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Ron Irving
Trusted Contributor

Re: LAN problem

Here's the hp_apaconf. There is no /etc/lanmon/lanconfig.asci...only the .sample.
Should have been an astronaut.
Ron Irving
Trusted Contributor

Re: LAN problem

and here's the hp_apaportconf.
Should have been an astronaut.
Ron Irving
Trusted Contributor

Re: LAN problem

So...has anyone come up with the BIG answer yet?

thx!!
Should have been an astronaut.