Configuring IP interfaces enables a system to connect to the network. The procedure essentially involves assigning IP addresses to the interfaces.

When you assign an IP address to an IP interface, a corresponding address object is created to represent that address.

The address object uses the format interface/address-family, where address-family is either v4 or v6. For example, net0 with an IPv4 address would have the address object net0/v4. Multiple address objects of the same IP interface are distinguished by a letter suffix, such as net0/v4a, net0/v4b, net0/v4c, and so on.

Similarly, an IP interface with IPv6 addresses would have address objects such as net1/v6a, net1/v6b, and so on.

Any subsequent command on this interface's address can use the address object as reference. For instance, using an address object from the previous examples, you would type ipadm delete-addr net0/v4b.

How to Configure an IPv4 Interface

Before You Begin

Ensure that your role has the appropriate rights profile to perform this procedure. See Using Rights Profiles to Perform Network Configuration.

1. Create the IP interface.

   $ ipadm create-ip interface

   The interface name follows the datalink name on which the interface is created.

   This syntax is the most commonly used to configure networking on a system. However, two other create subcommands are available for other types of configuration:

   • create-vni creates a STREAMS virtual network interface.

   • create-ipmp creates an IPMP group. See Chapter 2, About IPMP Administration in Administering TCP/IP Networks, IPMP, and IP Tunnels in Oracle Solaris 11.4.

2. Configure the IP interface with a valid IP address.

   Use one of the following commands depending on the type of address:

   • Create a static address

     $ ipadm create-addr -a IP-address interface

     The address can be in Classless Inter-Domain Routing (CIDR) notation.

   • Configure a dynamic address.

     $ ipadm create-addr -T dhcp interface

3. Display information about the system's IP interfaces.

   $ ipadm

   See also Monitoring IP Interfaces and Addresses that show how to obtain interface information by using show-* subcommands.

4. If you are configuring a static IP address that uses a host name, add the entries for the IP address to the /etc/hosts file.

   The entries in this file consist of IP addresses and their corresponding host names.

   ---

   Note -  DHCP configurations do not require updates to the /etc/hosts file.

   ---

Example 2  Configuring an IPv4 Interface With a Static IP Address

The following example shows how to configure an IPv4 interface with a static IP address. The example also shows how to configure a persistent route for the interface by using the route command.

$ dladm show-phys
LINK     MEDIA        STATE     SPEED     DUPLEX     DEVICE
net3     Ethernet     up        100Mb     full       bge3

$ dladm show-link
LINK     CLASS     MTU     STATE     OVER
net3     phys      1500    up        --       --

$ ipadm create-ip net3
$ ipadm create-addr -a 192.0.2.3/24 net3
net3/v4

$ ipadm
NAME              CLASS/TYPE STATE        UNDER      ADDR
aggr0             ip         down         --         --
lo0               loopback   ok           --         --
   lo0/v4         static     ok           --         127.0.0.1/8
   lo0/v6         static     ok           --         ::1/128
net3              ip         ok           --         --
   net3/v4        static     ok           --         192.0.2.3/24

$ vi /etc/hosts
# Internet host table
# 127.0.0.1     localhost
203.0.113.14    foohost
192.0.2.3       sales1

Example 3  Configuring a Network Interface to Receive an IP Address From a DHCP Server

In the following example, the IP interface is configured to receive its address from a DHCP server. DHCP typically also installs a default route. Therefore, this example does not include a step for manually adding a default route by using the route command.

$ dladm show-phys
LINK     MEDIA        STATE     SPEED     DUPLEX     DEVICE
net3     Ethernet     up        100Mb     full       bge3

$ dladm show-link
LINK     CLASS     MTU     STATE     OVER
net3     phys      1500    up        --       --

$ ipadm create-ip net3
$ ipadm create-addr -T dhcp net3
net3v4

$ ipadm
NAME              CLASS/TYPE STATE        UNDER      ADDR
aggr0             ip         down         --         --
lo0               loopback   ok           --         --
   lo0/v4         static     ok           --         127.0.0.1/8
   lo0/v6         static     ok           --         ::1/128
net3              ip         ok           --         --
   net3/v4        static     ok           --         203.0.113.3/24

Create LDOM
# ldm add-domain DB01
# ldm add-vcpu 8 DB01
# ldm add-memory 16G DB01
# ldm add-vnet vid=98,99 vnet01 primary-vsw-core DB01

Create Volume Disk
# zfs create -V 100gb ldom-pool/DB01-OS

Create Alias
# ldm add-vdsdev /dev/zvol/dsk/ldom-pool/DB01-OS DB01-OS@primary-vds0
# ldm remove-vdsdev ldomweb_disk9 /dev/dsk/c13t5006016936E02582d0s2

Add Disk to LDOM
# ldm add-vdisk vdisk1 DB01-OS@primary-vds0 DB01

Remove Disk from LDOM
# ldm remove-disk vdisk9 ldom-web

Add ISO to LDOM
# ldm add-vdsdev options=ro /source/sol-11_4-text-sparc.iso iso@primary-vds0
# ldm add-vdisk sol11_iso iso@primary-vds0 DB01

Check Config LDOM
# ldm list-bindings DB01

Listing LDOM
# ldm list
# ldm bind DB01
# ldm start DB01

Setting variables
# ldm set-var auto-boot?=true ldom01
# ldm set-var boot-device=vdisk1 ldom01

List the resource for all LDOMs and per LDOM
# ldm list -o cpu primary
# ldm list -o network,memory ldom01

List all server resources
# ldm list-devices -a
# ldm list-devices mem

Remove ISO / Disk from LDOM
# ldm rm-vdisk iso11 ldom-DB01

Before You Begin

To collect SP data using the Service Snapshot utility, you need the Admin (a) role enabled.

1. Log in to the Oracle ILOM CLI.
2. Type the following commands:

   ->set /SP/diag/snapshot dataset=data

   ->set /SP/diag/snapshot dump_uri=URI

   where data and URI are one of the following:

   
   

   Value Option Header data normal Specifies that the Oracle ILOM, operating system, and hardware information is collected. full Specifies that all data is collected (“full” collection). Note - Using this option might reset the running host. normal-logonly or full-logonly Specifies that only log files are collected. URI Any valid target directory location Specifies the URI of the target directory. The URI format is as follows: protocol://username:password@host/directory where protocol can be one of these transfer methods: SFTP or FTP. For example, to store the snapshot information in the directory named data on the host, define the URI as follows: ftp://joe:mypasswd@host_ip_address/data The directory data is relative to the user login, so the directory would probably be /home/joe/data.

   The snapshot places a zip file in the specified URI.

3. Unzip the file to access the data produced by the snapshot

This procedure requires Administration (a) permission.

1. Log in to the Oracle ILOM web interface.
2. Select Snapshot from the Maintenance tab.

   The Service Snapshot Utility screen appears.

   
   
3. Select the data set you want: Normal, FRU ID, Full, or Custom.
   • Normal – Specifies that Oracle ILOM, operating system, and hardware information is collected.
   • FRU ID – Provides FRU ID information.
   • Full – Specifies that all data is collected. Selecting Full might reset the system.
   • Custom – Allows you to choose one or more of the following data sets:

     • Oracle ILOM data

     • Hardware data

     • Basic OS data

     • Diagnostic data

4. Select the Enabled check box if you want to collect only log files from the data set.
5. Select the Enabled check box if you want to encrypt the output file.
6. Select one of the following methods to transfer the output file:

   • Browser

   • SFTP

   • FTP

7. Click Run.

   A Save As dialog box appears.

8. In the dialog box, specify the directory to which to save the file and the file name.
9. Click OK.

   The utility places a zip file in the specified directory.

10. Unzip the file to access the data produced by the snapshot.

With Solaris 11, Oracle introduces the new zpool split command to split the ZFS pool (SPARC / x86 ). This comes in handy to increase the size of the rpool. Below are the high level steps involved :

Steps Involved

1. attach a mirror device to the rpool
2. reboot off the mirror (to verify everything works).
3. split the original disk from the pool.
4. set the “autoexpand” property of the rpool

Detailed procedure

1. Assuming that your initial rpool has the disk c0t0d0s0 and that you have a new disk c1t1d0s0 that is the size that you want to expand to. We will attach the new device c1t1d0s0 to the exisitng rpool.

# zpool attach rpool c0t0d0s0 c1t1d0s0

2. Now wait for the resilvering to complete. You can track this with :

# zpool status rpool

3. At this point, you can reboot from the mirror disk to verify that it works.
– On Sparc, you can do this by setting OBP to boot from the mirror disk c1t1d0s0, e.g.:

# init 6      ( or init 0 if you have autoboot set to true)
ok> boot /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/disk@1

– On x86, you would configure the system BIOS.

4. And then we detach the old sub-mirror.

# zpool split rpool oldrpool c0t0d0s0

Now if you look at the pool it will show only one device (the new disk) but at the old size. You will also see a pool called “oldrpool” with the old disk that we split off. At this point, you should be able to boot from either of the two disks, but each will be a distinct rpool.

5. In order to expand the rpool size to that of the new disks we added, we need to tell zfs to expand to the capacity of the new disk. To do so, we have to set the autoexpand property on.

# zpool set autoexpand=on rpool

Use the following procedure if you need to preserve the IP configuration that is associated with one network device and then move that configuration to another network device. You might perform this procedure prior to removing a network card from the system or when changing a network cable connection.

The procedure uses e1000g0 and nge0 as sample devices.

Before You Begin

Ensure that your role has the appropriate rights profile to perform this procedure. See Using Rights Profiles to Perform Network Configuration.

1. Display the physical link to device mappings on the system.

   The following example shows that the IP configuration for e1000g0 is down and the configuration needs to be moved to nge0:

   $ dladm show-phys
   LINK    MEDIA    STATE    SPEED    DUPLEX    DEVICE
   net0    Ethernet down     0        unknown   e1000g0
   net1    Ethernet down     0        unknown   e1000g1
   net2    Ethernet up       1000     full      nge0
   net3    Ethernet down     0        unknown   nge1
   

2. Disable the IP configuration on the datalink temporarily, leaving its persistent settings intact.

   For example:

   $ ipadm disable-if net0

3. Rename the datalink of the device that is down.

   For example:

   $ dladm rename-link net0 oldnet0

   This step makes oldnet0 as the link name of e1000g0.

4. Assign the primary link name to the datalink that is designated to become the primary device.

   For example, net2 is the link name of the nge0 device. Thus, you would type:

   $ dladm rename-link net2 net0

5. Re-enable the IP configuration on the newly named datalink (net0).

   $ ipadm enable-if -t net0

How to Set Up an NTP Server

1. Become an administrator.

   For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: Security Services.

2. Create the ntp.conf file.

   To ensure proper execution of the ntpd daemon, the ntp.conf file must first be created. The ntp.client file can be used as a template.

   # cd /etc/inet
   # cp ntp.client ntp.conf
   
   

3. Read the ntp.server file.

   If needed, add more information to the ntp.conf file.

4. Edit the ntp.conf file.

   Make site specific changes to this file as needed.

5. Start the ntpd daemon.

   # svcadm enable ntp

How to Set Up an NTP Client

1. Become an administrator.

   For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: Security Services.

2. Create the ntp.conf file.

   To activate the ntpd daemon, the ntp.conf file must first be created.

   # cd /etc/inet
   # cp ntp.client ntp.conf

3. Edit the ntp.conf file.

   Make site specific changes to this file as needed.

4. Start the ntpd daemon.

   # svcadm enable ntp

How to Enable NTP Logging

1. Become an administrator.

   For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: Security Services.

2. Enable logging.

   # svccfg -s svc:/network/ntp:default setprop config/verbose_logging = true

   See the svccfg(1M) man page for more information.

3. Update the SMF repository and restart the service.

   # svcadm refresh svc:/network/ntp:default
   # svcadm restart svc:/network/ntp:default 

4. Verify that logging has been enabled.

   # svcprop -p config/verbose_logging svc:/network/ntp:default
   true

How to Display the SMF Properties Associated With the NTP Service

• List the SMF properties.

  • To list all of the properties associated with the NTP service, type:

    # svcprop svc:/network/ntp:default

  • To list all of the properties in the config property group, type:

    # svcprop -p config svc:/network/ntp:default

Hello, if you are removing a hard drive while the operating system is still running,