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.
I was digging through the Broadcom support to see if I could find the latest custom ESXi iso and it seems like several vendors showed up but Cisco did not... Any reason for this that anyone knows? And does anyone happen to have the latest ESXi custo...
I did an initial config and accidently labeled a full domain as FI-A for example:
Actual Domain: UCS-PROD
What its named now: UCS-PROD-A
FI-A name currently showing in intersight: UCS-PROD-A FI-A
FI-B name currently showing in intersight: UCS-PROD-A...
When deploying a greenfield UCS Domain and there isn't already a vCenter or no way to allow connectivity from a legacy vCenter to the new UCS Domain, what are the options for deploying a PVA?
The issue I see is to deploy a 5108 or 9508 you need to de...
Hello,
I'm trying to figure out if and how to configure 2 vNIC's on 2 different b200 blades to communicate without having to use a northbound ACI switch.
Each b200 has a vNIC-a and vNIC-b
Both vNIC's have been given the same random vlan 1234
Both vNI...
Update2:
Even though the command sent out a response "Error: Domain name update failed" it seems the command actually worked regardless as the domain name has changed in intersight.
Setting this as the answer for now.
Quick update:
I see there is a command in the CLI "change-domain-name" But that doesn't seem to be working with IMM FI's says it cant find /bootflash/tmp/initial.config.name/setup
Thanks for the reply,
Due to the fact this was a time sensitive issue I went and had the vlan added to one of the upstream switches regardless which resolved the issue. This is interesting and I wouldn't mind testing it in a lab when I get ahold of ...
OK so if I had vNIC-A pinned to FI-A defined on B200-1 and vNIC-A pinned to FI-A on B200-2 I should in theory see connectivity.
Which is still not working.
I think this is due to the fact that the host isn't in switching mode and requires a NB switch...
To clarify
Do you mean if we have a bonded pair in the OS with 1 NIC pinned to FI-A and another nic pinned to FI-B that the bond wont work OR are you stating that between 1 blade a NIC from FI-A and FI-B will not communicate?
