6248UP Fabric Interconnect HA functionality not ready
Hey Cisco community,
last night I received two "Information" messages from UCS:
Fabric Interconnect A, HA functionality not ready
Fabric Interconnect B, HA functionality not ready
A "Resolved" message I didn't received. Now I checked UCS, but can not found any problems:
ucs1-B# sh sys fi
ucs1-B# sh clu ex
Cluster Id: 0xba377bdcbbd811e3-0xa77a002a6a7ff0e1
Start time: Wed Jul 16 07:22:22 2014
Last election time: Wed Jul 16 08:08:13 2014
B: UP, PRIMARY
A: UP, SUBORDINATE
B: memb state UP, lead state PRIMARY, mgmt services state: UP
A: memb state UP, lead state SUBORDINATE, mgmt services state: UP
heartbeat state PRIMARY_OK
INTERNAL NETWORK INTERFACES:
Detailed state of the device selected for HA storage:
Chassis 1, serial: FOX1736GWMY, state: active
Chassis 2, serial: FOX1736GWKV, state: active
Chassis 3, serial: FOX1815GDW8, state: active
Can some tell me, what happened? We have four chassis, three are quorum chassis. The only thing I did yesterday, I created two disjoint L2 network and pinned some VLANs to different up-link port-channels. Po10 - VLAN 100, Po66 - VLAN 101,102, 117. Po10 is connected to a test environment with Nexus, Po66 is connected to the productive environment with Catalyst 6509. I can not imaging that is concerning with the HA issue.
I've checked the event log. There are many log every ten minutes from "sys/user-ext" and "sys/pki-ext".
Around 01:13:40 AM and 01:25:40 AM there are some events of the fabric. I attached the event log of that time period. Unfortunately the time stamp format is crashed, so you have to read the log from down to up. :)
I don't understand, why this happens in the night, nobody has triggered that. Are those some "self health check" tasks?
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...