Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
wiki:infrastructure_tools:snmp:snmp-ms_windows [2014/07/03 15:59]
iggy.ttt@gmail.com [GUI SNMP Trap Configuration ( evntwin )]
wiki:infrastructure_tools:snmp:snmp-ms_windows [2014/07/03 16:16] (current)
iggy.ttt@gmail.com [CLI SNMP Trap Configuration ( envtcmd )]
Line 240: Line 240:
 ==== CLI SNMP Trap Configuration (" envtcmd ") ==== ==== CLI SNMP Trap Configuration (" envtcmd ") ====
  
-In the case that you are maintaining more as one MS Windows server it is handy to use some kind of automaton to safe your time. It’s nice from M$ that they are providing ​as well CLI tool to maintain SNMP Trap configuration. \\+In the case that you are maintaining more as one MS Windows server it is better ​to use some kind of automaton to safe your time. At MS Windows is possible to use as well CLI tool to maintain SNMP Trap configuration. \\
 \\ \\
 According to this it is possible to (standardize your configuration across all MS Windows servers):\\ According to this it is possible to (standardize your configuration across all MS Windows servers):\\
Line 248: Line 248:
 - Upload actual config file to share drive (for example on SAMBA server)\\ - Upload actual config file to share drive (for example on SAMBA server)\\
 - Write script: \\ - Write script: \\
-- - to login to all of your MS Windows serves from central server (with help of winexe” it is possible to do it as well from Linux)\\+- - to login to all of your MS Windows serves from central server (with help of "winexe" ​it is possible to do it as well from Linux)\\
 - - to update local MS Windows server configuration based on config file from share drive. \\ - - to update local MS Windows server configuration based on config file from share drive. \\
 \\ \\
-It is nice scenario for integration,​ just our topic is limited to SNMP Trap configuration ​according ​to this I will focus on configuration of SNMP Traps on MS Windows server. As I have mentioned the integration is pretty easy and I will describe it later in another document (any way I have mentioned all important tools that will be used).+It is nice scenario for integration,​ just our topic is limited to SNMP Trap configuration. According ​to this I will focus on configuration of SNMP Traps on MS Windows server. As I have mentioned the integration is pretty easy and I will describe it later in another document (any way I have mentioned all important tools that will be used).
  
 ===   === ===   ===
Line 257: Line 257:
 === Export existing config: === === Export existing config: ===
  
-In the case that you are using one MS Windows Server for testing ​of developing your SNMP Trap configuration it is possible to export this configuration in to config file that you can modify ​or deploy on another MS Windows Server.+In the case that you are using one MS Windows Server for testing ​and developing ​of your SNMP Trap configuration it is possible to export this configuration in to config file that can be modified ​or deploy on another MS Windows Server.
  
 <​code>​ <​code>​
Line 268: Line 268:
 {{  :​wiki:​infrastructure_tools:​snmp:​win2008-snmp-evntwin-export-config.jpg?​721x494 ​ }} {{  :​wiki:​infrastructure_tools:​snmp:​win2008-snmp-evntwin-export-config.jpg?​721x494 ​ }}
  
-In the case that you would like to modify exported " events.cnf " file it is possible to use standard editor vi/​vim/​notepad/​… to edit and modify this config:+In the case that you would like to modify exported " events.cnf " fileit is possible to use standard editor vi/​vim/​notepad/​… to edit and modify this config:
  
 <​code>​ <​code>​
Line 315: Line 315:
 #pragma add_trap_dest private 10.0.0.2 ​               # This will configure new SNMP Trap destination #pragma add_trap_dest private 10.0.0.2 ​               # This will configure new SNMP Trap destination
 #pragma delete "​System"​ "​SNMP"​ 1090454505 1 0         # This will remove configuration for already configured Interesting event #pragma delete "​System"​ "​SNMP"​ 1090454505 1 0         # This will remove configuration for already configured Interesting event
-#pragma add "​System"​ "​SNMP"​ 1090454505 1 0            # This will add new Interesting event to our list events that will be forwarded to SNMP trap detination+#pragma add "​System"​ "​SNMP"​ 1090454505 1 0            # This will add new Interesting event to our list events that will be forwarded to SNMP trap destination
 </​code>​ </​code>​
  
Line 324: Line 324:
 </​code>​ </​code>​
  
-<note tip>To in some cases you would like to run “ evntcmd “ with parameter “ –n “ as this will prevent restart of SNMP service on your MS Windows server. In general the restart of mentioned SNMP service is root cause for triggering “ coldStart “ SNMP Trap.</​note>​+<note tip>In some cases you would like to run “ evntcmd “ with parameter “ –n “ as this will prevent restart of SNMP service on your MS Windows server. In general the restart of mentioned SNMP service is root cause for triggering “ coldStart “ SNMP Trap.</​note>​ 
 ===== Test ===== ===== Test =====
  
Navigation
Print/export
QR Code
QR Code wiki:infrastructure_tools:snmp:snmp-ms_windows (generated for current page)