US Tools

# PRL Updates

This document describes how to update a single device PRL using the SOUP server. 

## Prerequistes

 1. Ensure you have access to the production SOUP server.  Create a ticket if needed.

 1. Provide adequate notification prior to updating customer devices. 

 1. Ensure you have correct information including: Carrier and Model for the particular Device (MAC address)

## Update process

 1. Login to SOUP server: densoup01.contournetworks.net

 1. Run the following commands:

~~~

cd /opt/sdm/www/soupfiles

ln -s /opt/sdm/configs/systechConfig/prls/[prlfile] M[last six of MAC]99000000.prl 

~~~

### PRL Versions [prlfile]

    #### Sprint Versions

        ##### PRL 304xx (73xx series Sprint Systech)

               This is an MVNO-type 1xRTT PRL that supports Sprint's 1900 CMDA network used for devices unable to 'load' an IS-683E or IS-683C PRL type.

        ##### PRL 404xx (8xxx series Sprint Systech)

               This is an MVNO-type EVDO PRL that supports Sprint's 1900 CMDA network used for devices unable to 'load' an  IS-683E PRL type.

        ##### PRL 506xx (77xx series Sprint Systech)

              This is a Sprint-type 1xRTT PRL that supports Sprint's 1900 CMDA network and includes ERI (Extended Roaming Indicators) used for devices unable to 'load' an IS-683E or IS-683C PRL type. This PRL is the Sprint-type analog to 304xx.  

### Examples 

    #### 73xx

         ln -s /opt/sdm/configs/systechConfig/prls/30402.prl  M0DF06A99000000.prl

    #### 77xx

         ln -s /opt/sdm/configs/systechConfig/prls/50652.prl  M0EFFA699000000.prl

    #### 81xx  

         ln -s /opt/sdm/configs/systechConfig/prls/40492.prl  M10778899000000.prl

## Validation

Run the following command to ensure the file is linked correctly.

~~~

ls -ltra 

~~~

### Examples

[root@densoup01 soupfiles]# pwd  - show the current directory

/opt/sdm/www/soupfiles

[root@densoup01 soupfiles]# ls -ltra list files with attributes

lrwxrwxrwx. 1 root root     45 May 17 13:48 M0FD18199000000.prl -> /opt/sdm/configs/systechConfig/prls/50652.prl

lrwxrwxrwx. 1 root root     45 May 17 13:48 M10054199000000.prl -> /opt/sdm/configs/systechConfig/prls/50652.prl

lrwxrwxrwx. 1 root root     45 May 17 13:48 M10035A99000000.prl -> /opt/sdm/configs/systechConfig/prls/50652.prl

lrwxrwxrwx. 1 root root     45 May 17 13:48 M1002E799000000.prl -> /opt/sdm/configs/systechConfig/prls/40492.prl

lrwxrwxrwx. 1 root root     45 May 17 13:48 M10189F99000000.prl -> /opt/sdm/configs/systechConfig/prls/40492.prl

lrwxrwxrwx. 1 root root     45 May 17 16:01 M0DEE8199000000.prl -> /opt/sdm/configs/systechConfig/prls/30402.prl

lrwxrwxrwx. 1 root root     45 May 17 16:02 M0DF04B99000000.prl -> /opt/sdm/configs/systechConfig/prls/30402.prl

if any links show up red or underlined the link is not correct

## Know Issues

   Sprint Master Service Lock (MSL) codes are required to update a prl via Soup.

   The MSL spreadsheet provided by Sprint is on P:\Contour Support Files\Master_MSL.xlsx

   The soup server will deliver the file to the router but if the module is locked the updates is not processed.

# Nightly Validation

A script is run nightly at 07:00 which will parse the logs to determine which routers have been successfully updated.  This will send an email to: prlupdate@contournetworks.com which show the following information.

the script is located at /opt/soup-adminscripts/getdailylogsprl.sh 

This can be ran manually and it will mail a report that has

- The Date

- status 

- Last Six (6) of MAC Address

 # Exmaple of report

[160519 03:42:15 Delivering new to 0E72B5

[160519 03:47:51 Delivering new to 0E72A3

[160519 03:49:30 Delivering new to 0E72B5

[160519 03:51:06 Delivering new to 0EEE10

[160519 03:53:41 Delivering new to 0ED95B

[160519 03:54:26 Delivering new to 0E72A3

[160519 04:03:44 Delivering new to 0ED95B

[160519 04:08:26 Delivering new to 0EB0EC

[160519 04:16:03 Delivering new to 0ED95B

[160519 05:12:46 Delivering new to 10035A

[160519 05:21:41 Delivering new to 0E94FE