SNMP example 4.3 – Create SNMP queries from several OID queries

Article description

SNMP example 4.3 – Create SNMP queries from several OID queries
You can create SNMP queries from any number of OID queries.

cyanProfile

A classic example for a SNMP profile consisting of several OIDs is the determination of the fill level of the cartridge.

The used OIDs are:
1.3.6.1.2.1.43.11.1.1.8.1.1 = Max. toner level (Cyan)
1.3.6.1.2.1.43.11.1.1.9.1.1 = Current toner level (Cyan)

In order to determine this value, the current fill value has to be subtracted from the maximum fill value and divided by 100. The sum of this result is the current fill value in percent (%).

We create a SNMP query and call it “Cyan”. We choose Marker as the category and specify manufacturer and model for this query. We then create 2 OID queries with the category Marker:
We choose the color Cyan and the max. capacity. We enter 1.3.6.1.2.1.43.11.1.1.8.1.1 as the OID and confirm with “OK”. Now we create the second query with current capacity. We enter 1.3.6.1.2.1.43.11.1.1.9.1.1 as the OID and again confirm with “OK”.

cyanCurrentOid

cyanOid

ID: sP00000 | Created on: 09-Nov-2015

Back to overview

SNMP Example 4.4 – Edit a SNMP query

Article description

In order to edit a SNMP query, you can directly click “…” of the respective query in the Monitoring tab or get to this view via the SNMP profiles. The function Edit enables you to edit all previously defined values for this SNMP query. The category of the query cannot be subsequently edited.

ID: sP00000 | Created on: 09-Nov-2015

Back to overview

SNMP Example 4.5 – Creating a report including page prices

Article descriptionExample 4.5: Creating a report including page prices

Best Practice:
We recommend to provide a separate server for the Monitoring function so that all environments can be controlled.
Create a new performance profile in the Center to collect SNMP data and disable the collection of SNMP data in all other performance profiles so that all data will be recorded once from a central point.

PerformanceProfileSNMPsammeln

Switch to the Monitoring tab and create the OID queries for color pages and monochrome print.

OidColor

Please take the OIDs from the MIB files of the respective manufacturer. Choose Page Counter (color) or Page Counter (mono) as OID category. With this setting the OIDs are connected to the report.

Open Reporting (under the tab Extras) and create a report containing page prices.

Reporting

ID: sP00000 | Created on: 09-Nov-2015

Back to overview

Configuration of SNMP connection settings

Description of the problem

We are using the SNMP monitoring of steadyPRINT. In order to access our printers via SNMP, however, we need a special configuration, among others the adjustment of the “Community String” for reading SNMP values. Is it possible to adjust the Connection parameters?

Read more

Webserver cannot be started – invalid access rights

Description of the problem

We are currently installing the steadyPRINT web server. Unforunately, the service cannot be started on our computer. The following error is displayed in the event log:

The Apache service named reported the following error:
>>>(OS 10013)The access to a socket was invalid due to the access rights of the socket. : AH00072: make_sock: could not bind to address [::]:443 .

The Apache service named reported the following error:
>>>(OS 10013)The Access to a socket was invalid due to the access rights of the socket. : AH00072: make_sock: could not bind to address 0.0.0.0:443 .

The Apache service named reported the following error:
>>>AH00451: no listening sockets available, shutting down .

The Apache service named reported the following error:
>>>AH00015: Unable to open logs .

Can you provide further assistance?

Read more

New licensing

Description of the problem

The technical implementation of the new licensing had long remained to be done. In version 5.1.1 this can now be realized. Depending on the used license, only those functions which have actually been licensed are provided. As a result it can happen that features used before are now no longer available.

Read more

Extended Logging

Description of the problem

steadyPRINT writes important information to the Windows Event Viewer. All normal application components like the steadyPRINT Agent and the steadyPRINT Center store the entries in the Event Viewer > Windows Logs > Application. However, the steadyPRINT service components write the information to Event Viewer > Windows Logs > System.

Read more

Although the monitoring of the printer environment was activated, no printers are shown in the dashboard

Description of the problem

By default, the dashboard only indicates printers with a current warning or error status. In case none of the printers selected for the monitoring has such a status, they are not displayed in the dashboard.

Read more

Job monitoring under Windows Server 2008

Description of the problem

Currently, it is only possible for steadyPRINT Center to perform job monitoring under Windows Server 2003. An implementation for later versions is currently being worked on.

Read more

Determination of status information takes “a long time”

Description of the problem

The information needed for the display of status information directly derives from the corresponding print server. Only if a printer failure is noticed, this error will be displayed in the steadyPRINT Agent and/or Center.

Read more