2 Replies Latest reply on Oct 9, 2014 6:54 AM by gwielen

    VSA appliances online and one replica degraded

    gwielen Novice

      To whom who can help,

       

      I have a 2 node VSA cluster and since one week the vsa-0 replica is degraded. VSA-0 and VSA-1 are online and functioning, but the replica will not sync. VSA-1 and replica are online and all of the datastores are onine and reacheble.

      I have tried to put the cluster into maintenance mode, but it won't let me since the cluster is in a degraded state. I have reset the vsa-0 VM, also reset the VSA-1 VM, but stil no replication. I have verified the backend network and all is stable and both ip's 192.168.0.1 and 192.168.0.2 are pingable from each VSA VM.

       

      Here is a copy of the GetStorageCluster state

       

      Storage Cluster ID = e25367e8-a632-4aa5-bc95-1898232be780

      Name = vStorage Cluster

      Maintenance mode = false

      Management interface = 192.168.1.234/24

      Master = 780c3ce1-4eb9-45a7-bdde-ab44db2aa789

      VSA Cluster Service address = 192.168.1.230

      VSA Cluster Service State = true

      Physical capacity = 140063539250 KB (13357.50 GB)

      Storage capacity = 7003176960 KB (6678.75 GB)

      ### Members:

      Member 0:

                        SVA ID = 780c3ce1-4eb9-45a7-bdde-ab44db2aa789

                        Name = localhost

                        Maintenenace mode = false

                        Domain name = localdom

                        Member ID = fbb84973-489b-4373-99d0-911155b92765

                        Storage Cluster ID = e25367e8-a632-4aa5-bc95-1898232be780

                       Primary member = true

                        State = ONLINE

                        Management interface = 192.168.1.235/24

                        Internal interface = 192.168.0.1/24

                        No DNS servers

                        Gateway = 192.168.1.8

                        Total storage = 7003176960KB

                        Free storage = 0KB

                        Used storage = 7003176960KB

                        Storage pool 0:

                                               ID = 00000000-0000-0000-0000-000000000000

                                               Total storage = 7003176930

                                               Free storage = 0

                                               Used storage = 7003176960

                        Export storage entities:

                                                              64c06faf-b13e-42d1-06fa-dfff425f1e89

                                                               e1cf17b3-31c6-4e62-bbd1-d4118796bc76

       

       

      Member 1:

              SVA ID = e56947bc-17d0-4e35-a9fe-6d8de7c1d6b8

              Name = localhost

              Maintenenace mode = false

              Domain name = localdom

              Member ID = 5220d8f5-a934-4392-9941-811c240d1f17

              Storage Cluster ID = e25367e8-a632-4aa5-bc95-1898232be780

        Primary member = true

              State = ONLINE

              Management interface = 192.168.1.237/24

              Internal interface = 192.168.0.2/24

              No DNS servers

              Gateway = 192.168.1.8

              Total storage = 7003176960KB

              Free storage = 0KB

              Used storage = 7003176960KB

              Storage pool 0:

                      ID = 00000000-0000-0000-0000-000000000000

                      Total storage = 7003176960

                      Free storage = 0

                      Used storage = 7003176960

              No exported entities

       

       

      ### Storage Entities:

      Storage entity 0:

      NFSv3StorageEntity:

              Id = 64c06faf-b13e-42d1-a6fa-dfff425f1e89

              Name = NFSv3StorageEntityBlc-64c06faf-b13e-42d1-a6fa-dfff425f1e89

              State = DEGRADED

        AccessInterface 192.168.1.238/24

        Export Member SVA id = 780c3ce1-4eb9-45a7-bdde-ab44db2aa789

        # Exports = 1

        Export[0]:

        Name = NFSv3StorageEntityBlc-780c3ce1-4eb9-45a7-bdde-ab44db2aa789

        Id = 780c3ce1-4eb9-45a7-bdde-ab44db2aa789

        StorageEntity id = 64c06faf-b13e-42d1-a6fa-dfff425f1e89

        Export Path = /exports/f56b8f51-ad01-4a51-a7bbe-dfff425f1e89

        Acl[] = [192.168.1.231 192.168.1.232 192.168.1.239 192.168.1.233 192.168.1.240]

        Volume:

                              Name = Volume-50a539f8-1601-45a3-b273-893188fffbdb

                              Id = 50a539f8-1601-45a3-b273-893188fffbdb

                              Size = 3501588480

                              Primary Owner = 780c3ce1-4eb9-45a7-bdde-ab44db2aa789

                              Current Owner = 780c3ce1-4eb9-45a7-bdde-ab44db2aa789

                              Export Id = f56b8f51-ad01-4a51-a7be-e1cf9813a8bf

                              State = DEGRADED

                              Type = RAID1

                              # Disks = 2

                              Sync Percent = 100.00 %

        Sync Time-to-Complete = 0 sec.

        Sync Speed = - KB/s

        Disk[0]

        Name = Disk-af0eb237-3d83-478a-a517-18ea3372cfc4

        Id = af0eb237-3d83-478a-a517-18ea3372cfc4

        Owner id = 780c3ce1-4eb9-45a7-bdde-ab44db2aa789

        State = ONLINE

        Synced = true

        Disk[1]

        Name = Disk-c4d0d82a-51b7-4b3b-a36e-96482cd57f26

        Id = c4d0d82a-51b7-4b3b-a36e-96482cd57f26

        Owner Id = e56947bc-17d0-4e35-a9fe-6d8de7c1d6b8

        State =  FAULTED

        Synced =  false

      Storage entity 1:

      NFSv3StorageEntity:

              Id = e1cf17b3-31c6-4e62-bbd1-d4118796bc76

              Name = NFSv3StorageEntityBlc-e1cf17b3-31c6-4e62-bbd1-d4118796bc76

              State = DEGRADED

        AccessInterface = 192.168.1.236/24

        Export Member SVA id = 780c3ce1-4eb9-45a7-bdde-ab44db2aa789

        # Exports = 1

        Export[0]:

        Name = NFSv3Export-6daa557f-52ff-4cae-b548-a4e307ec003f

        Id = 6daa557f-52ff-4cae-b548-a4e307ec003f

        StorageEntity id = e1cf17b3-31c6-4e62-bbd1-d4118796bc76

        Export Path = /exports/6daa557f-52ff-4cae-b548-a4e307ec003f

        Acl[] = [192.168.1.231 192.168.1.232 192.168.1.239 192.168.1.233 192.168.1.240]

        Volume:

                              Name = Volume-c0e96f41-5402-459a-8a08-e328b26a1d16

                              Id = c0e96f41-5402-459a-8a08-e328b26a1d16

                              Size = 3501588480

                              Primary Owner = e56947bc-17d0-4e35-a9fe-6d8de7c1d6b8

                              Current Owner = 780c3ce1-4eb9-45a7-bdde-ab44db2aa789

                              Export Id = 6daa557f-52ff-4cae-b548-a4e307ec003f

                              State = DEGRADED

                              Type = RAID1

                              # Disks = 2

                              Sync Percent = 100.00 %

        Sync Time-to-Complete = 0 sec.

        Sync Speed = - KB/s

        Disk[0]

        Name = Disk-832b8479-cc93-4f3f-8b89-b9c2e999784e

        Id = 832b8479-cc93-4f3f-8b89-b9c2e999784e

        Owner id = e56947bc-17d0-4e35-a9fe-6d8de7c1d6b8

        State = FAULTED

        Synced = false

        Disk[1]

        Name = Disk-64911541-7e42-408b-a2ec-cb89279b806d

        Id = 64911541-7e42-408b-a2ec-cb89279b806d

        Owner Id = 780c3ce1-4eb9-45a7-bdde-ab44db2aa789

        State =  ONLINE

        Synced =  true

       

      Any help would be apreciated

        • 1. Re: VSA appliances online and one replica degraded
          Lurker

          Both the VSA datastores are getting exported out of one VSA appliance hence the replica sync is not happening. There should have been some failure because of which the VSA datastore must have failed over to other alive appliance. Ideally when the other VSA comes up fall back followed by data sync should have happened. But it did not happen in this case. In the VSA manager you should be able to see this. Both the VSA datastores are exported from one appliance and other appliance has both replicas.

          Try to ping VSA 1 from VSA 0. Or Restart the VSA 1appliance (the one which shows both replicas).

           

          Thanks,

          Chittra

          • 2. Re: VSA appliances online and one replica degraded
            gwielen Novice

            Deat Chittra,

             

            Thanks for your educated aswer. I am able to ping from VSA-0 and VSA-1 all other ip's that does matter, so I can ping VSA's, frontend, backend, Cluster Network, Datastores, Cluster Service etc, etc. I believe that this thing started after a network related problem, but that was fixed quickly, but it has left we with a somewhat odd VSA configuration.

             

            I am not able to restart the VSA-1 due to production servers running now, but I'll do so in the weekend. I have done this before and nothing changed, but I'll do it again just bacause I can...

             

            Cheers,

             

            Goswin.