Sun Microsystems Logo
Products and Services
 
Support and Training
 
 

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 Formatsmachine.conf(4)


NAME

 machine.conf - SMCT configuration file to define the cluster in terms of hardware elements, disk layout, and file system

SYNOPSIS

 SMCT_CONFIG_DIR/models/machine.conf
 smct-config-dir/models/machine.conf

DESCRIPTION

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

The machine.conf configuration file enables you to define the hardware components, disk layout for master-eligible and dataless nodes, and the file system of the cluster.

A pre-configured machine.conf template file for each example hardware configuration is available in the /opt/SUNWcgha/nhsmct/etc/models/ directory. For a description of the files in this directory, see the Netra High Availability Suite Foundation Services 2.1 6/03 README.

The machine.conf configuration file contains the following sections:

  • Cluster hardware definition

    This section is a hierarchical description of the cluster hardware, starting with a top level description of the contents of the shelf, which typically contains drawers and switches. The cluster hardware definition is referenced by the cluster definition in the cluster.conf file.

    The following configuration elements are defined by the ELEMENT keyword:

    • drawer

      A container that holds one or several boards and disks.

    • board

      The CPU board associated to a node and the network interface cards (NIC) that it uses. Nodes are defined in the cluster.conf file.

    • switch

      The set of ports used to connect the NICs.

    • port

      The connection between the switch ports and the NICs.

  • Disk layout

    The disk layout section contains a description of the disk layout for the master-eligible nodes and dataless nodes.

    The following configuration elements are defined by the ELEMENT keyword:

    • disk

      A disk is described in terms of slices by using the slice configuration element.

    • slice

      Each slice is described in terms of size of partition, the file system to be mapped to the slice, and whether the slice is replicated or not, using the attributes number, size, type, and role.

  • File system definitions

    The file system definition section contains definitions of the file systems on each disk. The following configuration element is defined by the ELEMENT keyword:

    • filesys

      Each file system is defined in terms of root directories, read and write permissions, if the file system is exported, and if the file system is shared.

  • link

    A direct link connecting the serial ports of the master-eligible nodes can be configured to prevent a split brain situation, which is an error scenario where a cluster has two master nodes.

The ip configuration elements referenced in the machine.conf file are defined in the network.conf file.

PARAMETERS

This section describes the parameters in the machine.conf file:

{ ELEMENT shelf name
                  CONTAIN {drawer name}+ {switch name}*
}+
{ ELEMENT drawer name type drawer-type
                  [ CONTAIN {board name}* {disk name}* ]
}+             
{ ELEMENT drawer name type drawer-type 
	[ CONTAIN {board name}* {disk name}* ]
}+
{ ELEMENT switch name type switch-type
	[ CONTAIN  {port name}* ]
	[ USE {ip name}* ] 
}*
{ ELEMENT port number number number-value 
	CONNECT nic name 
}*
{ ELEMENT board name arch arch-type type board-type
	[ vendorType board-vendorType ] [ class board-class ] 
 [ clientId board-clientId ]
	[ USE {nic name}+ [link name] 
}+
{ ELEMENT nic name device nic-device type nic-type role nic-role
	class nic-class [address nic-address]
	[ USE ip name ] 
}*
{ ELEMENT disk name device disk-device type disk-type size disk-size 
	CONTAIN {slice name}+
}*
{ ELEMENT slice name number slice-number type slice-type size slice-size 
	rawDev rawDev-name blockDev blockDev-name [role slice-role]
	[ MAP filesys name ]
	[ USE slice name ]
	[ MANAGE replicatedSlice name ]
}*
{ ELEMENT filesys name role filesys-role type filesys-type 
	[ size filesys-size ] [ fsck filesys-fsck ] [ mntPt filesys-mntPt ] 
	[ mntBt y/n ] [ mntOpt filesys-mntOpt ] [ remMntPt filesys-mntOpt ]
	[ CONTAIN {exportedFileSys name}+ ]
}*
{ ELEMENT link name device name [ speed speed-value ] } *
  • name

    The unique name of the configuration record.

  • drawer-type

    The type of drawer. This can be one of the following:

    • CT410

    • CT810

    • CT821

    • NETRA_20

    • NETRA_120

    • T1_105

    • T1_200

  • switch-type

    The type of switch. This must be set to GENERIC.

  • board-type

    The type of board. This can be one of the following:

    • CP2140

    • CP2160

    • CP2300

    • T4

    • V120

    • T1_105

    • T1_200

    • GENERIC

    • sun4u

  • board-class

    The type of machine hardware, for example, sun4u. Configure this parameter if you have set the board-type to GENERIC. It is not necessary to configure this parameter for non-generic boards as it is pre-configured with the output from the uname -m command.

  • board-vendorType

    The type of hardware implementation. For example, SUNW,UltraSPARC-IIi-cEngine. Configure this parameter if you have set the board-type to GENERIC. It is not necessary to configure this parameter for non-generic boards as it is pre-configured with the output from the uname -i command.

  • disk-size

    The size of the disk in Gbytes.

  • arch-type

    The type of architecture. This must be set to SPARC.

  • nic-type

    The type of NIC. This can be one of the following:

    • PHYSICAL

      For a NIC that is not aliased. For example, eri0.

    • VIRTUAL

      For a NIC that is not related to a physical device. For example, cgtp0.

    • LOGICAL

    • For a NIC that is aliased on a physical NIC. For example, eri1:10.

  • nic-class

    The class of the NIC. This can be one of the following:

    • PRIMARY

      For a NIC using the Solaris JumpStart configuration.

    • SECONDARY

      For a NIC that is not using the Solaris JumpStart configuration.

  • nic-role

    The role of the NIC. A NIC can be assigned to the CGTP or the Node State Manager (NSM).

    For the CGTP service, you need to choose three NICs:

    • A NIC associated to physical subnet A with the role CGTP_NIC0.

    • A NIC associated to physical subnet B with the role CGTP_NIC1.

    • A NIC associated to the virtual subnet CGTP with the role CGTP.

    For the NSM service, you need to choose a NIC associated to an external subnet with the role NSM.

  • nic-address

    The Ethernet address of the NIC. This parameter is needed for:

    • Master-eligible nodes and dataless nodes. This parameter must be configured for the PRIMARY NIC to configure Solaris JumpStart.

    • Diskless nodes. This parameter must be configured for the PRIMARY and SECONDARY NICs if the boot policy of the associated node group set to MAC_ADDR_POLICY in the cluster.conf file.

  • disk-type

    The type of the disk. This can be one of the following:

    • SCSI

    • IDE

    • FC (Fibre Channel-Arbitrated Loop)

  • slice-number

    The slice-number parameter is used with the disk device name to define the name of the slice.

    The name of the slice = disk-device+ slice-number.

    For example:

    c0t0d0s0 = c0t0d0 + s0
    In this case, the slice-number is 0.

  • slice-rawDev

    The name of the raw-device family associated to the slice. For example, /dev/rdsk.

  • slice-blockDev

    The name of the block-device family associated to the slice. For example, /dev/md/dsk.

  • slice-type

    The type of slice. This can be one of the following:

    • PHYS

      A slice that is not managed by Solaris Volume Manager.

    • META

      A slice managed by Solaris Volume Manager that is the same size as the related PHYS slice

    • SOFT

      A slice managed by Solaris Volume Manager that is less than or equal to the related PHYS slice.

    The PHYS and META slices are associated to PHYS slices by the keyword USE.

  • slice-role

    The role of the slice. This can be one of the following:

    • META_DB

      Used for Solaris Volume Management.

    • BITMAP_SNDR

      Used by Sun StorEdge Network Data Replicator (SNDR) for each REPLICATED slice. BITMAP_SNDR slices can be either PHYS slices or SOFT slices.

    • REPLICATED

      Slices that SNDR must manage. REPLICATED slices can either be PHYS slices or META slices.

    If a REPLICATED slice is defined, then you must define a BITMAP_SNDR slice, linked to the previous one by the keyword MANAGE.

  • slice-size

    The number of cylinders multiplied by 1 Mbyte.

  • y/n

    This is yes or no for the mntBt option, that is, the mount at boot option.

  • filesys-role

    The role of the file system. This can be one of the following:

    • root

      Defines the root file system.

    • swap

      Defines the swap file system.

    • export

      Defines the file system containing the diskless environment.

    • shared

      Defines the file system that contains the software shared by all the cluster nodes.

    • user

      User-defined file system

    • data

      NFS file system exporting cluster-wide data.

    • database

      NFS file system exporting shared software database.

    • services

      NFS file system exporting shared software.

    The data, database, and services file systems are related to the shared file system.

  • filesys-type

    The type of file system. This can be one of the following:

    • ufs

    • nfs

    • swap

  • filesys-size

    The size of the file system in Mbytes.

  • filesys-fsck

    The file system to be checked. This can be either 1 or 2.

  • filesys-mntPt

    The mount point for the file system. The value can include the <--SWLID--> tag, which is replaced with the software load version by the SMCT.

  • filesys-mntOpt

    The mount options for the file system.

  • filesys-remMntPt

    The exported mount point for the shared file systems.

  • speed-value

    The speed of the serial line. Valid values are 38400, 57600, 76800, and 115200. The default value is 115200.

EXAMPLES

Following is an example of the disk layout section of the machine.conf file:

ELEMENT slice s0@disk1 number 0 rawDev /dev/rdsk blockDev /dev/dsk 
        type PHYS size 2048 
        MAP filesys ROOT

# Swap partition
ELEMENT slice s1@disk1 number 1 rawDev /dev/rdsk blockDev /dev/dsk 
        type PHYS size 1024 
        MAP filesys SWAP

# Shared software and data partition (replicated)
ELEMENT slice s3@disk1 number 3 rawDev /dev/rdsk blockDev /dev/dsk 
        type PHYS size 2048 

ELEMENT slice d3@disk1 number 3 rawDev /dev/md/rdsk blockDev /dev/md/dsk 
        type META size 2048 role REPLICATED
        USE slice s3@disk1 
        MAP filesys SHARED

ELEMENT slice d31@disk1 number 31 rawDev /dev/md/rdsk blockDev /dev/md/dsk
        type SOFT size 10 role BITMAP_SNDR
        USE slice s7@disk1
        MANAGE replicatedSlice d3@disk1

# User partition 1 (replicated)
ELEMENT slice s4@disk1 number 4 rawDev /dev/rdsk blockDev /dev/dsk 
        type PHYS size 2048 

ELEMENT slice d4@disk1 number 4 rawDev /dev/md/rdsk blockDev /dev/md/dsk 
        type META size 2048 role REPLICATED
        USE slice s4@disk1 
        MAP filesys USER1
...

The following is an example of a configuration for the direct link via a serial line between the two master-eligible nodes:

ELEMENT link serial-b device /dev/term/b speed 57600

ELEMENT board T1105@peerNode1 type T1_105 arch SPARC
         USE nic nic0@peerNode1
             nic nic1@peerNode1
             nic cgtp@peerNode1
             link serial-b

ATTRIBUTES

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

ATTRIBUTE TYPEATTRIBUTE VALUE
ArchitectureSPARC
AvailabilitySUNWnhsmc
Interface StabilityEvolving

SEE ALSO

cluster.conf(4), network.conf(4), slconfig(1M), slcreate(1M), sldelete(1M), sldeploy(1M)


Netra HAS FS 2.1Go To TopLast Changed September 2004