VPLEX: Post upgrade to GeoSynchrony 6.1, License installing process fails with the error : "not supported for 'UNKNOWN' configuration" on GUI/CLI

           

   Article Number:     537840                                   Article Version: 2     Article Type:    Break Fix 
   

 


Product:

 

VPLEX VS6,VPLEX for All Flash,VPLEX GeoSynchrony,VPLEX Local,VPLEX Metro,VPLEX VS2,VPLEX GeoSynchrony 6.1,VPLEX GeoSynchrony 6.1 Patch 1,VPLEX GeoSynchrony 6.1 Patch 2,VPLEX Series

 

Issue:

 

 

Post upgrade of VPLEX to GeoSynchrony 6.1.x, the license installation fails with the error "License feature 'VPLEX_1TO1_FRAME' is not supported for 'UNKNOWN' configuration".   

     
      Example:     
                 service@<cluster-name>:~> vplexcli   
   
      Trying ::1...       
        Connected to localhost.       
        Escape character is '^]'.       
        VPlexcli:/>       
        VPlexcli:/> license install -l /home/service/CKxxxxxxxxxxxx_VPLEX_xxxxxxx_dd-Mon-YYYY.lic       
        license install:  Evaluation of <<license install ********>> failed.       
        cause:            Command execution failed.       
        cause:            Unable to install license.       
        cause:            License feature 'VPLEX_1TO1_FRAME' is not supported for 'UNKNOWN' configuration.
   
                                                             

 

 

Cause:

 

 

   

      The license install command fails with the cause License feature not supported for 'UNKNOWN' configuration. The 'UNKNOWNconfiguration refers to the VPLEX individual cluster configuration.    
                                                             

 

 

Resolution:

 

 

Workaround:   
   
    Step 1. Log in to the VPlexcli via the management server from which you are trying to install the license.   

     
      Example:     
          
   
      From cluster-1 management server:   
   
     
      service@<cluster-name>:~> vplexcli       
        Trying ::1...       
        Connected to localhost.       
        Escape character is '^]'.       
                       
        VPlexcli:/>
   
   
   
    Step 2. Verify you are on the right VPLEX cluster which is reporting the error during license install   
                 process.   
     
        Example:   
   
     
      From the VPlexcli:   
                          VPlexcli:/> ll management-server/   
      /management-server:       
       
        Attributes:       
        Name             Value       
        ---------------  --------------       
        cluster-ip-seed  2 <<
the mgmt server your are on     
      part-number      100-564-932-00       
        serial-number    FCNMC190500148
   
   
    Step 3. Check the configuration of the VPLEX cluster using the command   
                 "configuration get-product-type"    
     
        Example:   
                           VPlexcli:/> configuration get-product-type   
      The cluster is currently configured as a VPLEX Unknown <<   
   
   
    Step 4. The configuration needs to be changed to 'Metro' or 'Local' depending on the configuration   
                 type, if the VPLEX is a Metro configuration the configuration needs to be changed to 'Metro' if   
                 a 'Local' the VPLEX needs to be set for 'Local". To determine the configuration of the VPLEX   
                 from the VPLEX cli run the command   
   
                         "ll /engine/engine-*/directors/director-*/hardware/io-modules"   
   
                 from the output see if A2 is listed, if it is these are the WAN-COM modules only in a Metro   
                 configuration. If the A2 modules are not listed the VPLEX is a 'Local'.   
   
                 Example:   
       VPlexcli:/> ll /engines/engine-*/directors/director-*/hardware/io- modules       
       
        /engines/engine-1-1/directors/director-1-1-A/hardware/io-modules:       
        Name       
        ----       
        A0       
        A1       
        A2 <<<
indicates WAN-COM only in a Metro     
      A3       
        ... <truncated>
   
   
     
      Step 5. To set the product type follow the steps below     
     
                    a. at the VPlexcli run "script -i VPlexadmin"     
                    b. Next run the command "configuration set-product-type and enter the correct configuration     
                        type.     
                    c. Once set unimport the VPlexadmin script using "script -u VPlexadmin"     
          
   
      Example:   
                   
                         VPlexcli:/> script -i VPlexadmin   
              VPlexcli:/> configuration set-product-type   
      The cluster is currently configured as a VPLEX Unknown       
       
       
        This command will change the VPLEX product type for this cluster.       
        Do you want to continue? (Y/N): Y       
       
        Please enter a VPLEX Product Type [Local, Metro] or exit to quit: : Metro       
        The product type has successfully been set to VPLEX Metro       
       
        VPlexcli:/> script -u VPlexadmin
   
   
          
   
     
      Step 6. Re-try the license install command as attempted previously and verify the license is installed     
                   using the cluster status command.   
   
     
        Example:     
          
   
          
   
      VPlexcli:/> license install -l /home/service/CKxxxxxxxxxxxx_VPLEX_xxxxxxx_dd-Mon-YYYY.lic       
        License installed.       
                       
                       
        VPlexcli:/> cluster status       
       
        Cluster cluster-1       
        operational-status:            ok       
        transitioning-indications:       
        transitioning-progress:       
        health-state:                  ok       
        health-indications:       
        local-com:                     ok       
        certificates:                  ok       
        license:                       OK. License is installed. <<<       
       
        Cluster cluster-2       
        operational-status:            ok       
        transitioning-indications:       
        transitioning-progress:       
        health-state:                  ok       
        health-indications:       
        local-com:                     ok       
        certificates:                  ok       
        license:                       OK. License is installed. <<<