Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Is RMA only permanent solution or there is a way to fix it with some SW upgrade, without need to replace the switch? I'm talking about affected switches (i.e. those that are part of PID and SN lists).
There is a list of known fixed releases but based on my testing it doesn't work yet. I'm not aware of any "test button for callhome", has anyone else seen it? CLI command ("callhome test") still seems useless (last release I tried is 3.2.3n).
I'm running 3.2(1m) in my lab and I uploaded new version via CLI to /home/admin folder. When I execute "firmware repository add" command, I receive the following:
apic1# firmware repository add aci-apic-dk9.3.2.3n.iso
Error: Failed to move image ...
Does APIC contain a log file where any configuration change can be identified? I'd like to be able to identify who, when and what was modified in ACI config.
Apart from physical work involving installation and power up new spine switch plus cabling it with all leafs, is there any mandatory config needed on APIC side? I know we can add node id and specify OOB IP or some other things but I'm curious to lear...
I haven't played enough with Classic LAN but I would expect to see different instances. Just like I'm not expecting LAN Fabric instance to cover SAN Management, I would expect same behavior to be applied to Classic LAN instance.
Hi Tomas,
first, I'd like to thank you for all those great posts; searching through various ACI docs for the right piece of info is often tedious work. Your posts keep my attention even when they don't cover any of my current ACI related challenges...
ACI switch firmware is having problem retrieving config from MGMT port. If you configure it while switch is running NX-OS and then covert to ACI, IP will stay on that interface but ACI firmware will not be able to recognize it and APIC will inform yo...
Thanks Ganesh!
Is it possible that my ACI environment is not configured to assign IP to a new members of the fabric, i.e. that I have to do it manually? I'm assuming that we talk here about in-band IP. What about OOB IP for new switch?
Thanks,
we are currently using 1.1(2h). i.e. the very first ACI version that supports vShere 6.0. Is there anything special we have to do during the vCenter upgrade so we don't lose DVS that was injected by APIC controllers?
To reach APIC version 2.0...
