FWSM and CSM - Naming the control-plane PortChannel
Hopefully a very easy one for someone to answer - given that the internal backplane (FWSM <-> Cat65xx) and (CSM-S <-> Cat65xx) is automatically generated, and seemingly can't be changed (i.e. our CSM-S works on Po262, or 261 and I think the FWSM is something like Po276), will IOS allow me to name the PortChannel and/or automatic interfaces?
For instance, would the following be permitted/work, or because these are automatically generated, could it break something?
On the FWSM (Firewall Services Module), I get the idea of using "svc-vlans" etc to chose your "Virtual Line Cards", but for the CSM-S (Content Switching Module with SSL), there doesn't seem to be any "svc" or other configuration for the backplane transports at all on the Cat65xx; it's just "there".
Cat6500#conf t int po262 desc *** CSM-S Control Plane PortChannel *** int range gi6/1-4 desc *** CSM-S Control Plane Trunks *** end
Cat6500#conf t int po276 desc *** FWSM Control Plane PortChannel *** int range gi7/1-4 desc *** FWSM Control Plane Trunks *** end
Moquery is the command line cousin of Vizore, it's very helpful and efficient sometimes during the troubleshooting. This article aims to provide moquery cheat sheet to the users for some most common seen scenarios.
Here is the checklist before customers/partners contact Cisco TAC:
Firmware Version of APIC and Switch
Download Switch and APIC techsupport logs
Problem description (Symptoms with details)
Business impact (eg, what kind of services...
moquery usageAPIC moquerySwitchmoquery
This document discuss a common issue observed during the VMM integration & VM workload migration to ACI fabric.
VMware Virtual machines are hosted in Cisco UCS-B seri...