Hi everyone,one clarification...: when we set-up a VMM integration (VMWare AVS, or Kubernetes), which multicast address we can use for "Fabric-wide multicast"? Have to be different from "bridge domain multicast address (GIPo)"? Or have just to be dif...
Hi everyone,regard ACI and Kubernetes Integration, when we deploy the Kubernetes VMM domain with acc-provision we have option to choise to use VXLAN or VLAN as encap_type used by OPFLEX. Questions:Which is the best practice or suggested option to use...
Hi everyone,
I have some problem with KVM InBand access to UCS b-series server. I have configured all things that are needed to access via InBand management access. But when I try to access with browser I receive some errors.
1 - If I click "KVM co...
Hi everyone,
I have just one doubt regarding the data-group range for OTV. In some documentations I read that I have to configure the data-group range to be part of a SSM multicast address; while in other document seems that I can configure a ASM as ...
Hi everyone,someone knows exactly how is the Access VLAN Port Count calculated? And, If I have the feature failover enabled in the vNICs, could it increase the total in some way?
Thanks so much
Regards,Roberto
Hi micgarc2,thank you for your answer.I asked it because by default Plug-In use IP 225.1.2.3 that overlap with default BD GiPo (225.0.0.0/15). Also, in Cisco DevNet Learning Labs, the Kubernetes and ACI CNI plug-in lab use 225.1.2.3 as Fabric wide mu...
Hi Kirk,thank you for your suggestion, but I don't have any pop-up blocker active. I have tried to set all security settings on my browser to minimum; I have tried with more browser and with more pc, but unfortunately the problem is the same.
Regards...
Hi Pranavgu,
yes, I confirm I have assigned an InBand IP Address to CIMC. I can ping the InBand IP Address of the CIMC correctly; also, I am able to reach this IP through https...but I receive error indicated.
Thank you anyway.
Regards
Roberto
Hi Kirk,
I think you are right, but I have tried to migrate a service profile from template called one to template called two. The second service profile template was cloned from the first. The only difference is basically related to failover feature...
