Is there any chance that a Fabric Interconnect 6296 in EHM make a loop in a LAN?
A couple of weeks ago we try to make a upgrade from a 6140xp to a 6296up, when the first fabric (6296) was put into the cluster one chassis go crazy and the fans in that chassis start making very loud noise. All the network entered into a loop and we have to make rollback. When the 6140xp was put again into the cluster the chassis 3 go back to normal. The loop in the LAN stooped when i disconnect the uplinks from the 6296UP.
So...i hope anyone can get my question answered and provide some document or info about the anti-loops mechanins.
In the time when the 6296UP was connected all services on my network were down, no magnagement trough ssh/telnet on the 6500 or the n7k.
what you saying abouts the chassis is correct, but what is strange is that when the 6296 was connected the chassis loose communication and go full power. In the moment we do some TS but the only way that the problem were solved was doing the rollback.
- We are migrating from a FI 6140XP to a full FI 6296UP so the port mapping is not a problem.
- All the hardware is in the same version (v 2.1)
- I follow the procedure describe in the same document you provide.
in the moment when the first 6296UP was incorporate in the cluster the problems begins; a chassis (we have 10 chassis) was alarmed and the fans go full power; loose magnament capabilities with the n7000 and the 6500 switches; The UCSM console loose communication with the fabric several seconds after log in; Making a ping to FI cluster ip show loose of packets.
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...
Cisco Documents are usually accurate, but when it came to the document
on Cisco APIC Signature-Based Transactions it was slightly off the mark.
This document is for those novices to API like me who cant seem to
figure out how to go about performing signat...