No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

eSight V300R009C00 Operation Guide 10

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Setting Protocol Parameters for Unified Communications Devices

Setting Protocol Parameters for Unified Communications Devices

Setting Protocol Parameters for IADs

Set protocol parameters on IADs so that the IADs can properly connect to the eSight.

Background

  • By default, the IADs (IAD101, IAD102, IAD104, IAD132, IAD196, IAD208 and IAD1224) support Telnet. IAD104, IAD132, IAD196 and IAD1224 support SSH.

    Exercise caution when using Telnet because it may bring information security risks.

  • By default, the eSight domain name ucems.huawei.com is configured on IADs.
  • If a DNS server exists on the network, configure the mapping between the eSight domain name and the IP address on the DNS server.
  • If no DNS server is available on the network and IADs are added in the automatic discovery mode, configure the IP address of the eSight by referring to Procedure.
  • By default, all IADs support SNMPv2c for reporting alarms.

    Exercise caution when using SNMPv2c because it may bring information security risks.

    An SNMPv2c user is configured by default for each IAD before delivery.

  • IAD1224 supports SNMPv3 from V300R001C07SPC200, and IAD104, IAD132 and IAD196 support SNMPv3 from V300R002C01.
    NOTE:

    If an IAD supports SNMPv3, use SNMPv3 because it has high security.

    An SNMPv3 user is configured by default for IAD104, IAD132, IAD196 and IAD1224 before delivery. You can add IADs as the SNMPv3 user or configure this user according to Procedure before adding IADs. The default parameter settings are:

    • Security Name: SNMPV3
    • Authentication Mode: SHA
    • Encryption Type: CBC_DES

      Be cautious to use CBC_DES because it may bring information security risks.

Procedure

NOTE:
  • You do not need to configure the eSight IP address on the IAD if an IAD is not added in automatic discovery mode.
  1. Use the remote tool to log in to the IAD using SSH or Telnet.

    Be cautious to use Telnet because it may bring information security risks. You are advised to use SSH.

    Be cautious to use SSH of low version because it may bring information security risks. You are advised to use the latest SSH.

    NOTE:
    • In the global IAD configuration mode, run the terminal ssh_user command to modify the user name and password of SSH.
    • For more login modes, see the IAD Product Documentation.

  2. Enter the global configuration mode for the IAD.

    ==You need to enter the bold section========================================= 
    User name:root 
    User password:admin or huawei123 
    TERMINAL>  
    TERMINAL>enable 
    TERMINAL#configure terminal 
    TERMINAL(config)# 
    ============================================================

  3. Set the eSight IP address on the IAD.

    If you enable NAT traversal, you should take the translated IP address as the IP address of eSight.

    • eSight is single-node cluster system or local two-node cluster system.
      NOTE:

      The eSight local two-node cluster provides only one IP address externally. Therefore, you only need to specify a value for primary.

      For example, if the IP address of the is 192.168.3.240, run the following command:

      nms primary 192.168.3.240

    • eSight is two-node cluster system.

      For example, if the IP address of the primary eSight server is 192.168.3.240, and the IP address of the standby eSight server is 192.168.3.241, run the following command:

      nms primary 192.168.3.240 secondary 192.168.3.241

  4. Set communication parameters between IADs and the eSight.

    • If the default SNMPv2c protocol is used for communication:

      nms getcom Read community setcom Write community trapcom Trap community trapport Listening port number

      • Read community: Public@123
      • Write community: Private@123
      • Trap community: Public@123
      • Listening port: 10162 for the SUSE Linux operating system and 162 (default value) for the Windows operating system
    • If IAD104, IAD132, IAD196, and IAD1224 use SNMPv3 for communication:
      NOTE:

      If an IAD supports SNMPv3, use SNMPv3 because it has high security.

      snmpv3-agent group groupname privacy

      Here, privacy means authentication and encryption.

      snmpv3-agent usm-user username groupname authentication-mode sha Authentication password privacy-mode des56 Encryption password

      • Authentication Mode: SHA
      • Authentication Password: Huawei@123
      • Encryption Type: CBC_DES

        Be cautious to use CBC_DES because it may bring information security risks.

      • Encryption Password: Huawei@123
      • When alarms are reported to eSight installed on SUSE through the SNMP protocol, the trap port of the IAD must be set to 10162.

        nms trapport 10162

      • When eSight installs on Windows, you are advised to use the default value 162.

  5. Set the handshake parameters.

    nms handshake switch on interval 30

    By default, the IAD sends a handshake message to the eSight at an interval of 30 seconds to ensure that IAD information is the latest on the eSight.

  6. View the state of the IAD registered on the eSight.

    display nms

    the config is IP 
    ---------------------------------------------------------------- 
      type                            IP address      status 
      primary                         192.168.3.240 normal 
      secondary                       <unconfig>      unconfiged 
    ---------------------------------------------------------------- 
     
    get community : public 
    set community : private 
    trap community  : public 
    trap port       : 10162 
    nms access value: Enable 
    register nms ip : 192.168.3.240 
    register state  : succeed 
    handshake       : on 
    handshake time  : 30 S 
    register switch : on 
    snmp version    :v3

  7. Configure the FTPS service of IADs.

    By default, the following versions of IADs use the FTPS service:

    • IAD101, IAD102, and IAD208: No version supports the FTPS service
    • IAD104: V300R002C01 or later
    • IAD132: V300R002C01 or later
    • IAD196: V300R002C01 or later
    • IAD1224: V300R001C07SPC200, IAD1224 V300R002C01, or later

    If an IAD does not support the FTPS service, enable the FTP service for the IAD.

    Exercise caution when enabling the FTP service because it may bring information security risks.

    Ensure that the configured port number does not conflict with any existing port number used in the system; otherwise, the service may malfunction.

    To enable the FTP service, perform the following operations:

    Log in to the eSight server as administrator user, and configure the parameter <param name="enable"> of <config name="ftp"> in eSight installation directory/AppBase/sysagent/etc/sysconf/svcbase/med_node_1_svc.xml as true, and configure the parameter IAD.FTPSorFTP in eSight installation directory/AppBase/etc/uc/config.properties as FTP. Restart the eSight server.

    Modify the FTP service port:

    • SUSE OS: Modify the FTPS redirection port as 31921.
      NOTE:

      If the eSight is two-node cluster system, you need perform the following steps on both nodes.

      1. Query the redirection port.

        iptables -t nat -L PREROUTING

      2. Delete the redirection port.

        iptables -t nat -D PREROUTING {fill in number which is according with the rules}

        {fill in number which is according with the rules} is the row number of the 14001 redirection port.

      3. Add the FTP service redirection port.

        iptables -t nat -A PREROUTING -p tcp --dport 21 -j REDIRECT --to-port 31921

    • Windows OS: Modify the FTP service port as 21.

      Log in to the eSight server as the Administrator user, and configure the parameter listenerPort of <config name="ftp"> area in eSight installation directory\AppBase\sysagent\etc\sysconf\svcbase\med_node_1_svc.xml as 21, modify the parameter UC.FTPS.PORT in eSight installation directory\AppBase\etc\uc\config.properties as 14001. Restart the eSight server.

    To enable the FTPS service, perform the following operations:

    An IAD uses port 21 for the FTPS service. Before enabling the FTPS service for the IAD, disable the FTP service. The two services use the same port. If they are both enabled, the file server cannot work. If network or IT devices are also deployed, they will behave unexpectedly if the FTP service is disabled. In this case, the FTP service is recommended.

    Log in to the eSight server as administrator user, and configure the parameter <param name="enable"> of <config name="ftp"> in eSight installation directory/AppBase/sysagent/etc/sysconf/svcbase/ent_uc_med_node_svc.xml as false.

    1. Getting root certificate esightRootCA.pem from directory eSight installation directory/AppBase/etc/certificate.
    2. Upload the root certificate manually.

      If the esight.keystore.sftp certificate file on the eSight is modified, you need to generate and upload the esightRootCA.pem certificate again.

      Upload root certificate to IAD in TFTP or FTP mode.

      NOTE:

      Place the root certificate on the FTP or TFTP server, ensure that communication between the IAD and the FTP or TFTP server is normal and the FTP or TFTP service is enabled.

      For details, see How to Use FTP/TFTP Tool in IAD Product Documentation.

      Log in to the IAD device as the administrator user.

      If IAD has old certificate, you need to execute following command to delete it first, and then upload the new root certificate.

      undo ftps_rootcert

      • Upload the FTPS root certificate by the TFTP server.

        load ftps_rootcert tftp IP address of the TFTP server Name of the FTPS root certificate

      • Upload the FTPS root certificate by the FTP server.

        load ftps_rootcert ftp IP address of the FTP server User name of the FTP server Password Name of the FTPS root certificate

        For example: load ftps_rootcert ftp 192.168.1.152 iad huawei esightRootCA.pem

    3. Modify the IAD time which is consistent with eSight time.

      time xx:xx:xx xx-xx-xx

    4. Restart the IAD device.
    5. Configure the FTPS service for the eSight.

      Log in to the eSight server as administrator user, and configure the parameter implicitSsl in eSight installation directory/AppBase/sysagent/etc/sysconf/svcbase/ent_uc_med_node_svc.xml as false, and configure the parameter <param name="enable"> of <config name="ftps"> in eSight installation directory/AppBase/sysagent/etc/sysconf/svcbase/ent_uc_med_node_svc.xml as true, and configure the parameter <param name="keystoreFileName"> of <config name="ftps"> in eSight installation directory/AppBase/sysagent/etc/sysconf/svcbase/ent_uc_med_node_svc.xml as etc/certificate/esight.keystore.ftps, and configure the parameter <param name="ssl.protocol"> of <config name="ftps"> in eSight installation directory/AppBase/sysagent/etc/sysconf/svcbase/ent_uc_med_node_svc.xml as TLSv1,TLSv1.1,TLSv1.2.

      Exercise caution when using TLSv1 because it may bring information security risks.

      The TLSv1 protocol must be used for IAD.

    6. Open the FTPS service.

      Log in to the eSight server as administrator user, and configure the parameter IAD.FTPSorFTP in eSight installation directory/AppBase/etc/uc/config.properties as FTPS. Change jdk.tls.disabledAlgorithms=SSLv3 in the configuration file eSight installation directory/AppBase/jre/lib/security/java.security to #jdk.tls.disabledAlgorithms=SSLv3. Restart the eSight server.

      Exercise caution when using SSLv3 because it may bring information security risks.

    7. Modify the FTPS service port.
      • SUSE OS: Modify the FTPS redirection port as 14001.
        NOTE:

        The default FTPS redirection port is 31921.

        If the eSight is two-node cluster system, you need perform the following steps on both nodes.

        1. Query the redirection port.

          iptables -t nat -L PREROUTING

        2. Delete the redirection port.

          iptables -t nat -D PREROUTING {fill in number which is according with the rules}

          {fill in number which is according with the rules} is the row number of the 31921 redirection port.

        3. Add the FTPS service redirection port.

          iptables -t nat -A PREROUTING -p tcp --dport 21 -j REDIRECT --to-port 14001

      • Windows OS: Modify the FTPS service port as 21.

        Log in to the eSight server as the Administrator user, and modify listenerPort as 21 in eSight installation directory\AppBase\sysagent\etc\sysconf\svcbase \ent_uc_med_node_svc.xml. Restart the eSight server.

  8. (Optional) Configure Network Address Translation (NAT).

    If you enable NAT traversal, the FTPS service becomes unavailable. The Configuration Backup and Restore, SIP User Info Backup and Restore and Upgrading IADs function under Software Management becomes invalid for IADs.

    If you need the Configuration Backup and Restore, SIP User Info Backup and Restore, and Upgrading IADs function under Software Management are valid for IADs, you can use FTP service. Exercise caution when using FTP because it may bring information security risks.

    • You do not need to perform the following operations if the IP address of the eSight can directly communicate with devices.
    • Perform the following operations if the IP address of the eSight cannot directly communicate with devices.

    The mappings between IP addresses and ports have been configured on the onsite firewall, switch, or router. Ensure that device IP addresses (or translated IP addresses) can communicate with the translated eSight IP address.

    1. Log in to the eSight server as the ossuser user.
    2. Open the config.properties file.

      cd eSight installation directory/AppBase/etc/uc

      vi config.properties

      Add the following statement to the file:

      NATIP=192.168.3.39:10.135.36.198/192.168.3.111:10.137.96.92
      • In 192.168.3.39:10.135.36.198, 192.168.3.39 indicates the original eSight IP address, and 10.135.36.198 indicates the translated IP address.
      • If the eSight is deployed in two-node cluster mode or has multiple network adapters, a mapping must be configured between each original IP address and translated IP address. Use a slash (/)to separate each two mappings.
      NOTE:

      After editing the configuration file, you do not need to restart the eSight> server. The system automatically updates every 1 minute. The configuration file automatically takes effect after the update.

  9. (Optional) Set the large capacity management parameter for IADs.

    When the number of managed IADs is larger than 500, you are advised to set the large capacity management parameter to reduce the load of the eSight server and ensure proper running of eSight.

    1. Log in to the eSight server as the ossuser user.
    2. Open the config.properties file.

      cd eSight installation directory/AppBase/etc/uc

      vi config.properties

      Add the following statement to the file:

      iad.big.capacity=true
      NOTE:

      After editing the configuration file, you do not need to restart the eSight> server. The system automatically updates every 1 minute. The configuration file automatically takes effect after the update.

Setting Protocol Parameters for IP PBXs

Set protocol parameters on IP PBXs so that the IP PBXs can properly connect to the eSight.

Prerequisites

The user name and password have been configured for IP PBXs.

Background

The protocols used by IP PBXs to connect to the eSight vary depending on IP PBX models. For details, see Table 13-2.

Table 13-2 Description of protocols used by IP PBXs to connect to the eSight

Device Model

Versions That Support Telnet

Versions That Support Telnet and SSH (SSH Recommended)

U1910, U1911, U1930, U1960, U1980 and U1981

-

V100R001C01 or later

SoftCo5500, SoftCo5816, and SoftCo9500

V100R003C01SPC200 or earlier

V100R003C01SPC200 or later

  • If Telnet is disabled on an IP PBX, the eSight uses the SSH protocol to connect to the IP PBX.
  • If Telnet is enabled on an IP PBX, the eSight can use SSH or Telnet to connect to the IP PBX.

    Be cautious to use Telnet because it may bring information security risks. You are advised to use SSH.

    Be cautious to use SSH of low version because it may bring information security risks. You are advised to use the latest SSH.

    If multiple types of IP PBXs are available on the network, Telnet is preferred.

  • The U1911, U1960 and U1981 reports alarms using Telnet or SNMPv3. Telnet is used by default. The version of the IP PBXs is V100R001C01SPC200 or a later version.

    If you need to use SNMPv3, log in to eSight server as the root user and change the value of ippbx.alarm.type to SNMP in <eSight installation directory>/AppBase/etc/uc/config.properties.

    Restart the eSight after updating the configurations. The procedure is as follows: Run the ./shutdown.sh command in eSight installation directory/bin to stop the eSight, and run the ./startup.sh command to start the eSight.

Procedure

  1. Use the Telnet tool to log in to the IP PBX using SSH.

    Be cautious to use Telnet because it may bring information security risks. You are advised to use SSH.

    Be cautious to use SSH of low version because it may bring information security risks. You are advised to use the latest SSH.

    NOTE:

    If a model of IP PBXs does not support SSH, use Telnet to log in.

  2. Access the configuration mode on the IP PBX.

    ==You need to enter the information in bold.========================================= 
    [.login    .] Login:>admin 
    [.password .] Password:>huawei123
    [.result   .] succeed 
    [%eSpace U1960]>enable 
    [.password .] Password:>huawei123
    [.result   .] succeed 
    [%eSpace U1960(config)]# 
    ============================================================

  3. Enable or disable the Telnet protocol.

    If an IP PBX can use only the Telnet protocol to communicate with the eSight, run the [%eSpace U1960(config)]#config telnet switch on command to enable the Telnet protocol.

    If an IP PBX can use both the Telnet protocol and the SSH protocol to communicate with the eSight, it is recommended that you run the [%eSpace U1960(config)]#config telnet switch off command to disable the Telnet protocol to ensure information security.

  4. Query the whitelist of the IP PBX.

    1. Run the following command to check whether the whitelist is enabled:

      show trust loginip switch

    2. If on is displayed, the whitelist is enabled. Run the following command to check whether the whitelist contains the eSight IP address:

      show trust loginip

    3. If the whitelist does not contain the eSight IP address, run the following command to add the eSight IP address segment to the whitelist:

      config add trust loginip startip eSight start IP address endip eSight end IP address

  5. Set IP PBX parameters.

    • Set the parameters of Telnet or SSH, see Table 13-3 to set the parameters.
      Table 13-3 Key parameter description

      Parameter

      Description

      Setting

      SSH User

      User name for logging in to the device through SSH.

      Set this parameter based on the site requirements.

      You can run the config modify sshuser name username password password command on the IP PBX to modify the user name and password.

      SSH Password

      Password for logging in to the device through SSH.

      Login Name

      User name for entering the view mode of the device.

      Set this parameter based on the site requirements.

      You can run the config add cliuser name username loginpassword loginpassword enablepassword enablepassword command on the IP PBX to add a new user.

      Login Password

      Password for entering the view mode of the device.

      Set this parameter based on the site requirements.

      You can run the config modify loginpassword command on the IP PBX to change the password.

      Enable Password

      Password for entering the configuration mode of the device.

      Set this parameter based on the site requirements.

      You can run the config modify enablepassword command on the IP PBX to change the password.

    • If SNMP is used, refer to the flowing steps:
      1. Add the eSight IP address to the whitelist.

        config add snmp manager ip eSight IP address

      2. Add SNMP user groups.

        For example, to add a user group V3 whose security mode is privacy, run the following command:

        config add snmp group name V3 securitymode privacy

        Table 13-4 SNMP user group parameter description

        Parameter

        Description

        Setting

        group name

        User group name.

        -

        securitymode

        Security mode.

        Optional values are as follows:

        • noauth: no authentication and no encryption.
        • authentication: authentication without encryption.
        • privacy: authentication with encryption.
        NOTICE:

        Be cautious to use noauth or authentication because it may bring information security risks. You are advised to use privacy.

      3. Add SNMP users.

        For example, to add an SNMP user and the IP address of the eSight server is 10.10.10.10, run the following command:

        config add snmp user name SNMP notifyname V2 targetip 10.10.10.10 groupname V3 authmode sha authpassword huawei privacymode aes privacypassword huawei

        Table 13-5 SNMP user parameter description

        Parameter

        Description

        Setting

        user name

        User security name.

        When adding IP PBX on the eSight, ensure that the security user name is the same as the value of this parameter.

        notifyname

        Notify name.

        The name can be customized.

        targetip

        Destination IP address.

        Set this parameter to the IP address of the eSight server.

        groupname

        User group name.

        Set this parameter to the value of group name that is specified when the SNMP user group is added.

        authmode

        Authentication mode. This parameter is required only when the value of securitymode is authentication or privacy.

        Set this parameter to md5 or sha.

        NOTICE:

        Be cautious to use MD5 because it may bring information security risks. You are advised to use sha.

        When adding IP PBX on the eSight, ensure that the authentication mode is the same as the value of this parameter.

        authpassword

        Authentication password. This parameter is required only when the value of securitymode is authentication or privacy.

        When adding IP PBX on the eSight, ensure that the authentication password is the same as the value of this parameter.

        NOTICE:

        The value of authpassword must be a string of 1 to 32 characters that contain at least two types of the following: uppercase letters, lowercase letters, digits, and special characters. In addition, the password must not be a string of repeated sub-strings, for example, ABABABAB, ABCABCABC, and ABCDABCD.

        privacymode

        Encryption type. This parameter is required only when the value of securitymode is privacy.

        Set this parameter to des or aes.

        NOTICE:

        Be cautious to use DES because it may bring information security risks. You are advised to use AES.

        When adding IP PBX on the eSight, ensure that the encryption type is the same as the value of this parameter.

        privacypassword

        Encryption password. This parameter is required only when the value of securitymode is privacy.

        When adding IP PBX on the eSight, ensure that the encryption password is the same as the value of this parameter.

        NOTICE:

        The value of privacypassword must be a string of 1 to 32 characters that contain at least two types of the following: uppercase letters, lowercase letters, digits, and special characters. In addition, the password must not be a string of repeated sub-strings, for example, ABABABAB, ABCABCABC, and ABCDABCD.

        Run the [%eSpace U1960(config)]#show snmp user information command to check whether the configured SNMP user information is correct.

      4. Enable SNMP.

        [%eSpace U1960(config)]#config snmp switch enable

      5. Configure the eSight IP address segment that can be trusted by IP PBXs.

        [%eSpace U1960(config)]#config add trust server ip address 192.168.3.0/24

        In the command, 192.168.3.0/24 is the IP address segment of the eSight server. Change the IP address segment based on the site requirements.

        Run the [%eSpace U1960(config)]#show trust server information command to check whether the configured SNMP user information is correct.

  6. Configure the FTPS service of IP PBXs.

    By default, IP PBXs use the FTPS service. At the same time, the TFTP service is also enabled on IP PBXs. The eSight automatically checks whether an IP PBX supports the FTPS service.

    • If an IP PBX supports the FTPS service, the FTPS service is used for communication.
    • If an IP PBX does not support the FTPS service, the TFTP service is used for communication.

    The following versions of IP PBXs support the FTPS service:

    • U1910, U1930 and U1980: V100R001C01SPC100B018 or later
    • U1911 and U1960: V100R001C01B012 or later
    • U1981: All versions support the FTPS service
    • SoftCo 5500 and SoftCo 9500: V100R003C01SPC400 or later
    • Softco 5816: No version supports the FTPS service

    If an IP PBX does not support the FTPS service, enable the TFTP service for the IP PBX.

    Exercise caution when enabling the TFTP service because it may bring information security risks.

    Ensure that the configured port number does not conflict with any existing port number used in the system; otherwise, the service may malfunction.

    To enable the TFTP service, perform the following operations:

    Log in to the eSight server as administrator user, and change the parameter <param name="enable"> of <config name="tftpServer"> in eSight installation directory/AppBase/etc/conffile/tftpconfig.xml to true, change the value of ippbx.ftps.enable in the eSight installation directory/AppBase/etc/uc/config.properties configuration file to false. Restart the eSight server.

    Modify the port number of the TFTP service.

    • SUSE operating system:
      NOTE:

      If the eSight is two-node cluster system, you need perform the following steps on both nodes.

      iptables -t nat -A PREROUTING -p udp --dport 69 -j REDIRECT --to-port 32182

      In this command, 69 is the port number on the device, and 32182 is the mapped port number on eSight, which is the same as <param name="listenerPort">32182</param> in the tftpconfig.xml file in the eSight installation directory/AppBase/etc/conffile directory.

    • Windows operating system: The default port number is 69 on eSight and the device. You do not need to modify the port number.

    To enable the FTPS service, perform the following operations:

    An IP PBX uses port 21 for the FTPS service. Before enabling the FTPS service for the IP PBX, disable the FTP service. The two services use the same port. If they are both enabled, the file server cannot work. If network or IT devices are also deployed, they will not work properly if the FTP service is disabled. In this case, the TFTP service is recommended.

    Log in to the eSight server as administrator user, and configure the parameter <param name="enable"> of <config name="ftp"> in eSight installation directory/AppBase/sysagent/etc/sysconf/svcbase/med_node_1_svc.xml as false.

    1. Getting root certificate esightRootCA.pem from directory eSight installation directory/AppBase/etc/certificate.

      If the esight.keystore.sftp certificate file on the eSight is modified, you need to generate and upload the esightRootCA.pem certificate again.

    2. Upload FTPS root certificate to the IP PBX device.
      1. Log in to LMT, and add the IP PBX device.
      2. Configure the parameter hostip of IP PBX as the IP address of LMT.

        config system hostip IP address of LMT

      3. Configure TFTP upload path.

        config tftp_ftps path type other name /read/

      4. Open TFTP server path.

        Path is LMT installation directory\tftp.

      5. Put FTPS root certificate in the directory read of TFTP server, and rename it as webrootcert.pem.
      6. Upload FTPS root certificate to the IP PBX device.

        config download file webrootcrt

    3. Configuring FTPS service of eSight.

      Configuring the parameter implicitSsl in eSight installation directory/AppBase/sysagent/etc/sysconf/svcbase/med_node_1_svc.xml as false, and configure the parameter <param name="enable"> of <config name="ftps"> in eSight installation directory/AppBase/sysagent/etc/sysconf/svcbase/med_node_1_svc.xml as true, and configure the parameter <param name="ssl.protocol"> of <config name="ftps"> in eSight installation directory/AppBase/sysagent/etc/sysconf/svcbase/med_node_1_svc.xml as TLSv1,TLSv1.1,TLSv1.2.

      Exercise caution when using TLSv1 because it may bring information security risks.

      The TLSv1 protocol must be used for IP PBX.

    4. Open the FTPS service.

      Log in to the eSight server as the root user, and change the parameter <param name="enable"> of <config name="tftpServer"> in eSight installation directory/AppBase/etc/conffile/tftpconfig.xml to false, change the value of ippbx.ftps.enable in the eSight installation directory/AppBase/etc/uc/config.properties configuration file to true. Change jdk.tls.disabledAlgorithms=SSLv3 in the configuration file eSight installation directory/AppBase/jre/lib/security/java.security to #jdk.tls.disabledAlgorithms=SSLv3. Restart the eSight server.

      Exercise caution when using SSLv3 because it may bring information security risks.

    5. Modify the FTPS service port.
      • SUSE OS: Modify the FTPS redirection port as 31923.
        NOTE:

        The default FTPS redirection port is 31921.

        If the eSight is two-node cluster system, you need perform the following steps on both nodes.

        1. Query the redirection port.

          iptables -t nat -L PREROUTING

        2. Delete the redirection port.

          iptables -t nat -D PREROUTING {fill in number which is according with therules}

          {fill in number which is according with the rules} is the row number of the 31921 redirection port.

        3. Add the FTPS service redirection port.

          iptables -t nat -A PREROUTING -p tcp --dport 21 -j REDIRECT --to-port 31923

      • Windows OS: Modify the FTPS service port as 21.

        Log in to the eSight server as the Administrator user, and configure the parameter listenerPort of <config name="ftps"> area in eSight installation directory\AppBase\sysagent\etc\sysconf\svcbase\med_node_1_svc.xml as 21. Restart the eSight server.

  7. (Optional) Configure information for the user and password when an old version IP PBX is used to ensure that the eSight management functions can work.

    The old versions indicate SoftCo5500, SoftCo5816, and SoftCo9500 of V100R001 and V100R002.

    1. Obtain the user name and password for logging in to the IP PBX.
      NOTE:

      Obtain the user name and password from onsite engineers.

    2. Log in to the eSight server as the root user.
    3. Open the config.properties file.

      cd eSight installation directory/AppBase/etc/uc/

      vi config.properties

      The following information is displayed:

      ippbx.oldVersion.loginName=User name

      ippbx.oldVersion.password=Encryptedpassword

      The encrypted password is the value that is obtained by encrypting the user name and password of the IP PBX using the encryption tool. For detailed operations, see Changing the Collaborations Passwords in the Maintenance Guide.

      If the user name and password of the IP PBX are admin14 and Changeme@123 respectively, the encryption command is as follows:

      cd eSight installation directory/AppBase/tools/bmetool/encrypt

      ./encrypt.sh 0

      When the following information is displayed, type admin14Changeme@123 and press Enter.

      please input the password: 
       
      Please input the password again: 
      NOTE:

      After editing the configuration file, you do not need to restart the eSight> server. The system automatically updates every 1 minute. The configuration file automatically takes effect after the update.

  8. (Optional) Configure Network Address Translation (NAT).

    If you enable NAT traversal, the FTPS service becomes unavailable. The Manual Restoration function under Configuration Backup and Restore and the Load patches function under Patch Management become invalid for IP PBXs.

    If you need the Manual Restoration function under Configuration Backup and Restore and the Load patches function under Patch Management are valid for IP PBXs, you can use TFTP service. Exercise caution when using TFTP because it may bring information security risks.

    • You do not need to perform the following operations if the IP address of the eSight can directly communicate with devices.
    • Perform the following operations if the IP address of the eSight cannot directly communicate with devices.

    The mappings between IP addresses and ports have been configured on the onsite firewall, switch, or router. Ensure that device IP addresses (or translated IP addresses) can communicate with the translated eSight IP address.

    1. Log in to the eSight server as the root user.
    2. Open the config.properties file.

      cd eSight installation directory/AppBase/etc/uc

      vi config.properties

      Add the following statement to the file:

      NATIP=192.168.3.39:10.135.36.198/192.168.3.111:10.137.96.92

      • In 192.168.3.39:10.135.36.198, 192.168.3.39 indicates the original eSight IP address, and 10.135.36.198 indicates the translated IP address.
      • If the eSight is deployed in two-node cluster mode or has multiple network adapters, a mapping must be configured between each original IP address and translated IP address. Use a slash (/)to separate each two mappings.
      NOTE:

      After editing the configuration file, you do not need to restart the eSight> server. The system automatically updates every 1 minute. The configuration file automatically takes effect after the update.

Setting Protocol Parameters for Agent

The Agent server sends alarms to the eSight through the uniform operation and maintenance agent (UOA) server. Therefore, you need to configure UOA server connection information on the Agent server, and add the Agent server's alarm resource package on the UOA server.

Prerequisite

The UOA server has been installed and is running properly.

Configuration on the UOA Server

  1. Log in to the UOA server as the uoa user.
  2. Stop the UOA service.

    cd $UOA_Server/shell

    uoa_stop.sh

  3. Obtain the eSpace_Agent_UOA.zip file from the IPCCV200R001C60_PUBLIC.zip > UOA.zip directory, decompress the file, and perform the following operations:

    1. Copy the files in alarm/ to the $UOA_Server/alarm/ directory.
    2. Copy the files in templates/ to the $UOA_Server/templates/ directory.

      The Agent server and ICS server share a template file. If the template file has been uploaded for one of them, you do not need to upload it again for the other.

      NOTE:
      • Ensure that the UOA user has the read, write, and execute permissions on the copied files.
      • In the preceding directories, $UOA_Server is the installation directory of the UOA server.

  4. Set the IP address of the Agent server in the $UOA_Server/cfg/system/adapter.acl file. The configuration results are displayed in bold as follows:

    10.10.10.116
    NOTE:

    When you need to configure multiple IP addresses, separate them in different lines.

  5. Start the UOA service.

    cd $UOA_Server/shell

    uoa_start.sh

Configuration on the Agent Server

  1. Log in to the Agent server as the elpis user.
  2. Open the /home/elpis/tomcat7/webapps/agentgateway/WEB-INF/config/uoa.properties file using the vi editor and configure the parameters by referring to Table 13-6. The configuration results are displayed in bold as follows:

    ##################################UOA Config ######################## 
    #UOA Alarm Switch: ON or OFF 
    uoa.switch = on 
    #If the path is an absolute path, the log is initialized to the absolute path.  
    #If the path is a relative path, the log is initialized to the current directory\relative path directory. 
    #If the value is null, the log is initialized to the current directory. 
    uoa.uoaLogPath = ${catalina.home}/logs/agentgateway/agentgateway_UOA_oamlib.log 
    #The alarm file is stored in the $ buffer directory/alarm directory. 
    uoa.uoaAlarmBufferPath = ${catalina.home}/logs/uoa 
    uoa.uoaBufferSize = 1000 
    #UOA Server Ip 
    uoa.uoaServerIP = 10.10.10.10 
    #the port added 6 based on AppOMListenPort  
    uoa.uoaServerPort = 6706 
    #UOA binding Local IP address for application side 
    uoa.moduleIP = 10.10.10.116 
    uoa.modulePort = 0 
     
     
    # Module Version 
    uoa.moduleVersion=V200R001 
     
     
    # Element Type for Agent Gateway 
    uoa.netEleType.agentGateway=30521 
    # Element Name for Agent Gateway 
    uoa.netEleName.agentGateway=eSpace Agent Desktop 
    # Element Id for Agent Gateway 
    uoa.netEleId.agentGateway=3052100 
    # Module Type for Agent Gateway 
    uoa.moduleType.agentGateway=3052102 
    # Module Name for Agent Gateway 
    uoa.moduleName.agentGateway=eSpace Agent Gateway
    Table 13-6 Parameter description

    Parameter

    Description

    uoa.switch

    Indicates whether to enable the UOA alarm function. The value on indicates yes and off indicates no.

    uoa.uoaServerIP/uoa.uoaServerPort

    uoa.uoaServerIP indicates the IP address of the server where the UOA is installed. uoa.uoaServerPort indicates the number of the port connected to applications. The value of uoa.uoaServerPort equals to 6 plus the port number of the UOA for listening applications.

    uoa.moduleIP

    Indicates the IP address of the Agent server.

  3. Restart the Agent service.

Setting Protocol Parameters for ICS

The ICS server sends alarms to the eSight through the uniform operation and maintenance agent (UOA) server. Therefore, you need to configure UOA server connection information on the ICS server, and add the ICS server's alarm resource package on the UOA server.

Prerequisite

The UOA server has been installed and is running properly.

Configuration on the UOA Server

  1. Log in to the UOA server as the uoa user.
  2. Stop the UOA service.

    cd $UOA_Server/shell

    uoa_stop.sh

  3. Obtain the eSpace_Agent_UOA.zip file from the IPCCV200R001C60_PUBLIC.zip > UOA.zip directory, decompress the file, and perform the following operations:

    1. Copy the files in alarm/ to the $UOA_Server/alarm/ directory.
    2. Copy the files in templates/ to the $UOA_Server/templates/ directory.

      The Agent server and ICS server share a template file. If the template file has been uploaded for one of them, you do not need to upload it again for the other.

      NOTE:
      • Ensure that the UOA user has the read, write, and execute permissions on the copied files.
      • In the preceding directories, $UOA_Server is the installation directory of the UOA server.

  4. Set the IP address of the ICS server in the $UOA_Server/cfg/system/adapter.acl file. The configuration results are displayed in bold as follows:

    10.10.10.130
    NOTE:

    When you need to configure multiple IP addresses, separate them in different lines.

  5. Start the UOA service.

    cd $UOA_Server/shell

    uoa_start.sh

Configuration on the ICS Server

  1. Log in to the ICS server as the prometheus user.
  2. Open the /home/prometheus/tomcat7/webapps/icsgateway/WEB-INF/config/uoa.properties file using the vi editor and configure the parameters by referring to Table 13-7. The configuration results are displayed in bold as follows:

    ##################################UOA Config ######################## 
    #UOA Alarm Switch: on of off 
    uoa.switch = on 
    #If the path is an absolute path, the log is initialized to the absolute path.  
    #If the path is a relative path, the log is initialized to the current directory\relative path directory. 
    #If the value is null, the log is initialized to the current directory. 
    uoa.uoaLogPath = ${catalina.home}/logs/icsgateway/icsgateway_UOA_oamlib.log 
    #The alarm file is stored in the $ buffer directory/alarm directory. 
    uoa.uoaAlarmBufferPath = ${catalina.home} 
    uoa.uoaBufferSize = 1000 
    #UOA Server Ip 
    uoa.uoaServerIP = 10.10.10.10 
    #the port added 6 based on AppOMListenPort 
    uoa.uoaServerPort = 6706 
    #UOA binding Local IP address for application side 
    uoa.moduleIP = 10.10.10.130 
    uoa.modulePort = 0 
     
     
    # Module Version 
    uoa.moduleVersion=V200R001 
     
     
    # Element Type for ICS Gateway 
    uoa.netEleType.icsGateway=30521 
    # Element Name for ICS Gateway 
    uoa.netEleName.icsGateway=eSpace Agent Desktop 
    # Element Id for ICS Gateway 
    uoa.netEleId.icsGateway=3052100 
    # Module Type for ICS Gateway 
    uoa.moduleType.icsGateway=3052103 
    # Module Name for ICS Gateway 
    uoa.moduleName.icsGateway=eSpace ICS Gateway     
    Table 13-7 Parameter description

    Parameter

    Description

    uoa.switch

    Indicates whether to enable the UOA alarm function. The value on indicates yes and off indicates no.

    uoa.uoaServerIP/uoa.uoaServerPort

    uoa.uoaServerIP indicates the IP address of the server where the UOA is installed. uoa.uoaServerPort indicates the number of the port connected to applications. The value of uoa.uoaServerPort equals to 6 plus the port number of the UOA for listening applications.

    uoa.moduleIP

    Indicates the IP address of the ICS server.

  3. Restart the ICS service.

Setting Protocol Parameters for DataStation

The DataStation sends alarms to the eSight through the uniform operation and maintenance agent (UOA) server. Therefore, you need to configure UOA server connection information on the DataStation, and add the DataStation's alarm resource package on the UOA server.

Prerequisite

The UOA server has been installed and is running properly.

Configuration on the UOA Server

  1. Log in to the UOA server as the uoa user.
  2. Stop the UOA service.

    cd $UOA_Server/shell

    uoa_stop.sh

  3. Obtain the datastation_UOA.zip file from the IPCCV200R001C60_PUBLIC.zip > UOA.zip directory, decompress the file, and perform the following operations:

    1. Copy the files in alarm/ to the $UOA_Server/alarm/ directory.
    2. Copy the files in templates/ to the $UOA_Server/templates/ directory.
      NOTE:
      • Ensure that the UOA user has the read, write, and execute permissions on the copied files.
      • In the preceding directories, $UOA_Server is the installation directory of the UOA server.

  4. Set the IP address of the DataStation server in the $UOA_Server/cfg/system/adapter.acl file. The configuration results are displayed in bold as follows:

    10.10.10.131
    NOTE:

    When you need to configure multiple IP addresses, separate them in different lines.

  5. Start the UOA service.

    cd $UOA_Server/shell

    uoa_start.sh

Configuration on the DataStation Server

  1. Log in to the DataStation server as the root user.
  2. Change the encoding format of alarmid_map to unix.

    cd {DataStation_home}/bin

    In the preceding command, {DataStation_home} indicates the DataStation installation directory.

    mac2unix alarmid_map

  3. Open the {DataStation_home}/bin/DSParameters.txt file using the vi editor and configure the parameters. The configuration results are displayed in bold as follows:

    uoa_enable = yes 
    send_alarm = yes 
    uoa_server_ip = 10.10.10.10 
    uoa_server_port = 6700 
    uoa_local_ip = 10.10.10.131 
    uoa_local_port = 32675
    Table 13-8 Parameter description

    Parameter

    Description

    uoa_enable

    Indicates whether to enable the UOA alarm function. The value on indicates yes and off indicates no.

    send_alarm

    Indicates whether to send alarms to the UOA. Two options are available: on (enable) and off (disable).

    uoa_server_ip/uoa_server_port

    uoa_server_ip indicates the IP address of the server where the UOA is installed. uoa_server_port indicates the number of the port connected to applications. The value of uoa_server_port is the port number of the UOA for listening applications.

    uoa_local_ip/uoa_local_port

    uoa_local_ip indicates the IP address of the DataStation server. uoa_local_port indicates the number of an available port on the DataStation server.

    NOTE:

    After the alarm function is enabled, the following alarms take effect by default:

    • FTP disconnection alarm
    • Database disconnection alarm

    To make other alarms take effect, enable them in the {DataStation_home}/bin/DSParameters.txt file and restart the DataStation service.

  4. Restart the DataStation service.

Setting Protocol Parameters for CMS (TestTool mode)

The CMS server sends alarms to the eSight through the UOA server. Therefore, you need to configure UOA server connection information on the CMS server, and add the CMS server's alarm resource package on the UOA server.

Prerequisite

The UOA server is running properly.

Configuration on the UOA Server

  1. Log in to the UOA server as the uoa user.
  2. Stop the UOA service.

    cd $UOA_Server/shell

    uoa_stop.sh

  3. Obtain the eSpace_CMS_UOA.zip file from the IPCCV200R001C60_PUBLIC.zip > UOA.zip directory, decompress the file, and perform the following operations:

    1. Copy the files in alarm/ to the $UOA_Server/alarm/ directory.
    2. Copy the files in templates/ to the $UOA_Server/templates/ directory.
      NOTE:
      • Ensure that the UOA user has the read, write, and execute permissions on the copied files.
      • In the preceding directories, $UOA_Server is the installation directory of the UOA server.

  4. Obtain the eSpace_Agent_UOA.zip file from the IPCCV200R001C60_PUBLIC.zip > UOA.zip directory, decompress the file, and perform the following operations:

    1. Copy the files in alarm/ to the $UOA_Server/alarm/ directory.
    2. Copy the files in templates/ to the $UOA_Server/templates/ directory.
      NOTE:
      • Ensure that the UOA user has the read, write, and execute permissions on the copied files.
      • In the preceding directories, $UOA_Server is the installation directory of the UOA server.

  5. Set the IP address of the CMS server in the $UOA_Server/cfg/system/adapter.acl file. The configuration results are displayed in bold as follows:

    As the CMS Client, CMS Gateway, and Agent Gateway share an external IP address, only one IP address needs to be configured here.

    10.10.10.118
    NOTE:

    When you need to configure multiple IP addresses, separate them in different lines.

  6. Start the UOA service.

    cd $UOA_Server/shell

    uoa_start.sh

Configuration on the CMS Server

  1. Log in to the CMS server as the CMS installation user.
  2. Configure the CMS Client to automatically report alarms.

    1. Go to /home/cms/tomcat7/webapps/cmsclient/WEB-INF/classes, open the bme.properties file, and determine whether to enable UOA connection.
      ... 
      uoa.connected.on-off=on 
      ...
      Table 13-9 Parameter description

      Parameter

      Description

      uoa.connected.on-off

      Indicates whether to enable UOA connection. The options are as follows:

      • on: enable
      • off: disable
    2. Access the /home/cms/tomcat7/webapps/cmsclient/WEB-INF/classes directory and configure parameters, such as UOA Server IP, UOA Port, and CMS localIP in the bme.basic.properties file.
      #the address of UOA,cannot be 127.0.0.1,nonsupport asterisk wildcard 
      om.global.agentIP = 10.10.10.10 
      #the port of UOA,default value is 6706,nonsupport asterisk wildcard 
      om.global.agentPort = 6706 
      #local ip address ,cannot be 127.0.0.1,nonsupport asterisk wildcard 
      om.global.localIP = 10.10.10.118 
      #local binding port ,default value is 0 
      om.global.localPort=0 
      #local binding port ,default value is 0 
      om.global.localPort=0 
      #host name 
      om.global.hostName=X00204706 
      #module configuration, the meaning of name is module name, the meaning of index is module priority 
      om.module.name=CMS 
      om.module.index=1 
      #module is need register default is:true 
      om.module.isNeedRegister=true 
      #module type 
      om.module.moduleType=3051201 
      #module version 
      om.module.moduleVer=V200R001 
      #1-single model 2-double machine hot spare 3-double machine hot spare 4-cluster model 
      om.module.workingMode=1 
      #1-primary  2-backup.while workingMode=2 effect 
      om.module.workStatus=1 
      #net element name 
      om.module.netEleName=CMS 
      #attach net element id 
      om.module.netEleID=30512 
      #while WorkingMode=2,fill in double machine fluctuate ip address.while WorkingMode=1,fill in local ip address. 
      om.module.IP = 172.16.5.128
      Table 13-10 Parameter description

      Parameter

      Description

      om.global.agentIP/om.global.agentPort

      om.global.agentIP indicates the IP address of the server where the UOA is installed. om.global.agentPort indicates the number of the port connected to applications. The value of om.global.agentPort equals to 6 plus the port number of the UOA for listening applications.

      om.global.localIP

      Indicates the CMS server IP address.

      om.module.IP

      • For the CMS single-node system, set om.module.IP to the CMS server IP address.
      • For the CMS two-node cluster, set om.module.IP to the floating IP address.

  3. Configure the CMS Gateway to automatically report alarms.

    1. Open the /home/cms/tomcat7/webapps/cmsgateway/WEB-INF/config/uoa.propertiesfile using the vi editor and configure the parameters by referring to Table 13-11. The configuration results are displayed in bold as follows:
      #UOA Alarm Switch: ON or OFF 
      uoa.switch = on 
      #If the path is an absolute path, the log is initialized to the absolute path.  
      #If the path is a relative path, the log is initialized to the current directory\relative path directory. 
      #If the value is null, the log is initialized to the current directory. 
      uoa.uoaLogPath = ${catalina.home}/logs/cmsgateway/cmsgateway_UOA_oamlib.log 
      #The alarm file is stored in the $ buffer directory/alarm directory. 
      uoa.uoaAlarmBufferPath = ${catalina.home}/logs/uoa 
      uoa.uoaBufferSize = 1000 
      #UOA Server Ip 
      uoa.uoaServerIP = 10.10.10.10 
      #the port added 6 based on AppOMListenPort  
      uoa.uoaServerPort = 6706 
      #UOA binding Local IP address for application side 
      uoa.moduleIP = 10.10.10.118 
      uoa.modulePort = 0 
       
      # Module Version 
      uoa.moduleVersion=V200R001
      Table 13-11 Parameter description

      Parameter

      Description

      uoa.uoaServerIP/uoa.uoaServerPort

      uoa.uoaServerIP indicates the IP address of the server where the UOA is installed. uoa.uoaServerPort indicates the number of the port connected to applications. The value of uoa.uoaServerPort equals to 6 plus the port number of the UOA for listening applications.

      om.module.IP

      • For the CMS single-node system, set om.module.IP to the CMS server IP address.
      • For the CMS two-node cluster, set om.module.IP to the floating IP address.

  4. Configure the Agent Gateway to automatically report alarms.

    1. Open the /home/elpis/tomcat7/webapps/agentgateway/WEB-INF/config/uoa.properties file using the vi editor and configure the parameters by referring to Table 13-12. The configuration results are displayed in bold as follows:
      ##################################UOA Config ######################## 
      #UOA Alarm Switch: ON or OFF 
      uoa.switch = on 
      #If the path is an absolute path, the log is initialized to the absolute path.  
      #If the path is a relative path, the log is initialized to the current directory\relative path directory. 
      #If the value is null, the log is initialized to the current directory. 
      uoa.uoaLogPath = ${catalina.home}/logs/agentgateway/agentgateway_UOA_oamlib.log 
      #The alarm file is stored in the $ buffer directory/alarm directory. 
      uoa.uoaAlarmBufferPath = ${catalina.home}/logs/uoa 
      uoa.uoaBufferSize = 1000 
      #UOA Server Ip 
      uoa.uoaServerIP = 10.10.10.10 
      #the port added 6 based on AppOMListenPort  
      uoa.uoaServerPort = 6706 
      #UOA binding Local IP address for application side 
      uoa.moduleIP = 10.10.10.116 
      uoa.modulePort = 0 
       
       
      # Module Version 
      uoa.moduleVersion=V200R001 
       
       
      # Element Type for Agent Gateway 
      uoa.netEleType.agentGateway=30521 
      # Element Name for Agent Gateway 
      uoa.netEleName.agentGateway=eSpace Agent Desktop 
      # Element Id for Agent Gateway 
      uoa.netEleId.agentGateway=3052100 
      # Module Type for Agent Gateway 
      uoa.moduleType.agentGateway=3052102 
      # Module Name for Agent Gateway 
      uoa.moduleName.agentGateway=eSpace Agent Gateway
      Table 13-12 Parameter description

      Parameter

      Description

      uoa.switch

      Indicates whether to enable the UOA alarm function. The value on indicates yes and off indicates no.

      uoa.uoaServerIP/uoa.uoaServerPort

      uoa.uoaServerIP indicates the IP address of the server where the UOA is installed. uoa.uoaServerPort indicates the number of the port connected to applications. The value of uoa.uoaServerPort equals to 6 plus the port number of the UOA for listening applications.

      uoa.moduleIP

      Indicates the IP address of the Agent server.

  5. Restart the CMS service.

Setting Protocol Parameters for CMS (RestWebservice mode)

The CMS server sends alarms to the eSight through the UOA server. Therefore, you need to configure UOA server connection information on the CMS server, and add the CMS server's alarm resource package on the UOA server.

Prerequisite

The UOA server is running properly.

Configuration on the UOA Server

  1. Log in to the UOA server as the uoa user.
  2. Stop the UOA service.

    cd $UOA_Server/shell

    uoa_stop.sh

  3. Obtain the eSpace_CMS_UOA.zip file from the IPCCV200R001C60_PUBLIC.zip > UOA.zip directory, decompress the file, and perform the following operations:

    1. Copy the files in alarm/ to the $UOA_Server/alarm/ directory.
    2. Copy the files in templates/ to the $UOA_Server/templates/ directory.
      NOTE:
      • Ensure that the UOA user has the read, write, and execute permissions on the copied files.
      • In the preceding directories, $UOA_Server is the installation directory of the UOA server.

  4. Set the IP address of the CMS server in the $UOA_Server/cfg/system/adapter.acl file. The configuration results are displayed in bold as follows:

    10.10.10.118
    NOTE:

    When you need to configure multiple IP addresses, separate them in different lines.

  5. Start the UOA service.

    cd $UOA_Server/shell

    uoa_start.sh

Configuration on the CMS Server

  1. Log in to the CMS server as the CMS installation user.
  2. Open the /home/cms/tomcat7/webapps/cmsgateway/WEB-INF/config/uoa.propertiesfile using the vi editor and configure the parameters by referring to Table 13-13. The configuration results are displayed in bold as follows:

    #UOA Alarm Switch: ON or OFF 
    uoa.switch = on 
    #If the path is an absolute path, the log is initialized to the absolute path.  
    #If the path is a relative path, the log is initialized to the current directory\relative path directory. 
    #If the value is null, the log is initialized to the current directory. 
    uoa.uoaLogPath = ${catalina.home}/logs/cmsgateway/cmsgateway_UOA_oamlib.log 
    #The alarm file is stored in the $ buffer directory/alarm directory. 
    uoa.uoaAlarmBufferPath = ${catalina.home}/logs/uoa 
    uoa.uoaBufferSize = 1000 
    #UOA Server Ip 
    uoa.uoaServerIP = 10.10.10.10 
    #the port added 6 based on AppOMListenPort  
    uoa.uoaServerPort = 6706 
    #UOA binding Local IP address for application side 
    uoa.moduleIP = 10.10.10.118 
    uoa.modulePort = 0 
     
    # Module Version 
    uoa.moduleVersion=V200R001
    Table 13-13 Parameter description

    Parameter

    Description

    uoa.uoaServerIP/uoa.uoaServerPort

    uoa.uoaServerIP indicates the IP address of the server where the UOA is installed. uoa.uoaServerPort indicates the number of the port connected to applications. The value of uoa.uoaServerPort equals to 6 plus the port number of the UOA for listening applications.

    om.module.IP

    • For the CMS single-node system, set om.module.IP to the CMS server IP address.
    • For the CMS two-node cluster, set om.module.IP to the floating IP address.

  3. Restart the CMS service.

Setting Protocol Parameters for EDS

The EDS server sends alarms to the eSight through the uniform operation and maintenance eds (UOA) server. Therefore, you need to configure UOA server connection information on the EDS server, and add the EDS server's alarm resource package on the UOA server.

Prerequisite

The UOA server has been installed and is running properly.

Configuration on the UOA Server

  1. Log in to the UOA server as the uoa user.
  2. Stop the UOA service.

    cd $UOA_Server/shell

    uoa_stop.sh

  3. Obtain the EDS_UOA.zip file from the IPCCV200R001C60_PUBLIC.zip > UOA.zip directory, decompress the file, and perform the following operations:

    1. Copy the files in alarm/ to the $UOA_Server/alarm/ directory.
    2. Copy the files in templates/ to the $UOA_Server/templates/ directory.
      NOTE:
      • Ensure that the UOA user has the read, and write permissions on the copied files.
      • In the preceding directories, $UOA_Server is the installation directory of the UOA server.

  4. Set the IP address of the EDS server in the $UOA_Server/cfg/system/adapter.acl file. The configuration results are displayed in bold as follows:

    10.10.10.182
    NOTE:

    When you need to configure multiple IP addresses, separate them in different lines.

  5. Start the UOA service.

    cd $UOA_Server/shell

    uoa_start.sh

Configuration on the EDS Server

  1. Log in to the EDS server as the eds user.
  2. Open the /home/eds/tomcat7/webapps/eds/WEB-INF/conf file using the vi editor and configure the parameters. The configuration results are displayed in bold as follows:

     
    # uoa config 
    uoa.flag            = on 
    uoa.serverIp        = 10.10.10.10 
    uoa.serverPort      = 6706 
    uoa.moduleIp        = 10.10.10.182 
    uoa.modulePort      = 0
    Table 13-14 Parameter description

    Parameter

    Description

    uoa.flag

    Indicates whether to enable the UOA alarm information. The value on indicates yes and off indicates no.

    uoa.serverIp/uoa.serverPort

    A combination of the IP address of the UOA server and the port number that the UOA server uses to connect to the Agent. The port number is 6 plus the port number that the UOA server uses to listen on the EDS.

    uoa.moduleIp

    A combination of the IP address of the EDS server.

  3. Restart the EDS service.

Setting Protocol Parameters for CTI (R5)

Set protocol parameters on CTIs (R5) so that the CTIs (R5) can properly connect to the eSight.

Prerequisites (R5)

The prerequisites for CTI platform components to connect to the eSight, connection process, and points for attention.

CTI platform

  • The components of the CTI platform have been installed and are running properly.
  • The database script that is provided in the OAS&OMD has been loaded to the UIDB of the CTI platform.
    • For the Oracle database: oas_access_platform_db.orasql
    • For the DB2 database: oas_access_platform_db.db2sql

UOA

The UOA is installed and runs properly.

Obtaining OAS and OMD Software Packages

  1. Visit http://support.huawei.com/enterprise.
  2. Click Log In. In the page that is displayed, enter the account name and password, and click Log In.
  3. After login, enter eSpace CC in the search box.
  4. Click the path to enter the product documentation page.
  5. Click the Software tab page to download your desired software.

Obtain the OAS and OMD software packages ICDV300R005C*_OAM_ICD, and obtain CTI platform product information that must be configured on the UOA side from the software packages, as shown in Table 13-15.

NOTE:
  • The OAS and OMD software packages vary according to the Windows, AIX, and SUSE Linux operating systems.
  • UOA configuration information varies according to CTI platform versions. You must obtain the UOA configuration file based on the version of the CTI platform. The configuration file in the ICDV300R004 directory is applicable to CTI platforms V300R004 and V300R005.

    The OAS and OMD software that is integrated in the installation package of the CTI platform can be installed in Windows and SUSE Linux.

Table 13-15 Description of OAS and OMD installation packages

Directory

Installation Package

Description

OAS and OMD installation packages

OAS

aix unix install

oas_install.tar.gz

OAS installation package for AIX5.1 and AIX5.3

suse linux install

oas_install.tar.gz

OAS installation package for SUSE Linux 10 and SUSE Linux 11

win32 install

OAS Setup.exe

OAS installation package for Windows

OMD

aix unix install

omd.tar.gz

OMD installation package for AIX5.1 and AIX5.3

suse linux install

omd.tar.gz

OMD installation package for SUSE Linux 10 and SUSE Linux 11

win32 install

OMD Setup.exe

OMD installation package for Windows

DB_SCRIPT

OAS Access CTI Platform DB Script\DB2

oas_access_platform_db.db2sql

Script loaded to the DB2 database of the CTI platform when the OAS monitors the CTI platform that is loaded with the customer service

oas_access_service_db.db2sql

Script loaded to the DB2 database of the customer service when the OAS monitors the CTI platform that is loaded with the customer service

OAS Access CTI Platform DB Script\ORACLE

oas_access_platform_db.orasql

Script loaded to the Oracle database of the CTI platform when the OAS monitors the CTI platform that is loaded with the customer service

oas_access_service_db.orasql

Script loaded to the Oracle database of the customer service when the OAS monitors the CTI platform that is loaded with the customer service

NOTE:

When the OAS monitors the CTI platform that is loaded with the customer service, you need to import the corresponding scripts to the user information database (UIDB) of the CTI platform and the ICDMAIN database of the customer service.

When the OAS monitors the CTI platform that is loaded with the RBT service, no script needs to be imported.

UOA configuration file

UOA Config

ICDV300R002

ICDV300R003

ICDV300R004

alarm

It contains the alarm resource files of CTI platform components. According to the reported alarm ID, the UOA queries the relevant static information, fills the information in an alarm, and reports the alarm to the eSight.

log

It contains the log resource files of CTI platform components. According to the reported log ID, the UOA queries the relevant static information, fills the information in an alarm, and reports the alarm to the eSight.

mib

It contains the configuration files of the Mib interfaces of the CTI platform. These files provide detailed description of the network management interfaces of the CTI platform for the UOA.

perftaskfiles

It contains the configuration files of the performance statistics tasks of the CTI platform. The configuration items include the measurement units supported by NEs, measurement objects, measurement indexes, measurement granularity periods, and measurement task plans.

templates

It contains the configuration file of the CTI platform. The file provides the configuration information about all the components to be managed by the UOA.

trace

When the iTrace is used to trace messages of the CTI platform, use the following directories to replace the corresponding directories in the iTrace client:

  • config: stores tracing files.
  • neapi: stores tracing plug-ins.
NOTE:

Before you use the iTrace to trace the messages of the CTI platform, make sure that the iTrace is installed. For the method of installing the iTrace, see the installation guide of the iTrace.

Currently, messages of the CTI platform are traced by the ICDDebug. Do not use the iTrace.

Obtaining ICDComm Installation Packages

  1. Visit http://support.huawei.com/enterprise.
  2. Click Log In. In the page that is displayed, enter the account name and password, and click Log In.
  3. After login, enter eSpace CC in the search box of the Product Support tab page. A path is displayed under the search box.
  4. Click the path to enter the product documentation page.
  5. Click the Software tab page to download your desired software.

Obtain the CTI platform installation package, which contains ICDComm installation packages, as shown in Table 13-16.

NOTE:
  • The ICDComm installation packages vary according to the Windows, AIX, and SUSE Linux operating systems.
  • The version of the ICDComm installed on the OAS must be the same as the versions of the ICDComms used by the OMD and CTI platform components that are managed by the OMD.
Table 13-16 Description of ICDComm installation packages

Directory

Installation Package

Description

ICDV300R005C*_AIX_ICD

ICDV300R005C*_AIX_ICD.zip

ICDComm installation package of the call center for AIX5.1 and AIX5.3

ICDV300R005C*_AIX_AIP

ICDV300R005C*_AIX_AIP.zip

ICDComm installation package of CTI platform for AIX5.1 and AIX5.3

ICDV300R005C*_LINUX_ICD

ICDV300R005C*_LINUX_ICD.zip

ICDComm installation package of the call center for SUSE Linux 10 and SUSE Linux 11

ICDV300R005C*_LINUX_AIP

ICDV300R005C*_LINUX_AIP.zip

ICDComm installation package of CTI platform for SUSE Linux 10 and SUSE Linux 11

ICDV300R005C*_WIN_ICD

ICDV300R005C*_WIN_ICD.zip

ICDComm installation package of the call center for Windows

ICDV300R005C*_WIN_AIP

ICDV300R005C*_WIN_AIP.zip

ICDComm installation package of CTI platform for Windows

Required Resources

Before configuring the components described in Table 13-17, you need to collect parameter values according to the actual situation. When configuring the components, use the collected parameter values.

Table 13-17 Parameters for connecting the CTI platform to the eSight

Component

Parameter

Example

UOA

-

-

OAS

IP addresses of the active CCS and standby CCS.

IP address of the active CCS: 10.70.104.203

IP address of the standby CCS: 10.70.104.118

Service data source name configured on the Web configuration console, pointing to the ICDMAIN database of customer services.

icdmain

IP address for the UOA to provide services for the application access point (AAP).

10.70.104.172

Listen port for the UOA to provide services for the AAP.

6700

OMD on a CTI platform host

IP address bound with the ICDComm on the host where the OAS is located.

10.70.101.140

eSight

IP address of the host where the UOA that registers on the CTI platform is located.

10.70.101.190

Port number that the UOA uses to connect to the eSight.

6600

Configuring Information in the UOA (R5)

How to configure information in the UOA when CTI platform components connect to the eSight.

Context

After configuring the information about the CTI platform in the UOA, you must restart the UOA for the configurations to take effect.

Procedure

  1. Log in to the computer where the UOA is located.

    If the UOA is installed in the computer that runs UNIX or SUSE Linux, log in to the computer as the user who installs the UOA.

  2. Obtain the UOA installation packages described in Table 13-15, and then copy the configuration file that matches the CTI platform version from the UOA Config directory to the corresponding directory in $UOA_RUN_ROOT\UOA\data.

    Assume that the version of the monitored CTI platform is of V300R004 series. Copy all the files in alarm in the UOA Config\ICDV300R004 directory to $UOA_RUN_ROOT\UOA\data\alarm.

    NOTE:

    $UOA_RUN_ROOT is the installation directory of the UOA.

    If the system displays a message asking whether to replace existing files when you copy files, pay attention to the following:

    • If the version of the UOA is of UOAV100R001C01 series and you copy the files in templates, click No. That is, do not replace the productsconfig.xml file.
    • In other cases, click Yes.

  3. (Optional) Modify the productsconfig.xml file in $UOA_RUN_ROOT\UOA\data\templates.

    NOTE:

    The productsconfig.xml file needs to be modified only when the version of the UOA is of UOAV100R001C01 series.

    Add the following characters in bold to the <products> section in the productsconfig.xml file:

    <products> 
    <!--Product: example--> 
    <product productname="uoa" productConfigFileName="uoa_productconfig.xml"/><product productname="cti" productConfigFileName="cti_productconfig.xml"/> 
    </products>     

  4. Restart the UOA for the configurations to take effect.

    • Restarting the UOA in Windows

      To restart the UOA in Windows, double-click the shortcut icon of the UOA on the desktop, or choose Start > Programs > huawei, and then select UOA.

    • Restarting the UOA in UNIX or SUSE Linux

      To restart the UOA in UNIX or SUSE Linux, log in to the computer that runs UNIX or SUSE Linux as the user who installs the UOA, and then run the following command:

      uoa_start.sh

Installing and Configuring the OAS (R5)

The following sections describe the procedures for installing the OAS in Windows and UNIX or Linux.

Prerequisites

  • The CTI platform has been installed.
  • The MainAst has been installed.

Context

The OAS must be installed on the CTI Server as planned and uses the ICDComm configured for the CTI Server. Therefore, you do not need to install the ICDComm for the OAS.

Procedure

  • Installing and Configuring the OAS in Windows

    To install the OAS, do as follows:

    1. Obtain the OAS installation package described in Table 13-15, and double-click OAS Setup.exe to run the installation program.
    2. Select a language type in the Choose Setup Language dialog box.
      Figure 13-1 Selecting a language type
    3. Click Yes in the License Agreement dialog box to continue the installation.
    4. Set User Name, Company Name, and Serial Number in the Customer Information dialog box.

      The default values of User Name, Company Name, and Serial Number can be retained.

      Figure 13-2 Setting customer information
    5. Select a device type in the Select Device dialog box, as shown in Figure 13-3.
      • If the CTI platform is loaded with the RBT service, select CRBT.
      • If the CTI platform is loaded with the customer service, select ICD
        Figure 13-3 Selecting a device type
    6. In the Select version dialog box, select the version of the CTI platform that is monitored, as shown in Figure 13-4.
      Figure 13-4 Selecting a platform version
    7. Set a path for installing the OAS in the Choose Destination Location dialog box, as shown in Figure 13-5.
      Figure 13-5 Path for installing the OAS
    8. Click Next to start the installation.

      During the installation, if the system displays the message shown in Figure 13-6, it indicates that the dynamic link library (DLL) for installing the OAS exists in the system and there are processes that use the DLL currently. In this case, you need to stop the processes that use the DLL, and then click Retry. Stop the processes until the installation is successful; otherwise, the OAS does not run properly.

      Figure 13-6 Detecting the locked file
    9. After the installation, double-click the icon of the OAS, and then configure the basic information about the OAS.
      NOTE:

      The OAS service must be stopped before the OAS is configured.

      1. In the running window of the OAS, choose System > Stop or double-click the icon on the tool bar to stop the OAS service.
      2. Select Config in the running window of the OAS.

        The Base Config window, as shown in Figure 1-8, is displayed.

        Figure 13-7 Figure 1-7 Basic configuration of the OAS
      3. Set the information about the connection between the OAS and the CCS on the monitored CTI platform and the connection between the OAS and the UOA according to the description provided in Table 13-18.
        Table 13-18 Basic configuration

        Parameter

        Description

        Setting

        CCS Config

        Connect to CCS

        Indicates whether to connect to the CCS to obtain statistics.

        Whether the OAS should be connected to the CCS.

        If this option is selected, it indicates that the OAS must be connected to the CCS; otherwise, the OAS does not need to be connected to the CCS.

        Set the connection to the CCS.

        NOTE:

        Make sure that the OAS can successfully connect to the CCS, and log in to the Web configuration console as a system user with the configuration permission, choose Web Configuration Console > System Configuration > Basic Configuration > Primary Module Information, and then set the IP address of the alert server to the IP address bound with the ICDComm on the OAS host.

        Master IP

        IP address of the active CCS.

        The value of Master IP must be the IP address of the active CCS on the CTI platform.

        Standby IP

        IP address of the standby CCS.

        The value of Standby IP must be the IP address of the standby CCS on the CTI platform.

        ServiceDB name

        Name of the data source for accessing services.

        The data source specified by this parameter must be the data source specified by Third-party data source in data source settings on the web configuration console.

        NOTE:

        The service data source must be loaded with the script oas_access_service_db.orasql (for Oracle database) or oas_access_service_db.db2sql (for DB2 database).

        UOA Config

        Connect to UOA

        Whether the OAS should be connected to the UOA.

        If the OAS is not connected to the eSight through the UOA, the UOA does not need to be connected.

        OAS IP

        IP address bound with the ICDComm on the OAS host.

        -

        UOA IP

        IP address of the host where the UOA resides.

        The value of UOA IP must be the IP address that is set to be connected to the AAP when the UOA is installed.

        UOA port

        Port used by the UOA to monitor the OAS.

        The default value is 6700.

        The value of UOA port must be the port number that is set to be connected to the AAP when the UOA is installed.

        NOTE:

        If the version of the UOA interconnected with the OAS is later than V100R001C02B132, the port number on the OAS side is the port number on the UOA side plus 6.

      4. Click OK to finish the configuration.
  • Installing and Configuring the OAS in UNIX/Linux

    To install and configure the OAS, do as follows:

    1. Obtain the OAS installation package in Table 1-15 matching the operating system, and then upload the installation package (for example, oas_install.tar.gz) to /home/icd on the CTI host in binary mode.
    2. Log in to the CTI host as the icd.
    3. Run the gunzip oas_install.tar.gz command to decompress the installation package.
    4. Run the tar -xvf oas_install.tar command to decompress the oas_install.tar package.
    5. Run the cd oas_install command to access the installation directory.
    6. Run the ./oas_in.sh command to run the installation script.

      Table 13-19 describes the related parameters for configuring the OAS.

      Table 13-19 Parameters for configuring the OAS in UNIX

      Parameter

      Description

      Setting

      Please select the language [0:English, 1:Chinese]:

      Language of the OAS system.

      The value 0 indicates the English version.

      The value 1 indicates the Chinese version.

      Please select the type of CTIPlatform [CRBT/ICD]:

      Type of the CTI platform.

      • If the CTI platform is loaded with the RBT service, select CRBT.
      • If the CTI platform is loaded with the customer service, select ICD.

      Please select the version of CTIPlatform [ICDV300R002/ICDV300R003/ICDV300R004]

      Version of the CTI platform.

      • To monitor the ICDV300R002 platform, select ICDV300R002.
      • To monitor the ICDV300R003 platform, select ICDV300R003.
      • To monitor the ICDV300R004 platform, select ICDV300R004.

      Please input OAS install directory[/home/icd/oas_install/oasdir]

      Installation directory of the OAS.

      Enter the OAS installation directory.

      Do you connect with UOA? [yes/no]

      Whether to connect the UOA.

      • The value yes indicates that the OAS connects to the UOA.
      • The value no indicates that the OAS does not connect to the UOA.

      If the OAS is not connected to the eSight through the UOA, the UOA does not need to be connected.

      Please input the UOA IP

      UOA IP:

      PORT[6700]

      IP address of the UOA if the UOA is connected.

      Port number of the UOA.

      Enter the IP address and port number of the UOA.

      The IP address and port number must be the IP address and port number that are set to be connected to the AAP when the UOA is installed.

      NOTE:

      If the version of the UOA interconnected with the OAS is later than V100R001C02B132, the port number on the OAS side is the port number on the UOA side plus 6.

      Please input OAS local address

      IP[10.71.111.44]

      IP address bound with the ICDComm on the OAS host.

      -

      Do you connect with CCS? [yes/no]

      Whether to connect the CCS.

      To connect to the CCS, select yes; otherwise, select no.

      Set the connection to the CCS.

      NOTE:

      Make sure that the OAS can successfully connect to the CCS, and log in to the Web configuration console as a system user with the configuration permission, choose Web Configuration Console > System Configuration > Basic Configuration > Primary Module Information, and then set the IP address of the alert server to the IP address bound with the ICDComm on the OAS host.

      Please input CCS master IP

      CCS Master IP

      IP address of the active CCS if the CCS is connected.

      Enter the IP address of the active CCS.

      Please input CCS slave IP

      CCS Slave IP

      IP address of the standby CCS.

      Enter the IP address of the standby CCS.

      If the standby CCS does not exist, do not set this parameter.

      ServiceDB Name[icdmain]

      Name of the data source for accessing services.

      The data source specified by this parameter must be the data source specified by Third-party data source in data source settings on the web configuration console.

      NOTE:

      The service data source must be loaded with the script oas_access_service_db.orasql (for Oracle database) or oas_access_service_db.db2sql (for DB2 database).

      Are you sure these parameters are correct? [yes/no/quit]

      Ensure whether the configured parameters are correct.

      • Click yes to save the configuration.
      • Click no to reconfigure the information.
      • Click quit to end the configuration.
    7. After saving the configuration, run the source .cshrc command in the $HOME directory of the OAS installation user for the environment variables required by the OAS to take effect.

Starting the OAS (R5)

The following sections describe the procedures for installing the OAS in Windows and UNIX or Linux.

Procedure

  • Starting the OAS in Windows

    On the OAS host, double-click the OAS icon on the desktop to start the OAS.

    After the OAS is started, the system displays the window shown in Figure 13-8 if the following conditions are met:

    • The OAS is correctly installed and configured.
    • The UOA runs properly.
    • The CTI platform runs properly.
    Figure 13-8 OAS running window

  • Starting the OAS in UNIX or Linux

    To start the OAS in UNIX or Linux, do as follows:

    1. Log in to the OAS host as the installation user of the OAS.
    2. Run the oas& command to start the OAS.
    3. After the OAS is started, run the p command to check whether the OAS process exists. If the system displays the information shown in Figure 13-9, the OAS process exists.
      Figure 13-9 Starting the OAS

      NOTE:

      To stop the OAS under the UNIX prompt, you can use run the kill command.

      Enter the process querying command p under the UNIX prompt to view the process number of the OAS. Then run the command kill process number of the OAS.

Installing the OMD (R5)

The following sections describe the procedures for installing the OMD in Windows and UNIX or Linux.

Context

The OMD must be installed on the server where CTI platform components are located, except the database server.

Procedure

  • Installing the OMD in Windows

    To install the OMD, do as follows:

    1. Obtain the OMD installation package described in Table 13-15, and then double-click OMD Setup.exe to run the installation program.
    2. Click Yes in the License Agreement dialog box to continue the installation.
    3. Set User Name, Company Name, and Serial Number in the Customer Information dialog box.

      The default values of User Name, Company Name, and Serial Number can be retained.

      Figure 13-10 OMD customer information

    4. Select a device type for the monitored CTI platform in the Select Device dialog box, as shown in Figure 13-11.

      The device type must be the same as the device type that is selected when the OAS is installed.

      • If the CTI platform is loaded with the RBT service, select CRBT.
      • If the CTI platform is loaded with the customer service, select ICD.
      Figure 13-11 Selecting a device type

    5. Set the path for installing the OMD in the Choose Destination Location dialog box, as shown in Figure 13-12.
      Figure 13-12 Selecting a destination folder

    6. Click Next until the installation is complete.
  • Installing the OMD in UNIX/Linux

    To install the OMD, do as follows:

    1. After obtaining the OMD installation package described in Prerequisites (R5), upload the omd.tar.gz package matching the operating system to the installation directory of the CTI platform in binary mode.
    2. Run the gunzip omd.tar.gz|tar -xvf omd.tar command to decompress the installation package.
    3. Set the environment variables required for running the OMD.
      NOTE:

      Generally, the system automatically sets the environment variables for running the OMD during the installation of the OMD. If the environment variables cannot be set because an exception occurs during the installation of the OMD, set the environment variables as follows:

      1. Access the HOME directory of the CTI platform user icd.
      2. Run the vi .cshrc command to modify the .cshrc file.
      3. Add the environment variable OMDDIR to the end of the .cshrc file.

        The value of OMDDIR is the same as the value of ICDDIR. That is, the value is the absolute path of the icddir directory for installing the OMD, as shown in Figure 13-13.

        Figure 13-13 Setting the environment variable for the OMD

      4. Run the source .cshrc command for the environment variable to take effect.

Configuring ICDComms (R5)

This topic describes how to configure NAT conversion information for ICDComms in Windows and UNIX or Linux.

Background Information

The version of the ICDComm on the OMD must be the same as the versions of the ICDComms on the OAS and the devices managed by the OAS.

ICDComms are installed during CTI platform component installation. You do not need to install ICDComms separately.

The OAS is installed on the intranet of the monitored CTI platform. If some monitored components are isolated from the intranet by using firewalls, you must configure NAT conversion information in the ICDComms on the computers where the components are located. The OMD can communicate with the OAS only after NAT conversion information is configured.

The following is an example of NAT conversion information.

Figure 13-14 IP address mapping

As shown in Figure 13-14:

  • The IP address of the ICDComm on the OAS is 10.10.10.1.
  • The IP address of the ICDComm Portal on the OMD is 192.168.1.2.
  • The OAS IP address is mapped to 192.168.1.1 on a firewall.
  • The OAS IP address configured in the OMD is 10.10.10.1.

Procedure

  • Configuring NAT conversion information in Windows
    1. On the computer where a component is located, open the ICDComm configuration page.

      Choose Start > Programs > HUAWEI Intelligent Call Center > HUAWEI Voice-added Service Platform > ICD communication program group > ICD configuration program to open the ICDComm configuration page. See Figure 13-15.

      Figure 13-15 ICDComm configuration

    2. Click Advanced. The NAT table configuration window appears.

      The window that appears may vary according to the version. You need to focus on the NAT table configuration window only.

    3. Right-click on the blank area in the NAT table configuration window and choose Append from the shortcut menu.
    4. In the dialog box that appears, set the destination IP address to the OAS IP address 10.10.10.1, and set the replacement IP address to the OAS IP address 192.168.1.1 mapped on the firewall. See Figure 13-16. Click OK to save the configuration.
      Figure 13-16 NAT conversion information

    5. Restart the ICDComm service for the configuration to take effect.
  • Configuring NAT conversion information in UNIX or Linux
    1. Access the directory for storing the icdcomm.cfg file.
    2. Run the vi icdcomm.cfg command.
    3. Add NAT Table = (IPb,NATIPb), for example, NAT Table = (10.71.111.44,10.9.21.8).
    4. Run the :wq command to save the configuration and exit.
    5. Restart the ICDComm service for the configuration to take effect.

Configuring NEs to Be Monitored by the OMD (R5)

The following sections describe the procedures for configuring NEs to be monitored by the OMD in Windows and UNIX or Linux.

Context

The OMD can monitor NEs only after those NEs are configured.

NOTE:

The type of the devices that the OMD can monitor depends on the platform device type that is selected when the OMD is installed.

After configuring the NEs to be monitored by the OMD, restart the OMD for the configuration to take effect. For details, see Starting the OMD (R5).

Procedure

  • Configuring the OMD in Windows

    To configure an NE, do as follows:

    1. Double-click the icon or choose Start > Program > OMD > OMD Config on the desktop to start the OMD configuration tool.

      The OMD Config - ICD window is displayed, as shown in Figure 13-17Figure 13-18.

      Figure 13-17 Configuring an NE to be monitored by the OMD

      Figure 13-18 Configuring an NE to be monitored by the OMD

    2. Set the IP address of the OAS.

      The OAS IP parameter indicates the IP address bound with the ICDComm on the OAS host that is connected to the OMD. After the OMD is started, the OMD communicates with only the OAS whose IP address is specified by the OAS IP parameter.

    3. Select an NE to be monitored by the OMD from the NE Type list box.

      The selected NEs must be the CTI platform components that are installed on the OMD host.

    4. Click Add.

      The NE Config - XXX window is displayed, as shown in Figure 13-19Figure 13-20.

      Figure 13-19 Adding a single-instance NE

      Figure 13-20 Adding a single-instance NE

    5. Set the parameters for the NE according to the description provided in Table 13-20.
      Table 13-20 Setting parameters for NEs

      Parameter

      Description

      Setting

      Common configuration items

      ProgID

      Process ID of a program.

      • The values of ProgID set for the ApLogic and DtProxy can be 12 or range from 201 to 299 or range from 2900 to 3299.
      • The values of ProgID set for the system range from 301 to 399 or range from 2500 to 2899.
      • For a single-instance NE, the default value of ProgID must be retained.
      • For a multi-instance NE, the value of ProgID must be the process ID that is used when the NE runs.

        The ApLogic, DtProxy, IVRUI system are multi-instance NEs. Except these NEs, the NEs in the list are single-instance NEs.

      Name

      Name of an NE.

      Enter the name of an NE.

      Run Mode

      Mode in which an NE runs. The options are Exe, Service, and Other.

      • Exe: Indicates that an NE runs in program interface mode.
      • Service: Indicates that an NE runs in background service mode.

      For the CCS, CTI Server, MailM, WebM, and WAS, the Run Mode parameter can be set to Exe or Service.

      For other NEs, the Run Mode parameter can be only set to Exe.

      Need OMD Start

      Flag indicating whether the OMD automatically restarts an NE. That is, whether the OMD automatically restarts a device when the OMD detects that an exception occurs in the device or that the device does not run.

      If the OMD automatically restarts the NE, select Yes; otherwise, select No.

      Select Yes or No according to the actual situation.

      NOTE:

      When an NE is monitored by the OMD and MDS or another monitoring program simultaneously, the value of the configuration item Need OMD Start set for the NE must be No in the OMD window.

      Application File

      Running file of an NE program.

      • For a program that runs in exe mode, set the parameter to the full path of an executable running file.
      • For a program runs in service mode, set the parameter to a service name.

      Special configuration items for the DtProxy

      Max Command Num

      Maximum number of command words of the DtProxy supported by the OMD.

      The default value 500 is recommended.

      The default value can be changed according to the number of command words that is set in the Dtproxy.ini file. The value must be greater than the actual number of command words.

      Config File

      Full path of the configuration file of the DtProxy.

      Click the button, and then select the dtproxy.ini file from the displayed file browsing box.

      Special configuration items of the WAS

      IP

      IP address of the computer where the WAS is installed.

      Enter an IP address.

      Port

      Port number of the computer where the WAS is installed.

      The default value 8080 is used.

      If the port number of the WAS is changed in the WAS server, the value of Port must be changed.

      User/PWD

      User name and password for logging in to the WAS.

      Enter a user name and a password according to the actual situation.

      Service name(s) Started By OMD

      Full path of the WAS.

      Click Add, and then select the startup.bat file. The startup.bat file is the running file of the WAS.

      HTTP Page(s) For To Get State

      Website address for determining whether the computer where the WAS is installed runs properly.

      Click Add, and then enter a website address.

    6. Click OK.

      The added NE is displayed in the NE group box.

  • Configuring the OMD in UNIX/Linux

    To configure the OMD, do as follows:

    1. Log in to the server where the OMD is installed as the CTI platform user icd, and then access the icddir directory of the CTI platform.
    2. Run the omdconfig command to start the OMD configuration program.

      The system displays the following information:

      % icd/bin> omdconfig 
      OAMV2.0D313 
       
      0) Quick-config 
      1) List Base Config 
      2) List Device Config 
      3) Modify Base Config 
      4) Add Device 
      5) Modify Device 
      6) Delete Device 
      7) Clear Device Config 
      q) Quits 
      Please Select (0~7 or q):     
    3. Type the serial number (SN) or letter before a configuration item to perform the corresponding operation.

      Table 13-21 describes the operations corresponding to the serial numbers.

      Table 13-21 Operations related to the configuration

      SN

      Operation

      0

      The SN corresponds to the operation of configuring NE information quickly. After typing 0, you can quickly add NEs according to the default configurations. The NEs that can be added vary with the platform types. The differences are as follows:

      • If the CTI platform is loaded with the customer service, the following NEs are added by default: CCS, CTI Server, MailM, WebM, MDS, CTI-Link, and MCP.
      • If the CTI platform is loaded with the RBT service, the following NEs are added by default: CCS, CTI Server, MDS, FEP, and MCP.

      1

      After you type 1, the system displays the configured basic information.

      2

      After you type 2, the system displays the detailed configuration information of the device.

      3

      After typing 3, you can configure the basic information according to the description provided in Table 13-22.

      4

      After typing 4, you can add NEs.

      Table 13-23 describes the information about the NEs that needs to be configured.

      NOTE:

      The NEs must be the components of the CTI platform that are installed in the computer where the OMD is located, such as the CCS, CTI Server, MailM, WebM, MDS, CTI-LinkFEP, MCP, IVRUI system, and ApLogic.

      5

      After typing 5, you can change the monitored NEs.

      6

      After typing 6, you can delete the monitored NEs.

      7

      After you type 7, the system automatically deletes all NEs.

      q

      After typing q, the configurations are saved and you exit the OMD.

      NOTE:

      When exiting the OMD, you cannot press any key until the system prompts that saving the configurations is successful.

      Table 13-22 Basic configuration information

      Parameter

      Description

      Setting

      OAS IP Address

      IP address bound with the ICDComm on the OAS host.

      -

      ICD Run Mode

      If running in ICD mode, the OMD can only start the MDS. Other programs are started by the MDS. If not running in ICD mode, the OMD can start any program that is configured to be started by the OMD.

      If the CTI platform carries customer services, click YES; otherwise, click NO.

      Max Log File Size

      Maximum size of the log file.

      The value can be 1, 2, 5, 10, or 12.

      The unit is MB.

      Log Level

      Log level.

      Log levels can be ranked from high to low as follows:

      • 0: EMERGENCY
      • 1: ALERT
      • 2: CRITICAL
      • 3: ERROR
      • 4: WARN
      • 5: NOTICE
      • 6: INFO
      • 7: DEBUG

      The OMD records the logs of the levels higher than the level specified by the Log Level parameter.

      The INFO level is recommended.

      Table 13-23 NE information

      Configuration Item

      Description

      Setting

      Common configuration items

      Please select a device type

      Name of an NE to be added.

      NE names are case sensitive. The entered NE name must be the same as the NE name that the system allows to add.

      Please input the device ProgID

      Process ID of a program.

      • The values of ProgID set for the ApLogic and DtProxy can be 12 or range from 201 to 299 or range from 2900 to 3299.
      • The values of ProgID set for the IVRUI system range from 301 to 399.
      • For a single-instance NE, the default value of ProgID must be retained.
      • For a multi-instance NE, the value of ProgID must be the process ID that is used when the NE runs.

        The ApLogic, DtProxy, IVRUI system are multi-instance NEs. Except these NEs, the NEs in the list are single-instance NEs.

      Need Start

      Flag indicating whether the OMD automatically restarts an NE. That is, whether the OMD automatically restarts a device when the OMD detects that an exception occurs in the device or that the device does not run.

      If the OMD automatically restarts the NE, set Yes; otherwise, set No.

      Select Yes or No according to the actual situation.

      NOTE:

      When an NE is monitored by the OMD and MDS or another monitoring program simultaneously, the value of the configuration item Need Start set for the NE must be No in the OMD window.

      App Full Path

      Full path of the executable file of a monitored program.

      -

      Special configuration items for the DtProxy

      Max Command Num

      Maximum number of command words of the DtProxy supported by the OMD.

      The default value 500 is recommended.

      The default value can be changed according to the number of command words that is set in the Dtproxy.ini file. The value must be greater than the actual number of command words.

      Config File

      Full path of the configuration file of the DtProxy.

      Set the full path of the dtproxy.ini file.

Starting the OMD (R5)

Procedure

  • Starting the OMD in Windows

    To start the OMD, do as follows:

    1. Double-click the shortcut icon or choose Start > Program > OMD > OMDon the desktop to start the OMD.

      If the icon is displayed on the task bar, it indicates that the OMD is started.

    2. Double-click the icon on the task bar.

      The window, as shown in Figure 13-21Figure 13-22, is displayed.

      Figure 13-21 OMD running window

      Figure 13-22 OMD running window

      NOTE:

      To exit the OMD, click the icon in the OMD running window.

  • Starting the OMD in UNIX/Linux

    To start the OMD, do as follows:

    1. Log in to the computer where the OMD is installed as the CTI platform user icd.
    2. Run the mdscmd command.

      The system displays the following information:

      0). Get Process State From MDS 
      1). List All Process 
      2). Add  Process 
      3). Modify Process Setting 
      4). Delete Process 
      5). Get Config From CCS 
      6). Start Process 
      7). Stop Process 
      8). Start All Process 
      9). Stop All Process 
      a). Set Alarm Info 
      b). Set reference IP 
      q). Quits 
      Please Select (0~9 or q):     
    3. Type 2 to add the OMD program.

      Make sure that the OMD is monitored and started by the MDS.

      When adding the OMD program, retain the default settings.

    4. After the OMD is started, run the p command to check whether the OMD process exists.

      If the system displays the information shown in Figure 13-23, it indicates that the OMD process exists.

      Figure 13-23 Starting the OMD

Follow-up Procedure

To stop the OMD under the UNIX prompt, you can use MDS or run the kill command.

  • Use MDS to stop the OMD
    1. Enter the mdscmd command under the UNIX prompt.
    2. Enter 7 after the MDS prompt menu appears. Select Stop Process.
    3. Enter omd according to the prompt.
  • Run the kill command to stop the process
    1. Enter the process querying command p under the UNIX prompt to view the process number of the OMD.
    2. Run the command kill process number of the OMD.

Setting Protocol Parameters for CTI (R6)

Set protocol parameters on CTIs (R6) so that the CTIs (R6) can properly connect to the eSight.

Prerequisites (R6)

The prerequisites for CTI platform components to connect to the eSight, connection process, and points for attention.

CTI platform

  • The components of the CTI platform have been installed and are running properly.
  • The oas_access_platform_db.sql (for the Oracle database) or oas_access_platform_db.sql (for the DB2 database) script that is provided in the OAS&OMD has been loaded to the UIDB of the CTI platform.

UOA

The UOA is installed and runs properly.

Obtaining OAS and OMD Software Packages

  1. Visit http://support.huawei.com/enterprise.
  2. Click Log In. In the page that is displayed, enter the account name and password, and click Log In.
  3. After login, enter eSpace CC in the search box.
  4. Click the path to enter the product documentation page.
  5. Click the Software tab page to download your desired software.

Obtain the OAS and OMD software packages, and obtain CTI platform product information that must be configured on the UOA side from the software packages, as shown in Table 13-24.

NOTE:
  • The OAS and OMD software packages vary according to the Windows, AIX, and SUSE Linux operating systems.
  • UOA configuration information varies according to CTI platform versions. You must obtain the UOA configuration file based on the version of the CTI platform. The configuration file in the ICDV300R004 directory is applicable to CTI platforms V300R004 and V300R005.
Table 13-24 Description of OAS and OMD installation packages

Directory

Installation Package

Description

OAS and OMD installation packages

OAS&OMD

win32 install

ICDV300R006C*_WIN_ICD.zip

The OAS and OMD installation packages for Windows are integrated in the installation package of the CTI platform.

suse linux install

ICDV300R006C*_LINUX_ICD.zip

The OAS and OMD installation packages for SUSE Linux 10 and SUSE Linux 11 are integrated in the installation package of the CTI platform.

Obtaining the DB_SCRIPT Software Package, UOA Configuration File, and Service Monitoring Package of the CTI Platform

  1. Visit http://support.huawei.com/enterprise.
  2. Click Log In. In the page that is displayed, enter the account name and password, and click Log In.
  3. After login, enter eSpace CC in the search box of the Product Support tab page. A path is displayed under the search box.
  4. Click the path to enter the product documentation page.
  5. Click the Software tab page to download your desired software.

Obtain the ICDV300R006C*_PUBLIC_ICD.zip package. After the software package is decompressed, the OAS directory contains the DB_SCRIPT software package, UOA configuration file, and the service monitoring package of the CTI platform, as shown in Table 13-25.

Table 13-25 Description of the DB_SCRIPT software package, UOA configuration file, and service monitoring package of the CTI platform

Directory

Installation Package

Description

DB_SCRIPT software package

DB_SCRIPT

OAS Access CTI Platform DB Script\DB2

oas_access_platform_db.sql

Script loaded to the DB2 database of the CTI platform when the OAS monitors the CTI platform that is loaded with the customer service

oas_access_service_db.sql

Script loaded to the DB2 database of the customer service when the OAS monitors the CTI platform that is loaded with the customer service

OAS Access CTI Platform DB Script\ORACLE

oas_access_platform_db.sql

Script loaded to the Oracle database of the CTI platform when the OAS monitors the CTI platform that is loaded with the customer service

oas_access_service_db.sql

Script loaded to the Oracle database of the customer service when the OAS monitors the CTI platform that is loaded with the customer service

NOTE:

When the OAS monitors the CTI platform that is loaded with the customer service, you need to import the corresponding scripts to the user information database (UIDB) of the CTI platform and the ICDMAIN database of the customer service.

When the OAS monitors the CTI platform that is loaded with the RBT service, no script needs to be imported.

UOA configuration file

UOA Config

ICDV300R006

alarm

It contains the alarm resource files of CTI platform components. According to the reported alarm ID, the UOA queries the relevant static information, fills the information in an alarm, and reports the alarm to the eSight.

log

It contains the log resource files of CTI platform components. According to the reported log ID, the UOA queries the relevant static information, fills the information in an alarm, and reports the alarm to the eSight.

mib

It contains the configuration files of the Mib interfaces of the CTI platform. These files provide detailed description of the network management interfaces of the CTI platform for the UOA.

perftaskfiles

It contains the configuration files of the performance statistics tasks of the CTI platform. The configuration items include the measurement units supported by NEs, measurement objects, measurement indexes, measurement granularity periods, and measurement task plans.

templates

It contains the configuration file of the CTI platform. The file provides the configuration information about all the components to be managed by the UOA.

trace

When the iTrace is used to trace messages of the CTI platform, use the following directories to replace the corresponding directories in the iTrace client:

  • config: stores tracing files.
  • neapi: stores tracing plug-ins.
NOTE:

Before you use the iTrace to trace the messages of the CTI platform, make sure that the iTrace is installed. For the method of installing the iTrace, see the installation guide of the iTrace.

Currently, messages of the CTI platform are traced by the ICDDebug. Do not use the iTrace.

Required Resources

Before configuring the components described in Table 13-26, you need to collect parameter values according to the actual situation. When configuring the components, use the collected parameter values.

Table 13-26 Parameters for connecting the CTI platform to the eSight

Component

Parameter

Example

UOA

-

-

OAS

IP addresses of the active NIS and standby NIS.

IP address of the active NIS: 10.70.104.203

IP address of the standby NIS: 10.70.104.118

Service data source name configured on the Web configuration console, pointing to the ICDMAIN database of customer services.

icdmain

IP address for the UOA to provide services for the application access point (AAP).

10.70.104.172

Listen port for the UOA to provide services for the AAP.

6700

OMD on a CTI platform host

IP address bound with the ICDComm on the host where the OAS is located.

10.70.101.140

eSight

IP address of the host where the UOA that registers on the CTI platform is located.

10.70.101.190

Port number that the UOA uses to connect to the eSight.

6600

Configuring Information in the UOA (R6)

How to configure information in the UOA when CTI platform components connect to the eSight.

Context

After configuring the information about the CTI platform in the UOA, you must restart the UOA for the configurations to take effect.

Procedure

  1. Log in to the computer where the UOA is located.

    If the UOA is installed in the computer that runs UNIX or SUSE Linux, log in to the computer as the user who installs the UOA.

  2. Obtain the UOA installation packages described in Table 13-24, and then copy the configuration file that matches the CTI platform version from the UOA Config directory to the corresponding directory in $UOA_RUN_ROOT\UOA\data.

    Assume that the version of the monitored CTI platform is of V300R004 series. Copy all the files in alarm in the UOA Config\ICDV300R004 directory to $UOA_RUN_ROOT\UOA\data\alarm.

    NOTE:

    $UOA_RUN_ROOT is the installation directory of the UOA.

    If the system displays a message asking whether to replace existing files when you copy files, pay attention to the following:

    • If the version of the UOA is of UOAV100R001C01 series and you copy the files in templates, click No. That is, do not replace the productsconfig.xml file.
    • In other cases, click Yes.

  3. Modify the productsconfig.xml file in $UOA_RUN_ROOT\UOA\data\templates.

    NOTE:

    The productsconfig.xml file needs to be modified only when the version of the UOA is of UOAV100R001C01 series.

    Add the following characters in bold to the <products> section in the productsconfig.xml file:

    <products> 
    <!--Product: example--> 
    <product productname="uoa" productConfigFileName="uoa_productconfig.xml"/><product productname="cti" productConfigFileName="cti_productconfig.xml"/> 
    </products>     

  4. Restart the UOA for the configurations to take effect.

    • Restarting the UOA in Windows

      To restart the UOA in Windows, double-click the shortcut icon of the UOA on the desktop, or choose Start > Programs > huawei, and then select UOA.

    • Restarting the UOA in UNIX or SUSE Linux

      To restart the UOA in UNIX or SUSE Linux, log in to the computer that runs UNIX or SUSE Linux as the user who installs the UOA, and then run the following command:

      uoa_start.sh

Installing and Configuring the OAS (R6)

The following sections describe the procedures for installing the OAS in Windows and UNIX or Linux.

Context

The OAS must be installed on the CTI Server as planned and uses the ICDComm configured for the CTI Server. Therefore, you do not need to install the ICDComm for the OAS.

Procedure

  • Installing the OAS in Windows
    NOTE:

    In ICD V300R006C10 and later version, the OAS installation program is integrated in the platform installation package, and the OAS needs to be installed as a platform component according to the site requirements.

    1. Obtain the OAS installation package described in Table 13-24, decompress it to a local directory, and double-click Setup.exe to run the installation program.
    2. In the window shown in Figure 13-24, select OAM agent server in Select Components.
      Figure 13-24 Select Components

    3. Click Next.

      Install the OAS by referring to "Installing Call Center Platform CTI Platform Components in Windows" in the ICD Product Documentation.

    4. After the installation, Choose Start > Programs > HUAWEI Intelligent Call Center > OAM agent server on the desktop to access the OAS main window, and configure the basic information about the OAS.

      Before configuring the OAS, you must stop it first.

      1. In the running window of the OAS, choose System > Stop or double-click the icon on the tool bar or select the OAS service in the MDS to stop the OAS service.
      2. Select Config in the running window of the OAS. The Base Config window appears, as shown in Figure 13-25.
        Figure 13-25 Configuring basic OAS information

      3. In the Base Config window, set the information about the connection between the OAS and the CCS on the monitored CTI platform and the connection between the OAS and the UOA. See Table 13-27.
        Table 13-27 Basic configuration information

        Configuration Item

        Description

        Setting

        NIS Config

        Master IP

        IP address of the active NIS.

        Set the parameter to the IP address of the active NIS on the CTI platform.

        Standby IP

        IP address of the standby NIS.

        Set the parameter to the IP address of the standby NIS on the CTI platform.

        ServiceDB name

        Name of the data source that accesses the service database.

        The value of ServiceDB name must be the name of the third-party data source that is configured on the web configuration console.

        NOTE:

        The script oas_access_service_db.sql (for the Oracle database) or oas_access_service_db.sql (for the DB2 database) must be loaded to the data source specified by this parameter.

        UOA Config

        Connect to UOA

        If you select this item, the OAS needs to connect to the UOA. If you do not select this item, the OAS does not need to connect to the UOA.

        The OAS needs to connect to the UOA only when the OAS connects to the eSight by using the UOA.

        UOA IP

        IP address of the host where the UOA is located.

        The value of UOA IP must be the same as the IP address that is configured to provide services for the AAP when the UOA is installed.

        UOA port

        Port number for the UOA to monitor the OAS.

        The default value is 6700.

        The value of UOA port must be the same as the port number that is configured to provide services for the AAP when the UOA is installed.

        NOTE:

        If the version of the UOA interconnected with the OAS is later than V100R001C02B132, the port number on the OAS side is the port number on the UOA side plus 6.

      4. Click OK.
  • Installing and configuring the OAS in UNIX/Linux

    To install and configure the OAS, perform the following steps:

    1. Obtain the OAS installation package shown in Table 13-24.
    2. In the MainAst window, click the Device Manager tab to select the CTI device to be installed.
    3. Click the Toolkit tab, and double-click CTI Install/Upgrade/Uninstall.

      The Installation Panel window appears.

    4. Select the version of the CTI platform installation package and the computer where the device is to be installed, and click Next. See Figure 13-26.
      Figure 13-26 Installation panel

    5. Set the installation type to Add/Delete Component and click Next.
    6. In Installation Planning, select oas in Other Component, and click Next. See Figure 13-27.
      Figure 13-27 Installation planning

    7. Verify Figure 13-27 and click Next. The OAS installation starts. When Installation Progress is 100%, click Next until the Finish dialog box appears. Click Finish.
    8. Click the Toolkit tab and double-click Maintain Terminal.
    9. Expand the navigation tree shown in Figure 13-28. Double-click Configure OAS.
      Figure 13-28 Navigation tree

    10. In the Config OAS window, configure information about the connection between the OAS and the NIS on the monitored CTI platform and the connection between the OAS and the UOA. See Figure 13-29.
      Figure 13-29 Configuring the OAS

      Click Renew and click Exit.

Starting the OAS (R6)

The following sections describe the procedures for installing the OAS in Windows and UNIX or Linux.

Procedure

  • Starting the OAS in Windows

    Choose Start > Programs > HUAWEI Intelligent Call Center > OAM agent server on the desktop to start the OAS.

    After the OAS is started, the system displays the window shown in Figure 13-30 if the following conditions are met:

    • The OAS is correctly installed and configured.
    • The UOA runs properly.
    • The CTI platform runs properly.
    Figure 13-30 OAS running window

  • Starting the OAS in UNIX or Linux

    To start the OAS in UNIX or Linux, do as follows:

    1. Log in to the OAS host as the installation user of the OAS.
    2. Run the oas& command to start the OAS.
    3. After the OAS is started, run the p command to check whether the OAS process exists. If the system displays the information shown in Figure 13-31, the OAS process exists.
      Figure 13-31 Starting the OAS

      NOTE:

      To stop the OAS under the UNIX prompt, you can use run the kill command.

      Enter the process querying command p under the UNIX prompt to view the process number of the OAS. Then run the command kill process number of the OAS.

Configuring ICDComms (R6)

This topic describes how to configure NAT conversion information for ICDComms in Windows and UNIX or Linux.

Background Information

The version of the ICDComm on the OMD must be the same as the versions of the ICDComms on the OAS and the devices managed by the OAS.

ICDComms are installed during CTI platform component installation. You do not need to install ICDComms separately.

The OAS is installed on the intranet of the monitored CTI platform. If some monitored components are isolated from the intranet by using firewalls, you must configure NAT conversion information in the ICDComms on the computers where the components are located. The OMD can communicate with the OAS only after NAT conversion information is configured.

The following is an example of NAT conversion information.

Figure 13-32 IP address mapping

As shown in Figure 13-32:

  • The IP address of the ICDComm on the OAS is 10.10.10.1.
  • The IP address of the ICDComm Portal on the OMD is 192.168.1.2.
  • The OAS IP address is mapped to 192.168.1.1 on a firewall.
  • The OAS IP address configured in the OMD is 10.10.10.1.

Procedure

  • Configuring NAT conversion information in Windows
    1. On the computer where a component is located, open the ICDComm configuration page.

      Choose Start > Programs > HUAWEI Intelligent Call Center > HUAWEI Voice-added Service Platform > ICD communication program group > ICD configuration program to open the ICDComm configuration page. See Figure 13-33.

      Figure 13-33 ICDComm configuration

    2. Click Advanced. The NAT table configuration window appears.

      The window that appears may vary according to the version. You need to focus on the NAT table configuration window only.

    3. Right-click on the blank area in the NAT table configuration window and choose Append from the shortcut menu.
    4. In the dialog box that appears, set the destination IP address to the OAS IP address 10.10.10.1, and set the replacement IP address to the OAS IP address 192.168.1.1 mapped on the firewall. See Figure 13-34. Click OK to save the configuration.
      Figure 13-34 NAT conversion information

    5. Restart the ICDComm service for the configuration to take effect.
  • Configuring NAT conversion information in UNIX or Linux
    1. Access the directory for storing the icdcomm.cfg file.
    2. Run the vi icdcomm.cfg command.
    3. Add NAT Table = (IPb,NATIPb), for example, NAT Table = (10.71.111.44,10.9.21.8).
    4. Run the :wq command to save the configuration and exit.
    5. Restart the ICDComm service for the configuration to take effect.

Configuring NEs to Be Monitored by the OMD (R6)

The following sections describe the procedures for configuring NEs to be monitored by the OMD in Windows and UNIX or Linux.

Context

The OMD can monitor NEs only after those NEs are configured.

NOTE:

The type of the devices that the OMD can monitor depends on the platform device type that is selected when the OMD is installed.

After configuring the NEs to be monitored by the OMD, restart the OMD for the configuration to take effect. For details, see Starting the OMD (R6).

Procedure

  • Configuring the OMD in Windows

    To configure an NE, do as follows:

    1. Double-click the icon or choose Start > Program > OMD > OMD Config on the desktop to start the OMD configuration tool.

      The OMD Config - ICD window is displayed, as shown in Figure 13-35.

      Figure 13-35 Configuring an NE to be monitored by the OMD

    2. Set the IP address of the OAS.

      The OAS IP parameter indicates the IP address bound with the ICDComm on the OAS host that is connected to the OMD. After the OMD is started, the OMD communicates with only the OAS whose IP address is specified by the OAS IP parameter.

    3. Select an NE to be monitored by the OMD from the NE Type list box.

      The selected NEs must be the CTI platform components that are installed on the OMD host.

    4. Click Add.

      The NE Config - XXX window is displayed, as shown in Figure 13-36.

      Figure 13-36 Adding a single-instance NE

    5. Set the parameters for the NE according to the description provided in Table 13-28.
      Table 13-28 Setting parameters for NEs

      Parameter

      Description

      Setting

      Common configuration items

      ProgID

      Process ID of a program.

      • The values of ProgID set for the ApLogic and DtProxy can be 12 or range from 201 to 299.
      • The values of ProgID set for the system range from 301 to 399.
      • For a single-instance NE, the default value of ProgID must be retained.
      • For a multi-instance NE, the value of ProgID must be the process ID that is used when the NE runs.

        The ApLogic, DtProxy, IVRUI system are multi-instance NEs. Except these NEs, the NEs in the list are single-instance NEs.

      Name

      Name of an NE.

      Enter the name of an NE.

      Run Mode

      Mode in which an NE runs. The options are Exe, Service, and Other.

      • Exe: Indicates that an NE runs in program interface mode.
      • Service: Indicates that an NE runs in background service mode.

      For the CCS, CTI Server, MailM, WebM, and WAS, the Run Mode parameter can be set to Exe or Service.

      For other NEs, the Run Mode parameter can be only set to Exe.

      Need OMD Start

      Flag indicating whether the OMD automatically restarts an NE. That is, whether the OMD automatically restarts a device when the OMD detects that an exception occurs in the device or that the device does not run.

      If the OMD automatically restarts the NE, select Yes; otherwise, select No.

      Select Yes or No according to the actual situation.

      NOTE:

      When an NE is monitored by the OMD and MDS or another monitoring program simultaneously, the value of the configuration item Need OMD Start set for the NE must be No in the OMD window.

      Application File

      Running file of an NE program.

      • For a program that runs in exe mode, set the parameter to the full path of an executable running file.
      • For a program runs in service mode, set the parameter to a service name.

      Special configuration items for the DtProxy

      Max Command Num

      Maximum number of command words of the DtProxy supported by the OMD.

      The default value 500 is recommended.

      The default value can be changed according to the number of command words that is set in the Dtproxy.ini file. The value must be greater than the actual number of command words.

      Config File

      Full path of the configuration file of the DtProxy.

      Click the button, and then select the dtproxy.ini file from the displayed file browsing box.

      Special configuration items of the WAS

      IP

      IP address of the computer where the WAS is installed.

      Enter an IP address.

      Port

      Port number of the computer where the WAS is installed.

      The default value 8080 is used.

      If the port number of the WAS is changed in the WAS server, the value of Port must be changed.

      User/PWD

      User name and password for logging in to the WAS.

      Enter a user name and a password according to the actual situation.

      Service name(s) Started By OMD

      Full path of the WAS.

      Click Add, and then select the startup.bat file. The startup.bat file is the running file of the WAS.

      HTTP Page(s) For To Get State

      Website address for determining whether the computer where the WAS is installed runs properly.

      Click Add, and then enter a website address.

    6. Click OK.

      The added NE is displayed in the NE group box.

  • Configuring the OMD in UNIX/Linux

    To configure the OMD, do as follows:

    1. Log in to the server where the OMD is installed as the CTI platform user icd, and then access the icddir directory of the CTI platform.
    2. Run the omdconfig command to start the OMD configuration program.

      The system displays the following information:

      % icd/bin> omdconfig 
      OAMV2.0D313 
       
      0) Quick-config 
      1) List Base Config 
      2) List Device Config 
      3) Modify Base Config 
      4) Add Device 
      5) Modify Device 
      6) Delete Device 
      7) Clear Device Config 
      q) Quits 
      Please Select (0~7 or q):     
    3. Type the serial number (SN) or letter before a configuration item to perform the corresponding operation.

      Table 13-29 describes the operations corresponding to the serial numbers.

      Table 13-29 Operations related to the configuration

      SN

      Operation

      0

      The SN corresponds to the operation of configuring NE information quickly. After typing 0, you can quickly add NEs according to the default configurations. The NEs that can be added vary with the platform types. The differences are as follows:

      • If the CTI platform is loaded with the customer service, the following NEs are added by default: CCS, CTI Server, MailM, WebM, MDS, CTI-Link, and MCP.
      • If the CTI platform is loaded with the RBT service, the following NEs are added by default: CCS, CTI Server, MDS, FEP, and MCP.

      1

      After you type 1, the system displays the configured basic information.

      2

      After you type 2, the system displays the detailed configuration information of the device.

      3

      After typing 3, you can configure the basic information according to the description provided in Table 13-30.

      4

      After typing 4, you can add NEs.

      Table 13-31 describes the information about the NEs that needs to be configured.

      NOTE:

      The NEs must be the components of the CTI platform that are installed in the computer where the OMD is located, such as the CCS, CTI Server, MailM, WebM, MDS, CTI-LinkFEP, MCP, IVRUI system, and ApLogic.

      5

      After typing 5, you can change the monitored NEs.

      6

      After typing 6, you can delete the monitored NEs.

      7

      After you type 7, the system automatically deletes all NEs.

      q

      After typing q, the configurations are saved and you exit the OMD.

      NOTE:

      When exiting the OMD, you cannot press any key until the system prompts that saving the configurations is successful.

      Table 13-30 Basic configuration information

      Parameter

      Description

      Setting

      OAS IP Address

      IP address bound with the ICDComm on the OAS host.

      -

      ICD Run Mode

      If running in ICD mode, the OMD can only start the MDS. Other programs are started by the MDS. If not running in ICD mode, the OMD can start any program that is configured to be started by the OMD.

      If the CTI platform carries customer services, click YES; otherwise, click NO.

      Max Log File Size

      Maximum size of the log file.

      The value can be 1, 2, 5, 10, or 12.

      The unit is MB.

      Log Level

      Log level.

      Log levels can be ranked from high to low as follows:

      • 0: EMERGENCY
      • 1: ALERT
      • 2: CRITICAL
      • 3: ERROR
      • 4: WARN
      • 5: NOTICE
      • 6: INFO
      • 7: DEBUG

      The OMD records the logs of the levels higher than the level specified by the Log Level parameter.

      The INFO level is recommended.

      Table 13-31 NE information

      Configuration Item

      Description

      Setting

      Common configuration items

      Please select a device type

      Name of an NE to be added.

      NE names are case sensitive. The entered NE name must be the same as the NE name that the system allows to add.

      Please input the device ProgID

      Process ID of a program.

      • The values of ProgID set for the ApLogic and DtProxy can be 12 or range from 201 to 299.
      • The values of ProgID set for the IVRUI system 4 or range from 301 to 399.
      • For a single-instance NE, the default value of ProgID must be retained.
      • For a multi-instance NE, the value of ProgID must be the process ID that is used when the NE runs.

        The ApLogic, DtProxy, IVRUI system are multi-instance NEs. Except these NEs, the NEs in the list are single-instance NEs.

      Need Start

      Flag indicating whether the OMD automatically restarts an NE. That is, whether the OMD automatically restarts a device when the OMD detects that an exception occurs in the device or that the device does not run.

      If the OMD automatically restarts the NE, set Yes; otherwise, set No.

      Select Yes or No according to the actual situation.

      NOTE:

      When an NE is monitored by the OMD and MDS or another monitoring program simultaneously, the value of the configuration item Need Start set for the NE must be No in the OMD window.

      App Full Path

      Full path of the executable file of a monitored program.

      -

      Special configuration items for the DtProxy

      Max Command Num

      Maximum number of command words of the DtProxy supported by the OMD.

      The default value 500 is recommended.

      The default value can be changed according to the number of command words that is set in the Dtproxy.ini file. The value must be greater than the actual number of command words.

      Config File

      Full path of the configuration file of the DtProxy.

      Set the full path of the dtproxy.ini file.

Starting the OMD (R6)

Procedure

  • Starting the OMD in Windows

    To start the OMD, do as follows:

    1. Double-click the shortcut icon or choose Start > Program > OMD > OMDon the desktop to start the OMD.

      If the icon is displayed on the task bar, it indicates that the OMD is started.

    2. Double-click the icon on the task bar.

      The window, as shown in Figure 13-37, is displayed.

      Figure 13-37 OMD running window

      NOTE:

      To exit the OMD, click the icon in the OMD running window.

  • Starting the OMD in UNIX/Linux

    To start the OMD, do as follows:

    1. Log in to the computer where the OMD is installed as the CTI platform user icd.
    2. Run the mdscmd command.

      The system displays the following information:

      0). Get Process State From MDS 
      1). List All Process 
      2). Add  Process 
      3). Modify Process Setting 
      4). Delete Process 
      5). Get Config From CCS 
      6). Start Process 
      7). Stop Process 
      8). Start All Process 
      9). Stop All Process 
      a). Set Alarm Info 
      b). Set reference IP 
      q). Quits 
      Please Select (0~9 or q):     
    3. Type 2 to add the OMD program.

      Make sure that the OMD is monitored and started by the MDS.

      When adding the OMD program, retain the default settings.

    4. After the OMD is started, run the p command to check whether the OMD process exists.

      If the system displays the information shown in Figure 13-38, it indicates that the OMD process exists.

      Figure 13-38 Starting the OMD

      NOTE:

      To stop the OMD under the UNIX prompt, you can use MDS or run the kill command.

      • Use MDS to stop the OMD

        Enter the mdscmd command under the UNIX prompt. Enter 7 after the MDS prompt menu appears.

        Select Stop Process.

        Enter omd according to the prompt.

      • Run the kill command to stop the process

        Enter the process querying command p under the UNIX prompt to view the process number of the OMD. Then run the command kill process number of the OMD.

Setting Protocol Parameters for U2900s

If an non-admin user is used, you must register a new user on U2900 and assign NE and operation rights to the user.

Adding an LMT User

  1. Log in to the LMT client as the administrator user (default password: Change_Me).
  2. Add a user.

    1. Click System > Security.
    2. In the window that is displayed, right-click User and choose New.
    3. In the dialog box that is displayed, enter the user name and password of the new user, and choose Account valid forever and Password valid forever.
    4. Click Apply.

    For details about the procedure, see Figure 13-39.

    Figure 13-39 Adding a user on the LMT client

    The user is added. The admin1 user is displayed in the window on the right.

  3. Assign the NE right to the user.

    1. Right-click the new user admin1 and choose Authorized ME.
    2. In the dialog box that is displayed, click Add.
    3. In the dialog box that is displayed, choose UAP and click OK.

    For details about the procedure, see Figure 13-40.

    Figure 13-40 Assigning the NE right to the user

  4. Assign the operation right to the user.

    1. Right-click the new user admin1 and choose Authorized Operation.
    2. In the dialog box that is displayed, click Add.
    3. In the drop-down list box, set ME ID, Command Group Name and Managed Object Group to ALL.
    4. Click OK.

    For details about the procedure, see Figure 13-41.

    Figure 13-41 Assigning the operation right to the user

Setting Protocol Parameters for UMSs

Set protocol parameters on UMSs so that the UMSs can properly connect to the eSight.

Procedure

  • For Movius UMSs, perform the following operations:
  1. Log in to the UMS server as the root user.
  2. Configure SNMP user information if the SNMPv3 protocol is used.

    1. Stop the SNMP service.

      stop snmp

    2. Create an SNMPv3 user.

      net-snmp-create-v3-user -a password username

      In the command, username is the SNMP user to be created, and password is the MD5 authentication protocol password for the user.

      Be cautious to use HMAC_MD5 because it may bring information security risks.

      Assume that the user name and authentication password are movius and M0vius@123 respectively.

       
      adding the following line to /var/net-snmp/snmpd.conf: 
       createUser SNMP MD5 "M0vius@123" AES 
      adding the following line to /usr/local/share/snmp/snmpd.conf: 
       rwuser movius
    3. Start the SNMP service.

      start snmp

  3. Configure UMS alarm reporting information.

    1. Switch to the directory where the movius-onms.properties file is stored.

      cd /opt/opennms/etc

      vi movius-onms.properties

       
      trap_ip=10.137.96.93      <-----------eSight server IP address 
      trap_port=162      <-----------Port number 
      version=3      <-----------SNMP protocol version 
      security-name=movius      <-----------Security name 
      auth-passphrase=M0vius@123      <-----------Authentication key 
      auth-protocol=MD5      <-----------Authenticatioin protocol 
      privacy-passphrase=M0vius@123      <-----------Private key 
      privacy-protocol=AES      <-----------Private protocol 
      #NOAUTH_NOPRIV = 1;AUTH_NOPRIV = 2;AUTH_PRIV = 3; 
      security-level=1

      Be cautious to use HMAC_MD5 because it may bring information security risks.

    2. Restart the OpenNMS.

      stop opennms

      start opennms

  • For eSpace UMSs, perform the following operations:
  1. Log in to the UMS system through the browser as the user admin.
  2. In the navigation tree, choose System > Nms manage > Nms server config.

  3. Click Add, and set related parameters in the displayed Add group dialog box to create a SNMPV3 user.

    NOTE:

    You are recommended to set the Auth type to SHA, and the Privacy type to AES.

  4. Click Save, and click ok in the displayed dialog box.
  5. In the navigation tree, choose System > Nms manage > Nms server config.

  6. Set related parameters, and click Save, and click ok in the displayed dialog box.

    NOTE:
    • If the eSight is two-node cluster system, you need to set Prepare eSight address.
    • Set Group name list to the SNMPV3 user whitch created in 3.

  7. Click load config, and click ok in the displayed dialog box.

Setting Protocol Parameters for VCLOG

Set protocol parameters on VCLOGs so that the VCLOGs can properly connect to the eSight.

Procedure

  1. Log in to the HWLog server as the Administrator user.
  2. Start SNMP Service.

    1. Choose Start > Run and enter services.msc. The Service window is displayed.
    2. Right-click the SNMP Service service, and choose Start.

  3. Click the Trap tab and add the public community in the SNMP Service Properties (SIPSERVER0) dialog box.
  4. Click Security tab and grant the Read only permission to the public community.
  5. Choose Start > Huawei Recording > HWLogDiagnostics > Alarm Server.
  6. Add email addresses in the HWLog Diagnostic-Server Side dialog box, as shown in Figure 13-42.

    Figure 13-42 Configuring email addresses

  7. Click Level.
  8. Click Snmp in the Alarm Level dialog box.
  9. Set parameters in Set Parameter. Table 13-32 describes the parameters.

    Table 13-32 SNMP parameters

    Parameter

    Description

    IP Address

    IP address of the eSight server.

    Community

    Community name. Set this parameter based on the site requirements.

    Send Port

    SNMP port for sending mails. Set this parameter based on the site requirements.

    Receive Port

    SNMP port for receiving mails. Set this parameter based on the site requirements.

Setting Protocol Parameters for SBCs (SX Series)

Set protocol parameters on SX1000s so that the SX1000s can properly connect to the eSight.

Background

  • By default, the eSight domain name ucems.huawei.com is configured on SX1000s.
  • If a DNS server exists on the network, configure the mapping between the eSight domain name and the IP address on the DNS server, without performing steps in Procedure.
  • If no DNS exists on the network, configure the server URL by referring Procedure.

Procedure

  1. Log in to the web page of the SBC (SX Series).

    1. Type the SBC (SX Series) IP address in the address box, and press Enter.
    2. Log in to the SBC (SX Series).

  2. Configure the server URL.

    1. Choose Advance in the main menu.
    2. In Server, enter the IP address corresponding to the TR-069 service on the eSight.
      • You are suggested to use HTTPS protocol for higher security requirements. Enter https://IP address of the eSight server:32237/tr069SBC/services/acs.
      • In the case of lower security requirements, enter http://IP address of the eSight server:32236/tr069SBC/services/acs.

        Exercise caution when using HTTP because it may bring information security risks.

Follow-up Procedure

To use the HTTP protocol, you must manually modify the related files in the eSight installation directory.

HTTP has security risks. Exercise caution when you use it.

  • Modify the supportSBCHttp=false item in the config.properties file in the AppBase\etc\uc\ directory under the eSight installation directory to supportSBCHttp=true.
  • In the webserver.roa.inst.xml file in the /opt/eSight/AppBase/etc/iemp.framework/ directory, add the eSight IP address and port number.

    In <webserver name="tr069SBC"></webserver>, add the following content:

    <connector name="Tr069HttpPort" type="http"> 
    <property name="ip" value="@{ENT_HOSTIP}" /> //Replace @{ENT_HOSTIP} with the eSight IP address, such as 10.10.134.120. 
    <property name="port" value="32236" /> 
    </connector>

Restart eSight after the modification.

Setting Device Protocol Parameters for the EC3.0 ECS

Set protocol parameters on devices involved in the EC3.0 ECS so that you can use the eSight to manage EC3.0 ECS devices.

Prerequisites

The EC3.0 ECS devices are running properly.

Configuring the Whitelist

  1. Log in to the UOA server as the uoa user.
  2. Edit the UOA configuration file.

    su - uoa

    cd $UOA_RUN_ROOT/cfg/system

    vi adapter.acl

    Add the eSight IP address to the end of the adapter.acl file.

  3. Restart the UOA server.

Setting Protocol Parameters for the CGP Server

To ensure that eSight can normally manage the CGP server, you need to set protocol parameters on the CGP server.

Prerequisites

The CGP server runs normally.

Procedure

  1. Log in to HUAWEI Operation & Maintenance System as the admin user.
  2. Run the ADD SNMPUSER command to create a user, for which Authentication protocol and Private protocol are not NULL and the protocol version is V3.
Translation
Download
Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 312762

Downloads: 635

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next