I am not getting a login page at all for the primary ACE, but getting a full login page and able to login to the stand-by device. The Admin Context between the two contexts are identical. Below is the Admin Context config:
logging enable logging buffered 6
resource-class ABC limit-resource all minimum 75.00 maximum unlimited
boot system image:c4710ace-mz.A3_2_0.bin
peer hostname LB2-A hostname LB2-S interface gigabitEthernet 1/1 channel-group 1 no shutdown interface gigabitEthernet 1/2 channel-group 1 no shutdown interface gigabitEthernet 1/3 channel-group 1 no shutdown interface gigabitEthernet 1/4 channel-group 1 no shutdown interface port-channel 1 switchport trunk allowed vlan 201-204 no shutdown
clock timezone standard EST
class-map type management match-any ACCESS 2 match protocol https any 3 match protocol icmp any 5 match protocol ssh any
policy-map type management first-match REMOTE-ACCESS_PL class ACCESS permit
interface vlan 202 ip address 10.11.202.251 255.255.255.224 peer ip address 10.11.202.250 255.255.255.224 service-policy input REMOTE-ACCESS_PL no shutdown
ft interface vlan 203 ip address 10.11.202.10 255.255.255.224 peer ip address 10.11.202.11 255.255.255.224 no shutdown
ft peer 1 heartbeat interval 300 heartbeat count 10 ft-interface vlan 203 query-interface vlan 202 ft group 1 peer 1 priority 75 associate-context Admin inservice
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
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...