| Asset ID: |
1-71-2146113.1 |
| Update Date: | 2017-09-22 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2146113.1
:
CommsGBU Network Support Signaling Solutions PIC Handoff Procedure
| Related Items |
- Oracle Communications Performance Intelligence Center (PIC) Hardware
- Oracle Communications Performance Intelligence Center (PIC) Software
|
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec PIC
|
In this Document
Applies to:
Oracle Communications Performance Intelligence Center (PIC) Hardware - Version 4.1 and later
Oracle Communications Performance Intelligence Center (PIC) Software - Version 4.1 and later
Information in this document applies to any platform.
Goal
The goal is to provide the Oracle Support and Consulting Teams, as well as the Oracle Partners, with the necessary documentation and instructions to start and complete successfully the Project Handoff to Support procedure for the Tekelec PIC Product.
Solution
Document Description
The Handover Report is an excel file which should be created and named following the rules below:
Handover – Customer name – SO number – beginning date of the Handover
The document contains the 7 tabs below :
- Welcome
- Overview
- Health Check
- Engineering Document
- Correlation Rates
- DFP Input
- NSP Backup
- CSR in progress
The Support Engineer should follow the color codes below when completing the report:
|
Color Codes for validation
|
| Green - Validated |
| Orange- Not Blocking issue or issue not related to the project |
| Red - Not Validated, impacting |
Work instruction Flow
This section describes how to complete the 7 tabs.
Welcome tab
The Welcome Tab contains the information below :
- Customer Name
- SO number ( Sales Order number )
- System Identifer ( SI XXXXXXXX )
- Consulting Engineer name.
- Support Engineer name.
- Oracle Project Manager contact information.
- Customer Project Manager Contact Information.
- Project Scope.
Overview tab
This Tab contains 2 parts:
- Data:
- HealthCheck
- Engineering Document
- Correlation Rates
- NSP Backup
- Embedded documents:
- Engineering Document
- NSP Configuration Report from CCM
- Health Check
- NSP backup ( location on the Oracle network )
Health check tab
The servers concerned by the Handover are listed on this Tab.
After running the Health Check script, all the errors must be listed.
Please refer to table below for validation :
|
Color Codes for validation
|
| Green - No errors on the system |
| Orange - Not Blocking Errors or Errors not related to the project ( Errors preceded by the word : Minor ) |
| Red - Impacting and Blocking Errors ( Errors preceded by the word : Major or ERROR ) |
Engineering Document and Patch Checks Tab
- The Support Engineer has to check if the information below are present on the Engineering Document, and list all incorrect information:
|
Items
|
| Customers Contact (Name, email, fix/mobile phone, address) |
| Responsible by site |
| Project Manager on the customer side |
| Address of delivery and address of sites |
| Remote connection |
| Connexion procedure |
| password of connections |
| Test of connection |
| Procedure to Access on site |
| Hardware identification (Delivered by Tekelec) |
| Constructor Serial number by server |
| Product number (exist in the same etiquette than the serial number in front of server) |
| Serial number of CxC, Lantronix |
| Server configuration |
| Raid configuration |
| Disk capacity |
| LAN connectivity (speed card LAN, full duplex, half duplex,..) |
| IP addresses of servers |
| LAN diagram |
| Type of servers (DS, NSP, IXP, IMF,..) |
| Users/Password administrator of the servers + PCAnywhere, VNC,... |
| Global view of system architecture (Schema presenting all servers with their disposition) one schema by type of system except some cases |
| Global view of connection between cross connect |
| List of the sessions by PMF & IXP |
| List of Software installed and delivered to customer |
| Specific parameter (in case of modification of default setting, add a column ‘specific parameter’ to be checked in case of presence of modification, add a column commentaries ) + backup of configuration |
| diagram of bays, KVM, switch, cxc and lantornix (Cabinet Layout) |
| Emplacement of bays on different sites |
| Document of engineering version, n° of projects with date of finalisation |
| Licences |
| ILO access (Yes or no) + IP adress |
| Software availability in case of reinstallation (version, path,...) |
- Check patches as below :
- latest patches are installed on the system
- All equipment are on the same level of patches/release
There is a separate Knowledge document created for every release which includes all currently available patches for a particular release. These documents can be found in PIC Info Center (Doc ID
1989320.2), Tab “Patch and Maintenance”.
Please refer to table below for validation :
| Color Codes for validation |
| Green -The information is correct |
| Orange - The information is incorrect but related not to the project |
| Red - The information is incorrect and related to the project |
Correlation rates tab
The Support Engineer has to check the availability of Monica sessions and Correlation Rates by providing the graphs. Next step is to confirm that the correlation rates are above the agreed level and accepted by customer.
Since PIC 10.1 correlation rate can be checked in the capacity management cession as well as the volume of data from DFPs but also from xMF
Capacity Management Best Practices (Doc ID 1683859.2)
Please refer to table below for validation :
|
Color Codes for validation
|
| Green - If the Monica rates are between 100% and 99% |
| Orange - If the Monica rates are between 99% and 95% |
| Red - If the Monica rates are under 95% |
DFP Input
The Support Engineer has to list the Build DFP per IXP and the corresponding Input graph for 1 week,
It is required to calculate Build Input traffic in “Mbps” to know the Builder load per protocol. Please follow the instructions below for the DFP Build graphs :
- Extraction :
- From ProTrace application, retrieve the data contained in Build Monitor session (ixpXXXXbuildmonitor) for a period of at least 5 days (preferably from last Thursday 00:00:00 to Monday 23:59:59) for all the IXP subsystem.
- Download format should be in “.CSV” not in “Direct Excel”. It’s preferred to follow naming convention for automation steps: “IxpXXXX_Build_Monitor” whereas XXXX – subsystem number.
- Processing
- Build Input is obtained by filtering on the “Initial” and retrieving the “BldReceivedBytes” values for the particular Build Dataflow processing(DFP) running on that particular IXP.
- All these values are available in Bytes which are pre-processed during one minute.
- It is converted into “Mbps” by the following formula:
- X*8/(60*1000000) whereas “X” is Build data in bytes.
- “Initial” values corresponds to the Input traffic coming on each Build DFP, whereas “Final” corresponds to the Output traffic generated from each Build DFP according to the xDR builder applied.
- For each DFP, separate sheets must be created for Build Input data and Build input graph requires to be created based on the data formatted.
NSP Backup Tab
The Support Engineer has to Check the information below :
- Crontab on the NSP server
- ExpNSP.dmp file
- Exportrealm file
Please refer to table below for validation :
|
Color Codes for validation
|
| Green - f the backup is running |
| Red - If the backup is not running |
PIC Inventory Tab
The Support Engineer has to insert the PIC Inventory report provided by PS adding comments if required.
picInventory: Installation and Usage (Doc ID 2047371.1)
SR in Progress Tab
All the SR should be listed with the information below :
- Issue description
- Solution Description
- Bug/SR number
- Status
References
<NOTE:2141679.1> - (CommsGBU Network Support) Signaling Solutions Project Handoff Guidelines
Attachments
This solution has no attachment
