I am wondering if anyone has any experience/advice on the best way to accomodate the HP Virtual Connect (VC) modules into our Cisco DC environment.
We have a new HP chassis about to go in with two VC modules. It is my understanding that these modules, although physical, are just like the soft switches in the VMWare environment. In other words, they are not traditional L2 networking devices. They don't pass BPDU's, the appear to the upstream switch as a host, etc. They can't do cross-stack LACP, and load balances across VC modules using a "nic-teaming" like feature that can take up to 5secs to failover.
I have two specific questions. First, I am wondering if it makes sense to connect these to the access layer rather than the distribution layer (which was my original intent). Not sure I feel comfortable connecting an non-networking device directly to the distribution layer. What are the pros/cons of going to the distribution layer with the VC modules?
Second, If going to the access layer would a 3750 stack be sufficient for redundancy. The idea would be to split the uplinks across the stack members. As opposed to going into separate physical Cat6ks.
Long term we plan to migrate to the Nexus platform with N7ks distribution, 5k end-of-row, 2k ToR. I want to make sure we have a consistent server access architecture and whatever we implement now and will migrate as easy as possible to the future DC architecture. Even if it means having the server team order traditional layer2 switch modules for the HP chassis.
Any feedback on what others have done and/or advice is appreciated.
You can consider the HP VC modules like a Vswitch, supports 802.1q but transparent to networking protocols, except portchannel 802.3ad.
It supports etherchannel per VC modules, we connect it in straight through topology (one HP VC on one Nexus 5k with 2 10GE portchannel) on the access layer.
Connecting the VC on the access or aggregation layer ? it depends on the flows and the expected throughput... For Flex10 or FlexFabric, I would connect it on the aggregation layer to avoid any problem of oversubscription, for VC 1GE, I would connect it on the 3750 stack.
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...