Everything about Tahiru: setting up sites and collectors, policies, licenses, access, supported hardware, configuration guides and troubleshooting.
Getting started
Add a collector to a site
A collector is a small Windows service on your network that discovers and monitors your servers. Install one per site or network segment. It connects out on HTTPS 443 only; no inbound ports or VPN.
Open Sites, choose the site (or create it), and press Add a collector here. From Collectors, Add collector also works: choose the site first, or + New site.
Name the collector, for example "Seattle DC collector", and press Create pairing code. The code works once and expires.
On the Windows machine (Windows 10/11 or Server 2019+, 64-bit), open PowerShell as Administrator and run the command shown. Paste the pairing code when asked; it is hidden as you paste.
Back in the portal, press Approve. The collector joins its site and shows Connected within about 5 minutes.
Discover the servers at a site
Tahiru finds servers on the networks you approve and starts monitoring them through their management controllers (Redfish: Cisco CIMC, Dell iDRAC, HPE iLO, Lenovo XClarity and others).
Open the site. Under Networks ready to scan, press Scan this network for each network the collector sees, or add a network by hand. Nothing is scanned until you approve it.
Under Credentials, add a read-only BMC login. It is encrypted in your browser; only your collectors can read it.
Press Scan now. Follow it in Workflows (top right): the collector picks it up, scans, and the servers appear under Servers, already monitored where a credential worked.
Scans also run every 6 hours on their own, and whenever you approve a network or add a credential.
Upgrade collectors
Collectors upgrade from the portal: no one needs to visit the machine. The installer is signed and checked before it runs, and monitoring pauses for about a minute.
One collector: on Collectors (or the collector's page), press Upgrade next to "Update available".
Several at once: tick the collectors to upgrade in the Collectors table, then press Upgrade selected.
Follow each in Workflows (top right). The step in progress spins and says what it is waiting on; the collector shows Upgrading, then Connected with the new version, usually within 10 minutes.
If a step fails, it turns red with a code. Press the code for the fix.
Tahiru monitors your servers and network from the cloud through small collectors on your networks. Everything you set up follows one path.
Sites: a site is a location or network you monitor, such as a data center or an office.
Collectors: a collector is a small Windows service at a site. It discovers devices, polls them and sends what it finds to Tahiru over HTTPS. It needs no inbound ports.
Credentials: the read-only logins the collectors use (SNMP, device logins, vCenter). They are encrypted in your browser for your collectors only; Tahiru cannot read them.
Devices: everything discovered at your sites, with health, faults, backups and logs.
Policies: what Tahiru does on its own for each device, such as daily configuration backups, log collection, fault rules and weekly health reports.
Licenses: each device is Free, Gold or Platinum. Policies and log analysis need Gold; working investigations with a Tahiru engineer needs Platinum.
Set up your first site
From an empty organization to monitored devices in about 15 minutes.
Open Sites and press New site. Give it a name, for example "Dallas data center".
On the site, press Add a collector here and install the collector on a Windows machine at that site (see Add a collector to a site). Approve it when it appears.
Under Networks, approve the networks the collector found, or add a network by hand. Nothing is scanned until you approve it.
Under Credentials, add an SNMP credential (v3 recommended) for your network devices, and a device login for servers and configuration backups.
Press Scan now. Devices appear under Devices as they are found; follow the scan in Workflows.
Open Policies and assign Daily backup, a log policy and a health report to the devices you want covered.
Sites and collectors
Create, edit or delete a site
Owners and admins manage sites. Each site has its own collectors, networks and credentials.
Create: Sites, New site. Name it and add a description if you like.
Edit: open the site and press Edit at the top right to change its name or description.
Delete: Edit, then Delete site. A site can be deleted only once it has no collectors: move or remove them first.
Every change is recorded in Workflows and the audit log.
Approve, disable, move or remove a collector
Collectors appear on Collectors and on their site.
Approve: a newly paired collector waits for approval. Press Approve on its row; it starts working within a few minutes.
Disable: on the collector's page, Disable stops it at once. Enable lets it connect again.
Move to another site: on the collector's page, change its site. It drops the old site's credentials and receives the new site's.
Remove: disable it, then uninstall it from the Windows machine (Apps and features, Tahiru Collector).
Devices
The Devices page and saved views
Every device across your sites, with health, license, site and when it was last seen.
Search by name, model, vendor or serial; filter by site and health.
Saved views: press New view to save a tab such as "Lab servers" (sites Lab and HQ, servers only). Views are kept in your browser and only narrow what is shown.
Assign policy and Assign license (top right) put a policy or license on many devices at once; see Assign policies.
Open a device for its own page: Overview, Health, Backups, Log analysis, Policies, License and Workflows.
Performance graphs and threshold alerts
A network device's Health tab shows its CPU, memory and traffic over the last 24 hours, 7 days or 30 days, from SNMP polling every minute.
Open the device, Health tab, Performance. Choose the range at the top right; hover a graph for the values at that time.
Traffic shows ingress and egress on the device's busiest interfaces; pick one from the list. Each point is the highest value in its five minutes (or hour, for 7 and 30 days).
Tahiru opens a fault on its own when CPU stays at 90% or more, memory at 95% or more, an interface at 90% of its speed or 50 errors a minute, a sensor (fan, power supply, temperature) reports a failure, or a disk or flash is 95% full. It clears when the value comes back down.
Those faults follow your fault policies (for example ignore Interface errors or saturation on access ports) and your alert rules decide who is told.
History is kept for 30 days.
Graphs need a working SNMP credential for the device; the first points appear within five minutes.
Rename a device, set its type, or stop managing it
Tahiru names and types devices from what they report. You can override both.
Open the device and press Edit (top right).
Change its name or type, or turn off Managed to keep it listed but stop monitoring, backups and logs for it.
Save. The change is recorded in Workflows and the audit log.
Credentials
Add credentials
Credentials are added per site and sealed in your browser to each of the site's collectors. Tahiru stores only ciphertext and cannot read them.
Open the site, Credentials, and choose the type: SNMP v3 (recommended), v2c or v1 for network devices; Device login for servers (Redfish) and configuration backups (SSH); VMware for vCenter or ESXi.
Choose where it applies: every device at the site, or only the devices and networks you pick.
To use the same account at other sites, tick Also add to other sites (or All sites). Each site's collectors get their own sealed copy.
Read-only user with auth and privacy (authPriv) recommended
SNMP v2c / v1
Older network devices
Community string is sent unencrypted; use v3 where supported
Device login
Servers over Redfish; switches, routers and firewalls over SSH (backups, logs)
One account per device type. For backups it must run show running-config
VMware
vCenter Server or standalone ESXi
A read-only vSphere user
Use one shared, LDAP, TACACS+ or RADIUS account
If many devices accept the same account, add it once.
Add a Device login with that account and leave it on Every device. Tahiru tries it on each device at the site.
Accounts your devices check against LDAP, Active Directory, TACACS+ or RADIUS work the same way: enter the username as the devices expect it (user, DOMAIN\user or user@domain).
Tick Also add to other sites to add it everywhere in one step.
Policies and retention
How policies work
A policy decides what Tahiru does on its own for a device. Each policy does one thing, and every device starts on No policy, where nothing happens.
Four types are set per device: Backup, Log, Fault and Health report. A device follows one policy of each. Alert rules are different: they are set once for the whole organization (see Get alerted).
Each type has ready-made policies (No policy, Daily, Weekly and, for health reports, Monthly). Create your own for anything else.
Which policy a device follows: one set on the device itself wins; otherwise its family's default (Policies, Device families: Servers and compute, Network, Security, Storage, Power, Other); otherwise No policy. Set a family once and new devices of that family follow it too.
Policies run only on Gold and Platinum devices. On a Free device the choice is kept and starts working once the device is licensed.
Servers monitored through their management controller take Fault and Health report policies; backup and log policies are for network devices.
Type
What it does
Shown on the device's
Backup policy
Backs up the configuration over SSH at the time you set; only changed configurations are stored
Backups tab
Log policy
Reads the device's own log and collects a tech support on a schedule
Log analysis tab
Fault policy
Decides what matters: keeps the vendor's severity, or changes it or ignores it for a category of fault, for example interface down → ignore
Faults
Health report policy
Emails a weekly or monthly health report of the devices on it to the people you choose
Health tab
Alert rule
Organization-wide, not per device: tells the people you choose (owners and admins if you choose no one), in the portal and by email, about faults at or above a severity on the device families and sites you pick, and when they clear
The bell, top right
Get alerted when a fault opens
Alert rules decide who is told about which faults, for the whole organization: a notification under the bell (top right) and an email. They are not set device by device.
Open Policies, Alerts. Two ready-made rules exist: Critical faults, and Warnings and critical faults. Both also alert when the fault clears.
Edit a rule: turn it on or off, choose who is told (no one chosen: the owners and admins), and which device families and sites it covers (none ticked: everything, including devices found later).
Add as many rules as you need with + New policy, Alert rule. For example: NOC on Major and above for everything; the CIO on Critical only; the branch team on Warnings and above at their site.
Every rule that is on and covers a fault's device alerts. Someone named in several rules is told once.
Alerts follow the device's fault policy: a type of fault it ignores never alerts, and one it re-grades alerts at its new severity.
A new organization starts with Critical faults on, for every device, so owners and admins hear about critical faults from the first device.
Open the bell to see your alerts; pressing one marks it read and opens its device. Mark all read clears the count.
Alerts run on Gold and Platinum devices, like every policy.
Email is sent once your organization's email is set up; notifications in the portal work straight away.
Faults and alerts: how a fault becomes an alert
Every vendor names and grades faults its own way. Tahiru keeps the vendor's own severity, sorts each fault into a category, and then your policies decide what matters and who is told.
The device reports a fault. Tahiru keeps the severity the vendor gave it: Critical, Major, Minor, Warning or Informational. A Cisco UCS Major fault stays Major, and a Minor one stays Minor.
Tahiru sorts it into a category the same way for every vendor: device unreachable, interface down, power supply, fan, temperature, memory, storage, processor, adapter, fabric, firmware, configuration and more. A Cisco power supply fault and a Dell one are both Power supply.
The device's fault policy decides what matters. For each category: as the vendor reports it (the default), a different severity, or ignore.
Your alert rules decide who is told, for the whole organization: each rule names people, a severity (Critical faults, Major and above, Minor and above, Warnings and above, or every fault), the device families and sites it covers, and whether to tell again when the fault clears.
Severity
Means
Critical
Service is down or about to be; act now
Major
Service is impaired, for example a redundant part has failed
Minor
Something is wrong but service is not affected
Warning
Something may become a problem
Informational
Worth knowing; nothing is wrong
Set both policies once per family on Policies, Device families, and change single devices on their Policy tab.
The Faults page shows the severity after your fault policy, with the vendor's original next to it when the policy changed it.
Create or edit a policy
Owners and admins create policies on the Policies page.
Policies, New policy, then choose the type.
Name it and set what it does: how often, the hour, the weekday and the time zone; for faults, the rule for each kind; for health reports, how often and who receives it.
Save. Then assign it to devices (see Assign policies).
Ready-made policies keep their name and frequency; you can change only their time, time zone and recipients (Change time).
Assign policies to devices, one or many
One way to put a policy on devices, wherever you start.
Many devices: Devices or Policies, Set policies, then press Assign policy. Choose the devices (search, tick, or Select all shown), the type and the policy, and press Assign.
One device: open it, Policies tab, choose a policy for each type and press Save.
Back to nothing: assign No policy for that type.
Each assignment is one change in Workflows and the audit log, however many devices it covers.
Delete a policy
Owners and admins can delete policies they created.
Policies, find the policy, press Delete and confirm.
Devices it was on go back to No policy for that type.
Ready-made policies (No policy, Daily, Weekly, Monthly) cannot be deleted.
Retention: how long data is kept
Retention is one system policy for the whole organization, on Policies, Retention. Owners and admins change it.
Data
Choices
Default
Configuration backups
90 days, 1 year, 2 years
Every change kept; the newest of each device is always kept
Device logs
7, 30, 90 days, 1 year
Newest 20 per device
Fault history (cleared faults)
90 days, 1 year, 2 years
Kept; open faults are never deleted
Tech supports, syslog, sensor history
Fixed
30 days
Older records are deleted for good on Tahiru's regular pass. Each change is recorded in Workflows and the audit log.
Licenses
License tiers
Every device has a license tier. What it includes applies to that device.
Includes
Free
Gold
Platinum
Discovery, inventory, health and faults
Yes
Yes
Yes
Policies: backups, logs and tech supports, fault rules, health reports
—
Yes
Yes
Log parsing in investigations
—
Yes
Yes
Tahiru assistant: how-to, guidance and advisory
—
Yes
Yes
Investigations you run yourself
—
Yes
Yes
Investigations worked with a Tahiru engineer
—
—
Yes
Deep log review and bug call-outs
—
—
Yes
New devices are Gold for their first 30 days, then Free until licensed.
A license can have an end date. After it, the device is Free again; nothing collected is deleted.
Buy, assign or change licenses
Licenses are bought from Tahiru and applied by Tahiru. Your team sees each device's license on the Licenses page and on each device's License tab.
Contact your Tahiru account team, or open an investigation, with the number of Gold and Platinum licenses and the term you need.
Tahiru applies them to the devices you name, all at once. Each change is recorded in Workflows and your audit log.
Check them on Licenses: each tier's card shows how many devices have it; the table shows each device's tier and end date.
Access and single sign-on
Roles: who can do what
Each member has one organization role. Site roles give extra access on chosen sites. The full table is on Access, Roles.
Role
Can do
Owner
Everything, including other owners, single sign-on and the organization itself
Admin
Sites, collectors, credentials and policies; invites engineers, viewers and site members
Engineer
Works devices, backups, logs, faults and investigations on every site
Support
A Tahiru support engineer working your investigations with you
Viewer
Reads everything; changes nothing
Site member
Only the sites given to them, with the site role chosen (Site admin, Operator or Viewer)
Invite someone
Owners invite anyone; admins invite engineers, viewers and site members.
Access, Invite someone. Enter their email and choose a role.
They receive an email and sign in with that address within 7 days. Pending invitations are listed under Members; Revoke withdraws one.
For a site member, give their sites under Manage access once they join.
Change a role, give site access or remove someone
From Access, Members.
Press Manage access on the member. Change their organization role, or give a role on a site.
To remove someone, press Remove from organization under Manage access. They lose access at once; Restore access brings it back.
You cannot change your own role; ask another owner.
Your organization: plan, people and renaming it
Admin, Organization shows who your organization is, its plan and trial, what it has, and who runs it.
Open Organization in the menu (or Settings, Organization page). Everyone except site members can see it.
The plan shows how many trial days are left. Contact Tahiru to continue after a trial.
Owners and admins also see the owners, member and invitation counts, single sign-on and whether Tahiru support may open the organization; each links to where it is changed.
Owners can rename the organization: press Rename, type the new name and Save. The short name and sign-in do not change.
A rename is a change in Workflows and the audit log.
Keep at least two owners so the organization is never locked out.
Add a co-owner or transfer ownership
An organization always keeps at least one active owner.
Add a co-owner: Manage access on a trusted member and set their role to Owner. Keep at least two owners so the organization is never stranded.
Transfer ownership: make the new person an owner, then ask them to change your role. A transfer is always a two-person step.
Single sign-on with your directory
Your people sign in with their company account (LDAP or Active Directory, Microsoft Entra ID, Okta, Google, SAML or OIDC) and get their Tahiru role from their directory groups. Tahiru never sees their passwords. Owners set it up on Access, Single sign-on.
Ask Tahiru support to connect your directory. They give you the connection name. On-premises AD or LDAP uses a small connector inside your network that makes outbound connections only.
Enter the directory and connection name.
Add your email domains and publish the TXT record shown for each (_tahiru-verification.<domain>), then press Verify.
Map directory groups to roles, for example NOC-Admins to Admin, or Dallas-Ops to Operator on the Dallas site. Groups can grant any role except Owner.
Turn single sign-on on. To require it, choose one to five break-glass owners who can still sign in without the directory.
Removing someone from every mapped group removes their access at their next sign-in.
Investigations, workflows and audit
Open an investigation and add evidence
An investigation gathers the devices, logs and files for a problem.
Investigations, Open a case (or Open a case on a device). Describe the problem, its priority and when it started, and add the devices.
Add evidence: collect logs and tech supports from the devices, or upload files. Files are stored encrypted and scanned for known problems on Gold and Platinum devices.
Follow the timeline. On Platinum devices a Tahiru engineer works the investigation with you in the conversation panel.
Workflows and the audit log
Every change and action is a workflow you can follow; who did what is in the audit log.
Workflows (top right, or the side menu) lists every action with its steps: running, succeeded or failed. A failed step shows a code; press it for the fix.
Audit log (owners and admins) records who changed what and when. Secrets, names and free text never enter it.
Supported hardware
Supported hardware and software
What Tahiru reads today, by how it reaches the device.
In Tahiru, add an SNMP v3 credential with the same user, security level authPriv, and the same protocols and passphrases.
Prepare a login for configuration backups
Backups run show running-config over SSH, so the account needs that right.
Cisco IOS and IOS-XE: an account at privilege 15, or a lower privilege plus the enable password in the credential (CLI enable password).
username tahiru privilege 15 secret <password>
Make sure SSH is enabled and reachable from the collector. On first contact Tahiru pins the device's SSH host key; a changed key stops backups until you trust it again on the device's Backups tab.
In Tahiru, add a Device login with the account, then assign a backup policy to the devices.
Create a read-only Redfish user on a server
Servers are read through their management controller (CIMC, iDRAC, iLO, XClarity).
In the controller's web page, open user management and create a local user with the read-only role (Read Only, Operator or ReadOnly, depending on the vendor).
Make sure Redfish (HTTPS) is enabled on the controller.
In Tahiru, add a Device login with that user. The first time, confirm the controller's certificate when asked; Tahiru then uses the credential only while the certificate matches.
Send syslog to the collector
Tahiru keeps 30 days of syslog and turns critical messages into faults.
Find the collector's address on the site's Syslog section.
Cisco IOS and IOS-XE:
logging host <collector-ip>
logging trap warnings
Other devices: send syslog to the collector's address on UDP 514. Messages are matched to the device by its address.
Technotes
Technote: open a case with a Tahiru engineer
Something is wrong and you want a Tahiru engineer to work it with you. A case is an investigation; with Platinum, a Tahiru engineer who knows the issue works it with you.
From the device that has the problem, press Open a case at the top of its page. Or open Investigations in the side menu and press Open a case.
Screenshot: A device page with the Open a case button at the top right
Give the case a title and describe the problem: what you see, what changed, and what you have tried.
Screenshot: The case form: Title and Problem description
Optionally say when it started and what you need from us (a fix, a root cause, advice).
Screenshot: When did it start? and What do you need from us? fields
Choose a priority: P1 Critical (production down, no workaround), P2 High, P3 Medium or P4 Low.
Screenshot: The four priority choices, P1 to P4
Under Which devices?, choose the affected devices. Leave Collect logs now ticked so Tahiru gathers their logs straight away, or upload logs and files yourself.
Screenshot: Which devices? with a device chosen and Collect logs now ticked
Press Open case. The case gets a number (INV-…) and opens; the logs being collected appear under Files as they arrive.
Screenshot: A new case page with its number, Conversation and Files
Do not paste passwords or keys into a case. Device logins belong under Credentials, where they are encrypted.
Technote: reply to the engineer and chat while you work on the device
How to answer the engineer, keep the conversation in view while you look at the device, and add what they ask for.
Open the case from Investigations. The Conversation shows every message, newest at the bottom, and refreshes every few seconds.
Screenshot: The Conversation panel on a case page
Write your reply in the box under the conversation and press Send (or Ctrl+Enter).
Screenshot: The reply box and the Send button
To look at the device while you chat, press Open device with chat. The device opens with the conversation docked on the right; collapse it with the arrow, or open the full case with the link icon.
Screenshot: A device page with the case conversation docked on the right
Any device with an open case shows that case's conversation on the right by itself. Press Keep chat open (the pin) to keep it there on every page until you unpin it.
Screenshot: The pin button in the docked conversation
When the engineer asks for logs, add them under Files on the case: upload a file, or collect logs from the device page (Collect logs).
Screenshot: The Files panel with an upload in progress
Follow progress in the case's state (Open, In progress, Evidence collected, Resolved, Closed) and its timeline.
Screenshot: The case header showing its state, and the timeline
Technote: resolve, close or reopen a case
The problem is fixed, or you want to stop working a case.
When the fix works, set the case to Resolved with the state menu at the top of the case. The engineer may do this for you.
Screenshot: The state menu on a case set to Resolved
A resolved case stays open for replies. Set it to Closed when nothing more is needed; a closed case cannot take new messages.
Screenshot: A closed case with the reply box replaced by a note
If the problem comes back, open a new case and mention the old case number in the description.
Screenshot: A new case description mentioning an earlier INV number
Technote: let Tahiru support into your organization
Tahiru engineers open your organization with the Support role to work your cases. You control this and can see every visit.
Open Access in the side menu, then the Tahiru support tab. It shows whether Tahiru support can open your organization (on by default).
Screenshot: Access, Tahiru support tab, showing On
Owners can press Turn off or Turn on. Turning it off stops Tahiru engineers opening your organization, including for open cases.
Screenshot: The Turn off button and its confirmation
Every visit is in the Audit log as Tahiru support opened, and anything the engineer changes is recorded under their name.
Screenshot: The Audit log filtered to Tahiru support opened
Technote: download a collector version and check it
You need the collector installer, or a specific earlier version that Tahiru support asked for.
Open Downloads in the side menu. The latest version is at the top with its SHA-256; every earlier version is listed below with its release notes.
Screenshot: The Downloads page with the latest version and the version list
Press Download on the version you need. Expand a version to read its release notes and SHA-256.
Screenshot: An expanded version showing release notes and SHA-256
Check the file on the Windows machine before installing: compare the result with the SHA-256 on the Downloads page.
Installed collectors upgrade from Collectors without visiting the machine; download an installer only for a new collector or when support asks.
Screenshot: The Upgrade button on the Collectors page
Troubleshooting
Start here: check the collector
Anything looks wrong with a collector. Run these on the collector machine in PowerShell as Administrator (Start, type PowerShell, right-click, Run as administrator).
Collect the support bundle and send it to support. Go to guide
Collector shows No recent contact
The collector has not checked in for over 10 minutes. During an upgrade a short gap is normal and the status shows Upgrading instead.
Check the machine is on and awake, then run the check in "Start here".
If you see
Then
The machine was asleep or off
It checks in within 5 minutes of waking. Set the power plan so it never sleeps.
Heartbeat refused (401 or 403) in the log
The cloud refused the collector's certificate. Send the support bundle to support. Go to guide
The support bundle shows an unexpected TLS issuer
A proxy inspects TLS. Let the collector reach Tahiru on HTTPS 443 without interception.
Certificate expired or missing
The log repeats "Collector certificate pending or unavailable" and every heartbeat fails. Collectors before 0.1.59 did not renew their 24-hour certificate; 0.1.59 and later renew it themselves.
Set the expired certificate aside so the collector asks for a new one at start-up. Nothing is deleted.
Within a minute the log shows "Collector certificate acquired for approved machine"
Fixed. Upgrade the collector from the portal to 0.1.59 or later so it renews by itself.
Rename-Item says the file does not exist
Just start the service; it requests a certificate at start-up.
Start-Service TahiruCollector
Still "pending or unavailable" after 5 minutes
The collector may have been disabled in the portal, which revokes it. Check its state; a disabled collector must be paired again.
Running, but never checks in
The service runs and logs "Application started" (newer versions: "Cloud connection is off"), but the portal's Last seen does not move. An installer repair restored the files but not the service settings.
A Collector upgrade workflow failed at a step. Each step has a deadline, and the failed step shows a code. The collector keeps running its current version.
Check the updater task and what the collector staged.
The installer ran but the collector did not come back. Run "Start here" and read install.log in the newest C:\Windows\SystemTemp\TahiruUpdate-* folder. Go to guide
LastTaskResult 2
The task is not running as SYSTEM. Reinstall the collector by hand. Go to guide
The updater tries the same version again only after 6 hours. To retry at once:
For collectors older than 0.1.46 (no portal upgrade), or when a portal upgrade keeps failing. Do not press Disable to upgrade: it revokes the collector, which must then be paired again.
Download the installer (Collectors, Download installer). Browsers save repeats as TahiruCollector (1).msi, (2) and so on; this installs the newest file and keeps pairing and certificate.
A scan completes but finds no servers, or the collector page shows discovery errors.
On the site page, check the network is approved under Approved networks and the collector is assigned to the site, then press Scan now.
If you see
Then
job_refused
The job failed signature or scope checks. Contact support.
credential_unreadable
A credential was sealed to an earlier collector key. Delete it and add it again.
timeout
The scan ran over 90 minutes. Approve smaller networks, for example /24 blocks.
A server shows Needs a credential
It answered Redfish but no login worked. Add a read-only BMC login under Credentials; it is tried on the next scan.
A server shows Certificate changed
It presented a different certificate from the one first trusted. Confirm with the server owner, then Review certificate.
A monitored server is unreachable
The collector cannot read a server's management controller (BMC). The code says why.
Match the code on the collector or server page:
If you see
Then
connect_failed or network_error
No connection to the BMC on 443. Check routing and firewalls from the collector machine to the BMC.
timeout
The BMC did not answer in time. Check BMC load and the network path.
tls_error
The TLS handshake failed. Check the BMC's web interface certificate and TLS settings.
certificate_changed
A different certificate from the trusted one. Verify it, then review it in the portal.
auth_failed or http_403
The BMC refused the login. Fix the account on the BMC or replace the credential.
http_error, read_failed, invalid_response or invalid_document
The BMC answered unexpectedly. Send the support bundle. Go to guide
Pairing fails with a challenge or expiry error
The connect command stops with a challenge, expired or signature error.
Pairing allows 2 minutes of clock difference. Check and fix the clock, then create a new pairing code and run the connect command again.
w32tm /query /status; w32tm /resync
If you see
Then
signature_invalid, expired or wrong_collector persist
Create a fresh pairing code; codes work once and expire. If it repeats, send the support bundle. Go to guide
Send a support bundle
When nothing above fixes it. The bundle never contains keys, pairing codes or credentials, and is deleted after 30 days.
Connected collector (0.1.62 and later): on its page, open Support logs and press Collect logs. Within about 5 minutes the bundle is ready to download; follow it in Workflows.
Not connected: run this on the collector machine as Administrator, then on the collector page open Support logs, press Upload bundle and choose the zip from C:\Users\Public\Documents.