XtremIO: Configuration file not sent to CLM when using the Legacy ESRS-GW and Email Call Home Notification configurations on XMS version 6.2.1-36

           

   Article Number:     532295                                   Article Version: 4     Article Type:    Break Fix 
   

 


Product:

 

XtremIO Family,XtremIO X1,XtremIO X2

 

Issue:

 

 

With XMS version 6.2.1-36 that is using the legacy ESRS-GW or Email Call Home Notifications configurations, the sending of a configuration file to CLM for the affected cluster is not working.   
   
    Note: This issue affects X1 and X2 clusters connected to an XMS with version 6.2.1-36.   
   
    Note: This issue does not affect the sending of alerts to CLM for the affected cluster or the triggering of Support Request based on these alerts.   
   
    Note: This issue does not affect the ESRS-VE Call Home Notifications configuration with XMS version 6.2.1-36.   
   
    Note: This issue does not affect connect-in/remote access to clusters connected to XMS with version 6.2.1-36.   
   
    Note: This issue does not affect CloudIQ services as these use the ESRS-VE Call Home Notifications configuration with XtremIO clusters.   

Follow the steps below to check if the connected XMS is affected by this issue:    
   
         
  1.         Connect to the XMS as admin     
  2.      
  3.         Verify the XMS version by running the show-xms XMCLI command     
  4.    
   
      Example: show-xms command output when the XMS is running version 6.2.1-36     
      xmcli (tech) > show-xms     
      Name Index SW-Version Xms-IP-Addr Xms-Mgmt-Ifc REST-API-Protocol-Version IP-Version Default-User-Inactivity-Timeout     
      xms   1    6.2.1-36   <XMS IP>     eth0         2.0                       ipv4      10   
   
         
  1.         Execute the show-syr-notifier XMCLI command to verify that the Call Home Notifications configuration currently set on the XMS is legacy ESRS-GW or Email     
  2.    
   
      Example: show-syr-notifier command output when the legacy ESRS-GW Call Home Notifications configuration is currently set on the XMS     
      xmcli (tech)> show-syr-notifier       
        Enabled: True       
        Config-File-Frequency (hours): 24       
        Advisory-Polling-Interval (hours): 24       
        ConnectEMC-Config: ----->       
        Connection Type: ESRS Gateway (Legacy)       
        URL: https://10.76.223.64:443/incoming       
        Site Name: 15112364
     
      PSNT: XIOAPPLAB00101     
     
      Example: show-syr-notifier output when the Email Call Home Notifications configuration is currently set on the XMS     
        xmcli (tech)> show-syr-notifierEnabled: TrueFrequency (hours): 24ConnectEMC-Config: ----->ConnectionType: EmailEmailServer: smtp-serverEmailSender: xmsEmailAddress: emailalert@emc.comSite Name: 15112364PSNT: XIOAPPLAB00101      
   
    ​​​​​​                                                           

 

 

Cause:

 

 

This issue is due to an XMS software issue with the SYR notifier service code for all ConnectEMC-based Call Home Notification configurations (i.e. legacy ESRS-GW and Email). Due to this issue, for these Call Home Notification configurations only, a cluster log bundle is generated but is not passed to ConnectEMC for sending to CLM.   

     
                                                             

 

 

Resolution:

 

 

Workaround:   
    To resume the sending of configuration files from the affected cluster, switch to the ESRS-VE Call Home Notifications configuration on the XMS connected to the cluster. For details on switching to the ESRS-VE Call Home Notifications configuration refer to Dell EMC KB# 519311 (https://support.emc.com/kb/519311).   
   
    This workaround is most suitable for XMSes connected to an ESRS-VE GW machine.   
   
    For XMSes currently connected to a customer SMTP server and using the Email Call Home Notification configuration, this workaround will require the customer to agree to use ESRS and to deploy an ESRS-VE GW machine. Refer to Dell EMC KB# 519311 for details on this.   
   
    Contact EMC Global Tech Support to perform this workaround on the connected XMS.