VMware Cloud Community
ccie8122
Contributor
Contributor
Jump to solution

"501 Not Implemented" error on vCenter plugin

Background:

So i am running vCenter 4.1.0.345043, with a pair of ESXi 4.1.0.348481 hosts.  the storage is a Dell MD3000i iSCSI storage array.  i have thus far used the Dell MD Storage Manager to set up Hosts, Host Groups, Host-to-VD-mappings, etc.

Then I go into vCenter and enable the iSCSI SW initiator, rescan the HBAs and voila, the targets show up, and i am able to share the storage across the hosts just fine.

I noticed that Dell has an MD Storage Array vCenter Plugin Dell MD  Storage Array vCenter Plug-In.  So download the installer for this  (v01.00.3650.0007) and install the plugin on the vCenter server.

(ESXi is installed on a pair of Dell 2950 dual-Xeon; vCenter is installed on a Dell R410 on Windows Server 2008 R2 x64.)

Problem:

After install, i go into client and select Manage Plugins, and I see the Dell MD plugin is DISABLED (will not enable) with the following error:

The following error occured while downloading the script plugin from https://<vcenter_IP>:8084/vcenterconfig/configuration.xml:
The remote server returned an error: (501) Not Implemented.

I turn off WIndows Firewall in case that was the problem, and no dice.

Any ideas?

kr

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
paxri01
Enthusiast
Enthusiast
Jump to solution

Most likely this is due to a conflict in the port assignments with the VMware Update Manager service, if the vCenter Plug-In application server is installed on the same system as the vCenter Server.

To resolve the issue, reinstall the vCenter Plug-In and choose an unused port number instead of the default 8084.

User Guide Excerpt:

      5.  Either change the port number of the Jetty server, or accept the default of 8084 and 8081, and click Next

Please update this post with your results.

Thanks!

View solution in original post

0 Kudos
13 Replies
DSTAVERT
Immortal
Immortal
Jump to solution

I don't know whether you might want to try a newer version assumning the a version 2.1 is newer. http://goo.gl/SUvPC

-- David -- VMware Communities Moderator
0 Kudos
ccie8122
Contributor
Contributor
Jump to solution

Yeah, that is actually the file i downloaded/installed: SMIA_vCenter_WSX64_2.1_R299488.zip

Dont know why it lists the version as v01.00.3650.0007 in vCenter.

0 Kudos
GeLLow
Contributor
Contributor
Jump to solution

Hello,

I got exactly the same error !

vCenter (v. 4.1.0 build 258902) on R310 and 3 ESXi hosts on R710 ( v. 4.1.0 build 348481) connected to a SAS MD3200...

Have you found anything yet ? I can't try to install v 2.0 because MD3200 is not supported...

Regards

Gilles

0 Kudos
ccie8122
Contributor
Contributor
Jump to solution

nope

0 Kudos
DSTAVERT
Immortal
Immortal
Jump to solution

I would check with Dell support. Is there anything about the plugin that requires an updated licence? New or different features that are seperately licensed?

-- David -- VMware Communities Moderator
0 Kudos
ccie8122
Contributor
Contributor
Jump to solution

tried that. they were not very helpful - said they "can only provide best effort on setup issues/questions" and sent me the UG for the plugin, which was of no help.

0 Kudos
ccie8122
Contributor
Contributor
Jump to solution

and no new features that require any licensing that i am aware of.  the UG just says to install the plug and rock n roll.

0 Kudos
paxri01
Enthusiast
Enthusiast
Jump to solution

Most likely this is due to a conflict in the port assignments with the VMware Update Manager service, if the vCenter Plug-In application server is installed on the same system as the vCenter Server.

To resolve the issue, reinstall the vCenter Plug-In and choose an unused port number instead of the default 8084.

User Guide Excerpt:

      5.  Either change the port number of the Jetty server, or accept the default of 8084 and 8081, and click Next

Please update this post with your results.

Thanks!

0 Kudos
GeLLow
Contributor
Contributor
Jump to solution

Many thx paxri01 !

That was it !

Cheers

Gilles

ccie8122
Contributor
Contributor
Jump to solution

that was it for me as well.  thanks

0 Kudos
SICN
Contributor
Contributor
Jump to solution

i have the same issue. how can you reinstall vcenter plug-in? do you mean reinstall vCenter Server?

0 Kudos
ccie8122
Contributor
Contributor
Jump to solution

no, do NOT reinstall vCenter server.  just uninstall the Dell MD plugin from the vCenter server (via Control Panel | Add/Remove programs in W2k3 or Progs & Features in W2k8).  Then reinstall the MD plugin from the executable and during install, when prompted for port to use, change the default port from 8084 to remove the conflict.  I used 8082 and that fixed the issue.

kr

0 Kudos
SICN
Contributor
Contributor
Jump to solution

thanx for the fast reply. your advise solved my problem. is the SMI-S provider upgrade procedure required  for the plugin.

0 Kudos