My Oracle Support Banner

Working out ldom's guest vnet to physical device (Doc ID 1528250.1)

Last updated on APRIL 18, 2023

Applies to:

Solaris Operating System - Version 11 to 11.1 [Release 11.0]
Information in this document applies to any platform.

Symptoms

It can sometime get confusing which interface points to which vSwitch (vsw) and is backed by which physical interface on the Control/Service domain, even more so with renaming virtual NIC and using VLAN's.This document describes commands and steps to understand guest domain network topology  using  "dladm show-phys" , "ldm ls -al" outputs.     

Example: 

The system is running ,Oracle Solaris 11.1 SRU 2.5.The administrator named vnets "vnet#" however he didn't follow the usual procedure and start with zero, instead he started with 1. So when he looked at dladm show-phys and the first network was listed as using vet1, however the MAC address was correct for Device ID 0.


1. First the Control/Service domain virtual networking output :-

# ldm list -o network

NAME
primary

MAC
   xx:yy:zz:10:46:ea

VSW
   NAME             MAC                        NET-DEV   ID   DEVICE     LINKPROP   DEFAULT-VLAN-ID PVID VID                  MTU   MODE   INTER-VNET-LINK
   primary-vsw0     xx:yy:zz:fb:cd:1c  ixgbe0     0    switch@0   phys-state 1               2        222,102,103            1500             on
   primary-vsw1     xx:yy:zz:fa:b8:d0  ixgbe1     1    switch@1   phys-state 1               102     222,2,103               1500             on

------------------------------------------------------------------------------
NAME
Guest

MAC
   xx:yy:zz:f9:04:68

NETWORK
   NAME             SERVICE                           ID   DEVICE          MAC                         MODE   PVID VID                  MTU   LINKPROP
   vnet1            primary-vsw0@primary      0    network@0  xx:yy:zz:f8:a4:dd        222  102,103              1500
   vnet2            primary-vsw1@primary      1    network@1  xx:yy:zz:fa:01:c7        102  222,103,2            1500
   vnet3            primary-vsw0@primary      2    network@2  xx:yy:zz:f9:34:09        222  102,103              1500
   vnet4            primary-vsw1@primary      3    network@3  xx:yy:zz:fa:aa:52        102  222,103,2            1500

on the LDOM control domain, please note the vnet names, device ID's and MAC addresses.

From Guest LDOM, dladm show-phys output and ifconfig out put for those devices.
note that net0 lists the device as vnet0 and has a MAC address for vnet1 as shown in the previous post.

# dladm show-phys
LINK              MEDIA                STATE      SPEED  DUPLEX    DEVICE
net2              Ethernet             up             0         unknown   vnet2
net3              Ethernet             up             0         unknown   vnet3

Notice here that as this is solaris 11.x guest ldom net0 is vanity name of device "vnet0"

root@Guest:~# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
       inet 127.0.0.1 netmask ff000000
net2: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
       inet  xx.xx.xx.xx netmask ffffff00 broadcast xx.xx.xx.255
       ether xx:yy:zz:f9:34:9
net3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
       inet xx.xx.xx.xx netmask ffffff00 broadcast xx.xx.xx.255
       ether xx:yy:zz:fa:aa:52
[..]

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
 Example: 
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.