ECS Agent Relocation on DNCS

February 2008

Revision 1.0


Proprietary Notice

Information in this document is confidential and proprietary to itaas, Inc. Access to and use of this information is limited strictly to licensees of itaas, Inc. and is subject to the terms of a separate and appropriate written license agreement between the Licensee and itaas, Inc. The information in this document may be protected by patent applications owned by itaas, Inc.

In addition, the information in this document is subject to change without notice and does not represent a commitment on the part of itaas, Inc. The software described in this document may be used only in accordance with the terms of the license agreement. It is against the law to copy the software on any medium except as specifically allowed in the license or non-disclosure agreement. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the licensee’s personal use without express written permission of itaas, Inc.

All specifics of the product, its use and implementation contained in this document are provided in good faith. However, all warranties, implied or expressed, including but not limited to implied warranties of merchantability or fitness for a particular purpose are excluded.

This document is intended solely to assist the Licensee in the use of the itaas, Inc. Licensed Software Product and for no other purpose. itaas, Inc. shall not be liable, in any way under any theory of law, for any loss or damage of any kind what so ever, arising from the use of any of the information contained in this manual, or any error or omission in the information, or any incorrect use of the Software Product.

Copyright © 2007 itaas, Inc. All rights reserved.

itaas is a registered trademark of itaas, Inc.

Revision History

Revision Number / Date / Description
1.0 / 2/2008 / Initial version.


Table of Contents

1 Introduction 4

1.1 System Architecture 4

1.2 Scope 4

1.3 Audience 5

1.4 Reference 5

2 Moving ECS agent install directory 6

2.1 Create appropriate directory structure. 6

2.2 Disable tcpdump process 6

2.3 Move the ECS install directory 7

2.4 Create appropriate ECS agent home directory 7

2.5 Enable tcpdump process 8

2.6 Verify ECS Processes 9

3 Address and Support 10

Table of Figures

Figure 1: System Architecture 4

1  Introduction

The ECS tool monitors the Video on Demand (VOD) infrastructure and provides statistics and error/event information from all the various components, which can help with troubleshooting problems throughout the network. As many different vendors provide system components for the TWC VOD infrastructure, the tool collects information from the various sources and brings it into a consolidated information model that can be used to monitor system health and troubleshoot problems.

In this chapter:

·  System Architecture

·  Scope

·  Audience

·  Reference

1.1  System Architecture

Events are collected in near real-time. An ECS agent gathers data from the source of the event and sends it to a central event database.

Figure 1: System Architecture

1.2  Scope

This document describes the steps to follow to move the ECS agent install from one disk filesystem to another on the DNCS.

1.3  Audience

This document is intended for system administrators responsible for upgrading the DNCS, and may be used by operators who will install and use ECS tool to monitor VOD traffic.

1.4  Reference

1  itaas_ECS_RemoteComponent_InstallGuide.pdf

2  Moving ECS agent install directory

itaas, Inc. recommends installing the ECS agent on any filesystem other than the root ‘/’ filesystem on any of the remote server’s of the VOD network. The steps in the below sections describe the process of moving the ECS agent from the ‘/’ filesystem on the DNCS to the ‘/export’ filesystem.

Note: During this agent re-location process, the tcpdump process is disabled for some time time (approx. 15 min); and as a result session data is lost for the time period when tcpdump is inactive.

2.1  Create appropriate directory structure.

1  Login as user root on the DNCS.

$ su -

2  Create appropriate directory structure to hold the distribution. Due to space limitations found at various divisions, ask the site which filesystem to use and create similar to the example that follows. Typically ‘/export’ filesystem is used, but ‘/disk1’ or any other filesystem as appropriate may be used.

# mkdir –p /export/home/dncs/itaas/ecs/opt/isaecs/

Note: It is not recommended to install the agent on the ‘/’ filesystem of the DNCS. Modify the above command if another location for agent install is selected.

2.2  Disable tcpdump process

1  Save the existing “/etc/inittab” file.

# cd /etc/

# cp inittab inittab.sav.tcpdump

2  Edit the /etc/inittab file to remove the tcpdump line from the file.

# vi /etc/inittab

3  Verify the difference between the saved and the modified ‘inittab’ file.

# diff inittab inittab.sav.tcpdump

bash-2.03# diff inittab inittab.sav.tcpdump

19a20

> xtd:234:respawn:/opt/isaecs/bin/tcpdumpCmd >/opt/isaecs/tcpdump/script.out 2&1

4  Disable the tcpdump process, by executing the below commands.

# init q

# ps –ef |grep tcpdump

Note: Issue the kill command given below to disable the currently running tcpdump process. Replace the ‘tcpPid’ with the process id generated by the output of the above ‘ps –ef’ command.

# kill -9 tcpPid

5  Verify that the tcpdump process is not running; and new tcpdump log is not getting created.

# ps –ef |grep tcp

# ls –lt /opt/isaecs/tcpdump |head

Note: Verify the timestamp on the latest tcpdump file. It should not show current time.

2.3  Move the ECS install directory

Once it is verified that the tcpdump process is disabled and new tcpdump logs are not getting created, proceed with the steps in this section.

1  Move the ECS install sub-directories to the new directory structure as created in step 2 of section 2.1.

# cd /export/home/dncs/itaas/ecs/opt/isaecs

Note: Modify the above ‘cd’ command as per the new directory path created in step 2 of section 2.1

# mv /opt/isaecs/* . &

2  Verify that the ECS directories are moved to the new directory.

# pwd

bash-2.03# pwd

/export/home/dncs/itaas/ecs/opt/isaecs

# ls –l

bash-2.03# ls -l

total 34

drwxr-xr-x 2 root other 512 Apr 25 2006 Docs

drwxr-xr-x 2 root other 512 Apr 25 2006 bin

drwxr-xr-x 2 root root 1024 Aug 9 2004 download

drwxr-xr-x 2 root other 1024 Apr 25 2006 install

drwxr-xr-x 2 root other 1024 Feb 21 02:20 logs

drwxr-xr-x 3 root other 8192 Sep 11 09:34 tcpdump

# ls –l tcpdump/

Note: Verify that all the tcpdump logs and contents of ‘old’ sub-directory under ‘tcpdump’ directory are in new location.

3  Verify the disk space on ‘/’ filesystem is reclaimed after moving the ECS agent on another filesystem on the DNCS.

# df -h

2.4  Create appropriate ECS agent home directory

1  Verify that the ‘/opt/isaecs’ directory is empty with no files.

# ls –l /opt/isaecs/

Note: If there is any file, make sure to move it to the new location as created in step 2 of section 2.1.

2  Delete the ‘/opt/isaecs’ directory which lies under ‘/’ filesystem of the DNCS.

# cd /opt/

# rm –R isaecs

3  Create appropriate ‘isaecs’ solftlink to the desired location within the /opt directory.

# ln –s /export/home/dncs/itaas/ecs/opt/isaecs/ /opt/isaecs

Note: Modify the above ‘ln’ command to reflect the change in the directory path as created in step 2 of section 2.1 above.

# ls –l /opt

lrwxrwxrwx 1 root root 13 Sep 18 12:34 isaecs à /export/home/dncs/itaas/ecs/opt/isaecs/

# ls –l /opt/isaecs/

bash-2.03# ls -l

total 34

drwxr-xr-x 2 root other 512 Apr 25 2006 Docs

drwxr-xr-x 2 root other 512 Apr 25 2006 bin

drwxr-xr-x 2 root root 1024 Aug 9 2004 download

drwxr-xr-x 2 root other 1024 Apr 25 2006 install

drwxr-xr-x 2 root other 1024 Feb 21 02:20 logs

drwxr-xr-x 3 root other 8192 Sep 11 09:34 tcpdump

2.5  Enable tcpdump process

1  Edit the ‘/etc/inittab’ to add the tcpdump line.

# cd /etc/

# cp inittab inittab.orig.notcpdump

# mv inittab.sav.tcpdump inittab

2  Verify that the ‘/etc/inittab’ file has the below tcpdump line.

# grep tcpdump /etc/inittab

xtd:234:respawn:/opt/isaecs/bin/tcpdumpCmd >/opt/isaecs/tcpdump/script.out 2&1

Note: This tcpdump line entry, with the word respawn, is required in case this process gets killed due to some reason; it will automatically get re-launched and will NOT result in loss of any tcpdump packets.

If the DNCS system is not a V890 server running Solaris 10, then the above tcpdump line does not require the ‘x’ at the beginning of the line. The tcpdump line will be as shown below.

td:234:respawn:/opt/isaecs/bin/tcpdumpCmd >/opt/isaecs/tcpdump/script.out 2&1

This is because the inittab entry begining with a ‘t’ does not allow a telnet session to the V890 DNCS remotely.

3  Start the tcpdump process.

# init q

The above command reads the “/etc/inittab” file, and will start the new process because of the respawn keyword.

4  Verify that the tcpdump process started.

# ps –ef |grep tcpdump

2.6  Verify ECS Processes

1  Verify that recent tcpdump logs are being produced under “/opt/isaecs/tcpdump” folder.

2  Verify that crontab has entry for “/opt/isaecs/bin/rsync_cronjob” and “/opt/isaecs/bin/logClean” processes. In addition, verify that these processes have executable permissions.

# crontab –l

0,5,10,15,20,25,30,35,40,45,50,55 * * * * /opt/isaecs/bin/rsync_cronjob

20 2 * * * /opt/isaecs/bin/logClean

Note: If the DNCS system is a V890 server and is running Solaris 10, then the cronjob ‘rsync_cronjob’ needs to be replaced by ‘rsyncDNCS’. This is because the system cron does not execute the softlink file. Edit the file ‘/var/spool/cron/crontabs/root’ to make changes to the crontab.

3  Check the current “/opt/isaecs”logs/rsync*.log” for error messages to verify that all logs (tcpdump,dsm,drm,qam) are being rsynced over to the ECS server.

3  Address and Support

For questions about re-configuring the ECS agent on the DNCS server that were not answered here, you can contact the itaas ECS Support team at:

Email:

Phone: 770-368-4024 (Between 8.30 a.m. to 5.30 p.m. EST Monday to Friday)

For support after business hours, please contact 1-888-Go-itaas (1-888-464-8227).

Our office address:

itaas Inc.

11695 John's Creek Parkway, Suite 300,

Duluth, GA 30097

Tel: 770-368-4024

Fax: 770-246-0616

Email:

Website: www.itaas.com

- 3 - itaas, Inc., Confidential and Proprietary