LDoms virtual networking, VLANs and resiliency

Scope: Oracle Solaris 11.4 and, for LDoms, compatible SPARC hardware with Oracle VM Server for SPARC. Examples are educational: verify release, privileges, target names and backups before running changes.

How it works

Virtual path

Guest vnet interfaces connect through a virtual switch (vsw) to other guests or a physical uplink. Inside Solaris, configure the interface with ipadm.

VLAN policy

Use port VLAN IDs and tagged VLANs deliberately; do not assume a virtual switch provides firewall segmentation.

Resilience

A guest with one virtual network connected to one service domain has a dependency on that service domain. Separate switches/services and IPMP may reduce single points of failure where supported.

Performance

Measure both guest and service domain, especially when the service domain handles substantial guest traffic.

Worked examples

Each example explains the question it answers, a reproducible starting point, what to look for, and operational precautions.

1. Inspect guest-to-switch mapping

Find which virtual switch serves each NIC.

ldm list-services
ldm list-bindings app01
dladm show-phys

Interpretation: Compare switch uplink to the intended physical network.

Operational note: Run commands in a test environment first; confirm device names, privileges and release-specific options.

2. Add an isolated VLAN-backed NIC

Illustrative guest interface with PVID 120.

ldm add-vnet pvid=120 appnet primary-vsw0 app01
ldm list-bindings app01

Interpretation: The guest receives a virtual interface connected to the configured virtual network.

Operational note: Coordinate VLAN 120 on upstream switches; verify switch security and supported change behavior.

3. Configure Solaris guest IP

Configure a persistent static address on the guest.

dladm show-link
ipadm create-ip net0
ipadm create-addr -T static -a 192.0.2.20/24 net0/v4
ipadm show-addr

Interpretation: Use the actual guest interface name; 192.0.2.0/24 is documentation-only addressing.

Operational note: Do not apply illustrative IP addresses to a live network.

4. Diagnose missing connectivity

Separate link, IP and route failures.

dladm show-link
ipadm show-if
ipadm show-addr
netstat -rn
ping 192.0.2.1

Interpretation: If guest link is present but packets fail, inspect vnet/vsw binding and service-domain physical uplink.

Operational note: Run commands in a test environment first; confirm device names, privileges and release-specific options.

Before you finish

Document physical uplinks and VLAN trunking.
Check whether guest migration constraints include network topology.

Primary documentation

Read the relevant Oracle documentation for exact version-specific flags, supported platforms and limitations: Oracle primary reference ↗.

This field manual is independent, not affiliated with or endorsed by Oracle. Command examples should be adapted to your environment.

Logical Domains: architecture and design →Build a guest LDom from scratch →LDoms virtual disks and ZFS backends →LDom migration: prerequisites and runbook →