17.1 Setting Up SNMP Notifications on Windows

  1. Install and enable the SNMP service on your Windows system. Define the SNMP community to which to send trap messages ("public", for instance). Then designate that name as an Accepted Community in the SNMP Service Properties.
    For details on installing and configuring SNMP on Windows, refer to your operating system documentation.
  2. On Windows Server 2012 and Windows 8.x systems, the SNMP sub-agent does not have permission to open a socket over TCP/IP or UDP, preventing it from communicating with the maxView Storage Manager. Use the following PowerShell scripts to allow the SNMP sub-agent to communicate with the maxView Storage Manager and send trap notifications:
    1. Outbound Rule for Port 34572: 
      $OutBound = @{
    DisplayName = "Maxview Outbound Rule on TCP port 34572 for SNMP Service"
    Direction = "Outbound"
    InterfaceType = "Any"
    Action =  "Allow"
    Protocol =  "TCP"
    Service = "snmp"
    Program = "$($env:systemdrive)\WINDOWS\system32\snmp.exe"
    Enabled = "TRUE"
    RemotePort = "34572"
    PolicyStore = "ConfigurableServiceStore"
}
New-NetFirewallRule @OutBound
    2. Inbound Rule for Port 34572: 
      $InBound = @{
    DisplayName = "Maxview Inbound Rule on TCP port 34572 for SNMP Service"
    Direction = "Inbound"
    InterfaceType = "Any"
    Action =  "Allow"
    Protocol =  "TCP"
    Service = "snmp"
    Program = "$($env:systemdrive)\WINDOWS\system32\snmp.exe"
    Enabled = "TRUE"
    RemotePort = "34572"
    PolicyStore = "ConfigurableServiceStore"
}
New-NetFirewallRule @InBound
  3. To remove the NetFirewall rules (as needed):
    1. Outbound Rule for Port 34572: 
      Remove-NetFirewallRule -DisplayName "Maxview Outbound Rule on TCP port 34572 for SNMP Service" -PolicyStore "ConfigurableServiceStore"
    2. Inbound Rule for Port 34572: 
      Remove-NetFirewallRule -DisplayName "Maxview Inbound Rule on TCP port 34572 for SNMP Service" -PolicyStore "ConfigurableServiceStore"