Quantcast
Channel: VMware Communities: Message List - vSphere™ Storage
Viewing all articles
Browse latest Browse all 5826

vSphere 6u2 and EMC UnityVSA and VVOLs -> Protocol Endpoints are not created

$
0
0

Hi all,

 

I've just installed UnityVSA from EMC (Version 4.0.1) in my lab with vSphere 6u2.

 

I've created an old fashioned VMFS-Datastore on a LUN and an NFS-Datastore on a share. Everything is working fine.

 

Then I created using Unisphere a Datastore for blockbased VVOLs (via iSCIS) and for filebased VVOLs (via NFS). Everything went fine in the UnityVSA.

 

Then I added the StorageProvider in vCenter - also this workes without error.

 

BUT: There are no PEs created on the vSphere.

 

The PEs are present on the UnityVSA (output from uemcli executed directly on the UnityVSA):

 

18:25:40 service@VIRT1636W2LHJW-spa spa:~> uemcli -d localhost -u admin -securePassword /stor/prov/vmware/pe show

Password:

Storage system address: localhost

Storage system port: 443

HTTPS connection

 

 

1:    ID                   = rfc4122.b835c8dd-5cc2-48d8-9bb6-4e1483c35ecf

      Name                 = nas_pe_3

      Type                 = NAS

      VMware UUID          = rfc4122.b835c8dd-5cc2-48d8-9bb6-4e1483c35ecf

      Export path          = 192.168.4.33:/rfc4122.3c70af02-00ad-4d9e-be70-16fe20fe07e7

      IP address           = 192.168.4.33

      WWN                  =

      Default SP           =

      Current SP           =

      NAS Server           = nas_1

      VMware NAS PE server = PES_1

      VVol datastore       = res_9

      Host                 =

      Health state         = OK (5)

      Health details       = "The protocol endpoint is operating normally. No action is required."

 

 

2:    ID                   = rfc4122.60060160-b2ed-2021-a932-d2f0067c0253

      Name                 = scsi_pe_13

      Type                 = SCSI

      VMware UUID          = rfc4122.60060160-b2ed-2021-a932-d2f0067c0253

      Export path          =

      IP address           =

      WWN                  = 60:06:01:60:B2:ED:20:21:A9:32:D2:F0:06:7C:02:53

      Default SP           = SPA

      Current SP           = SPA

      NAS Server           =

      VMware NAS PE server =

      VVol datastore       =

      Host                 = Host_1

      Health state         = OK (5)

      Health details       = "The protocol endpoint is operating normally. No action is required."

 

 

3:    ID                   = rfc4122.60060160-b2ed-2021-a2df-e66d9f94b2d1

      Name                 = scsi_pe_14

      Type                 = SCSI

      VMware UUID          = rfc4122.60060160-b2ed-2021-a2df-e66d9f94b2d1

      Export path          =

      IP address           =

      WWN                  = 60:06:01:60:B2:ED:20:21:A2:DF:E6:6D:9F:94:B2:D1

      Default SP           = SPA

      Current SP           = SPA

      NAS Server           =

      VMware NAS PE server =

      VVol datastore       =

      Host                 = Host_2

      Health state         = OK (5)

      Health details       = "The protocol endpoint is operating normally. No action is required."

 

 

4:    ID                   = rfc4122.60060160-b2ed-2021-b146-73a102b508cf

      Name                 = scsi_pe_15

      Type                 = SCSI

      VMware UUID          = rfc4122.60060160-b2ed-2021-b146-73a102b508cf

      Export path          =

      IP address           =

      WWN                  = 60:06:01:60:B2:ED:20:21:B1:46:73:A1:02:B5:08:CF

      Default SP           = SPA

      Current SP           = SPA

      NAS Server           =

      VMware NAS PE server =

      VVol datastore       =

      Host                 = Host_3

      Health state         = OK (5)

      Health details       = "The protocol endpoint is operating normally. No action is required."

 

 

19:02:21 service@VIRT1636W2LHJW-spa spa:~>

 

Also the appropriate LUNs for the blockbased VVOLs are created and provisioned (snipplet form vmkernel.log from one of the ESXi; the iSCSI-LUNs are available via two paths):

 

2016-09-09T18:38:00.810Z cpu3:32925)ScsiPath: 604: Path vmhba33:C0:T3:L1023 is a VVol PE (ver:6)

2016-09-09T18:38:00.811Z cpu1:32924)ScsiPath: 604: Path vmhba33:C0:T2:L1023 is a VVol PE (ver:6)

 

I can create the VVOL-Datastore from vSphere Web Client, the appropriate Storage Containers (i.e. "Datastores" from UnityVSA) are presented. But as there are no PEs, the Datastores are unaccessible and show a size of 0 bytes (output from PowerCLI):

 

PowerCLI C:\> get-datastore vvol*

Name                               FreeSpaceGB      CapacityGB

----                               -----------      ----------

vvol-nfs-vsa-1                           0,000           0,000

vvol-iscsi-vsa-1                         0,000           0,000

PowerCLI C:\>

 

By the way, the vvold on the ESXi ist not running, it says, that there is no VVOL-configuration.

 

[/etc/init.d/vvold: /etc/init.d/vvold start, called by pid 43665]

[/etc/init.d/vvold: vvold max reserve memory set to 200]

2016-09-09T20:20:15.054Z Section for VMware ESX, pid=43696, version=6.0.0, build=4192238, option=Release

------ Early init logs start --------

2016-09-09T20:20:15.052Z info -[FFD82350] [Originator@6876 sub=Default] Successfully registered SIGHUP handler

2016-09-09T20:20:15.052Z info -[FFD82350] [Originator@6876 sub=Default] Successfully registered SIGPIPE handler

2016-09-09T20:20:15.052Z info -[FFD82350] [Originator@6876 sub=Default] Successfully registered SIGTERM handler

------ Early init logs end   --------

2016-09-09T20:20:15.054Z info vvold[FFD82350] [Originator@6876 sub=Default] Logging uses fast path: true

2016-09-09T20:20:15.054Z info vvold[FFD82350] [Originator@6876 sub=Default] The bora/lib logs WILL be handled by VmaCore

2016-09-09T20:20:15.054Z info vvold[FFD82350] [Originator@6876 sub=Default] Initialized channel manager

2016-09-09T20:20:15.055Z info vvold[FFD82350] [Originator@6876 sub=Default] Current working directory: /var/log/vmware

2016-09-09T20:20:15.055Z info vvold[FFDC3B70] [Originator@6876 sub=ThreadPool] Thread enlisted

2016-09-09T20:20:15.055Z info vvold[FFE04B70] [Originator@6876 sub=ThreadPool] Thread enlisted

2016-09-09T20:20:15.055Z info vvold[FFE45B70] [Originator@6876 sub=ThreadPool] Thread enlisted

2016-09-09T20:20:15.055Z info vvold[FFD82350] [Originator@6876 sub=ThreadPool] Thread pool on asio: Min Io, Max Io, Min Task,

Max Task, Max Concurency: 2, 22, 2, 52, 2147483647

2016-09-09T20:20:15.055Z info vvold[FFD82350] [Originator@6876 sub=ThreadPool] Thread enlisted

2016-09-09T20:20:15.055Z info vvold[FFE86B70] [Originator@6876 sub=ThreadPool] Thread enlisted

2016-09-09T20:20:15.055Z info vvold[FFD82350] [Originator@6876 sub=Default] Syscommand enabled: true

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default] ReaperManager Initialized

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default] Initalized App with config file:/etc/vmware/vvold/config.xml

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default] Listening on port 8090 (NOT using SSL) using version 'vvol.version.version1'.

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default] Initializing SOAP tcp adapter

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default.HTTPService] Using default for nonChunkingAgents: 'VMware VI Client|VMware-client|VMware-client/3.*'

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default.HTTPService] Using default for agentsNeedingContentLength: 'VMware-client'

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default.HTTPService] Max buffered response size is 104857600 bytes

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default] enableChunkedResponses: true

2016-09-09T20:20:15.057Z info vvold[FFD82350] [Originator@6876 sub=Libs] UUID: Running in UW, but cannot verify vmk syscall version, giving up.

2016-09-09T20:20:15.057Z info vvold[FFD82350] [Originator@6876 sub=Libs] UUID: Valid gethostid routine. Value = A8C01704.

2016-09-09T20:20:15.058Z info vvold[FFD82350] [Originator@6876 sub=Default] Creating SOAP body handler for version 'vvol.version.version1'

2016-09-09T20:20:15.058Z info vvold[FFD82350] [Originator@6876 sub=SOAP-1] Created SOAP body handler for vvol.version.version1 (vvol/1.0)

2016-09-09T20:20:15.058Z info vvold[FFD82350] [Originator@6876 sub=Default] Creating SOAP body handler for internal version 'vvol.version.version1'

2016-09-09T20:20:15.058Z info vvold[FFD82350] [Originator@6876 sub=SOAP-2] Created SOAP body handler for vvol.version.version1 (internalvvol/1.0)

2016-09-09T20:20:15.066Z error vvold[FFD82350] [Originator@6876 sub=Default] VVold SI:main, no VVol config available, exiting

[/etc/init.d/vvold: /etc/init.d/vvold stopnomemclear, called by pid 43701]

[/etc/init.d/vvold: vvold stopped.]

[/etc/init.d/vvold: WaitVvoldToComeUp /var/run/vmware/.vmware-vvol.started created]

[/etc/init.d/vvold: vvold stopped after start!]

[/etc/init.d/vvold: /var/run/vmware/.vmware-vvol.started is not created]

[/etc/init.d/vvold: Successfully cleared vvold memory reservation]

 

With "esxcli storage vvol vasaprovider list" I don't get a Storage Provider listed - although it's registered in vCenter (and listed as online vie the Web Client).

 

Anything I should be missing, but at the moment, I don't have any idea to go further. Any help very appreciated.

 

Best regards,

Christian


Viewing all articles
Browse latest Browse all 5826

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>