Dell VNX2 Configuring and Managing CIFS on VNX VNX1-VNX2 - Page 54

Windows Server-compatible CIFS server.

Get Dell VNX2 PDF manuals and user guides View all Dell VNX2 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 54 highlights

Configuring NOTICE Do not attempt to mix the NetBIOS and compname in the same Windows domain. Doing so can result in the Data Mover losing contact with the domain. Assign a NetBIOS or computer name alias on page 75 provides procedural information. Procedure 1. To create the CIFS server for a Windows Server environment on the Data Mover, use this command syntax: $ server_cifs -add compname=,domain= [,netbios=][,interface=] [,dns=] Where: = name of the Data Mover or VDM. = Windows Server-compatible CIFS server. = full domain name for the Windows environment. = (Optional) a NetBIOS name used in place of the default NetBIOS name. Type an optional NetBIOS name if the first 15 characters of the do not conform to the NetBIOS naming conventions or if you want something other than the default. Note You can only assign one compname to a CIFS server. You may assign multiple NetBIOS names to a CIFS server by creating aliases. = an interface to be used by the CIFS server being configured. If you add a CIFS server and do not specify any interfaces (with the interfaces= option), this server becomes the default CIFS server and uses all interfaces not assigned to other CIFS servers on the Data Mover. You can only have one default CIFS server per Data Mover. Note Link local interfaces cannot be added to a CIFS server as they are not supported on VNX. = different DNS suffix for the interface for DNS updates. By default, the DNS suffix is derived from the domain. This DNS option has no impact on the DNS settings of the Data Mover. Example: To create CIFS server dm32-ana0 on server_2, type: $ server_cifs server_2 -add compname=dm32-cge0,domain=universe.com, netbios=eng23b,interface=cge0,dns=nasdocs.emc.com Output: server_2 : done 54 EMC VNX Series VNX1, VNX2 Configuring and Managing CIFS on VNX

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
NOTICE
Do not attempt to mix the NetBIOS and compname in the same Windows domain. Doing
so can result in the Data Mover losing contact with the domain.
Assign a NetBIOS or computer name alias on page 75
provides procedural information.
Procedure
1. To create the CIFS server for a Windows Server environment on the Data Mover, use
this command syntax:
$ server_cifs
<mover_name>
-add
compname=
<comp_name>
,domain=
<full_domain_name>
[,netbios=
<netbios_name>
][,interface=
<if_name>
]
[,dns=
<if_suffix>
]
Where:
<mover_name>
= name of the Data Mover or VDM.
<comp_name>
= Windows Server-compatible CIFS server.
<full_domain_name>
= full domain name for the Windows environment.
<netbios_name>
= (Optional) a NetBIOS name used in place of the default NetBIOS
name.
Type an optional NetBIOS name if the first 15 characters of the
<comp_name>
do not
conform to the NetBIOS naming conventions or if you want something other than the
default.
Note
You can only assign one compname to a CIFS server. You may assign multiple NetBIOS
names to a CIFS server by creating aliases.
<if_name>
= an interface to be used by the CIFS server being configured. If you add
a CIFS server and do not specify any interfaces (with the interfaces= option), this
server becomes the default CIFS server and uses all interfaces not assigned to other
CIFS servers on the Data Mover. You can only have one default CIFS server per Data
Mover.
Note
Link local interfaces cannot be added to a CIFS server as they are not supported on
VNX.
<if_suffix>
= different DNS suffix for the interface for DNS updates. By default,
the DNS suffix is derived from the domain. This DNS option has no impact on the DNS
settings of the Data Mover.
Example:
To create CIFS server dm32-ana0 on server_2, type:
$ server_cifs server_2 -add compname=dm32-cge0,domain=universe.com,
netbios=eng23b,interface=cge0,dns=nasdocs.emc.com
Output:
server_2 : done
Configuring
54
EMC VNX Series
VNX1, VNX2
Configuring and Managing CIFS on VNX