Noc

*Monitoring EPC, IMS, IP, TX alarms from Nokia-ALTAN network. MME, SAE, DRA, PCRF, TAS, SBC, HSS, HLR, ONE NDS, MNP, CFX, RTI, RDC, BFW, RPE, Apodaca-Monterrey and Tultitlan-Mexico equipments.

*Once an alarm is identified it is needed to open a case to start Tier I Trouble Shooting, if issue is fixed in First line, the ticket will be closed. If not possible, it needs to be sent to second/third level to a further investigation and find the root cause of the problem.
*Answer email requests from other areas as: ALTAN SIC/SOC, IP, TX, TIER II, MSCORE, IT operations, in order to open a ticket, make tests, Trouble Shootings, traces or check alarms.

*Monitor incoming/outgoing traffic for Network Laredo and McAllen via PRTG tool.

*Elaborate hourly reports, to have a quick status of the network and to identify possible issues in the network, if something is found not working as it has to be, a ticket needs to be opened and assign it to the team responsible for the equipment reporting issues.

*Run Health check to the elements in the Network to identify any problem in the equipment that is not reported in the alarms tool.

*Tools to monitor Network. IT Service Management (ITSM), Network Function Manager (NSP), Zabix, NetAct, Grafana, PRTG Sensors, Secure CRT, FileZila, WinSCP, Netchart, Mobax.

*Monitoring 5E, IPA, OMP Voice and Data for Alcatel-Lucent vendor (SPRINT Network).
Core equipment was monitored in this area, examples of this equipment: 5e, IPA, OMP, AAA. 
Lucent Core Tier I had the responsibility of monitoring the alarms and performance of the network Voice and Data services. To report any issue in the network like a switch blocking calls, dropping calls or even the entire switch not giving service, E911 issues in the network, TI´s down, Fiber cuts, natural disasters, In any kind of this issues a ticket was created to investigate the root cause.
The troubleshooting started checking Voice and Data performance, It was also needed to check the equipment like CCU, CU, MCTSI, RRH, Ports in the IPAs etc...

*The RAN side was also checked to verify if all BTS´s, NodeBs and eNodeBs belonging to the switch were having bad performance, or not giving service due to it could also affect the switch performance.
The MME, PGW, SGW were checked to discard issues in those equipments. It was possible to fix some issues in the Tier 1 team, If it was not possible, it was needed to engage some other teams responsible for other areas of the network to give a solution. Many times, it was needed to work together with the USA Engineers to fix the problem, The area also coordinates and engage all the people needed to give a solution. 
Most of the outages needed to be fixed immediately, if equipments needed to be replaced or a change in the configuration it was done during the night shift to not affect the user during the process. The maintenance windows were performed by the switch techs and together with the Tier I to monitor network during the procedure.

*Tools used to do the troubleshooting were: TRAMS, Netcool, Probe pages, Falcon, My Deviants, Secure CRT, Netwatch, REACT, Quickpad, Viper, RNC.

*Monitoring performance; CDMA, EVDO, LTE for Samsung, Nortel, and Lucent vendors (SPRINT Network).

*Base Transiver Station (BTS), NodeBs and eNodeBs were monitored in this area through alarms reported by the network. When issues occurred on the BTS´s (network Vision equipment & enodBs) like blocking calls, dropping calls, no service in one sector on in the entire BTS, The troubleshooting started investigating what was the issue causing this problem and to do this, a ticket was opened to register all the information found during the troubleshooting, The first thing to do was to access the radio base to run a diagnostic of performance to get what service was affected. Each radio base has 3 sectors giving service and one by one needed to be checked to see if a component of it was not working in the normal way, it sometimes could be reset or restored remotely and sometimes it did not work, in this case the ticket needed to be sent to the Second level due to they had more privileges to investigate further. The neighbors also had to be checked due to it could be the cause of a blocking or dropping issues.

It was also needed to investigate the T1s that could be down or having errors, the backbone, the Radio Network Controllers RNCs, the ports in the IPAs that could be affecting the network, fiber cuts, natural disasters, mass calling events, maintenance Windows.

*During the night shift it was common to have maintenance windows to add equipment, to modify configuration, to replace damage equipment and it was done remotely together with the switch tech  to have service under control.

*Tools used to do the troubleshooting were: TRAMS, Falcon, My Deviants, Secure CRT, CMC, Netwatch, REACT, Quickpad, Viper, Spirent.

*Monitoring performance; CDMA, EVDO, IDEN, Samsung, Nortel and Lucent Vendors (SPRINT Network). 

*Opening ticket to report issues in the Legacy Network (BTS), for example; blocking calls, dropping calls, mass calling events, rogue mobiles no service in the BTS or part of it (sectors), natural disasters. If issue was not able to be fixed remotely, it was needed to work together with the remote and physical techs in the USA, it was the work for the second level team. Ticket was not closed until issue had been fixed.

*Tools used to troubleshoot were: TRAMS, Falcon, My Deviants, Secure CRT, Netwatch, REACT, Quickpad.

Técnico Superior universitario en Telemáticas.