Loader

Bulk UNI Provisioning

Panorama PON includes a "Bulk UNI Provisioning" script which enables users to more quickly provision UNIs, bypassing the manual UNI provisioning and activation procedures. For the typical GUI procedures, refer to “Provisioning Data Cross-Connections”.

Bulk UNI Provisioning, is typically performed following auto-provisioning of the OLT (refer to “Auto-Provisioning”). The bulk provisioning script does not “provision” the UNI, but rather automatically applies User Labels to each UNI auto-provisioned during the Add NE process (refer to “Adding a Network Element”. The UNI Bulk Provisioning script applies User Labels to auto-provisioned UNIs at approximately 3 UNIs per second vs. 20–30 seconds each if entered manually into pre-provisioned UNIs.

To manually provision UNIs, including the User Label, refer to “Provisioning Data Cross-Connections”.

The Panorama PON CD ROMs (provided for Windows contain the bulk provisioning scripts, provisionUNI.bat.

The UNI bulk provisioning script takes up to eight arguments, in a comma-separated value (.csv) input file, as listed in the following table.

Field

Description

Notes

IP Address

Internet Protocol (IP) address of the OLT

Required, if auto not specified

Slot

QOIU slot in the OLT (1-16 if Tellabs 1150 MDS5 OLT, 1-14 if Tellabs 1150 MDS7 OLT, or 1-4 is Tellabs 1134 OLT)

Required, if auto not specified

PON

Port on the QOIU (1-4) serving the PON device

Required, if auto not specified

ONT

ONT served by the PON device connected to the QOIU port (1-32)

Required, if auto not specified

Serial Number

Serial number of the ONT, consisting of a four-letter manufacturer code; i.e., TSLS for Tellabs, followed by an eight hexadecimal (0 to F) character serial number.

Required
Must contain 12
alpha-numeric characters

UNI

(1-24)

Required

UNI Label

Free-form text informational field.

Note 1: A maximum of 32 characters is allowed. Commas are not allowed. This information, if used, is displayed in the Common Tree (refer to “Common Tree”).

Note 2: Spaces are allowed in the UNI Label, i.e., My ONT. When spaces are included, enclose the UNI Label in double-quotes, i.e., “My ONT”.

Required

Auto

Optional – If UNIs are configured to auto, enter “auto” in this field.

Note: When “auto” is specified, the values specified in ipaddress, slot, pon, and ont are ignored during import, but may contain data.

Optional


Use the following procedure to utilize the UNI Bulk Provisioning script:

  1. Create a .csv input file, with the required field information, in a format shown in the input file example above. To make a .csv file, a spreadsheet program, such as Microsoft® Excel on the Windows platform, or a utility editor such as TextEditor. Create the file with one header row as shown in the following example:
Note: The header row is required but is ignored from being processed by the utility.

An example input.csv input file is shown below:


IPAddress,Slot,PON,ONT,Serial Number,UNI,UNI Label,Auto 172.28.128.207,1,4,27,TSLS0000001,3,UNILabel27,

,,,,TSLS00001215,3,1215,auto 172.28.128.207,1,4,28,TSLS00000028,3,,

,,,,TSLS00000002,3,uni1,auto

,,,,TSLS0000001,3,uni2,auto

,,,,TSLS000000%1,3,uni3,auto

,,,,TSLS00000001,3,uni4,abcd 1.1.1.1,1,1,1,MEEN00001111,3,uni5,auto

172.28.136.193,1,1,1,MEEN00001111,3,uni6,

172.28.136.193,1,2,1,MEEN00001111,3,,
,,,,SHGJ00001234,4,Cubicle 14 Dobozy Port1,auto


Upon executing the script (provisionUNI.ksh), the UNI data is processed one line at a time to the provisioning database, creating an output file as shown below.


C:\Tellabs\PanoramaPON\bbmgr\client1400>provisionUNI.bat C:\Tellabs\PanoramaPON\bbmgr\clie nt1400\UNIData.csv

Contacting EMS server at 172.28.103.29 and port 7101 Connected to EMS server

Reading data from input file C:\Tellabs\PanoramaPON\bbmgr\client1400\UNIData.csv Processing UNI data 172.28.128.207,1,4,27,TSLS0000001,3,UNILabel27,,SUCCEEDED

Processing UNI data ,,,,TSLS00001215,3,1215,auto,SUCCEEDED

Processing UNI data 172.28.128.207,1,4,28,TSLS00000028,3,,,INVALID INPUT,Fewer than expect ed fields in the data

Processing UNI data ,,,,TSLS00000002,3,uni1,auto,FAILED,Cannot locate the ONT with the ser ial number TSLS00000002

Processing UNI data ,,,,TSLS0000001,3,uni2,auto,INVALID INPUT,Invalid ONT Serial Number:TS LS0000001. It has to be 12 characters.

Processing UNI data ,,,,TSLS000000%1,3,uni3,auto,INVALID INPUT,Invalid ONT Serial Number:T SLS000000%1. It should have only alphanumeric characters.

Processing UNI data ,,,,TSLS00000001,3,uni4,abcd,INVALID INPUT,Invalid auto mode:abcd. It is not blank it should be auto or AUTO

Processing UNI data 1.1.1.1,1,1,1,MEEN00001111,3,uni5,auto,FAILED,Cannot locate the ONT wi th the serial number MEEN00001111

Processing UNI data 172.28.136.193,1,1,1,MEEN00001111,3,uni6,,SUCCEEDED

Processing UNI data 172.28.136.193,1,2,1,MEEN00001111,3,,,INVALID INPUT,Fewer than expecte d fields in the data

Processing UNI data ,,,,SHGJ00001234,4,Cubicle 14 Dobozy Port1,auto,SUCCEEDED
UNI provisioning is complete, the summary file can be found at C:\Tellabs\PanoramaPON\bbmg r\client1400\UNIData_summary.csv


If there are duplicate entries, the last entry encountered is the entry that appears in the database. A summary (*_summary.csv) file is generated providing a record of the processing and any failures that may have been encountered. The summary file is saved to the same folder containing the original .csv file. An example of the *_summary.csv file is shown below:


IPAddress,Slot,PON,ONT,Serial Number,UNI,UNI Label,Auto,Status,Details 172.28.128.207,1,4,27,TSLS0000001,3,UNILabel27,,SUCCEEDED

,,,,TSLS00001215,3,1215,auto,SUCCEEDED

172.28.128.207,1,4,28,TSLS00000028,3,,,INVALID INPUT,Fewer than expected fields in the data

,,,,TSLS00000002,3,uni1,auto,FAILED,Cannot locate the ONT with the serial number TSLS00000002

,,,,TSLS0000001,3,uni2,auto,INVALID INPUT,Invalid ONT Serial Number:TSLS0000001. Must only contain 12 alpha-numeric characters

,,,,TSLS000000%1,3,uni3,auto,INVALID INPUT,Invalid ONT Serial Number:TSLS000000%1. Must only contain 12 alpha-numeric characters

,,,,TSLS00000001,3,uni4,abcd,INVALID INPUT,Invalid auto mode:abcd. If not blank, it must be auto or AUTO

1.1.1.1,1,1,1,MEEN00001111,3,uni5,auto,FAILED,Cannot locate the ONT with the serial number MEEN00001111

172.28.136.193,1,1,1,MEEN00001111,3,uni6,,SUCCEEDED

172.28.136.193,1,2,1,MEEN00001111,3,,,INVALID INPUT,Fewer than expected fields in the data
,,,,SHGJ00001234,4,Cubicle 14 Dobozy Port1,auto,SUCCEEDED


 

The contents of the .csv input file should contain one line for each UNI to be provisioned, with each of the data fields separated by a comma. The example below shows a typical UNI data file created in Microsoft ® Excel:


 

  1. Save the input file as CSV (Comma-Separated Value) format file.
  2. When the data input file has been created, it must be copied to the client machine.
    Note 1: ASCII files created on a Windows platform contain an extra carriage-return character at the end of each line which must be removed.
    Note 2: If the script is being executed from a remote client, the IP address and, optionally, the RMI port address, if not the default RMI port address (7101 for Windows) of the other server, are required.
  1. On Windows, open a command window, with elevated privileges, and navigate to the folder containing the provisionONT.bat batch file.
           cd c:\Tellabs\PanoramaPON\bbmgr\client
  2. In the command window, enter the following command, and press Enter.
           provisionONT.bat c:\temp\input.csv 1.2.3.4 xxxx

 

where:

   – c:\temp\input.csv – represents the location and name of the .csv file

Note 1: If executed from the client installed with the server, the GUI Client, the following options are not required. If executed from a remote client, one or both of the following options are required.

 

–1.2.3.4 – represents the IP address of the target server (required if the script is being executed from a remote client)

           and

Note 1: If the RMI port is not the default (1101) the IP address of the server is also required.

– xxxx – represents the RMI port of the target server (required if the server RMI port is not the default OR the script is being executed from a remote client and the RMI port of the target server is not the default of 7101)

 

  1. As each entry in the .csv file is executed, the entry is displayed, followed by the status.
  2. Upon completion, an output summary file is generated in the same directory as the input file.
  3. Check the output file, i.e., summary_input.csv, for a listing of provisioned UNIs, as well as any possible errors and causes.
  4. The UNI User labels can be verified by checking the Ethernet Port Status and Configuration (refer to “Viewing Ethernet Port Status and Configurations”) of the desired OLT.

 

FEEDBACK: Are you happy with this material?