VPLEX VS1 & VS2 Engine Comparision
VPLEX Management Server Upgrade Steps / NDU (Non-Disruptive Upgrade) Overview
VPLEX Management Server Upgrade Steps / NDU Overview
- NDU pre-check script needs to be run
- Verify director communication status
- Verify directors have been commissioned
- Verify firmware software version can be retrieved
- Verify no unreachable storage-volumes
- Verify no unhealthy virtual-volumes
- Verify no unhealthy storage views
- Verify storage view configuration
- Verify valid system configuration.
- Verify cluster status
- Verify and prepare directors for ndu
Command to run the Pre-Check:
VPlexcli:/> ndu pre-check
========================================================================
Performing NDU pre-checks
========================================================================
Verify director communication status.. OK
Verify directors have been commissioned.. OK
Verify firmware software version can be retrieved.. OK
Verify no unreachable storage-volumes.. OK
Verify no unhealthy virtual-volumes.. OK
Verify no unhealthy storage views.. OK
Verify storage view configuration.. ERROR
Verify valid system configuration.. OK
Verify cluster status.. OK
Verify and prepare directors for ndu.. OK
==============================================================
The output for 'ndu pre-check' has been captured in /var/log/VPlex/cli/capture/ndu-pre-check-session.txt
VPlexcli:/> ndu pre-check
========================================================================
Performing NDU pre-checks
========================================================================
Verify director communication status.. OK
Verify directors have been commissioned.. OK
Verify firmware software version can be retrieved.. OK
Verify no unreachable storage-volumes.. OK
Verify no unhealthy virtual-volumes.. OK
Verify no unhealthy storage views.. OK
Verify storage view configuration.. ERROR
Verify valid system configuration.. OK
Verify cluster status.. OK
Verify and prepare directors for ndu.. OK
==============================================================
The output for 'ndu pre-check' has been captured in /var/log/VPlex/cli/capture/ndu-pre-check-session.txt
Overview:
How to Collect Diagnostic information in VPLEX
How to Collect Diagnostic information in VPLEX ?
Run CMD on Management Server > Collect-Diagnostics
Note: Metroplex you will only get the management server logs (smsDump) from the management server where Collect-Diagnostics is run. You will not get the smsDump logs from the remote management server.
The collect-diagnostics works by invoking other log collection scripts and cli commands and collecting the results in a file, in the below Zip format
collect-diagnostics-<timestamp>.zip
Which is located in the below path:
/diag/collect-diagnostics-out
The following commands are executed:
–Session.log files – Vplexcli command history for a session
–Firmware.log files – system log messages from firmware on all directors
–configDump.xml files – system configuration information including views, ports, initiators and backend.
–Other logs include tracing from firmware, element manager, system messages, etc.
Run CMD on Management Server > Collect-Diagnostics
Note: Metroplex you will only get the management server logs (smsDump) from the management server where Collect-Diagnostics is run. You will not get the smsDump logs from the remote management server.
The collect-diagnostics works by invoking other log collection scripts and cli commands and collecting the results in a file, in the below Zip format
collect-diagnostics-<timestamp>.zip
Which is located in the below path:
/diag/collect-diagnostics-out
The following commands are executed:
- syrcollect -d /var/log/VS1/cli/collect-diagnostics-tmp
- director appdump -p -d /var/log/VS1/cli/collect-diagnostics-tmp
- sms dump -d /var/log/VS1/cli/collect-diagnostics-tmp/
- configdump for each cluster
- cluster configdump -c <cluster-name> -f <cluster-name>-configdump<timestamp>.xml
- storage-volume summary
- ds summary
- connectivity show
- validate-system-configuration --verbose
–Session.log files – Vplexcli command history for a session
–Firmware.log files – system log messages from firmware on all directors
–configDump.xml files – system configuration information including views, ports, initiators and backend.
–Other logs include tracing from firmware, element manager, system messages, etc.
VPLEX - Code Version Format
VPLEX - Code Version Format
Sample Format: A.B.C.DD.EE.FF
A - > The major release number
B - > The minor release number
C - > The service pack number ( 0 for first release)
DD - > The patch number
EE -> The HotFix number
FF - > The build number
Example:
5.0.0.00.00.11
Major 5
Minor 0
Service Pack 0
Patch 00
HotFix 00
Build 11
VPLEX Metro - inter-cluster connections/Communication Configuration
VPLEX Metro - inter-cluster connections/Communication Configuration
Requirement:
- FC ISL limitations at GA.
- ISL - not greater than 62 miles
- < 5ms latency
- SMS servers require VPN tunnel for connection.
VPLEX Local - Single Cluster 1,2,4 Engines.
VPLEX Metro - Upto <5ms Latency & Synchronous Communication
VPLEX Geo - Upto <50ms Latency & ASync Communication
VPLEX Global - both Sync and ASync Commuication
Configuration:
VPLEX Metro - Upto <5ms Latency & Synchronous Communication
VPLEX Geo - Upto <50ms Latency & ASync Communication
VPLEX Global - both Sync and ASync Commuication
Configuration:
Run the same connection between the clusters
Subscribe to:
Posts (Atom)