Nexus Basic Interview questions:-

Q) Which is implemented first? VPC Keep Alive or VPC Peer Link?

Ans- vPC keepalive to be configure first, once you have configured the keepalive destination address
of switch 2, switch-1 start to send heartbeat messages on every second.

It continues the monitoring, keepalive link also monitor Hearth beat to prevent dual-active scenario,
that peer link is fine or down.

If we configure peer-link first the vpc peer-link will not come up because switch cannot check the
neighbor. Hence we configure keepalive link first.

============================================================

Q) What are the steps to configure VPC?

ANS-

Make sure your Nexus OS support VPC..

Get access of switches management.

enable VPC feature--Nexus(config)# feature vpc

enable lacp feature--Nexus(config)# feature lacp

configure vPC domain-- Nexus(config)# vpc domain 1 (ensure that domain ids match on both
switches)

-- role priority <value>-----You can also configure switch priority for role under domain id to force
vPC role to primary for a

dedicated peer device.

Configure the peer keepalive-- nexux(config-vpc-domain)# peer-keepalive destination 10.10.10.2

source 10.10.10.1 vrf management vpc-keepalive

configure peer-link---configure port-channel and assign ports to channel-group. under the port-
channel configre vpc peer-link.

Nexus(config-vpc-domain)# interface ethernet 1/40-41

Nexus(config-if-range)# channel-group 1 mode active

Nexus(config-if-range)# int po1

Nexus(config-if)# vpc peer-link

Nexus(config-if)# switchport mode trunk

Nexus(config-if)# switchport trunk allowed vlan 1, 40

Configure VPC peer-gateway-- Nexus(config-vpc-domain)# peer-gateway

============================================================

Q) Which physical ports are used for Peer Link?

Ans- Peer-link should configure at least two 10G interfaces in a port channel.

When using a chassis-based switch, be sure to use ports from different line cards, this will provide
you redundancy of link failure situation.

============================================================

Q) How to troubleshoot, If Peer link is flapping?

Ans- 1. Most likely cases- Faulty cable, SFT/FET.

2. In rare cases- faulty switch ports and faulty switch.

3. Flapping under cisco bug..

4. Check counters on the interface to see if traffic is coming across at all?

5. Layer 2 connectivity issue. On interface level there can be many reasons for interfaces flaps.

6. Port-channel flapping, any single link is flapping from configured port-channel.The LACP is not
functioning properly. Mis-configured port-channel on the end device.

7. Check the Compatibility Parameters are identical configured for peer-link.

use command- show vpc consistency-parameters, to to display the configured values on all
interfaces in the vPC.

8. Duplicate mac address are learning from different ports, mac table is being flashed by any reason.

Note- I know you all are well known for interfaces issues, i have skipped...

===========================================================

Q) How to troubleshoot, if Peer Keepalive link is flapping?

ANS- As we know vPC keepalive link carries the heartbeat message between two vPC peer switches
and default hello time is 1 sec.

and you can configure the interval between 400 milliseconds and 10 seconds.

So reason of link flapping- Switches are not recieving response of their hello messages. Check latency
is increasing in between both switches. Keepalive-link Port is flapping,

Physical connectivity issues with in connection between both switches for keepalive link.

Check if your nexus OS is covered keepalive link flapping under cisco known bug.

Keepalive link flapping logs--

2017 Aug 2 09:27:47.718391 CO-DERB-02-V01 %VPC-6-PEER_KEEP_ALIVE_RECV_INT_LATEST: In

domain 2, VPC peer-keepalive received on interface Eth1/47
2017 Aug 2 09:27:47.718450 CO-DERB-02-V01 %VPC-2-PEER_KEEP_ALIVE_RECV_FAIL: In domain 2,
VPC peer keep-alive receive has failed

2017 Aug 2 09:27:47.975636 CO-DERB-02-V01 %VPC-6-PEER_KEEP_ALIVE_RECV_INT_LATEST: In

domain 2, VPC peer-keepalive received on interface Eth1/47

2017 Aug 2 09:27:47.975688 CO-DERB-02-V01 %VPC-6-PEER_KEEP_ALIVE_RECV_SUCCESS: In

domain 2, vPC peer keep-alive receive is successful

===========================================================

Q) How you come to know if VPC is flapping? What type of logs you will get?

ANS- Currently i do not have logs, VPC to be flaps because the interval time 500 timeout 3 times.

Please consider all reasons are mentioned for peer-link.