This happened due to Interface is down buckeye it reached the maximum allowed retransmission failures.
This may be because of a loss of IP connectivity. Enter the show interface, show ip route CLI commands or use a similar Fabric Manager/Device Manager procedure to provide the IP address of the peer and the route used to connect to this FCIP peer. Enter the traceroute ipaddr CLI command or use a similar Fabric Manager/Device Manager procedure to check the connectivity to the peer. Introduced Cisco MDS SAN-OS Release 1.2(2a).
what alerts are the peer switch sending when the link flaps?
we ran into a new bug when upgrading to SAN-OS 3.1(3a). if using IP compression set to (auto). 'auto' uses a combination of both software and hardware based compression depending on the type of traffic, load, bandwidth, etc.. the software portion of the ip compression in SAN-OS 3.1(3a) wiggs out dealing with packet buffers. this would cause our fcip profile to bounce randomly anywhere from 10-20 times a day. EMC SAC and Cisco TAC had me enable IPS full core dumps to a tftp server. from there they were able to determine that it was specifically the 'auto' setting in IP compression on the MPS 14/2 blades on the MDS 9216i's. we then set the IP compression to 'mode1', which is all hardware based compression, on all switches and that resolved our issue with the fcip profile flapping.
%PORT-5-IF_DOWN_PEER_CLOSE: %$VSAN 50%$ Interface fcip1 is down
(TCP conn. closed by peer)
I am wondering if it is a carrier issue.
We recently had someone tell us the 3275 router cannot handle a full DS3 with any other services running and this could caused the isse, but I have seen this link peak at around 40Mbps and not have any problems.
Seems I saw somewhere that this could be caused by the frame size, that since FC uses a larger packet, it doesn't always work well when transmitting across an IP link. Resolution was to set the packet size to a smaller number.
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
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...