Importing Location Information Into Cisco Emergency Responder

Introduction

The Tellabs CER Data Utility is provided to facilitate the importing of data into the Cisco CER (Cisco Emergency Response) system. The utility will query the targeted OLTs LLDP data and retrieve equipment data that matches a specified system description name. This utility will perform a one-time execution (and data retrieval).  The Windows system scheduler must be used if the utility needs to be executed at regular intervals.   

This utility does not perform the import into the Cisco CER system.  After the utility has been executed and the data has been obtained, separate steps to import the data into the Cisco CER must be taken.   Those steps are not covered in this document.    

Document Number

ENG-010609

Applies To

Tellabs OLT SR29.2 or above and any EMS version are supported.

Installation

The Tellabs utility is distributed in the form of a zip file.   The latest version can be obtained from TAC personnel.   After obtaining the zip file (SshExpect_FP29V2.0.zip), unzip it onto your root drive (C:).  Open a cmd shell and traverse to the following folder:

The contents of the folder are displayed below;

Configuration

Configuration of the utility is provided via an XML file.  The XML file contains data necessary to connect to targeted OLTs (as well as the AID of the targeted equipment/QOIUs).

The format of the configuration XML is as follows;

<?xml version="1.0" encoding="utf-8"?>

<data-config>

                <olt-data ip="xxx.xxx.xxx.xxx">

                                <pon-list>10-1,10-2,10-3,10-4</pon-list>

                                <device-list>Cisco</device-list>

                                <olt-banner>false</olt-banner>

                                <ssh-username>user</ssh-username>

                                <ssh-password>password</ssh-password>

                </olt-data>

</data-config>

The configuration XML consists of one data-config category and may contain multiple olt-data categories (each targeting a separate OLT).

The attributes are as follows: 

• ip - The IP address of the OLT
• pon-list - The list on QOIUs to target.  This may also contain the keyword all (to search all the QOIUs).  Using the keyword all is much slower than specifying AIDs.
• device-list - The utility will search the LLDP System Description for this specific type of equipment. The devices we care about.  Ex. Cisco,Polycom
• olt-banner - This value must be either true or false.  It should be specified as true only if the targeted OLT has been configured to use a security/login banner.    
• ssh-username - The craft user name.  Ensure that this is not a new user and there is no password expiry and/or prompt for a password change pending.   
• ssh-password - The craft user password in plain text.  After the first run, the given password is encrypted and written back to the xml configuration file (in encrypted format).   

A sample configuration file is provided with the distribution (SshToCliConfigCreds.xml).  This file can be copied and used as a template.  Do not leave unused olt-data categories.  Either remove them or comment them out.

Utility Execution

To run the Tellabs CER Data Utility, perform the following steps;

1) Ensure the XML file has been configured accordingly.  

2) Open a cmd shell and traverse to the following folder;

C:SshExpect_FP29V2.0SshExpect_FP29FullBundlewinSshExpect

3) Run the utility given the following syntax;

SshLldp.bat -in <confing.xml> -out <output.txt> -log <command.log> 

in - The configuration xml file

out - This parameter is optional and new to V2.0. The resultant output (STDOUT) is saved to the file specified.

log - The log file. It will contain all the CLI command output as well as OLT and AID information. 

ex.

The following example is using the attached configuration xml file;

C:SshExpect_FP29V2.0SshExpect_FP29FullBundlewinSshExpect>SshLldp.bat -in c:SshExpectSshToCliConfigCreds.xml -out c:installersmyoutput.txt -log c:installersoutput.log 

,Cisco IP Phone 7961G-GE,SCCP41.9-4-2-1S,172.28.76.20,001646CB5609,,Kerwin's Phone - green cable

,Cisco IP Phone 7961G-GE,SCCP41.9-4-2-1S,172.28.76.10,001646CB5764,,Frank's Phone

,Cisco IP Phone 7945G,SCCP45.9-4-2-1S,172.28.76.28,E8BA70FA04F1,,Gainer's Phone

,Cisco IP Phone 7945G,SCCP45.9-4-2-1S,172.28.76.4,E8BA70076B2A,,Duncan's Phone

,Cisco IP Phone 7945G,SCCP45.9-4-2-1S,172.28.76.26,E8BA70FA0427,,Willis-Phone

,Cisco IP Phone 7961G-GE,SCCP41.9-4-2-1S,172.28.76.14,001819230A1A,,Wisnoski's Phone/PC

,Cisco IP Phone 7945G,SCCP45.9-4-2-1S,172.28.76.8,1CAA07107AF9,,Hornok's Phone/PC

,Cisco IP Phone 7945G,SCCP45.9-4-2-1S,172.28.76.6,1CAA071079A9,,Tom's PC

,Cisco IP Phone 7945G,SCCP45.9-4-2-1S,172.28.76.32,FCFBFBCAD675,,Jeffs Phone

,Cisco IP Phone 7961G-GE,SCCP41.9-4-2-1S,172.28.75.108,001646CB5646,,

If the script cannot login to the OLT you will get an authentication error (in red).

172.28.152.113,Error: Authentication Failed!   

The format of the output is as follows;

Extension (leave Blank), Type, Version, IPAddress, MACAddress, ERLName (leave blank), Location

Summary

Using the script will allow you to extract the location information of phones attached to the Tellabs OLT and ONTs in a form that can then be added to Cisco Emergency Responder.