Administrator Guide

Checking the script status
Steps
1. Check the status of the script to see if it is running.
VPlexcli:/> port-monitor status
Status: running with the following parameters:
Emails: [e-mail]
SMTP: x.x.x.x
Local-only: False
2. To ensure the script restarts on the chance there is a reboot or restart of the management server, you can add persistence
by adding the command that is used to start the script back in Starting the script to the VPlexcli-init file under
the /var/log/VPlex/cli directory as shown in this step. Use the vi editor, and add the script start command line to
end of /var/log/VPlex/cli/VPlexcli-init file.
Sample output:
service@ManagementServer:/var/log/VPlex/cli> vim VPlexcli-init
#-------------------------------------------------------------------------------
#- (C) 2007-2010 EMC Corporation. All rights reserved.
#-
#- This CLI initialization script is executed if it's located in any of the
#- following locations:
#- (CLI terminates the search on first success.)
#- if the --init-file option is specified on the command line then use that file
#- else search for the file "VPlexcli-init" in the following order:
#- a. CLI directory (specified with the --cli-directory option)
#- b. current dir (of the shell that started CLI)
#- c. user.dir (usually equivalent to the current dir)
#- d. user.home
#- e. classpath
#- This script is processed as if it had been sourced using the 'source' command
#-------------------------------------------------------------------------------
.
.
ll /monitoring/directors/*/monitors/
#
#
<new entry added below at the end of VPlex-init file,
script -i port_stats_monitor
port-monitor start –smtp <mail server ip address> -e <email>,<email>,...>
Adjust Thresholds (if needed)
Steps
On the management server, both if a Metro, create a directory port-stats-monitor and copy the specific hardware, VS2
or VS6, config.json file, you saw earlier after uncompressing the port-stats-monitor_6.2.zip file, to the newly
created directory.
a. Create the directory /var/log/VPlex/cli/port-stats-monitor.
Example: mkdir /var/log/VPlex/cli/port-stats-monitor
b. Copy the appropriate hardware <vsX>_config.json file to this directory for the metro node hardware you are working
on. Examples: cp vs2-config.json /var/log/VPlex/cli/port-stats-monitor/config.json or cp vs6-
config.json /var/log/VPlex/cli/port-stats-monitor/config.json.
NOTE:
For Step c, do not make any changes after loading the script. Let the monitor script run for a bit and if there are
performance issues, then the end user will get email alerts of any issues and they will reach out to metro node support
for further assistance. Go to Step d, though only to confirm that the monitor is running. In Step d scroll down to where
96 Performance and Monitoring