Filter
Top Products
Version 3.1-en Solaris 10 Container Guide - 3.1 5. Cookbooks Effective: 30/11/2009
5.2. Network
5.2.1. Change network configuration for shared IP instances
[dd] For an already configured zone with a shared IP instance, it may be necessary to change the
physical interface or the network address.
global# zonecfg -z zone1
zonecfg:zone1> info net
net:
address: 192.168.1.1/24
physical: bge1
zonecfg:zone1> select net physical=bge1
zonecfg:zone1:net> set physical=bge0
zonecfg:zone1:net> set address=192.168.2.1/24
zonecfg:zone1:net> info
net:
address: 192.168.2.1/24
physical: bge0
zonecfg:zone1:net> end
zonecfg:zone1> commit
zonecfg:zone1> exit
global#
5.2.2. Set default router for shared IP instance
[dd] In the zone configuration, the default router can be specified for a zone with a shared IP
instance. Using this configuration option ensures that a certain network route is available in the global
zone when a zone is booted (since Solaris 10 11/08)
global# zonecfg -z keetonga
zonecfg:keetonga> select net physical=e1000g0
zonecfg:keetonga:net> set defrouter=1.2.3.1
zonecfg:keetonga:net> info
net:
address: 1.2.3.4/24
physical: e1000g0
defrouter: 1.2.3.1
zonecfg:keetonga:net> end
5.2.3. Network interfaces for exclusive IP instances
[dd] In order to use exclusive IP instances, GLDv3-driver enabled network interfaces or tagged VLAN
interfaces are required and are collectively termed GLDv3-interfaces below. These drivers include:
bge, ce, e1000g, eri, hme, ixgb, nge, nxge, rge, xge. Further details on supported adapters can be
found at: http://opensolaris.org/os/project/crossbow/faq/#ip_instances. The adapters in the system
can be displayed with dladm show-link.
Each exclusive IP instance must have a physical interface or a tagged VLAN interface assigned.
Therefore, the required number of interfaces results from the number of zones with an exclusive IP
instance required. If tagged VLAN interfaces are used, the maximum number of zones within a VLAN
results in the number of physical interfaces required. The reason for this lies in the creation rule for
tagged VLAN interfaces:
Interface = Interfacename<instance + (VLAN-ID * 1000)>
e.g. bge1000 uses the VLAN with ID 1 on bge0
or
bge4003 uses the VLAN with ID 4 on bge3
81