UCS to a Catalyst inconsistent network between blades
I'm fairly new to UCS, so this may be (hopefully) a quick fix.
We have two chassis connected to a pair of 6296 FIs. The FIs break out of the network via 10Gb ethernet to a Catalyst 4500. Each blade works perfectly to anything outside of UCS, but they cannot communicate between each other.
At the moment there is only a single link to the network (this will be upped to 4 on monday), the port is set to an uplink.
I am guessing that comms between the blades go down to the Catalyst and should go back up the same link to the next chassis, but the catalyst is not doing this?
Are you saying that there is only ONE link from one FI (let´s say FI-A) to the 4500 and the other FI (FI-B) has no links to the upstream switch?
Servers cannot communicate to each other when you ping each other´s management IP/OS IP/VM´s IPs?
I think the issue might be that the Cat4500 does not support VN-Link (Now called VM-FEX or Adapter FEX), which basically allows the switch (VN-Link capable, e.i Nexus7K or Nexus5K) to understand that his phisical link is actually divided in 2 (or more) virtual interfaces, letting the switch send traffic back from the same physical interface it is receiving it on. A regular switch, not VN-Link capable, would normally drop a packet that has the same destination as its source to avoid a loop.
The unmanaged mode is also known as Network only switching, which is introduced in Brazos release. It adds the flexibility for customer to use only network automation for service appliance.
If a device is configured a...
Usually, we can access ESXi Shell by pressing Alt+F1 from ESXi DCUI (Direct Console User Interface).
But on HyperFlex system, it just shows black window.
This is expected behavior because HyperFlex redirects ESXi Shell output to SoL...
Configuring an Export Policy Using the GUI
This procedure explains how to configure an Export policy using the APIC GUI. Follow these steps to trigger a backup of your data:
On the menu bar, choose Admi...