-.TH lmc 1 "2003 Oct 8" Lustre "configuration utilities"
+.TH lmc 1 "2004 Sep 16" Lustre "configuration utilities"
.SH NAME
lmc \- Lustre configuration maker
.SH SYNOPSIS
This will create a new node with the given name if not already present.
.TP
--timeout <num>
-Timeout before going into recovery
+Timeout before going into recovery.
.TP
--lustre_upcall <path>
-Set the location of the Lustre upcall scripts used by the client for recovery
+Set the location of the Lustre upcall scripts used by the client for recovery.
.TP
--portals_upcall <path>
-Specify the location of the Portals upcall scripts used by the client for recovery
+Specify the location of the Portals upcall scripts used by the client for recovery.
.TP
--upcall <path>
-Specify the location of both (Lustre and Portals) upcall scripts used by the client for recovery
+Specify the location of both (Lustre and Portals) upcall scripts used by the client for recovery.
+.TP
+--ptldebug <debug_level>
+Set the portals debug level.
+.TP
+--subsystem <subsystem_name>
+Specify which Lustre subsystems have debug output recorded in the log.
.PP
.B --add net
Adds a network device descriptor for the given node, with parameters as indicated.
This will create a new node with the given name if not already present. This is also used to specify a specific node for other elements.
.TP
--nettype <type>
-This can be tcp, elan, gm, scimac.
+This can be tcp, elan, or gm.
.TP
--nid nid
The network id, e.g. ElanID or IP address as used by Portals. If nid is '*', then the local address of the interface with specified nettype is will be substituted when the node is configured with lconf. An nid of '*' should be used only for the generic client configuration.
.TP
+--cluster_id id
+Specify the cluster ID.
+.TP
--hostaddr addr
+Specify the host address, which will be transfered to the real host address by lconf.
.TP
--router
-Optional flag to mark this node as a router
+Optional flag to mark this node as a router.
.TP
--port [port]
Optional arguement to indicate the tcp port. The default is 988.
Optional arguement since some OSTs might not have the required support. This is turned off by default, value of 1 will turn it ON.
.PP
.B --add mds
-Specify the MDS configuration
+Specify the MDS configuration:
.TP
--node <node name>
-Name of the node on which the MDS resides
+Name of the node on which the MDS resides.
.TP
--mds <mds_name>
-Common name of the MDS
+Common name of the MDS.
+.TP
+--mdsuuid <uuid>
+Specify MDS uuid.
+.TP
+--failover
+Enable failover support on MDS.
.TP
--dev <pathname>
Path of device on local system. If the is a file, then a loop device is created and used as the block device.
.TP
+--backdev <pathname>
+Path of the device for backing storage on local system.
+.TP
--size <size>
Optional argument indicating the size (in KB) of the device to be created (used typically for loop devices).
.TP
--fstype extN|ext3
Optional argument used to specify the file system type. Default is ext3.
.TP
+--backfstype ext3|tmpfs
+Specify the backing filesystem type.
+.TP
+--nspath
+Local mount point of server namespace.
+.TP
+--inode_size <size>
+Specify new inode size for underlying ext3 file system.
+.TP
+--mkfsoptions <options>
+Optional argument to mkfs.
+.TP
+--mountfsoptions <options>
+Optional argument to mount fs. Mount options will be passed by this argument. For example, extents are to be enabled by adding ",extents" to the --mountfsoptions option. "errors=remount-ro" and "asyncdel" can also be added to it.
+.TP
--journal_size <size>
Optional arguement to specify the journal size for the ext2/ext3 file system. The size should be in the units expected by mkfs, so for ext3 it should be in MB. If this is option is not used, the ext2/ext3 filesystem will be configured with the default journal size.
.PP
--node <nodename>
Node on which the OST service is run, can not be a profile node.
.TP
+--failover
+Enable failover support on OST.
+.TP
--dev <pathname>
Path of device on local system. If this is a file, then a loop device is created and used as the block device.
.TP
+--backdev <pathname>
+Path of the device for backing storage on local system.
+.TP
--size [size]
Optional argument indicating the size (in KB) of the device to be created (used typically for loop devices).
.TP
--fstype
extN|ext3 Optional arguement used to specify the file system type. Default is ext3.
.TP
+--backfstype ext3|tmpfs
+Optional argument to specify the backing filesystem type.
+.TP
+--inode_size <size>
+Specify new inode size for underlying ext3 file system.
+.TP
+--nspath
+Local mount point of server namespace.
+.TP
+--mkfsoptions <options>
+Optional argument to mkfs.
+.TP
+--mountfsoptions <options>
+Optional argument to mount fs. Mount options will be passed by this argument. For example, extents are to be enabled by adding ",extents" to the --mountfsoptions option. "errors=remount-ro" and "asyncdel" can also be added to it.
+.TP
--journal_size <size>
Optional arguement to specify the journal size for the ext2/ext3 file system. The size should be in the units expected by mkfs, so for ext3 it should be in MB. If this is option is not used, the ext2/ext3 filesystem will be configured with the default journal size.
.PP
.TP
--ost ost_name | --lov lov_name
OST or LOV name as specified earlier in the configuration
+.TP
+--clientoptions options
+Specify the options for Lustre, such as async.
.PP
.B --add route
Creates a static route through a gateway to a specific nid or a range of nid's.
--node node
Node to add the route to.
.TP
+--router
+Optional flag to mark a node as router.
+.TP
--gw nid
The nid of the gateway (must be a local interface or a peer).
.TP
---tgt nid
-For a specific route, this is the target nid.
+--gateway_cluster_id id
+Specify the id of the cluster, to which the gateway belongs.
+.TP
+--target_cluster_id id
+Specify the id of the cluster, to which the target of the route belongs.
.TP
--lo nid
For a range route, this is the lo value nid.
Name of the node that echo client should run on,
.TP
--obd obd_name
+.PP
+.B --add mgmt
+Management/monitoring service.
+.TP
+--node nodename
+Node on which the mgmt service resides.
+.TP
+--mgmt <mgmt_service_name>
+Specify management/monitoring service name.
+.PP
+.B --add cobd
+Create the cobd on the specified node.
+.TP
+--node nodename
+Node on which the cobd resides.
+.TP
+--cache_obd obd_name
+Specify the cache device for the cache obd system.
+.TP
+--real_obd obd_name
+Specify the real device for the cache obd system.
.SH OPTIONS
One of the following options should be specified.
.TP 12
.TP
--merge filename
Add the new element to an existing file.
+.TP
+--reference
+Print short reference for commands.
+.TP
+--verbose
+Print system commands as they are run.
+.TP
+--batch filename
+Used to execute lmc commands in batch mode.
.SH EXAMPLES
-Real life examples are given in the Lustre-conf manual page.
+.TP
+.B lmc --node adev3 --add net --nid adev3 --cluster_id 0x1000 --nettype tcp --hostaddr adev3-eth0 --port 988
+.TP
+.B lmc --node adev3 --add net --nid adev3 --cluster_id 0x2000 --nettype tcp --hostaddr adev3-eth1 --port 989
+Used to add a Lustre node to a specified Lustre cluster through a network interface. In this example, Lustre node adev3 has been added to 2 Lustre clusters whose cluster_id are 0x1000 and 0x2000 separately through 2 network interface cards: adev3-eth0 and adev3-eth1. adev3 would listen in some specified port(s) to prepare for possible connection requests from nodes in these two clusters.
+.TP
+.B lmc --node adev3 --add route --nettype tcp --gw 5 --gateway_cluster_id 0x1000 --target_cluster_id 0x1000 --lo 4 --hi 7
+Used to add a route entry for a Lustre node. Here Lustre node adev3 is told it has a new route entry that now it could send packets to Lustre nodes whose nids is from 4 to 7 with the help of Lustre gateway node whose nid is 5. Besides, Lustre gateway node is in cluster whose id is 0x1000 and target of the route belongs to cluster whose id is also 0x1000. The network in this route path is a tcp network.
.SH BUGS
None are known.
git://git.whamcloud.com / fs / lustre-release.git / blobdiff