Just want to make sure, in your lacp commands you reference ports ge.3.35 & 
ge.3.45 but in your VLAN egress statement you reference ge.3.36 & ge.3.46.  
Hopefully, this is just a typo.

Jay
________________________________________
From: Nick Allen [[email protected]]
Sent: Thursday, December 23, 2010 1:33 PM
To: Enterasys Customer Mailing List
Subject: [enterasys] HP NIC Teaming...

Hi guys,

Hopefully a very basic question for someone.

With HP NIC Teaming on Windows 2008 R2, we've been advised that "Switch 
assisted load balancing with fault tolerance (SLB)" is the best option for a 
NIC team connected to an Enterasys C2G stack, provided we manually create the 
LAG.

I've created the LAG as follows:

set lacp aadminkey lag.0.2 102
set port lacp port ge.3.35 aadminkey 102
set port lacp port ge.3.45 aadminkey 102

I've done quite a few switch-to-switch LAG's so am familiar with seeing entries 
under "Attached ports" when the LAG is active but this one shows none:

================================================
C2Stack(su)->show lacp lag.0.2
Global Link Aggregation state: enabled
Single Port LAGs:              disabled

Aggregator: lag.0.2
                         Actor                  Partner
System Identifier:     00:11:88:64:7F:AA    18:A9:05:60:FA:10
  System Priority:                 32768                32768
        Admin Key:                   102
         Oper Key:                   102                  768
   Attached Ports:     None.
C2Stack(su)->

================================================

The partner Mac address is the Mac address of the Team, but the question is - 
should I be seeing ge.3.35 and ge.3.45 as "Attached Ports:" if it's functioning 
correctly?

These ports are in VLAN 100 by the way, so I've also made sure the same VLAN 
can egress the lag:

set vlan egress 100 ge.1.36-46;lag.0.2 untagged

Thanks,

Nick.


--
This e-mail is intended only for the named person or entity to which it is 
addressed and
contains valuable business information that is proprietary, privileged, 
confidential and/or
otherwise protected from disclosure. If you received this e-mail in error, any 
review, use,
dissemination, distribution or copying of this e-mail is strictly prohibited. 
Please notify
us immediately of the error via e-mail to [email protected] and 
please delete
the e-mail from your system, retaining no copies in any media. We appreciate 
your cooperation.






 *    --To unsubscribe from enterasys, send email to 
[email protected]<mailto:[email protected]> with the body: unsubscribe enterasys 
[email protected]




---
To unsubscribe from enterasys, send email to [email protected] with the body: 
unsubscribe enterasys [email protected]

Reply via email to