Enabling Networking Between the Control/Service Domain andOther Domains

By default, networking between the control domain and other domains in the system is
disabled. To enable this, the virtual switch device should be configured as a network device. The
virtual switch can either replace the underlying physical device (nxge0 in this example) as the
primary interface or be configured as an additional network interface in the domain.
Guest domains can automatically communicate with the control domain or service domain as
long as the corresponding network back-end device is configured in the same virtual LANor
virtual network.

How to Configure theVirtual Switch as the Primary Interface
1. Print the addressing information for all interfaces.
primary# ifconfig -a

2. Configure the virtual switch network interface.
primary# ifconfig vsw0 plumb

3. Remove the physical interface for the device that is assigned to the virtual switch (net-dev).
primary# ifconfig nxge0 down unplumb

4. To migrate properties of the physical network device (nxge0) to the virtual switch device (vsw0),
do one of the following:

■ If networking is configured by using a static IP address, reuse the IP address and netmask of
nxge0 for the virtual switch.
primary# ifconfig vsw0 IP-of-nxge0 netmask netmask-of-nxge0 broadcast + up

■ If networking is configured by using DHCP, enable DHCP for the virtual switch.
primary# ifconfig vsw0 dhcp start

5 Make the required configuration file modifications to make this change permanent.
primary# mv /etc/hostname.nxge0 /etc/hostname.vsw0
primary# mv /etc/dhcp.nxge0 /etc/dhcp.vsw0

Enabling the Virtual Network Terminal Server Daemon
Use the svcadm command to enable the virtual network terminal server daemon, vntsd.
primary# svcadm enable vntsd

Use the svcs command to verify that the vntsd daemon is enabled.
primary# svcs vntsd
STATE      STIME    FMRI
online       Oct_08     svc:/ldoms/vntsd:default

Read More

Rebooting toUse Logical Domains

You must reboot the control domain for the configuration changes to take effect and for the
resources to be released for other logical domains to use.

Shut downand reboot the control domain.
primary# shutdown -y -g0 -i6

Note – Either a reboot or power cycle instantiates the new configuration. Only a power cycle
actually boots the configuration saved to the service processor (SP), which is then reflected in
the list-config output.

Read More

How to Set Up the Control Domain

1. Determine whether you have cryptographic devices in the control domain.
Note that only UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 platforms have
cryptographic devices (MAUs). Because newer platforms, such as SPARC T4 systems and
Fujitsu M10 systems, do not have separate cryptographic units, there is no need to assign a
cryptographic accelerator on these platforms.
primary# ldm list -o crypto primary

2. Assign cryptographic resources to the control domain, if applicable.
The following example would assign one cryptographic resource to the control domain,
primary. This leaves the remainder of the cryptographic resources available to a guest domain.
primary# ldm set-mau 1 primary

3. Assign virtual CPUs to the control domain.
For example, the following command would assign 8 virtual CPUs to the control domain,
primary. This leaves the remainder of the virtual CPUs available to a guest domain.
primary# ldm set-vcpu 8 primary

4. Initiate a delayed reconfiguration on the control domain.
primary# ldm start-reconf primary

5. Assign memory to the control domain.
For example, the following command would assign 4 gigabytes of memory to the control
domain, primary. This leaves the remainder of the memory available to a guest domain.
primary# ldm set-memory 4G primary

6. Add a logical domain machine configuration to the service processor (SP).
For example, the following command would add a configuration called initial.
primary# ldm add-config initial

7. Verify that the configuration is ready to be used at the next reboot.
primary# ldm list-config
factory-default
initial [current]
This ldm list-config command shows that the initial configuration set will be used after
you perform a power cycle.

Create Primary Control Domain:-

root@proddb01:~# svcadm enable ldmd

root@proddb01:~# ldm add-vcc port-range=5000-5100 primary-vcc0 primary

root@proddb01:~# ldm add-vds primary-vds0 primary

root@proddb01:~# ldm add-vsw net-dev=net1 primary-vsw0 primary

root@proddb01:~# ldm list-services primary

root@proddb01:~# ldm set-vcpu 32 primary

root@proddb01:~# ldm start-reconf primary

root@proddb01:~# ldm set-memory 64G primary

root@proddb01:~# ldm add-config initial

root@proddb01:~# ldm list-config

factory-default

initial [current]

root@proddb01:~# shutdown -y -i 6

Read More