I just install a network based on layers of access (to WAN), DLSw and CSNA. When we start the tests some remote devices start a DLSw circtuits and SNA traffic with no problems, but other devices (SDLC) on remote sites start a DLSw traffic but can't start applicatins on Mainframe (CICS). The command show dlsw circuits history detail showed bellow show many WAN INFOFRAMES without response. Anyone can help us to fix this problem or indicate where is the problem (WAN, DLSw, CSNA, Mainframe, etc.) ?
Where do you the show dlsw circuit history detail?
The WAN Infoframe may not be the problem because I do not think that RR (LLC2 ack) frames show up in the show dlsw circuit history detail. The root cause is the WAN HALT-DL. This causes the DLSw circuit to disconnect. We need to find out why the remote DLSw peer sends out HALT_DL.
I suggest you to do a show dlsw circuit history detail on the other side of DLSw and find out why it issues a HALT_DL. You may also need debug llc2 packet, CIP console trace, show interface serial, or debug sdlc packet.
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...