Difficulties With NEC Equipement
Difficulties With NEC Equipement
Difficulties With NEC Equipement
Impact: This feature is not available in NEC equipment/NMS system. Whenever any 2G/3G service is down, there is no option to find the E2E path of the
impacted service. Its also like a blind situation and it takes long time to recover the service.
Consequence: Long time service outage and it hits network availability.
NEC Comment: No roadmap shared yet.
Impact: When any NE becomes offline, there is no way to reroute the DCC routes of the offline NE’s despite of having alternate route with the same GNE
or another GNE. In some cases, the issue becomes critical when one NE lost its connection with the NMS while performing any modification activities
and no reroute is possible. Site intervention was required and it takes long time to restore the service.
Consequence: Long time service outage and it hits network availability.
NEC Comment: No roadmap shared yet.
Impact: When VLAN loop occur, there is no option to check which VLAN is actually creating the loop. Also there is no alarms triggers for VLAN loop. Its
also like a disastrous situation and it takes long time to recover the service.
Consequence: Long time service outage and it hits network availability.
NEC Comment: No roadmap shared yet.
NEC issues
Feature: License pooling
Impact: A default license is mapped in each Modem. Everytime when the link needs to be upgraded, license also need to be downloaded to that
corresponding Modem. It makes delay in total work progress. In addition a new server(SKA Server) required just to export license from server to NE.
Consequence: Man-hour lost and increases CAPEX.
NEC Comment: No roadmap shared yet.
Impact: No direct option to monitor real time historical BW utilization trend for individual link.PM data is available in Octet format. Manual
intervention/XL operation is required to manipulate the PM data for getting the % of BW utilization.
Consequence: Huge Man hour lost, difficult to identify BW congested links.
NEC Comment: No roadmap shared yet.
Impact: There is no alarm in NEC radio that will indicate that utilization exceeds the designed BW. So preemptive measure cannot be taken before
service is impacted.
Consequence: Network KPI impacted.
NEC Comment: No roadmap shared yet.
NEC issues
Feature: Dynamic MAC learning
Impact: No such feature in NEC PNMS/UNMS system to see MAC learned dynamically from upstream/downstream interfaces. There is FDB table in NEC MW
radio but it needs to be downloaded everytime to see the learned MAC address. It can not be used for E2E checking and troubleshooting purposes of IP traffic.
Consequence: Long time service outage and it hits network availability.
NEC Comment: No roadmap shared yet.
Impact: No such feature in NEC PNMS/UNMS system. No option to check optical RSL from MW radio. Troubleshooting becomes difficult.
Consequence: Long time service outage and it hits network availability.
NEC Comment: No roadmap shared yet.
Cascading problem
Impact: Still in many nodes, there are cascading among NEC radios and NEC GUI system is unable to show the properties/traffic status of the cascading
interfaces . It makes service commissioning and troubleshooting much more difficult and time consuming.
Consequence: Man hour lost, long time service outage and it hits network availability.
NEC Comment: No roadmap shared yet.
NEC issues
Feature: GUI not support to configure bunch of VLAN
Impact: No option in current GUI to input bunch of VLANs in Modem/Eth port interfaces simultaneously. VLAN has to be created first and then added
one by one in the interfaces. It costs huge time/Man hour to provision a particular service.
Consequence: Man hour lost
NEC Comment: No roadmap shared yet.
Comment:
In a summery, the equipment lacks of very common basic features to operate 3G/LTE services. Moreover it is not user friendly at all and creating
hazards for engineers for daily operation/maintenance/troubleshooting purposes.
Thank you