Working on a 6509 that has Radius authentication set.
All works well except some errors in the radius log. It appears that there is something in the 6509 that trys to authenticate via Radius in order to talk to itself (client and server ip the same). The entry pops into the log every minute.
Client IP: 10.101.254.5 (6509's IP)
Connect Request: IAS_NO_SUCH_USER
Connect Result: Rejected
FQ Username: PHLVRC\azbycx
server IP: 10.101.254.5
Any suggestions of what I should look at to tackle this problem?
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...