We have put an SSLM in place last week and I am having some strange problems with the way IP connectivity is working on that module.
We currently have 2 6509 switches with CSM-S. So in summary we have 2 MSFCs, 2 CSMs and 2 SSLMs. On each of these devices we have 2 networks configured. One for PROD traffic and the other one for management. The management network is 10.2.69.xxx and the production network is 10.2.70.xxx.
The IP address of the devices are:
MSFC Pri - 10.2.70.3 (PROD)
- 10.2.69.11 (MGT)
MSFC Sec - 10.2.70.4 (PROD)
- 10.2.69.12 (MGT)
CSM Pri - 10.2.70.86 (PROD)
- 10.2.69.69 (MGT)
CSM Sec - 10.2.70.91 (PROD)
- 10.2.69.70 (MGT)
SSLM Pri - 10.2.70.100 (PROD)
- 10.2.69.51 (MGT)
SSLM Sec - 10.2.70.99 (PROD)
- 10.2.69.52 (MGT)
The gateway on PROD is 10.2.70.1 and on MGT is 10.2.69.1.
Now from SSLM Sec for example I can ping the following:
10.2.69.69 (CSM Pri MGT)
10.2.69.1 (MGT Gateway)
10.2.69.51 (SSLM Pri MGT)
But I cannot ping 10.2.69.70 which is CSM Sec or the local CSM.
SSLM Pri is also showing the same behaviour.
On PROD interface it is even more weird. I can only ping the local CSM from the SSLM and nothing else (like .1 gateway or .3 & .4 the real addresses of the routers or the remote CSM).
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...