This article is intended for administrators wishing to configure event notifications for reporting. This enables SvHCI hosts and SvSAN VSAs to forward alerts to the preferred technology of choice.
These could be Splunk (Syslog), ServiceNow (SMTP), Microsoft SCOM (SNMP) etc.
Resolution/Information
Overview
SvHCI and SvSAN provides numerous reporting methods to monitor and alert based upon certain events detailed below.
| Reporting method | Knowledgebase |
|---|---|
| Reporting via SMTP | SMTP Reporting/Notifications/Alerts |
| Reporting via SNMP | SNMP Reporting/Notifications/Alerts |
| Reporting via Syslog | SYSlog Reporting/Notifications/Alerts |
| Reporting via vCenter Forwarding | vCenter Forwarding/Notifications/Alerts |
Common Events
System
| Severity | Event | Notes |
|---|---|---|
| Informational | Appliance started | Appliance started |
| Informational | Appliance restarted | Appliance restarted |
| Informational | Appliance shut down | Appliance shut down |
| Informational | Firmware version 6.3.P2.51846 was written successfully | Written but may not yet be applied, e.g. system may not yet have restarted |
| Informational | Default route was created on interface 'VM Network' | |
| Informational | Interface 'Storage1' was created | |
| Informational | The appliance password was changed | |
| Informational | Running firmware version 6.3.P1.51791 | Posted at each boot |
| Informational | Running firmware version 6.3.P1.51791 | Posted at each boot |
| Informational | Debug mode was entered | Debug mode enables SSH to the appliance and is only accessible via the StorMagic Support Team |
| Informational | Debug mode was exited | Debug mode enables SSH to the appliance and is only accessible via the StorMagic Support Team |
| Warning | System has been in an abnormal state for the last hour | The VSA status has been in Warning for a long period and should be investigated |
| Informational | Name server '2' was set to '192.168.1.1' | |
| Informational | Hostname was set to 'VSA1' | |
| Informational | Physical interface '00:15:5D:AA:07:05' was added | |
| Informational | Appliance started | |
| Informational | Appliance shut down | |
| Informational | Interface 'Default 00:15:5D:0A:0D:69' acquired a DHCP lease on ""'192.168.10.81' | |
| Informational | License key ABCD-EFGH-IJKL was set | |
| Informational | Domain name was set to 'stormagic.local' | |
| Informational | Hostname was set to 'VSA-HOST01' | |
| Informational | Successful logout from 192.168.10.13 | |
| Informational | Interface 'iSCSI-10G' was modified | |
| Informational | Previous event was repeated 12 times | |
| Informational | Network device settings were modified for 'eth2'(00:15:5D:EE:C2:02) | |
| Informational | NTP server was set to 'pool.ntp.org' | |
| Informational | This system is licensed, but also has evaluation features with 239 hour(s) remaining | |
| Informational | Appliance rebooted | |
| Informational | Connecting to VSA1.stormagic.local - 1 outbound connections to establish | |
| Informational | Remote syslog server 'splunk' was added | |
| Informational | Remote syslog server 'splunk' was removed | |
| Warning | Appliance was not safely shut down | Log data that was held in memory will have been lost during a hard reboot |
| Warning | There is an IP conflict on 10.10.48.67 between interface VM Network and 1C:98:EC:FA:98:3F | An IP conflict between the VSA and another device with MAC address shown, should be investigated and resolved |
| Warning | The maintenance for this system has expired | The maintenance for this system has expired |
| Warning | An unsuccessful login attempt was made from 10.102.0.16 | An incorrect password was entered via the VSA Web Client or the plugin VM has old cache credentials. Note the IP address of the login attempt |
| Error | The evaluation features have expired | Evaluation time against caching for example may continue after a Production license has been applied that doesn't have the caching feature |
| Error | The system is not licensed | |
| Error | iSCSI connection from '10.20.1.80' on non-iSCSI interface 'VM " "Network' was rejected |
Targets and mirrors
| Severity | Event | Notes |
|---|---|---|
| Informational | A simple target was created | A simple target was created |
| Informational | Target 'm0datastore' was created (6.13 TB) | A mirrored target was created |
| Informational | Mirrored target 'm0datastore' was created with remote plex 'demo-vsa1.ts.stormagic.com' (6431092 MB) | A mirrored target was created, synchronizing it's data to demo-vsa1. e.g. only posted on VSA with the initial synchronized data |
| Informational | Target 'm0svsandatastore' was deleted | |
| Informational | Target 'm0svsandatastore' was enabled | iSCSI access to a target was enabled |
| Informational | Target 'm0svsandatastore' was disabled | This would force logout any incoming initiators that may be expecting to access the disk/target |
| Information | Target 'm0svsandatastore' was deleted | A target was destroyed |
| Informational | Mirrored target 'm0svsandatastore': plex 'demo-vsa1' is synchronized | A mirror plex was resynchronized. This event will be posted on the VSA that was previously unsynchronized, i.e. the receiver. |
| Informational |
Connection to node 'demo-vsa1' was established or Connection to node 'demo-witness' was established |
Connectivity between devices was re-established |
| Informational | Rebuilding SSD cache after abnormal shutdown | Rebuilding SSD cache after abnormal shutdown |
| Informational | Login [demo-esxi2.ts.stormagic.com:m0datastore] on interface 'SvSAN2PG [192.168.2.4]' | An initiator has logged in to a Target on an interface |
| Informational | Logout [demo-esxi2.ts.stormagic.com:m0webinar.421] | An initiator has logged out of a Target on an interface |
| Informational | Plex 'NVLPLSTORMAGIC2.oshpd.gov' was broken away from mirrored " "target 'm0svsanmirror'; new target 'Simple' |
|
| Informational | Target 'm0svsanmirror' has Prefer Local Path set and now has a " 'local initiator in its access control list |
|
| Informational | Plex 'A4A2E2256F84' was added to mirrored target 'M0deployed' | |
| Informational | Plex 'A4A2E2256F84' was removed from mirrored target 'm0deployed' | |
| Informational | Target 'm0svsanmirror' has recovered | |
| Informational | Target 'encrypted' was resized from 300 MB to 400 MB | |
| Informational | System does not appear to have been shut down cleanly. Forcing full mirror resynchronization | |
| Warning | Synchronization state of plex 'mhp-dep-mv01212' on mirrored target 'm0deployed' was manually overridden | |
| Warning | Mirrored target 'allflash': plex 'demo-vsa2' is unsynchronized | A mirror plex became unsynchronized, e.g. the partner VSA became uncontactable over all available network interfaces |
| Warning | Connection to node 'demo-witness.ts.stormagic.com' was lost | The VSAs have lost connectivity to the witness on all available interfaces |
| Warning | Connection to node 'demo-vsa1.ts.stormagic.com' was lost | The VSA have lost connectivity to the partner VSA on all available interfaces |
| Warning | Login failure iqn.1998-01.com.vmware:demo-esxi2.ts.stormagic.com:2039985455:65 : iqn.2006-06.com.stormagic:60d86a0200000137.m0backupstore: Target Not Found | An initiator is looking for a target in it's discovery list that doesn't exist on this VSA |
| Warning | Unexpected disconnection on iSCSI session [SRV-03:m0svsan1.4] | An initiator unexpectedly dropped it's connection. Such as a compute only node having a network drop to the storage |
| Warning | Login failure [ESXi-host01:m0svsandatastore.5]: Authentication Failure: ' 'Authentication failure |
|
| Warning | m0deallvic30vsad02' node '0D72359E02C1' cannot be discovered | |
| Error | Mirrored target 'm0svsandatastore' was taken offline due to loss of quorum | Having first lost connectivity to the witness then the partner VSA this storage is now failed safe and unavailable due to network isolation and prevent data corruption |
| Error | A mirror plex went offline due to a storage failure | This VSA is no longer serving storage, with the I/O being proxied to the other VSA |
| Error | iSCSI Service exited unexpectedly and has been restarted | This VSA is no longer serving storage |
| Error | Resynchronization of plex 'mhp-dep-mv01213' on mirrored target 'm0deployed' failed. Forcing full resynchronization | |
| Error | Mirrored target 'm0deployed' was taken offline due to loss of quorum | |
| Error | Orphaned target entry 'ORPHANb112480900000012' was created |
Storage devices
| Severity | Event | Notes |
|---|---|---|
| Informational | Pool 'P1680768490944' was created (6.13 TB) | A storage pool was created |
| Informational | Pool 'P1680768490944' storage device is back online after a failure/timeout | I/O issues to underlying storage device |
| Informational | RAID subsystem 'Direct Device Mapping' device added 'P1680768490944' (SCSI:0:0:2:0) | A storage device was added and an existing pool signature detected |
| Informational | SSD cache storage was created on pool 'C1680768494080' (600 GB) | |
| Informational | The storage journal was restarted (sequence number 64) | |
| Informational | The storage journal has been created on device SCSI:1:0:0:0 | |
| Informational | The storage journal has been extended | |
| Informational | Pool 'WLOG_DISK' storage device is back online after a " 'failure/timeout |
|
| Warning | Pool 'WLOG_DISK' storage I/O timeout | |
| Warning | Pool 'pool0' storage I/O timeout | |
| Warning | Pool 'SvSAN_HDD' had '100' I/Os with latencies of at least '10' seconds in the last '5' minutes | |
| Error | The storage journal failed | The storage journal failed |
| Error | A storage device failed | A storage device failed |
| Error | Mirrored target 'm0svsandatastore' was taken offline after detection of split brain operation | Only possible on an UP mirror, not a majority quorum based mirror |
| Error | Pool 'P1680768490944' storage device has failed | I/O issues to underlying storage device |
| Error | RAID subsystem 'Direct Device Mapping' device removed '' (SCSI:0:0:2:0) | A storage device was removed |
| Error | Target 'm0datastore' pool 'P1680768490944' storage I/O error LBA 202643712: 128 | I/O issues to underlying storage device |
| Error | Storage journal disk has failed |
Caching
| Severity | Event | Notes |
|---|---|---|
| Informational | Memory cache storage was created | |
| Informational | SSD cache storage was created on pool 'CACHE01' (1.75 TB) | |
| Informational | Enabled read-ahead on target 'm0svsandatastore' | |
| Informational | SSD cache storage was deleted | |
| Informational | Removal of 'm0svsandatastore' SSD cache deferred until dirty data has been ''flushed.' | |
| Informational | SSD caching on target 'm0svsandatastore' was enabled | |
| Informational | Disabled read-ahead on target 'm0svsandatastore' | |
| Warning | Failed SSD cache storage has been replaced discarding all cached data | |
| Warning | Caching is running with limited memory | |
| Warning | SSD cache is filling faster than it can be flushed; caching may be ineffective | |
| Warning | SSD caching effective after reclaiming space | |
| Error | SSD cache storage has failed |
Encryption
| Severity | Event | Notes |
|---|---|---|
| Informational | Connected to key server | |
| Informational | Target "m0encryptedsvsandatastore" starting encryption | |
| Informational | Target "m0encryptedsvsandatastore" encryption complete | |
| Informational | Encrypted Target "m0encryptedsvsandatastore" is online | |
| Informational | Target "m0encryptedsvsandatastore" starting encryption re-keying | |
| Informational | Target "m0encryptedsvsandatastore" encryption re-key complete | |
| Informational | Target "m0encryptedsvsandatastore" starting decryption | |
| Informational | Target "m0encryptedsvsandatastore" decryption complete | |
| Warning | Key Management Server 'SvKMS1' certificate is due to expire within 11 day(s) | Starts at 30 days and notifies daily |
| Error | Failed to connect to key Server | |
| Error | Failed to get encryption keys for target | |
| Error | Target "m0encryptedsvsandatastore" unable to get encryption key |
See Also
Comments
0 comments
Article is closed for comments.