5 Replies Latest reply on Jul 29, 2014 3:35 AM by Manjunat

    Cannot create VSA cluster createCluster() failed

    gatoadra Lurker

      Hi!

       

      I would like to test VSA cluster before I will buy it. But i cannot create it. I get message Cannot create VSA cluster: createCluster() failed. Unable to reconfigure back end interface.

      Can anyone help?

       

      ESX configuration (the same on both ESXs):

       

      vsa1.png

       

      vsa2.png

       

      vsa3.png

       

      VSAManager.log:

       

      2011-11-09 12:34:28,370 186 [BaseEventListener] [Thread-212] INFO  - Listening to topic: node.topic at URL failover:(ssl://172.16.24.53:61619?trace=true&daemon=true&keepAlive=true&soTimeout=60000)
      2011-11-09 12:34:28,370 152 [MessageListenerService] [Thread-212] INFO  - Initialized Node Event listener with 172.16.24.53
      2011-11-09 12:34:28,370 319 [ClusterService] [Thread-212] INFO  - Connect to VSA: 172.16.24.53
      2011-11-09 12:34:28,432 325 [ClusterService] [Thread-212] INFO  - Successfully login to VSA: 172.16.24.53
      2011-11-09 12:34:28,432 132 [SvaMessagingService] [Thread-212] INFO  - createStorageCluster()
      2011-11-09 12:34:29,056 166 [SvaMessagingService] [Thread-212] ERROR - createCluster() failed.Unable to reconfigure back end interface.
      2011-11-09 12:34:29,072 61 [PersistenceService] [Thread-212] INFO  - clear Data - Key: createClusterTask
      2011-11-09 12:34:29,119 169 [BaseEventListener] [Thread-212] INFO  - Stopping the JMS listener connection on 172.16.24.51
      2011-11-09 12:34:29,119 169 [BaseEventListener] [Thread-212] INFO  - Stopping the JMS listener connection on 172.16.24.53
      2011-11-09 12:34:29,119 169 [BaseEventListener] [Thread-212] INFO  - Stopping the JMS listener connection on 172.16.24.51
      2011-11-09 12:34:29,119 169 [BaseEventListener] [Thread-212] INFO  - Stopping the JMS listener connection on 172.16.24.53
      2011-11-09 12:34:29,119 188 [CreateClusterThread] [Thread-212] ERROR - Create cluster failed:
      java.lang.Exception: createCluster() failed.Unable to reconfigure back end interface.
          at com.vmware.sva.manager.service.SvaMessagingService.createStorageCluster(SvaMessagingService.java:167)
          at com.vmware.sva.manager.service.ClusterService.createCluster(ClusterService.java:336)
          at com.vmware.sva.manager.service.SessionService.createCluster(SessionService.java:421)
          at com.vmware.sva.manager.service.CreateClusterThread.run(CreateClusterThread.java:178)
      2011-11-09 12:34:29,134 61 [PersistenceService] [Thread-212] INFO  - clear Data - Key: createClusterTask
      2011-11-09 12:34:29,150 193 [Utils] [Thread-212] INFO  - Retrieve dev.property: vm.rollback=true
      2011-11-09 12:34:56,263 88 [SVAManager] [http-127.0.0.1-8080-5] INFO  - VSA Manager dummyPing invoked.
      2011-11-09 12:35:03,017 206 [FailoverTransport] [InactivityMonitor Async Task: java.util.concurrent.ThreadPoolExecutor$Worker@1a56832c] WARN  - Transport failed to ssl://172.16.24.51:61619?trace=true&daemon=true&keepAlive=true&soTimeout=60000 , attempting to automatically reconnect due to: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long: 172.16.24.51/172.16.24.51:61619
      2011-11-09 12:35:03,017 206 [FailoverTransport] [InactivityMonitor Async Task: java.util.concurrent.ThreadPoolExecutor$Worker@1a56832c] WARN  - Transport failed to ssl://172.16.24.51:61619?trace=true&daemon=true&keepAlive=true&soTimeout=60000 , attempting to automatically reconnect due to: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long: 172.16.24.51/172.16.24.51:61619
      2011-11-09 12:35:03,017 141 [BaseEventListener] [InactivityMonitor Async Task: java.util.concurrent.ThreadPoolExecutor$Worker@1a56832c] INFO  - TransportListener: transportInterupted
      2011-11-09 12:35:08,353 206 [FailoverTransport] [InactivityMonitor Async Task: java.util.concurrent.ThreadPoolExecutor$Worker@7977afca] WARN  - Transport failed to ssl://172.16.24.53:61619?trace=true&daemon=true&keepAlive=true&soTimeout=60000 , attempting to automatically reconnect due to: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long: 172.16.24.53/172.16.24.53:61619
      2011-11-09 12:35:08,353 206 [FailoverTransport] [InactivityMonitor Async Task: java.util.concurrent.ThreadPoolExecutor$Worker@7977afca] WARN  - Transport failed to ssl://172.16.24.53:61619?trace=true&daemon=true&keepAlive=true&soTimeout=60000 , attempting to automatically reconnect due to: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long: 172.16.24.53/172.16.24.53:61619
      2011-11-09 12:35:08,353 141 [BaseEventListener] [InactivityMonitor Async Task: java.util.concurrent.ThreadPoolExecutor$Worker@7977afca] INFO  - TransportListener: transportInterupted
      2011-11-09 12:39:48,935 629 [SVAVMConfigurator] [Thread-212] ERROR - Destroy VSA VM failed with error: Client side time out waiting for task to comeplete
      2011-11-09 12:39:48,935 193 [Utils] [Thread-212] INFO  - Retrieve dev.property: ha.config=true
      2011-11-09 12:39:48,935 221 [CreateClusterThread] [Thread-212] INFO  - Undoing HA configuration
      2011-11-09 12:39:56,922 88 [SVAManager] [http-127.0.0.1-8080-5] INFO  - VSA Manager dummyPing invoked.
      2011-11-09 12:41:32,410 193 [Utils] [Thread-212] INFO  - Retrieve dev.property: network.config=true
      2011-11-09 12:41:32,410 231 [CreateClusterThread] [Thread-212] INFO  - clearing the host network configuration

        • 1. Re: Cannot create VSA cluster createCluster() failed
          lvong Novice
          VMware Employees

          Try settting vmnic1 and vmnic3 into a separate subnet then vmnic0 and vmnic2. 

          • 2. Re: Cannot create VSA cluster createCluster() failed
            Enthusiast

            Please check the KB below

             

            vSphere Storage Appliance (VSA) network troubleshooting (2007363)

            http://kb.vmware.com/kb/2007363


             

             

            In that KB there is a "Case C" which is not visible publicly yet.

             

            Issue:

            VSA Cluster creation fails with: “Unable to reconfigure back end interface”

            Reason:

            The IPs of the back-end interface (192.168.0.1, 192.168.0.2, ...) are already in use in the network (2 or 3 IPs, depending if the VSA cluster has 2 or 3 nodes).

            To verify that, from any OS with access to the back end network (if using VLANs) or from vCenter Server (if not using VLANs) ping those IPs to ensure nobody responds.
            Other reasons may lead to this error.
            Resolution:
            Make sure that these IPs are not assigned or in use by any OS on the back end network.
            • 3. Re: Cannot create VSA cluster createCluster() failed
              gatoadra Lurker

              Many thanks for response.

              I will check it today.

              • 4. Re: Cannot create VSA cluster createCluster() failed
                gothicreader Novice

                For the past day the VSA cluster build was crapping out on me. Each time I used the format the disk immediately to save time when VMs were being deployed, the cluster after an hour or so would error out and rollback the cluster.

                I started to look at the log files and noticed an error "ERROR - createCluster() failed.Unable to reconfigure back end interface." At this point I checked my networking vswitches for my cluster and those were setup correctly.

                The last time I tried to build the cluster I used the option the format the disk after the cluster is built and for the first deployed virtual machine. The cluster build failed, again. However, I was able to see the message "Cannot create VSA cluster createCluster() failed. Unable to reconfigure back end interface".

                This was the problem all along. In my test environment I have an existing VSA cluster under the same IP schema 192.168.1.x. When the second cluster is being built on the same network the backend IP address was being used starting with 1 and my second cluster was using the same backend IP address. Once I changed the backend IP address - the cluster completed without any errors.

                 

                I hope this helps others...................

                • 5. Re: Cannot create VSA cluster createCluster() failed
                  Manjunat Lurker

                  Thanks a Ton...It worked....