NN20000-316 05.02 MTX18 Cdma Configuration

CDMA

Core and Billing Manager 850Configuration Management forCDMARelease: MTX18Document Revision: 05.02

NN20000-316.

CDMARelease: MTX18Publication: NN20000-316Document release date: 28 July 2010

© Ericsson AB 2010. All rights reserved. No part of this document may be reproduced in any form without thewritten permission of the copyright owner.

The contents of this document are subject to revision without notice due to continued progress in methodology,design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from theuse of this document.

All trademarks are the property of their respective owners.

.

3.

ContentsNew in this release 5Features 5Other changes 6

SPFS-based server functions 7Installing and configuring the Passport Log Streamer application 8Enabling or disabling the tuple number configuration for the OMDD

application 14Configuring the Passport OMs using OMDD application 16Configuring log delivery destinations 19Modifying a log device using logroute 23Deleting a device using logroute 28Configuring log delivery for MDM/PPEM security and audit logs (MDM 601 and

PPEM 601) 31Excluding MDM/PPEM audit and security logs from other log devices 35Specifying the logs delivered from the CM to the Core and Billing Manager 48Configuring log delivery global parameters 52Configuring the GDD parameter using logroute 57Configuring outbound connection security for OMDD 59Configuring CBM LI Proxy application 64Adding or deleting a downstream LI server trust certificate for the CBM LI Proxy

application 68Configuring the time zone option of the OM delivery application 70Configuring core access for SBRM through the CBM 850 73Creating the backup user ID on the core for SBRM 75Commissioning or decommissioning Network Time Protocol (NTP) 77Adding or removing an NTP server or peer 86Installing the logreceiver tool on a client workstation 89Installing the CMFT on a client workstation 91Configuring the SuperNode Billing Application 93Installing SCFT 94Enabling the second LAN interface on the CBM 96Configuring the second LAN interface on the CBM 98Disabling the second LAN interface on the CBM 101Selecting the highest priority interface for CBM MultiNet failover 103

CDMACore and Billing Manager 850 Configuration Management for CDMA

NN20000-316 05.02 28 July 2010

.

4

Enabling the third LAN interface 105Configuring the third LAN interface 107Disabling the third LAN interface 109Querying the port status of uplink0, uplink2, and uplink3 111Changing the IP address for uplink3 113Associating a logical OAM tag with a physical interface 115Installing optional software on a CBM 850 117Configuring a virtual IP address on an SPFS-based server 123Configuring client and server ports on an SPFS-based server for secure Firewall

communications 128Provisioning static routes on an SPFS-based server 131Logging in to an SPFS-based server 145Configuring OSS and application services 151Configuring OSS communications services 152


NN20000-316 05.02 28 July 2010

.

5.

New in this releaseThe following sections detail what is new in Core and Billing Manager 850Configuration Management for CDMA (NN20000-316) for this release.

• “Features” (page 5)

• “Other changes” (page 6)

ATTENTIONThe SBS platform and all configurations with a 2pVS transcoding card on theBSC are not supported in Release 18. The ENET, SPM/DTC, and ISM/MTMcomponents in the core are also not supported in Release 18. These elementswill continue to be supported on prior active releases (for example, Release17) until their end of life. Release 18 documentation continues to show theseconfigurations in order to provide a single source of documentation for a mixednetwork that is operating under Releases 17 and 18. For any questions orconcerns, please contact your sales/account manager.

FeaturesSee the following sections for information about feature changes:

Sun T5220 supportYou can use the Sun T5220 hardware platform as an alternative to theSun Netra 240 hardware platform. Procedures for the Netra 240 areunchanged when performed on the T5220. The Sun T5220 comesequipped with the Quad Gigabit Ethernet card for multi-net support.

Secure Lawful Intercept ProxyThis feature adds security functionality to the existing CDMA LI Proxyapplication. The key security enhancements to the application are:

• To protect and secure the LI CDC data records from CBM to LIdownstream servers.

• To protect and secure the LI provisioning data between Core & LIdownstream servers.


NN20000-316 05.02 28 July 2010

.

6 New in this release

In addition to the default TCP non-encrypted path, this feature supports theTLS1.0 protocol over TCP communication to provide a secure path for theCDC messages between the CBM and LI downstream servers.

A new application configuration option is introduced within the cbmmtcconfig menu level, to configure the LI proxy application with the followingnew supported configurations:

• Non-encrypted mode—The CDC records are sent to the downstreamLI servers using the non-encrypted path over TCP. This is the defaultconfiguration.

• Encrypted (TLS) mode—The CDC records are sent to the downstreamLI servers using the secure TLS path over TCP.

This feature also supports secure LI provisioning for the CDMA LIapplication on the Core from the LI downstream servers. This is performedby using the CBM passthru functionality, to connect securely to the MTXCore through the CBM.

See “Configuring CBM LI Proxy application” (page 64), and “Adding ordeleting a downstream LI server trust certificate for the CBM LI Proxyapplication” (page 68).

Other changesThere are no other changes in this software release.


NN20000-316 05.02 28 July 2010

.

7.

SPFS-based server functionsThis document contains configuration procedures for the Core and BillingManger 850 for CDMA.

ATTENTIONThe SPFS platform and OAM applications residing on SPFS are patched by theNetwork Patch Manager (NPM). For information about the NPM and how to useit, see CDMA Using the Network Patch Manager, (NN20000-367).

In addition to the configuration procedures contained in this document, seethe following procedures for CBM configuration:

• "Changing the system IP address or hostname on an SPFS server" inCDMA Core Configuration, (NN20000-709)

• "Canceling a running remote backup process" in CDMA CoreConfiguration, (NN20000-709)

• "Initiating a switch-over to the remote backup server" in CDMA CoreFault Management, (NN20000-708)

• "Performing a manual backup of the target server" in CDMA CoreConfiguration, (NN20000-709)

• "Scheduling automatic backups of the remote server, " in CDMA CoreConfiguration, (NN20000-709)

• "Viewing configuration information for remote server backups" in CDMACore Configuration, (NN20000-709)

• "Viewing logs from a remote backup" in CDMA Core Configuration,(NN20000-709)


NN20000-316 05.02 28 July 2010

.

8 SPFS-based server functions

Installing and configuring the Passport LogStreamer application

Use the following procedure to install and configure the Passport LogStreamer application.

Prerequisites• Ensure that the Multiservice Data Manager (MDM) has all required

cartridges installed.

• Ensure that the cartridge version installed on the MDM and theMDM software version are compatible. See the compatibility list athttp://www130.nortelneworks.com/cgi-bin/eserv/cs/main.jsp.

• To ensure that the Passport Log Streamer is able to communicatewith the configured MDMs and to collect logs, any restrictions for theconfigured MDM ports should be removed from all of the firewalls thatexist between the MDM and the Core and Billing Manager.

ATTENTIONDo not install this application if you are using the Customer Network Manager(CNM) or duplicate logs appear at the CNM. The CNM handles all log streamingdirectly from each PM.

ATTENTIONInstructions for entering commands in the following procedure do not show theprompting symbol, such as #, >, or $, displayed by the system through a GUIor on a command line.

Procedure steps

Step Action

1 At the Core and Billing Manager use the following table todetermine your first step.

If you are installing and configuringthe Passport Log Streamerapplication for

Then

a PT-AAL1 or UA-AAL1 office go to step 2.

any other office go to step 4.

2 Obtain the IP address for each of the two nodes that constitutethe Preside MDM.


NN20000-316 05.02 28 July 2010

.

Procedure steps 9

3

ATTENTIONThe port numbers are those the Passport Log Streamer applicationon the Core and Billing Manager will connect to.

Obtain the port number for the pserver application on each of thePreside MDM nodes.

4 Begin to install the Passport Log Streamer application: log onto the Core and Billing Manager using the maint user ID andpassword.

5 Switch user to root using the root ID and password.

6 Use the following table to determine your next step.

If the filesets are Then

on CD or DVD go to step 7 and specify:/cdrom/cdrom/applications/cbm/packages as the <source directory>

in a directory retrieve the filesets from thedirectory, and go to step 8.

7 Access the Apply level of the maintenance interface and displaythe list of filesets contained in the source location (CD ordirectory):

cbmmtc apply <x>

For more information, see “Variable definitions” (page 12).

8 Select the filesets required for the Passport Log Streamerapplication:

select <fileset_number>


9 Install the filesets:

apply

10 To configure the Passport Log Streamer application access theConfig level and display the list of applications:

config

11 Start the configuration process:

config <x>


12 When prompted, enter the IP address for the first Preside MDMnode, then the second.

Example response


NN20000-316 05.02 28 July 2010

.


Enter the IP address for the firstMDM[000.000.000.000]:47.135.209.70

Enter the IP address for thesecond MDM[000.000.000.000]:47.135.209.124

13

ATTENTIONIf MDM filters were previously defined, they will appear.

When prompted, enter the port number configured for thepserver application on the first Preside MDM node, then thesecond.

Example response

Enter the port number for the firstMDM[3197]:

Enter the port number for the secondMDM[3197]:

14 When prompted, indicate whether you want to receive MDMfilters.

Example response

No previous Preside MDM filters defined.Do you want to specify Preside MDM filters? [y/n]

If Then

y (yes) go to the next step.

n (no) go to step 16.

15 When prompted, enter the host name of the first Preside MDMnode, then the second.

Example response

Enter MDM hostname 1: PGMDM00

Enter MDM hostname 2: PGMDM01

16

ATTENTIONIf Passport 15000 filters were previously defined, they will appear.

When prompted, indicate whether you want to receive Passport15000 filters.

Example response


NN20000-316 05.02 28 July 2010

.

Procedure steps 11

No previous Passport 15000 filters defined. Do you wantto specify Passport 15000 filters [y/n]

If Then



17

ATTENTIONSpecify one filter per Passport 15000 to receive logs from.

When prompted, type the number of Passport 15000 filters youwant to specify.

Example response

How many Passport 15000 filters do you wish to specify?[4]:

18 When prompted, enter the required set of Passport 15000module names (a typical module name is often defined to bethe network element’s CLLI). You can receive logs only from themodules that are specified.

19

ATTENTIONIf Passport 8600 filters were previously defined, they will appear.

When prompted, indicate whether you want to receive Passport8600 filters.

Example response

No previous Passport 8600 filters defined.Do you want to specify Passport 8600 filters? [y/n]

If Then



20 When prompted, type the number of filters you want to specify.

21 When prompted, enter the required set of Passport 8600 modulenames (a typical module name is often defined to be the networkelement’s CLLI). You can receive logs only from the modulesthat are specified.

22 When prompted, confirm the configuration data you entered:

y

Example response


NN20000-316 05.02 28 July 2010

.


Saving new configuration data...

23

ATTENTIONIf you installed and configured the Passport Log Streamer applicationfileset, ensure the Preside MDM is installed, configured, and inservice before continuing with this procedure.

Begin to bring the Passport Log Streamer application intoservice. Access the Application (Appl) level:

appl

24 Busy the application fileset:

bsy <fileset_number>


25 Return the application fileset to service:

rts <fileset_number>


After you return the application fileset to service, the systemretrieves any current log records. For more informationabout how to view or store log records, see the procedure"Displaying or storing log records using log receiver" in the FaultManagement document.

ATTENTIONIf the application fileset has been out of service for an extendedperiod of time, the system retrieves any older log records that areavailable prior to any current log records. However, for Passport LogStreamer application, once it returns to service, the system retrievesonly the current log records.

--End--

Variable definitionsUse the information in the following table to complete the commands inthis procedure.

Variable Value

<x> The path of the source directory.

fileset_number in step 8 The number of the fileset next toPassport Log Streamer application.


NN20000-316 05.02 28 July 2010

.

Variable definitions 13

Variable Value

<x> in step 11 The number of the fileset next to thePassport Log Streamer application.

fileset_number in step 24 and 25 The number next to Passport LogStreamer application.


NN20000-316 05.02 28 July 2010

.


Enabling or disabling the tuple numberconfiguration for the OMDD application

Use this procedure to enable or disable the tuple number configuration tobe provided with the OM groups, using the OMDD application.

Prerequisites• You have root user or emsadm user permission.

For information about how to log on to the CBM as an authorizeduser or how to display information about a user or role group, seeCore and Billing Manager 850 Security and Administration for CDMA,(NN20000-320).

• You back up the file /cbmdata/configdata/00/omdd/odsl.config_filebefore changing the configuration.

Procedure steps

Step Action

1 Log on to the CBM.

2 From the command line prompt, access the configuration level ofthe cbm maintenance interface:

cbmmtc config

3 Select the OMDD application for configuration.

select <n>

config <n>


4 Enter Y to provide the tuple number with the OM groupinformation.

5 Enter Y to provide the time zone with the OM filenames.

6

ATTENTIONTo determine whether the Multiservice Data Manager (MDM) andSuccession Network Manager (SNM) are integrated, refer to thebacked up odsl.config_file. If the MDM and SNM are integrated,then refer to the same file for the MDM IP addresses, port numbersand custom connection settings to configure the application as perthe previous configuration.


NN20000-316 05.02 28 July 2010

.


If Then

MDM and SNM were integratedin the previous configuration

enter Y and perform step 7 tostep 19 of the “Configuring thePassport OMs using OMDDapplication” (page 16).

If the MDM and SNM are notintegrated

enter N .

7 Press Enter to return to the configuration level in CBMmaintenance interface.

The OMDD application configuration is complete.

8 Busy the OM Delivery application:

bsy <n>


9 Return the application to service:

rts <n>


--End--


Variable Value

<n> The number corresponds to the OMDelivery or its menu item.


NN20000-316 05.02 28 July 2010

.


Configuring the Passport OMs using OMDDapplication

Use this procedure to configure Passport OMs using the OMDDapplication.

Prerequisites• You have root user or emsadm user permission.


Procedure steps

Step Action


2 From the command line prompt, access the configuration level ofthe CBM maintenance interface:

cbmmtc config

3 Select the OMDD application for configuration:

select <n>

config <n>

4 Press Enter to select the default option to provide the tuplenumber with the OM Group.

5 Press Enter to select the default option to provide the Timezonewith the OM Filenames.

6 Enter Y to indicate that the Multiservice Data Manager (MDM)and Succession Network Manager (SNM) are integrated.

7 Enter the IP address of the first MDM.

Example

47.135.43.76

8 Enter the hostname of the first MDM.

Example input

ucars0353c

9 Enter the IP address of the second MDM.

Example input


NN20000-316 05.02 28 July 2010

.

Procedure steps 17

47.135.43.77

10 Enter the host name of the second MDM.

Example input

ucars0363c

11 Enter the desired port for 5-minute PM data or press the returnkey to select the default port 1646.

12 Enter the desired port for 30-minute PM data or press the returnkey to select the default port 1647.

13 Enter Y to use the custom connection retry settings.

If you are not using the custom connection retry settings then goto step 19.

14 Enter the interval for retry for the first connection.

Example input

5

15 Enter the number of retry attempts to be made in the interval.

Example input

2

16 Enter the interval for retry for the second connection.

Example input

5

17 Enter the number of retry attempts to be made in the interval.

Example input

2

18 Enter the interval for retry for the third connection.

Example input

5

19 Enter Y to confirm that the MDM and SNM data that is enteredis correct.

20 Press Enter to return to the configuration level in CBMmaintenance interface.

OMDD application configuration is complete.

21 Busy the OM Delivery application:

bsy <n>


22 Return the application to service:

rts <n>


NN20000-316 05.02 28 July 2010

.



--End--


Variable Value

<n> The number next to the OM Deliveryor its menu item.


NN20000-316 05.02 28 July 2010

.

Procedure steps 19

Configuring log delivery destinations

Use this procedure to add an output log device. An output log device is adestination to which your system forwards user-defined streams of logs.

Prerequisites• All users are authorized to perform this procedure.

• For information about how to log in to the CBM as an authorizeduser or how to display information about a user or role group, seeCore and Billing Manager 850 Security and Administration for CDMA,(NN20000-320).

Procedure stepsATTENTIONInstructions for entering commands in the following procedure do not show theprompting symbol, such as #, >, or $, displayed by the system through a GUIor on a command line.

Step Action

1 Log on to the Core and Billing manager.

2 Access the logroute tool:

logroute

The Logroute Main Menu screen appears.

3 Display the device list by entering the number next to DeviceList.

The Device List Menu screen appears.

4 If you want to view the devices currently configured, enterthe number next to View Device and press Enter. Follow theon-screen instructions to display the details for the selecteddevice.

5 Add a new log device by entering the number next to AddDevice.

The Add Device screen appears.

If Then

you want to add a TCP device go to step 6.

you want to add a TCP-IN device go to step 9.

you want to add a file device go to step 12.


NN20000-316 05.02 28 July 2010

.


6 Add a TCP device by entering the number next to Add TCPDevice.

7 Enter a host IP address.

8 When prompted, enter a port number from the range displayed.

Continue with step 14.

9 Add a TCP-IN device by entering the number next to Add TCPINDevice.

10 Enter an authorized remote IP address. Enter a if you want toleave the default value of any.

11 When prompted, enter a CBM 850 Core Manager port number.


12 Add a file device by entering the number next to Add File Device.

13 Enter the name of the file where you want to store the logs.

14 When prompted, enter the log format (STD, STD_OLD, SCC2, orSCC2_OLD).

Enter STD or SCC2 if you want the following informationto appear in all log reports (otherwise, enter STD_OLD orSCC2_OLD):

• user-defined office ID, same for all logs and streams

• the name of the node (ECORE) from which the log isgenerated

• the sequence number in dual (global and device) format

The default format is STD.

15 When prompted, set the ECORE option to ON or OFF.

Enter ON, if you want the log-generating node name to appear inall reports (the format must be STD or SCC2). Otherwise, enterOFF.

You are now prompted to define a log routing entry for the devicethat you are adding. Use the following table to determine yournext step.

If Then

you want to suppress logs (cause them not tobe routed to this device)

enter d, and pressEnter.

you want to unsuppress logs (cause them to berouted to this device)

enter a, and pressEnter.

The rules you enter here only accommodate the set of logsdefined in “Specifying the logs delivered from the CM to the Coreand Billing Manager” (page 48). Logs suppressed at the CMcannot be unsuppressed for a specific device.


NN20000-316 05.02 28 July 2010

.

Procedure steps 21

Example response

Enter log identifier ("log_type", or "log_typelog_number") ==>

16 Enter a log type, or a combination of log type and log number(separated by a space). The new entry is added to the logrouting list on the screen.

An example of a log type is "PM". This entry suppresses orun-suppresses all PM logs.

An example of a combined log type and log number is PM 181.This entry suppresses or un-suppresses the PM181 logs butleaves the routing of other PM logs unchanged.

You can also enter all, which suppresses or un-suppresses alllogs routed to this device.

Example response

Wish to enter more Logrouting Details? (Y/N)[N]:

If you Then

want to add more routing entries

The maximum number of log routing entries is1024. If you have 1024 entries, and you want toadd another one, you must replace one of theexisting entries with the new entry.

enter y, andreturn to step15.

do not want to add more routing entries enter n, and goto step 17.

17 You are prompted to save the device details. Save the newdevice:

y

The new device is added to the system.

Example response

Save data completed -- press return to continue

Press Enter to return to the Add Device screen.

If you enter n, the system returns to the Device List Menuscreen. No new device is added to the system.

If Then

you want to add more devices go to step 5.

you do not want to add more devices go to step 18.


NN20000-316 05.02 28 July 2010

.


18 Return to the Device List Menu screen by entering the numbernext to Return to Main Menu.

19 Return to the Logroute Main Menu screen by entering thenumber next to Return to Main Menu.

20 Quit the logroute tool by entering the number next to QuitLogroute.

--End--

Job aidThe following information lists the aids related to performing thisprocedure:

You can add any of the following log devices using the Log DeliveryApplication Commissioning Tool (logroute):

• a TCP device (a host IP and port on the network)

You can configure up to 30 Log Delivery output devices. If you want to:

• change any aspect of an existing device, including log routing entries,refer to “Modifying a log device using logroute” (page 23).

• delete an existing device, refer to “Deleting a device using logroute”(page 28).

• modify global parameters (parameters that apply to all devices), referto “Configuring log delivery global parameters” (page 52).


NN20000-316 05.02 28 July 2010

.

Procedure steps 23

Modifying a log device using logroute

Use this procedure to change any parameter of an existing log device,including the routing entries that suppress or unsuppress logs delivered tothat device.

The routing rules you enter for each device only accommodate the set oflogs defined in “Specifying the logs delivered from the CM to the Core andBilling Manager” (page 48). Logs that are suppressed at the core cannotbe unsuppressed for a specific device.

If you want to modify global parameters (parameters that apply to alldevices), see “Configuring log delivery global parameters” (page 52).



Step Action

1 At your workstation or the remote server console log on to theCore and Billing Manager.


logroute


3 Display the device list:

1


4 Access the Modify Device Menu screen:

4

The system displays all currently configured devices.


NN20000-316 05.02 28 July 2010

.


Example response

5 Enter the number for the device that you want to modify.

The screen for the selected device appears.

Example response

6 Enter the number for the parameter that you want to modify.

If Then

the parameter that you selected is REMOTE IP,HOST IP, PORT, or FILENAME

go to step 7.

the parameter that you selected is FORMAT go to step 8.

the parameter that you selected is ECORE go to step 9.

the parameter that you selected is Log Routing go to step 10.


NN20000-316 05.02 28 July 2010

.

Procedure steps 25

7 At the prompt, enter a new value for the selected parameter. Goto step 16.

8 At the prompt, enter the new log format (from the rangedisplayed).

Enter STD or SCC2 if you want the following information toappear in all log reports:

• user-defined office ID, same for all logs and streams

• the name of the node (ECORE) from which the log isgenerated

• the sequence number in dual (global and device) formatContinue with step 16.

9 At the prompt, change the setting for the ECORE option (ON orOFF).

If you enter ON, the name of the node from where you generatethe log appears in all log reports (for STD and SCC2 formatsonly).


10 The system displays all existing logrouting entries for theselected device, and prompts you to add or delete an entry.Complete the following steps to add or delete a routing entry.

If Then

you want to add an entry enter a, and go to step 11.

you want to delete anentry

enter d, and go to step 14.

11 At the prompt, enter one of the following values:

• aif you want to unsuppress logs (cause them to be routed tothe device)

• dif you want to suppress logs (cause them not to be routed tothe device)

Example response


12 Enter a log type or a combination of log type and log number(separated by a space). The new entry is added to the logrouting list on the screen. For example, an entry of:


NN20000-316 05.02 28 July 2010

.


• PM suppresses or un-suppresses all PM logs.

• PM 100 suppresses or un-suppresses the PM100 logs, butleaves the routing of other PM logs unchanged.

Example response

Wish to enter more Logrouting Details (Y/N) [N]:

13 If you want to suppress or unsuppress more logs, enter y, and goback to step 11. Otherwise, enter n, and continue with step 16.

14 Enter the number of the entry that you want to delete from thelog routing list. The entry you specified is removed from thedisplay.

Example response

Wish to delete more Logrouting Details (Y/N) [N]:

15 If you want to delete more entries, enter y, and repeat step 14.

If you do not want to delete any more entries, enter n, andcontinue with step 16.

16 When prompted, save your changes:

y

Example response

WARNING: Some log devices will be restarted. Do youwish to proceed?

17 Confirm the save command:

y

Example response


Press Enter to confirm the change.

If you do not want to save your change, enter n and press Enter.

If Then

you want to make more changes for theselected device

go to step 6.

you do not want to make more changes for theselected device

go to step 18.

18 Type abort and press Enter. The system returns to the ModifyDevice Menu screen.

19 If you want to modify another device, go back to step 5.Otherwise, continue with step 20.


NN20000-316 05.02 28 July 2010

.

Procedure steps 27

20 Exit the Modify Device Menu screen:

abort

21 Return to the Logroute Main Menu screen:

6

22 Quit the logroute tool:

6

--End--


NN20000-316 05.02 28 July 2010

.


Deleting a device using logroute

Use this procedure to delete a log device using the Log DeliveryApplication Commissioning Tool (logroute). This procedure allows you todelete any one of the following devices:

• a TCP device (an IP and port address on the network)

• a TCP-IN device (a port on the Core and Billing Manager)

• a file device (a file on the Core and Billing Manager)



Step Action

1 Log on to the Core and Billing Manager.


logroute


3 Display the device list:

1


If you want to view the devices currently configured, enter 1.Follow the on-screen instructions to display the details for theselected device.

4 Access the Delete Device Menu screen:

3

The system displays the list of configured devices and promptsyou to enter the number of the device that you want to delete.


NN20000-316 05.02 28 July 2010

.

Procedure steps 29

Example response

5 Enter the number of the device you want to delete.

Example response

Device will be deleted permanently. Continue...(Y/N)[N]:

6 Confirm that you want to delete the selected device:

y

Example response


If you do not want to delete the selected device, enter n, pressEnterand select a new device to delete.

7 Press Enter to confirm that you want to continue.

The device is removed from the list and you are prompted toenter the next device you want to delete.


If Then

you want to delete another device go to step 5.

you do not want to delete another device go to step 9.

9 Return to the Device List Menu screen:

abort


6



NN20000-316 05.02 28 July 2010

.


6

--End--


NN20000-316 05.02 28 July 2010

.

Procedure steps 31

Configuring log delivery for MDM/PPEM securityand audit logs (MDM 601 and PPEM 601)

Use this procedure to set up a log device that contains only the securityand audit logs that are sent to the Core and Billing Manager’s syslogsystem.



• The Multiservice Switch Log Streamer application should be configuredon the Core and Billing Manager to retrieve logs from the MDM.


Step Action



logroute


3 Enter the number next to Device List to display the device list.


4 Enter the number next to Add Device to add a new log device.

The Add Device screen appears.


If Then

you want to add a TCP device go to step 6.

you want to add a TCP-IN device go to step 18.

you want to add a file device go to step 30.


NN20000-316 05.02 28 July 2010

.


6 Enter the number next to Add TCP Device to add a TCP device.

7 Enter a host IP address.

8 Enter a port number from the range displayed.

9 Enter the log format (STD, STD_OLD, SCC2, or SCC2_OLD).

10 Enter ON or OFF to set the ECORE option to ON or OFF.

11 Enter "a" to add report.

12 Enter the log identifier as "MDM 601"

13 Enter "Y" to add more logrouting details.


15 Enter the log identifier as "PPEM 601".

16 Enter "N" to indicate you do not want to add more logroutingdetails.

17 Enter "Y" to save device details.

The message, "Save data completed -- press return to continue"appears.



If Then



18 Enter the number next to Add TCPIN Device to add a TCP_INdevice.

19 Enter a remote IP address or "a" for any IP address.

20 Enter a port number from the range displayed.




24 Enter log identifier as "MDM 601".



27 Enter log identifier as "PPEM 601".




NN20000-316 05.02 28 July 2010

.

Procedure steps 33




If Then



30 Enter the number next to Add File Device to add a file device.

31 Enter the file name with the full path, where you want to storethe logs.




35 Enter log identifier as "MDM 601".



38 Enter log identifier as "PPEM 601".






If Then



41 Return to the Device List Menu screen by entering the numbernext to Return to Main Menu.

42 Return to the Logroute Main Menu screen by entering thenumber next to Return to Main Menu.


NN20000-316 05.02 28 July 2010

.


43 Quit the logroute tool by entering the number next to QuitLogroute.

--End--


NN20000-316 05.02 28 July 2010

.

Procedure steps 35

Excluding MDM/PPEM audit and security logs fromother log devices

Use this procedure to exclude MDM/PPEM audit and security logs fromother log devices.


For information about how to log in to the CBM as an authorized useror how to display information about a user or role group, see Coreand Billing Manager 850 Security and Administration for GSM/UMTS,(NN20000-321).


• Configure the Multiservice Switch Log Streamer application on theCore and Billing Manager to retrieve logs from the Multiservice DataManager (MDM), see “Configuring log delivery for MDM/PPEM securityand audit logs (MDM 601 and PPEM 601)” (page 31).


Step Action



logroute


3 Enter "1" to display the device list.


4 Enter "1" to view the configured devices.

The Device List screen appears.


NN20000-316 05.02 28 July 2010

.


This example screen, and other example screens shown in thisprocedure, show log removal only for a TCP device. Theseexamples show the type of screen that appears in response tothe steps you perform in this procedure. Thus, the content ofthe screen that actually appears when you are performing thisprocedure varies according to device type and the configurationof your system.

Example response

5 Enter the number for the device you want to review. Forexample, in the example screen shown in step 4, enter "1" todisplay the details for the device shown.

Example response

6 In the device detail screen that appears, verify that logs "MDM601" and "PPEM 601" are shown configured for the device. Alsoverify whether the device is configured for ALL logs.


NN20000-316 05.02 28 July 2010

.

Procedure steps 37

If Then

the device is configured for ALL logs go to step 23.

the device is configured for "MDM 601" and"PEM 601" logs

go to step 7.

7 Press Enter to return to the Device List Screen and when theDevice List Screen displays, press Enter again to return to theDevice List Menu.


8 Enter "4" to modify a device.


9 Enter the number for the device you want to modify. Forexample, in the example screen shown in step 8, enter "1" todisplay the device shown.

Example response

10 Enter "5" to change the Log Routing device parameter.


NN20000-316 05.02 28 July 2010

.


Example response

11 Enter "d" to delete a report.

Example response

12 Enter the log routing number for MDM 601. For example, in theLogrouting of TCP Device screen shown in step 11, enter "1".

Example response


NN20000-316 05.02 28 July 2010

.

Procedure steps 39

13 Enter "Y" to indicate that you want to delete another Logroutingdetail.

Example response

14 Enter the log routing number for PPEM 601. For example, in theLogrouting of TCP Device screen shown in step 13, enter "1".

Example response


NN20000-316 05.02 28 July 2010

.


15 Enter "N" to indicate that you do not want to delete moreLogrouting details.

16 Enter "Y" to save the Logrouting details changes you have made.

Example response

17 Enter "Y" to confirm that you wish to proceed with saving theLogrouting details changes.

Example response

18 Press Enter to continue.


NN20000-316 05.02 28 July 2010

.

Procedure steps 41

Example response

19 Enter "abort" to return to the Modify Device Menu.

Example response

20 Enter "abort" to return to the Device List Menu.


21 Enter "6" to return to the Logroute main menu screen.



If Then

you want to exclude MDM/PPEMaudit and security logs fromanother device

go to step 3.

you do not want to excludeMDM/PPEM audit and securitylogs from another device

go to step 40.


NN20000-316 05.02 28 July 2010

.


23 Press Enter to return to the Device List Screen and when theDevice List Screen appears, press Enter again to return to theDevice List Menu.


24 Enter "4" to modify a device.


25 Enter the number for the device you want to modify. Forexample, in the example screen shown in step 24, enter "1" todisplay the device shown.

Example response

26 Enter "5" to change the Log Routing device parameter.


NN20000-316 05.02 28 July 2010

.

Procedure steps 43

Example response


Example response

28 Enter "d" to delete report.

Example response


NN20000-316 05.02 28 July 2010

.


29 Enter the log identifier, "MDM 601".

Example response

30 Enter "Y".

Example response

31 Enter "d" to delete report.


NN20000-316 05.02 28 July 2010

.

Procedure steps 45

Example response

32 Enter the log identifier, "PPEM 601".

Example response

33 Enter "N" to indicate that you do not want to enter moreLogrouting details.

34 Enter "Y" to save the Logrouting details changes you have made.

Example response


NN20000-316 05.02 28 July 2010

.


35 Enter "Y" to confirm that you wish to proceed with saving theLogrouting details changes.

Example response


Example response


NN20000-316 05.02 28 July 2010

.

Procedure steps 47

37 Enter "abort" to return to the Modify Device Menu.

Example response

38 Enter "abort" to return to the Device List Menu.


39 Enter "6" to return to the Logroute main menu screen.


40 Enter "6" to exit from the Logroute tool.

--End--


NN20000-316 05.02 28 July 2010

.


Specifying the logs delivered from the CM to theCore and Billing Manager

Use this procedure to specify the logs the computing module (CM) deliversto the Core and Billing Manager. When first installed, the Log Deliveryservice receives all logs in the CM log stream by default. To modify theincoming CM log stream, use the CM Configuration File menu in thelogroute tool to add or delete individual logs or log types.


• For information about how to log in to the CBM as an authorizeduser or how to display information about a user or role group,see Core and Billing Manager 850 Security and Administration forCDMA(NN20000-320).


Step Action



logroute


3 Access the CM Configuration File menu:

3

The CM Config File Menu screen appears.

If Then

you want to add routing report to the list go to step 4.

you want to delete routing report fromthe list

go to step 7.

4 Access the CM - Add Report screen:

2


NN20000-316 05.02 28 July 2010

.

Procedure steps 49

The system displays the list of the current routing entries for theincoming CM log stream.

Example response

If Then

you want to suppress logs (causethem to be removed from theincoming CM log stream)

enter d, and press Enter.

you want to unsuppress logs(cause them to be included in theincoming CM log stream)

enter a, and press Enter.

An entry of n (NOCMLOGS) suppresses all CM logs -- no CMlogs are delivered to your system.

Example response


5 Enter a log type or a combination of log type and log number(separated by a space).

An example of a log type is "PM". This entry suppresses orun-suppresses all PM logs.

An example of a combined log type and log number is PM 181.This entry suppresses or un-suppresses the PM181 logs butleaves the routing of other PM logs unchanged.

Example response

Save Report details? (Y/N)[N]:

6 Save your changes:

y


NN20000-316 05.02 28 July 2010

.


The new item is added to the list.

If Then

you want to add more entries tothe list

go to step 4.

you do not want to add moreentries to the list

go to step 10.

7 Access the CM - Delete Report screen:

3

The system displays the list of the current routing entries for theincoming CM log stream.

Example response

8 Enter the number of the item you want to delete from the list.

Example response

Report will be deleted permanently. Continue?(Y/N)[N]:

9 Confirm the delete command:

y

The system displays the CM Delete Report screen with thefollowing warning

Example response

Warning: You must BSY and RTS the Log Deliveryapplication for the CM configuration to take effect.


NN20000-316 05.02 28 July 2010

.

Procedure steps 51

If Then

you want to delete more entriesfrom the list

go to step 8.

you do not want to delete moreentries from the list

go to step 10.

10 Return to the CM Config File Menu screen:

abort

If Then

you want to make more changesto the CM log stream list

go to step 4.

you do not want to make morechanges to the CM log stream list

go to step 11.


5


6

--End--


NN20000-316 05.02 28 July 2010

.


Configuring log delivery global parameters

Use this procedure to configure the Log Delivery global parameters. Theglobal parameters are set to default values at initial installation and shouldnot require modification.

The online Log Delivery commissioning tool called logroute controls LogDelivery global parameters. The Log Delivery global parameters applyto all Log Delivery output devices and are separate from device-specificparameters.

For information about how to configure or modify device-specificparameters, refer to one of the following procedures:

• “Configuring log delivery destinations” (page 19)

• “Modifying a log device using logroute” (page 23)


• For information about how to log in to the CBM as an authorizeduser or how to display information about a user or role group,see Core and Billing Manager 850 Security and Administration forCDMA(NN20000-320).


Step Action



logroute


3 Access the Global Parameters screen:

2

4 Select the parameter that you want to change:


NN20000-316 05.02 28 July 2010

.

Procedure steps 53

<n>

You must enter the log and line delimiters (incoming andoutgoing end of line characters, and start and end of logcharacters) as decimal or hexadecimal ASCII code.

5 Enter a new value for the selected parameter.

6 The system prompts you to save the change. The followingmessage appears:

Example response

Save Global Parameter details [Y/N][N]:

If Then

you want to save your change enter y, press Enter and go tostep 7.

you do not want to save yourchange

enter n, press Enter and go tostep 11.

7 The system displays the following warning:

Example response

WARNING: All log devices will be restarted. Do youwish to proceed.

If Then

you want to complete the savingprocess

go to step 9.

you want to stop the saving process go to step 8.

8 Enter n.

The unchanged value appears on the Global Parameter screen.


9 Enter y.

The system displays the following message:

Example response


10 Press Enter to confirm the change. The new value appears onthe Global Parameter screen.

If Then

you want to change anotherglobal parameter

go to step 4.

you do not want to changeanother global parameter

go to step 11.


NN20000-316 05.02 28 July 2010

.


11 Return to the Logroute Main Menu:

13


6

--End--

Variable definitionsUse the information in the following table to determine the value for thevariables used in this procedure.

Variable Value

<n> The menu number next to the global parameteryou want to change.

Job aidThe following information lists the aids related to performing thisprocedure:

The logroute tool allows you to customize the following global parameters:

• log_office_id (office name)

This parameter is valid only for devices that have log format set to STDor SCC2.

• buffer size (number of logs)

• reconnect time-out value (seconds)

• lost logs threshold (number of lost logs before the system generates adesign log)

This parameter is for Ericsson personnel only.

• incoming end of line character (ASCII code)

• outgoing end of line characters (ASCII code)

• start of log characters (ASCII code)

• end of logs characters (ASCII code)

• the number of days to keep log files

• maximum size of a log file (Mbyte)

• maximum size action


NN20000-316 05.02 28 July 2010

.

Job aid 55

ATTENTIONAny settings changed by the Log Delivery application and the logroute toolwill not affect Generic Data Delivery settings or the logs in the /gdd volume.

If the global parameters do require modification, the ranges and defaultfor each parameter are as follows:

• log_office_id: values are NULL, CLLI, CORE-COMPAT, or up to12-characters office name, default is CLLI

The log_office_id parameter refers to the office name, which will beattached to all logs delivered to all devices that have log format set toSTD or SCC2. If you enter

— NULL, the office name will not be attached to the logs.

— CLLI, the CLLI name of your system will be attached to all logs.

— CORE-COMPAT, the core’s LOG_OFFICE_ID defined in tableOFCVAR will be used for all logs. Until the first log arrives from thecore, the system CLLI is used.

• buffer size (number of logs): range is 50 to 300, default is 150

• reconnect time-out value (secs): range is 1 to 3600, default is 15

• lost logs threshold: range is 1 to 300, default is 100 (-1 turns thisoption off)

• number of days to keep log files: range is 1 to 45, default is 5

• maximum size of a log file (Mbytes): range is 5 to 300, default is 40

• maximum size action: values are STOPDEV, CIRCULATE, andROTATE

The maximum size action parameter allows you to configure the actionthe system performs when the file reaches its maximum size. TheSTOPDEV value tells the file device to save the data in separate filesevery 12 hours. When the file created at each 12-hour rotation is full,the system stops writing log data to the file. The system loses any logdata generated from the time the system stops writing to the file to thestart of a new file at the next rotation.

The ROTATE value tells the file device to save the data in separatefiles every 12 hours. When the file created at each 12-hour rotation isfull, the system creates another file to continue saving any log data.The system does not wait until the next 12-hour rotation to create anew file.

The CIRCULATE value tells the file device to save the data in separatefiles every 12 hours. When the file reaches its maximum size, thesystem saves the new log data by overwriting the earliest data in thefile.


NN20000-316 05.02 28 July 2010

.


The remaining global parameters are represented by ASCII charactercodes. For more information on these parameters including their ranges,see the logroute help menu. The values for the global parametersrepresented by ASCII character codes are as follows:

• incoming end of line character: default is 10 which corresponds to aline feed character (go to the next line)

• outgoing end of line characters: default is 10 13 which represents aline feed (go to the next line) followed by a carriage return

• start of log characters: default is 10 13 which represents a line feed (goto the next line) followed by a carriage return

• end of logs characters: default is 10 13 which represents a line feed(go to the next line) followed by a carriage return

Any configuration changes take effect immediately. You do not have tobusy and return the Log Delivery application to service for the changesto take effect.


NN20000-316 05.02 28 July 2010

.

Procedure steps 57

Configuring the GDD parameter using logroute

Use this procedure to configure the Generic Data Delivery (GDD)parameter. This parameter defines how many days the log files will bestored in the /gdd directory on the datavg volume.

For the Core and Billing Manager, you will need to resize the GDD volume(/cbmdata/00/gdd) based on the following engineering rules:

• for an End-Office: 220 MBytes/day * #RetentionDay.

• for a Tandem PT-IP Office: 100 Mbytes/day * #RetentionDay.

• for the installations previously specified you will also need to resizethe data volume (/cbmdata/00) using these rules if a file device isconfigured to capture all the logs and the global parameter "MaximumSize action" has been set to ROTATE.

When the configured number of days is reached (maximum 30 days), thelogs are rotated, and the oldest log file is replaced by the newest.



Step Action



logroute


3 Access the GDD Menu:

4

4 Select the GDD parameter:

1


NN20000-316 05.02 28 July 2010

.


Example response

Enter number of days (range 1 to 30) ==>

5 Specify how many days you want the log files to be stored in the/gdd directory. Enter the number (within the range) and pressEnter.

Example response

Save GDD Value [Y/N][N] :

If Then

you want to save your change got to step 7.

you do not want to save your change go to step 6.

6 Cancel your change:

n

If Then

you want to make another change got to step 4.

you do not want to make anotherchange

go to step 10.

7 Save the GDD value:

y

Example response

Warning: This would change the number of days tostore logs in /gdd. Log files older than the dayspecified would be deleted.

8 Press Enter to confirm the change.

Example response



The new value appears.


3


6

--End--


NN20000-316 05.02 28 July 2010

.

Procedure steps 59

Configuring outbound connection security forOMDD

Secure outbound file transfer of OMs is provided through the OpenSSHSFTP (secure file transfer protocol) client. The SFTP client protects alldata, including sensitive users’ passwords, by encrypting the data beforeit leaves the core manager and decrypting the data after it arrives at thedownstream OSS destination. The SFTP client also provides data integritychecking to ensure that the data has not been tampered with during thetransfer.

Both password-based authentication and key-based (public key)authentication are supported for secure outbound file transfers using theOpenSSH SFTP.

Prerequisites• An SSH sftp server (SFTP server subsystem) that is compatible

with the OpenSSH sftp client must be running on the downstreamOperations Support System (OSS) in order for the OMDD to transferdata with the OpenSSH sftp client.

• For the CBM, this secure outbound transfer capability depends on theOpenSSH packages as well as NTutil.

• The initial host key acceptance of the downstream processor should beperformed manually in order for the SFTPW to be used for file transferfrom the core manager. The .ssh/known_hosts file in the maint homedirectory is edited by SSH software to include the host key. After thisis completed, sftp can be used to send files to the downstream OSS.This step must be performed for each downstream destination prior toschedule tuple configuration for SFTPW.

• You have the root user ID and password.



NN20000-316 05.02 28 July 2010

.


ATTENTIONTo configure secure data transfer to a downstream OSS destination, itis necessary to first accept the known host key for the downstream OSSdestination. This procedure enables you to perform this task. This task must beperformed whenever the destination downstream OSS is rebooted or wheneverthe SFTPD server on the OSS is restarted.

Step Action

1 Establish a Telnet connection to the core manager by completingthe following substeps.

2 Open a terminal window that is VT100 compatible.

3 Log onto the core manager from the terminal window prompt:

telnet <ip_address>

4 When prompted, enter your user ID and password.

5 Change to the root user. Type

su - root

and press Enter.

6 When prompted, enter the root password.

7 Change directory to the maint home directory:

cd ~maint

8 Look in the maint directory for the ".ssh" directory:

ls -lad .ssh

If Then

the .ssh file does not exist go to step 9.

the .ssh file does exist go to step 17.

9 Create the .ssh directory:

mkdir .ssh

10 Change the .ssh directory ownership:

chown maint:maint .ssh

11 Change the permissions associated with the .ssh directory:

chmod u+rwx .ssh

12 Change to the maint user:

su maint

13 Run the SSH client to the downstream OSS destination byproviding a "maint" user name and IP address for the SSH client,by performing the following steps:


NN20000-316 05.02 28 July 2010

.

Job aid 61

14 Type

ssh -l maint <nn.nn.nn.nn>

Example responseThe authenticity of host Ô10.10.10.10’ can’t beestablished.

RSA key fingerprint is 3a:d5:d7:6e:ee:6b:45:fc:b9:0b:92:a7:1c:d8:f1:be.

Are you sure you want to continue connecting (yes/no)?

15 Type

yes

Example response

Warning: Permanently added Ô10.10.10.10’ (RSA) tothe list of known hosts.

16 Press Ctrl + C to terminate the program.

17 Exit the Telnet session:

exit

ATTENTIONFor more information about how to configure an outbound file transferschedule, see "Configuring the outbound file transfer schedule" inCore and Billing Manager 850 Performance Management for CDMA,(NN20000-324).

--End--


Variable Value

<ip_address> The IP address of the Core Manager.

<nn.nn.nn.nn> The IP address of the SSH client.

Job aidUse the information in the following sections that aids you in performingthis procedure:


NN20000-316 05.02 28 July 2010

.


Limitations and restrictionsUse the following limitations and restrictions that apply to the secureoutbound file transfer capability:

• Secure outbound file transfer (SFTPW) cannot re-send ClosedSentfiles when ClosedSent files already exist on the target directory in thedownstream system. Therefore, it is important that existing ClosedSent(or processed) files at the downstream system be either moved toanother directory or renamed before an attempt is made to re-sendClosedSent files from the core manager to the downstream system.

• Automatic dumping of the public key file on the remote system is notsupported. Users have to manually dump the contents of the publickey file into the user’s authorization file on the remote system.

If the remote system is running OpenSSH server, the public key shouldbe appended to .ssh/authorized_keys or .ssh/authorized_keys2 file.

• The user SHELL (cshrc or bash) startup script at the downstreamsystem must not contain ANY echo or print statements which willinterfere the handshaking between sftp client and sftp-server. Thesymptom is that the sftp session terminated prematurely and themessage "Received message too long <a long num> is printed".

• The data transfers of AFT, RTB and sendtape applications are notsecured.

TroubleshootingPossible error scenarios that may occur when you are performing thisprocedure and the steps to perform in addressing these problems arelisted in the following:

• Connection refused

This error causes a "Down" status for the SSH Collector Statusparameter.

Example

Error : ssh; connect to host <hostname/hostip> port 22:Connection refusedConnection closed.

To resolve this problem:

— Verify that the host machine is on the network.

— Verify that the SSH server on the host machine is running andthat the configuration is correct (such as, the port number andfingerprint).

• known_hosts file cannot be datafilled


NN20000-316 05.02 28 July 2010

.

Job aid 63

This error is caused by the nonexistence of, or incorrect permissionsfor, the /cbmdata/users/maint/.ssh directory in a CBM 850 machine.


— Verify that you are logged in as the root user and that you switcheduser (su) to the maint user.

— Verify that the directory /cbmdata/users/maint/.ssh is present on theCBM 850 Core Manager and has read/write permissions set for themaint user. If the directory doesn’t exist, create it.

— Verify that the correct IP address is used for host key acceptance.

• SSH server’s host key has changed

If the server’s host key has changed, the client will notify you that theconnection cannot proceed until the server’s host key is deleted fromthe known_hosts file using a text editor. Before performing this task,you must contact the system administrator of the SSH server to ensurethat the server operation will not be compromised.


— Try to create an ssh connection to a different machine. If youreceive an error message about a changed or incorrect public key,it is probably due to the host changing its public key. Edit the file/home/maint/.ssh/known_hosts using a text editor and delete anyline containing the name of that host.

— Try to create an ssh connection to that host again and then accepta new public key for the host.

• SSH warns about "man-in-the-middle attack"

This problem is caused either by someone eavesdropping on yourconnection or by the host key having been changed.


— Contact your system administrator to determine whether the hostkey has been changed or whether the ip address of the client hasbeen changed.

— Edit the file /home/maint/.ssh/known_hosts using a text editor anddelete any line containing the name of that host.

— Datafill the known_host keys with new information.

• sftp session terminated prematurely with the message "Receivedmessage too long <a long num>"

Ensure that the user SHELL (cshrc or bash) startup script at thedownstream system does not contain any echo or print statementswhich will interfere the handshaking between sftp client and sftp-server.


NN20000-316 05.02 28 July 2010

.


Configuring CBM LI Proxy application

Use this procedure to change the configuration mode for the CBM LI Proxyapplication.

ATTENTIONThe CBM LI Proxy application supports self signed trusted server certificatesonly for the “Encrypted (TLS) mode”. The self signed server certificates must begenerated by the LI servers without the use of passphrase. All current servercertificates must be stored manually on the application specific certificatedirectory (/cbmdata/configdata/00/clp/trustcerts) within CBM before the“Encrypted (TLS) mode” is selected

Prerequisites• Confirm the protocol (TCP or TLS over TCP) a customer plans to use

to deliver LI CDC data from CBM to downstream LI servers in thecustomer’s network.

• Verify all downstream LI servers in the customer’s network are set upto use the selected protocol (TCP or TLS over TCP).

For more information about how to add or delete a downstream LIserver trust certificate, see “Adding or deleting a downstream LI servertrust certificate for the CBM LI Proxy application” (page 68).

• Determine the configuration mode for the CBM LI Proxy application.

— If the TCP protocol is selected the default “Non-encrypted” modeis used

— If TLS over TCP protocol is selected the “Encrypted (TLS)” modeis used.

• You are a user in a role group authorized to perform config-adminactions.

• You obtain nonrestricted shell access. For more information onhow to log in to the CBM as an authorized user, how to request anonrestricted shell access, or how to display actions a role group isauthorized to perform, see Core and Billing Manager 850 Security andAdministration for CDMA, (NN20000-320).

Procedure steps

Step Action

1 At any workstation or console, log on to the CBM.


NN20000-316 05.02 28 July 2010

.

Procedure steps 65

2 From the command line prompt, access the config level of theCBM maintenance interface:cbmmtc config

3 Verify whether the current CBM LI Proxy application mode is theone you plan to use.

4 If the current CBM LI Proxy application mode is the one you planto use, you have completed this procedure. Otherwise, continuewith the next step.

5 Check the status of CBM LI Proxy application. The status shouldbe ManB/Offl. If not, change the CBM LI Proxy status toManB/Offl.

Exit the cbmmtc config level, by "quit all".

From command line prompt type,appctrl –q all

Change the status to ManB/Offl, type:appctrl –b <n>appctrl -o <n>


6 Again, access the config level of the CBM maintenance interface,typecbmmtc configand select the “CBM LI Proxy” application for configuration, typeselect <n>config <n>


7 Example response

CBM LI Proxy Application Configuration MenuCurrent application configuration: Non-encryptedmodeEnter the new application configuration.0. Quit1. Non-encrypted mode2. Encrypted (TLS) modeConfiguration? [0-2]

8 If you plan to change the CBM LI Proxy application configurationto the “Non-encrypted” mode, continue with the next step.Otherwise, go to step 13.

9 To select the “Non-encrypted” mode, type 1 and press Enter.

10 Example response

Non-encrypted mode selected.Press the Enter key to continue.

11 Press Enter.


NN20000-316 05.02 28 July 2010

.


12 You have completed this procedure.

13 To select the “Encrypted (TLS)” mode, type 2 and press Enter

14 Example response

Please ensure all trust certificates for thedownstream LI servers are installed on CBMAre all the current trust certificates stored underdirectory/cbmdata/configdata/00/clp/trustcerts (Y)es or(N)o?

15 If you do not have the current trust certificates for thedownstream LI servers installed on CBM, continue with the nextstep. Otherwise, go to step 19.

16 Type N and press Enter.

17 Example response

Please store the trust certificates for thedownstream LI servers on the CBM, before changingthe configuration to Encrypted (TLS) mode.Press the Enter key to continue

18 Press Enter.

19 You have completed this procedure.See “Adding or deleting a downstream LI server trust certificatefor the CBM LI Proxy application” (page 68)to ensure all currenttrust certificates are installed on CBM.

20 You have all the current trust certificates for the downstream LIservers installed on CBM. Type Y and press Enter.

21 Example response

Encrypted (TLS) mode selected.Press the Enter key to continue.

22 Press Enter.

23 Exit the cbmmtc config level, typequit all

24 Return to service (RTS) the CBM LI Proxy application.From the command line prompt, check the statusappctrl –q all

To bring the CBM LI Proxy application in service (Insv), type:appctrl –r <n>


--End--


NN20000-316 05.02 28 July 2010

.


Variable definitionsVariable Value

<n> The number that corresponds to the CBM LIProxy or its menu item.


NN20000-316 05.02 28 July 2010

.


Adding or deleting a downstream LI server trustcertificate for the CBM LI Proxy application

Use this procedure to add or delete a downstream LI server trust certificatefor the CBM LI Proxy application.

The CBM LI Proxy application supports self signed trusted servercertificates only for the “Encrypted (TLS) mode”. The self signedserver certificates must be generated by the LI servers withoutthe use of passphrase. All current server certificates must bestored manually on the application specific certificate directory(/cbmdata/configdata/00/clp/trustcerts) within CBM before the “Encrypted(TLS) mode” is selected. These server certificates within CBM must beadded or deleted manually when necessary.

Prerequisites• The CBM LI Proxy application is set to the “Encrypted (TLS)” mode.

For more information, see “Configuring CBM LI Proxy application”(page 64).

• The self-signed server certificates must be generated by the LI serverswithout the use of passphrase. The CBM LI Proxy application supportsself-signed trusted server certificates only. Pre-shared secret orCertificate Authority (CA) certificates are not supported.

• You are a user in a role group authorized to perform config-adminactions

• You have nonrestricted shell access.

For more information about how to log in to the CBM as an authorizeduser, how to request a nonrestricted shell access, or how to displayactions a role group is authorized to perform, see Core and BillingManager 850 Security and Administration for CDMA, (NN20000-320).

Procedure steps

Step Action


2 Go to the CBM LI Proxy application directory for the trustcertificates, type:

cd /cbmdata/configdata/00/clp/trustcerts

3 To add a downstream LI server trust certificate go to the nextstep.


NN20000-316 05.02 28 July 2010

.

Procedure steps 69

OR

To delete a downstream LI server trust certificate, go to step 8.

4 FTP the server trust certificate to the CBM under directory /tmpand rename it to .pem format.

5 Put the new trust certificate from the downstream LI server to theapplication directory on CBM. For example:cp /tmp/server1.pem /cbmdata/configdata/00/clp/trustcerts/server1.pem

6 Change the permission of the new trust certificate:chmod 440 server1.pem

7 Hash all the trust certificates in the CBM LI Proxy applicationdirectory:/opt/perl/bin/perl /opt/openssl/bin/c_rehash<space>.

8

WARNINGDeleting a trust certificate that is still in use couldcause lose of LI CDC data. Confirm that thedownstream LI server trust certificate is no longerneeded before you proceed.

To delete a downstream LI server trust certificate, in the CBM LIProxy application directory locate the certificate.

9 Delete the trust certificate. For example:rm server2.pem

10 Hash the trust certificates in the CBM LI Proxy applicationdirectory:/opt/perl/bin/perl /opt/openssl/bin/c_rehash<space>.

--End--


NN20000-316 05.02 28 July 2010

.


Configuring the time zone option of the OM deliveryapplication

Use this procedure to enable or disable time zone option for OM filenames.

Prerequisites• You are a user in a role group authorized to perform config-admin

actions.

• If Multiservice Data Manager (MDM) IP addresses are configured, see“Job aid” (page 71) to determine the OM configuration values and hostnames for the corresponding MDM servers.


For more information on how to log in to the CBM as an authorizeduser, how to request a nonrestricted shell access, or how todisplay actions a role group is authorized to perform, see CBM850Administration and Security, (NN20000-320)

Procedure steps

Step Action


2 From the command line prompt, access the config level of theCBM maintenance interface:

cbmmtc config

3 Select the OMDD application for configuration:

select <n>

config <n>


4 Press Enter to accept the default value for tuple numberconfiguration.

5 When prompted, do one of the following:

Type y to enable the Timezone option.

OR

Type n to disable the Timezone option.

6 Press Enter to accept the default value for MDM and SuccessionNetwork Manager (SNM) integration.


NN20000-316 05.02 28 July 2010

.

Job aid 71

7 Press Enter to return to the Config level in CBM maintenanceinterface.

8 To access the application (Appl) level, type

appl<n>


9 To busy the application, type

bys<n>


10 To return the application to service, type

rts<n>


--End--


Variable Value

<n> The number next to the OM Deliveryor its menu item.

Job aidIf MDM IP addresses are configured, determine the OM configurationvalues and host names for the corresponding MDM servers, as shown inthese examples.

Example: determining OM configuration valuescat /cbmdata/configdata/00/omdd/odsl.config_file | grep-v "^#"

..MDM_IP_ADDRESS_1PP_5MIN_PM_PORTPP_30MIN_PM_PORTPP_RETRY_INTERVAL_1PP_NUM_RETRIES_1PP_RETRY_INTERVAL_2PP_NUM_RETRIES_2PP_RETRY_INTERVAL_3..


NN20000-316 05.02 28 July 2010

.


Example: determining OM configuration valuescat /cbmdata/configdata/00/omdd/odsl.config_file | grep-v "^#"

..

..MDM_IP_ADDRESS_1 47.135.43.76MDM_IP_ADDRESS_2 47.135.43.77PP_5MIN_PM_PORT 1646PP_30MIN_PM_PORT 1647PP_RETRY_INTERVAL_1 1PP_NUM_RETRIES_1 1PP_RETRY_INTERVAL_2 2PP_NUM_RETRIES_2 2PP_RETRY_INTERVAL_3 3....

Example: determining MDM server host namescat /etc/hosts

..# Internet host table#127.0.0.1 localhost....47.135.43.76 ucars0353c47.135.43.77 ucars0363c..


NN20000-316 05.02 28 July 2010

.

Procedure steps 73

Configuring core access for SBRM through the CBM850

This procedure enables you to configure access to the core for theSynchronous Backup Restore Manager (SBRM). This procedure must beperformed before the SBRM can automatically backup a core image.

This procedure should be performed whenever the password for the coreuser password expires or is changed. This ensures that the password youset in this procedure matches that set for the user on the core.

Prerequisites• Before you perform this procedure for the first time, perform “Creating

the backup user ID on the core for SBRM” (page 75) .



For more information on how to log in to the CBM as an authorizeduser, how to request a nonrestricted shell access, or how to displayactions a role group is authorized, see , Core and Billing Manager 850Security and Administration for CDMA (NN20000-320).


Step Action

1 Log on to the Core and Billing Manager as a user authorized toperform config-admin actions at your workstation.

2 Change directory to the directory containing appropriateconfiguration script:

cd /opt/nortel/bkresmgr/cbm/scripts

3 Run the configuration script:

./bkmgr_config.sh

4 As the script runs, you are first prompted for the user name. Youcan use this user namei to log on to the core in order to initiatean image dump. The script restricts the name to a maximum of


NN20000-316 05.02 28 July 2010

.


16 characters. You must first enable the user name on the core(“Creating the backup user ID on the core for SBRM” (page 75)).

5 As the script continues to run, you are then prompted for theuser you entered (in step 4). The script restricts the password toa maximum of 16 characters. This password is the one that wasset up in “Creating the backup user ID on the core for SBRM”(page 75).

6 As the script continues to run, you are then prompted for thelogical volume where you want to store the backup. This isthe device on which you can store the core image dump . Youshould ensure that this device has enough space to store thebackup.

7 As the script continues to run, you are then prompted for thecore type, either xa-core or Compact. You need this informationfor the software to know whether the core also has a MessageSwitch load.

--End--


NN20000-316 05.02 28 July 2010

.

Job aid 75

Creating the backup user ID on the core for SBRM

This procedure enables you to create the user ID on the core to enablethe operation of the Synchronous Backup Restore Manager (SBRM). Thetypes of operations that can be performed by this user are:

• set dump_restore_in_progress field in ofcstd table

• start image dump

• ability to run itocci command set

Command instructions do not show the system prompt symbol, such as #,>, or $ displayed on the command line.


Step Action

1 At the CI prompt on the core, enter the following command:

permit <backupuser> <backupuser_pswd> 4 10000english all

If Enhanced Password Control is in effect on the CM, thepassword must be at least six characters in length.

If Enhanced Password Control is in effect the system promptsyou to change the password at the first logon. Change thepassword and then perform “Configuring core access for SBRMthrough the CBM 850” (page 73) using the <backupuser> useryou created and the changed password.

The SBRM does not have the ability to manage passwords.Therefore, you must rerun the configuration script in “Configuringcore access for SBRM through the CBM 850” (page 73).

--End--

Job aidThe following table list the parameters for creating the backup user ID onthe core for SBRM.


NN20000-316 05.02 28 July 2010

.


Command Variable Definition

permit <backupuser> This is the user name for the core,that is up to 16 characters in length,that will be used by SBRM for logon.

permit <backupuser_pswd> This is the password for the<backupuser> user you are creating,which can be up to 16 characters inlength.

permit <4> This is the priority.

permit <10000> This is the stack size.

permit <english> This is the language setting.

permit <all> This is the privilege setting.


NN20000-316 05.02 28 July 2010

.

Commissioning the NTP 77

Commissioning or decommissioning Network TimeProtocol (NTP)

Use this procedure to add or remove a Network Time Protocol (NTP)server or peer on the Core and Billing Manager.

After CBM 850 HA system installation, if no external NTP server isconfigured the ntp level of cbmmtc will display an NTP peer server, whichis the unit mate. This is for cluster internal synchronization purposes only.During this time, the overall NTP state is "unequipped" (-) and NTP infois "No NTP servers or peers defined." After the external NTP server isadded, the NTP info will change, and the NTP state will change from (-) to(.), to reflect the presence of an external source.


actions.

For more information on how to log in to the CBM as an authorizeduser, or how to request a nonrestricted shell access, or how to displayactions a role group is authorized , see Core and Billing Manager 850Security and Administration for CDMA, (NN20000-320).


• If you have a distributed Computing Environment (DCE) DistributedTime Service (DTS) commissioned, you will be prompted to removeit after you commission NTP. For this, you need a DCE administratorpassword.

ATTENTIONOn CBM, if you configure more than one NTP server with different stratumlevels then a CBM alarm (log APCL327) is generated. For this you need tocommission NTP servers of same stratum level.

Commissioning the NTPUse this procedure to commission the NTP.


NN20000-316 05.02 28 July 2010

.


Procedure steps


Step Action

1 Log on to the Core and Billing Manager as a user authorized toperform config-admin actions at your workstation or the remoteserver console.

2 Ping the NTP servers to verify connectivity.

ping <A>.<B>.<C>.<D>

Example response

<A>.<B>.<C>.<D> is alive

3 Access the CLI tool:

cli

4 Access the CLI configuration level:

<#>

5 Access the NTP configuration level:

<#>

6 Add an NTP server or peer:

<#>

7 Enter the IP address of the server or peer.

A peer can act as a server.

You can add a maximum of three NTP servers or peers. If youattempt to add more than three, then the system only recognizesthe three most recent NTP servers or peers.

8 Add additional servers or peers, or exit.

If Then

you want to add additionalservers or peers

go to step 6.

you want to exit go to step 13.

After you add each set of 5 NTP servers, you are automaticallytaken to the prompt (shown in step 9) to assign the aliases forthose 5 servers.

9 When prompted, enter x to exit the NTP daemon level.


NN20000-316 05.02 28 July 2010

.


10 Enter the name to be associated with the NTP server.

<ntp_name>

Do not use the IP address of the NTP server as the alias.

11 When prompted, enter x to exit the NTP daemon level.

12 When prompted for TAG(alias), enter the hostname for the NTPserver/peer. Repeat this step until all TAG(alias) have beenentered for the IP addresses previously entered.

The TAG(alias) is not optional for the CBM.

13 When prompted, enter x to exit the NTP configuration level.

14 When prompted, enter x to exit the CLI configuration level.

15 When prompted, type x to exit the CLI tool.

16 Access the RMI level to see the response.

cbmmtc ntp

17

ATTENTIONCompact Call Agent (CCA) and Versatile Service Engine (VSE)platforms derive their NTP timing from the LINUX layer and notfrom the CBM/SDM. Do not activate the OFCENG table parameterSNTP_CLIENT for CCA or VSE platforms; progress to the end ofprocedure.

After you synchronize the CBM , log on to the MTX and ensurethat the date and time are correct before continuing with thisprocedure. SOC TEL00016 "TOD Clock Sync to SD" must haveRTU=Y and STATE=ON.

date

Response:

Date is <XXX>. dd/mm/yyyy hh:mm:ss

18 Change parameter SNTP_CLIENT to Y in table OFCENG. Thisrequires "RWOK ON" access.

TABLE OFCENG;POS SNTP_CLIENT

TABLE: OFCENGSNTP_CLIENT rwok on

WRITE ACCESS ENABLED FOR RESTRICTED DATA

cha

PARMVAL: N

y


NN20000-316 05.02 28 July 2010

.


********************************************NOTE: THE SETTING OF SNTP_CLIENT TO "Y" WILLENABLE THE SNTP CLIENT APPLICATIION.PLEASE ENSURE THE DAEMON ON SDM ISRUNNING BEFORE YOU SET THIS PARAMETERTO "y"Please Execute the CI command STARTNTP to initiatesampling by the SNTP CLIENT application.********************************************TUPLE TO BE CHANGED:SNTP_CLIENT YENTER Y TO CONFIRM, N TO REJECT OR E TO EDIT.

y

TUPLE CHANGEDWRITTEN TO JOURNAL FILE AS JF NUMBER 486

19 Access NTPCI level.

ntpci

WARNING: NTP commands should NOT be used if date is notcorrect. Prior to starting NTP, make sure the date iscorrectly set. If it is not, please set it using theSETDATE command.

date

Date is <XXX>. dd/mm/yyyy hh:mm:ss

help ntpci

LEVEL TO EXECUTE NTP COMMANDS********************************STARTNTP - TO START NTP DATE SAMPLING.QUERYNTPTIME - QUERIES FOR LATEST NTP TIME.SETTIMETONTP - SETS LOCAL CLOCK WITH LATEST NTP TIMEQUIT - TO QUIT THE NTPC LEVEL.

20 Use STARTNTP command to enter the corresponding time zone.You can calculate offset according to GMT. Use the followinginformation as a quick reference.

Standard Time:

• EST =-300(5 hours or 300 minutes)

• CST =-360(6 hours or 360 minutes)

• MST =-420(7 hours or 420 minutes)

• PST =-480(8 hours or 480 minutes)


NN20000-316 05.02 28 July 2010

.


Daylight Savings Time:

• EDT =-240(4 hours or 240 minutes)

• CDT =-300(5 hours or 300 minutes)

• MDT =-360(6 hours or 360 minutes)

• PDT =-420(7 hours or 420 minutes)

STARTNTP <-XXX>

PLEASE CONFIRM IF YOU REALLY WANT TO START NTP DATACOLLECTION WITH TIMEZONE VALUES AS : <-XXX> MINUTESPlease confirm ("YES", "Y", "NO", or "N"):

y

NTP DATA COLLECTION STARTED WITH TIMEZONE VALUE : <-XXX>MINUTESPLEASE REMEMBER TO EXECUTE SETTIMETONTP COMMAND TOSYNCHRONISE CORE CLOCK WITH NTP********************************************Collecting SAMPLEs from SDM. It may take a few minutes.******************************************

21 Execute QUERYNTPTIME to query NTP time. Values vary.

QUERYNTPTIME

Example response

******************************************THE CORE CLK WRT NTP TIME IS AS UNDER:******************************************TIME OFFSET : 40267 MILLI SECONDSROUND TRIP DELAY : 24 MILLI SECONDSNTP TIME : 3309735086 SECONDS,488 MILLI SECONDSTIME ZONE : -360 MINUTESSAMPLE AGE : 53 SECONDSVALID SAMPLE %AGE : 0 %

22 Execute SETTIMETONTP to sync MTX to NTP server. Valuesvary.

SETTIMETONTP


NN20000-316 05.02 28 July 2010

.


Example response

******************************************THE CORE CLK WRT NTP TIME IS AS UNDER:******************************************TIME OFFSET : 40267 MILLI SECONDSROUND TRIP DELAY : 24 MILLI SECONDSNTP TIME : 3309735096 SECONDS,454 MILLI SECONDSTIME ZONE : -360 MINUTESSAMPLE AGE : 63 SECONDSVALID SAMPLE %AGE : 0 %PLEASE CONFIRM IF YOU INTEND TO SYNCHRONISE CORE CLKWITH ABOVE VALUESPlease confirm ("YES", "Y", "NO", or "N"):y

**********************************************THE CORE CLK IS SYNCHRONISED WITH NTP AS UNDER:**********************************************TIME OFFSET : 40267 MILLI SECONDSROUND TRIP DELAY : 24 MILLI SECONDSNTP TIME : 3309735140 SECONDS,507 MILLI SECONDSTIME ZONE : -360 MINUTESSAMPLE AGE : 67 SECONDSVALID SAMPLE %AGE : 0 %

23 Verify the time and date and compare to the CBM. They mustbe the same.

--End--

Decommissioning the NTPUse this procedure to decommission the NTP.



NN20000-316 05.02 28 July 2010

.

Decommissioning the NTP 83

Procedure steps


Step Action

1 From the MTX, change the parameter SNTP_CLIENT to N intable OFCENG.

Ericsson recommends that you remove NTP from the MTXbefore CBM.

Ericsson recommends that you run the SOS logs during thisprocess on a separate terminal.

parmfind sntp

TABLE OFCENG;POS SNTP_CLIENT YNo more entries found

TABLE OFCENG;POS SNTP_CLIENT Y

TABLE: OFCENGSNTP_CLIENT Y

cha

PARMVAL: Y

n

**********************************************NOTE: THE SETTING OF SNTP_CLIENT TO "N" WILL DISABLETHE SNTP CLIENT APPLICATION. THIS PARAMETER SHOULDNEVER BE SET FROM "Y" -> "N" TO GET RID OF SNTP CLIENTSALARMS/LOGS.********************************************TUPLE TO BE CHANGED:SNTP_CLIENT NENTER Y TO CONFIRM, N TO REJECT OR E TO EDIT.

y

**********************************************NOTE: THE SETTING OF SNTP_CLIENT TO "N" WILL DISABLETHE SNTP CLIENT APPLICATION. THIS PARAMETER SHOULDNEVER BE SET FROM "Y" -> "N" TO GET RID OF SNTP CLIENTSALARMS/LOGS.**********************************************TUPLE CHANGEDWRITTEN TO JOURNAL FILE AS FJ NUMBER 489


NN20000-316 05.02 28 July 2010

.


2 Log on to the Core and Billing Manager as the root user at yourworkstation or the remote server console.

3 Access the CLI tool:

cli


<#>


<#>

6 Remove all servers or peers, remove selected servers or peers,or exit.

If Then

you want to remove all NTPservers or peers

go to step 8.

you want to remove only selectedNTP servers or peers

go to step 10.


7 Remove all NTP servers

<#>

8 When prompted, enter y to confirm the deletion or n to cancel.Go to step 14.

9 Remove only selected NTP servers or peers

<#>

You can also delete an NTP server or peer using either itshostname or IP address.

10 When prompted, enter the hostname for the NTP server or peerwhich you want to delete.

If Then

you want to remove an additionalNTP server or peer

repeat this step.


11 Access the Unconfigure the NTP daemon level.

<#>

12 When prompted, enter y to confirm the deletion or n to cancel.Go to step 14.



15 When prompted, type x to exit the CLI tool.


NN20000-316 05.02 28 July 2010

.


16 Access the RMI level to see the response.

cbmmtc ntp

17 Verify the time and date on the MTX and CBM. Billing is affectedif the time is incorrect.

--End--


Variable Value

<A>.<B>.<C>.<D> The NTP server IP address.

<#> The number next of the menu item youwant to select.


NN20000-316 05.02 28 July 2010

.


Adding or removing an NTP server or peer

Use this procedure to add or remove a Network Time Protocol (NTP)server or peer.

You can add up to three NTP servers or peers.

If you have Distributed Computing Environment (DCE) installed on yoursystem and are deleting the last NTP server or peer, you will be promptedto set up the DCE’s DTS. For this, you will need a DCE administratorpassword.

Prerequisites• You are a user authorized to perform config-manage actions.


For information about how to log in to the CBM as an authorized user,how to request a nonrestricted shell access, or how to display actionsa role group is authorized, see Core and Billing Manager 850 Securityand Administration for CDMA, (NN20000-320).


Step Action

1 Log on to the Core and Billing Manager as a user authorized toperform config-admin actions at your workstation or the remoteserver console.

2 Access the CLI tool

cli


<#>


<#>

If Then

you want to add an NTP serveror peer

go to step 5.


NN20000-316 05.02 28 July 2010

.

Procedure steps 87

If Then

you want to remove all NTPservers or peers

go to step 8.

you want to remove only aselected NTP server or peer

go to step 10.

5 Add an NTP server or peer:

<#>

6 When prompted, enter the IP address for that server or peer.

If Then

you want to add an additionalNTP server or peer

repeat this step.

you want to exit enter x.

You can add a maximum of three NTP servers or peers. If youattempt to add more than three, then the system only recognizesthe three most recent NTP servers or peers.

A peer can act as a server.

7 When prompted, enter the hostname for the server or peer.Repeat this step until all TAG (alias) have been entered for theIP addresses previously entered.

Please do not use the IP address as an NTP hostname TAG(alias).

The TAG (alias) is not optional for the CBM.

If Then

you want to add an NTP serveror peer

go to step 5.


8 Remove all NTP servers

<#>

9 When prompted, type y to confirm the deletion or n to cancel.Go to step 12.

10 Remove only selected NTP servers or peers

<#>

You can also delete an NTP server or peer using either itshostname or IP address.

11 When prompted, enter the hostname for the NTP server or peerwhich you want to delete.


NN20000-316 05.02 28 July 2010

.


If Then

you want to remove an additionalNTP server or peer

repeat step 11.




14 When prompted, enter x to exit the CLI tool.

15 Access the Core and Billing Manager RMI level to see theresponse.

cbmmtc ntp

--End--


Variable Value

<A>.<B>.<C>.<D> The NTP server IP address.

<#> The number of the menu item youwant to select.


NN20000-316 05.02 28 July 2010

.

Procedure steps 89

Installing the logreceiver tool on a clientworkstation

Use this procedure to install the logreceiver tool on a client workstation.The procedure accesses the logreceiver software stored on the CBM towhich the workstation can connect, and installs it in a specific directory onthe workstation.

The logreceiver tool is supported only on clients running Solaris 7, Solaris8, or Solaris 9.



Step Action

1 FTP to the CBM at the local or remote VT100 console

ftp <CBM_IP_address>

2 Change the directory to /swd/client

ftp> cd /swd/client

3 Change the files transfer mode to binary

ftp> binary

4 Get the logreceiver tool

ftp> get logreceiver

5 Quit FTP

ftp> bye

6 Grant execute permissions to the logreceiver

chmod +x logreceiver

--End--


NN20000-316 05.02 28 July 2010

.



Variable Value

<CBM_IP_address> The IP address or node name of theCBM.


NN20000-316 05.02 28 July 2010

.

Procedure steps 91

Installing the CMFT on a client workstation

Use this procedure to install the Command Module (CM) File Transferscript (CMFT) on a client workstation.

This procedure copies the CMFT from the CM to a specified directory onthe client workstation, typically /sdm/bin. The CMFT script allows you touse SCFT (SSH Core File Transfer) to transfer files to and from the CM.

SCFT is described in the "OpenSSH Overview" section in Core and BillingManager 850 Accounting for CDMA, (NN20000-318).

CMFT is supported only on clients running Solaris 7, Solaris 8, or Solaris9.

SCP and SSH must be installed before you can install CMFT. The versionof SSH that is installed must support the SSH 2.0 protocol.



Step Action

1 Log on to the client workstation.

2 FTP to the Core and Billing Manageras an authorized user forFTP.

ftp <CBM_IP_address>

3 Change the directory to/sdm/scft, type:

cd /sdm/scft

4 Change the files transfer mode to binary.

binary

5 Verify that you have successfully transferred the CMFT script

ls -l cmft

The client workstation displays the CMFT script.


NN20000-316 05.02 28 July 2010

.


6 Set the ownership and permissions of the CMFT script to 755:

chmod 755 cfmt

--End--


Variable Value

<CBM_IP_address> The IP address or node name of theCore and Billing Manager.


NN20000-316 05.02 28 July 2010

.


Configuring the SuperNode Billing Application

For more information about how to install and configure the SuperNodeBilling Application (SBA) see CBM 850 Accounting for CDMA,(NN20000-318).


NN20000-316 05.02 28 July 2010

.


Installing SCFT

Use this procedure to install SCFT (SSH Core File Transfer). SCFT allowsyou to use secure FTP to access the Core. SCFT usage is described inCBM 850 Security and Administration for CDMA, (NN20000-320).


actions.


For more information about how to log in to the CBM as an authorizeduser, how to request a nonrestricted shell access, or how to displayactions a role group is authorized, see Core and Billing Manager 850Security and Administration for CDMA, (NN20000-320).


Step Action

1 Log on to the core manager as a user authorized to performconfig-admin actions at the local or remote VT100 console.

2 Access the cbmmtc interface:

cbmmtc

3 Go to the apply level of the cbmmtc interface:

apply

4 Select the SSH Core File transfer number.

5 Select the default source for the directory path on the core:

/data/swd/sdm

6 Apply this selection:

apply

A dialog prompts you to confirm your selection:

Example response

Do you wish to proceed? Please confirm ("YES", "Y","NO", or "N")


NN20000-316 05.02 28 July 2010

.


7 Enter Y to confirm your selection.

The system executes your request. A dialog then confirms thesuccessful execution of your selection.

--End--


Variable Value

<n> The number next to the SSH Core FileTransfer selection.


NN20000-316 05.02 28 July 2010

.


Enabling the second LAN interface on the CBM

Use this procedure to enable or disable the second LAN.

ATTENTIONDo not use this procedure unless directed, as CBM to core communication willbe disrupted.

After this procedure is enabled on one unit, changes are automaticallypropagated to mate unit in the cluster.


actions.


For more information on how to log in to the CBM as an authorizeduser, how to request a nonrestricted shell access, or how to displayactions a role group is authorized, see Core and Billing Manager 850Security and Administration for CDMA, (NN20000-320).


Step Action

1 At the Inactive unit, log on to the SPFS-based server using SSH(secure) is as follows:

2 Log on to the server, type

ssh -l root<server>

and press Enter.

If this is the first time you are logging on using SSH, the systemrequests that you confirm to continue connecting. Enter yes atthe prompt.


4 Browse to the Security Services Configuration menu within thecommand line interface as follows:

Access the command line interface, type


NN20000-316 05.02 28 July 2010

.


cli

and press Enter.

5 Enter the number next to the "Configuration" option in the menu.

6 Enter the number next to "IP Configuration".

7 Enter the number next to the "enable_2network" option in themenu.

Example response

== Executing "enable_2network"Enabling second network interfaceEnabling second LAN interface completed successfully

=== "enable_2network" execution completed

8 Enter x to exit each level until you have exited from the CLI tool.

ATTENTIONYou must perform a reboot to make FUNCTIONAL beforeconfiguration.

--End--


Variable Value

<server> The IP address or host name of theSPFS-based client server.


NN20000-316 05.02 28 July 2010

.


Configuring the second LAN interface on the CBM

Use this procedure to configure the second LAN interface.


The hardware card must be inserted before enabling the second LAN.


actions.



• The second LAN interface must be enabled to be configured.


Step Action


2 Log on to the server, type

ssh -l root <server>

and press Enter.




Access the command line interface, type


NN20000-316 05.02 28 July 2010

.

Procedure steps 99

cli

and press Enter.



7 Enter the number next to the "config_data_2network" option inthe menu.

Example response

=== Executing "config_data_2network"WARNING: Changing the network settings will effectall applications! Improper network configurationwill result in loss of service! Applications mayrequire restart or reconfiguration after networkchangesCurrent configuration ---------------------second network hostname: wcarsx0q-public1 secondnetwork IP address: second network netmask: secondnetwork unit 0 IP address: second network unit 0hostname: wcarsx0q-public1-unit0 second networkunit 1 IP address: second network unit 1 hostname:wcarsx0q-public1-unit1Specify new configuration -------------------------Enter the hostname for the second interface:[wcarsx0q-public1] public1 Enter IP address forpublic1: 10.0.01 Enter netmask for public1:255.255.0.0Configure additional virtual IP address? [no] noEnter IP address for unit 0: 10.0.0.2 Enter IPaddress for unit 1: 10.0.0.3 New configuration--------------------- second network hostname:public1 second network IP address: 10.0.0.1 secondnetwork netmask: 255.255.0.0second network unit 0 IP address: 10.0.0.2 secondnetwork unit 0 hostname: public1-unit0 secondnetwork unit 1 IP address: 10.0.0.3 second networkunit 1 hostname: public1-unit1Enter "ok" to accept current settings Enter anythingelse to re-enter settings ok Attempting to updatefiles on mate unit, please wait... Reconfiguringcluster node(s), please wait...The network changes have been made, however thecluster requires a restartof both units. The units must be restarted in thebelow order.


NN20000-316 05.02 28 July 2010

.


1) Login as root on the console of the standby unit andshut it down with the command: "shutdown -i 0 -y".2) After the standby unit has shutdown, restart theactive unit with the command: "shutdown -i 6 -y".3) After the restart is complete, the new networksettings are in effect. 4) Boot the standby unit withthe command "boot".

=== "config_data_2network" execution completed


ATTENTIONYou must reboot for all changes to take effect properly.

--End--


Variable Value



NN20000-316 05.02 28 July 2010

.

Procedure steps 101

Disabling the second LAN interface on the CBM

Use this procedure to disable the second LAN interface.



actions.



• The second LAN interface must be enabled to be configured.


Step Action


2 Log on to the server , type


and press Enter.




Access the command line interface,type

cli


NN20000-316 05.02 28 July 2010

.


and press Enter.



7 Enter the number next to the "config_data_2network" option inthe menu.

Example response

=== Executing "disable_2network"Disabling second network interfaceThis script will disable the second LAN interface andremove allassociated configuration. Specifically, we will beremoving thefollowing hostnames from the /etc/inet/hosts file:public1public1-unit0public1-unit1Enter ’ok’ to continue, anything else to abort: [no]okuser choosing to continue procedure, continuingThe network changes have been made, however thecluster requires a restartof both units. The units must be restarted in thebelow order.1) Login as root on the console of the standby unit andshut it down withthe command: "shutdown -i 0 -y".2) After the standby unit has shutdown, restart theactive unit withthe command: "shutdown -i 6 -y".3) After the restart is complete, the new networksettings are in effect.4) Boot the standby unit with the command "boot".

=== "disable_2network" execution completed


--End--


Variable Value



NN20000-316 05.02 28 July 2010

.

Procedure steps 103

Selecting the highest priority interface for CBMMultiNet failover

Select the highest priority interface, between the first and second LAN forcluster failover in response to severe network faults.

You can also set priority for CBM Northbound connectivity over CBM Coreconnectivity. In this situation, a node with only NOC/OSS connectivitythrough uplink0 is considered healthier than a node with uplink2 up, butno uplink0.

Prerequisites• You must install MTX17 on a Netra server cluster.

• The second LAN interface must be enabled and configured. See“Enabling the second LAN interface on the CBM” (page 96) and“Configuring the second LAN interface on the CBM” (page 98).





Step Action

1 At the active unit, log on to the server, type


and press Enter.




NN20000-316 05.02 28 July 2010

.


3 Browse to the cbmmtc net menu within the command lineinterface.

4 Type priority view, and press Enter.

5 Type priority set uplink0 or priority set uplink2 andpress Enter.

6 Type priority view, and press Enter.

7 Type quit all, and press Enter.

--End--


Variable Value



NN20000-316 05.02 28 July 2010

.

Procedure steps 105

Enabling the third LAN interface

Use the following procedure to enable the third network interfacesuccessfully.







Step Action

1 Log on to the SPFS-based server type


and press Enter.



3 Browse to the IP Configuration menu within the command lineinterface as follows:

Access the command line interface type

cli

and press Enter.


NN20000-316 05.02 28 July 2010

.


4 Select the number next to the ’Configuration’ option in the menu.

5 Select the number next to the ’IP Configuration’ option in themenu.

6 Select the number next to the ’enable_3network’ option in themenu.

--End--


Variable Value



NN20000-316 05.02 28 July 2010

.

Procedure steps 107

Configuring the third LAN interface

Use the following procedure to configure the third network successfully.






Step Action

1 Act the active unit, log on to theSPFS-based server type


and press Enter.





cli

and press Enter.




NN20000-316 05.02 28 July 2010

.


6 Select the number next to the ’configure_3network’ option in themenu. The old configuration data appears.

7 Provide the correct parameters for configuration.

8 Follow the instructions provided by the CLI to restart both units.

--End--


Variable Value



NN20000-316 05.02 28 July 2010

.

Procedure steps 109

Disabling the third LAN interface

Use the following procedure to disable third network interface successfully.






Step Action

1 At the active unit, log on to the SPFS-based server using SSH(secure) as follows:

2 Log on to the server type


and press Enter.





cli

and press Enter.



NN20000-316 05.02 28 July 2010

.



7 Select the number next to the ’disable_3network’ option in themenu.

--End--


Variable Value



NN20000-316 05.02 28 July 2010

.

Procedure steps 111

Querying the port status of uplink0, uplink2, anduplink3

Use the following procedure to query the port status of uplink interfaces.The status for multinets are displayed if uplink2 and upink3 are configured.






Step Action

1 At the active unit, log on to the SPFS-based server by typing


and press Enter.





cli

and press Enter.

4 Select the number next to the ’view’ option in the menu.


NN20000-316 05.02 28 July 2010

.


5 Select the number next to the ’port_util’ option in the menu.

--End--


Variable Value



NN20000-316 05.02 28 July 2010

.

Procedure steps 113

Changing the IP address for uplink3

Use the following procedure to change the IP address for uplink3.






Step Action

1 At the active unit, log on to the SPFS-based server type


and press Enter.





cli

and press Enter.




NN20000-316 05.02 28 July 2010

.


6 Select the number next to the ’enable_3network’ option in themenu.

7 Select the number next to the ’configure_3network’ option in themenu. The old configuration data appears.

8 Provide the correct parameters for configuration.

9 Follow the instructions provided by the CLI to restart both units.

--End--


Variable Value



NN20000-316 05.02 28 July 2010

.

Procedure steps 115

Associating a logical OAM tag with a physicalinterface

Associate a logical OAM tags with physical interfaces to define the LANthat OAM traffic switches to after a failover.







Step Action

1 At the active unit, log on to the SPFS-based server using SSH(secure) as follows:

2 Log on to the server type


and press Enter.



4 Browse to the cbmmtc net menu within the command lineinterface.

5 Type TagDef view, and press Enter.


NN20000-316 05.02 28 July 2010

.


6 Type Tagdef set dualLAN, provide uplink0 or uplink2 as inputsand press Enter.

7 Type TagDef view, and press Enter.

8 Type quit all, and press Enter.

--End--


Variable Value



NN20000-316 05.02 28 July 2010

.

Procedure steps 117

Installing optional software on a CBM 850

This is a generic procedure that is used for installing optional softwarepackages on the CBM 850.

After completing this procedure you need to run patch audit to get theapplicable patches for the packages you just installed.

PrerequisitesATTENTIONContact your next level of support to ensure the optional package you want toinstall is compatible with your current CBM profile.


Step Action

1 At your workstation, log on to the CBM.

2 From the command line prompt, access the apply level of thecbm maintenance interface:

cbmmtc apply

The system displays the apply level screen of the cbmmaintenance interface, which shows a list of the packages, if anyexist, in the default source directory.

You can display up to 12 software packages at a time. Usethe Down command (command 13 as shown in the followingexample) to view other packages.

Example response of cbm maintenance interface applylevel


NN20000-316 05.02 28 July 2010

.



If Then

CD-ROM is used todeliver the CBM software

go to step 4 and specify/cdrom/cdrom/applications/cbm/packages forthe <source_directory_name> variable.

you want to exit fromthe cbm maintenanceinterface

go to step 14.

4 Insert the CD-ROM into the CD drive if it is not already presentin the drive.

5 At the command line located at the bottom of the cbmmtc userinterface screen, type:

source <source_directory_name>

Example response apply level showing the CD-ROMsource directory

As shown in the following example, the system displaysthe apply level screen of the cbm maintenance interface,which shows a list of all packages in the source directorythat you specified.


NN20000-316 05.02 28 July 2010

.

Procedure steps 119

6 In the list of packages, locate the packages you want to applyand take note of their numbers (located next to the names of thepackages). Select the packages you want to apply:

select <package number> ... <package number>

Example responseTo select the Reach Through SPM application, which isnumber 6, and OM Delivery, which is number 11 in thesample screen display shown in the previous figure, enter

select 6 11

To de-select any packages that you selected, re-enter theselect command for the packages you want to de-select.The highlighting on the packages that you deselect isremoved.

The packages you selected are highlighted on the cbmmtc applyscreen, as shown in the following figure.

Example response of selecting packages to apply


NN20000-316 05.02 28 July 2010

.


7 Apply the selected packages:

apply

8 If a prerequisite package for the packages you have selected toapply is not already applied on the system, the system SWIMtool automatically selects and applies the prerequisite packageunless the package is currently selected to be applied.

Example response of the results screen after applyingpackages

The system prompts if you want to continue with applying theselected packages.

9 Use the following table to determine your next step

If Then

you want to continue the package application go to step 10.

you do not want to continue the package application go to step 13.

10 Type yes in response to the prompt.

The status of each package application appears on the cbmmtcapply screen, as shown in the following figure.


NN20000-316 05.02 28 July 2010

.

Procedure steps 121

Example response of the apply level showing the statusof applied packages

11 When you complete the application, the installed packagesappear in the list that appears when you enter the cbmmtcpackages level. Verify that the status of the new packagesindicates Applied under the Status column.

ATTENTIONIt is important that packages installed on the system not be leftwith a Partial status. If any package installed application fails orotherwise shows a Partial status, contact your next level of supportfor assistance.

12 If applicable, review details about the CBM package applicationby entering the following command:

history

The system displays information about package transactionsperformed, including a log file and the results of the individualoperations. Included is an indication of the node on which theoperations were performed. If the operations were performedon the inactive node, the inactive node identifier appears in theinformation displayed.

13 Type no in response to the prompt.

14 Exit from the cbm maintenance interface:

quit all

15 Ensure the CBMs are patch-current.


NN20000-316 05.02 28 July 2010

.


16 You have completed this procedure. If applicable, return tothe higher level task flow or procedure that directed you to thisprocedure.

--End--


Variable Value

<source_directory_name> The full pathname of the directorycontaining the package that you wantto apply. Since CD-ROM is being usedfor the installation, specify /cdrom/cdrom/applications/cbm/packages as thesource_directory_name.

<package number> The number associated with apackage, that you noted. Eachpackage number is separated bypreceding and succeeding spaces.


NN20000-316 05.02 28 July 2010

.

Procedure steps 123

Configuring a virtual IP address on an SPFS-basedserver

Use this procedure to configure a virtual IP address on a Server PlatformFoundation Software (SPFS) based server. This procedure applies tosimplex and high availability (HA) servers. An HA server refers to a SunNetra 240 or T5220 server pair.

A virtual IP address is required for the Audio Provisioning Server (APS),which resides on the same server with the tools software.

Prerequisites• You have the root or emsadm user ID and password for the server on

which you are configuring the virtual IP address.




Procedure stepsATTENTIONIn a cluster configuration, perform these steps on the Active server.

Step Action

1 At your workstation, log in to the server.

ATTENTIONFor administrative purposes, customers must connect to either clusternode through the console only.

In a cluster configuration, log in to the active server through theconsole as root or emsadm user, and ensure you are on theactive server using the ubmstat command.

For more information about how to log in to an SPFS-basedserver through the console, see CDMA Core Administration andSecurity, (NN20000-707).

Example output from active unitClusterIndicatorACT


NN20000-316 05.02 28 July 2010

.


Example output from inactive unit

ClusterIndicatorSTBY

For a simplex configuration, log in to the unit as root or emsadmthrough the console.

2 In a cluster configuration, before changing the networkconfiguration, bring the standby node to OK prompt.

shutdown -i 0 –y

3 Access the command line interface by typing

cli

and press Enter.

4 Enter the number that corresponds to the "Configuration" optionin the menu.

5 Enter the number that corresponds to the "IP Configuration"option in the menu.

6 Enter the number that corresponds to the "config_data" option inthe menu

Example response

===Executing "config_data"WARNING: Changing the network settings will effectall applications! Improper network configurationwill result in loss of service! Applications mayrequire restart or reconfiguration after networkchanges

CAUTION: HTTPS Certificate is installed forwebservices. Changing the hostname or ip may requirean updated certificate.

hostname:<hostname>ip address:<ip address>Enter the hostname for this system [hostname]

7 When prompted, enter the hostname for this SPFS-based server,or press Enter to accept the default value if one is specified.

Example response

Enter ip address for <hostname> [00.00.00.00]

8 When prompted, enter the IP address for this SPFS-basedserver, or press Enter to accept the default value if one isspecified.

Example response

Configure additional ip address? [yes]


NN20000-316 05.02 28 July 2010

.

Procedure steps 125

9 When prompted, indicate whether you want to configure anadditional IP address.

If you enter Do

yes step 10.

no step 13.

10 When prompted, enter the virtual IP address you want toconfigure on this server, or press Enter to accept the defaultvalue if one is specified.

Example response

Enter application for ip address <ip address>

11 When prompted, enter the application name for the additional IPaddress you just specified, or press Enter to accept the defaultvalue if one is specified.

The system allocates a hostname for each virtual IPaddress that is configured. The hostname is in the formof <spfs_primary_hostname-application>, for example,“wxe0s00j-aps” when the virtual IP address is set up for APS.Hostnames are stored in file” /etc/hosts” on the system.

Example response

Configure additional ip address? [no]

12 Repeat step 9.

13 When prompted, confirm the settings by typing

ok

and press Enter.

Example response on an HA system

The network changes have been made to the localcluster unit only.To complete the changes on the local unit and updatethe mate unit, you must perform the following actionsin order:1) Ensure the Ethernet cables for new subnet/IP arenow connected OR the 4 Router ports are reconfiguredfor the new subnet.


NN20000-316 05.02 28 July 2010

.


NOTE: You need to perform step 1 only if you arereconfiguring to new subnet2) Restart this (local) unit with the command:"shutdown -i 6 -y".3) After the restart is complete, the new networksettings are in effect on the local unit only.4) It is necessary to clone the remote unit from thelocal unit.Please follow the documented cloning procedure’Cloning the image of one node in a cluster to theother node’ to update the remote unit which willcomplete the configuration changes for this cluster.=== "config_data" execution completed

Example response on a simplex system

The network changes have been made, however a restartis required to use the new network settings. Rebootto ensure all applications are restarted. You mustperform the following actions in order.1) Ensure the Ethernet cables for new subnet/IP arenow connectedOR the 2 Router ports are reconfigured for the newsubnet.NOTE: You need to perform step 1 only if you arereconfiguring to new subnet2. Reboot machine using the command "shutdown -i 6-y"=== "config_data" completed successfully

14 Exit each menu level of the command line interface to eventuallyreturn to the command prompt, by typing

select - x

and press Enter.

15 Restart system to activate the new IP configuration. In the caseof cluster configuration, perform this operation on active consoleserver.

Run the command shutdown

shutdown -i 6 –y

ATTENTIONIn the case of cluster configuration, perform this operation on activeconsole server.

16 In case of cluster configuration, clone the remote unit from thelocal unit. Please follow the documented cloning procedure’Cloning the image of one node in a cluster to the other node’to update the remote unit which will complete the configurationchanges for this cluster.


NN20000-316 05.02 28 July 2010

.

Procedure steps 127

ATTENTIONThis step is not applicable for simplex machine.

--End--


NN20000-316 05.02 28 July 2010

.


Configuring client and server ports on anSPFS-based server for secure Firewallcommunications

Use this procedure to configure the client-side and server-side ports ona Server Platform Foundation Software (SPFS)-based server to facilitatesecure firewall communication between client and server applications.

You can also use this procedure to list the ports that are currentlyconfigured.

ATTENTIONThe server-side port has a default value of 10080, and the client-side port hasa default value of 10090. If the default value is acceptable, it is not necessaryto configure the ports.

Prerequisites• The server-side port has the same value across all offices in the

network. If the ports do not have the same value, the client applicationGUIs fails to launch.

Procedure steps

Step Action

1 At your workstation, Telnet to the server:

telnet <server>


2 When prompted, enter your user ID and password.

3 Change to the root user:

su - root


5 Access the command line interface:

cli

6 Enter the number next to the Configuration command on themenu.

7 Enter the number next to the Security Services Configurationcommand on the menu.


NN20000-316 05.02 28 July 2010

.

Procedure steps 129

8 Enter the number next to the Socks Configuration commandon the menu.

9 Enter the number next to the list_socks command on the menuto display the server-side and client-side Socks Proxy portscurrently configured.

Example response:

The ports configured for use by socks are:The Client side SOCKS Proxy will listen on port 10090The Server side SOCKS Proxy will listen on port 10080

==="list_socks" completed successfully

10 To change the ports, enter menu, choose config_sockscommand on the menu.

Example response:

The changes of the server side port is a disruptiveaction. If the server side port is changed, the SOCKSserver and all dependent applications must be restarted.SOCKS ports in all offices must be configured to the sameport. Misconfiguration will cause EMS clients to notfunction.Proceed with caution.

Enter the port the Server side SOCKS Proxy will listen on.Value must be within [1025 - 655351]. current Value -10080 [?, q]

11

ATTENTIONChanging the Socks server-side port requires a restart of the SOCKSserver and all dependent applications.

Enter the server-side port, or press Enter to accept the defaultvalue (10080).

Example response:

Leaving SERVER port at 10080

Enter the port the Client side SOCKS Proxy will listen on.Value must be within [1025 - 655351]. Current value -10090 [?, q]

12 Enter the client-side port, or press Enter to accept default value(10090).

Example response


NN20000-316 05.02 28 July 2010

.


Leaving CLIENT port at 10090Leaving both ports at configured values:Server side SOCKS Proxy port: 10080Client side SOCKS Proxy port: 10090

==="Config_socks" completed successfully

ATTENTIONChanging the Socks client-side port requires that all clientworkstations that run the application GUIs, be restarted to use thenew port.

13 Exit each menu level of the command line interface:

select - x

14 If you changed the server-side port, restart the Socks server andall dependent server applications (SESM, SAM21EM).

For more information, see CDMA Core Administration andSecurity, (NN20000-707) for the Socks server, SESM andSAM21 server applications.

15 If you changed the client-side port, restart any client workstationsthat run the application GUIs.

--End--


<server> The IP address or host name of theSPFS-based server.


NN20000-316 05.02 28 July 2010

.

Performing a query of the provisioned static route(s) on a SPFS-based server 131

Provisioning static routes on an SPFS-based server

ApplicationBefore entering a static route on static route SPFS-based server(s),preliminary planning must take place. This planning is normally done by anetwork engineer or IT specialist. The role of this prime is to add all theinformation necessary to successfully add a new static route on a Solaris©system.

It is not recommended to have multiple administrators perform some staticroute provisioning simultaneously on the same cluster/server.

As enforced by the Solaris route command, the network gateway identifiedin the template below must be reachable (that is, the address can be pingand the ARP request passes).

Use the following template to fill in as a worksheet, before adding ordeleting a static route:

Field Value

Route Type: net or host

Target host/network IP address

Target network netmask (not applicable for ahost entry)

Network gateway IP address

Node IP address to ping

Use the following template to fill in as worksheet, before modifying a staticroute:

Field Original Value New Value

Route type: net or host

Target host/network IP address

Target network netmask (notapplicable for a host entry)

Network gateway IP address

Node IP address to ping

Performing a query of the provisioned static route(s) on aSPFS-based server

This section shows the user how to perform a query of the provisionedstatic route(s) on a SPFS-based server.


NN20000-316 05.02 28 July 2010

.


Prerequisites• You can log in with permission level that allows you to run the CLI tool.

ProcedurePerforming a query of the provisioned static route(s) on a SPFS-basedserver

Step Action

At your workstation1 From the command line type:

cli

2 Enter the number next to Configuration.

3 Enter the number next to IP Configuration

4 Enter the number next to Static Route Configuration.

5 Enter the number next to query_static_route (Query ProvisionedStatic Route).

Example Response

--End--


NN20000-316 05.02 28 July 2010

.

Procedure 133

Performing an add static route(s) on a SPFS-based serverThis sections shows the user how to perform an add static route on aSPFS-based server.

PrerequisitesWARNINGIf the template listed in the Application section of this procedureis not completed, STOP and contact your network administrator.Failing to do so could lead to a network outage.

Query the system to ensure there are no network alarmsreported. Resolve any network alarms, before you continuewith provisioning. Failure to follow this action may result in lostbilling.

WARNINGStatic route provisioning should not be performed under thefollowing conditions:

• During a fresh software installation. Provisioning is doneafter the mate unit clone.

• During a software upgrade. Provisioning is done after theupgrade acceptance is executed.

• You have root user privileges. For CBM users, refer to the followingprerequisites section.

Prerequisites for Core and Billing Manager 850

• You are user in a role group authorized to perform config-adminactions.

See "Displaying actions a role group is authorized to perform," inCore and Billing Manager 850 Security and Administration for CDMA,(NN20000-320).


See "Requesting nonrestricted shell access," in Core and BillingManager 850 Security and Administration for CDMA, (NN20000-320).

ProcedurePerforming an add static route(s) on a SPFS-based server

Step Action

At your workstation1 From the command line type:

cli


NN20000-316 05.02 28 July 2010

.



3 Enter the number next to IP Configuration.


5 Enter the number next to add_static_route to add a new staticroute.

Example response (host):

=== Executing "add_static_route"

To abort the operation, type abort in any of the following fields:

Enter route type [net or host]: <Enter the route type fromthe template.> Abort this command by abort or answeringn at the confirmation prompt.

Enter target IP address[xx.xx.xx.xx]: <Enter the target IPaddress from the template.>

Enter gateway IP address[xx.xx.xx.xx]: <Enter the gatewayIP address from the template.>

Verify the information and enter y if correct. If you enter n, thecommand is aborted.Add command complete successfully.

=== "add_static_route" execution completed

Example response (net):=== Executing "add_static_route"

Enter route type [net or host]: <Enter the route type fromthe template.>

Enter target IP address[xx.xx.xx.xx]: <Enter the target IPaddress from the template.>

Enter target IP netmask[xx.xx.xx.xx]: <Enter the targetnetmask from the template.>

Enter gateway IP address[xx.xx.xx.xx]: <Enter the gatewayIP address from the template.>


NN20000-316 05.02 28 July 2010

.

Performing a delete static route(s) on a SPFS-based server 135

Verify the information and enter y if correct. If you enter n, thecommand is aborted.

Add command completed successfully.

6 Test the newly-added static route. Identify the pingeable IPaddress in the template.

A minor alarm under the NET class with static route appears.The alarm clears once the finalize static route configurationcommand executes. This alarm is not raised on single serveroperation.

7 Perform a ping test by entering:

ping <IP address in the template>traceroute <IP address in the template>

8 The ping test must pass. The traceroute command identifies thegateway IP in the template as first entry in the trace. If the pingtest fails, perform a ping test on the gateway IP address. Contacta network administrator for support.

Once the ping and traceroute tests pass, repeat step a, ifapplicable for the next static route or proceed to step 7.

9 Ensure there are no unexpected alarms raised or no SWACToccurred. If not, investigate if the new alarm or SWACT is dueto the newly-added route. When all static routes pass testing,proceed with finalizing the static route configuration.

ATTENTION*SPFS381 Mate file /etc/static-route.cfg out ofsyncStatic route configuration in progress on activenodecbm850=zngds1gb;NODE-zngdslgb-unit0;CLASS-NET;NETTYPE-staticrouteFri Jan 31 16:34:05 2007

WARNINGThis procedure is not complete until the static routeconfiguration is finalized and executed.

--End--

Performing a delete static route(s) on a SPFS-based serverThis section shows the user how to delete static route(s) on a SPFS-basedserver.


NN20000-316 05.02 28 July 2010

.


PrerequisitesWARNINGStatic route provisioning should not be performed under thefollowing conditions:



• For CBM users, refer to the following prerequisites:

Prerequisites for Core and Billing Manager 850





• See "Logging in to the CBM," in Core and Billing Manager 850 Securityand Administration for CDMA, (NN20000-320).

Procedure steps

Step Action

1 At your workstation, from the command line type:

cli




5 Enter the number next to delete_static_route to delete a staticroute. Abort this command by typingabort or answering n atthe confirmation prompt field.

Example response (host):

=== Executing "delete_static_route"

Content of the provisioned/added static route(s) file (table canbe empty)


NN20000-316 05.02 28 July 2010

.

Procedure steps 137

Identify and enter the index that matches the entry in thetemplate.

Verify the information and enter y if correct. If you enter n, thecommand is aborted.Configuration file update successfully.Command completed successfully.

=== "delete_static_route" execution completed

6 Test the newly-deleted static route. Identify the pingeable IPaddress in the template.

A minor alarm under the NET class with staticroute appears. Thealarm clears once the finalize static route configuration commandexecutes. This alarm is not raised on single server operation.



8 The ping test must fail. The traceroute command identifies thedefault gateway IP as first entry in the list.

Note: The default gateway may also be identified by enteringthe command:cat /etc/defaultrouter

Once the ping and traceroute tests times out, repeat step a, ifapplicable for the next static route or proceed to step 7.

9 Ensure there are no unexpected alarms are raised or no SWACToccurred. If not, investigate if the new alarm or SWACT is due tothe newly-added route. When all static routes test, proceed withfinalizing the static route configuration.


NN20000-316 05.02 28 July 2010

.



WARNINGThis procedure is not complete until the static routeconfiguration is finalized and executed. The minorNET class with static route alarm will be cleared bythe finalize static route command.

--End--

Performing a modify static route(s) on a SPFS-based serverAfter completing this section, the user will know how to modify statusroute(s) on a SPFS-based server.

PrerequisitesWARNINGStatic route provisioning should not be performed under thefollowing conditions:



WARNINGIf the template listed in the Application section of this procedureis not completed, STOP and contact your network administrator.Failing to do so could lead to a network outage. Query thesystem to ensure there are no network alarms reported.Resolve any network alarms, before you continue with thisprovisioning.






NN20000-316 05.02 28 July 2010

.

Procedure steps 139

Procedure steps

Step Action


cli


X - exit

select -



5 Select the number next to modify_static_route to modify aprovisioned static route. Abort this command by abort oranswering n at the confirmation prompt.

Example response:

== Executing "modify_static_route"

Content of the provisioned/added static route(s) file (table canbe empty),

Identify and enter the index that matches the entry in thetemplate.Enter gateway IP address[47.135.214.1]:

Enter the new gateway IP address supplied in the template.

Verify the information and enter y if correct. If you enter n, thecommand is aborted.

Configuration file updated successfully.Modify completed successfully.

=== "modify_static_route" execution completed


NN20000-316 05.02 28 July 2010

.


6 Test the newly-modified static route. Identify the pingeable IP inthe template.

A minor alarm under the NET class with staticroute appears. Thealarm clears once the finalize static route configuration commandexecutes. This alarm is not raised on single server operation.



Note: The default gateway may also be identified by enteringthe command:cat /etc/defaultrouter

Once the ping and traceroute tests pass, repeat step a, ifapplicable for the next static route or proceed to step 7.

8 The ping test must pass. The traceroute command identifies themodified gateway IP as the first entry in the trace list. If the pingtest fails, perform a ping test on the gateway IP address. Contacta network administrator for support.

9 Ensure there are no unexpected alarms are raised or no SWACToccurred. If not, investigate if the new alarm or SWACT is dueto the newly-added route. When all static routes pass testing,proceed with finalizing the static route configuration.


WARNINGThis procedure is not complete until the static routeconfiguration is finalized and executed. The minorNET class with static route alarm will be cleared bythe finalize static route command.

--End--

Performing a finalize static route(s) configuration on a SPFS-basedserver

This section shows the user how to finalize static route(s) configuration ona SPFS-based server.


NN20000-316 05.02 28 July 2010

.

Procedure steps 141


actions.




Procedure steps

Step Action


cli




5 Select the number next to finalize_stat_rte_confg to finalize astatic route configuration.

Example response (HA cluster):

=== Executing "finalize_static_route"Removing all user defined routes on mate routing table.Updating configuration file on mate.Adding all user defined routes on mate routing table.Finalize configuration completed successfully.

Example response (single server):

=== Executing "finalize_static_route"Finalize configuration completed successfully.

=== "finalize_static_route" execution completed

6 For servers CBM 850 or MG9KEM, perform a full systembackup. For other servers, perform only a critical data backupinstead of the full system backup.

7 Return to the invoking procedure or end of procedure.

--End--


NN20000-316 05.02 28 July 2010

.


WARNINGIf the template listed in the Application section of this procedureis not completed, STOP and contact your network administrator.Failing to do so could lead to a network outage. Query thesystem to ensure there are no network alarms reported.Resolve any network alarms, before you continue with thisprovisioning.

Recovering from a bad static route configurationThis section shows the user how to recover from a bad static routeconfiguration.


actions.




Procedure stepsThis recovery procedure may be required when the administratorlooses access to the system during provisioning. The following task flowillustrates guidelines to follow while performing recovery procedures.


NN20000-316 05.02 28 July 2010

.

Procedure steps 143

Step Action

1 At your workstation, to recover from a SWACT during a staticroute provisioning, investigate if the SWACT was due tosome networking issue. If not, execute “Performing a finalizestatic route(s) configuration on a SPFS-based server” (page140) from the newly active node. After you know the cause ofthe SWACT, contact a network administrator if the event wascaused by the static route. Reverse any changes using theCLI as indicated in the procedure on the formally active node.Return to “Performing an add static route(s) on a SPFS-basedserver” (page 133), “Performing a delete static route(s) on aSPFS-based server” (page 135), or “Performing a modify staticroute(s) on a SPFS-based server” (page 138) procedure andretry the provisioning. If another SWACT occurs, contact anetwork administrator.

2 For a dual server system:

3 If you lost access to the system, log on to the inactive node.

From the inactive node, SSH to the active cluster using theprivate IP alias either unit0-priv0 or unit1-priv0. After you accessthe active unit command prompt, delete the incorrect staticroute number following “Performing a delete static route(s)on a SPFS-based server” (page 135). After deleting a staticroute, make sure the active node is accessible. If not, contacta network administrator. After you restore the access to theactive node, log off from the inactive, mated node. Log on to the


NN20000-316 05.02 28 July 2010

.


active node and complete the finalize operation. The delete andrecovery operation is completed.

4 If the mated node is not accessible, you can also use the singleserver logon approach listed in step 3. Log on to the activenode console. For more information, see “Logging in to anSPFS-based server” (page 145).

5 On a single server:

If the server is no longer accessible, log on to the system usingthe console port.

After you access the active unit command prompt, delete theincorrect static route following the “Performing a delete staticroute(s) on a SPFS-based server” (page 135) procedure. Runthe finalize command once. The delete and recovery operationis completed.

ATTENTIONAfter deleting a static route, make sure the active node is accessible.If not, contact a network administrator. After you restore access to theactive node, log off from the console. Log on using the active nodeand complete the finalize operation.

--End--


NN20000-316 05.02 28 July 2010

.

Procedure steps 145

Logging in to an SPFS-based server

Use this procedure to log into a Server Platform Foundation Software(SPFS) server. This procedures provides the steps to establish a loginsession using SSH, which is secure, or Telnet, which is not secure.

Some tasks will require that you log in to the server through the console(port A) using the root user ID and password.

Prerequisites• You have the IP address or host name of the server.

In a two-server configuration, you need the physical IP address of theactive or inactive server.

• You have a valid user ID and password.

• You have root user privileges, if required.

• If the console has not been started, the ILOM login prompt appears.For the first connection attempt to log on to the T5220 server throughthe console, you must know the ILOM root password.


Procedure stepsPerform the steps under one of the following headings to complete thisprocedure.

• “Logging in using SSH” (page 145)

• “Logging in using Telnet” (page 147)

• “Logging in through the console” (page 148)

Logging in using SSH

Step Action

1 At your workstation establish an SSH session.

If you have access to a workstation which supports the SSHcommand (Linux, for example) then go to the next step.

Otherwise, connect to the server using an SSH client andproceed to step 3.


NN20000-316 05.02 28 July 2010

.


2 Establish an SSH session to the server by typing

> ssh -l <user_id> <server>


If you receive Then

a message indicating a hostauthentication issue anda request to continue theconnection

go to step 4.

a prompt for a password go to step 5.

4

ATTENTIONThe prompt indicates SSH is verifying whether the server is a trustedhost for the workstation. SSH performs the verification the first timeSSH is run on a workstation.

Continue the connection by typing

yes

and press Enter.

5 Enter the password for root or your user ID and press Enter.


If your server is a Then

one-server configuration go to step 10.

two-server configuration go to step 7.

7 Ensure you are on the correct server by typing

ubmstat

and press Enter.


If you need to be on the Then

active server and the response isClusterIndicatorSTBY

go to step 9.

inactive server and the response isClusterIndicatorACT

go to step 9.

active server and the response isClusterIndicatorACT

go to step 10.

inactive server and the response isClusterIndicatorSTBY

step 10.

9 You are logged in to the wrong server. Return to step 1 to log into the other server.


NN20000-316 05.02 28 July 2010

.

Procedure steps 147

10 If applicable, return to the high-level task or procedure thatdirected you to this procedure.

--End--

Logging in using Telnet

Step Action

1 At your workstation establish a Telnet session to the server bytyping

telnet <server>

and press Enter.

2 When prompted, enter your userid.

ATTENTIONYou cannot log in using the root userid at this step.

3 When prompted, enter your password.


If Then

you need to log in as root go to step 5.

otherwise go to step 7.

5 Change to the root user by typing

su -

and press Enter.





two-server configuration go to step 8.


ubmstat

and press Enter.




go to step 10.


NN20000-316 05.02 28 July 2010

.




go to step 10.


go to step 11.


go to step 11.

10 You are logged in to the wrong server. Log out of this server andreturn to step 1 to log in to the other server.

11 You have completed this procedure.If applicable, return to the high-level task or procedure thatdirected you to this procedure.

--End--

Logging in through the console

Step Action

1 At the console connected to the server log in to the serverthrough the console (port A).

2 Select your next step.

• If you are logging on to a T5220 server, go to the next step.

• If you are logging on to a Netra 240 server, go to step 8.

3 Select your step:

If Then

the login prompt is <systemname> login:

go to step 4.

the login prompt is -> go to step 6.

4 If you are logging on to a T5220 server, enter the root user ID.

5 Enter the ILOM root password.

6 To start the console, enter start /SP/console.

7 At the prompt, enter Y.

8 Select your step:


NN20000-316 05.02 28 July 2010

.

Procedure steps 149

If Then

The prompt is <hostname>console login:

go to step 9.

The prompt is #, <hostname>:/>, or <hostname>-unit[0|1](active|inactive):/>,

go to step 10.

9 Enter the required UNIX console username and password.




two-server configuration go to the next step.


ubmstat

and press Enter.

In a two-server configuration, log in to the active or inactiveserver as required.




go to step 13.


go to step 13.


go to step 14.


go to step 14.

13 You are logged in to the wrong server. Log out of this server andreturn to step 1 to log in to the other server.

14 If applicable, return to the high-level task or procedure thatdirected you to this procedure.

--End--


NN20000-316 05.02 28 July 2010

.



<server> The IP address or host name of the SPFS-based server, orthe physical IP address of the active or inactive server asrequired, in a two-server configuration.

<user_id> The root or your user ID.


NN20000-316 05.02 28 July 2010

.


Configuring OSS and application services

Use this procedure to configure OSS and Application Svcs.

Prerequisites• You have root user permission.


Procedure steps

Step Action


2 From the command line prompt, access the configuration level ofthe cbm maintenance interface, type:

cbmmtc config

3 From the maintenance window prompt, type the followingcommand to select OSS and Application Svcs:

Select <n>

4 From the maintenance window prompt, type the followingcommand to configure OSS and Application Svcs:

config

This configures OSS and Application Svcs.

--End--


<n> The number of the menu item youwant to select.


NN20000-316 05.02 28 July 2010

.


Configuring OSS communications services

Use this procedure to add OSS communication services (Comms Svcs).

Prerequisites• You have root user permission.

• You have four core users with unrestricted privileges on the core,which allows them to modify any table or execute any command on thecore. This is needed for the DDMS application to send commands tothe core. These users must already be permitted on the core and youmust use the same user names and passwords in this procedure.

For more information about how to log in to the CBM as an authorizeduser, how to request a nonrestricted shell access, or how todisplay actions a role group is authorized to perform, see CBM850Administration and Security, (NN20000-320).

Procedure steps

Step Action


2 From the command line prompt, access the configuration level ofthe cbm maintenance interface, type:

cbmmtc config

3 From the maintenance window prompt, type the followingcommand to select OSS Comms Svcs:

Select <n>

4 From the maintenance window prompt type the followingcommand:

config

The options to add DDMS logroute configuration appear.

5 To add DDMS logroute configuration, press Enter.

The Logroute Main Menu appears.


If Then

you want to configure DDMS logroute configuration

go to the next step.

you do not want to configureDDMS log route configuration

go to step 20.


NN20000-316 05.02 28 July 2010

.

Procedure steps 153

7 Type the number for the Device List menu item.

8 Type the number for the Add Device menu item.

9 Select the number for the Add File Device menu item.

10 At the prompt, type the file name. For example,

Example/cbmdata/00/data/logs/ossaps/ossapslog

11 At the prompt, type the format type.

ExampleSTD

12 At the prompt, set the Ecore option.

If Then

you want to turn Ecore on type on.

you want to turn Ecore off type off.

13 At the prompt, select to add or delete logs.

If Then

you want to add logs type a.

you want to delete logs type d.

14 At the prompt, type the log identifier.

ExampleDDMS

15 At the prompt, type N to stop adding more Logrouting Details.

16 Type Y to save the device details

17 At the Save data completed prompt, press Enter to continue.

18 To quit the Add Device menu, type the number for Return toDevice List Menu menu item.

19 To quit the Device List Menu, type the number for Return toMain Menu menu item.

20 To quit Logroute Main Menu, type the number for Quit Logroutemenu item.

The CM User Setup menu appears. Use this menu to configurethe core Telnet users used by DDMS to log in to the core.

21 To display users who are already configured, type the numberfor Display users (ID) menu item.



NN20000-316 05.02 28 July 2010

.


If Then

no DDMS users are configured,and you need to add the users

type the number for the Adduser option and provide the username and password. These arethe same values given on thecore.

you want to delete a DDMS coreuser

type the number for the Deleteuser (by ID) option and enter theuser ID of the user to delete.

you want to update the passwordof a user already configured

type the number for the Updatepasswd (by ID) option andenter the user ID and the newpassword.

23 To go to the DDMS Clients Configuration menu, type thenumber for the Quit menu option.

24 To list the client IP (SESM), type the number for the Listexisting client menu item.

25 Select your next step

If Then

the IP client is not configured go to the next step.

you need to delete an IP client(only one SESM IP is allowed inthe client configuration)

go to step 28.

26 To add the new client (SESM IP address), type the number forthe Add new client menu item.

Only one SESM IP is allowed in the client configuration.

27 Type the IP address of the DDMS client and go to step 30.

ExampleEnter the IP address of the DDMS client ordone: 12.123.111.000

28 To delete an IP client, type the number for the Remove existingclient menu item.

29 Enter the IP address of the DDMS client.

ExampleEnter the IP address of the DDMS client toremove: 12.123.111.000


NN20000-316 05.02 28 July 2010

.


30 Type the number for the Quit menu option to exit from theDDMS Clients Configuration menu.

--End--


<n> The number of the menu item you wantto select.


NN20000-316 05.02 28 July 2010

.



NN20000-316 05.02 28 July 2010

.

CDMA

Core and Billing Manager 850 Configuration Management forCDMARelease: MTX18Publication: NN20000-316Document revision: 05.02Document release date: 28 July 2010

© Ericsson AB 2010. All rights reserved. No part of this document may be reproduced in any form without the written permissionof the copyright owner.

The contents of this document are subject to revision without notice due to continued progress in methodology, design andmanufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

All trademarks are the property of their respective owners.

NN20000-316 05.02 MTX18 Cdma Configuration

Documents

cdma core

cbm li proxy application

cdma release

cdma nn20000

omdd application

billing manager

application services

lan interface