Auto-Port Aggregation w/ Cisco 6509 & Fast EtherChannel issue

[Pasha_2]

Hi,
We're running an rp8400 w/ 2 Copper Gigabit ethernet cards. The issue is that when we boot the system w/ the 2 ports on the switch channelized, the networking does not work properly.

However, if we channelize the ports on the switch AFTER the cards have initialized on the server, it works fine.

Any thoughts? I can provide more info if needed.

Thanks!

[Steven E. Protter]

Would be nice to know the OS and version.

Would be nice to know the part number on the cards.

Contents of config files would also help.

/etc/rc.config.d/netconf and hpbtlanconf

Try this anyway:

lanadmin -x #

replace # with tha actual lan number from ifconfig

Make sure the lanadmin output is what you expect, 1000 BaseT Full Duplex, whatever.

My understanding is that with Cisco in 100 BaseT mode you must not use autonegotiate on the switch port.

For 1000 BaseT speeds, you MUST use autonegotiate on the switch port.

check with your cisco guys and see what the settings are and if there are errors.

if you need to hard code settings /etc/rc.config.d/hpbtlanconf is the place to go for 100 BaseT cards,

There is a similarly named file for the 1000 BaseT cards.

SEP

[Pasha_2]

OS is HP-UX is 11.11
Part #'s are A6096-69001

When I try the lanconfig -x lan900, here are the results:

whatcom # ifconfig lan900
lan900: flags=1843
inet 159.1.251.130 netmask ffffff00 broadcast 159.1.251.255
whatcom # lanadmin -x lan900
Invalid PPA Number entry
whatcom # exit

script done on Mon Jun 16 10:13:54 2003
-----------------------------------------

I've attatched a text file w/ both config files.

The switch guy says that the ports are set to Full, No-Auto. So we'll give that a shot when we can.

Any other ideas would be very helpful. Would like to do as much as I can to get it to work correctly when we attempt this again.

Thanks!

[Steven E. Protter]

take out the lan part in the lanadmin command

example

lanadmin -x 0

Checking the config files.

Will get back to you if time permits.

SEP

[Pasha_2]

it must have been a while since i did this last...if i do a

lanadmin -x 900
it says its expecting more options...

so i tried w/ the ppa

lanadmin -x 4

and i got nothing but a prompt back.

[James A. Donovan]

What's the output of lanscan say?
Any error messages in your /etc/rc.log file?

[Pasha_2]

lanscan output:

Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
LinkAgg0 0x00306E28581D 900 UP lan900 snap900 4 ETHER Yes 119
LinkAgg1 0x000000000000 901 DOWN lan901 snap901 5 ETHER Yes 119
LinkAgg2 0x000000000000 902 DOWN lan902 snap902 6 ETHER Yes 119
LinkAgg3 0x000000000000 903 DOWN lan903 snap903 7 ETHER Yes 119
LinkAgg4 0x000000000000 904 DOWN lan904 snap904 8 ETHER Yes 119


rc.log output:

Configure HP AUTO-PORT AGGREGATION interfaces
Output from "/sbin/rc2.d/S337hpapa start":
----------------------------
DLPI version is 2
/sbin/rc2.d/S337hpapa started.
Please be patient. This may take about 40 seconds.
HP_APA_MAX_LINKAGGS = 50
HP_APA_DEFAULT_PORT_MODE = MANUAL
/usr/sbin/hp_apa_util -S 0 FEC_MANUAL
/usr/sbin/lanadmin -X -g 0 3 900
New Group Capability = 3
/usr/sbin/hp_apa_util -S 1 FEC_MANUAL
/usr/sbin/lanadmin -X -g 1 3 900
New Group Capability = 3
lan900
/usr/sbin/lanadmin -X -g 900 3 900
New Group Capability = 3
/usr/sbin/lanadmin -X -a 0 1 900
Added ports:0 1 to lan900
/sbin/rc2.d/S337hpapa Completed successfully.

Configure LAN interfaces
Output from "/sbin/rc2.d/S340net start":
----------------------------

Configure Auto-Port Aggregation(LAN Monitor) interfaces
Output from "/sbin/rc2.d/S343hplm start":
----------------------------
DLPI version is 2
/sbin/rc2.d/S343hplm started.
/etc/lanmon/lanconfig.ascii not present on the system.
lanapplyconf will not be executed
/sbin/rc2.d/S343hplm Completed successfully.

[James A. Donovan]

The output of lanscan and rc.log looks good. My guess is that once you change the switch to autonegotiate your problem will go away.

[rick jones]

If I were to guess... given that life is good if you activeate the aggregate after boot, but not during boot, and ginve that mention of "this may take 40 seconds" in some of the rc output...

...perhaps the link aggregate is not fully "up" by the time the ifconfig commands start happening?

...it is though just a wild guess... i'm not sure how one might go about adding a delay to test the hypothesis. it would probably involve hacking the startup scripts, which might not be strictly kosher done in the field by customers so I cannot suggest it directly... :)