If you still want to disable SMB1 on the VNX - even though its not necessary - you can do that easily via a param change
For VNX and older products, from CS using the user nasadmin ssh session,
server_param ALL –f cifs –m smb1.disabled -v 1
For Unity 4.1.x, from the master SP using the user service user ssh session,
svc_param ALL –f cifs –m smb1.disabled -v 1
Just keep in mind that this will lock out all CIFS clients that only support SMB1 like Windows XP and older plus other devices like some network printers or scanners
disabling SMBv1 on Unity / VNX / VNXe is NOT necessary.
On unpatched Windows systems WannaCry can use a Microsoft bug to infect them through a remote execution vulnerability in the Microsoft SMB code.
This is not present on Unity / VNX / VNXe since it does NOT run the Microsoft SMB stack.
Plus it doesnt run Windows OS so WannaCrypt wouldnt run there even if it could get there.
Please be careful though and do not disable SMB1 on the domain controller that the systems are using for authentication - for talking to the DC with SMBv2 you would need a hotfix on the Unity / VNX / VNXe
Rainer_EMC
6 Operator
•
8645 Posts
7366
0
Posted May 17th, 2017 07:00
If you still want to disable SMB1 on the VNX - even though its not necessary - you can do that easily via a param change
For VNX and older products, from CS using the user nasadmin ssh session,
server_param ALL –f cifs –m smb1.disabled -v 1
For Unity 4.1.x, from the master SP using the user service user ssh session,
svc_param ALL –f cifs –m smb1.disabled -v 1
Just keep in mind that this will lock out all CIFS clients that only support SMB1 like Windows XP and older plus other devices like some network printers or scanners