sun.com | docs.sun.com |  | How To Buy | My Sun | Worldwide Sites |

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

File Formats | network.conf(4)

- NAME
- SYNOPSIS
- DESCRIPTION
- PARAMETERS
- EXAMPLES
- ATTRIBUTES
- SEE ALSO

## NAME

> network.conf - SMCT configuration file to define the network parameters for the cluster

## SYNOPSIS

> `SMCT_CONFIG_DIR/models/network.conf`
> `smct-config-dir/models/network.conf`

## DESCRIPTION

> Do not use the SMCT tool with the current patch level of the Foundation Services product.

> Configure the `network.conf` file to define specific network information used by the target cluster. This includes IP addresses, network, and netmask information for physical and virtual cluster network interfaces, and default routes used to access the cluster.

> A pre-configured `network.conf` template file for each example hardware configuration is available in the `/opt/SUNWcgha/nhsmct/etc/models/` directory.

## PARAMETERS

> The following are the parameters of the `network.conf` file:

> >     { ELEMENT network name type network-type number network-number
> >     netmask network-netmask
> >     }+

> >     { ELEMENT ip name address ip-address type ip-type {alias name}*
> >     	BELONG_TO network name}+

> >     { ELEMENT router name
> >     	USE ip name}+

> - name

>   Unique ID as an ASCII string.

> - network-type

>   Network type. This parameter must be set to `IPV4`.

> - network-number

>   IP network number in standard IP network number format (dotted notation), for example, `10.101.1.0`.

> - network-netmask

>   IP network netmask in standard IP network netmask format (dotted notation), for example, `255.255.255.0`.

> - ip-type

>   IP address type. This can be one of the following:

>   - `FLOATING`

>     The floating address triplet of the master node referenced by the configuration element `domain` in `cluster.conf` file. Alternatively, you can specify the floating address used by the Node State Manager, which is defined in the `cluster.conf` file.

>   - `STATIC`

>     All IP addresses that are not of type `FLOATING`.

> - ip-address

>   IP address in standard IP address format (dotted notation), for example, `10.101.1.10`.

>   You can choose to configure IP addresses of any class for your nodes. However, the following rules apply:

>   - The nodeid in the `cluster.conf` file must be a decimal representation of the host part of the corresponding IP address.

>   - The host part of the IP address for the NIC0, NIC1, and `cgtp0` interfaces of a node must be the same.

## EXAMPLES

> The following is an example of a `network.conf` file for a four-node cluster:

> >     # ---------------------------------------------------------
> >     #   ident "@(#)network.conf.4N.tmpl 1.5"
> >     # -----------------------------------------------------------------
> >     #      - 4 nodes reference platform network definition template -
> >     # ------------------------------------------------------------------
> >     #
> >     ELEMENT network phys-A type IPV4 number 10.101.1.0 netmask 255.255.255.0
> >     ELEMENT network phys-B type IPV4 number 10.101.2.0 netmask 255.255.255.0
> >     ELEMENT network cgtp type IPV4 number 10.101.3.0 netmask 255.255.255.0
> >     #
> >     # Cluster nodes IP addresses
> >     #
> >     ELEMENT ip peerNode1-4N-nic0 address 10.101.1.10 type STATIC alias node1
> >             BELONG_TO network phys-A
> >     ELEMENT ip peerNode1-4N-nic1 address 10.101.2.10 type STATIC
> >             BELONG_TO network phys-B
> >     ELEMENT ip peerNode2-4N-nic0 address 10.101.1.20 type STATIC alias node2
> >             BELONG_TO network phys-A
> >     ELEMENT ip peerNode2-4N-nic1 address 10.101.2.20 type STATIC
> >             BELONG_TO network phys-B
> >     ELEMENT ip peerNode3-4N-nic0 address 10.101.1.30 type STATIC alias node3
> >             BELONG_TO network phys-A
> >     ELEMENT ip peerNode3-4N-nic1 address 10.101.2.30 type STATIC
> >             BELONG_TO network phys-B
> >     ELEMENT ip peerNode4-4N-nic0 address 10.101.1.40 type STATIC alias node4
> >             BELONG_TO network phys-A
> >     ELEMENT ip peerNode4-4N-nic1 address 10.101.2.40 type STATIC
> >             BELONG_TO network phys-B
> >     #
> >     # Master floating addresses
> >     #
> >     ELEMENT ip master-cgtp address 10.101.3.1 type FLOATING alias master
> >             BELONG_TO network cgtp

> >     ELEMENT ip master-nic0 address 10.101.1.1 type FLOATING
> >             BELONG_TO network phys-A

> >     ELEMENT ip master-nic1 address 10.101.2.1 type FLOATING
> >             BELONG_TO network phys-B

> >     #
> >     # Cluster nodes CGTP addresses
> >     #
> >     ELEMENT ip peerNode1-4N-cgtp alias peerNode1-4N-cgtp.localdomain
> >             address 10.101.3.10 type STATIC
> >             BELONG_TO network cgtp
> >     ELEMENT ip peerNode2-4N-cgtp alias peerNode2-4N-cgtp.localdomain
> >             address 10.101.3.20 type STATIC
> >             BELONG_TO network cgtp
> >     ELEMENT ip peerNode3-4N-cgtp alias peerNode3-4N-cgtp.localdomain
> >             address 10.101.3.30 type STATIC
> >             BELONG_TO network cgtp
> >     ELEMENT ip peerNode4-4N-cgtp alias peerNode4-4N-cgtp.localdomain
> >             address 10.101.3.40 type STATIC
> >             BELONG_TO network cgtp
> >     #
> >     # Router ip addresses
> >     #
> >     ELEMENT ip router-4N-nic0 address 10.101.1.90 type STATIC
> >             BELONG_TO network phys-A
> >     ELEMENT ip router-4N-nic1 address 10.101.2.90 type STATIC
> >             BELONG_TO network phys-B
> >     #
> >     # Default router configuration
> >     #
> >     ELEMENT router default-router
> >             USE ip router-4N-nic0
> >                 ip router-4N-nic1
> >     #
> >     # External access to switches
> >     #
> >     ELEMENT ip switch1-4N-nic0 address 10.101.1.100 type STATIC
> >             BELONG_TO network phys-A
> >     ELEMENT ip switch2-4N-nic0 address 10.101.2.200 type STATIC
> >             BELONG_TO network phys-B

## ATTRIBUTES

> See `attributes`(5) for descriptions of the following attributes:

> ATTRIBUTE TYPE | ATTRIBUTE VALUE
> --- | ---
> Architecture | SPARC
> Availability | SUNWnhsmc
> Interface Stability | Evolving

## SEE ALSO

> `cluster.conf`(4), `machine.conf`(4), `slconfig`(1M), `slcreate`(1M), `sldelete`(1M), `sldeploy`(1M), `slexport`(1M)

Netra HAS FS 2.1 | Go To Top | Last Changed September 2004

Company Info | Contact | Copyright 2004 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.