OpenText Cadence 04/02/2026
Meeting Start
Introduction and gathering the team.
Speaker checks in to see if the team is present.
Shares screen for the meeting.
Personal Health Update
Speaker mentions recovery after a recent illness.
Hopeful about team progress during their absence.
Acknowledges upgrades were implemented successfully.
Ticket Overview
Total number of tickets: 16
Breakdown: 8 P2 (Priority 2), 5 P3 (Priority 3), 5 P4 (Priority 4).
High alert from different locations:
Rentback Location: One incident reported, handled successfully.
Johannesburg Location: 154 alerts reported, all types of alerts included.
Incidents Hosted by Site
Data Center Tokyo: 5 incidents in the last 7 days.
Johannesburg Location: Remaining incidents details still pending record.
Ticket Updates
Osaka Location (INC1591837):
Change freeze is in effect; updates on the ticket will proceed after it is lifted.
Issue identified as "ton of flash persists due to both hubs acting as interior."
Next step: Apply passive mode fix post change freeze.
Current Status: Pending Tier 3 confirmation.
Waterloo Location (INC1610982):
Traffic issues post upgrades to version 6.5.3b5 due to instability.
Next steps include awaiting customer confirmation and gathering the team call quality matrix after testing.
Other Waterloo ticket: Nine seven two post upgrade behavior stable but unconfirmed; waiting for validation of traffic patterns and BGP advertisement anomalies.
Bangalore Office: Latency issues tied to subsea cable repairs.
Next step: Monitoring carrier for updates and requesting alternative routing if ETR slips.
GP Client Issue: Client is stuck at retrieval portal configuration.
Next steps: Collect policy logs and timestamps of failures for escalation to Tier 3.
Ashburn Location (INC1631100): Users unable to reach LAN while connected through GP.
Next step: Schedule a live TCP dump session and gather logs.
Hoof Ferdorp Location: Issues arose after a reboot; waiting for a Vendor update.
Complete Root Cause Analysis (RCA) and validate failover behavior before the next maintenance window.
Cologne Location: Sporadic packet loss reported by customer but Zayo/Ion testing shows 0% loss.
Next step: Waiting for ping evidence during the next occurrence to compare timestamps.
Johannesburg (INC33630): Primary DIA on Internet 1 is hard down; unable to ping the ISP gateway.
Update: Engaging local carrier for last-mile repair; the secondary DIA is operational.
Dubai Location (INC1633222): Primary and secondary DIA tunnels up, but backup links down.
Current status: Engaged the carrier team, awaiting updates.
Milan Location: WAN to gateway is unreachable; secondary circuit shows 100% packet loss.
Tier 1 team is currently investigating.
Huffendorf (INC1633769): An issue reported with the SD WAN; waiting for site address help for the carrier ticket.
Packet Loss and Performance Overview
Overall uptime is good; no significant dips reported.
Pre and post-QOL performance metrics reflect stable conditions.
Bengaluru location showed minor performance dip, which is being monitored by the SME.
Total Data Transfer (TDTs)
Data transfer metrics show strengths in several locations:
High Red Badge Location, Provo, Brook Park receiving special mention for traffic management.
Escalation and Collaboration Updates
Speaker notes successful escalation of previous tickets during their absence.
Opening the floor for questions regarding the current status or pending action items.
Action Items Review
Review of past action items from Tuesday’s meeting concluded nothing has changed.
Forthcoming meetings scheduled for necessary approvals, anticipated for the twenty-first.
Miscellaneous Queries
Inquiry regarding issues at the Dubai location, focusing on Internet circuits' operation and the BGP issue indicating problems with Prisma access.
Members confirm ticket status and awaiting further investigation on the matter by the technical team.
Meeting Wrap-Up
Acknowledgements and well-wishes for the weekend.
Looking forward to further updates and follow-ups on Monday's call.