OpenText Cadence 03/05/2026

Meeting Participation and Attendance

• Unknown participants joining the call

• Participants include Marissa, Brad, Michelle, Steve, and Faiza

• Discussion about whether to wait for Steve to join the meeting

Initial Communication

• Greetings exchanged among participants

• Acknowledgment of waiting for Steve's arrival

Meeting Agenda

• Marissa confirms receiving an email; clarification on previous conversation

• Discussion on referencing ticket number for clarity and follow-ups

Status Updates on Project Tickets

• Presentation date: Thursday, March 5

• Ticket status: 9 Priority 2 (P2s), 9 Priority 3 (P3s), and 6 Priority 4 (P4s)

  • Percentages: 65% P2s, 63% P3s, 92% of tickets reported as good

  • Top site for alerts: Bangalore with 96 alerts and 4 open incidents

• Discussion on incident tickets related to various sites:

Ticket Summaries

Ticket 1595584

• Issue: Cable cut impacting latency at the Bangalore office

• Estimated Time of Repair (ETR): March 6 to 16

• Status: Under repair by the carrier team.

Ticket 5946 (Bangalore site)

• Issue: Recurring device offline issue

  • Awaiting Root Cause Analysis (RCA) confirmation from Palo Alto’s tech

  • Status awaiting freeze lift for version 6.53

Ticket 5593 (Provo site)

• Status: Replacement confirmed but awaiting freeze lift on version 6.53 for implementation

Ticket 1837 (Osaka location)

• Ongoing investigation into recurring service link tunnel flaps

  • Escalated to senior engineers of Palo Alto

Ticket 1019 (Quela site)

• Scheduled troubleshooting call for Teams connectivity issues on March 10

  • MTU related packet drop issues affecting Teams live events

Ticket 0860 (MAC flapping issue)

• Issue: MAC flapping conditions persist

  • Investigated by Palo Alto tech for root cause isolation

Further Incidents

• Discussion on ticket 5284 relating to Tokyo Data Center’s service link stability

• Ticket 0972 (Waterloo) reported ongoing six five three routing faults

• Ticket 7387 (Cambridge) mentioning multiple split-brain events due to a known bug

Review of Performance Data

• Discussion on uptime and packet loss monitoring

  • Finding: Overall performance is stable with a minor dip in Temperi Latham location

• Data transfer metrics presented, with the highest usage noted for hybrid hydrant office and data center

Upcoming Training and Follow-Up Tasks

• Training needed for OpenText new hires on the z insight portal

• Need to coordinate an upcoming upgrade and renewal discussions

  • Continuous follow-up with sales teams on completed tasks

• Addressing delays in change orders

Action Items

• Follow up on training schedules for OpenText

• Ensure change orders are processed in a timely manner

• Keep checking on shipping labels needed for returns

End of Meeting Discussion

• Invite confirmations for upcoming meetings

• Expressing gratitude and confirming attendance for future discussions

• Closing remarks made by participants before concluding the meeting.

Overall Summary and Notes

• Full discussion around enhancement of communication protocols and ticket management practices

• Need for timely follow-ups and clarification on project responsibilities among team members

• Ongoing efforts to consolidate training processes for better knowledge transfer among teams.

Meeting Participation and Attendance

• Participants included Marissa, Brad, Michelle, Steve, and Faiza with an introductory discussion item focused on unknown participants potentially joining the call. This raised concerns about the nature of the meeting and the need for clarity regarding attendance.

• The group deliberated on whether to delay the meeting for Steve's arrival, considering his critical role in the ongoing projects. Consensus was reached swiftly that some initial topics could be commenced while awaiting his attendance.

Initial Communication

• Greetings were dynamically exchanged among participants, setting a positive and collaborative tone for the meeting.

• The participants collectively acknowledged the necessity of waiting for Steve's arrival to ensure he is included in crucial discussions that would impact project direction.

Meeting Agenda

• Marissa confirmed receipt of an important email, prompting a conversation to clarify points from a previous discussion on key initiatives.

• The group emphasized the importance of referencing ticket numbers during conversations for accurate follow-ups and transparency. This discussion highlighted the need for a streamlined communication process to minimize misunderstandings.

Status Updates on Project Tickets

• The upcoming presentation date was set for Thursday, March 5, marking a pivotal milestone for project updates.

• Current ticket status reported included: 9 Priority 2 (P2) tickets, 9 Priority 3 (P3) tickets, and 6 Priority 4 (P4) tickets.

  • Percentages reported: 65% for P2s, 63% for P3s, and a notable 92% of all tickets categorized as 'good' status, indicating effective resolution.

  • The team identified the top site for alerts as Bangalore, recording 96 alerts and 4 open incidents that require urgent attention.

• The discussion transitioned to focus on various incident tickets, addressing emergent issues and the allocation of resources:

Ticket Summaries

Ticket 1595584

• Issue: A significant cable cut impacting latency was reported at the Bangalore office, leading to escalated performance issues.

• Estimated Time of Repair (ETR): Set between March 6 to March 16, effectively communicated by the carrier team to manage expectations.

• Status: The issue is currently under active repair, with updates expected from the carrier team.

Ticket 5946 (Bangalore site)

• Issue: A recurring device offline issue that has persisted over several weeks.

  • The team is currently awaiting Root Cause Analysis (RCA) confirmation from Palo Alto’s technical team to determine the origin of the issue.

  • The status remains pending due to a freeze on system updates for version 6.53, necessitating further discussions.

Ticket 5593 (Provo site)

• Status: Replacement has been confirmed but is also awaiting a freeze lift for version 6.53 to facilitate implementation smoothly.

Ticket 1837 (Osaka location)

• An ongoing investigation has been initiated into recurring service link tunnel flaps, highlighting the need for stable service connections.

  • This issue has been escalated to senior engineers from Palo Alto due to its complexity and impact on service delivery.

Ticket 1019 (Quela site)

• A troubleshooting call is scheduled for March 10 to address persistent connectivity issues affecting Teams-related activities.

  • The issues have been attributed to MTU-related packet drops, particularly impacting Teams live events and overall communication efficiency.

Ticket 0860 (MAC flapping issue)

• Issue: Persistent MAC flapping conditions affecting network stability, currently under investigation.

  • The Palo Alto technical team is engaged for root cause isolation to mitigate future occurrences efficiently.

Further Incidents

• During further discussions, ticket 5284 was highlighted, which concerns the Tokyo Data Center’s ongoing service link stability and reliability.

• Ticket 0972 (Waterloo) reported problematic routing faults, notably six five three errors affecting service reliability.

• Ticket 7387 (Cambridge) outlined multiple split-brain events attributed to a known bug in the system, necessitating immediate remediation steps.

Review of Performance Data

• The panel reviewed uptime and packet loss metrics, noting that overall performance remains stable with a minor dip reported in the Temperi Latham location towards the beginning of the week.

• Detailed data transfer metrics were presented, revealing the hybrid hydrant office and data center exhibiting the highest usage patterns, further necessitating resource allocation review.

Upcoming Training and Follow-Up Tasks

• The need for targeted training sessions was emphasized for OpenText new hires to navigate the z insight portal efficiently.

• Coordination for an upcoming system upgrade and renewal discussions was noted as a high priority, particularly concerning resource allocation.

  • The team was encouraged to maintain continuous follow-up with sales teams to ensure completed tasks are well-tracked and adequately documented.

• Acknowledgment of delays in processing change orders raised concerns about accountability and timely execution.

Action Items

• It was decided that action items would include: Follow up on training schedules and other educational opportunities for OpenText users.

• Ensure that change orders are processed in a timely and efficient manner to minimize disruptions in operations.

• Ongoing checks are needed on shipping labels necessary for any potential returns from the current equipment configurations.

End of Meeting Discussion

• Participants confirmed invitations for upcoming meetings and expressed gratitude for everyone's contributions and inputs during this meeting.

• Attendance for future discussions was confirmed, ensuring continued collaboration.

• Closing remarks made by participants served to reinforce the need for clear communication and unity of purpose moving forward.

Overall Summary and Notes

• The meeting encompassed a thorough discussion centered on enhancing communication protocols and ticket management practices, confirming the group's commitment to efficiency and transparency.

• There remains an acute need for timely follow-ups and clarity on project responsibilities among team members to enhance productivity.

• Ongoing efforts to consolidate training processes and create more effective knowledge transfer mechanisms among teams were underscored as essential in building a stronger organizational framework.