NVP vProxy: Registration fails with "vProxy in unstable state, method not allowed. Received an HTTP code: 405"
Resumen: Unable to register NSR VMware proxy 'vproxyname.local': vProxy in unstable state, method not allowed
Este artículo se aplica a
Este artículo no se aplica a
Este artículo no está vinculado a ningún producto específico.
No se identifican todas las versiones del producto en este artículo.
Síntomas
The NetWorker VMware Protection integration is configured with the vProxy Appliance. The vProxy is being registered, and the NetWorker Management Console shows an HTTP warning code 405.
Warning HH:MM:SS event vm proxy Unable to register NSR VMware proxy '[VPROXY_NAME]': vProxy in unstable state, method not allowed. Received an HTTP code: 405, libCURL message: "", url: "https://[NETWORKER_SERVER_NAME]:9090/api/v1/VproxyEngines/RestEngine/Registration"
The vProxy /opt/emc/vproxy/runtime/logs/vrapid/vrapid-engine.log shows:
YYYY/MM/DD HH:MM:SS TRACE: rejecting unauthorized request "/api/v1/VproxyEngines/RestEngine/process":
YYYY/MM/DD HH:MM:SS TRACE: {"Config": {"LogTag": "28", "Username": "admin", "SessionId": "", "IdleTimeout": 300, "LogLevel": "INFO", "Password": "*****", "NWS": "[NETWORKER_SERVER_NAME]", "Cp": "-----BEGIN CERTIFICATE-----\nMIICwD....\n-----END CERTIFICATE-----\n-----BEGIN RSA PRIVATE KEY-----\n.....==\n-----END RSA PRIVATE KEY-----\n", "MobServer": {"HostName": "[VCENTER_SERVER_NAME]", "UserName": "[VCENTER_USER]", "UserPassword": "*****", "TcpPort": 0}}}
YYYY/MM/DD HH:MM:SS ERROR: AdminEngine: sending response error: code=401, errText=only requests from [NETWORKER_SERVER_NAME] are allowed
YYYY/MM/DD HH:MM:SS TRACE: rejecting unauthorized request "/api/v1/VproxyEngines":
YYYY/MM/DD HH:MM:SS ERROR: AdminEngine: sending response error: code=401, errText=only requests from [NETWORKER_SERVER_NAME] are allowed
Causa
If the NetWorker server has multiple network interfaces, the vProxy may see another interface and deny the registration.
Resolución
Use one of the following workaround options:
Workaround 1:
2. Switch to root: sudo su - root
3. Edit the systemd unit config file: vi /usr/lib/systemd/system/vrapid.service
4. Find the line starting with "ExecStart=/opt/emc/vproxy/bin/vrapid"
5. Append/edit command-line arg to disable access control.
Example: ExecStart=/opt/emc/vproxy/bin/vrapid --disable-access-control
6. Reload the unit config file into systemd: systemctl daemon-reload
7. Restart the vrapid engine: systemctl restart vrapid.service
8. Register the vProxy with the NetWorker server.
Workaround 2:
Configure DNS entries for all the NetWorker Server interface IP addresses to resolve to the NetWorker Server hostname. The vProxy registration resolves all the IP addresses for the NetWorker Server and add them to the access control list.
Workaround 3:
Edit the vProxy /etc/hosts file prior to registration and add all the NetWorker Server interface IP addresses to resolve to the NetWorker Server hostname.
NOTE: Using this method will cause the nsrvproxy_mgmnt redeploy option to fail when upgrading the vProxy appliance in the future as the /etc/hosts settings are not redeployed.
Información adicional
Productos afectados
NetWorker SeriesProductos
NetWorker, NetWorker SeriesPropiedades del artículo
Número del artículo: 000050318
Tipo de artículo: Solution
Última modificación: 28 sept 2023
Versión: 4
Encuentre respuestas a sus preguntas de otros usuarios de Dell
Servicios de soporte
Compruebe si el dispositivo está cubierto por los servicios de soporte.