Scribd
Upload
7 views9 pages

NEW process of OCC LINK deletion (2)

The document outlines the procedures and prerequisites for LINK Deletion MOP at MPOCC, including a pre-health checkup of the OCC node and necessary configurations. It details the step-by-step process for logging into the OCC GUI, editing configurations, and performing post-checks to ensure successful integration. Recommendations for troubleshooting and log verification are also provided to address potential issues after configuration changes.

Uploaded by

grahulsah02
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
7 views9 pages

NEW process of OCC LINK deletion (2)

The document outlines the procedures and prerequisites for LINK Deletion MOP at MPOCC, including a pre-health checkup of the OCC node and necessary configurations. It details the step-by-step process for logging into the OCC GUI, editing configurations, and performing post-checks to ensure successful integration. Recommendations for troubleshooting and log verification are also provided to address potential issues after configuration changes.

Uploaded by

grahulsah02
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

LINK Deletion MOP : MPOCC’s

1. Pre-Requisites

1.1 Pre Health Checkup


Take the pre health check-up of the OCC node.
 Check errors in Server transaction logs, business logs and server notification
logs.
 Business Log Errors need to be checked in Node A and Node B Separately.
 Take netstat -nrv output

1.2 Prerequisites for User


The following pre-requisites must be met.

Pre-Requisite for User


No. Status
1.3 Pre-activity
OCC Manager’scheckpoints
IP , Username and Password for GUI
Configuration
Impact: 1. For changes in 1_**_**** :: Application restart is
1. required which involves 15-20 minutes of Outage/Traffic
Diversion.

2.

 Check the alarm status. Make sure that there are no Major active alarms in
the node. If there are any Critical active alarms the source of the alarm must
be corrected before the node Integration procedure is started.
 Configuration file backup to be taken before and after deletion activity.
 OCC IP’s should be reachable to all the integrated node and vice-versa
 All gateways IP’s should be reachable.

C2 – Vodafone Idea Internal


2 Procedure

1. Log in to the OCC GUI as a System Administrator.

2. Select the common Front-End configuration in which Diameter Front-End (Diameter


Peer activity) interface resides.
Note: The configuration number associated with Diameter Front-End Interface is
1_19089-CXC_****

3. Check out the configuration to ensure that it is in edit mode.

4. Go to Active pane as shown below (here configuration 1_19089-CXC_1730371 is


shown for example)

5. Right click on configuration active version and check out to edit the configuration
New editable version will be open .

6. Right-click in the Configuration Frame and select Properties from the pop-up menu.
o In properties window goto Definition of peers.
o Remove the link details under Diameter Identity in the Peer table and the
Realm in the Application table.
o Remove the peer entry (complete entry) from new revision’s Peer table and
remove the corresponding entry from Outgoing Request Routing table for the
same Peer, if the Peer is already available. (Note : All the peers need to be
edited in all OCC’s)

C2 – Vodafone Idea Internal


7. Check-In the saved configuration.
8. Select ok to save and a new version will be saved (For ex.16 is a new version in
snap).

9. As displayed in the below snap – right click on the front end configuration from
grouped section and Click on stop to stop the front end configuration, click on YES in
the Pop Up.

C2 – Vodafone Idea Internal


10 . As displayed in the below snap – right click on the front end configuration and Click
on Unassign, and click YES in the Pop Up.

C2 – Vodafone Idea Internal


 11 . Assign the new configuration revision on Right Click on that (For ex.16 is a new
version).

C2 – Vodafone Idea Internal


12. As displayed in the below snap – right click on the front end configuration and Click on Start,
and click YES in the Pop Up.

C2 – Vodafone Idea Internal


13. After performing the above STEP’S, Fresh version of configuration becomes live.

C2 – Vodafone Idea Internal


2.Post-Checks

Recommendations:

1. If any further problem observed, then OCC components restart can be


performed. (Follow the OCC components restart MoP)
This will help to resolve any hung status, memory related issues within the
the
OCC configurations.
2. Always verify the OCC SERVER.System, SERVER.Business,
SERVER.Notification, Alarm logs after configuration change activities.
3. CDR file generation check in OCC after 5-10 mins of activity

post checks commands:


1.
cat /opt/occ/var/performance/counters_2023120816* | grep -i
",transactions.rejected" | grep -i "1_1"
cat /opt/occ/var/performance/counters_2023120816* | grep -i
'transactions.tps' | grep -i "1_1"
cat /opt/occ/var/performance/counters_2023120816* | grep -i
',transactions.timeout,' | grep -i "1_1"
cat /opt/occ/var/performance/counters_2023120816* | grep -i
',transactions.failed,' | grep -i "1_1"

C2 – Vodafone Idea Internal


Note:please change date and hr as per activity date.

2.

SERVER.System.log:
SERVER.Business.log

cd /opt/occ/var/log/

Sample Erros:

SERVER.System.log:
------------------------------------------
Time: 2023-07-20 09:47:06.919, Level: SEVERE, Logger: module.Runtime
Processing.Transaction Handler
- Processing error, current activity was '1_19089-CXC_1730371/Diameter
Front-End', next activity was '1_19089-CXC_1730371/Diameter Front-End'
Exception was: java.lang.NullPointerException
Message: java.lang.NullPointerException
------------------------------------------
SERVER.Business.log
------------------------------------------
Time: 2023-07-20 09:47:06.919, Level: SEVERE, Logger: business.1_19089-
CXC_1730371.Diameter Front-End
- Transaction: [ TID:29877795987 GID:31101299203 TT:Active SID:d26-
INVIMH01PUN1SAEX01ER;1689826626;7775656;64b8b542-
404223708204609 RT:Begin RN:0 CC:272 AID:4 HID:7943c3e5
EID:12452c8b]
Error while sending DIAMETER_UNABLE_TO_COMPLY 5012 as response for
timeout
java.lang.NullPointerException
------------------------------------------

C2 – Vodafone Idea Internal

You might also like