Skip to main content

Posts

Transform

  Transforming Our Global Application Support Team Embracing the Future of Support We're embarking on an exciting journey to transform our global application support team into a world-class organization. Over the next few years, we'll be implementing a new framework designed to enhance our capabilities, streamline processes, and elevate the overall support experience. As we progress and grow, this framework will gradually be integrated into our operations, creating an awesome Application Support organization that empowers our team and delivers exceptional value to our customers. Stay tuned for more updates as we unveil the details of this transformative initiative! As we embark on this journey, we will gradually implement a new framework that will optimize our processes, enhance our skills, and elevate our overall service delivery. The following pages will be evolving but it is the start of the process.
Recent posts

vCenter Overview

  Overview: This MOP outlines the general steps involved in patching a vCenter environment. It's important to note that this is a high-level guide, and specific procedures may vary depending on the customer's unique environment and configuration. Key Considerations: Environment Uniqueness: The customer's vCenter environment may have specific configurations or dependencies that are not reflected in this generic MOP. It's crucial to proceed with caution and adapt the steps as needed. VMware Environment Access: Since we do not have direct access to the customer's VMware environment, it's essential to coordinate closely with their IT team to ensure accurate information and avoid potential issues.

Closure

Closure Criteria: Issue Resolved : The underlying problem has been successfully resolved. Workaround Provided : A temporary solution has been provided, and the user has been informed of the permanent resolution timeline. Issue is Deferred : The customer has agreed to defer resolution to a future release or update. Additional Considerations: Knowledge Base Update : If applicable, the resolution should be documented in the knowledge base for future reference. Follow-up : If necessary, schedule a follow-up ticket to ensure the resolution is holding. Escalation : If the issue cannot be resolved, escalate to BES team.

User Guide

  Subject: RE: Your Inquiry Regarding the User Guide and SSL Issue Dear [Customer Name], Thank you for reaching out to us regarding the user guide and SSL issue. I understand your concerns and appreciate you taking the time to report them. I will be reviewing the user guide and SSL issue thoroughly to determine the best course of action. I will provide you with a comprehensive update as soon as possible. In the meantime, please feel free to contact me if you have any further questions or require additional assistance. Sincerely, [Your Name] [Your Position] [Company Name]

M32

  Subject: Update on Pending Delete Intereps and Grafana Issue – Good Day.  Just wanted to send a quick update on the Invalid Interceptions "stuck" in Pending Delete. We worked with our colleague to successfully reproduce the scenario in our internal Reference environment.  The issue is that an Invalid formatted Interception can sometimes be accepted by the TSS (using Curl or Swagger). This is passed through the TSS > Filter Provider TSS, and distributed to the Modules. By the time that gets to the ETSI X1/X23 modules, they correctly identify the Invalid Filter Criterion and respond with 30002 Invalid Criterion Feedback Code. At this point, the intercept will sit in Interceptions Not Active, which can also seen in Grafana on the Inactive Filters (main) dashboard, and when using the GET Target Feedbacks by Filter ID. Upon attempting to DELETE the Invalid Intercept, the module is then unable to delete the invalid interception without a restart of the module, thus leaving...

Cert Info

  If customer is saying all the certs are showing the correct ones, maybe the error message is valid.  And based on this page   http://curl.haxx.se/docs/sslcerts.html , which is outlined in the error message, maybe the cert used with curl is out of sync.  (i.e. If curl was built with Schannel or Secure Transport support, then curl uses the system native CA store for verification . All other TLS libraries use a file based CA store by default. )   A process of copying your certificates inside /etc/pki/ca-trust/source/anchors/ then running the following command “update-ca-trust”, may help the issue along.    We don’t have access to prod so I did a comparison in lab and the certis in /etc/pki/ca-trust/source/anchors/ seem to be updated and it doesn’t get the error.    Some things researched or to check on prod maybe: not sure if it was done already but following the error message….. The error seems to say it has accessed the NSS ...

JIRA 2

  Jira Ticket Description Brief Troubleshoot Ericsson SMF communication failure to far-end endpoint resulting in disconnections. Technical Detail Summary Investigate and resolve an issue where the Ericsson SMF is experiencing communication failures to a far-end endpoint, leading to service disconnections. This includes: Analyzing SMF logs for error messages and patterns. Verifying network connectivity to the far-end endpoint. Checking SMF configuration parameters related to the far-end endpoint. Testing SMF functionality with relevant tools and scripts. Coordinating with network and application teams for troubleshooting. Extra Information (Possible Breakdown) To provide a more detailed understanding of the issue, please include the following information: Specific error messages or codes encountered. Affected services or users. Timeline of the issue (when it started, frequency, duration). Recent changes to the SMF or network configuration. Any relevant network diagrams or...