There's hardware in the 6500 design which handles packet classification and forwarding.
The supervisor CPU and routing CPUs aren't directly involved in forwarding packets. They instead look after programming the hardware with forwarding, QoS, ACL and routing information.
This means the hardware can do what its good at - forwarding packets - and the CPUs can handle running monitoring, housekeeping and switching/routing protocols without any impact on forwarding performance.
It does, however, mean the featureset can be somewhat restrictive compared to the software routers. You have to keep an eye on the hardware resource usage and do a little research before you enable features. Some features work in hardware (eg GRE decapsulation) except in certain circumstances (GRE hardware decapsulation requires the GRE endpoints to have unique IP addresses. If you terminate more than one GRE tunnel on a single IP address then it might be punted to the CPU for processing.)
The platform uses hardware to implement functions traditionally found implemented in software. This means it achieves its advertised speed regardless of session count and connection rate. It does, however, put a pretty harsh upper limit on the parameters you can use.
Have a read of the datasheet, which covers the parameters.
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...