Just want to get your expert opinion on this. I configured port-channel & vPC on two separate Nexus switch. The configuration is correct as the vPC is up and are port-channeling. The only thing I noticed is the aggregated bandwidth or link speed on the vPC as shown on the verification below. It does not show the aggregated BW which should be 2000000 Kbit in this case because I bundled two 1Gbe interfaces from diferent Nexus switches.
vPC is define as: "A virtual port channel (vPC) allows links that are physically connected to two different Cisco Nexus 5000 Series switches to appear as a single port channel to a third device."
My questions is, does vPC aggregates the bandwidth or speed accross multiple physical switches? Why it wasn't shown on the "show vpc" result as aggregated bandwidth?
Just curious and I wonder if I missed something on the configuration.
Input flow-control is off, output flow-control is on
Switchport monitor is off
EtherType is 0x8100
Members in this channel: Eth100/1/1
Verification on Switch-2:
N5K-02# show vpc statistics vpc 100 port-channel100 is up vPC Status: Up, vPC number: 100 Hardware: Port-Channel, address: Description: MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA Port mode is trunk full-duplex, 1000 Mb/s Beacon is turned off Input flow-control is off, output flow-control is on Switchport monitor is off EtherType is 0x8100 Members in this channel: Eth100/1/1
Remember a downstream device sees the two Nexus switches as a single logical device, but it still uses 'port-channel' and not 'virtual port-channel' to the upstream device. The vPC is only between the two Nexus 5k switches.
vPC actively forwards on both links. Hence it uses up all the uplink bandwidth.
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...