Insights, comments, tips and random ramblings.
This is the main feature. This only applies if you are running the Scale edition.
Multiple InfiniBand switches are now supported. SRP discovery and SRP traffic can be done on each switch.
Switches are monitored and alerts are generated should the switch fail.
But the most significant feature is the ability to multipath the same backend disk across multiple InfiniBand fabrics.
For single switch based configurations, the ZFS pool looks like this:
zetavault@head1:~# zpool status pool: zfs state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM zfs ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 serial-00d87518c7169c ONLINE 0 0 0 serial-00f40800c8289c ONLINE 0 0 0 errors: No known data errors
The disk devices names start "serial".
Once reconfigured as multipath, this is what the pool looks like:
zetavault@head1:~# zpool status pool: zfs state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM zfs ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 mpath-00d87518c7169c ONLINE 0 0 0 mpath-00f40800c8289c ONLINE 0 0 0 errors: No known data errors
The disk devices names now start "mpath".
Each "mpath" device is constructed from one or more SRP disks. Management is extremely easy.
With dual controllers, it is possible to move from a single switch configuration to a multiple switch setup without any downtime to the storage clients.
It is now possible to apply a custom date range in the Historical Monitor.
The custom range dialog also has a date picker.
The date picker is also used in other dialogs throughout the system.
The SNMP service has now been extended to monitor the health and capacity of each ZFS pool.
zetavault@head1:~# snmpwalk -c public -v2c localhost 184.108.40.206.4.1.43220.127.116.11.1 ZETAVAULT-MIB::poolName.0 = STRING: zfs1 ZETAVAULT-MIB::poolName.1 = STRING: zfs2 ZETAVAULT-MIB::poolHealth.0 = STRING: ONLINE ZETAVAULT-MIB::poolHealth.1 = STRING: DEGRADED ZETAVAULT-MIB::poolCapacity.0 = INTEGER: 35 ZETAVAULT-MIB::poolCapacity.1 = INTEGER: 10
The relevant OIDs are detailed in the SNMP help page.