D-PDD-DY-01: Dell PowerProtect Data Domain DeployDemo

By Dell · Question Mode

QuestionQ20

Post-Deployment

A customer's Dell PowerProtect Data Domain appliance is deployed in a network environment with multiple VLANs: 112, 217, 218, and 310.

After configuring VLAN tagging on veth1 for all four VLANs, the appliance can connect successfully to VLANs 112, 218, and 310, but the connection to VLAN 217 fails.

The VLAN tagging configuration on the appliance has been verified and confirmed to be correct.

What is the cause of the connection failure?

  • A The switch port is not properly configured for the VLAN
  • B The network cable is not connected to the correct switch port
  • C The network card being used does not support four tagged VLAN
  • D The network switch port has not been enabled
Explanation

Because the appliance-side VLAN tagging configuration is confirmed correct and three of the four tagged VLANs pass traffic successfully over the same veth1 trunk interface, the physical cabling and port-enablement can be ruled out as causes (a bad cable or disabled port would affect all VLANs on that interface, not just one). The failure isolated to VLAN 217 indicates that the upstream network switch port has not been properly configured to allow/trunk that specific VLAN, so tagged frames for VLAN 217 are being dropped by the switch.

Community Discussion

No comments yet. Be the first to start the discussion!