Home » Cisco » 350-080 » What happens when a module that does not match the resource type is installed?
If the default VDC is configured to limit resources to a specific module type, what happens when a module that does not match the resource type is installed?
A. The module is powered up, and interfaces are in an “admin down” state.
B. The module is denied power, and a syslog message is generated.
C. The module is powered up, and interfaces are allocated to VDC0.
D. The module is powered up, and interfaces are allocated to VDC100.
Correct Answer: C
Explanation/Reference:
Explanation:
Starting with Cisco NX-OS Release 6.2(2), there is no need to support the interoperability of F1 and F2 Series modules in any VDC, either in a dedicated mode or in a shared mode. If you have configured F1 and F2 Series modules as supported line cards in a storage VDC during an In-Service Software Upgrade (ISSU) to Cisco NX-OS Release 6.2(2) or later releases, before ISSU, reconfigure your storage VDC by using the limit-resource module-type command to avoid any unnecessary disruption to the system.
Reference: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/nx-os/virtual_device_context/configuration/guide/b-7k-Cisco-Nexus-7000-Series-NX-OS-Virtual-Device-Context-Configuration-Guide/manage-vdc.html
