getting configuration of a APA device

[Jdamian]

My system uses APA (Auto Agregation Port) to join two lan interfaces.

APA creates several agregated lan devices (LinkAgg0, LinkAgg1, ...) and new PPA numbers, as you can see below:

1/12/0/0 0x001083F64DC7 2 UP lan2 snap2 7 ETHER Yes 119
LinkAgg0 0x001083F62D87 100 UP lan100 snap100 9 ETHER Yes 119
LinkAgg1 0x000000000000 101 DOWN lan101 snap101 10 ETHER Yes 119
LinkAgg2 0x000000000000 102 DOWN lan102 snap102 11 ETHER Yes 119
LinkAgg3 0x000000000000 103 DOWN lan103 snap103 12 ETHER Yes 119
LinkAgg4 0x000000000000 104 DOWN lan104 snap104 13 ETHER Yes 119

The problem is the "lanadmin" command reports an error message when the PPA of an APA devs is used:

$ lanadmin -x 100
Expected "-" before the sub-option.

Note that if the PPA number belongs to an non-APA dev it runs fine:

$ lanadmin -x 2
Current Speed = 100 Full-Duplex Auto-Negotiation-OFF

Why does lanadmin not run on a APA dev ?

[John Poff · Accepted solution]

Hello,

Try it this way. Do a 'lanscan -q' to get a list of how the individual cards have been group by APA, and then do 'lanadmin -x PPA' for the individual cards. For example, on my box using APA my lanscan -q returns:

2
100 1 6
101 0 5


So I can do:

lanadmin -x 1
lanadmin -x 6

to see the settings for the two cards that make up lan100.


JP

[John Poff]

And to answer your question (someday I gotta learn to read the whole question!), the 'lanadmin' command just works on an actual PPA number. The lan100, lan101, etc. are created by APA grouping physical cards together. I don't think APA will work if the individual cards are set to different speeds/duplexes, so you have to get that part right before APA will combine them, and so you just look at the individual cards.

JP

[Sridhar Bhaskarla]

The standard lanadmin commands do not work on APA devices.

There are sub commands to -X and -x for APA devices. For ex

lanadmin -x -m APA_NO gives the status.

-Sri