Checking A 4.0 Release; Creating A Super-User Login, If One Does Not Exist (Releases Earlier Than Release 4.0) - Avaya G700 Installing And Upgrading

Manual upgrade of an existing S8300B and G700 to S8300C with R4.0
4. If a super-user login does not exist, create one. See
not exist (releases earlier than Release

Checking a 4.0 release

To ensure that a super-user login exists in Communication Manager in Release 4.0 or higher:
1. Log in with ssh.
2. At the Linux command line, type cat /etc/passwd |grep 555.
The following list of super-user logins appears.
init:x:778:555::/var/home/defty:/bin/bash
inads:x:779:555::/var/home/defty:/bin/bash
craft:x:780:555::/var/home/defty:/bin/bash
dadmin:x:1001:555::/var/home/defty:/bin/bash
erik:x:1002:555::/var/home/defty:/bin/bash
3. Look for any logins other than the init, inads, and craft logins. If no additional super-user
logins exist, you must create one. See
(releases earlier than Release
Creating a super-user login, if one does not exist (releases earlier
than Release 4.0)
If a super-user login does not exist, one must be added before you can complete the upgrade.
The customer or remote services should complete the following task.
1. Use the following steps only if you are starting from a software release earlier than Release
4.0:
Note:
Adding a super-user login with the SAT command line requires a dadmin, init, or
Note:
inads login.
Note:
If you are upgrading an S8300 LSP, create the super-user login on the primary
Note:
controller. Then, at the LInux command line on the primary controller, run the
filesync -a <IP_address_of_LSP> command.
698 Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server
Creating a super-user login, if one does
4.0).
Creating a super-user login, if one does not exist
4.0).