I would suggest opening a TAC to get the full details on why it’s happening if
the root cause not readily apparent. Typically remediating a these types of
mismatches entails copying the default config to startup (triggers a reload)
and rejoining the fabric.
On 6/30/16, 1:41 PM, "NANOG
I have to agree with Dan in that even if you disagreed with the talk you
have to agree that it probably spawned relevant discussion and reflection
(both on and off list). I would hate to see a move to ideas and discussions
that are chosen simply for offending the fewest people. Another sort of
I have a feeling that most if not all of the requirements you have could be
achieved with a Cisco ISR router running some kind of FlexVPN/DMVPN setup
back to a network VPN hub. The ISR G3 series has the option of enabling a
built in firewall/IPS. You'd need a RADIUS solution to authenticate the
The various domains and IP address listed in the following file
are, as we speak, acting as distribution/infection points for
some sort of Javascript malware which is almost certainly a
flavor of ransomware.
** FAIR WARNING *** Please use exceptional caution when browsing
to any of the domains
NANOG Community,
The NANOG Program Committee is excited to announce that we are accepting
proposals for all sessions at NANOG 68 in Dallas, TX on October 17-19. I
have included key points from the Call for Presentations and the complete
text is available on the NANOG website:
Hello Mike,
Running a few larger Brocade VDX fabrics here...
In case of that message, there is no other option not to reset that
specific new switch and then re-join the device. I had that a few times,
too.
It happens when you already did some configuration changes on the new
switch and
Dear Mike,
Are you running fabric with logical-chassis mode. Did you set priorities on the
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
I asked on the Brocade forum, but it's largely been crickets there. I hoped
someone here would have an idea.
One switch says: 23 Te 12/0/24 Up ISL segmented,(ESC mismatch, Distributed
Config DB)(Trunk Primary)
The other switch says: 23 Te 54/0/24 Up ISL segmented,(ESC mismatch,
Distributed
Haha, I would have done the same thing.
If it is important, someone will show up.
On Tue, Jun 28, 2016 at 5:58 PM, Carlos Alcantar wrote:
> We had a similar situation a couple years ago we went around for weeks
> trying to find someone that could help us with the equipment.
As mentioned at the peering personals...
route-views.chicago.routeviews.org is now up and running.
New peers are welcomed. We request full
tables if possible. We send zero back in your direction.
Peers should minimally filter default/null/rfc1918 from
their view. Our side is:
AS6447
10 matches
Mail list logo