Q15Network
Refer to the exhibit. Which action finalizes the vPC domain implementation?
← → navigate · a answer
Community votes
Discussion · 18
A 4
Selected Answer: A
Technically both A & C are right. But I would go with A as it's clearly missing memebrs.
A 4
Selected Answer: A
You don't need to create another VRF, VRF mgmt already exists by default and the int mgmt0 is already a member of the VRF, so C is incorrect.
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/6-x/interfaces/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Interfaces_Configuration_Guide/b_Cisco_Nexus_9000_Series_NX-OS_Interfaces_Configuration_Guide_chapter_0111.html
A 3
Selected Answer: A
A is correct, vpc peer link port channel is missing it's members eth1/1 and eth1/2
A 3
Selected Answer: A
A is correct
3
A is correct.. all vlans are enable by default in vpc peer link
3
Answer is "C"
A 3
Selected Answer: A
A is correct.because vPC need
C 2
Selected Answer: C
Correct answer is C...by default all vlans are added to trunks, so they will not stop the VPC config from working. However, the keepalive will not work as configured because the vrf is not specified.
C 2
Selected Answer: C
As we are using mtmt links for keepalive of VPC we have to specify VRF management (mgmt link vrf) in vpc config. Otherwise the keep alive link will not work. The question is about VPC domain implementation and not about allowing vlan's through it or configuring VPC on specific ports, so A and D are wrong. Mac on VPC domain is wrong too.
2
Correct to me is B
The question is about vPC domain implementation? If so, the vpc domain is missing the vrf information:
peer-keepalive destination 10.10.10.2 source 10.10.10.1 "vrf management" <---
Without this, keepalive won't work and the domain won't form.
Allowing vlans - by default all vlans are allowed - so D is incorrect.
Adding members to the vPC - if the vPC domain is not formed first, this is not relevant.
A 1
Selected Answer: A
The interfaces need to be added to the Portchannel. Configuring allowed VLANs on the vPC peer-link is optional.
A 1
Selected Answer: A
A is correct. Portchannel is missing ports
A 1
Selected Answer: A
A is correct. Portchannel is missing ports
1
Member ports are ports going down to servers, other switches, etc.. The ports that are missing the port-channel info are for the peer-link (not member ports).. answer has to be C
1
A is correct!! The rest of the responses are incorrect and non-sense for vPC config
1
must be C, peer-keepalive destination ipaddress source ipaddress | vrf {name | management vpc-keepalive}
Configures the IPv4 and IPv6 addresses for the remote end of the vPC peer-keepalive link.
https://www.ciscopress.com/articles/article.asp?p=3150966&seqNum=2
and https://www.letsconfig.com/how-to-configure-cisco-nexus-vpc/
1
Sorry - I meant C
1
management port and management VRF are the defaults for keepalive.
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/93x/interfaces/configuration/guide/b-cisco-nexus-9000-nx-os-interfaces-configuration-guide-93x/b-cisco-nexus-9000-nx-os-interfaces-configuration-guide-93x_chapter_01000.html#task_BF54587CCA544A70A100104CFBFE4B03