EMC VNX .server_config command reference

EMC VNX .server_config command reference

It’s been a while since my last post, this time I’ll try to document as many parameters as I can for the .server_config command from EMC. This command is used to configure parameters and read information directly from your Data Movers, for some reason it is not documented by EMC, I guess it is because the command can make some powerful stuff and they do not want customers dealing with that, that being said be really careful with it, since if you mess with it and something goes wrong I don’t know if EMC is going to be very happy about it, in the other hand it has some useful stuff so be careful. My recommendation, consider safe commands used output information, commands used to change settings, try to document the values prior the change and keep an eye close.I’ll keep updating the list as long as I find new commands and information.

HBA related commands

These 2 are useful to gather information from FC devices attached to the Celerra, very useful if you are working with tape drives attached to the system:

.server_config server_2 -v “fcp show”

.server_config server_5 -v “fcp bind show”

HBA stats, sounds awesome most of all for performance troubleshooting or health checks, but I’ve never been able to make them work:

.server_config server_2 -v “printstats fcp reset” (to enable / disable FC stats collection)

.server_config server_x -v “printstats fcp”

.server_config server_2 -v “printstats fcp full”

.server_config server_x -v “printstats scsi reset” (to enable / disable SCSI stats collection. I guess this one is for legacy Celerra systems)

.server_config server_x -v “printstats scsi”

CIFS / AD Domain connectivity related

.server_config server_2 -v “pdc dump” (in order to obtain more detailed information about the DCs you are connected to than server_cifs)

.server_config server_2 -v “pdc disable=” (Disable a DC, the DM will avoid connecting to it, you have to use the IP after the enable=)

.server_config server_2 -v “pdc enable=” (Enable a DC previously disabled, you have to use the IP after the enable=)

.server_config server_x -v “cifs” (This one VERY similar to server_cifs <cifsServer>)

File services related

.server_config server_x -v “printstats filewrite”
.server_config server_x -v “printstats filewrite full”
.server_config server_x -v “printstats filewrite reset”

NDMP logging

I’ve collected these around the internet, never had the need of them, at least for me the default logging level for NDMP (which can be accessed from server_log, i.e. server_log server_2 | grep –I NDMP) has been enough but if you need to go deeper, try these:

To check your current values:

.server_config server_2 -v “logsys get severity NDMP”

.server_config server_2 -v “logsys get severity PAX”

To enable/disable NDMP Logging:

.server_config server_x -v “printstats vbb show”

Turn it on:

.server_config server_x “logsys set severity NDMP=LOG_DBG2″

.server_config server_x “logsys set severity PAX=LOG_DBG2″

Turn it off:

.server_config server_x “logsys set severity NDMP=LOG_ERR”

.server_config server_x “logsys set severity PAX=LOG_ERR”

Nerworking related

These are useful, but most of times I work with server_netstat command:

.server_config server_x -v “printstats tcpstat”
.server_config server_x -v “printstats tcpstat full”
.server_config server_x -v “printstats tcpstat reset”

To disable specific network interfaces, never tried these either, for what I read are for the old NS systems. Check what devices are on your system before going into these:

XENA devices

.server_config <server> -v “xena <interface> start|stop”

bcmXG devices

.server_config  <server> -v “bcmxg <interface> start|stop”

bcm devices

.server_config  <server> -v “bcm <interface> start|stop”

Virus check related

.server_config server_2 “param viruschk Traces=0×00000004” (Turns on debug for AV in the server_log )
.server_config server_2 “param viruschk Traces=0×00000000” (Turns off debug for AV in the server_log)

Hernán J. Larrea

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.