SNMP issue caused total system shutdown

[EricPatterson]

We are in the process of implementing SNMP on our all servers for monitoring them in a 3rd party software, so all servers can be monitored from a single location by any of us in the department.

When I installed it onto my JDE servers, the system shutdown. We found several entries in the logs similar to this:

2632/2636 MAIN_THREAD Fri Aug 14 09:53:08.546000 Jdbodbc.c1340
ODB0000164 - DBC:00 [08001][53] [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [53].

2632/2636 MAIN_THREAD Fri Aug 14 09:53:08.546001 Jdbodbc.c1340
ODB0000164 - DBC:01 [HYT00][0] [Microsoft][SQL Native Client]Login timeout expired

2632/2636 MAIN_THREAD Fri Aug 14 09:53:08.546002 Jdbodbc.c1340
ODB0000164 - DBC:02 [08001][53] [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

Has anyone else experienced a similar situation? Or. is there a best practice for implementing SNMP on our JDE servers.

We run e8.10, Tools Release 8.97 on Windows 2003 server and SQL Server 2005 for a database.

 

[altquark]

What port are you using for SNMP ?

 

[EricPatterson]

Jon,

I had not even begun to configure SNMP when the system went down. I disabled, then un-installed it as quickly as possible to get the system running quickly. I did not have a chance to check the port. I can look at one of our other servers to check the port it is running on there.

 

[altquark]

SNMP should not interfere with SQL - but if you're installing it on a port that SQL Server is trying to communicate with, then you're going to get communication errors. Before you do this again, make sure that all the ports are completely unused, otherwise change SNMP to a different port.

 

[EricPatterson]

Thanks Jon...

I am looking into this further and checking ports.