Viewing System Information After Redundancy Has Fully Started
Viewing Redundancy Configuration
Enter the following command to view details of the redundancy configuration:
redundancy show configuration
The output will be similar to the following:

Note the following points about the redundancy configuration:
- Replication type: Currently, this is always set to Geo redundant. Other modes may be available in future releases.
- Auto-failover: Possible values are: Enabled and Disabled. It is set to Enabled by default. The system will switch from the active to the passive when it determines that this is necessary. Auto-failover can be disabled, but this should be done with caution. For more information, see Disabling Automatic Failover.
Viewing Redundancy Status
Enter the following command to view the status of the redundancy feature:
redundancy show status
The output will be similar to the following:

The possible redundancy status results are as follows:
- Global Status: Possible values: Started, Stopped, Suspended.
- Node Status: Possible values: Active, Passive, Offline
- Replication status: Possible values: Up, Down, Synchronizing:
- Up means data is being transferred from the active to the passive site.
- Down means data is not being transferred from the active to the passive site. This is normal if the Global Status is Stopped or Suspended. This is not normal if the Global Status is Started.
- Synchronizing means the system is catching up on replicating data. This happens after redundancy starts or after a long suspension.
Viewing Redundancy Statistics
Enter the following command to view statistics about redundancy:
redundancy show statistics
The output will be similar to the following:

Note that the redundancy statistics that displayed are expressed in terms of the site on which you are logged on and currently viewing the statistics:
- Network sent: Data sent from the local site to the other site.
- Network received: Data received by the other site.
- Disk write: Data written on the local site.
- Disk read: Disk read on the local site.
- Out of sync: This value should be close to 0 during normal operations.
Viewing Partition Configuration
To view the partition configuration
- Open a terminal and connect to both sites using SSH on port 22.
- Run the
lsblkcommand. - Check the /mysql partition configuration.
- On Active site:
- The drbd0 must be mapped from sda8.
- The /mysql partition must be mounted on drbd0.
Example Output:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 150G 0 disk
├─sda1 8:1 0 243M 0 part /boot/efi
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 9M 0 part /PID
├─sda6 8:6 0 28G 0 part /
├─sda7 8:7 0 28G 0 part
├─sda8 8:8 0 28G 0 part
│ └─drbd0 147:0 0 28G 0 disk /mysql
├─sda9 8:9 0 37.3G 0 part /data
└─sda10 8:10 0 28.7G 0 part [SWAP]
- On Passive site:
- The drbd0 must be mapped from sda8.
- The /mysql partition must not be mounted on drbd0.
Example Output:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 150G 0 disk
├─sda1 8:1 0 243M 0 part /boot/efi
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 9M 0 part /PID
├─sda6 8:6 0 28G 0 part /
├─sda7 8:7 0 28G 0 part
├─sda8 8:8 0 28G 0 part
│ └─drbd0 147:0 0 28G 0 disk
├─sda9 8:9 0 37.3G 0 part /data
└─sda10 8:10 0 28.7G 0 part [SWAP]
If the output on either site is DIFFERENT from the examples above—for instance, if neither MySQL nor drbd0 is present after redundancy has fully started in the Active Site—contact our technical support team, as this could indicate a potential issue.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 150G 0 disk
├─sda1 8:1 0 243M 0 part /boot/efi
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 9M 0 part /PID
├─sda6 8:6 0 28G 0 part /
├─sda7 8:7 0 28G 0 part
├─sda8 8:8 0 28G 0 part
├─sda9 8:9 0 37.3G 0 part /data
└─sda10 8:10 0 28.7G 0 part [SWAP]
DO NOT attempt to start or stop the redundancy feature, or reboot the virtual machine.
Viewing System Information After Redundancy Has Fully Stopped
Verify that redundancy has completely stopped after executing the redundancy control stop command.
Viewing Redundancy Status
Skylight: redundancy show status
[ Redundancy status ]
Global Status : Stopped
Status is not available.
Viewing Partition Configuration
To view the partition configuration
- Open a terminal and connect to both sites using SSH on port 22.
- Check that the /mysql/data/visiondata/ folder exists and contains .ibd files by entering the
ls /mysql/data/visiondata/command.
Example Output:
$ ls /mysql/data/visiondata/
AAAJWTCONFIG.ibd COSPROFILEMO.ibd
messagebrokerconfig.ibd REQUESTADAPTER.ibd
towsess.ibd ACTIVEALARMCOUNTS.ibd
...
...
...
- Check /mysql partition configuration by entering the
lsblkcommand.
- The drbd0 partition does not appear in the output on either site.
- The /mysql partition should normally be mounted as designed to sda8.
Example Output:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 150G 0 disk
├─sda1 8:1 0 243M 0 part /boot/efi
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 9M 0 part /PID
├─sda6 8:6 0 28G 0 part /
├─sda7 8:7 0 28G 0 part
├─sda8 8:8 0 28G 0 part /mysql
├─sda9 8:9 0 37.3G 0 part /data
└─sda10 8:10 0 28.7G 0 part [SWAP]
If the output on either site is DIFFERENT from the examples above—for instance, if the /mysql partition is not mounted to sda8—contact our technical support team, as this could indicate a potential issue.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 150G 0 disk
├─sda1 8:1 0 243M 0 part /boot/efi
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 9M 0 part /PID
├─sda6 8:6 0 28G 0 part /
├─sda7 8:7 0 28G 0 part
├─sda8 8:8 0 28G 0 part
├─sda9 8:9 0 37.3G 0 part /data
└─sda10 8:10 0 28.7G 0 part [SWAP]
DO NOT attempt to start or stop the redundancy feature, or reboot the virtual machine.
© 2026 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and trademarks