CybrIQ
  1. Home
  2. Products
  3. CrossCheck
CrossCheckFor whoever signs off the change window

The last firmware upgrade took the boardroom down.

CrossCheck rehearses the change on a model built from your own equipment. You get Go, Caution or No-Go before Saturday, with the device it is worried about and the reason.

Book a 30-minute working session How CrossCheck works
Before every change window
What it isWhat it needs before Saturday
When it runsSoftware, run before a change

It works on a model of your network and never changes a production device.

What it takes inYour inventory and the release notes

What you have, what version it is on, and what the vendor says the new one changes.

What it cannot doApply anything

CrossCheck is a preflight. It has no ability to install, stage or roll back a change.

Its ceilingIt caps at 60

If the current firmware version came from memory instead of the device, the verdict cannot score above 60.

The problemThe Saturday window

You find out on Monday whether Saturday worked.

The change goes in overnight. Nobody is in the rooms. The first real test is a board meeting on Monday morning, and by then the window has closed and the engineer has gone home.

The release notes list what changed in the firmware. They do not say what that means for the six devices you have that depend on it.

A pass needs 75. A verdict built on a version somebody remembered caps at 60, so it sends you to check the real one first.

What you seeThe verdict, before the window

Go, Caution or No-Go, and which device is the problem.

A CrossCheck verdict panel showing an overall score, a Go, Caution or No-Go result, the devices contributing to the score, and the specific reason each one was flagged.
One verdict, and the reason under it. The score, the devices that pulled it down, and what would raise it. CrossCheck<br>verdict
How it worksThree steps, all on paper

It rehearses the change on your own gear.

01It models what you have

From your own inventory: the devices, their versions, and how they depend on each other.

02It applies the change on paper

The proposed firmware, against that model, with the vendor release notes read as constraints.

03It returns a verdict with a score

Go, Caution or No-Go, the devices that decided it, and the specific thing that would change the answer.

The method behind CrossCheck
Where it stopsWhy it stops at 60

The most it will score on remembered data is 60.

Last time, a confident verdict on an assumed version took the boardroom down. Here is how the score goes up.

  1. 1
    Read the real versions off the devices

    This is the single biggest lift. A verdict on read versions can reach a pass; a verdict on remembered ones cannot, by design.

  2. 2
    Then close the dependency gaps

    It scores lower where it cannot see what depends on what. Tell it once, or let CrossConnect tell it.

  3. 3
    Then run it every window, including the quiet ones

    The changes you assumed were fine are the ones that take a room down.

What people askAsked by whoever signs the change

Does it apply the change?

Does it apply the change?

No. It is preflight only, with no way to install, stage or roll back anything.

What if it says No-Go and we go anyway?

That is your call, and sometimes it is the right one. The verdict is written to paste into the change record, so the decision is on file either way.

Where does the model come from?

Your own inventory. If you run CrossScan or CrossConnect it can take it from there. If not, it can be imported.

Does it need vendor release notes?

It uses them where it has them, and it tells you when it does not. A verdict without release notes scores lower and is marked that way.

CrossCheck and the other seven, in the FAQ

See it work

Two upgrades on Saturday. The verdict comes first.

The sample CrossCheck ships with: a Q-SYS Core going 9.8.0 to 9.9.0 and a Cisco Catalyst 9300 going 17.6.4 to 17.9.1, on a switch with IGMP snooping on and no querier. Build it, run the preflight, and read what comes back.

CrossCheck Demo data
1

Start here. You will collect two devices, pick the firmware you are moving to, run the preflight check by check, and read the verdict. About two minutes.

CrossCheck Preflight for AV upgrades Sample

Start a check

Loaded a sample environment. Run the preflight to see a verdict, or edit it.

Collect your devices

Capture it · confirmedFull marks. Nothing is held back for a thin model. Upload it · importedScores at four fifths. A file can be out of date. Type it · inferredScores at three fifths, so a clean pass is out of reach.

Devices (2)

qsys-core QSC Core 110f 9.8.0 to 9.9.0
av-switch Cisco Catalyst 9300 17.6.4 to 17.9.1

Read-only and advise-only. CrossCheck rehearses the change against a model of your gear. It never signs in to a device, changes a setting or applies firmware.

Sample data. Every verdict here was computed by CrossCheck from its own built-in sample environment, not from a reading of your equipment.

Where it leadsAfter the window

When the change still hurts a room

If a meeting goes badly after the change anyway, CrossRoom rebuilds the call and names the device.

CrossCheck next to the other seven
Next

CrossCheck hands you a Go or a No-Go for the change ticket, which is where CrossRoom picks up: “Why was that call so bad?”

Working sessionOne change window of yours

Bring one upcoming change window.

Bring the firmware change you are planning and a list of the gear it touches. In thirty minutes you see the verdict and the device that decided it.

Book a 30-minute working session Evaluate CrossCheck without a call