discoverylogoboss.netlify.com › Connecting To The Vnx Block Storage Processor (sp Over A Serial Cable ▲
This section provides information about connecting devices to server (remotely and locally), so you can interact with the service processor (SP) and the server console. Go to main content oracle home.
Hi – we recently moved a celerra but now getting the following error messages after running the /nascheckup script.————————————-Checks————————————-Control Station: Checking if NBS clients are started. PassControl Station: Checking if NBS configuration exists.
Connecting To The Vnx Block Storage Processor (sp Over A Serial Cable Look
PassControl Station: Checking if NBS devices are accessible. FailControl Station: Checking if NBS service is started FailControl Station: Checking if NAS partitions are mounted. PassData Movers: Checking status.?——————————————————————————–Any help would be greatly appreciated.Thanks in advance. NBS is the Network Block Service, which is a proprietary client/server protocol of VNX/Celerra for file that provides a block device (for example,iSCSI device) management functionality over a TCP/IP connection. You can check the parameter by typing serverparam server2 -facility nbs -list, then check the settings for each parameter with serverparam server2 -facility nbs -info.paramname. To be honest, I’m not at all familiar with NBS, if EMC support is available to you I’d recommend opening an SR.
Sorry I can’t be of more help. Great info — thanks for collecting! Very helpful. One suggestion — to allow people to be able to cut’n’paste, some of the commands were put into uppercase (probably an automatic “correction” by your blog software); for example, “Nasfs”, “Serverstats”, and “Fsgroup” are examples of commands not found (because of the initial capital letter). There are also 3 commands with syntax “.serverconfig” (two leading dots) instead of “.serverconfig” (one leading dot). For newbies, might have problem debugging what went wrong, and this is so wonderful I wanted to help you make it “perfect” 🙂.
It is possible to see which DC’s are being used by the Celerra. To view the current domain controllers visible on the data mover run this command.serverconfig server2 -v “pdc dump”That command will show you all of the domain controllers that the Celerra can see. It pulls the info from DNS. A successful connection to a DC will show a ‘Cnx=SUCCESS,DC request succeeded’ in the output.
If you want to disable certain DC’s from being used, you can enable or disable a domain controller on the data mover with these commands.serverconfig server2 -v “pdc enable=0.0.0.0” Enable a domain controller.serverconfig server2 -v “pdc disable=0.0.0.0” Disable a domain controllerWith that said, I don’t believe there is a specific command to change the preference for lookups. That’s just my experience, however, there could be a way I’m not aware of. I’ll do a little research and post again if I find anything. Remember that the.serverconfig command is undocumented from EMC. If you decide to use it, I would recommend opening an SR before using the above mentioned commands on a production system, test it on a test/dev array first. Use the.serverconfig command at your own risk! I don’t have any firsthand experience with the issue you’re having so I can’t say for certain that setting those parameters will help, but on the surface it does look like you’d be ok to do it.
I of course don’t work for EMC so you’d need to contact them for assurance that it won’t cause another problem. I read that that changing those parameters will trigger SID-to-Name lookup attempts to the Domain Controller for any orphaned SID detected, which could cause performance problems between the Celerra and the DC, so be warned.You can modify those CIFS Parameters using the serverparam command:# serverparam server2 -facility cifs -modify acl.mappingErrorAction -value 3# serverparam server2 -facility cifs -modify acl.retryAuthSid -value 600# serverparam server2 -facility cifs -modify acl.FailOnSDRestoreError -value 0. This drove me crazy for a few hours When running the below command you have to ensure that you leave off the initial “/” in the export directory you want to add.Ex. Serverexport server2 -Protocol nfs -name exports/usr/home/ace /ace/path1So in this example I wanted to add /exports/usr/how/ace to the /ace/path1 filesystem. After many attempts I found out that I can not have the initial “/” in the command. I couldn’t find this in any documentation and it was trial and error until I figured it out. Perhaps this is common knowledge but just thought I’d share.
Use nasdisk -list to view the connected LUNs. The fifth column in the output is a dash with a four digit number. This number is a hexadecimal representation of the Clariion/VNX LUN (for example, 021D = LUN 541).Sample Output:nasadmin@celerra $ nasdisk -listid inuse sizeMB storageID-devID type name servers17 y 511999 CKM9-0078 MIXED d17 1,218 y 511999 CKM9-0207 MIXED d18 1,219 y 511999 CKM9-0085 MIXED d19 1,220 y 511999 CKM9-0215 MIXED d20 1,221 y 511999 CKM9-021C MIXED d21 1,222 y 511999 CKM9-021B MIXED d22 1,223 y 511999 CKM9-021E MIXED d23 1,2.
How to launch?To launch a Unisphere you can fire up an Internet browser and type the IP address of either one of the SPs or the Control Station. How to login for fist time?Default login/password for EMC VNX Unified system is:. login: sysadmin. password: sysadminOr for VNXe:. login: admin.
password: Password123#Administration of VNX is performed with the Unisphere graphical user interface (GUI). Administration of the VNX system can also be performed with a command line interface (CLI). File enabled VNX systems use a command line interface to the Control Station for file administrative tasks. Block enabled systems have a host-based Secure CLI software option available for block administrative tasks. The CLI can be used to automate management functions through shell scripts and batch files.
Administrative Authentication Scope. The VNX provides three different administrative user auth scopes. Global authentication scope is used when the VNX is configured to be a member of a Storage Domain. All the systems within the domain can be administrated using a single sign-on with a global account. Local authentication scope is used to manage a specific system only. Logging into a system using a local user account is recommended when there are a large number of systems in the domain.
LDAP authentication scope is used when the VNX is configured to “bind” to an LDAP domain. The VNX performs an LDAP query to the domain to authenticate the administrative users.
Unisphere Storage Domains. Adding VNX into Storage DomainTo add a VNX system into an existing VNX local domain, in Unisphere navigate to the System List, and perform Add operation. You have to provide an SP (Storage Processor) IP address of the VNX system to be added. When adding a system into the domain, the system being added will be removed from any of its existing domain configurations.
Obviously you will also be asked for credentials to login to the VNX system being added. Once the VNX system is added, it will be displayed in the System List page. I’m having a problem with a VNXe3150 when accessing Unisphere. I’ve reset the admin/service password and when I login with the default it prompts to change both. Once I get the info and hit enter I get“this operation is not supported.
This function may not yet be implemented” next to the OLD Service password box and the admin password does not update.However when I SSH into the service account it’s using the new password I tried setting.Is there a way to create a new global admin in SSH so that I can login to Unisphere using that account? I’m seriously at a loss right now.