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. ... View more

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.    Back to my issue with the callhome: I'm running version 3.2(1m) and I followed your doc (totd-apic-callhome-example_01.pdf) but something is wrong. It will help a lot if you can answer following questions: 1. If I complete first two steps ("Create a scheduler" in step one and "Callhome Query Group" plus "Callhome Destination Group" in step two) should I see anything in the output of "show callhome common" command? In other words, what is the minimal callhome related config so I can see something in the output of "show callhome" related commands (like "show callhome common destination-profile" and "show callhome common transport-email" etc... 2. Is callhome email always sent from APIC or each device generates its own email? In other words, will leaf or spine switch generate its own callhome email if one power supply stops working or APIC is going to do it for them? 3. Can you clarify purpose of steps three (Configure Callhome for Fabric -> Fabric Policies) and four (Configure Callhome for Fabric -> Access Policies)? Is callhome enabled per switch or for complete ACI environment (if I want to have a pair of switches for testing purposes and need callhome for everything except those two)? 4. Finally, is your callhome config expecting some pre-configured environment? If I have brand new ACI (or I removed any previous config and only applied OOB IP addresses) should described callhome procedure work? ... View more

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 you that OOB IP is 0.0.0.0. However, if you ping it or ssh everything works fine. This is true for many versions I tested so my guess is that it is not easy to fix. ... View more

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? ... View more

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 or 2.1 it seems like we'll have to do intermediate jump first. Two options are available, 1.2(3) or 1.3(2), and I'm not sure if one of these is preferred. Any suggestions from your side? ... View more

Thanks for your swift response Vishal! Here is the detail that bothers me: vPC requires two neighboring switches to be connected with peer-link but spine-and-leaf topology doesn't allow two leafs to be directly connected, right? I'm talking here about N9ks running NX-OS (not ACI) and I even found one article (link below) where spine-and-leaf topology is described but  vPC is not mentioned at all. So, I'm looking for your help to clarify if vPC will work in that scenario (N9ks running NX-OS in spine-and-leaf topology)? http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/6-x/fundamentals/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Fundamentals_Configuration_Guide/b_Cisco_Nexus_9000_Series_NX-OS_Fundamentals_Configuration_Guide_chapter_01.html ... View more

Hi gents, I hope my question is not out of the scope, as it is related to Nexus switches and VXLANs: customer decided to use NSX and part of the design includes Cisco spine-and-leaf switches. However, we can't agree if we should use NX-OS (with N93936 as leafs and N9508 as spine switches) or ACI approach. Can we even provide vPC functionality if first scenario is used (one with NX-OS)? Thanks, Renato ... View more