I have 2 dlsw router at head quater office, named dlswA and dlswB.
From branches router, dlswA is a primary peer and dlswB is a backup peer.
Both dlswA and B have 2 fast ethernet interfaces.
The current configuration of dlswA and dlswB are 1 port as IP port and other port as sna/bridge port.
With this configuration the problem is when SNA port at dlswA problem, then dlsw circuit will have the problem, because dlsw peer from branches still connected to dlswA.
if I configure 2 fast ethernet port become a port channel. And configure IP and bridge group at port channel interface (IP and SNA at the same interfaces), so when the port channel is down, then branches will connect to dlswB as a backup peer
Are the port channel configuration will solve the problem ? How about the stability of this configuration?
i dont think that a port channel will help you in this scenario.
1. as far as my understanding goes a port channel does not go down if at least one member of the channel is still up. So you would have to go both channel members go down to get the port channel down and trigger something on the other router.
2. I dont think that mixing ip routing and bridging in a port channel is really going to work. for sure no one is testing this scenario.
if i understand your description correct you have a classic topology with a branch peering to two head end routers.
The second peer is defined as a backup peer of the first one. However a dlsw backup peer only backs up the tcp portion of the peer.
If you want to have full backup of the path you would have to use two permanent peers from the branch. One to each host end router.
However that depends a bit on how the topology on the host end looks like. I.e. since you say fast ethernet ports, are both head end routers on a common ethernet? Or do they go to two different hosts using the same mac address on different ethernet lans?
Both of head end routers are on the same vlan and the host is using same mac address.
As far as i know if from branch have 2 active peer with cost setup, there will loops posibility because both head end routers are using ethernet with same vlan and same host mac address.
I test the port channel within my LAB using netbios, seem works as expected. when single port at port channel down, branch circuit still remain at dlswA router, when all port channel member down, the branch peering move to dlswB.
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...