[119603] in North American Network Operators' Group
Re: OT: VSS + MEC - port-channel dynamically cloned?
daemon@ATHENA.MIT.EDU (Ross Vandegrift)
Tue Nov 24 17:57:53 2009
From: Ross Vandegrift <ross@kallisti.us>
Date: Tue, 24 Nov 2009 17:54:52 -0500
To: Leland Vandervort <leland@taranta.discpro.org>
In-Reply-To: <1259097573.5897.2.camel@leland-laptop>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--J2SCkAp4GZ/dPZZf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Nov 24, 2009 at 10:19:33PM +0100, Leland Vandervort wrote:
> In this case, though I cannot see where the mismatch is given that the
> encapsulation, trunking (vlans allowed, etc.) and channel mode (LACP)
> are all configured identically across all ports and the channel itself.
>=20
> Just wondering if it's a left-over from before the VSS migration when
> the original trunks were two separate etherchannels and then migrated
> them "live" to MEC...=20
Check flow control between all of the elements. The only time I've
seen this was inconsistent flow control settings between different
media types on an F5 BIG-IP <-> 6500 bundle.
show interfaces flowcontrol
Ross
--=20
Ross Vandegrift
ross@kallisti.us
"If the fight gets hot, the songs get hotter. If the going gets tough,
the songs get tougher."
--Woody Guthrie
--J2SCkAp4GZ/dPZZf
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAksMZDwACgkQMlMoONfO+HD2/QCeJs3bjnY3lsfx8tU9EzpFi/1n
WdoAoM1jQHRroWxBnWbFTCs/CEZ6yPSs
=JJoN
-----END PGP SIGNATURE-----
--J2SCkAp4GZ/dPZZf--