Document Display https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-stat...

Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.

Guest LDOMs cannot talk to primary/control Domain, viceversa but same guest and control domain can talk
with anyone else on the network (Doc ID 1451652.1)

In this Document

Symptoms
Cause
Solution

APPLIES TO:

Solaris Operating System - Version 10 3/05 and later

Information in this document applies to any platform.

SYMPTOMS

Guest logical domains cannot talk to the primary/control domain and viceversa. But the same guest and control domain can talk with any
other domain on the network.

CAUSE

Switch was not configured for this kind of communication.

SOLUTION

The reason is one has not configured the control domain for inter-domain communications.

If one just want guest domains to communicate with the outside world then one should plumb up the switch vsw's.

For eg.

ifconfig vsw0 plumb

If one wants to communicate between the guest domains and the control domain, one will need to replace the primaryinterface for eg
(e1000g0) with vsw0.

For eg.ldm ls -l and ifconfig -a from control and guest domain

#ifconfig -a

Primary/Control domain output:

bash-3.00# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 10.1.2.xx netmask ffffff00 broadcast 10.1.2.255
ether 0:21:28:3f:a3:50

ldm ls -l :(Only switch output)

VSW
NAME MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE
INTER-VNET-LINK
primary-vsw0 00:14:4f:fb:44:fb e1000g0 0 switch@0 1 1 1500 on

Guest domain GD1 output:

#ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000

1 of 2 12-03-2019, 00:51
Document Display https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-stat...

vnet0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 10.1.2.xx netmask ffffff00 broadcast 10.1.2.255
ether 0:14:4f:fa:e8:33

Here are the steps of replacing his e1000g0 with vsw0:

1) First, unbound the guest domain which is using vsw0.

# ldm unbind GD1

whereGD1 is the guest domain bound to that switch.

If you have other guest domains bound to that switch, same command needs to be run for those domains.

2) #mv /etc/hostname.e1000g0 /etc/hostname.vsw0

3) #ldm rm-vsw vsw-e1000g0 primary

4) #ldm add-vsw mac-addr=0:21:28:3f:a3:50 net-dev=e1000g0 vsw-e1000g0 primary

(NOTE: we are giving the mac-address of e1000g0 to vsw0)

5) #ldm add-config newconfig

6)#reboot

7)#ldm list-config (verify it booted off the newconfig, it should say "current")

8) ldm bind GD1

where GD1 is the guest domains bound to that switch. If you have other guest domains bound to that switch, same command needs to be
run for those domains.

9) ldm start GD1

where GD1 is the guest domains bound to that switch. If you have other guest domains bound to that switch, same command needs to be
run for those domains.

Validated network connectivity to primary domain (success!!!)

Didn't find what you are looking for?

2 of 2 12-03-2019, 00:51