Manual Pages
Table of Contents
na_vfiler - Commands for vfiler operations
vfiler create vfilername [-n] [-s ipspace ] -i ipaddr [-i
ipaddr ]... path [ path ...]
vfiler create vfilername -r path [-b old_vfiler_name ]
vfiler destroy [-f] vfilername
vfiler rename old_vfilername new_vfilername
vfiler add vfilername [-f] [-i ipaddr [-i ipaddr]...] [
path [ path ...]]
vfiler remove vfilername [-f] [-i ipaddr [-i ipaddr]...] [
path [path ...]]
vfiler limit [ max_vfilers ]
vfiler move vfiler_from vfiler_to [-f] [-i ipaddr [-i
ipaddr]...] [path [path ...]]
vfiler start vfilertemplate
vfiler stop vfilertemplate
vfiler status [-r|-a] [ vfilertemplate]
vfiler run [-q] vfilertemplate command [args]
vfiler allow vfilertemplate [proto=cifs] [proto=nfs]
[proto=rsh] [proto=iscsi] [proto=ftp] [proto=http]
[proto=ssh]
vfiler disallow vfilertemplate [proto=cifs] [proto=nfs]
[proto=rsh] [proto=iscsi] [proto=ftp] [proto=http]
[proto=ssh]
vfiler context vfilername
vfiler dr configure [-l user:password ] [-e ifname:IP
address:netmask,... ] [-d dns_server_ip:... ] [-n
nis_server_ip:... ] [-s ] [-a alt-src,alt-dst ] [-u ] [-c
secure ] remote_vfiler@remote_node
vfiler dr status remote_vfiler@remote_node
vfiler dr delete [-f] [-c secure ]
remote_vfiler@remote_node
vfiler dr activate remote_vfiler@remote_node
vfiler dr resync [-l remote_login:remote_passwd ] [-a alt_src,alt-dst
] [-s ] [-c secure ] remote_vfiler@remote_node
vfiler migrate [-m nocopy [-f]] [-l user:password ] [-c
secure ] [-e ifname:IP address:netmask,... ]
remote_vfiler@remote_node
vfiler migrate start [-l user:password ] [-c secure ] [-e
ifname:IP address:netmask,... ] remote_vfiler@remote_node
vfiler migrate status remote_vfiler@remote_node
vfiler migrate cancel [-c secure ]
remote_vfiler@remote_node
vfiler migrate complete [-l remote_login:remote_passwd ]
[-c secure ] remote_vfiler@remote_node
vfiler help
The vfiler command controls the configuration of Virtual
Filers (vfilers) on a node.
The vfiler command is available only if your node has the
vfiler license.
- create
- Creates the named vfiler. The named vfiler
must not already be defined on the system.
The default vfiler, vfiler0, always exists
on a node.
There are two ways to create a vfiler. The
first uses the -i option to specify configuration
information on the command
line. Use this form when creating a
vfiler for the first time. The second form
uses the -r option to re-create a vfiler
from configuration information stored in
the specified data set. Use this form
when creating a vfiler from a data store
that has been Snapmirrored between nodes.
When initially creating a vfiler with the
vfiler create vfilername [-s ipspace ] -i
form of the command, at least one path
must be supplied on the command line. The
paths can be either volumes or qtrees.
Additional paths can be specified later by
using the vfiler add command. Any attempt
to use storage claimed by another vfiler
causes the command to fail. The first
storage unit mentioned when creating a
vfiler is special in that it will be used
for the /etc store space for vfiler-visible
configuration information. This first
storage unit is permanently associated
with the vfiler. It can only be disassociated
when the vfiler is destroyed.
At least one IP address must be supplied
on the command line. Additional IP
addresses can be specified later by using
the vfiler add command. Unless the -s
option is used, the new vfiler is associated
with the default IP space. An attempt
to use an IP address that is already in
use by another vfiler in the same IP space
causes the command to fail.
Any IP address specified as part of this
command must also be unconfigured. To
unconfigure an interface address, you can
either configure the interface down, or
(if this address is an IP alias) remove
the address using ifconfig -alias.
When a vfiler is created using -i, a set
of default options is created. After a
new vfiler is created, it will be in a
running state; but no protocol servers
will be running. You can run the setup
command in the context of this vfiler
using "vfiler run" to setup the vfiler. If
the -n option is not used, the vfiler create
command will automatically run the
setup command after creating the vfiler.
When re-creating a Snapmirrored vfiler or
otherwise copied datastore, using the
vfiler create vfilername -r path form of
the command, the specified vfilername
parameter must match the name of the original
vfiler exactly, and the path must
match the first path that was specified in
the vfiler create command that originally
created the vfiler. Optionally, if the
vfilername is intended to be different,
then the -b option must be used and the
parameter must match the name of the original
vfiler exactly.
After a vfiler is re-created it will be in
the running state, and its protocol
servers will be running.
At the end of vfiler create the IP
addresses of the new vfiler are unconfigured.
The setup command can be run (manually,
or automatically if the -n option is
not used in the first form of vfiler create)
on this vfiler to configure these
addresses. If setup is not run, configure
the addresses using ifconfig and make this
IP address configuration persistent by
putting these ifconfig lines in /etc/rc.
- destroy
- The destroy subcommand releases all
resources and removes the configuration
information associated with the named
vfiler. The vfiler to be destroyed must be
in a stopped state. Note that no user data
is destroyed by this operation, just the
association of the storage and IPs with
the named vfiler. Any network interfaces
configured with an IP address of the
vfiler being destroyed must be configured
down before this operation can be performed.
The default vfiler, vfiler0, cannot
be destroyed. Unless the -f option is
specified, the action must be confirmed.
The storage resources are returned to the
hosting node.
- rename
- The rename subcommand renames an existing
vfiler with the new name.
- add
- The add subcommand adds the specified IP
addresses and/or paths to an existing
vfiler. The arguments have the same rules
as those specified during the initial create.
The -f option skips the confirmation
and warnings.
- remove
- The remove subcommand removes the named IP
addresses and/or paths from an existing
vfiler. The arguments must belong to the
named vfiler. Note that no user data is
modified by this command. The only effect
is to disassociate the paths and/or IPs
from the named vfiler. Note that the path
that holds the /etc directory can only be
removed by vfiler destroy. The storage
resources are returned to the hosting
node. The -f option skips the confirmation
and warnings.
- limit
- The limit subcommand sets the upper limit
on the number of vfilers that can be created
without rebooting. For HA systems,
the user is responsible for setting the
limit to the same value on both the local
and the partner node. When no argument is
supplied, this subcommand returns the current
upper limit. The range of acceptable
values for max_vfilers is platform dependent.
Use vfiler help limit to determine
the range for your platform. When the
vfiler limit is decreased, the change is
effective immediately. When the vfiler
limit is raised beyond what it was when
the node was last booted, the new limit
will not take effect until the next
reboot.
- move
- The move subcommand removes the named IP
addresses and/or paths from vfiler_from
and adds them to vfiler_to. The arguments
must belong to vfiler_from. At least one
IP address or storage path must be specified
as an argument for the subcommand. No
user data is modified by this command.
The only effect is to disassociate the
paths and/or IPs from the source vfiler
and add them to the destination vfiler.
This means that security information such
as UIDs and SIDs may not be valid or meaningful
in the destination vfiler, so the
administrator may have to re-perm the
files after moving. Note that the path
that holds the vfiler's /etc directory
cannot be moved to another vfiler. Also,
at least one IP must be left on the source
vfiler. The -f option skips the confirmation
and warnings.
- start
- The start subcommand causes one or more
previously stopped vfilers to enter the
running state. This means packets will be
accepted for the vfiler(s) that match the
specified vfilertemplate. A vfilertemplate
can be a "*" (matching all vfilers), a
vfiler name, a comma seperated list of
vfiler names or an IPspace (specified as
i:<ipspacename>). The hosting node is not
affected by this command.
- stop
- The stop subcommand causes the matching
vfilers to stop receiving network traffic.
From the point of view of a client the
vfiler will be down. The hosting node is
not affected by this command.
- status
- The status subcommand displays the running/stopped
status of the matching
vfiler(s). The -r flag displays all IPs
and storage assigned to the matching vfilers.
The -a flag combines the output of
vfiler status -r with a report on what
protocols and commands are allowed and
disallowed on the matching vfilers. If
vfilertemplate is omitted, all vfilers are
displayed.
- run
- The run subcommand runs the command on the
vfiler(s) specified in the vfilertemplate.
If more than one vfiler matches, the command
will be run separately for each
vfiler. Any vfiler-specific console command
can be supplied. If a command is not
vfiler-specific, an error will be issued
and the command will not be executed. A
wildcard specification will run the command
on all vfilers, including the hosting
node. The -q option prevents printing a
separator before the command runs for each
vfiler. The run command affects vfilers in
running states only.
- allow
- The allow subcommand allows the use of the
specified protocols on the vfiler(s) specified
in the vfilertemplate. If more than
one vfiler matches, the specified protocols
will be allowed on each vfiler. The
CIFS and NFS protocols can only be allowed
if they have been licensed on the hosting
node. A wildcard specification will allow
the specified protocols on all vfilers,
including the hosting node.
- disallow
- The disallow subcommand disallows the use
of the specified protocols on the
vfiler(s) specified in the vfilertemplate.
If more than one vfiler matches, the specified
protocols will be disallowed on each
vfiler. A wildcard specification will disallow
the specified protocols on all
vfilers, including the hosting node.
- context
- The context switches the vfiler context of
the CLI to the specified vfiler. Any subsequent
command typed on the CLI is executed
in the context of the specified
vfiler, and is subject to the constraints
of that vfiler. The command vfiler context
vfiler0 returns the context of the CLI to
the default vfiler context.
- dr
- The dr subcommand configures the specified
remote vfiler from the specified remote
node for disaster recovery on the local
node. This operation has three logical
stages. First, issue the configure command,
which initiates the mirroring of the
remote vfiler's storage to the local node
using SnapMirror. Then you can use the
status command to monitor the status of
this mirror. In the event of a disaster,
you can issue the activate command to
activate the remote vfiler on the local
machine. At any point when the remote
vfiler is mirrored, you can use the delete
command to remove this DR configuration.
The configure subcommand requires the user
to provide an administrative login id and
password for the remote pfiler; this
information can be provided as an argument
to the -l option, or in response to an
interactive question. The user also needs
to provide information for binding the IP
addresses of the vfiler to specific local
interfaces. This can be specified as an
argument to a -e options or in response to
interactive questions. Synchronous Snapmirror
can be used for data transfer by
specifying the -s option. The user may
specify an alternate set of DNS and NIS
servers to be used at the DR site, either
using the -d or -n options, or in response
to interactive questions. The -a option,
specified in conjunction with -s option,
can be used to specify the alternate hostnames
or IP addresses for redundancy purposes.
The -f option for dr delete forces
deletion in spite of errors. The -u
option can be used to skip snapmirror initialize.
The -c secure option is to use
secure command channel while communicating
with remote node. The resync subcommand
is used to resync a source with an activated
destination or resync a destination
with a source. One can specify the -l , -s
, -a options which have the same semantics
as that of the configure command.
- migrate
- The migrate subcommand moves the specified
remote vfiler from the specified remote
node to the local node. This operation has
three logical steps, and should be performed
in three stages. First, issue the
start command which initiates the movement
of the remote vfiler's storage to the
local node using SnapMirror. Then you can
use the status command to monitor the status
of this data movement. When this status
for each path changes from Being initialized
to SnapMirrored, you can issue
the complete command to finish the migration.
When the complete command completes,
the remote vfiler will have been moved to
the local machine. If the command argument
is omitted, the migrate command goes
through the three steps in sequence and
blocks until the migration is complete.
This command requires the user to provide
an administrative login id and password
for the remote pfiler; this information
can be provided as an argument to the -l
option, or in response to an interactive
question. The user also needs to provide
information for binding the IP addresses
of the vfiler to specific local interfaces.
This can be specified with the -e
option or in response to interactive questions.
The -m nocopy option indicates that the
vfiler should be migrated using software
disk ownership technology in order to
avoid copying the vfiler data. Both local
and remote machines must use software disk
ownership and be licensed for SnapMover.
The storage units belonging to the vfiler
must be complete volumes. This option
only applies when the command argument is
omitted. The -c secure option is to use
secure command channel while communicating
with remote node.
The vfiler will not be migrated if:
* the source node file system version is
not the same as the local file system version
* NFS, CIFS, or iSCSI are allowed on the
source vfiler but not licensed locally
* CFO is licensed on the source node but
not licensed locally
The -f option allows vfiler migration even
if the above conditions are not met. However,
it will not allow the migration of a
vfiler if the source node's file system
version is greater than the local node's
file system version.
- help
- The help subcommand provides help for the
vfiler subcommands.
Controller failover starts up instances of a failing partner's
vfilers on the partner that is taking-over. For this
to be successful, all IP addresses in use by vfilers must
failover correctly; that is, the partner interface
information for each interface in use by a vfiler must be
configured correctly. Thus, all ifconfig lines in /etc/rc
of either partner that specify the main address of an
interface must correctly and consistently specify the
partner interface. Lines in /etc/rc that specify IP
aliases should not specify a partner interface or address.
It is also required that all ipspaces defined on the failing
partner that are in use must also be configured on the
partner taking-over even though these ipspaces may not
have any vfilers defined on the taking-over partner.
Note also, for controller failover purposes, a vfiler
(other than vfiler0) does not have a partner vfiler. The
number of vfilers configured on each host of an HA pair
(and their specific configuration) may be completely asymmetric.
For instance, one partner may have 3 vfilers configured
and the other partner may have 7 vfilers configured.
Two non-default vfilers on different hosts of an HA
pair may even have the same name.
For vfiler0 the usual HA configuration restrictions still
apply. For example, certain configuration parameters
(options) of vfiler0 must match the corresponding parameters
of the partner's vfiler0.
na_ipspace(1), na_ifconfig(1)
Table of Contents