Packeteer SNMP Traps

PacketWise supports up to eight destinations for SNMP traps. Configure these addresses via the browser (see Configure PacketWise for SNMP Support) or the command-line interface (see setup snmp). These destinations also can be set via SNMP itself.

PacketWise issues several traps, which provide notification of component failures or status changes for certain PacketShaper models.

Fan Failure. (Available on PacketShaper 1400, 1700, 3500, 7500, 8500, 9500, 10000 models only.) A trap is generated when any of the fans fail.

• 1400/1700/3500: PacketShaper 1400, 1700, and 3500 models have a single CPU fan. Packeteer recommends that you power down the PacketShaper after a fan failure, in order to avoid damage to the unit.
• 7500: The PacketShaper 7500 model has two fans: one for the CPU and one for the power supplies. PacketWise issues a Fan 1 Failure if the CPU fan fails and a Fan 2 Failure if the power supply fan fails. Packeteer recommends that you power down the PacketShaper after a fan failure, in order to avoid damage to the unit.
• 8500/9500: If the CPU fan fails, a Fan 1 Failure trap will be issued and the unit will stop functioning. This type of failure is critical and requires immediate attention. If either of the two rear fans fail, PacketWise issues a Fan 2 Failure trap, but the unit will continue to operate with degraded air flow. In this case, you should inspect the back of the unit to determine which fan has failed.
• 10000: The PacketShaper 10000 model has a cooling unit that contains two sets of series fan pairs. If any of the four fans fail, the appropriate Fan Failure trap (1-4) will be sent. If one fan fails in a series pair, the other fan has sufficient cooling capacity under normal environmental conditions. Packeteer recommends that you replace the cooling unit as quickly as possible after a fan failure, to minimize the amount of time that the unit is functioning with reduced air flow.

High Availability Device Down. A trap is generated when a device that is being monitored by the high availability feature goes down. The device can be an access router or a WAN link interface. The trap includes the following information:

• Status — 0 (meaning the device has gone down)
• Router Name — The IP address or DNS name of the configured router that has gone down or whose configured interface has gone down
• Interface Name — The name of the interface (ifname) that has gone down. If the interface name could not be resolved, UNKNOWN will be displayed. If the router went down (as opposed to an individual interface), no information will be displayed.

Measurement Engine. A trap is generated when PacketWise detects any of the following conditions:

• The measurement engine fails to start properly.
• The measurement engine is stopped while measurement data is being backed up.
• The measurement engine is stopped while measurement data is being restored.
• Startup is disabled.
• Measurement data cannot be saved because of a problem on the hard disk.

Power Supply Failure. A trap is generated when a power supply fails. The trap indicates which power supply failed. On the PacketShaper 7500 model, the lower power supply is Power 1 and the top power supply is Power 2. Note: On the PacketShaper 8500, failure of either power supply generates a "psAlarmPowerSystemOne" trap. To determine which power supply has a problem, check the power supply LEDs — the power supply with the light off is the one that has come unplugged or has failed.

Site Router Status. A trap is generated to indicate the status of PacketWise 's site router:

• ready — Site router is actively routing or ready to route.
• gone — PacketWise is not receiving ARP replies from the router.
• error inside — PacketWise received an ARP reply, but from the inside.
• none — No site router has been configured.

Standby Status Change. A trap is generated when the standby status has changed. The status states are:

• 1: not configured (hot/direct standby is not configured on this unit)
• 2: active (hot standby is processing traffic according to its shaping mode)
• 3: passive (hot standby is not processing traffic but is monitoring the active partner of the paired PacketShapers)
• 4: down (hot standby has declared itself ineligible for active mode due to a self-detected fault
• 5: direct (direct standby is processing and copying traffic to its partner)
• 6: disconnected (direct standby is non-functional because it cannot reach its partner)
• 7: leak (PacketWise has detected a loop in the network and has disabled the direct standby functionality but is still processing traffic flowing through the unit)
• 8: disable (direct standby has been disabled and is non-functional)
  

Voltage Status. The PacketShaper 1700, 3500, and 7500 models have five voltage regulators: 2.5v, 3.3v, 5v, 12v, and CPU Core. If one or more of these regulators falls out of the proper range, an SNMP trap is sent. The possible values of the trap are as follows:

no voltage information available
all the voltage inputs are wihtin the normal range
the 2.5v input is not within the proper range
the CPU Core Voltage is not within the proper range
the 2.5v input and the CPU Core Voltage are not within the proper range
the 3.3v input is not within the proper range
the 2.5v and 3.3v input are not within the proper range
the CPU core and 3.3v input are not within the proper range
the 2.5v input, the CPU Core Voltage and 3.3v input are not within the proper range
the 5v input is not within the proper range
the 2.5v and 5v input are not within the proper range
the CPU core and 5v input are not within the proper range
the 2.5v input, the CPU Core Voltage and 5v input are not within the proper range
the 3.3v and 5v input are not within the proper range
the 2.5v, 3.3v and 5v input are not within the proper range
the CPU core, 3.3v and 5v input are not within the proper range
the 2.5v input, the CPU Core Voltage, 3.3v and 5v input are not within the proper range
the 12v input outside the proper range
the 12v input is not within the proper range
the CPU core and 12v input are not within the proper range
the 2.5v input, the CPU Core Voltage and 12v input are not within the proper range
the 3.3v and 12v input are not within the proper range
the 2.5v, 3.3v and 12v input are not within the proper range
the CPU core, 3.3v and 12v input are not within the proper range
the 2.5v input, the CPU Core Voltage, 3.3v and 12v input are not within the proper range
the 5v and 12v input are not within the proper range
the 2.5v and 5v and 12v input are not within the proper range
the CPU core, 5v and 12v input are not within the proper range
the 2.5v input, the CPU Core Voltage, 5v and 12v input are not within the proper range
the 3.3v and 5v and 12v input are not within the proper range
the 2.5v, 3.3v, 5v and 12v input are not within the proper range
the CPU core, 3.3v, 5v and 12v input are not within the proper range
the 2.5v, CPU core, 3.3v, 5v and 12v input are not within the proper range

PacketWise also supports the following standard SNMPv2 traps:

Authentication Failure. A MIB-II trap is generated when an SNMP agent determines that a request did not get proper authentication, usually the result of a bad community string.

Cold/Warm Start. PacketWise issues a MIB-II trap during reset — that is, when loading a new image, manually initiating a unit reset, or recovering from a crash.

Link Up/Down. A MIB-II trap is generated each time a link goes down and again when the link returns to normal. The trap indicates which link went down.

PacketGuide™ for PacketWise® 8.1