Configure CEM Controller on CentOS 6.9

Size: px

Start display at page:

Download "Configure CEM Controller on CentOS 6.9"

Doreen Cole
6 years ago
Views:

1 Configure CEM Controller on CentOS 6.9 Contents Introduction Background Prerequisites Requirements Components Used Installing Oracle Java SE Runtime Environment 8 Downloading and Installing the CEM Controller Steps for CEM Server Cloud. Steps for CEM Server On Premise. Installing the certificate cem_keypair.key Starting the Controller Service Optional step. Opening firewall port Troubleshoot Introduction This document describes how to install and configure Energywise on CentOS 6.9 Contributed by Israel Moreno, Cisco TAC Engineer. Background Cisco Energywise Management (CEM) controllers are responsible for direct device communication within the network, device and asset import, power measurement and policy control. Each management deployment requires a minimum of one Controller connected to the CEM Server. Larger deployments typically have multiple Controllers deployed across different sites or locations, or even multiple controllers in the same location for large networks. Controllers can be installed on both Windows and Linux boxes. Prerequisites Requirements Root access or user with administrator rights on CentOS 6.9 box. CEM Server installed. Credentials and key pair file created during its installation will be needed. Wget and netcat utility packages installed on the CentOS system. You can install them using the following command: yum install wget nc Oracle Java SE Runtime Environment 8. The RPM can be found here. Components Used

2 CEM Server installed on a Windows Server 2008 R2 Virtual Machine. CentOS 6.9 minimal installation Virtual Machine. Installing Oracle Java SE Runtime Environment 8 Copy the JRE RPM to the CentOS VM; skip this step if the RPM was downloaded directly on it. Install JRE with the following command: yum install /<path> jre-8u<x>-linux-x<64/86>.rpm The RPM can also be installed using: rpm ivh /<path> jre-8u<x>-linux-x<64/86>.rpm Downloading and Installing the CEM Controller Download Cisco Energy Management Controller for CentOS 6 from CEM Download page There are 32-bit and 64-bit versions available: Log in to the CentOS system. Navigate to the folder that contains the downloaded file. For example, if the controller installation file is in your Downloads folder and the folder structure is /home/admin/downloads, enter the following command: cd /home/admin/downloads Enter one of the following commands to install the controller: yum install EnergyWise-Controller-<version>.rpm rpm ivh EnergyWise-Controller-<version>.rpm The controller package is extracted and installed in the /var/lib/ewcontroller folder. This folder contains two different templates, one for CEM Server Cloud and one for CEM Server On Premise. The next steps depend on which type of CEM Server is being used. Steps for CEM Server Cloud. Copy the init.sample template entering the following command: cp /var/lib/ewcontroller/ewcontroller.init.sample /var/lib/ewcontroller/ewcontroller.init Using the preferred text editor edit the init file, which contains the following lines:

3 clouddomain="" cloudpassword="" javapath="" An explanation for each line is shown below: ctrllogdir= <Local path of the log directory> This line can be left empty, in which case, the default path /var/log/ewcontroller will be applied. clouddomain=" " This line holds the authentication domain associated to the CEM Server Cloud account. Cannot be empty. cloudpassword=" " This line holds the corresponding password for the domain used on the previous configuration line. javapath=" " Local path where Java is installed This is how the ewcontroller.init file looks like for this example: clouddomain="taclab.com" cloudpassword="taclabpassw0rd" javapath="/usr/java/jre1.8.0_131/bin/" Adjust the lines as needed. Steps for CEM Server On Premise. Copy the onpremise.init.sample template entering the following command: cp /var/lib/ewcontroller/ewcontroller.onpremise.init.sample /var/lib/ewcontroller/ewcontroller.init Open your preferred text editor and edit the init file, which contains the following lines: mqip="" mqusername="" mqpassword="" mqport="" javapath="" An explanation for each line is shown below: ctrllogdir="<local path of the log directory>" This line can be left empty, in which case, the default path /var/log/ewcontroller will be applied. mqip="<ip of the Message Queue>" CEM Server IP or FQDN. mqport="<port number of the Message Queue>" CEM Server port. Default port is mqusername="<username of the Message Queue>" Username configured during CEM Server installation. mqpassword="<password of the Message Queue>" Password associated to the username entered on the previous line. Also configured during CEM Server installation. javapath="" Local path where java is installed. This is how the ewcontroller.init file looks like for this example: mqip=" " mqusername="admin" mqpassword="adminpassword" mqport="5672" javapath="/usr/java/jre1.8.0_131/bin/"

4 From here, the steps are the same for both CEM Server Cloud and CEM Server On Premise. Installing the certificate cem_keypair.key The file cem_keypair.key is generated during CEM Server Installation. Also, it should be provided if CEM Server Cloud is being used. The file content looks similar to this: -----BEGIN RSA PRIVATE KEY----- MIIEvgIBADANBgkqhkiG9w0BAQEFAASCBKgwggSkAgEAAoIBAQDqvQg2LXJcJ+uhK3U+jnUJio C+ Sf7FU0qurJ9+FNSWOIsfN6Ebk8IbZsO3ysCPTcnpdXak4HSUAA5CCyQCVslomYka4vYrsw/uGyc S 4ooIaTHBcah7whFTxQSkxCeBbglDhbpwWTGgMcOwwCyEhRHdOyLqP/5aMfBrGblRN2vt+mYM KRMX Mg4fqOGtnhAssTrLWvS9L8Mg+UdeL1KumDbXLUBlpnxLulP4H14K2tQr73oBp7cKI+KHMv27JcJ b gtkj8p3lgzvoyltwmy2k36smz/bmdqdif7v04rhw6ukqw7hzcbs2sxeg/el2sqvu0skybbcw8 1R9 ho5nrjstylcragmbaaecggebaoecpg1yco3fomgsy8dupoirbsl5gotcbrodcygljcaxqvyc MZ/C qk0j27za1wzg9ayg38k6gwwjdchilhlb6ckpeidasgjboalvsiwzfudstrimzgmdhkj896+nc 6Vo ud6mwkntdfvxeblkk4fqgsirgbpdlc4vkrthkrmsw3v4nx8akz68ob99ahnll2jlnljgoqryxa dp xuy+0u6jvt0bdtzqxpbmewjlcbii1cv493xengmihhfb+lv0z9yegxh64x+jktzfmwxz3ccafgbu F1dn3/dUl5zlXzuIpGNTAYgsH6sqZhqaZ82VTHwefjsnKlHCc/htMyl1w6nyUfkCgYEA92qY44m9 n4rsjgznomxjom1fdavh+q5xdwulgtvowhn+10syqijnxpbo1zqyqkafveo7ja2lxyinx+15ex RB FChSeAxw0HOcrHEHKr9i0Wk2gHZtD+tCOCM/VvzrpNbK0X/YMIVQUfDfoLeVZKzEEz6MK0KUk zzn /lfo4h9gsh8cgyea8uhwlrysetoeogd+2rsqlc04tec226grdebvhw34g/ldfydb/01lv+ltnhgb zsmvetgjfpfu7fjfmssepby0kcxeoazy6lvgsrodr1yy3qji/0o7ng9krnls579tezngedbu6dge i72beqzz8oslpsi5nkvrwfjvmnqezjrah/ucgyea5hjsxfoq4c5ild7gfaewzkw5lb8g9+2nelh/ lkrbwr5mcdxrxe7dzvzgzvzpxyx/xdor8fyj+z6lbs9vuifrq3meznt4ljzgxls3whniboc5d CHQ Dr459SsfZ43BcQPkYNfE5PGGvVRIvdopu8EKg5bjy2L9XoAEQkwdwYn+ehMCgYB3ET9t3iB9HW Qo CoSlsuvsuD5hI1iBU0A6QH86Oh8akHUFXYm9HrQP5N8kWbCJLBnbnxnGqbg4JUy6Epz0n94lmF sl 5zBvsF5FQ/hJf6gwfF5MxWeAzRrapa9+7NkLRLSGOmfkbGIOH1jZfwAXl/9pfA2CQMXSznn09ggk EakeAQKBgHUWxiupruFehGnMri+Fv/Dy4CQMU2sPjcnqMamVEpB6fDdIeew7VcgAPSH1CyvspX ib G/oh3wLBfhCu+h2ewbG+o6ZvcgUDg4QUjzCu5o2C1kDcPwyn8rHRjs5MSKj1ZlTphQpPilFGjqpT ugqvtg3dvz33v/2aqxfd8vkbdg4o -----END RSA PRIVATE KEY BEGIN PUBLIC KEY----- MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6r0INi1yXCfroSt1Po51CYqAvkn+xVN K rqyffhtuljilhzehg5pcg2bdt8raj03j6xv2pob0laaoqgskalbjajmjgul2k7mp7hsneukkcgkx wxgoe8iru8uepmqngw4jq4w6cfkxodhdsmashiur3tsi6j/+wjhwaxm5utdr7fpmdcktfzio H6jh rz4qlle6y1r0vs/diplhxi9srpg21y1azaz8s7pt+b9ectruk+96aae3cipihzl9uyxcw4lso/d9

5 y4gbzmju1pstpn+rjmf2zhagybe79ok4vurikfux83autrf3hv3i9kkl1nepgawwspnufyaoz647 LWCwqwIDAQAB -----END PUBLIC KEY----- There are two valid options for installing the certificate file. The first one is putting the actual cem_keypair.key file to /var/lib/ewcontroller/cem_keypair.key. The command would look similar to this: mv /<path>/<filename> /var/lib/ewcontroller/cem_keypair.key The second one is to use a text editor to create the /var/lib/ewcontroller/cem_keypair.key file, paste the content and save it. Starting the Controller Service To start the controller service run the following command: /etc/init.d/ewcontroller start Note: This ewcontroller script looks for.firstboot file in the directory /var/lib/ewcontroller/. If this file exists, it imports the configuration from ewcontroller.init into the setting.json file. After this process is done, both ewcontroller.init and.firstboot files will be removed. If the wrong SSL certificate or wrong type of controller is configured (i.e. On Premise vs Cloud), then settings.json must be deleted and.firstboot must be created again within the same directory. Once the configuration is corrected, rerun /etc/init.d/ewcontroller start. After the service restarts, the controller registers the service with the central server. If the controller fails to start with an unknown host exception error, edit the host file located in /etc/hosts/ and include the following line: hostname hostname.domain where hostname is the name of the system on which the controller is installed. Optional step. Opening firewall port If the CentOS box is running a local firewall which blocks unauthorized outgoing connections (it is very likely there is not), it is necessary to allow outgoing TCP traffic on port To do so run the following command: iptables A OUTPUT p tcp dport 5672 m comment - comment ALLOWING_CEM-SERVER_CONNECTION j ACCEPT Troubleshoot After following the previous steps, the controller should show itself on CEM Server web interface. If any problem comes out, there are three files to look at. Those files are: /var/lib/ewcontroller/controller.stderr /var/lib/ewcontroller/controller.stdout /var/log/ewcontroller/controller.log

Teradici PCoIP Connection Manager 1.8 and Security Gateway 1.14

Teradici PCoIP Connection Manager 1.8 and Security Gateway 1.14 TER1502010/A-1.8-1.14 Contents Document History 4 Who Should Read This Guide? 5 PCoIP Connection Manager and PCoIP Security Gateway Overview