EN/LZTBU 880 103 RA

ascom Transmission

Engineering Bulletin

Customer ID handling

Note: This document does not claim integrity and accuracy in detail.

This document is protected by copyright. All rights in this c onnection remainwith Ascom Transmission AG.

We reserve the right to make changes at any time without prior notice.

Order number: EN/LZTBU 880 103 RA

Ascom Transmission AGSchwarzenburgstrasse 73CH-3097 Bern/LiebefeldSwitzerland March 2002 by Ascom Transmission AG

ascom Transmission

EN/LZTBU 880 103 RA Engineering Bulletin iii

Table of contents i1. How to change the Customer Identifier in a UMUX

How to renew a Central Card How to modify aUNEM installation with a Customer Identifier 1-1

1.1.1. Abstract 1-11.1.2. References to the Customer documentation 1-11.1.3. Validation 1-21.1.4. Terms used in this Application Note 1-2

1.2. What you should know 1-3

2. Steps to change or remove a Customer ID when theCustomer ID is known 2-1

3. Steps to remove a Customer ID on aUMUX1200/1500 if the old Customer ID is NOTknown 3-1

4. Steps to remove a Customer ID on aUMUX1100/1300 if the old Customer ID is NOTknown 4-1

5. Renew a COBU hardware 5-1

6. Renew a CENCA hardware 6-1

7. Implement a CID in UNEM R4E and newer 7-1

ascom Transmission

EN/LZTBU 880 103 RA Engineering Bulletin 1-1

1. How to change the CustomerIdentifier in a UMUX

How to renew a Central Card

How to modify a UNEMinstallation with a CustomerIdentifier

1.1.1. AbstractThis document describes how

to change a Custom ID on a UMUX to renew a central card CENCA and COBU to implement a CID in the UNEM version R4

Such a change can be necessary

because the UNEM R4 handles Customer ID and system access passwords in adifferent way to the UNEM R3.

to maintain correct operation of the management function when upgrading fromUNEM R3 to UNEM R4 and above.

1.1.2. References to the Customer documentationFor details of the

Customer ID and the handling of the Customer ID, refer to the User Guide UCST /UCST /UCST /UCST /System Operation BasicsSystem Operation BasicsSystem Operation BasicsSystem Operation Basics [401], chapter 2 "Installation Procedures".

Maintenance of the control unit, refer to the User Guides

UMUX 1500UMUX 1500UMUX 1500UMUX 1500 [302], chapter 7 "Maintenance".

COBUX/COBUVCOBUX/COBUVCOBUX/COBUVCOBUX/COBUV [315], section "Maintenance"

ascom Transmission

1-2 Engineering Bulletin EN/LZTBU 880 103 RA

1.1.3. ValidationThe described procedures are valid for

UMUX 1100 UMUX 1200 UMUX 1300 UMUX 1500 DSL line system (COLT-2) UNEM R4 UNEM R5 All UCST versions

1.1.4. Terms used in this Application NoteCID Customer ID

CID_old Customer ID which is originally stored in the NE

CID_new New Customer ID, can also be an empty CIDwhich is equal to "no CID"

UMUX_oldcid Name of an entry in the UCST dialogue ManagedNEs containing the CID_old

UMUX_newcid Name of an entry in the UCST dialogue ManagedNEs containing the CID_new

EM Element Manager (PC, Notebook, Workstation)

NE Network Element (UMUX)

ascom Transmission

EN/LZTBU 880 103 RA Engineering Bulletin 1-3

1.2. What you should know

The EM (UCST or UNEM) can only manage a NE (UMUX) if the Customer Identifiers of theEM and the NE are matching.

The Customer Identifier of the NE is loaded during the initial commissioning.

If you have to re-install the UCST, the loss of the Customer Identifier is fatal andloss of the Customer Identifier is fatal andloss of the Customer Identifier is fatal andloss of the Customer Identifier is fatal andwill force you to reset and reconfigure all NEs will force you to reset and reconfigure all NEs will force you to reset and reconfigure all NEs will force you to reset and reconfigure all NEs that you have configured withthis particular identifier and installation of UCST!

The Customer Identifier labels a particular installation of the UCST and all theNEs configured with it. Since the identifier is loaded to the NEs, there is no wayno wayno wayno wayto access these NEs with any other Customer Identifier unless you reset andreconfigure the NE!

As soon as you assign a Customer Identifier Customer Identifier Customer Identifier Customer Identifier, it is highly recommended that you store theidentifier together with the password for System ManagerSystem ManagerSystem ManagerSystem Manager in a safe placesafe placesafe placesafe place.

A UNEM can handle one CID only. Therefore you cannot manage UMUXs withdifferent CID with the same UNEM.

If you create a new entry of a NE in the UCST dialogue Managed NEsManaged NEsManaged NEsManaged NEs then thecurrent CID of the UCST is part of this new created entry.

Even if you change the CID of the UCST with the tool "Customer IdentifierSetup" the existing Managed NEsManaged NEsManaged NEsManaged NEs entries keep their old CID!

Therefore it is possible to have two names (entries) in the Managed NEsManaged NEsManaged NEsManaged NEs section,one with the old CID and one with the new CID!

The UMUX_oldcid was added with the original CID definition, theUMUX_newcid was added after you modified the CID (see Step 3 below).

As soon as you apply a download to a UMUX then the currentcurrentcurrentcurrent UCST CID isstored in the UMUX independent of the selected name in the Managed NEsManaged NEsManaged NEsManaged NEs list.

ascom Transmission

EN/LZTBU 880 103 RA Engineering Bulletin 2-1

2. Steps to change or remove aCustomer ID when the CustomerID is known

Prerequisites:

You need to have access to the NE with a UCST containing the CID_old and theUMUX_oldcid.

Step 1:

Establish a connection to the NE containing the CID_old with the existing Managed NEsname UMUX_oldcid.This step is to check the Prerequisites described above.

Step 2:

If everything works fine, close the UCST.

Step 3:

Modify the CID with the tool "Customer Identifier Setup". You find this tool in thewindows menu

Note: You need to know the System ManagerSystem ManagerSystem ManagerSystem Manager password!

ascom Transmission

2-2 Engineering Bulletin EN/LZTBU 880 103 RA

Step 4:

Open the UCST again

Step 5:

Upload the config of the UMUX with the Managed NEManaged NEManaged NEManaged NE name UMUX_oldcid.

Step 6:

Apply a partial download The new CID is set now in the UMUX.

Step 7:

Add a new Managed NEManaged NEManaged NEManaged NE name UMUX_newcid with the same parameters as theUMUX_oldcid.

You can now connect to the UMUX with the UMUX_newcid only!

ascom Transmission

EN/LZTBU 880 103 RA Engineering Bulletin 3-1

3. Steps to remove a Customer ID ona UMUX1200/1500 if the oldCustomer ID is NOT known

In this case you have to replace the central controller unit hardware (COBU) with a"factory new" new one. The chapter 5 and 6 in this document explains you how you canrenew a used COBU or CENCA hardware.

To save the current running configuration of the NE you must be able to access the NEwith a UCST having the correct CID_old installed (step 1). If such a UCST is not availablethen you will loose the configuration and therefore have to reconfigure the whole NE fromscratch, beginning with step 3.

Step 1:

Establish a connection to the NE containing the CID_old with the existing Managed NEsManaged NEsManaged NEsManaged NEsname UMUX_oldcid.Apply an upload and store the configuration in a file.

Step 2:

Modify the CID with the tool "Customer Identifier Setup". Define as CID the CID_newwhere CID_new could also be an empty CID (means no CID).

As an alternative you can also do a new installation of the whole UCST. This could also bedone with a newer UCST version. Define the CID_new during the installation processwhere CID_new could also be an empty CID (means no CID).

Note: You can install several UCSTs in parallel on the same PC, one with the CID_old andanother with the CID_new.

After the installation, define the Managed NEManaged NEManaged NEManaged NE name UMUX_newcid with the defaultdefaultdefaultdefault IPaddress:Node ID: 10.1.1.1.

Set on your EM also the UCST RAS direct on FUCST RAS direct on FUCST RAS direct on FUCST RAS direct on F IP address to 10.1.1.200.

Step 3:

Remove the central controller unit COBU and replace it with a new one. You do nothave to power off the UMUX.

You loose the traffic for about 3 minutes.

Step 4:

Wait until the new central unit COBU has rebooted. Connect then to the UMUX withthe new created Managed NEManaged NEManaged NEManaged NE name UMUX_newcid with the defaultdefaultdefaultdefault IP addresses.

ascom Transmission

3-2 Engineering Bulletin EN/LZTBU 880 103 RA

Step 5:

Open the safed configuration file and proceed a partial download. This will fail due to thewrong configuration identifier. Proceed now a full download.

After the full download the UMUX will have

the CID_new and its original Node ID address.

Therefore you have to update again

the UCST RAS direct on FUCST RAS direct on FUCST RAS direct on FUCST RAS direct on F IP address to the original address modify the Managed NEManaged NEManaged NEManaged NE name UMUX_newcid with the originaloriginaloriginaloriginal IP address.

ascom Transmission

EN/LZTBU 880 103 RA Engineering Bulletin 4-1

4. Steps to remove a Customer ID ona UMUX1100/1300 if the oldCustomer ID is NOT known

In this case you have to replace the central controller unit hardware (CENCA) with an"empty" new one.

To save the current running configuration of the NE you have to be able to access the NEwith a UCST having the correct CID_old installed (see step 1). If such a UCST is notavailable then you will loose the configuration and therefore have to reconfigure thewhole NE from scratch.

Step 1:

Establish a connection to the NE containing the CID_old with the existing Managed NEsManaged NEsManaged NEsManaged NEsname UMUX_oldcid.Apply an upload and store the configuration in a file.

Step 2:

Modify the CID with the tool "Customer Identifier Setup". Define as CID the CID_newwhere CID_new could also be an empty CID (means no CID).

As an alternative you can also do a new installation of the whole UCST. This could also bedone with a newer UCST version. Define the CID_new during the installation processwhere CID_new could also be an empty CID (means no CID).

Note: You can install several UCSTs in parallel on the same PC, one with the CID_old andanother with the CID_new.

After the installation, define the Managed NEManaged NEManaged NEManaged NE name UMUX_newcid with the correct HDLCaddress "0".

Step 3:

Remove the central controller unit CENCA and replace it with a new one. You do not haveto power off the UMUX.

You loose the traffic for about 3 minutes.

Step 4:

Wait until the new central unit CENCA has rebooted. Connect then to the UMUX with thenew created Managed NEManaged NEManaged NEManaged NE name UMUX_newcid with the defaultdefaultdefaultdefault HDLC address "0".

ascom Transmission

4-2 Engineering Bulletin EN/LZTBU 880 103 RA

Step 5:

Open the safed configuration file and proceed a partial download. This will fail due to thewrong configuration identifier. Proceed now a full download.

After the full download the UMUX will have

the CID_new and its original HDLC address.

Therefore you have to

modify the Managed NEManaged NEManaged NEManaged NE name UMUX_newcid with the originaloriginaloriginaloriginal HDLC address.

ascom Transmission

EN/LZTBU 880 103 RA Engineering Bulletin 5-1

5. Renew a COBU hardware

The following procedure renews a COBU unit. After you proceeded the following stepyour COBU unit has the same state as a factory new HW of the COBU except thefirmware files which remains on the COBU.

A renewed COBU has

the default Node Id address 10.1.1.1 the default Ethernet address 10.1.2.1 no CID

Step 1:

Place the COBU on a suitable work surface with the FLASH-card facing up.

Please be aware that the COBU hardware is sensitive to electrostaticdischarges.

Step 2:

Remove the FLASH-card from the COBU and insert it into a PC with a PCMCIA slot.This PC must be capable to access the FLASH card. Therefore you need to run a designatedsoftware. Ask your PC vendor for such a software.

Step 3:

Delete on the FLASH-card ALLALLALLALL directories except the FW.

Step 4:

This is also a possibility to copy or replace any unit firmware files: Copy all necessary unitfirmware files into the \FW\ directory.

ascom Transmission

5-2 Engineering Bulletin EN/LZTBU 880 103 RA

Step 5:

After the PC has finished writing/deleting on the FLASH-card remove it from the PC andinsert it back into the COBU.

Some PCs take a long time to handle files on the FLASH-card. If you remove aFLASH-card from the PC before all files are written/deleted then the FLASH-cardbecomes corrupted. So give the PC enough time to write/delete all the files!Note: Writing several unit software files to the FLASH-card can last up to severalminutes.

Step 6:

Insert the FLASH-card back into the COBU hardware.

The COBU unit is now renewed and available for use in the UMUX1200 andUMUX1500.

ascom Transmission

EN/LZTBU 880 103 RA Engineering Bulletin 6-1

6. Renew a CENCA hardware

The following procedure renews a CENCA unit. After you proceeded the following stepyour CENCA unit has the same state as a factory new HW of the CENCA.

The whole configuration information including the CID is stored in a FLASH-EEPROM onCENCA. The following steps explain how to erase the FLASH_EEPROM without any specialequipment so you can proceed it also in the field.

Please be aware that you will also loose the configuration information!

Step 1:

Place the CENCA on a suitable work surface.

Please be aware that the CENCA hardware is sensitive to electrostatic discharges.

Step 2:

Remove the FLASH-EEPROM (DIL 32 case) out of position A and place it in position B.

Step 3:

Insert the CENCA in a powered UMUX1100 or UMUX1300. You can insert it in any freeslot. Leave the unit at least 30 seconds in the shelf and then remove it again.Note: This erases automatically the whole content of the FLASH_EEPROM.

The CENCA unit is now renewed and available for use in the UMUX1100 and UMUX1300.

ascom Transmission

EN/LZTBU 880 103 RA Engineering Bulletin 7-1

7. Implement a CID in UNEM R4Eand newer

From the UNEM version R4 you cannot set the Customer ID anymore during the UNEMinstallation process. This may result in practical problems if you have to manage alreadyinstalled NEs which are configured with a CID.

Ascom generally recommends to remove all CIDs from the UMUX as described in theformer chapters. If due to any reason you cannot remove them then you have to upgradethe UNEM installation.

The following section is a guideline how you can add a CID to an existing UNEMinstallation.

The idea is that you define the CID in a UCST installation and then copy the relevant codedCID information from the UCST installation to the UNEM installation.

What you should know

In a UCST and UNEM installation you have several passwords such as CID and User classes.All these passwords are stored in a coded way in the UCST.INI file.

It is important to know that the CID password is linked with the user classpasswords:If you change the CID then the coded entries in the UCST.INI file of the userclasses will change too even if you did not change the user class password!

Step 1:

You need to have a UCST installation with the same CID definition as configured on theUMUX you want to manage.

Check whether you are able to connect with the UCST to one of the UMUX. If this ispossible then you are sure that both CIDs, the one in the UCST installation and the onedownloaded in the UMUX, matches together.

Step 2:

Locate on your EM the UCST home directory. The default location is

c:\Program files\uCST Rxy

but this will vary depending on the individual installation.

Open the file ucst.ini and scroll down to the end of the file. There you find the section[UCST Rxy] similar to this:

[UCST Rxy]CstId=24872PWD124872=15998PWD224872=38416PWD324872=2501PWD424872=52957

ascom Transmission

7-2 Engineering Bulletin EN/LZTBU 880 103 RA

You must now copy all the entries of your UCST to the UNEM installation.

Step 3:

Log in on your workstation as the unemadmunemadmunemadmunemadm. Close

all running UCST windows. All maps and also the Main Window.

Open the "UNEM Administration Tool" and double-click on the "Startup and Shutdown"icon.

Apply the "Status Stop Stop Core Components ONLY" command and wait until allCore Components are shutdown.

Step 4:

Open the File Manager.

Change to the folder

/unem/cst

and edit the file ucst.ini. At the bottom of the file you find the section [UCST Rxy] similar tothis:

[UCST Rxy]CstId=0PWD10=27762PWD20=33558PWD30=55754PWD40=21967

The "0" at the end of the line "CstId=0" tells you that there is no CID set yet.

You now have to update all 5 linesall 5 linesall 5 linesall 5 lines according the read-out of the UCST (step 2).

In our exampleour exampleour exampleour example the section must look like

[UCST Rxy]CstId=24872PWD124872=15998PWD224872=38416PWD324872=2501PWD424872=52957

Of course YOUR entry must have the appropriate numbers as read-out by your UCST.

Safe the ucst.ini file and close it.

Step 5:

You now have to restart the UNEM core components:

Apply the "Status Start Start Core Components ONLY" command and wait until allCore Components are running.

ascom Transmission

EN/LZTBU 880 103 RA Engineering Bulletin 7-3

Restart the UNEM main window and open your map(s).

Step 6:

You now have to delete ALL Managed NE'sManaged NE'sManaged NE'sManaged NE's entries and re-add them from new.

Note: You remember that the CID is also stored in the Managed NE'sManaged NE'sManaged NE'sManaged NE's entries. That's whyyou have to recreate them.

Step 7:

Add the NE symbol to your map for all NEs.

The UNEM should now discover, upload and manage the NEs.

Back to the ListBack to the Index1. How to change the Customer Identifier in a UMUX How to renew a Central Card How to modify a UNEM installation with a CuAbstractReferences to the Customer documentationValidationTerms used in this Application NoteWhat you should know2. Steps to change or remove a Customer ID when the Customer ID is known3. Steps to remove a Customer ID on a UMUX1200/1500 if the old Customer ID is NOT known4. Steps to remove a Customer ID on a UMUX1100/1300 if the old Customer ID is NOT known5. Renew a COBU hardware6. Renew a CENCA hardware7. Implement a CID in UNEM R4E and newer