Administrator Guide

VPlexcli:/> port-monitor status
Status: running with the following parameters:
Emails: None
SMTP: x.x.x.x
Local-only: False
Threshold config: None
### Restarting the monitor
If you wish to restart a stopped monitor with the same parameters as before, run `port-
monitor restart`. If you wish to use different options, use the `start` command documented
above.
## Configuring the driver-specific thresholds
The thresholds may be overridden by placing a JSON file at
/var/log/VPlex/cli/port-stats-monitor/config.json, with each key representing a stat to
monitor and the value representing the threshold at which to notify the user. Example
contents of the config.json:
{
"crc-errors": 40,
"link-failure": 15,
"loss-of-sync": 45,
"loss-of-signal": 45,
"invalid-transmission-word": 40,
"lr-remote": 5
}
Exemplo de resultado
Exemplo de resultado do e-mail que pode ser enviado para o contato.
From: VPLEX Port Stat Notifier [mailto:[e-mail]]
Sent: Day, Month date, YYYY H:MM <AM/PM>
To: <recipient>
Subject: VPlex Port Stat Notification for x.x.x.x <Serial Number>
The port stat monitor detected a problem.
Historical data is located in /var/log/VPlex/cli/port-stats-monitor.log
Current thresholds: crc-errors: 40, invalid-transmission-word: 40, link-failure: 15, loss-of-
signal: 45, loss-of-sync: 45
In the last 60 seconds:
director-1-1-A A1-FC03 (back-end) crc-errors has increased by 10924
director-1-1-A A1-FC02 (back-end) crc-errors has increased by 9541
director-1-1-A A1-FC01 (back-end) crc-errors has increased by 13655
director-1-1-A A1-FC00 (back-end) crc-errors has increased by 14982
The following I-Ts on director-1-1-A were banished:
x fcp i 0xc00144878f0e0800 t 0x500601683660190e
The following additional reports from the last hour were suppressed:
2019-03-22 14:21:12
director-1-1-B B0-FC02 (front-end) crc-errors has increased by 13354
director-1-1-B B0-FC03 (front-end) crc-errors has increased by 19255
director-1-1-B B0-FC00 (front-end) crc-errors has increased by 15254
director-1-1-B B0-FC01 (front-end) crc-errors has increased by 953630
Coisas a serem observadas
Anote o número de portas e o número de directors que relatam problemas. Por exemplo, se metade das portas estiver relatando
problemas, isso pode indicar um evento de fabric. No entanto, se apenas uma porta estiver relatando um erro, o problema será localizado
em um IT Nexus específico.
100
Desempenho e monitoramento