You have been asked to troubleshoot the initial configuration of a virtual network connecting two local zones with the outside world. The command dladm create-vnic -1 vswitch192.168.1 vnic1 fails…

Question

Exhibit

Options

• AThe name vswitch192.168.1 is not legal.
• BThe zone must be specified with
• CThe virtual interface must be specified with
• DThe virtual interface must be created with
• EThe virtual switch must be created first with

• A
  3% (1)
• C
  12% (4)
• D
  3% (1)
• E
  82% (28)

Explanation

Option E is correct because dladm create-vnic requires an existing datalink as its -l (link) argument. Since vswitch192.168.1 has never been created in the system, the kernel has no record of it as a valid link - hence "invalid link name." The fix is to first run dladm create-vswitch vswitch192.168.1 (or the equivalent vswitch creation command), then retry the create-vnic command.

Why the distractors are wrong:

• A is a plausible trap - Solaris link names do have character restrictions - but the specific error here signals a non-existent link, not a malformed name string.
• B, C, D are red herrings suggesting missing flags or alternate commands, none of which address the actual missing prerequisite step.

Memory tip: Think of it like a wall socket before a plug - you can't plug a VNIC into a virtual switch that doesn't exist yet. In Solaris virtual networking, always create the switch before the NIC: create-vswitch → create-vnic.

No community discussion yet for this question.