You are on page 1of 10

S.

No Items Issues
1 TX Nodes Visibility 1.We have only 21 % which is 489 node count out of 2185
nodes visibility of Ericsson TX nodes .
2. We only have View writes .

2 Alarm clearance drive 1.Will are unable to fetch alarms & performance reports due E

RSL improvement Plan 1. Planning to share the MW network link budget


2.We are not getting any performance reports of Ericsson &
Sagem due to DCN instability and for unmanaged nodes

3
Packet Congestion links 1. Competency issue with NEC .
2. Visibility issue of Ericsson nodes

4
Rings status check

5
Improvement Plan

1.Planning need to prepare and share the IP plan for TX nodes and network to avoid IP
conflict and share with us .
2. Ericsson to share read writes to work on visibility issues after the plan.
2. 1st we will do configurations of IP's on each unmanaged TX nodes from BO and raise
WO to the field if required their support to get is visible .
3. Once IP configuration done and IP starting pinging on server , will make it discover
through server and make the node visible on SO-eM.
4. Remove/Delete all duplicate TX Nodes from the server .

1. Will fetch the alarm direct from the Servers & analysis them.
2. Will analysis the alarms and assign the task based on support requirements from BO
or raise WO to get support from Field team .
3.Will start alarm clearance drive for OSN , Ceragon and NEC with the help of Local team
and BO team .
4. Will work on the Ericsson visibility once the plan received from planning
5. Will share daily tracker with progress update.

1. Planning need to provide link Budget for RSL improvement exercise


2. After restoration of visibility we will schedule the reports on SO-eM.
3. Report will take 24 hour to 1 week to get it completely .
4. We will prepare the RSL improvement tracker based on the last 5 to 7 days report .
5. Will compare the Field link t vs Plan RSL values to get deviation .
6.Whichever link will have 5 or above 5 value from the planning value will raise WO to
field team to get them align .
7. before raising WO, we BO we will optimize the TX power according to plan to avoid FE
visit .
8. Will prepare the report once in week and share share the daily progress update .

1. We fetch the at least 5 days packet link utilization report from the servers.
2. Will check & compare the bandwidth and utilization for all packet links .
3. Those link which are running from above 70% utilization .
4.Will share all high Utilization link with planning to get new plan for up gradation.
5. Will do upgrade the link based on plan to avoid any link interference issues .
6. Daily share the progress update .

1. We conduct the quarterly rings protection status test .


2. Based on the result we will share the status of rings.
3. Will define the protection for TDM and IP sites if any fails during the test.
S.No

5
5
Items

TX Nodes Visibility

Alarm clearance drive

RSL improvement Plan

Packet Congestion links

Rings status check


Rings status check
Issues

Limited visibility (Only 21 %) which is 489 node count out of 2185 nodes
visibility of Ericsson TX nodes Soe_m while the remaining are not.

1.Making fetching of alarms & performance reports easily base on Ericson


and Sagem Link visibility issue

1. unavailability of MW network link budget


2. Failure of getting any performance reports of Ericsson & Sagem due to
DCN instability and for unmanaged nodes

Congestion and link Upgrade

Reliability test
Reliability test
Improvement Plan
1.Work with Planning team to prepare the IP plan for TX nodes and
network to avoid IP conflict and share with us .
2. Base on the consolidated data to be received from Ericsson before
Exit ,we will commence validation towards ensuring visibility issues is as
planned.
2. Configurations of IP's on each unmanaged TX nodes from BO  and raise
WO to the field if required their support to get is visible .
3. Once IP configuration done we will ensure node visible on SO-eM is
closed on priority.
4. Remove/Delete all duplicate TX Nodes from the server .
1. Fetch the available alarms directly from the Servers for analysis while
other are pull manually.
2. Analyze the alarms and assign the task based on support requirements
from BO or raise WO to get support from Field team .
3.Coomenced alarm clearance on the OSN , Ceragon and NEC with the help
of Local team, Field and BO team .
4. Align on the  visibility plan above once the plan received from planning

5. Daily tracker with progress update and owners.

1. link Budget provided will be used for RSL improvement exercise


2. using the  existing visibility while still working on others we will schedule
the reports on SO-eM.
3. Report scheduling will be activated although it may take 24 hour to 1
week to get it completely close for the whole network.
4. RSL improvement tracker will be developed using the last 1 to 2 2weeks
report .
5. Deviation between the Field link  vs Plan RSL values to get deviation
margin across .
6.work will commence on link with 5 and above from the planning value by
raising WO to field team to get them align .
7. We will optimize the TX power according to plan if alignment can be
achieve before field intervention
8. Weekly report to be shared to track the progress  .
1. We fetch the at least 5 days packet link utilization report from the
servers.
2. Check & compare the bandwidth and utilization for all packet links .

3. Those link which are running from above 70% utilization .


4.Will share all high Utilization link with planning to get new plan for up
gradation.
5. Link upgrade maybe necessary based on plan to avoid any link
interference issues .
6. progress Update to be share daily.

1. We conduct the quarterly rings protection status test .


2. Based on the result we will share the status of rings.

3. Re-define the protection for TDM and IP sites if any fails during the test.

You might also like