Hi – I am trying to find some information on any limits on the number of FEX VIFs imposed by vntag and number of fabric interfaces between N2K and N7K… I know limits and rules exist with UCS 220X IOM and the fabric interconnect so I would assume (as ...
I understand the site vlan is used to establish L2 adjacency between AEDs within the same site. I also understand that these same site AEDs establish a L3 adjacency across the join / overlay interface.Does this 2nd (L3) adj require the two join inter...
If ruining fabricpath in a leaf, spine (vpc+ l2/l3 boundary) and l3 core design is it possible to breakout on a classical ethernet dot1q trunk from the spine to temporarily pass the fabricpath vlans to another site (catalyst only)?
If the iscsi vlans do not need to be accessible from outside of the ucs domain do they need to be on the uplink connections? I have an issue in which the iscsi vnics can’t ping the iscsi targets, however, from outside of the ucs domain I can ping bot...
Is an iSCSI vNIC created only to allow boot from SAN? So when the OS is installed these vNICs will not show up, only the overlay NIC will show?I am trying to understand what vNICs are required to allow boot from SAN and iSCSI SAN connectivity once th...
2nd this - You would only ever use ip hash if your upstream network supported "static port channel" of some description - With UCS as both FI's are independent bridges (bridges, from a port channel perspective) a connection to each FI could never sup...
It is my understanding that this is the correct / default behaviour. When you created a mgmt pool, physical hardware automatically picks up an address after discovery. When you create a template, you do not necessarily need to assign the pool to the ...
I personally would have separate IP subnets for blade KVM access and ESXi management, I would ‘think’ having a management network within the UCS domain which also passes through the UCS dataplane would be unsupported. Under FlexPod, this would be uns...
Correct… You create your vnics which will be used for block access (within the OS / hypervisor) and then overlay logical iscsi vnics on top of these which are then used by the service profile to boot.. The logical vnics do not show within the OS / hy...
Yes that helps, many thanks.To summarize, I could have FEX1 > e1/1, FEX2 > e1/2, FEX3 > e1/3, FEX4 e1/4 (all ports in the SOC)… Each FEX with only the single uplink..
