
PowerEdge Servers Error and Event Messages Reference Guide
NVUP—Uplink Event Messages
NVUP0001
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to configure the uplink because the configuredinterface arg1 does not exist.
- Arguments
- arg1 = interface name
- Detailed Description
- The uplink cannot be configured because the ConfiguredInterface identified in the message is not present.
- Recommended Response Action
- Enter a valid configuredinterface and retry the operation.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0002
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to configure the ConfiguredInterface arg1 as an uplink because it is already being used.
- Arguments
- arg1 = interface name
- Detailed Description
- The configuredinterface mentioned in the message cannot be configured as uplink because it is already being used.
- Recommended Response Action
- Enter another configuredinterface and retry the operation.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0003
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to configure the ConfiguredInterface arg1 as an uplink because it is not of Type Physical.
- Arguments
- arg1 = interface-name
- Detailed Description
- The configuredinterface mentioned in the message, cannot be configured as an uplink because it is not of Type Physical.
- Recommended Response Action
- Enter a configuredinterface of Type Physical and retry the operation.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0004
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to modify the configured interfaces for FC/FCoE/FCGateway uplink as they cannot be modified.
- Detailed Description
- The configured interfaces for FC/FCoE/FCGateway uplink cannot be modified or deleted.
- Recommended Response Action
- To modify the configured interfaces of uplink, please delete the uplink and create the uplink with desired interfaces.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0005
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to configure or update the Uplink because the Uplink configured with MediaType as Fiber Channel (FC) or Fiber Channel over Ethernet (FCoE) must have only one VLAN for the configured interfaces.
- Detailed Description
- The uplink cannot be configured or updated because the Uplink configured with MediaType as Fiber Channel (FC) or Fiber Channel over Ethernet (FCoE) must have only one VLAN for the configured interfaces.
- Recommended Response Action
- Make sure that the Uplink has only one VLAN for the configured interfaces.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0006
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to configure uplink because multiple Fiber Channel or storage uplinks are not supported.
- Detailed Description
- Uplink cannot be configured because only one Uplink of MediaType FiberChannel(FC) or FiberChannelOverEthernet(FCOE) and one uplink of MediaType iSCSI(storage uplink) is supported for the given Fabric.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0007
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to configure the uplink because the uplink does not exist.
- Detailed Description
- The uplink cannot be retrieved because the uplink identified in the message does not exist.
- Recommended Response Action
- Enter a valid uplink and retry the operation.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0008
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to configure or update the uplink because the media type entered is not supported.
- Detailed Description
- The uplink cannot be configured because the media type entered is not supported.
- Recommended Response Action
- Enter an uplink with the supported media type and retry the operation.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0009
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to configure the uplink because the FCoE Initiation Protocol(FIP) network is already used in this fabric.
- Detailed Description
- The Uplink cannot be configured because the FCoE Initiation Protocol (FIP) network is already used in this fabric. Two FC uplinks on the same fabric cannot have the same network.
- Recommended Response Action
- Enter an uplink with a different FIP network and retry the operation.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0010
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to configure the Uplink because a Layer3-routed network is configured (as a tagged network) on the uplink.
- Detailed Description
- The Uplink cannot be configured because a Layer3-routed network is configured (as a tagged network) on the uplink.
- Recommended Response Action
- Remove the Layer3-routed network from the tagged network list on the uplink, and then retry the operation.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0011
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to update the Uplink because the Link Aggregation Group (LAG) type of the Uplink cannot be modified.
- Detailed Description
- The Uplink cannot be updated because the Link Aggregation Group (LAG) type of the Uplink cannot be modified.
- Recommended Response Action
- To modify the Link Aggregation Group (LAG) type, delete the Uplink, and then create a new Uplink by using the desired LAG type.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0012
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to configure the Uplink because the Uplink ID arg1 already exists.
- Arguments
- arg1 = uplink ID
- Detailed Description
- The Uplink cannot be configured because the Uplink ID identified in the message already exists.
- Recommended Response Action
- Enter a new Uplink ID and retry the operation.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0013
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or update the Uplink because the network arg1 is configured as of both tagged and untagged types.
- Arguments
- arg1 = network ID
- Detailed Description
- The Uplink cannot be created or updated because the network identified in the message is configured as of both tagged and untagged types.
- Recommended Response Action
- Configure the network as either tagged or untagged, and then retry the operation.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0014
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to configure the uplink because the selected untagged VLAN ID arg1 is already in use on uplink arg2 in the SmartFabric.
- Arguments
- arg1 = Vlan ID
- arg2 = uplink name
- Detailed Description
- The uplink cannot be configured because the selected untagged VLAN ID is already in use on an existing uplink in the SmartFabric.
- Recommended Response Action
- Configure the uplink with an untagged VLAN ID which is not already in use on other uplinks in the SmartFabric and retry the operation.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0015
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to configure the uplink because the selected tagged network arg1 is already in use on uplink arg2 in the SmartFabric.
- Arguments
- arg1 = network name
- arg2 = uplink name
- Detailed Description
- The uplink cannot be configured because the selected tagged network is already in use on an existing uplink in the SmartFabric.
- Recommended Response Action
- Configure the uplink with a tagged network which is not already in use on other uplinks in the SmartFabric and retry the operation.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0016
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create Ethernet-No Spanning Tree uplink arg1 because Ethernet-No Spanning Tree and legacy Ethernet Uplinks cannot co-exist in the same SmartFabric.
- Arguments
- arg1 = Uplink name
- Detailed Description
- The Uplink cannot be created because Ethernet-No Spanning Tree and legacy Ethernet Uplinks cannot co-exist in same SmartFabric.
- Recommended Response Action
- To create a Ethernet-No Spanning Tree Uplink, delete the existing legacy Ethernet Uplinks and retry the operation. For more information, see the PowerEdge MX SmartFabric Configuration and Troubleshooting Guide.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0017
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create Ethernet Uplink arg1 because Ethernet and Ethernet-No Spanning Tree Uplinks cannot co-exist in the same SmartFabric.
- Arguments
- arg1 = Uplink name
- Detailed Description
- The Uplink cannot be created because Ethernet-No Spanning Tree and legacy Ethernet Uplinks cannot co-exist in same SmartFabric.
- Recommended Response Action
- To create a Ethernet uplink, delete the existing Ethernet- No Spanning Tree Uplinks and retry the operation. For more information, see the PowerEdge MX SmartFabric Configuration and Troubleshooting Guide.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0018
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the Ethernet-No Spanning Tree uplink arg1 because the switches in SmartFabric arg2 are running Rapid per VLAN Spanning Tree (Rapid PVST).
- Arguments
- arg1 = uplink name
- arg2 = fabric name
- Detailed Description
- The Ethernet-No Spanning Tree Uplink identified in the message cannot be created because the switches in the SmartFabric are running Rapid per VLAN Spanning Tree (Rapid PVST).
- Recommended Response Action
- Configure Rapid Spanning Tree Protocol (RSTP) as the mode of STP for SmartFabric switches, and then retry the operation. Run the following command at the Command Line Interface (CLI): "spanning-tree mode rstp". For more information, see the PowerEdge MX SmartFabric Configuration and Troubleshooting Guide.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0019
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the Ethernet-No Spanning Tree Uplink because FCoE Uplinks in SmartFabric arg1 have the same untagged VLAN arg2.
- Arguments
- arg1 = fabric name
- arg2 = VLAN ID
- Detailed Description
- The Ethernet-No Spanning Tree Uplink cannot be created because the FCoE Uplinks in the SmartFabric must have different untagged VLAN. For more information, see the PowerEdge MX SmartFabric Configuration and Troubleshooting Guide.
- Recommended Response Action
- Configure a different untagged VLAN for each FCoE Uplink, and then retry the operation.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0020
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or configure the Uplink because FCoE network arg1, is selected as the tagged network.
- Arguments
- arg1 = network name
- Detailed Description
- The Uplink cannot be created or configured because the FCoE network identified in the message is selected as the tagged network.
- Recommended Response Action
- To create or update an Ethernet or Ethernet-No Spanning Tree Uplink, select only non-FCoE networks as the tagged networks, and then retry the operation.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVUP0021
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or configure the FCoE Uplink because more than one port are selected.
- Detailed Description
- The FCoE Uplink cannot be created as more than one port are selected.
- Recommended Response Action
- To create or update an FCoE Uplink , select only one port.
- Category
- Configuration (NVUP = Uplink)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\