P Commands
This chapter describes the Cisco NX-OS commands that begin with P that are used to manage a Cisco Nexus 2000 Series Fabric Extender from a Cisco Nexus 5000 Series switch.
pinning max-links
To specify the number of statically pinned uplinks, use the pinning max-links command. To reset to the default, use the no form of this command.
Syntax Description
Command Default
Command Modes
Fabric extender configuration mode
Command History
|
|
The number of uplinks is extended to 8. Note In releases prior to Cisco NX-OS Release 4.2(1)N1(1), the maximum number of uplinks was 4. |
Usage Guidelines
Use the pinning max-links command when you create a number of pinned fabric interface connections to enable the parent switch to determine a distribution of host interfaces. The host interfaces are divided by the number of uplinks and distributed accordingly.
Examples
This example shows how to specify the number of statically pinned uplinks for a Fabric Extender:
switch#
configure terminal
switch(config)#
fex 101
switch(config-fex)#
pinning max-links 4
This example shows how to revert to the uplink count to the default for a Fabric Extender:
switch#
configure terminal
switch(config)#
fex 101
switch(config-fex)#
no pinning max-links
Related Commands
|
|
---|---|
Creates a Fabric Extender and enters fabric extender configuration mode. |
|
Displays all configured Fabric Extender chassis connected to the switch. |
provision
To preprovision a module in a chassis slot, use the provision command. To remove a preprovisioned module from a slot, use the no form of this command.
no provision model [ model-name ]
Syntax Description
Command Default
Command Modes
Slot configuration mode
Switch profile configuration mode
Command History
|
|
---|---|
Usage Guidelines
Use this command to define the modules (line card or Cisco Nexus 2000 Series Fabric Extender) to preprovision. If the card type does not match the card in the slot or the module is not compatible with the chassis, you see the following messages:
You can configure features or interfaces (Ethernet, Fibre Channel) on the modules before the modules are inserted in the switch chassis. You can also use this command to manage the configuration of these features or interfaces when the module is offline due to a failure or scheduled downtime. These configurations are applied when the module comes online.
When you preprovision a module by specifying the type of module, platform manager will allow only modules of matching type to come online. If you configure the interfaces for the module without specifying the module type, the configuration is applied when the module comes online, regardless of the module type.
You can preprovision modules and interfaces in a switch profile. The modules and interfaces are preprovisioned when you apply (commit) the switch profile. Once the module is inserted and interfaces are created, the preprovisioning module passes on the configuration to the respective applications before the interfaces come up.
Mutual exclusion is a mechanism where configuration outside the switch profile is not allowed in the switch profile and vice-versa. This requirement is to ensure that configuration in the switch profile is exactly the same on both switches. Preprovisioned configuration is the same as a configuration when the module is online, so mutual exclusion checks would continue to apply normally.
When you downgrade from Cisco NX-OS release 5.0(2)N1(1), which supports preprovisioning, to an earlier release of Cisco NX-OS that does not support module preprovisioning, you will be prompted to remove preprovisioning configuration that you configured on the switch.
Examples
This example shows how to preprovision a module in slot 2 of the chassis:
This example shows how to remove a preprovisioned module from a chassis slot:
This example shows how to remove all preprovisioned modules or line cards from a chassis slot:
Related Commands
|
|
---|---|
Displays the running configuration excluding the preprovisioned features. |
|