Live Chat
Monday - Friday 8am - 6pm EST Chat Now
Contact Us
Monday - Friday 8am - 8pm EST 1-800-268-7737 Other Contact Options
Checkout

Cart () Loading...

    • Quantity:
    • Delivery:
    • Dates:
    • Location:

    $

Avaya Session Manager Server Install (Redhat Kickstart DVD Procedure): Part Two

Date:
Feb. 20, 2012
Author:
Daniel Voigtlander

Last week we installed the Avaya System Manager. Now we will go to the Session Manager Server. This is the Redhat Kickstart DVD procedure. You will load this on a separate server than the one you just loaded  System Manager on (make sure you have a monitor and keyboard attached as this will be your only way to initially interact with the sesman until you do the SMnetSetup in a later step).

  1. Insert SM Kickstart DVD into the DVD tray and restart server by unplugging it and plugging it back in.
  2. Disk will popout when the install is complete.
  3. At the command prompt login using craft/craft01.
  4. Type ls to list files.
  5. Type ./SMnetSetup and press enter the following input when the prompted:
    1. Server Hostname: sesman
    2. b.      Server IP: xxx.xxx.xxx.xxx
    3. Netmask: xxx.xxx.xxx.xxx
    4. d.      Gateway: xxx.xxx.xxx.xxx
    5. Domain: FQDN
    6. DNS: xxx.xxx.xxx.xxx
  6. After the last input press enter and then enter again.
  7. At the timezone selection screen choose Chicago, then highlight okay and press enter.
  8. Verify date… press enter.
  9. Verify time… press enter.
  10. At the yes (y) prompt press enter.
  11. Time and date has been set enter y, then press enter.
  12. Would you like to enable NTP, type No, then enter.
  13. Customer Account – y then enter.
  14. Login ID: cust
  15. Password: cust01
  16. Password again: cust01
  17. Press Enter to complete the installation of the base Linux.
  18. Press y then enter when prompted to reboot (disk will popout).
  19. After reboot log back in using craft/craft01.
  20. Then su – sroot/sroot01.
  21. Insert SM6.1 disk into drive.
  22. Type cd /dev, then press enter.
  23. Type mount cdrom /cdrom then press enter (will show as read only).
  24. Type cd /cdrom, press enter, then ls to list files.
  25. Type ./install.sh.
  26. Press enter when prompted to continue install.
  27. Enter the following when prompted:
    1. SMGR Address: created in step 14
    2. SMGR FQDN: created in step 14
    3. Enrollment Password: created in step 22
  28. Press enter to continue install. After install is completed, the command prompt will return. Log back in using craft/craft01.
  29. Type eject to remove CD.
  30. Log into SMGR using username/password created in step 18 [link to first post].
  31. Next, go to the Home Screen and click Routing.
  32. Click Domains, then click new and enter FQDN, click commit.
  33. Click Sip Entities on the left, then click New.
  34. In the Name field enter name created in step 42A.
  35. In the FQDN or IP Address field enter xxx.xxx.xxx.xxx (SM100 equivalent).
  36. Under Ports click add, then choose domain from the Default Domain dropdown list.
  37. Click Commit.
  38. Go back to the home screen and click on the Session Manager link.
  39. On the left side click Session Manager Admin.
  40. Under the Session Manager Instances, click New.
  41. From the Sip Entity dropdown choose Sesman (the one created earlier).
  42. In the Management IP field, enter xxx.xxx.xxx.xxx (not the same as step 36).
  43. In the Default GW field, enter xxx.xxx.xxx.xxx.
  44. Click Commit.
  45. Putty to Sesman using craft/craft01, then type initTM and enter enrollment password when prompted.
  46. Go back to SMGR and login. Then go to Session Manager link and click checkbox next to Sesman and change service state to Accept.
  47. Wait approximately 5 minutes for stabilization, then verify both levels of the security module are up.
  48. You are done and your system is now ready for beginning of class.

This will assist you in setting up your System and Session Manager systems. You will, of course, have to use addressing and names that are applicable to your network. This does not address ME templates. I will cover that in another post.