Unsolved
This post is more than 5 years old
11 Posts
0
3821
Registering ScaleIO to ESRS gateway
--register_esrs_gateway --scaleio_gateway_ip --scaleio_gateway_user --scaleio_gateway_password --esrs_gateway_ip --esrs_gateway_user --esrs_gateway_password --
connect_in_ip
I am trying to register the ScaleIO to ESRS GW. I could not find what IP address to the replaced for connect_in_ip. I don’t find any information in the documents. Any help would be greatly appreciated.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
December 5th, 2016 03:00
Hi allunr,
Could you please confirm that the username/password to setup ScaleIO with ESRS are NOT the username/password which you use to login to the ESRS admin panel
Actually to register to SIO with ESRS, you need to use the credentials that received from EMC Secure Remote Support (ESRS) to register. The username is usually an email address (not admin).
Thanks,
Alaa H.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
December 9th, 2016 03:00
We're trying to integrate ScaleIO with ESRS too and I must admit, there is very little documentation apart from the deployment guide. The connect in address is, from what I understand, the management IP the customer uses to manage the ScaleIO: the primary MDM address.
Also, don't forget this tiny detail:
allunr
11 Posts
0
December 9th, 2016 04:00
If I register with Primary MDM and due to some network issue If the slave become Primary, Will ESRS lose access to ScaleIO?
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
December 9th, 2016 06:00
That's not entirely clear and definitely something that requires testing. With the release of 2.0.1.0 we have a virtual IP that is always mapped to the primary MDM, which eliminates the above situation.
MaximKh
5 Posts
0
December 14th, 2016 03:00
is anybody finished ESRS and SIO configuration?
i faced with problem at step set the connect-in IP address,
--set_connectin_ip --scaleio_gateway_ip xxxxx --scaleio_gateway_user admin --scaleio_gateway_password xxxxxx --connect_in_ip xxxxxxx
Exception in thread "main" org.springframework.web.client.HttpClientErrorException: 401 Unauthorized
at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:88)
at org.springframework.web.client.RestTemplate.handleResponseError(RestTemplate.java:557)
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:515)
at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:473)
at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:421)
at com.emc.s3g.scaleio.installation.cli.SioGWTool.loginToRestGateway(SioGWTool.java:1373)
at com.emc.s3g.scaleio.installation.cli.SioGWTool.main(SioGWTool.java:1055)
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
December 18th, 2016 06:00
Hi Maxim,
Before configuring ESRS, ensure that your system meets the following requirements,
and that you have the following information:
Requirements:
- ESRS Gateway v3 version 3.08 or higher must be installed and configured.
- ESRS Gateway must be reachable from ScaleIO on port 9443.
- The ScaleIO license must be installed.
- The ScaleIO Management IP address to be used as the Connect-In IP address must be an IP address that is accessible from the ESRS Gateway.
- On the ScaleIO Gateway, in the gatewayUser.properties file, set the property features.enable_esrs=true
Information:
- One or more IP addresses of the ESRS servers.
- ESRS user and password credentials.
- MDM user name and password.
- The ScaleIO Management IP address to be used as the Connect-In IP address.
Please note that the Username/Password to setup ScaleIO with ESRS are NOT the username/password which you use to login to the ESRS admin panel.
To register to SIO with ESRS, you need to use the credentials that received from EMC Secure Remote Support (ESRS) to register. The username is usually an email address (not admin).
> SioGWTool.bat --register_esrs_gateway --scaleio_gateway_ip x.x.x.x:443 --scaleio_gateway_user --scaleio_gateway_password --esrs_gateway_ip x.x.x.x --esrs_gateway_user --esrs_gateway_password PASSWORD> --connect_in_ip x.x.x.x
Hope it works with you this time.
Keep me updated!.
Thanks,
Alaa
MaximKh
5 Posts
0
December 18th, 2016 23:00
Hi Alaa,
Thanks for your reply.
Yes, it is helped) main problem was, i used wrong username for ESRS.
One more question. After this command on SIO Gateway i received
ESRS gateway has been registered successfully
Now it is enough? System configuration done? or i should also run this command?
SioGWTool --set_connectin_ip --scaleio_gateway_ip
--scaleio_gateway_user
--scaleio_gateway_password
--connect_in_ip
Then i run it, received error.
Exception in thread "main" org.springframework.web.client.HttpClientErrorException: 401 Unauthorized
at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:88)
at org.springframework.web.client.RestTemplate.handleResponseError(RestTemplate.java:557)
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:515)
at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:473)
at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:421)
at com.emc.s3g.scaleio.installation.cli.SioGWTool.loginToRestGateway(SioGWTool.java:1373)
at com.emc.s3g.scaleio.installation.cli.SioGWTool.main(SioGWTool.java:1055)
Thanks!
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
December 19th, 2016 04:00
Can you run this one: SioGWTool.bat --check_esrs_connectivity and tell us the output?
The --register_esrs_gateway cmd should be enough judging from the deployment guide. You may need to enable the esrs alerting with SioGWTool.bat --start_esrs, it's not clear in the guide whether registering with ESRS also enables it.
MaximKh
5 Posts
0
December 19th, 2016 04:00
Now ESRS successfully configured.
/opt/emc/scaleio/gateway/bin/SioGWTool.sh --check_esrs_connectivity --scaleio_gateway_ip xxxxxx --scaleio_gateway_password xxxxxx --scaleio_gateway_user admin
Esrs connected
/opt/emc/scaleio/gateway/bin/SioGWTool.sh --start_esrs --scaleio_gateway_ip xxxxxx --scaleio_gateway_password xxxxxx --scaleio_gateway_user admin
ESRS started successfully
But now, appear new problem.
ESRS send emails, but this emails don't contain information about SIO alerts.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
December 20th, 2016 02:00
Can you look at the content of the XML file? I noticed that there is a config file in SYR from yesterday so it seems to be working on the config send side.
Can anyone give a pointer on what username you exactly need to register with the ESRS gw? Did the customer receive it from EMC?
MaximKh
5 Posts
0
December 20th, 2016 02:00
Hi,
XML file located on ESRS server and include:
xsi:schemaLocation="/opt/connectemc/schema/ema_ConnectHome108.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
10
EventXML
0
2
1
XXXXXXXXX
EMC
ScaleIO
XXXXXXXXX
None available
Unknown
Unknown
Unknown
R2_0.7536.0
2
51200
Unknown
Symmremote
Unknown
Unknown
SIO03.01.1000014
Status
ALERT_LOW
Unknown
No
1
Affected Object TypeSdsAffected Object IDe0d6325500000006]]>
From SIO User guide, i found what SIO 03.01.1000014 mean SDS is in Maintenance Mode.
It is not very easy way to know, what happens))
About account for registration on ESRS, i used my EMS account for web portal.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
December 21st, 2016 01:00
Hi Maxim,
All ESRS messages are not detailed messages , the message is started with SIO and some numbers like the one you have received SIO 03.01.1000014 and by checking what this numbers mean you can get some details on the alert received , Actually this are configured for ESRS team to get the alerts and act accordingly.
So for meaningful messages on errors reported on the system , you can configure the SNMP , it's not related to ESRS however it will notify you with errors received on the system.
Hope this could help answer your question!
Thanks,
Alaa
MaximKh
5 Posts
0
December 21st, 2016 03:00
how it was easy and simply when was callhome))
harria5
12 Posts
0
August 17th, 2017 09:00
How do you test callhome on scaleio when connecting to esrs? I'm a technical PM on the esrs team.
asinghami
2 Posts
0
October 23rd, 2017 17:00
Hello Guys,
had the similar issues and didn't find a complete set of instructions to add the ScaleIO to ESRS after working with people in EMC got some details and had to add some more stuff to make it work. here is the complete step for adding scaleIO to ESRS:
1-
Make sure the ESRS feature is enabled in the ScaleIO user property file :
ScaleIO-10-200-201-120-GW:/opt/emc/scaleio/gateway # grep esrs webapps/ROOT/WEB-INF/classes/gatewayUser.properties
features.enable_esrs=true
2- update the cipher in server.xml file :
Open the file "/opt/emc/scaleio/gateway/conf/server.xml" and add the follwoing line after 'server=ScaleIO Gateway" :
ciphers="TLS_DHE_DSS_WITH_AES_128_CBC_SHA256,TLS_DHE_DSS_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_A"
file before adding the ciphers ::
.....
port="${http.port}"
protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="${ssl.port}"
compression="force"
compressableMimeType="application/json,application/octet-stream"
server="ScaleIO Gateway"
/>
The file will look like this after adding the cipher::
......
port="${http.port}"
protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="${ssl.port}"
compression="force"
compressableMimeType="application/json,application/octet-stream"
server="ScaleIO Gateway"
ciphers="TLS_DHE_DSS_WITH_AES_128_CBC_SHA256,TLS_DHE_DSS_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_A"
/>
ScaleIO-10-200-201-120 GW:~ # service scaleio-gateway restart
The EMC ScaleIO Gateway is not running.
The EMC ScaleIO Gateway is running. PID=13547.
# ./SioGWTool.sh --change_lb_passphrase --new_passphrase
Creating new lockbox
ScaleIO-10-200-201-120 GW:/opt/emc/scaleio/gateway/bin#
Add the MDM Credentials ::
ScaleIO-10-200-201-120 GW:/opt/emc/scaleio/gateway/bin # ./SioGWTool.sh --set_mdm_credentials --mdm_user admin --mdm_password
MDM user credentials successfully saved
ScaleIO-10-200-201-120 GW:/opt/emc/scaleio/gateway/bin # cat /root/root.crt
-----BEGIN CERTIFICATE-----
MIIEADCCAuigAwIBAgIJAPcU7MfTTlh5MA0GCSqGSIb3DQEBCwUAMF0xCzAJBgNV
BAYTAlVTMQswCQYDVQQIEwJNQTELMAkGA1UEBxMCU08xDDAKBgNVBAoTA0VNQzEN
MAsGA1UECxMERVNSUzEXMBUGA1UEAxMObnJ1c2NhLXNscDAzODEwHhcNMTcwNzEw
MDk1MTQ4WhcNMTgwNzEwMDk1MTQ4WjBdMQswCQYDVQQGEwJVUzELMAkGA1UECBMC
TUExCzAJBgNVBAcTAlNPMQwwCgYDVQQKEwNFTUMxDTALBgNVBAsTBEVTUlMxFzAV
MIIEADCCAuigAwIBAgIJAPcU7MfTTlh5MA0GCSqGSIb3DQEBCwUAMF0xCzAJBgNV
BAYTAlVTMQswCQYDVQQIEwJNQTELMAkGA1UEBxMCU08xDDAKBgNVBAoTA0VNQzEN
MAsGA1UECxMERVNSUzEXMBUGA1UEAxMObnJ1c2NhLXNscDAzODEwHhcNMTcwNzEw
MDk1MTQ4WhcNMTgwNzEwMDk1MTQ4WjBdMQswCQYDVQQGEwJVUzELMAkGA1UECBMC
TUExCzAJBgNVBAcTAlNPMQwwCgYDVQQKEwNFTUMxDTALBgNVBAsTBEVTUlMxFzAV
-----END CERTIFICATE-----
6 - create authentication token to add the certificate
ScaleIO-10-200-201-120 GW:~ # curl -k -v --basic --user admin: https://10.200.201.120/api/login
Copy the last line of the command output and save it as we will need that token to add the certificates.
ScaleIO-10-200-201-120 GW:~ # curl -k -v --basic -uadmin:YWRtaW46MTUwODgwNTk3NTM3OTo3M2YyYzU4NjA3ZmEyNzcxNmZjYzkxNmJkZjU3ZTY2Mg --form "file=@/root/root.crt"
Restart the ScaleIO gateway servics :
ScaleIO-10-200-201-120 GW:~ # service scaleio-gateway restart
The EMC ScaleIO Gateway is not running.
The EMC ScaleIO Gateway is running. PID=13547.
ScaleIO-10-210-21-150-GW:/opt/emc/scaleio/gateway/bin # ./SioGWTool.sh --register_esrs_gateway --scaleio_gateway_ip 10.200.201.120 --scaleio_gateway_user admin --scaleio_gateway_password --esrs_gateway_ip 10.155.162.200 --esrs_gateway_user --esrs_gateway_password --connect_in_ip 10.200.201.121
ESRS gateway has been registered successfully
Note ::
connect_in_ip 10.200.201.121 === > MDM server
esrs_gateway_user === > NT login of EMC support employee (work with support to get one)
esrs_gateway_password === > password from RSA key of the employee
Login credentials of ESRS we use to login to vApp will not work and we have to work with EMC support or Resident to get this.
after this login to ESRS and you will see the scaleIO .. you might need to work with support to accept the device from their end to complete the registration.