Translations of this page:

Osmius

Osmius agent for Amazing PDU amazing1_logo.jpg
Agent name: osm_ag_AMAZING1 Agent code: AMAZING1
Subject: User manual for AmazingPDU Power supply units
Date: 02/03/2010 Revision date: 08/03/2010

General Information

This agent can monitor several parameters of Power supply units manufactured by Amazing PDU. It has been tested against a Switched PDU AMzH-1623F/SW-08-8. However, we recommend checking its functionality before implanting it in a production environment.

The Osmius AmazingPDU agent has been developed using functionalities and enhancements of Osmius framework and ACE libraries, so it is necessary to install the ACE libraries for the proper deployment and operation of agente. See chapter: installation.

The AMAZING1 agent provides up to 167 basic events with configuration parameters to allow scaling of a very simple way. The basic events have been chosen by network experts. This agent also provides a general interface so the Osmius users can create customized events and associate them with any Instance within the monitoring system. Using the Osmius Web Console the users access to a MIB Navigator to load MIBS and to search for the appropriate snmp oid to create their own events.

In this agent all the provided events are non-intrusive events, remote events, so they can be retrieved from the network outside of the Instance being monitored. Events are build upon SNMP protocol version 1.

Instance AmazingPDU

As a general rule each Osmius agent can monitor one instance type. If you are not familiar with these concepts check out the glossary. Each instance is individually defined in the configuration file (if you want further information go to agents and instances); depending on agent type is the instance type and depending on instance is the connection info.

CONNECTION_INFO

The connection information or connection_info is data that the agent needs to know to connect to the instance. (See more about the connection_info)

In the particular case of AmazingPDU agent the CONNECTION_INFO field has no information needs as it uses the generic SNMP fields like Nodename, read community and snmp port.

CONNECTION_INFO= 

TYPE

The type defines the instance type to be monitored. Every declared instance must be associated with a type as you can see here

For AmazingPDU devices:

TYPE= AMAZING1

Event summary table

Here is briefly the capabilities of this agent, further down on this page each event is described in more detail.

EVENT DESCRIPTION c w a tseconds Extra parameters / Remarks
AMSYSDES System Description (SNMP) 1 0 0 86400 Silent mode ( -s) recommmended
AMSYSCON Contact Info 1 0 0 3600 Silent mode ( -s) recommmended
AMSYSLOC System Location 1 0 0 3600 Silent mode ( -s) recommmended
AMSYSNAM System Name (SNMP) 1 0 0 3600 Silent mode ( -s) recommmended
AMSYSUPT System Uptime in timeticks1 600 300 300 Interesting parameter for capacity plannings
AMINFDID Id Number 0 999 999 86400 Informative Event
AMINFVER Firmware version1 0 0 86400 Informative Event
AMINFIPI IP address, network mask, gateway and servidor DNS 1 0 0 86400 Informative Event
AMINFMAC MAC Address 1 0 0 86400 Informative Event
AMINFNUM Number of connected de PDUs and IDs 1 0 0 86400 Informative Event
AMINFVAL Current values from PDU1 to PDU16 1 0 0 86400 Informative Event
AMINHUMI Humidity percentage 0 70 80 3600 Interesting parameter for capacity plannings
AMINTEMP Temperature in Celsius 0 27 30 3600 Interesting parameter for capacity plannings
AMPDUC01 a AMPDUC16 Current in PDU01 (1 to 16) 0 8 10 300 Interesting parameter for capacity plannings
AMPDUV01 a AMPDUV16 Voltaje in PDU01 (1 to 16) 0 300 300 86400 Informative Event
AMPDUA01 a AMPDUA16 Alarm threshold in PDU01 (1 to 16) 1 0 0 86400 Informative Event
AMPDUW01 a AMPDUW16 Warning threshold in PDU01 (1 to 16) 1 0 0 86400 Informative Event
AMPDUI01 a AMPDUI16 PDU (01 to 16) Id 1 0 0 86400 Informative Event
AMPDUM01 a AMPDUM16 Model PDU (01 to 16) 1 0 0 86400 Informative Event
AMPDUN01 a AMPDUN16 Model Number PDU (01 to 16) 1 0 0 86400 Informative Event
AMPDUO01 a AMPDUO16 Outlets states from 1 to 8 in PDU (01 to 16) 1 0 0 600 Returns a list with the values
AMPDUS01 a AMPDUS16 Valores en los Outlets de 1 a 8 del PDU (01 a 16) 1 0 0 600 Returns a list with the values
AMUSER01 a AMUSER10 Get the SNMP values for the proposed parameters 1 0 0 600 Silent mode ( -s) recommmended
You can define from AMUSER01 to AMUSER10 (10 events)
-O oid -N override_nodename -K ovr_community -P ovr_port -V 1 (Use snmp v1 always when monitoring Amazing PDU devices)

AmazingPDU Events

AMSYSDES

AMSYSDES returns system description in the event associated text.

Return values:

VALUE MEANING
1 Error
0 Ok

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval Once a day
Warning threshold 0
Alert threshold 0

Parameter setting example:

AMSYSDES = -t 86400 -c 1 -w 0 -a 0 -T "System Description"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMSYSCON

AMSYSCOM returns the system contact info in the event associated text.

Return values:

VALUE MEANING
1 Error
0 Ok

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval Once a day
Warning threshold 0
Alert threshold 0

Parameter setting example:

AMSYSCON = -t 86400 -c 1 -w 0 -a 0 -T "Contact"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMSYSLOC

AMSYSLOC returns the system location info in the event associated text.

Return values:

VALUE MEANING
1 Error
0 Ok

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval Once a day
Warning threshold 0
Alert threshold 0

Parameter setting example:

AMSYSLOC = -t 86400 -c 1 -w 0 -a 0 -T "System Location"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMSYSNAM

AMSYSNAM returns the system snmp name in the event associated text.

Return values:

VALUE MEANING
1 Error
0 Ok

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval Once a day
Warning threshold 0
Alert threshold 0

Parameter setting example:

AMSYSDES = -t 86400 -c 1 -w 0 -a 0 -T "System Description"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMSYSUPT

AMSYSUPT event returns the number of ticks since the system was last time started up.

Return values:

VALUE MEANING
-1 Error
X Timeticks

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval 300 seconds – 1 hour –> depends on instance importance
Warning threshold 600 seconds. Consult your administrator
Alert threshold 300 seconds. Consult your administrator

Parameter setting example:

AMSYSUPT = -t 300 -c 1 -w 600 -a 300 -T "System Uptime"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMINFDID

AMINFDID return the unique Id number of the AmazingPDU device.

Return values:

VALUE MEANING
-1 Error
X Id

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval Once a day
Warning threshold 999
Alert threshold 999

Parameter setting example:

AMINFDID = -t 86400 -c 1 -w 0 -a 0 -T "System ID"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMINFVER

AMINFVER returns the Firmware version in the event associated text.

Return values:

VALUE MEANING
-1 Error
0 Ok

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval Once a day
Warning threshold 0
Alert threshold 0

Parameter setting example:

AMINFVER = -t 86400 -c 1 -w 0 -a 0 -T "Firmware Version"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMINFIPI

AMINFIPI return the network information: IP, netmask, gateway and DNS in the event associated text.

Return values:

VALUE MEANING
-1 Error
0 Ok

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval Once a day
Warning threshold 0
Alert threshold 0

Parameter setting example:

AMINFIPI = -t 86400 -c 1 -w 0 -a 0 -T "IP,netmask,gateway,DNS server"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMINFMAC

AMINFMAC returns the device network MAC address.

Return values:

VALUE MEANING
-1 Error
0 Ok

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval Once a day
Warning threshold 0
Alert threshold 0

Parameter setting example:

AMINFMAC = -t 86400 -c 1 -w 0 -a 0 -T "MAC Address"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMINFNUM

AMINFNUM returns the number of connected PDUs and the associated Ids. Example: STRING: “8,1,2,3,4,5,6,7,8”

Return values:

VALUE MEANING
-1 Error
0 Ok

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval Once a day
Warning threshold 0
Alert threshold 0

Parameter setting example:

AMINFNUM = -t 86400 -c 1 -w 0 -a 0 -T "PDUs and Ids"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMINFVAL

AMINFVAL returns the current values of associated PDUs. Example: STRING: “3,6,0,5,0,0,0,0,-1,-1,-1,-1,-1,-1,-1,-1”

Return values:

VALUE MEANING
-1 Error
0 Ok

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval Once a day
Warning threshold 0
Alert threshold 0

Parameter setting example:

AMINFVAL = -t 86400 -c 1 -w 0 -a 0 -T "Currents in PDUs"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMINHUMI

AMINHUMI returns the humidity percentage assuming the device has incorporated the appropriate sensor.

Return values:

VALUE MEANING
-1 Error
X % Humidity

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 300 seconds - 1 hour –> depends on instance importance
Warning threshold 999
Alert threshold 999

Parameter setting example:

AMINHUMI = -t 3600 -c 0 -w 70 -a 80 -T "Humidity Percentage"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMINTEMP

AMINTEMP returns the temperature in Celsius assuming the device has incorporated the appropriate sensor.

Return values:

VALUE MEANING
-1 Error
X Celsius

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 300 seconds - 1 hour –> depends on instance importance
Warning threshold 27
Alert threshold 30

Parameter setting example:

AMINTEMP = -t 3600 -c 0 -w 70 -a 80 -T "Temperature in Celsius degrees"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMPDUC01

AMPDUC01 returns the current in PDU01. The last part of this event name corresponds with the PDU number so you can change it from 01 to 16.

Return values:

VALUE MEANING
-1 Error
X Current

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 300 seconds - 1 hour –> depends on instance importance
Warning threshold 8
Alert threshold 10

Parameter setting example:

AMPDUC01 = -t 300 -c 0 -w 8 -a 10 -T "Current in PDU 01"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMPDUV01

AMPDUV01 returns the voltage in PDU01 (fixed value). The last part of this event name corresponds with the PDU number so you can change it from 01 to 16.

Return values:

VALUE MEANING
-1 Error
X Voltage

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 1 hour - 1 day –> depends on instance importance
Warning threshold 300 - Siempre OK
Alert threshold 300 - Siempre OK

Parameter setting example:

AMPDUV01 = -t 3600 -c 0 -w 8 -a 10 -T "Voltage in PDU 01"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMPDUW01

AMPDUW01 returns the Warning threshold configured in PDU01. The last part of this event name corresponds with the PDU number so you can change it from 01 to 16.

Return values:

VALUE MEANING
-1 Error
X Warning Value

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval 1 day - never –> depends on instance importance
Warning threshold Ask your administrator
Alert threshold Ask your administrator

Parameter setting example:

AMPDUW01 = -t 3600 -c 1 -w 0 -a 0 -T "Warning threshold PDU 01"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMPDUA01

AMPDUA01 returns the Warning threshold configured in PDU01. The last part of this event name corresponds with the PDU number so you can change it from 01 to 16.

Return values:

VALUE MEANING
-1 Error
X Warning Value

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval 1 day - never –> depends on instance importance
Warning threshold Ask your administrador
Alert threshold Ask your administrator

Parameter setting example:

AMPDUA01 = -t 3600 -c 1 -w 0 -a 0 -T "Alarm threshold in PDU 01"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMPDUI01

AMPDUI01 returns the Id associated to PDU01. The last part of this event name corresponds with the PDU number so you can change it from 01 to 16.

Return values:

VALUE MEANING
-1 Error
0 Ok

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval 1 day - never –> depends on instance importance
Warning threshold 0
Alert threshold 0

Parameter setting example:

AMPDUI01 = -t 86400 -c 1 -w 0 -a 0 -T "Id of PDU 01"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMPDUM01

AMPDUM01 returns the PDU01 model. The last part of this event name corresponds with the PDU number so you can change it from 01 to 16.

Return values:

VALUE MEANING
-1 Error
0 Ok

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval 1 day - never –> depends on instance importance
Warning threshold 0
Alert threshold 0

Parameter setting example:

AMPDUM01 = -t 86400 -c 1 -w 0 -a 0 -T "PDU 01 Model"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMPDUN01

AMPDUN01 returns PDU01 model number. The last part of this event name corresponds with the PDU number so you can change it from 01 to 16.

Return values:

VALUE MEANING
-1 Error
0 Ok

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval 1 day - never –> depends on instance importance
Warning threshold 0
Alert threshold 0

Parameter setting example:

AMPDUN01 = -t 86400 -c 1 -w 0 -a 0 -T "PDU 01 Model Number"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMPDUO01

AMPDUN01 returns the state of the PDU01 outlets from 1 to 8. The last part of this event name corresponds with the PDU number so you can change it from 01 to 16. Example: STRING: “1,-1,-1,-1,-1,-1,-1,-1”

Return values:

VALUE MEANING
-1 Error
0 Ok

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval 1 day - never –> depends on instance importance
Warning threshold 0
Alert threshold 0

Parameter setting example:

AMPDUO01 = -t 86400 -c 1 -w 0 -a 0 -T "PDU 01 Outlets state"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMPDUS01

AMPDUN01 returns current values in PDU01 outlets. The last part of this event name corresponds with the PDU number so you can change it from 01 to 16. Example: STRING: “3,2,5,0,-1,-1,-1,-1”

Return values:

VALUE MEANING
-1 Error
0 Ok

Recommended parameters:

Comparison type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring interval 1 day - never –> depends on instance importance
Warning threshold 0
Alert threshold 0

Parameter setting example:

AMPDUO01 = -t 86400 -c 1 -w 0 -a 0 -T "PDU 01 Outlets values"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

AMUSER01

AMUSER01 launches a SNMP get using the provided parameters. If the oid result is numeric this event returns a numeric value. If the oid result is a string this event returns 1 when everything is ok and the string within the event text. If something fails the returned value is 0.

Extra parameters:

PARAMETER MEANING Mandatory
-O -O “oid”- oid to recover. Try first one of these commands “snmpwalk -v1 -O f -c community target_IP” or “snmpget -v1 -c community -o oid target_IP. Yes
-N -L “nodename” - This node name overrides the one in the Instance CONNECTION_INFO and the default one (agent hostname). No
-K -K “community” - This “community name” overrides the one in the instance CONNECTION_INFO and the default one (“public”). No
-P -P “port” - This “port” overrides the one in the instance CONNECTION_INFO and the default one (161). No
-Q -Q “timeout” - timeout in seconds for the snmpget operations. Defaults to 0, no timeout. No
-V -V “version” - SNMP protocol version. Allowed values are [1, 2]. Defaults 2 (v2c). No

Return Values:

VALUE MEANING
-1 Error
0 Failed to retrieve
1 String value correctly retrieved
N Numeric value correctly retrieved

Recommended Parameters:

Comparison Type Inverted or Direct. Depending on the oid parameter.
monitoring interval 300 segundos – 1 hora –> depends on the instance classification
warning threshold 0 or N depending on the oid type
critical threshold or N depending on the oid type

Parameter setting example:

AMUSER01 = -t 300 -c 1 -w 0 -a 0 -T "Snmp system description" -O ".iso.org.dod.internet.mgmt.mib-2.system.sysDescr.0" -K secret_community -P 177 -Q 3 -V 1

Remarks: The associated SNMP text will be into the event text.
This event uses the Net-SNMP libraries

Prerequisites

In order to compile, this agent requires a set of prerequisites, which are generic to compile any Osmius agent, you can see these prerequisites.

In this particular agent you must also install Net-SNMP librares (Ubuntu “libsnmp”) that can be found here: http://net-snmp.sourceforge.net/ and in you OS repositories.

Compiling and Makefiles

  • Make Project Creator (MPC) is used by Osmius, so creating Makefiles is a trivial task. If you want to learn more about MPC and Osmius check out the section of Makefiles on Osmius.
  • In order to compile this agent we need include files and libraries provided by Net-SNMP (Ubuntu “libsnmp-dev”).
  • You can generate the Makefile in this way:

From the agent directory using console or terminal.

$ACE_ROOT/bin/mpc.pl -type gnuace osm_ag_amazing1.mpc
  • Now that you have created the Makefile, agent compiling is extremely simple.
gmake -f Makefile.Osm_Ag_Amazingpdu_Osmius

Binaries are automatically installed in the bin directory of OSM_ROOT base directory.

Running the Agent

The Osmius AmazingPDU Agent have the same running features of the other Osmius agents. You can check it out int he section Start and Stop Agents.

Without Osmius web console:

osm_ag_AMAZING1 -c osm_ag_AMAZING.ini -m MASTERAG -p 1950 -d [>> osm_ag_solaris.log]1)

Running in standalone mode

The Osmius AmazingPDU agent, like the others Osmius agents, allows the execution in standalone mode. This option may be particularly useful when developing a new agent or to perform specific agent tests.

Basically you have to add a new value, called SNDCMD, to Osmius agent configuration file (osm_ag_AMAZING1.ini) as shown here.

Setting Master Agent communications port to zero, for example:

osm_ag_AMAZING1 -c osm_ag_AMAZING1.ini -m 00000000 -p 0 -d

Tests list

Test performed to agent de Osmius para Solaris.

Date: 01/03/2010
Test Result Remarks
Creating an instance with all its events in silent mode OK N/A
Creating an instance with all its events with custom text OK N/A
Creating an instance with all its events but no custom text OK N/A
Declare 1 instance with all events set to 60 seconds and keep
running for 48 hours
OK no memory leaks detected
Declare 2 instances, cause a disconnect and then reconnectN.A. N/A
Declare 1 instance and test each event OK Sometimes it seems that the device gets over-questioned
Elimination of general parameter and check unbootable OK N/A
Elimination of instance CONN_INFO and check unbootable Can't do this no connect info

Events & OIDs

Evento oid
AMSYSDES .1.3.6.1.2.1.1.1.0
AMSYSUPT .1.3.6.1.2.1.1.3.0
AMSYSNAM .1.3.6.1.2.1.1.5.0
AMSYSLOC .1.3.6.1.2.1.1.6.0
AMSYSCON .1.3.6.1.2.1.1.4.0
AMINFDID .1.3.6.1.4.1.17420.1.2.1.0
AMINFVER .1.3.6.1.4.1.17420.1.2.4.0
AMINFIPI .1.3.6.1.4.1.17420.1.2.2.0
AMINFMAC .1.3.6.1.4.1.17420.1.2.3.0
AMINFNUM .1.3.6.1.4.1.17420.1.2.5.0
AMINFVAL .1.3.6.1.4.1.17420.1.2.6.0
AMINTEMP .1.3.6.1.4.1.17420.1.2.7.0
AMINHUMI .1.3.6.1.4.1.17420.1.2.8.0
AMPDUC01 .1.3.6.1.4.1.17420.1.2.9.1.11.0
AMPDUS01 .1.3.6.1.4.1.17420.1.2.9.1.12.0
AMPDUO01 .1.3.6.1.4.1.17420.1.2.9.1.13.0
AMPDUV01 .1.3.6.1.4.1.17420.1.2.9.1.17.0
AMPDUM01 .1.3.6.1.4.1.17420.1.2.9.1.18.0
AMPDUN01 .1.3.6.1.4.1.17420.1.2.9.1.19.0
AMPDUI01 .1.3.6.1.4.1.17420.1.2.9.1.20.0
AMPDUW01 .1.3.6.1.4.1.17420.1.2.9.1.15.0
AMPDUA01 .1.3.6.1.4.1.17420.1.2.9.1.16.0
AMPDUC02 .1.3.6.1.4.1.17420.1.2.9.2.11.0
AMPDUS02 .1.3.6.1.4.1.17420.1.2.9.2.12.0
AMPDUO02 .1.3.6.1.4.1.17420.1.2.9.2.13.0
AMPDUV02 .1.3.6.1.4.1.17420.1.2.9.2.17.0
AMPDUM02 .1.3.6.1.4.1.17420.1.2.9.2.18.0
AMPDUN02 .1.3.6.1.4.1.17420.1.2.9.2.19.0
AMPDUI02 .1.3.6.1.4.1.17420.1.2.9.2.20.0
AMPDUW02 .1.3.6.1.4.1.17420.1.2.9.2.15.0
AMPDUA02 .1.3.6.1.4.1.17420.1.2.9.2.16.0
AMPDUC03 .1.3.6.1.4.1.17420.1.2.9.3.11.0
AMPDUS03 .1.3.6.1.4.1.17420.1.2.9.3.12.0
AMPDUO03 .1.3.6.1.4.1.17420.1.2.9.3.13.0
AMPDUV03 .1.3.6.1.4.1.17420.1.2.9.3.17.0
AMPDUM03 .1.3.6.1.4.1.17420.1.2.9.3.18.0
AMPDUN03 .1.3.6.1.4.1.17420.1.2.9.3.19.0
AMPDUI03 .1.3.6.1.4.1.17420.1.2.9.3.20.0
AMPDUW03 .1.3.6.1.4.1.17420.1.2.9.3.15.0
AMPDUA03 .1.3.6.1.4.1.17420.1.2.9.3.16.0
AMPDUC04 .1.3.6.1.4.1.17420.1.2.9.4.11.0
AMPDUS04 .1.3.6.1.4.1.17420.1.2.9.4.12.0
AMPDUO04 .1.3.6.1.4.1.17420.1.2.9.4.13.0
AMPDUV04 .1.3.6.1.4.1.17420.1.2.9.4.17.0
AMPDUM04 .1.3.6.1.4.1.17420.1.2.9.4.18.0
AMPDUN04 .1.3.6.1.4.1.17420.1.2.9.4.19.0
AMPDUI04 .1.3.6.1.4.1.17420.1.2.9.4.20.0
AMPDUW04 .1.3.6.1.4.1.17420.1.2.9.4.15.0
AMPDUA04 .1.3.6.1.4.1.17420.1.2.9.4.16.0
AMPDUC05 .1.3.6.1.4.1.17420.1.2.9.5.11.0
AMPDUS05 .1.3.6.1.4.1.17420.1.2.9.5.12.0
AMPDUO05 .1.3.6.1.4.1.17420.1.2.9.5.13.0
AMPDUV05 .1.3.6.1.4.1.17420.1.2.9.5.17.0
AMPDUM05 .1.3.6.1.4.1.17420.1.2.9.5.18.0
AMPDUN05 .1.3.6.1.4.1.17420.1.2.9.5.19.0
AMPDUI05 .1.3.6.1.4.1.17420.1.2.9.5.20.0
AMPDUW05 .1.3.6.1.4.1.17420.1.2.9.5.15.0
AMPDUA05 .1.3.6.1.4.1.17420.1.2.9.5.16.0
AMPDUC06 .1.3.6.1.4.1.17420.1.2.9.6.11.0
AMPDUS06 .1.3.6.1.4.1.17420.1.2.9.6.12.0
AMPDUO06 .1.3.6.1.4.1.17420.1.2.9.6.13.0
AMPDUV06 .1.3.6.1.4.1.17420.1.2.9.6.17.0
AMPDUM06 .1.3.6.1.4.1.17420.1.2.9.6.18.0
AMPDUN06 .1.3.6.1.4.1.17420.1.2.9.6.19.0
AMPDUI06 .1.3.6.1.4.1.17420.1.2.9.6.20.0
AMPDUW06 .1.3.6.1.4.1.17420.1.2.9.6.15.0
AMPDUA06 .1.3.6.1.4.1.17420.1.2.9.6.16.0
AMPDUC07 .1.3.6.1.4.1.17420.1.2.9.7.11.0
AMPDUS07 .1.3.6.1.4.1.17420.1.2.9.7.12.0
AMPDUO07 .1.3.6.1.4.1.17420.1.2.9.7.13.0
AMPDUV07 .1.3.6.1.4.1.17420.1.2.9.7.17.0
AMPDUM07 .1.3.6.1.4.1.17420.1.2.9.7.18.0
AMPDUN07 .1.3.6.1.4.1.17420.1.2.9.7.19.0
AMPDUI07 .1.3.6.1.4.1.17420.1.2.9.7.20.0
AMPDUW07 .1.3.6.1.4.1.17420.1.2.9.7.15.0
AMPDUA07 .1.3.6.1.4.1.17420.1.2.9.7.16.0
AMPDUC08 .1.3.6.1.4.1.17420.1.2.9.8.11.0
AMPDUS08 .1.3.6.1.4.1.17420.1.2.9.8.12.0
AMPDUO08 .1.3.6.1.4.1.17420.1.2.9.8.13.0
AMPDUV08 .1.3.6.1.4.1.17420.1.2.9.8.17.0
AMPDUM08 .1.3.6.1.4.1.17420.1.2.9.8.18.0
AMPDUN08 .1.3.6.1.4.1.17420.1.2.9.8.19.0
AMPDUI08 .1.3.6.1.4.1.17420.1.2.9.8.20.0
AMPDUW08 .1.3.6.1.4.1.17420.1.2.9.8.15.0
AMPDUA08 .1.3.6.1.4.1.17420.1.2.9.8.16.0
AMPDUC09 .1.3.6.1.4.1.17420.1.2.9.9.11.0
AMPDUS09 .1.3.6.1.4.1.17420.1.2.9.9.12.0
AMPDUO09 .1.3.6.1.4.1.17420.1.2.9.9.13.0
AMPDUV09 .1.3.6.1.4.1.17420.1.2.9.9.17.0
AMPDUM09 .1.3.6.1.4.1.17420.1.2.9.9.18.0
AMPDUN09 .1.3.6.1.4.1.17420.1.2.9.9.19.0
AMPDUI09 .1.3.6.1.4.1.17420.1.2.9.9.20.0
AMPDUW09 .1.3.6.1.4.1.17420.1.2.9.9.15.0
AMPDUA09 .1.3.6.1.4.1.17420.1.2.9.9.16.0
AMPDUC10 .1.3.6.1.4.1.17420.1.2.9.10.11.0
AMPDUS10 .1.3.6.1.4.1.17420.1.2.9.10.12.0
AMPDUO10 .1.3.6.1.4.1.17420.1.2.9.10.13.0
AMPDUV10 .1.3.6.1.4.1.17420.1.2.9.10.17.0
AMPDUM10 .1.3.6.1.4.1.17420.1.2.9.10.18.0
AMPDUN10 .1.3.6.1.4.1.17420.1.2.9.10.19.0
AMPDUI10 .1.3.6.1.4.1.17420.1.2.9.10.20.0
AMPDUW10 .1.3.6.1.4.1.17420.1.2.9.10.15.0
AMPDUA10 .1.3.6.1.4.1.17420.1.2.9.10.16.0
AMPDUC11 .1.3.6.1.4.1.17420.1.2.9.11.11.0
AMPDUS11 .1.3.6.1.4.1.17420.1.2.9.11.12.0
AMPDUO11 .1.3.6.1.4.1.17420.1.2.9.11.13.0
AMPDUV11 .1.3.6.1.4.1.17420.1.2.9.11.17.0
AMPDUM11 .1.3.6.1.4.1.17420.1.2.9.11.18.0
AMPDUN11 .1.3.6.1.4.1.17420.1.2.9.11.19.0
AMPDUI11 .1.3.6.1.4.1.17420.1.2.9.11.20.0
AMPDUW11 .1.3.6.1.4.1.17420.1.2.9.11.15.0
AMPDUA11 .1.3.6.1.4.1.17420.1.2.9.11.16.0
AMPDUC12 .1.3.6.1.4.1.17420.1.2.9.12.11.0
AMPDUS12 .1.3.6.1.4.1.17420.1.2.9.12.12.0
AMPDUO12 .1.3.6.1.4.1.17420.1.2.9.12.13.0
AMPDUV12 .1.3.6.1.4.1.17420.1.2.9.12.17.0
AMPDUM12 .1.3.6.1.4.1.17420.1.2.9.12.18.0
AMPDUN12 .1.3.6.1.4.1.17420.1.2.9.12.19.0
AMPDUI12 .1.3.6.1.4.1.17420.1.2.9.12.20.0
AMPDUW12 .1.3.6.1.4.1.17420.1.2.9.12.15.0
AMPDUA12 .1.3.6.1.4.1.17420.1.2.9.12.16.0
AMPDUC13 .1.3.6.1.4.1.17420.1.2.9.13.11.0
AMPDUS13 .1.3.6.1.4.1.17420.1.2.9.13.12.0
AMPDUO13 .1.3.6.1.4.1.17420.1.2.9.13.13.0
AMPDUV13 .1.3.6.1.4.1.17420.1.2.9.13.17.0
AMPDUM13 .1.3.6.1.4.1.17420.1.2.9.13.18.0
AMPDUN13 .1.3.6.1.4.1.17420.1.2.9.13.19.0
AMPDUI13 .1.3.6.1.4.1.17420.1.2.9.13.20.0
AMPDUW13 .1.3.6.1.4.1.17420.1.2.9.13.15.0
AMPDUA13 .1.3.6.1.4.1.17420.1.2.9.13.16.0
AMPDUC14 .1.3.6.1.4.1.17420.1.2.9.14.11.0
AMPDUS14 .1.3.6.1.4.1.17420.1.2.9.14.12.0
AMPDUO14 .1.3.6.1.4.1.17420.1.2.9.14.13.0
AMPDUV14 .1.3.6.1.4.1.17420.1.2.9.14.17.0
AMPDUM14 .1.3.6.1.4.1.17420.1.2.9.14.18.0
AMPDUN14 .1.3.6.1.4.1.17420.1.2.9.14.19.0
AMPDUI14 .1.3.6.1.4.1.17420.1.2.9.14.20.0
AMPDUW14 .1.3.6.1.4.1.17420.1.2.9.14.15.0
AMPDUA14 .1.3.6.1.4.1.17420.1.2.9.14.16.0
AMPDUC15 .1.3.6.1.4.1.17420.1.2.9.15.11.0
AMPDUS15 .1.3.6.1.4.1.17420.1.2.9.15.12.0
AMPDUO15 .1.3.6.1.4.1.17420.1.2.9.15.13.0
AMPDUV15 .1.3.6.1.4.1.17420.1.2.9.15.17.0
AMPDUM15 .1.3.6.1.4.1.17420.1.2.9.15.18.0
AMPDUN15 .1.3.6.1.4.1.17420.1.2.9.15.19.0
AMPDUI15 .1.3.6.1.4.1.17420.1.2.9.15.20.0
AMPDUW15 .1.3.6.1.4.1.17420.1.2.9.15.15.0
AMPDUA15 .1.3.6.1.4.1.17420.1.2.9.15.16.0
AMPDUC16 .1.3.6.1.4.1.17420.1.2.9.16.11.0
AMPDUS16 .1.3.6.1.4.1.17420.1.2.9.16.12.0
AMPDUO16 .1.3.6.1.4.1.17420.1.2.9.16.13.0
AMPDUV16 .1.3.6.1.4.1.17420.1.2.9.16.17.0
AMPDUM16 .1.3.6.1.4.1.17420.1.2.9.16.18.0
AMPDUN16 .1.3.6.1.4.1.17420.1.2.9.16.19.0
AMPDUI16 .1.3.6.1.4.1.17420.1.2.9.16.20.0
AMPDUW16 .1.3.6.1.4.1.17420.1.2.9.16.15.0
AMPDUA16 .1.3.6.1.4.1.17420.1.2.9.16.16.0
1) Optional, to store agent messages in a file
 
en/agentes/amazing1.txt · Last modified: 2012/12/05 19:32 by osmius
 
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki