ethernet parameters configuration

[Jimmy_13]

What are the parameters that manage relay, windows size, timeout, etc in the hp-ux 11i?
I need the parameters that manage the ethernet packet only (ethernet protocol)
What i can modify this parameters.

Thanks

[Michael Steele_2]

Sounds like you have the opposites for another O/S. Could you provide this? Thanks!

[Paulo A G Fessel]

I think this will depend wildly on the hardware that you have.

Anyway, my guess is that you're talking about Solaris, which defines a complete set of variables for lan boards (i.e., /dev/hme, /dev/qfe, /dev/ge and so on). I've checked ndd for HP-UX, and it seems not to have these capabilities.

In HP-uX, you should use landamin, but I'm not certain that you can configure the ethernet drivers at this level of detail.

HTH
Paulo Fessel

[Jimmy_13]

I have problems with the comunications from a Hp-ux 11i to a S/390 (Operating System = VSE ). Sometimes i have time out in the ftp.

But Only i have problems whith the S/390.

The S/390 administrator give me this parameters from VSE:


s-Inactivity timer (Ti) ----------> 30.00 seconds
s-Response timer (T1) ------------> 2.00 seconds
s-Acknowledgement timer (T2) -----> 0.08 seconds
s-Max I frames before ack (N3) ---> 1
s-Maximum transmit window (TW) ---> 8

This parameters are from data link layer (ethernet protocol).
I would like chek the parmeters in the hp-ux similar to mainframe.

I check mi network and i think that is fine.

Do you know the ethernet parameters?

Thanks

[Steven E. Protter]

I don't think its parameter per say.

I think you control this stuff with the ndd command. There are a lot of options, and that's where I'd look first.

SEP

[Paulo A G Fessel]

Jimmy,

I would check first whether there are media layer errors before trying to change these parameters. You can do this with lanadmin:

* start lanadmin.
* select "lan" option.
* select the instance you want to inspect with "ppa". Choose 0 for lan0, 1 for lan1, etc...
* select display and check statistics for this board. Even if you have any errors or collisions, make sure that speed and duplex parameters of your board are correct. A 100BT configured for autonegotiation will hardly talk to any partner that has 100FD (Full Duplex) hardwired.
* If there are mismatches on speed/duplexing configuration, you can change these values through SAM.
* If you don't have any errors then your problem is not in the media layer, and then you can think about modifying parameters with ndd /dev/ip and ndd /dev/tcp.

Don't forget to assign the points!

HTH
Paulo Fessel

[Michael Steele_2]

Refer to the 'ndd' and 'ifconfig' commands. You can up/down a lan or plumb/unplumb a lan with 'ifconfig' and 'ndd' has some disabling arguements that will down the network if a condition is detected. '-h' for help.

ndd -h supported
ndd -h unsupported

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90129/B2355-90129_top.html&con=/hpux/onlinedocs/B2355-90129/00/02/209-con.html&toc=/hpux/onlinedocs/B2355-90129/00/02/209-toc.html&searchterms=parameter%7cndd&queryid=20030728-183915

[Paulo A G Fessel]

Michael,

If you take a look into ndd, you'll see that the only devices it accepts are /dev/ip, /dev/tcp, /dev/udp and /dev/arp.

Therefore it can't be used to modify ethernet settings. In Solaris there IS /dev/hme, /dev/qfe, /dev/ge - all of them are hardware devices. But AFAIT they don't exist on HP-UX, or aren't manageable through ndd.

Just my .02
Paulo Fessel

[Ron Kinner]

There is a config file for each driver where you can set a few parameters like the duplex. Something like:

/etc/rc.config.d/hpbtlanconf

but it is pretty limited. Most of the other stuff you mention in your first post is done in ndd.

I would suggest you get tcpdump and analyze the actual traffic to see what is going wrong. It's very unlikely that it is an Ehternet problem unless you need a newer driver. You might want to go to

http://www1.itrc.hp.com/service/patch/search.do?pageContextName=hpux:::

and search for patches for your driver and for ARPA.

Note there are a few NICs used by HP which are known to be EMI sensitive and these are just not trustworthy for data transfers. What NIC are you using?

Ron