Any issues running 3.3(4b) Fabric Manager on 3.3(1c) switches?
I'm doing a little pre SAN-OS upgrade work (and changing out my FM Server backend DB from Postgres to Oracle 10g) and I see that the clone option is back (finally) in 3.3.(4b) fabric manager. We've run newer versions of Fabric Manager before, ran 3.1.x on a 3.0.x fabric for a while so I'm just wondering if I could upgrade my production management FM server (not just data collection but management) from the current SAN OS to a newer one before I install SAN-OS 3.3(4b) on my switches? It should be backwards compatible but . . . just wondering if someone else has the scars from this sort of activity.
Re: Any issues running 3.3(4b) Fabric Manager on 3.3(1c) switche
Yeah that's the answer I'm getting from Cisco too. We've had some real flakey behaviour at odd times lately (zone sets that are inserted into the active zoneset but disappear when you try to activate, zone set renames that dont' take etc.) which all seem to be Java issues (i.e . it's slow and flakey and you're rdp'd to the FM server so that's in there too.) But we need to redo the FM server anyway and thought I'd make sure it was o.k. to upgrade at the same time.
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...