[190371] in North American Network Operators' Group
Re: Brocade Fabric Help
daemon@ATHENA.MIT.EDU (Youssef Bengelloun-Zahr)
Thu Jun 30 16:10:07 2016
X-Original-To: nanog@nanog.org
From: Youssef Bengelloun-Zahr <youssef@720.fr>
In-Reply-To: <1217501659.6466.1467315681031.JavaMail.mhammett@ThunderFuck>
Date: Thu, 30 Jun 2016 22:09:57 +0200
To: Mike Hammett <nanog@ics-il.net>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Dear Mike,
Are you running fabric with logical-chassis mode. Did you set priorities on t=
he rbridges to select selection order of the principal switch ? Did you make=
any configuration changes from anywhere else than on the principal switch (=
using cluster VIP to connect) ?
IF so, then message seems to point to a configuration difference between nod=
es hence a possible DB corruption.
When that happens, the switchs would rather not join the fabric then try mer=
ge and possibly cause configuration alterations and instabilities.
You should try to dig that message out on the net or in NOS guides. Maybe op=
en a case with BTAC ?
But ultimately, I think you'll probably end up disabling one of the switchs,=
reset the config and rejoin it in the fabric.
HTH.
Y.
> Le 30 juin 2016 =C3=A0 21:41, Mike Hammett <nanog@ics-il.net> a =C3=A9crit=
:
>=20
> I asked on the Brocade forum, but it's largely been crickets there. I hope=
d someone here would have an idea.=20
>=20
> One switch says: 23 Te 12/0/24 Up ISL segmented,(ESC mismatch, Distributed=
Config DB)(Trunk Primary)=20
> The other switch says: 23 Te 54/0/24 Up ISL segmented,(ESC mismatch, Distr=
ibuted Config DB)(Trunk Primary)=20
>=20
> I saw that means, "The DCM Configuration DB is different on both the ends o=
f ISL," but I have no idea how to resolve that.=20
>=20
>=20
> VDX-6720s running 4.1.3b.=20
>=20
>=20
>=20
>=20
> -----=20
> Mike Hammett=20
> Intelligent Computing Solutions=20
> http://www.ics-il.com=20
>=20
>=20
>=20
> Midwest Internet Exchange=20
> http://www.midwest-ix.com=20
>=20
>=20
