Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

2252

November 11th, 2015 00:00

snmp trap error

Hello experts

After enable snmp trap in scaleio gateway ,there are the following errors,could you help explain?

2015-11-11 16:55:29,674 [threadPoolTaskScheduler-1] INFO  c.e.s3g.scaleio.web.SNMP.TrapManager - New alerts: [Alert{affectedObject=System:4d2, severity=ALERT_MEDIUM, type=FAILED_CONNECT}]

2015-11-11 16:55:29,676 [threadPoolTaskScheduler-1] INFO  c.e.s3g.scaleio.web.SNMP.TrapSender - Sending V2 Trap: TRAP[requestID=0, errorStatus=Success(0), errorIndex=0, VBS[1.3.6.1.2.1.1.3.0 = Wed Nov 11 16:55:29 CST 2015; 1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.4.1.1139.101.1; 1.3.6.1.4.1.1139.101.1.1 = 5; 1.3.6.1.4.1.1139.101.1.2 = MDM.MDM_Cluster.SNMP_Server_Cannot_Connect_To_MDM; 1.3.6.1.4.1.1139.101.1.3 = NA; 1.3.6.1.4.1.1139.101.1.4 = 2.1.3]]

2015-11-11 16:55:59,672 [threadPoolTaskScheduler-1] ERROR c.e.s.s.s.ConnectionServiceImpl - Failed connecting to cluster

2015-11-11 16:55:59,672 [threadPoolTaskScheduler-1] ERROR c.e.s3g.scaleio.web.SNMP.TrapManager - Failed connecting to mdm cluster: com.emc.s3g.scaleio.services.ScaleIORemoteRuntimeException: Failed connecting to cluster

2015-11-11 16:55:59,672 [threadPoolTaskScheduler-1] ERROR c.e.s.s.s.ConnectionServiceImpl - Failed connecting to cluster

2015-11-11 16:55:59,673 [threadPoolTaskScheduler-1] ERROR c.e.s3g.scaleio.web.SNMP.TrapManager - Could not retrieve failed devices: com.emc.s3g.scaleio.services.ScaleIORemoteRuntimeException: Failed connecting to cluster

2015-11-11 16:55:59,673 [threadPoolTaskScheduler-1] ERROR c.e.s.s.s.ConnectionServiceImpl - Failed connecting to cluster

2015-11-11 16:55:59,673 [threadPoolTaskScheduler-1] ERROR c.e.s3g.scaleio.web.SNMP.TrapManager - Could not retrieve disconnected sdss: com.emc.s3g.scaleio.services.ScaleIORemoteRuntimeException: Failed connecting to cluster

November 12th, 2015 02:00

Make sure the MDM IP address appears in the gatwayUser.properties file, it not please the Mgmt IP of the Primary+Secondary (P.MDM_IP,S.MDM_IP) and restart the gateway service.

3 Posts

April 25th, 2016 02:00

curl --insecure --user admin:password https://gatewayip:443/api/login

{"message":"Failed connecting to cluster: mdm_ip","httpStatusCode":428,"errorCode":0}

2016-04-25 17:38:27,493 [http-nio-443-exec-4] ERROR c.e.s.s.s.ConnectionServiceImpl - Failed connecting to cluster

2016-04-25 17:38:27,497 [http-nio-443-exec-4] ERROR c.e.s.s.w.c.SpecialImplController - Got an exception in handleException

com.emc.s3g.scaleio.common.gateway.ScaleIORemoteRuntimeException: Failed connecting to cluster: 88.88.88.88

  at com.emc.s3g.scaleio.services.ConnectionServiceImpl.openConnection(ConnectionServiceImpl.java:337) ~[ams-1.0-SNAPSHOT.jar:na]

  at com.emc.s3g.scaleio.services.ConnectionServiceImpl.openConnection(ConnectionServiceImpl.java:347) ~[ams-1.0-SNAPSHOT.jar:na]

  at com.emc.s3g.scaleio.services.ConnectionServiceImpl.openConnection(ConnectionServiceImpl.java:347) ~[ams-1.0-SNAPSHOT.jar:na]

  at com.emc.s3g.scaleio.services.ConnectionServiceImpl.refreshConnection(ConnectionServiceImpl.java:323) ~[ams-1.0-SNAPSHOT.jar:na]

  at com.emc.s3g.scaleio.services.ConnectionServiceImpl.invokeRequest(ConnectionServiceImpl.java:251) ~[ams-1.0-SNAPSHOT.jar:na]

  at com.emc.s3g.scaleio.services.ConnectionServiceImpl.invokeMethod(ConnectionServiceImpl.java:225) ~[ams-1.0-SNAPSHOT.jar:na]

  at com.emc.s3g.scaleio.services.RestServiceImpl.sendRequest(RestServiceImpl.java:589) ~[ams-1.0-SNAPSHOT.jar:na]

  at com.emc.s3g.scaleio.services.RestServiceImpl.mdmLogin(RestServiceImpl.java:1059) ~[ams-1.0-SNAPSHOT.jar:na]

mdm.ip.addresses was configured in gatewayUser.properties in server A with gateway installed

mdm master is on server B.

mdm slave is on server C.

after login, adding-volume cmd works in Server B only.

  scli --add_volume --protection_domain_name default  --storage_pool_name defaultSP --use_nonsecure_communication --size_gb 8 --volume_name test1212

I am using scale IO 2.0. Error: security disabled on the MDM. So I use --use_nonsecure_communication to connect without security

Thanks

April 25th, 2016 05:00

I'm sorry but I fail to understand the correlation between the CURL and what you describe afterwards.

R U sure your syntax is correct? Please refer to the User Guide pages 554 onwards for CURL examples.

GW needs to have ALL Mgmt MDM IPs in its gatewayUser.properties file (comma separated)

GW is not used to add volumes -> this can be done only via SCLI / GUI / REST-API / vSphere plugin

If you want to add volume via SCLI you run the SCLI command on the current Master MDM (after SCLI --login).

If you with to have secure connection between Mgmt clients and MDM that can be set via  SCLI / REST-API) and then each Mgmt interface (GUI / GW / SCLI / Plugin) needs to accept the MDM certificate (using SCLI / REST-API).

Please refer to the Deployment guide + User guide, on how to switch from non-secured to secure communication.

3 Posts

April 26th, 2016 03:00

CURL is just to verify the GW/api/login.

The syntax is correct and it works now after I enable the secure setting.

mdm ips are added to the properties file.

I use scli command on the mdm server to create a volume successfully.

Can not find the document to switch from non-secured to secure commincation from the installation guide and user guide.

I uninstalled all components and reinstalled them with secure setting.

Now it works well.

Thanks anyway.

26 Posts

January 25th, 2017 00:00

Thanks for the insights Tomer.

After configuring

snmp.traps_receiver_ip=ip1,ip2

mdm.ip.addresses=ip1,ip2

Still Traps are not going to SMARTS server and not able to get generated with incident tickets.

This become great bottleneck on the Operations side for Scaleio systems.

Need your insights,  Thanks

No Events found!

Top