Diags

A detailed illustration depicting a complex network setup with ACI fabric and UCS components, featuring nodes, connections, and data flow illustrating network troubleshooting and management.

ACI Fabric and UCS Knowledge Quiz

Test your knowledge on ACI fabric, UCS management, and network configurations with our comprehensive quiz. This quiz covers various scenarios and troubleshooting techniques essential for professionals working with Cisco technologies.

Assess your understanding of ACI fabric behaviors
Explore configuration and management best practices
Challenge your troubleshooting skills in realistic situations

29 Questions7 MinutesCreated by ConfiguringCloud42

Customer is failure-testing ACI fabric before going into production. During the failure testing some interesting and unexpected behaviour was seen. The issue is escalated to you now.

� None expected behaviour on current version of customer software ISSU and hot standby came out later in version

� Expected behaviour on current version of customer software ISSU and hot standby came out in later version

� Expected behaviour on old version of customer software ISSU and hot standby came out in later version

Why did both the spine supervisors show the (config)# prompt?

� APIC spines have active/active supervisor and will store configuration regardless of APIC cluster status

� APIC clusters determines which supervisor becomes active by round robin

� Since new active supervisor could not download configuration from degraded APIC Cluster

� ACI spines download configuration from previously active supervisor through EOBC

Why did NTP being misconfigured on NTP cluster cause the APIC Cluster not to form? What command must be used to verify?

� With NTP wrong, the APIC Certificates are not valid and services fail to start.

� With NTP wrong, the APIC Certificates are valid and services start.

� ‘acidiag verifyapic’ can be used to verify APIC Certificate date.

'acidiag verifyapic’ cannot be used to verify APIC Certificate date.

What happens when Spine failover

� Leaf standby supervisor is warm standby and will need to download configuration from APIC after active goes down

� Spine standby supervisor is warm standby and will need to download configuration from APIC after active goes down

� Leaf standby supervisor is warm standby and will need to download configuration from APIC after active goes down

What is the next action plan you will propose so the server completes discovery? Or which option to choose to resolve the connection issue?

� Reset server CIMC and reconnect to UCSM

� Unconfigure port and reconfigure as server port

� Unseat the server CIMC and reconnect to UCSM

� Reconfigure port then unconfigure as server port

The customer can’t find the UCSM when he attached 3rd party fc card to the UCS-C server.

� 3rd party FC cards are not supported with UCS-C series integrated with UCSM.

� Connect the FC card directly to SAN outside the UCS

� Connect the FC card to FEX for SAN connectivity

� Connect the FC card to fabric interconnect for SAN connectivity

� Use the cisco vic and create vHBA for SAN connectivity through FI.

Based on provided information what could be the possible reason for connection failure?

� HTTP proxy required to reach Internet but is not configured

� DNS is not configured

� NTP is not configured

� NO valid CA-Signed certificate

What are the 4 necessary things (and steps) when starting implementing Intersight?

� Resolve svc.ucs-connect.cisco.com >>> (look for these key word in your answer) aka the Browser

� Cisco Account (Cisco ID)

� Use required license

� Single account for all platform

Question: which Vlan

� Admin PC in vlan 401 won’t be able to reach any networks connected to remote VTEP.

� Admin PC in vlan 301 won’t be able to reach any networks connected to remote VTEP.

� Admin PC in vlan 501 won’t be able to reach any networks connected to remote VTEP.

� Admin PC in vlan 601 won’t be able to reach any networks connected to remote VTEP.

Which command to see all learned hosts addresess information on VTEP (MAC, IP, Next-hop VTEP)

� Show l2route evpn all

� show mac l2route evpn all

� show evpn l2route all

� show l2route evpn mac-ip all

� show l2route evpn mac all

Which command on VTEPs would be the best to help TAC engineer confirm his findings from the collected captures? (two possible answers depending on evidence given, what are these 2?)

� Debug nve error

� show nve vxlan-params

� show vxlan interface

� show nve vni interface nve1 detail

1. When Looking at the “Show npv flogi-table’ output on both fabric interconnects we see that the tables are empty. This behaviour is consistent while the service profile is booting and we seem to be unable to perform a flogi. What is the cause of this?

� The NPV feature is not enabled on the bdsol-n5548-51 and bdsol-n5548-52 switch.

� VSAN 1 is configured with an incorrect fcoe-vlan

� We need to enable FC Uplink Trunking

� When using FCoE no flogies are used, this is only seen when doing FC

2. After Correcting the Previous Question, the Customer is seeing flogies on bdsol-n5548-02. What is the cause of this?

� We are using interface ¼ on FI-B where we should be using interface 1/3

� Int vrf 112 on bdsol-n5548-02 should be configured with vsan 980

� Bdsol-n5548-02 eth 1/12 is not configured with vlan 980

� Interface ¼ should be using FCoE VLAN 80

3. After correctly the previous question, we can see the correct flogies happening but now we are unable to discover the targets. What is causing this?

� The SAN administer forgot to activate the zoneset, the provide output is not from “show zoneset activate” but from “show zoneset”

� There is mistake in the boot policy, we should be using wwn 56:69:CE:90:4F:A6:B7:02 and 56:C9:CE:90:4F:A6:B7:04

� There is a mistake in the device-alias database on bdsol-n5548-02, we should be using 56:69:CE:90:4F:A6:B7:01 and 56:C9:CE:90:4F:A6:B7:03

� The storage device is not logged into the fabric and hence it cannot be discovered by the blades

4. After having booted the first two blades with service profiles, the customer now would like to install 6 more blades in the UCS chassis. Although he can see these blades booting by checking the flogi tables on the switches, he cannot connect to the KVMs. How can he correct the KVM connection issue?

� The customer should shut down the first 2 blades which will allow the UCSM to re-use these IPs on the new blades.

� The customer should move the IP addresss used for the DVMs by modifying the ext-mgmt ip pool.

� The customer needs to enable in band management by creating an inband IP Pool, VLAN, VLAN group, inband profiles and then enable this on the CIMC of the blade.

� The KVM IP space is only a /29 and hence has no space left. He should add 1 more /29 or bigger network to the UCS management interface.

5. The customer has added 2 different uplinks to the UCSM system (1 going to the legacy network and 1 going to the production network) and is using VLAN-groups to properly manage which VLAN is configured where (L2 disjoint). The morning however he received the error “ENM source pinning Failed” on all his service-profiles and he has lost all connectivity towards his production system. What is causing the “ENM source Pinning Failed” fault.

� An administrator has deleted a VLAN on an uplink interface in the VLAN group hence causing the linked vnic-templates which was using this VLAN to go into “ENM source pinning failed”.

� The switches managing the legacy network have been brought down and due to the “Action on uplink fail: linkdown” configured on the service-profile through the network control policy; the vnics go into “ENM source pinning failed”.

� Not all the VLANs which are a member of the VLAN group legacy have been added on the Legacy vNIC on the Service profiles.

� FI-6234-A failed hence causing the vNICs to loose the uplink connectivity which trigger the “ENM source pinning failed”.

You are working in the ACME corporate support team and one of your responsibilities is to provide second-level support to the ACME helpdesk. The ACME helpdesk just opened a case with your team and needs help with vPC and vPC+. Use the resources provided below and make a choice for each question that follows:

� The ping request destination MAC address is not standard

� The ping reply source MAC address is not standard

� The data is wrong and the switch drop the packet cdab0000cdab000cdat000cdab000cdab000

� The ping request source MAC address is not standard

� The packet has the wrong protocol in the frame eth ip icmp data

� The packet destination MAC address is not standard

2. What is the source of the problem is how can the problem be fixed?

� Configure the system mac to be different one

� Routing issue configure a static ip route on the Nexus7k1 and Nexus7k2

� Configure the feature peer gateway on both nexus 7000

� Configure the feature peer switch on both nexus 7000

� Replace the cable on the non working Nexus 7000

3. By looking at the configuration of the two nexus 7000 there is a security concern?

� vPC Auto recovery sstatus needs to be disabled

� Nexus7k1 has a Control Plane Policing simple profile

� Control Plane Policing is not configured on Nexus7k2

� vPC keepalive is wrongly configured and currently not working

4. Why the connection between the Nexus 7000 and the storage device were broken after enabling vPC+

� The vPC+ switch id cannot be the same as the vPC domain id

� There is a unidirectional link that caused the spanning tree interface to go into blocking

� The Nexus7k1 and the Nexus7k2 are not the STP root for VLAN 10

� The connection will go into forwarding soon because the spanning-tree output we see this bridge is the root

� There is a protocol mismatch rSTP cannot be used with vPC+

5. After Fixing the issue what will happen with the link from the Spanning Tree point of view and how loops between the STP domain and the FP domain will be prevented

� One link will be forwarding and one blocking this will prevent loops. The device with the lower MAC will put the link into forwarding

� Both links will be forwarding but only Nexus7k1 will forwarding Broadcast Multicast Unknown Unicast

� One link will be forwarding and one blocking this will prevent loops. The device with the Higher MAC will put the link into forwarding.

� Both links will be forwarding fabricpath will take care of loops.

� Both links will be forwarding but only Nexus7k2 will forward broadcast/multicast/unknown unicast

Unlock and Upgrade

Remove all limits from your Quizzes

Diags

ACI Fabric and UCS Knowledge Quiz

More Quizzes