Correct ! I am monitoring the server itself and I do not have the later one activated.
Reba R Gaines, MBA/TM Unicenter/Solarwinds Systems Manager Ciber Defense Technology Systems 200 Westpark Drive, Suite 330 Peachtree City, GA 30269 (770) 268-7448 Direct Dial (678) 449-9080 Mobile From: Alejandro Jimenez [mailto:[email protected]] Sent: Tuesday, October 19, 2010 11:13 AM To: spectrum Subject: RE:[spectrum] SNMP GRABS SPECTRUM PORTS DURING REBOOT AFTER MICROSOFT UPDATES I do absolutely agree with Michael, He explained perfectly; just want to clarify services names on a Windows box: SNMP Service: this the snmp agent to answer UDP 161 request from a NMS. This will not interfere with spectrum at all and you can use it to monitor Server itself. SNNP Trap Service: you should not activate this service as far as will listen on UDP 162 by default (same port used on spectrum), unless you made previous mentioned changes. Regards, Alejandro Jiménez Pérez Técnico de Ingeniería. Área de Soporte. Telindus S.A.U. Plaza Ciudad de Viena, 6 - 2ª 28040 Madrid Spain [email protected]<mailto:[email protected]> T +34 91 456 00 08 T +34 91 203 28 29 F +34 91 536 10 74 Telindus. Change things your way. http://www.telindus.es/ ________________________________ De: Michael Votaw - VTI [mailto:[email protected]] Enviado el: martes, 19 de octubre de 2010 16:55 Para: spectrum Asunto: RE:[spectrum] SNMP GRABS SPECTRUM PORTS DURING REBOOT AFTER MICROSOFT UPDATES I would like to put my $.02 in. Unless things have changed drastically, Spectrum never needs to hold UDP/161 open on the SpectroServer, only UDP/162. Spectrum will indeed send requests out to the destination port UDP/161 to poll devices. Spectrum must be able to receive SNMP traps on port UDP/162 and will try to open this port, but should never open UDP/161. Spectrum doesn't include its own SNMP agent on the server unless you put it there. There should be no issue at all with running the Microsoft snmp agent on the same machine as the spectrum server, as long as you don't enable the snmp trap port on the same server (UDP/162). Try running an application like TCPView (http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx ) to know for sure what application is holding these ports open. From: Gaines, Reba R [mailto:[email protected]] Sent: Tuesday, October 19, 2010 6:48 AM To: spectrum Subject: [spectrum] SNMP GRABS SPECTRUM PORTS DURING REBOOT AFTER MICROSOFT UPDATES Importance: High Hello Spectrum Users: Has anyone conquered this issue. We deploy Microsoft updates routinely and like clockwork, SNMP service grabs either UDP port 161 or 162 (sometimes both) before Spectrum can. I've tried telling SNMP to wait for Spectrum services to load first. That work for a while but then SNMP services would start anymore. I had to uninstall it and then reinstall SNMP to get it to work again. Any suggestions? Reba R Gaines, MBA/TM Unicenter/Solarwinds Systems Manager Ciber Defense Technology Systems 200 Westpark Drive, Suite 330 Peachtree City, GA 30269 (770) 268-7448 Direct Dial (678) 449-9080 Mobile * --To unsubscribe from spectrum, send email to [email protected]<mailto:[email protected]> with the body: unsubscribe spectrum [email protected] * --To unsubscribe from spectrum, send email to [email protected]<mailto:[email protected]> with the body: unsubscribe spectrum [email protected] * --To unsubscribe from spectrum, send email to [email protected]<mailto:[email protected]> with the body: unsubscribe spectrum [email protected] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
