01 · Inventory
What certificates do we have?
Yesterday
Open each node's OS admin page and read the list.
Today with FRINK
Identity certificates and trust stores of every node, all clusters, one search.
Certificates
One expiring certificate.
Two ways to find out.
Today, certificates are listed once, at installation, in a file someone left behind. The first sign of expiry is Jabber refusing to log in on a Monday morning.
02 · Expiry
What expires next?
Yesterday
Sort a spreadsheet by a date column somebody typed.
Today with FRINK
Days to expiry in red / amber / green; self-signed and expired flagged.
03 · Impact
What breaks if it does?
Yesterday
Discover the dependency when the trunk goes down.
Today with FRINK
The Cisco service each certificate belongs to – CallManager, Tomcat, CAPF …
04 · Result
Renewed in a planned window
Yesterday
Monday-morning outage, two unrelated-looking symptoms.
Today with FRINK
Renewed in a planned window, 30 days ahead.
What changes
- NoticeYesterday: NoneToday with FRINK: 30 days
- InventoryYesterday: Per node, by handToday with FRINK: All nodes, one search
- Symptoms to correlateYesterday: Two or moreToday with FRINK: None
Worked example · Insight 08
Certificate about to expire on the SIP trunk
A CallManager certificate was flagged at 30 days, with its service named.
Read the full case- What certificates do we have?Certificate overview shows it amber at 30 days to expiry.
- What expires next?Sorted by days; node and service named.
- What breaks if it does?The certificate-expiry alert e-mails the team.
- Renewed in a planned windowRenewed in a planned window.