Skip to main content

vserver cifs domain preferred-dc check

Contributors
Suggest changes

Display validation status of the Preferred-DC configuration

Availability: This command is available to cluster and Vserver administrators at the admin privilege level.

Description

Use the vserver cifs domain preferred-dc check command to check the status of configured preferred DC on a particular vserver.

Parameters

{ [-fields <fieldname>,…​]

If you specify the -fields <fieldname>, …​ parameter, the command output also includes the specified field or fields. You can use '-fields ?' to display the fields to specify.

| [-instance ] }

If you specify the -instance parameter, the command displays detailed information about all fields.

-vserver <vserver> - Vserver

Use this parameter to specify the Vserver whose preferred DC needs to be validated.

[-server-ip <text>,…​] - DC Address

Use this parameter to display IP-address of the configured CIFS Preferred-DC servers.

[-domain <TextNoCase>,…​] - Domain Name

Use this parameter to display Domain name of the configured CIFS Preferred-DCs.

[-status {down|up}] - DC Status

Use this parameter to display information only about CIFS Preferred-DC servers with a status that matches the value you specify.

[-status-details <text>,…​] - Status Details

Use this parameter to display information only about CIFS Preferred-DC servers with status details that match the value you specify.

Examples

The following example checks the connectivity of preferred DC on vserver vs0.

cluster1::> vserver cifs domain preferred-dc check -vserver vs0

Vserver : vs0

Domain Name             DC Address         Status       Status Details
-----------             -----------        ------       --------------
example.com             1.1.1.1             up         Response time (msec): 426
example.com             1.1.1.2             up         Response time (msec): 425
example1.com            2.2.2.2             up         Response time (msec): 423
example2.com            3.3.3.3             up         Response time (msec): 422