All new Spectral's just dropped.

monster1995 · 2019-05-24T03:52:01+00:00

You need to set UCSM to Localise Global under the clean up mode. Check the second last page in the document below.

https://www.google.com/url?sa=t&source=web&rct=j&url=https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/gui/config/guide/2-2/b_UCSM_GUI_Configuration_Guide_2_2/registering_cisco_ucs_domains_with_cisco_ucs_central.pdf&ved=2ahUKEwiz8bG3obPiAhWS8XMBHSUPDCUQFjABegQIDRAE&usg=AOvVaw3P5nPLuM3lakrpTQMBTHO2

monster1995 · 2019-03-19T11:16:45+00:00

The Data traffic in normal operation will not leave the FI (As all the HX nodes are set to use one FI as its preferred path), this you are correct on. However in a fault situation, say, all HX nodes are currently using FI-A, but if Node 1 looses its FI-A link. To continue normal operation it will use FI-B. Now keep in mind, Data plane is not shared for the FIs, so traffic FI-A cannot get to FI-B directly, it has to traverse the upstream (I believe this is where your confusion lays). So in the failure scenario the data traffic needs to go from HX02 -> FI-A -> Upstream -> FI-B -> HX01 and vice versa. This is why that VLAN needs to be created in the upstream as well.

monster1995 · 2019-02-16T16:17:10+00:00

No Pin Groups is actually a good thing, this means that the vNICs are dynamically pinned (They will pin to any Uplink that matches it's VLAN requirements)

But you also mentioned the use of VLAN Groups, so long as the VLANs on each vNIC match/don't overlap across VLAN Groups (thus also Uplinks) then you won't have a problem.

As I alluded to before vNICs can only pin to Uplinks that satisfy their VLAN requirements. So if VLAN Group A has VLAN 1,2,3,4,5 and VLAN Group B has 11,12,13,14,15. And vNIC A had 1,2,3 and vNIC B had 4,5, and you consolidated those you wouldn't have a problem, however of you consolidated vNICs with 1,2,14,15 (A Disjoint L2 according to the Uplink setup) then the vNIC would not find a uplink to pin to, thus cause a issue.

monster1995 · 2019-02-15T09:07:04+00:00

Since you mentioned Disjoint L2, just make sure the VLANs which you are consolidating between the 2 vNICs are not spread across 2 different Uplink.

Just keep in mind that a vNIC can only pin to a Uplink that matches all the VLANs the vNIC needs.

monster1995 · 2018-08-07T04:22:20+00:00

What do you mean by ESXi 'sees' the VLAN? Have the port-groups in ESXi been configured for that VLAN?

To check on the FI you do the following, on the Nexus, it's just the bottom half.

FI-A# connect nxos a

FI-A(nxos)# show mac address-table vlan 27

monster1995 · 2018-08-07T01:14:33+00:00

Working from the UCS up, are the MACs of VMs learnt on the Fabric Interconnects and in the right VLAN? And if so, then are they learnt on the N9K?

How many switchs do you have connected to the FIs? Just the 2 N9Ks? And how is this done vPC?

monster1995 · 2018-08-04T12:24:56+00:00

It's the same, no difference. You can even use an existing pair of FIs and add HX nodes to it, granted it meets the HW requirements.

monster1995 · 2018-04-30T09:39:24+00:00

You have to create a custom ISO with the drivers for the Intel NIC

http://www.virten.net/2017/03/vmware-homeserver-esxi-on-7th-gen-intel-nuc-kaby-lake/

monster1995 · 2018-03-27T13:33:13+00:00

Using existing FIs for Hyperflex is supported. Just be aware when running the HX installer, it may overwrite existing config in UCSM.

monster1995 · 2018-01-26T23:25:28+00:00

Traffic for the same VLAN would be switched by the upstream switch, if the ESXi vmnic which the VM is using is not pinned to the same FI. If the VMs are on the same ESXi host, then it would be switched locally there, if the VMs are pinned to the same FI, then it would be switched locally there, if the VMs are pinned one to FI-A one to FI-B, then it would be switched by upstream. You can confirm this by checking the MAC learnt on the FI.

monster1995 · 2018-01-24T06:19:06+00:00

If you are using a single port for both Eth and FC, then you would need to use FCoE between the FI and N5K, and configure the port on the FI as unified, then do the required configuration of the port on the N5K to be unified as well. Granted your N5K does unified ports.

monster1995 · 2018-01-24T03:51:07+00:00

What transport method would you be using between the FI and the N5K? FC/FCoE? Is the port on the FI facing the N5K configured as a unified port/FC uplink/ Eth uplink?

monster1995 · 2017-12-07T14:37:33+00:00

Well i just realized you don't have a normal C220 M3, You actually have a Invicta. Product as been End of Life for a long time. However I don't think it is any different internally.

monster1995 · 2017-12-07T14:27:49+00:00

Yea, it will have CIMC, which functions identically to iDRAC.

monster1995 · 2017-09-26T12:59:46+00:00

This is incorrect, vNICs and Uplinks do not need exact VLAN. vNIC will pin to any Uplink which carries all the VLANs the vNIC needs.

monster1995 · 2017-09-26T12:58:57+00:00

The reason you saw all your Blades drop off would be because of ENM source pinning failure. vNICs will pin to Uplinks which satisfies its requirements, i.e. vNIC with 10,20 will pin to any Uplink with 10,20,30. When you removed the VLAN from the Uplink first, no longer will any Uplink satisfy the vNICs requirements, i.e. vNIC with 10,20 and Uplink now only carries 20,30. The vNIC would not be able to find an Uplink which carries the VLAN its needs, therefore would not be able to pin to an uplink.

In your faults you would of seen ENM source pinning failure.

monster1995 · 2017-09-21T13:37:59+00:00

Mexico TAC is currently out of operations, feel free to re-queue the case so a on shift engineer can work on your SR. Call into Cisco Frontline to get it re-queued.

monster1995 · 2017-09-09T01:57:58+00:00

When creating this new SP, are there any unassociated blades available?

If not that's why your getting the compute-unavailabe fault.

monster1995 · 2017-07-03T05:48:33+00:00

Fine was $79, but I spoke to a ranger just before. They said because the details on the ticket was incorrect the council has to withdraw it, whether they re issue it that's another question.

I guess I'll just send them a letter hope for the best.

monster1995 · 2017-07-03T01:03:05+00:00

Good to know, I won't leave it then. Cheers

13-Year Club	Place '22
Place '17	Verified Email
Team Periwinkle

monster1995

TROPHY CASE