My name's Mostafa CHAKIR,I am a technical ingeneer in the CBI Networks Morocco.
We have a dual connection to a IBM Host via two 7206 routers called CPA1 and CPA2 in the central site.
In the remote site we have a 2610 routers connected with Public Frame-Relay, and anohter link with ISDN as backup.
Two peers dlsw from the remote site are configured, the first with CPA2 and its backup with CPA1 ( as you will see in the configuration).
when the link go down (FR), the peers stay in stat connected in both site until there is a SNA trafic, and the ddr is made from the remote site.
The problem is when the two link go down, the Host always see that the remote site is connected, the router CPA2 don't breack the circuit, and when the ISDN link come UP first, it open a circuit with a CPA1 even if the CPA2 is active, the HOST don't accept the second circuit cause it says that there is another circuit opened in the CPA2 with the same IDNum IDBlock. I tried to resolve that with the "dlsw timer sna-cahe-timeout" command but it have no effect.
If i remove the keepalive 0 from the configuration of the remote site's router, the ddr will be made immediately after the primary link goes down (FR), it will stay active all time, because the dlsw is the intersting trafic for the ddr :access-
access-list 101 deny icmp any any
access-list 101 deny eigrp any any
access-list 101 permit tcp any any eq 2065
access-list 101 permit udp any any eq 2065
access-list 101 permit udp any any eq 2067
dialer-list 1 protocol ip list 101
I tested it before, and the only solution is to configure keepalive 0.
Providing you are using the LINGER parameter on the dlsw backup peer statement, the backup peer connection should be completely torn down once the primary peer has been up for the linger period so no DLSW traffic should be passed over the ISDN and it will time out.
If you have tested this and are not seeing this behaviour, I would raise it with the TAC as a bug.
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...