Ordyn

Appearance

Printer Endpoints ​

Printer endpoints represent SNMP-managed printers in the Ordyn endpoint tree.

Printers do not run the Ordyn agent and do not enroll with an endpoint certificate. They are created manually in Ordyn and are queried by an assigned ordyn-snmp service client from the local network where the printer is reachable.

What you need ​

To create a printer endpoint, you need:

  • an active SNMP service client
  • an active SNMP credential profile in the same tenant
  • the printer hostname or management IP address
  • SNMP reachability from the selected service client to the printer

The hostname field is the SNMP management address. There is no separate printer management host field.

SNMP credential profiles support the same versions as switch endpoints:

  • SNMP v1 or v2c with a community string
  • SNMP v3 with username, security level, authentication protocol, privacy protocol, and matching secrets

Write-enabled credentials are not required for the current printer feature. Printer collection is read-only.

Create a printer endpoint ​

Create the endpoint from the endpoint tree or endpoint table:

  1. Open Create endpoint.
  2. Select type Printer.
  3. Enter the printer hostname or management IP.
  4. Select the SNMP service client that can reach the printer.
  5. Select the SNMP credential profile.
  6. Save the endpoint.

After creation, Ordyn immediately requests a lightweight printer system status collection. If the SNMP service client is connected and the printer responds, the printer overview starts showing the collected facts.

Editing printers ​

Use Edit printer from the endpoint action menu to change:

  • display name
  • hostname or management IP
  • SNMP service client
  • SNMP credential profile

Changing the hostname requests a fresh printer system status collection so the overview reflects the updated target.

Infrastructure role settings are not available for printer endpoints. Printers are managed infrastructure endpoints, not agent hosts.

Connected and active state ​

Printer endpoints use service-client based state.

Connected means the assigned SNMP service client is connected to Ordyn. It does not mean the printer itself has an open connection to Ordyn.

Active means Ordyn has a recent successful printer system status collection for that printer. The freshness window currently uses the shared SNMP Switch System Status Freshness setting and defaults to 7200 seconds.

This means a printer can be connected but inactive when the SNMP service client is online, but the printer has not responded recently or has never responded successfully.

Automatic refresh ​

Ordyn refreshes printer system status automatically.

Automatic collection runs when:

  • a printer endpoint is created
  • relevant printer endpoint details are updated
  • the background SNMP printer system status dispatcher finds a due printer

The background interval currently uses the shared SNMP Switch System Status Interval setting and defaults to 3600 seconds. The dispatcher only sends work for approved printer endpoints with:

  • SNMP configuration
  • an active credential profile
  • an active and connected SNMP service client

Pending requests are not retried continuously. A request that remains issued is considered stale after 15 minutes and can be dispatched again.

Collected data ​

Printer system status is intentionally lightweight and read-only. The SNMP service client collects generic SNMP and Printer-MIB facts where the printer exposes them.

The overview can show:

  • printer name
  • printer status
  • page count
  • system location
  • vendor
  • model
  • firmware
  • serial number
  • last collection status
  • last collection timestamp
  • last collection error
  • assigned SNMP service client
  • assigned credential profile

Printer status is mapped from the generic Printer-MIB status value:

  • other
  • unknown
  • idle
  • printing
  • warmup

Not every printer exposes all values. Missing values are shown as not reported.

Jobs ​

Printer endpoints support the Collect printer system status job task.

Use this task when you want to request a printer status collection on demand or include it in an automation. The task:

  • runs through the assigned SNMP service client
  • requires an active SNMP credential profile
  • stores the same facts as automatic collection
  • records success or failure in the job result

Use the Printer endpoints job requirement when a job should only run against printer endpoints.

IPAM ​

Printer endpoints can participate in IPAM as SNMP-managed endpoints.

The printer overview shows endpoint network interfaces. Each interface can store an IP address, MAC address, primary state, IPAM ignore state, and ICMP/common protocol probe settings.

When a matching IPAM network exists, Ordyn can reconcile printer interface addresses and printer management addresses into the IPAM address table.

Use Net node routing from the printer endpoint action menu to choose which net node should probe the printer's configured interfaces. If there is no direct endpoint assignment, Ordyn uses the inherited folder or tenant net-node assignment.

If the hostname is DNS-only, IPAM needs an observed or configured interface address to place the printer in a network address table.

Current limitations ​

The current printer feature does not include:

  • printer job management
  • toner or consumable inventory
  • tray status
  • print job inventory
  • SNMP trap workflows specifically for printers
  • printer write operations
  • vendor-specific printer extensions

Only safe generic SNMP facts are collected at this stage.