Gobu Sam’s Post

Senior Engineer Service Delivery Network Job Description Key AccountabilitiesProvide the needed-on time support and troubleshooting for all issues happens in all domains, since connectivity provided through IP.Do the needful escalation and involve vendors on time affecting manner in case of need, and ensuring adequate follow up and problem resolution within contracted SLAs.Performing periodic analysis of performance reports and observations to proactively prevent issues from occurringOverall responsibility that periodic reviews of devices configuration to remove any wrong or unneeded configuration are doneMeeting with service owners as customers to understand their problems and giving proper response for their queries.Handling daily Trouble Tickets as per du operation policies and scope of work.Oversee the provisioning of periodic and ad-hoc reports to planning team to help in the capacity planning and future upgrades of service delivery platforms and Data-Centers network.Providing the needed update for RFO – Reason for outage (if any)/following up all recommendation to avoid re-occurrence of similar faults till it take place.Assisting different planning teams/Acceptance Team in all Network Nodes Integrations, propose/attend ATP to assure redundancy, symmetry and best ways of integration are used.Maintains an up-to-date documentation/diagrams of the existing devices/solutions to help in troubleshooting issues and share them with other technical teams if requiredWork closely with planning team(s) on capacity planning, upgrades, and design issues related to existing solutionsPerform periodic health checks, preventive maintenance service delivery platforms and Data Centers network to identify potential problems or loopholes, and testing the redundancy.Ensure that all network elements and support systems are appropriately redundant and backed up in accordance with agreed policies wherever applicable.Implement patches and updates of the service delivery platforms and Data-Centers network devices to resolve any existing/potential bugs or performance issues.Review all the documentation presented by either vendors or Network Development for any new network elements or technologies introduced into the network.Ensure consistency of network configuration and configuration databasePrioritize & ensure the execution of performance, preventive maintenance related issues as the owner of the platformCoordinate with acceptance for all the changes in the network and ensure that the knowledge base is updated. Ensure monitoring and analysis of vendor performance as well as managing the vendor relationship together with the Vendor Management Organization·      Develop technical reports and documentation·      Work on any network disasters, prepare and implement alternative plans and finally restore network to deliver specified service levels. ·      Support all efforts for releasing DR run-books in order to allow for successful servic

This is a great steps by steps guide .

Step-by-step process to troubleshoot routing and switching issues in networks for network engineer: 1. **Gather Information:** - Understand the reported problem. - Collect network diagrams, configurations, and any recent changes. 2. **Physical Layer Check:** - Verify cable connections, interfaces, and physical components. - Ensure devices are powered on and functioning. 3. **Basic Connectivity Tests:** - Use tools like `ping`, `traceroute`, or `arp` to test connectivity between devices. - Check for connectivity issues between specific network segments. 4. **Check Device Configurations:** - Verify device configurations for routing tables, VLAN settings, access control lists (ACLs), etc. - Look for any misconfigurations or inconsistencies. 5. **Routing Protocols:** - Verify if routing protocols (OSPF, BGP, etc.) are correctly configured and neighbors are established. - Check routing tables for correct information and route advertisements. 6. **Switching Configuration:** - Review VLAN configurations, spanning-tree settings, and port configurations. - Ensure proper VLAN tagging and trunking between switches. 7. **Traffic Analysis:** - Use network monitoring tools to analyze traffic patterns, identify bottlenecks, or anomalies. - Look for excessive broadcasts, collisions, or errors. 8. **Hardware Diagnostics:** - Check hardware health using device-specific diagnostic commands. - Look for hardware-related errors or failures in logs. 9. **Firmware/Software Updates:** - Ensure devices are running the latest firmware/software versions to address known bugs or issues. 10. **Isolation Testing:** - Temporarily isolate segments or devices to narrow down the problematic area. - Verify if the problem persists within the isolated segment. 11. **Collaboration and Documentation:** - Collaborate with colleagues or vendor support if needed. - Document each step taken, changes made, and their effects. 12. **Implement Solutions:** - Apply fixes or configuration changes based on identified issues. - Test to confirm that the problem has been resolved. 13. **Monitor and Follow-up:** - Monitor the network after changes to ensure stability and functionality. - Follow up with users or stakeholders to confirm resolution. #troubleshooting #routingandswitching #ccna #ccnp #networkengineer

Tangent International urgently looking for Nokia CS TL: Location: Africa Please send your CV to: ying.cui@tanint.com Required personal data and working knowledge: - NOC/GNOC operation experience is a must - Operation, maintenance, troubleshooting and configuration of CS core network nodes (such as MSC, HLR, VLR, MSS, HSS, MGW, GMSC, STP, DRA, IMS) - Media processing, transcoding, call modeling CS, SMS, MMS and knowledge of MGW is required. - SPS-Diameter, SS7 message filtering/filtering based on message classes in CAP, MAP Diameter protocols - Concepts of all call flows, attach, detach, registration (2G, 3G and Volte) etc. - Basic IP knowledge working at Layer 2 level. - Black and white network entities and their interfaces in protocols - Evolving architecture - DNS query Products: Nokia CS devices Responsibilities: - Resolve trouble tickets raised by NOC/Customer/LNOC teams - Perform fault management for all network elements and provide follow-up - Implement network changes according to CR process - Capacity management and reporting in case of possible capacity breaches - Liaise with third party vendors/suppliers to resolve faults/issues requiring vendor support - Verify and maintain the Known Error Database (KEDB) of data communication nodes - Determine the root cause and recommend appropriate resolution actions for Priority 1 and Priority 2 incidents as well as other incidents determined by the customer to require Root Cause Analysis (RCA). - Integrated configuration (for example: VOLTE interconnection, roaming Volte solution support, new TUB vUSN integration with core nodes, SPS version upgrade delivered by ROT project, etc.) - Scam number/IMEI blocking, new APN/static IP configuration, international traffic routing policy changes. - New enterprise SIP interconnect configurations, network node upgrades, traffic shifting and balancing. - Complaint Handling (Customer, CC, Roaming and Internal Upgrades), Network Utilization Report, STP Link Load Report, Volte User Trend Report/Chart Analysis, Hardware Utilization Report Analysis. - CN license application, license renewal, license capacity monitoring and forecasting, customer interface/communication, weekly database backup checks, handling new requirements from customers, KPI/network quality improvement/optimization. - Weekly operational planning, major operational reviews/solutions/risks/script validations, remediation/prevention checks and iSite updates, contingency plans, topology updates, remote access and emergency defenses and drills. - Disaster recovery planning and reporting, change operation execution, spare parts management/updates. - Support customers with network security audits/vulnerability remediation, policy compliance/ad hoc requests.

Tangent International urgently looking for Nokia CS TL: Location: Africa Please send your CV to: ying.cui@tanint.com Required personal data and working knowledge: - NOC/GNOC operation experience is a must - Operation, maintenance, troubleshooting and configuration of CS core network nodes (such as MSC, HLR, VLR, MSS, HSS, MGW, GMSC, STP, DRA, IMS) - Media processing, transcoding, call modeling CS, SMS, MMS and knowledge of MGW is required. - SPS-Diameter, SS7 message filtering/filtering based on message classes in CAP, MAP Diameter protocols - Concepts of all call flows, attach, detach, registration (2G, 3G and Volte) etc. - Basic IP knowledge working at Layer 2 level. - Black and white network entities and their interfaces in protocols - Evolving architecture - DNS query Products: Nokia CS devices Responsibilities: - Resolve trouble tickets raised by NOC/Customer/LNOC teams - Perform fault management for all network elements and provide follow-up - Implement network changes according to CR process - Capacity management and reporting in case of possible capacity breaches - Liaise with third party vendors/suppliers to resolve faults/issues requiring vendor support - Verify and maintain the Known Error Database (KEDB) of data communication nodes - Determine the root cause and recommend appropriate resolution actions for Priority 1 and Priority 2 incidents as well as other incidents determined by the customer to require Root Cause Analysis (RCA). - Integrated configuration (for example: VOLTE interconnection, roaming Volte solution support, new TUB vUSN integration with core nodes, SPS version upgrade delivered by ROT project, etc.) - Scam number/IMEI blocking, new APN/static IP configuration, international traffic routing policy changes. - New enterprise SIP interconnect configurations, network node upgrades, traffic shifting and balancing. - Complaint Handling (Customer, CC, Roaming and Internal Upgrades), Network Utilization Report, STP Link Load Report, Volte User Trend Report/Chart Analysis, Hardware Utilization Report Analysis. - CN license application, license renewal, license capacity monitoring and forecasting, customer interface/communication, weekly database backup checks, handling new requirements from customers, KPI/network quality improvement/optimization. - Weekly operational planning, major operational reviews/solutions/risks/script validations, remediation/prevention checks and iSite updates, contingency plans, topology updates, remote access and emergency defenses and drills. - Disaster recovery planning and reporting, change operation execution, spare parts management/updates. - Support customers with network security audits/vulnerability remediation, policy compliance/ad hoc requests.

Step-by-step process to troubleshoot routing and switching issues in networks for network engineer: 1. **Gather Information:** - Understand the reported problem. - Collect network diagrams, configurations, and any recent changes. 2. **Physical Layer Check:** - Verify cable connections, interfaces, and physical components. - Ensure devices are powered on and functioning. 3. **Basic Connectivity Tests:** - Use tools like `ping`, `traceroute`, or `arp` to test connectivity between devices. - Check for connectivity issues between specific network segments. 4. **Check Device Configurations:** - Verify device configurations for routing tables, VLAN settings, access control lists (ACLs), etc. - Look for any misconfigurations or inconsistencies. 5. **Routing Protocols:** - Verify if routing protocols (OSPF, BGP, etc.) are correctly configured and neighbors are established. - Check routing tables for correct information and route advertisements. 6. **Switching Configuration:** - Review VLAN configurations, spanning-tree settings, and port configurations. - Ensure proper VLAN tagging and trunking between switches. 7. **Traffic Analysis:** - Use network monitoring tools to analyze traffic patterns, identify bottlenecks, or anomalies. - Look for excessive broadcasts, collisions, or errors. 8. **Hardware Diagnostics:** - Check hardware health using device-specific diagnostic commands. - Look for hardware-related errors or failures in logs. 9. **Firmware/Software Updates:** - Ensure devices are running the latest firmware/software versions to address known bugs or issues. 10. **Isolation Testing:** - Temporarily isolate segments or devices to narrow down the problematic area. - Verify if the problem persists within the isolated segment. 11. **Collaboration and Documentation:** - Collaborate with colleagues or vendor support if needed. - Document each step taken, changes made, and their effects. 12. **Implement Solutions:** - Apply fixes or configuration changes based on identified issues. - Test to confirm that the problem has been resolved. 13. **Monitor and Follow-up:** - Monitor the network after changes to ensure stability and functionality. - Follow up with users or stakeholders to confirm resolution. #troubleshooting #routingandswitching #ccna #ccnp #networkengineer

Step-by-step process to troubleshoot routing and switching issues in networks for network engineer: 1. **Gather Information:** - Understand the reported problem. - Collect network diagrams, configurations, and any recent changes. 2. **Physical Layer Check:** - Verify cable connections, interfaces, and physical components. - Ensure devices are powered on and functioning. 3. **Basic Connectivity Tests:** - Use tools like `ping`, `traceroute`, or `arp` to test connectivity between devices. - Check for connectivity issues between specific network segments. 4. **Check Device Configurations:** - Verify device configurations for routing tables, VLAN settings, access control lists (ACLs), etc. - Look for any misconfigurations or inconsistencies. 5. **Routing Protocols:** - Verify if routing protocols (OSPF, BGP, etc.) are correctly configured and neighbors are established. - Check routing tables for correct information and route advertisements. 6. **Switching Configuration:** - Review VLAN configurations, spanning-tree settings, and port configurations. - Ensure proper VLAN tagging and trunking between switches. 7. **Traffic Analysis:** - Use network monitoring tools to analyze traffic patterns, identify bottlenecks, or anomalies. - Look for excessive broadcasts, collisions, or errors. 8. **Hardware Diagnostics:** - Check hardware health using device-specific diagnostic commands. - Look for hardware-related errors or failures in logs. 9. **Firmware/Software Updates:** - Ensure devices are running the latest firmware/software versions to address known bugs or issues. 10. **Isolation Testing:** - Temporarily isolate segments or devices to narrow down the problematic area. - Verify if the problem persists within the isolated segment. 11. **Collaboration and Documentation:** - Collaborate with colleagues or vendor support if needed. - Document each step taken, changes made, and their effects. 12. **Implement Solutions:** - Apply fixes or configuration changes based on identified issues. - Test to confirm that the problem has been resolved. 13. **Monitor and Follow-up:** - Monitor the network after changes to ensure stability and functionality. - Follow up with users or stakeholders to confirm resolution. #troubleshooting #routingandswitching #ccna #ccnp #networkengineer