I have 2 ace modules in seperate 6500 chassis, one admin context and 2 production contexts, One FT peer configured and 2 FT groups.
All seems to work ok, but we had a power down on one of the 6500 chassies last weekend and after the ace module reloaded we experianced lots of issues with one context. The arp table on the 6500 was showing the ACE Vip pointing to the local ace although the FT show commands showed the ace in the other data centre as active. We had to remove the context on the ace in the end to get things working as we ran out of time. We plan to add the context back in during a change window and test.
I noticed one thing on the FT vlan that sits between the ace modules we also have layer 3 addresses and HSRP running between the 6500 on the FT VLAN, in the guide it mention no HSRP and no other data. ( we dont have any duplicate address issues)
My question although could be unrelated to my issue, is this correct should i remove the layer 3 configuration from the 6500 and just have the vlans configured with layer 3 only on the ACE FT vlan ?
Is there a reason why you have IP configured for FT vlan on 6500? If there is no requirement it can be removed.
The ACE would just send the heartbeats to its peer ip over the FT vlan to check the status. You could also consider configuing a query vlan, the purpose of the query vlan command is to have a second check in case the FT vlan fails. If both ACEs are up and running, but something happens to the FT vlan (cabling problem for instance) the ACE will ping the IP Address of the other ACE for the configured interface in the query vlan command.
Hi all,not sure this is the right place to raise my question..if not..beg you pardon.problem: I have to interconnect 2 datacenter with 2 links 10gb each so...10+10physical connection is DWDM (dark fiber) and each datacenter has is own nexus93108 (as ...
Coming soon - Be the first to know about the New Product/Release Series. Join Customer Connection to register for the briefings throughout the month of October!
Membership in the Cisco Customer Connection program is required to attend. Registra...
Description:Fault delegate: A Fabric Node Group (fabricNodeGrp) configuration was not deployed on the fabric node 152 because: Node Not Registered for Node Group Policies Type:Config Cause:configuration-failed Change Set:deplSt:not-register...
<original blog published on cisco @ https://blogs.cisco.com/datacenter/cisco-mds-32g-fibre-channel-fabric-switches-small-doesnt-mean-less >
When we think about fabric switches, we tend to consider low-end hardware. These typically do ...
Cisco Champion Radio · S7|E34 Cisco HyperFlex with iSCSI Helps Consolidate Workloads
IT organizations that get the most out of their technology investments tend to grow faster than their peers. As a result, they are always exploring enhancements to exist...