k06 en4442en00en 0001 Assistant - Papagayo System h4000 ver 5/k06...© 2007 Siemens AG 1 Siemens Assistant 4000 ... TSDM is designed for HiPath 4000 systems with TDM OpenStage phones

Siemens

Assistant 4000

1 TDM Software Download Manager (TSDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 Overview of the TSDM Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2 Starting the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3 TSDM Main Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.4 Software distribution: D-Channel Download and B-Channel Replication . . . . . . . . . . . 51.5 AMO Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.6 Help System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Manual and Scheduled Software Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1 Device List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2 Device List Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2.1 Column Visibility Selection for Device List . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2.2 Sorting Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2.3 Display Filtering by Model Type, Group or Job . . . . . . . . . . . . . . . . . . . . . . . 112.2.4 Refresh List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2.5 Create Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.2.6 Manage Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2.7 Manage Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2.8 Upload File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2.9 Manage Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.2.10 Column Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.2.11 Export CSV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.1 SNMP-Activation on HiPath 4000 V4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.2 SNMP-Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.3 MIB-Browser configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .General entries: 20

EN0000DE00EN_0000© 2007 Siemens AG

1

2

Siemens

3.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Values: 203.3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Agents: 20

3.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting SNMP-discovery 203.5 Query MIB-Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.6 Trap receiver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.6.1 Settings in the HiPath 4000 V4 for the Trap receiver . . . . . . . . . . . . . . . . . . 213.6.1.1 CPTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.6.1.2 AFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.6.1.3 UW7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4 Usage of a Hotfixes in the HiPath V4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.1 Download of the hotfixes from the SWS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.2 Transfer of the Hotfix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.3 Activation of the hotfix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28


TSDM Siemens

1 TDM Software Download Manager (TSDM)

1.1 Overview of the TSDM Application

TSDM is an abbreviation for TDM Software Download Manager. This application enables soft-ware updates on TDM (Time Division Multiplex) variants of OpenStage phones and the Up0 Extender on HiPath 4000 systems. In addition, a customer logo can be delivered to OpenStage devices supporting this feature, and trace and exception log data can be uploaded from the OpenStage device to the switch.

A separate application is available for HiPath 3000 to update OpenStage software on those systems.

OpenStage devices can also be updated by using the ’UniProg’ application. However, this re-quires a special adapter box, and the device must be physically removed from the system and updated manually, one at a time. TSDM enables remote and uninterrupted software updates for OpenStage devices.

Figure 1-1 Sample switch setup with OpenStage devices

> Note: TSDM is designed for HiPath 4000 systems with TDM OpenStage phones and is hence of little or no use on a system that does not contain such devices. Another solution is to use the Deployment Service DLS to update the software on the IP vari-ants of OpenStage devices. In this document, all further references to an ’Open-Stage device’ will assume that this device is of the TDM variant.


3

4

TSDMSiemens

There are two main components to TSDM. One is the JAVA client, which provides the interface and is available in a browser window on the HiPath4000 Assistant, and the other is a server process, which runs under UnixWare on the HiPath4000.

1.2 Starting the Application

Only one client can run TSDM at a time; if another user attempts to start TSDM at the same time, this will not be permitted.

The TSDM application can be started via the HiPath 4000 Assistant menu:

● Select Software Management -> TSDM

The TSDM main page is displayed.

It is possible to quit the TSDM client and have the server process continue if there are ongoing software transfers. A single TSDM client can reconnect to the TSDM server at any time.

The server will continue running while a client is connected or until all running jobs have been completed. If a job is scheduled for a future time, the TSDM server will start up when that job is scheduled and subsequently quit when the job has completed.

1.3 TSDM Main Page

The navigation pane on the left side of the main page shows the following four sections:

● Manual & Scheduled

Download phone software and customer logos to OpenStage devices.

The Manual and Scheduled Software Transfer page is displayed in the right pane by de-fault when TSDM is started.

● Trace

[This entry reserved for future use; the feature is not yet implemented.]

> TSDM supports OpenStage devices connected to SLMOP and SLMO24 (SLMO2) boards.The SLMOP and SLMO24 boards can be on HHS shelves or AP shelves. TSDM will handle any type of hardware configuration.Existing OptiSets and OptiPoints can also connected to the SLMOP and SLMO24 boards used by OpenStage devices.


TSDM Siemens

The Trace option will work in a similar manner to the Exception Log option (see below), except that this feature will only be available on OpenStage60 devices. The OpenStage20 and OpenStage40 devices do not have any tracing capabilities.

● Exception Log

[This entry reserved for future use; the feature is not yet implemented.]

The Exception Log option will be used to retrieve an exception log from an OpenStage de-vice. This will be done as an upload from the phone to the HP4K switch. Users will be able to transfer the exception log to their client PCs as well.

● Information

Contains general information, displayed in a text window, about the currently running TSDM application.

To start one of the components, click on the item in the left pane. The controls for the function will be displayed in the right pane of the main page.

1.4 Software distribution: D-Channel Download and B-Channel Replication

TSDM uses two methods for software distribution. These are:

● Software download via the D-Channel and

● Software replication via the B-Channel.

Software Download via the D-Channel

The first method involves an initial transfer of a software image to a device via the D-Channel. The software image is stored on the hard disk of the HiPath 4000 switch. This download pro-cess takes about 10 minutes for an OpenStage20 or OpenStage40 device. The OpenStage de-vice can be used normally during the transfer. Once a software image has been transferred, the device must be restarted in order to activate that software. TSDM will automatically restart the device if it is in an idle state. The restart process only takes a few seconds.

Software Replication via the B-Channel

The second method for software replication is via the B-Channel. Once an initial device has been updated via the D-Channel, the new software can then be replicated from that device to another. This process is faster than the D-Channel download (approximately 6 minutes for OpenStage20 and OpenStage40). Furthermore, subsequent replication steps can deliver the software version to many phone in a few steps.

The following diagram shows how 16 devices can be updated in four steps:


5

6

TSDMSiemens

Figure 1-2 Software deployment process with replication

The B-Channel replication process also eliminates overhead from the processor of the HiPath 4000 system, since the phones update each another. The TSDM application has to only initial-ize the B-Channel transfer and then periodically check on the progress of the update.

Limitations

Only four D-Channels are available concurrently for a software update via TSDM. Only one D-Channel download is possible at a time per SLMO board. There is no fixed upper limit on B-Channels. Hundreds of B-Channel updates are possible at once, depending on the system configuration.

The limitation on B-Channel copies is that it is only possible to make a B-Channel copy be-tween HHS shelves (Line/Trunk Unit (LTU) 1 to 16) and within a single AP shelf (LTU 17 to 99). It is not possible to perform a B-Channel replication between AP shelves or between an AP shelf and an HHS shelf. The TSDM application handles situations where there are separate AP shelves by first initiating a D-Channel download to each AP shelf and then replicating the soft-ware via the B-Channel within the AP shelf. Likewise, a D-Channel download is also made first to one HHS shelf and then replicated from there to any other HHS shelf.


TSDM Siemens

1.5 AMO Configuration

For TSDM to work efficiently, it is important that OpenStage devices be configured correctly.

To ensure that the B-Channel replication of software from phone to phone works properly, the OpenStage devices must be configured correctly with the AMO SBCSU or in CM (Configura-tion Management).

The DVCFIG (Device Configuration) field should be set to VIRTDTE, and the DPROT (Protocol variant for Date Device on S0 Bus) should be set to SBDSS1.

If this configuration has not been set, it is possible to change the configuration for a given sub-scriber and to then activate the change by using the following two commands:

ADD-SBCSU:STNO=8112,OPT=SVC,DVCFIG=VIRTDTE,DPROT=SBDSS1;

ACT-DSSU:ONTYPE=ANL,TYPE=STNO,STNO=8112;

TSDM can also use B-Channel replication if the DVCFIG field is configured with DTE instead of VIRTDTE, but this can only be done if the customer has sufficient licenses for DTE. The con-figuration with VIRTDTE does not require any additional licenses.

For TSDM to function, an ACL-C link needs to be configured. This is done automatically during the installation of TSDM; however, it is possible to subsequently delete this configuration. The following AMO sequence can be used to correctly configure the ACL-C link for TSDM:

– cha-funct:slang=eng; ADD-CPTP:DPCON,93,HU_INTER,192.0.2.5; ADD-CPTP:APPL,95,TSDM_APP,HU_INTER,TSDM_SF,YES,102,5095, HUI_S_0095,HUI_D_0095; ADD-XAPPL:95,TSDM_SF,TSDM APPLICATION,,N; CHA-XAPPL:SUBAPPL,95,D23,ALL,; ADD-ACMSM:A1,95,ACLAPPL,TSDM_SF,TSDM_APP,HU_INTER,CB,SFTS-DM,Y,1020,1020; CHA-ACMSM:A1,95,PARAMETER,,N;

This ACL-C configuration for TSDM will not conflict with CAP if the guidelines in the CAP user manual have been followed.

1.6 Help System

The Help System contains generic Help Topics that describe the functionality of the individual features. To start the Help Topics, the user can click the "?" icon in the toolbar.


7

8

TSDMSiemens


Software Transfer Siemens

2 Manual and Scheduled Software Transfer

The Manual & Scheduled software transfer page is automatically loaded after TSDM is started and is displayed in the right pane of the TSDM main page.

It can also be selected with the following item in the left pane of the TSDM main page:

– Manual & Scheduled

The Manual & Scheduled software transfer page can be used for the following tasks:

● Update the software (firmware) on OpenStage devices and on the Up0 Extender for Open-Stage. This is done by downloading a software image from the HiPath 4000 system to the device. Furthermore, once a software image has been installed on a device, it can be rep-licated to another device under the control of the application.

● Customer logos can be downloaded to devices which support this feature (OpenStage40 and OpenStage60)

● Software images and customer logos can be uploaded from the user’s PC to the HiPath 4000 system. The user can also delete these files later from the HiPath 4000 system.

● Devices can be organized into groups, which are saved for future use. Various selection options can be used to choose the devices for a group.

● Data transfer jobs can be started immediately or scheduled for a specific time. These jobs can also be stopped at any time.

● Information about the OpenStage devices on the system can be viewed in a table. The ta-ble can also be filtered by model, group or job.

2.1 Device List

The main feature in the Manual and Scheduled Software Transfer screen is the Device List. The Device List is a table to display the OpenStage devices on the system. Using this list, users can select which devices are to be used for a data transfer and which devices they want to or-ganize into groups.

Each line in the table represents a device.

Each column in the table represents a separate piece of information about each device.

The number of columns in the table can be configured, and the content of the columns can be sorted and filtered (Device List Operations).

The information in each column represents the following:


9

10

Software TransferSiemens

Select

A checkbox can either be checked or unchecked. If the item is checked, it can be used to create a job or to be included in a group.

Subscriber

The subscriber number of the device. This field may not always contain a number in cases where the device was logged off with the mobility feature (autoset relocate).

Type

The type or model of the device. The possible values are OpenStage20, OpenStage40, OpenStage60 and Up0 Extender.

PEN

Port Equipment Number. This is the physical port where the device is connected to the system. TSDM uses the PEN as the main identifier for each device in the program’s logic. If the PEN is followed by a ’U’, the device a Up0 Extender, whereas ’S’ means that it is a slave.

Firmware

The firmware (or software) version of the currently running phone software

AssetID

Each device in the field has a unique ID called an AssetID. This can be used to identify a phys-ical device with certainty in the event the device is moved around the system. This column is turned off by default; however, it can be enabled at any time (see Column Selection).

Snapshot

Contains the snapshot of the device’s state at the time the table was generated or at the time when this cell was updated by the user. If the snapshot is deviceOOS (Out of Service), this may be because no physical device is connected to that line or because the device was logged off with the mobility autoset relocate feature.

Master/Slave

This field only contains information if the device is in a Master / Slave pair. A Up0 Extender is needed for a Master / Slave pair.



Status

If a device is being updated, then the status of the update is shown. This status is updated by 1% increments for a D-Channel download; a B-Channel download is updated periodically (ap-prox. every 15 seconds).

2.2 Device List Operations

The following operations for displaying the device list table are supported:

● Column Visibility Selection for Device List

● Sorting Columns

● Display Filtering by Model Type, Group or Job

2.2.1 Column Visibility Selection for Device List

In some cases, the user might not be interested in all of the information displayed in the device list. For this reason, it is also possible to select which columns should be visible. This can be managed with the Column Selection entry in the Options menu.

2.2.2 Sorting Columns

By default, the items in the device list are sorted by subscriber number. The table can be sorted by clicking on the column title.

A triangle appears on the right of the column title, indicating that the table is sorted by the nat-ural order for that column.

Clicking the column title again reverses the sorting order and the direction of the triangle in the column title.Finally, clicking on the column title for a third time undoes the sorting to the default state

2.2.3 Display Filtering by Model Type, Group or Job

The items in the Device List can be filtered by model type, group and job.

There are three radio buttons to select the filter for the Device List: Model, Group and Job.

> When TSDM is started for the first time on a HiPath 4000 system, it takes some time for the application to build an initial list of all the TDM OpenStage devices to be dis-played in the Device List. The amount of time required depends on the number of devices and the system configuration. The created list is subsequently saved for fu-ture use and for quick access, although the user can regenerate the list of Open-Stage devices at any time.


11

12


When TSDM is run for the first time, the only enabled option is for the Model type.

The default option is All OpenStage TDM, which is used to display all OpenStage devices and Up0 Extenders on the system; in other words, no filtering occurs.

The other types of filtering that are possible are "by group" and "by job". These options are dis-abled if no groups or jobs have been defined.

2.2.4 Refresh List

The configuration of an HP4K switch can change over time; OpenStage devices may be added or moved. The first time TSDM is run, a Device List is generated. This list is subsequently cached on disk for further use.

The Refresh List options can be used to completely or selectively regenerate the Device List.

The Refresh List option contains the following submenu:

The Submenu Items

Full Regeneration

On a switch with hundred or even thousands of subscribers, a full regeneration of devices can take several minutes. This is why the user is warned before taking such an action.

Regenerate List The entire Device List is completely regenerated. This option can be a lengthy process, since many commands must be run to determine the valid OpenStage devices on the switch. A dialog box comes up to confirm the "regenerate list" action.It might also be a good idea to select Clear Table in this submenu before running this option in order to clear the Device List table.

Regenerate Selected Regenerates the data for all of the selected devices in the Device List.

Regenerate Partial Regenerates the selected data fields for the selected devices in the Device List.

Update Snapshot Updates the snapshot column for all devices to show the current call state. This option executes quickly.

Load Cached List Loads the information cached about the Device List from disk. Clear Table can be optionally used before this action.

Clear Table Clears all of the data displayed in the Device List. This action does not delete the cached file on disk.

Info Shows the start time when the last Device List was regenerated.



The device list information is saved on disk for further reference. Some of the information in the table can be generated quickly, including the Type of device, Firmware, AssetID, and Snap-shot. Other information is generated via the AMO interface and is therefore slower, but up-to-date.

Regenerate Partial

The Regenerate Partial window appears on selecting the Regenerate Partial submenu item from the Refresh List option.

Any combination of Device List Items can be selected by checking the corresponding check-boxes beside the device list item (Subscriber, Type, Firmware, AssetID, Snapshot, Master/Slave, Status).

The Regenerate button starts the partial regeneration using the selected items and subscrib-ers.

By default, all items selected in the Device List are used in the regeneration. However, if the Select All Devices option is checked, then all the selected items for all devices will be regenerated.

The Close button closes the window.

2.2.5 Create Group

To create a new group:

1. Select the desired members of the group in the Device List.

Groups must have at least one member. It is not possible to create empty groups.

2. Then select Options -> Create Group.

The Group Name window is displayed.

3. Enter the name of the group into the provided text field.

Each group must have a unique group name. Duplicate group names will be rejected.

4. Press the Enter key or click the Create button to create this new group.

Clicking the Cancel button closes the window without further action.


13

14


2.2.6 Manage Groups

Once groups are created, it is necessary to manage the groups.

The Manage Groups menu item brings up the Manage Groups window with the Delete tab and the Rename tab.

The Delete Tab

The Delete tab shows a list of items containing all the defined groups.

A listed group can be highlighted by clicking on it.

<SHIFT>+click selects multiple contiguous groups.

<CTRL>+click adds or deselects one group at a time to or from a selection.

The Delete button deletes the selected groups.


The Rename Tab

The Rename tab allows the user to select a single group from a drop-down menu and to specify a new name for the group.

The Rename button changes the name of the selected group from the drop-down menu to the name entered in the New Name input field.

The new name of the group must be unique, i.e., must not be identical to another existing group.


2.2.7 Manage Jobs

Once a transfer has been started or scheduled, a job is created. Additional information about the current and pending jobs can be viewed by clicking on the Manage Jobs menu item of the Options menu. This brings up the Manage Jobs window with the Members tab and the Jobs tab.Figure 2-1

The Members Tab

The Members tab should be selected first.

The individual members belonging to a currently running job can be displayed on this tab.

All currently running jobs are listed and selectable in the drop-down menu under Select Job.



All members belonging to the selected job are listed in the table. A row in the table can be selected by clicking on it.

Clicking the Delete Member button deletes all selected members of the job.

Clicking the Close button closes the window.

The Jobs Tab

Figure 2-2

The Jobs tab shows a table containing all the stored information for that particular job:

A row in the jobs table is selected by clicking on it.

The Delete Job button deletes the entire job.

2.2.8 Upload File

Three submenus are available to upload software images and customer logos to the switch.

The Submenu Items

The three upload options are summarized below:

Job Name name given to the job by the user

Creation date and time when the job was created (time on the HP4K server)

Type kind of job - FIRMWARE (software image) or LOGO (customer logo)

Source name of file (or files) to be transferred, or PEN of device starting point

Start date and time when the job was or is to be started

State usually blank, but if there is a blocking point due to another job, then this is displayed

Members total number of devices belonging to the job

Firmware Brings up a file selection box. A software image firmware file should be selected in this box for the upload.

Customer Logo Brings up a file selection box. A customer logo should be selected in this box for the upload.

HTML Upload Opens a new browser window which allows both software images and customer logos to be uploaded. This option provides additional feedback about the status of an upload and can also be run sepa-rately from the main TSDM application.


15

16


Software Image Names

The name of a software image can be something like "tdm_wp1_opera_tdm_dld.bin". TSDM will handle the upload of this file and rename it to something meaningful, which shows the tar-get device type and the version of the software. The customer logo, on the other hand, will not be renamed - here the user should make sure that it has a meaningful name.

Customer Logo Requirements

The customer logo is supported on the OpenStage40 and OpenStage60 only.

The requirements for a customer logo on an OpenStage40 are as follows:

– BMP file

– 144 pixels (width) x 32 pixels (height)

– black and white (no gray scale!)

– uncompressed, 702 bytes in size

If the BMP file does not meet these criteria, it will be discarded by the device. If a BMP file is created in another application (other than Paint in MS Windows), then it is advisable to first open the BMP file in Paint and save it before sending it to TSDM as a customer logo.

The requirements for a customer logo on the OpenStage60 are more flexible:

– PNG file

– Max. 240 pixels (width) x 72 pixels (height); smaller sizes are allowed

– colored logos are allowed (not only black and white)

– JPEG and BMP support planned for later releases (check Release Notes)

To remove a customer logo from a phone, a completely blank (white) logo can be downloaded to the phone.

> The HTML upload option can be run from any client PC that has access to the HP4K Assistant. Even if TSDM is running on another PC, it is possible to use this page to upload customer logo and firmware files. The following path should be entered into the browser window (with the correct HP4K switch name substituted):

https://my.hp4kswitch.name/TSDM/cgi-bin/firmware.cgi



2.2.9 Manage Files

After software image firmware files and customer logos have been uploaded to the system, it is necessary to be able to manage these files.

The Manage Files item on the Options menu opens the Manage Download Files window with the Firmware tab and the Customer Logo tab.

The Firmware Tab

The Firmware tab contains a table showing all the stored firmware software images, along with the corresponding name, device type, and version number.

The rows in the table can be highlighted by clicking on them.

<SHIFT>+click selects multiple contiguous rows.

<CTRL>+click adds or deselects one row at a time to or from a selection.

The Delete button deletes all highlighted firmware files.

The Refresh button searches if any new firmware files have been uploaded to the system and refreshes the screen if required.


The Customer Logo Tab

The Customer Logo tab is similar to the Firmware tab, except that it contains a list of all cus-tomer logos stored on the switch.

The items in the list can be selected by clicking on them.

<SHIFT>+click selects multiple contiguous rows.

<CTRL>+click adds or deselects one customer logo at a time to or from a selection.

The Delete button deletes all highlighted customer logos.

The Refresh button checks to see if any new logo files have been uploaded to the system and refreshes the screen if required.


> The customer logos can be retrieved from the system via an FTP connection to the HiPath 4000 Assistant. All of the files are stored under the /var/tsdm/logoup-load directory. Expert Unix users can also copy and combine these files into a sin-gle archive via a command line interface. The firmware files can also be similarly copied back; these files are found in the directory /var/tsdm/fwupload.


17

18


2.2.10 Column Selection

The user might not always be interested in all the information shown in the device list. In such cases, it is possible to select which columns should be made visible by using the Column Se-lection option.

Selecting the Column Selection option brings up the window:

When the Column Visibility Selection window appears, each of the available columns in the Device List is listed under the Column Name column, and if this column is shown in the Device List, then the checkbox in the Select column is also checked.

The user can turn a column on or off by checking or unchecking the checkbox beside each of the column names and then clicking the Apply button.

The Reset button restores the selected columns to reflect the current state of the Device List.


2.2.11 Export CSV

The information contained in the device list can be saved to a comma-delimited file on the client PC. The Export CSV menu item on the Options menu brings up a Save Dialog box.

Here the user should enter the filename of the CSV file.

The CSV file can later be opened in a text editor or spreadsheet.


Title Siemens

3 SNMP

This is a step by step description on how the SNMP feature can be activated and tested with a MIB-browser:

3.1 SNMP-Activation on HiPath 4000 V4

SNMP Service is not automatically running on the Assistant. This feature must be enabled in:

Launchpad2 -> Base Administration -> Application Control -> "SNMP Service"

3.2 SNMP-Configuration

Trap end point and Community must be configured.

This is done with the SNMP Configurator, started under:

Launchpad2-> Diagnostics -> SNMP Configurator

Trap end point can be the ip-address of a PC with a MIB-browser

Community is the name under which read/write access for SNMP-queries are used. Normally the name "hipath" is configured here.

3.3 MIB-Browser configuration

The MIB's of the HiPath 4000 V4 must be loaded and the HiPath 4000 V4 must be configured in the MIB-browser. The 2 MIB files (hipath4000.mib and hp4khim.mib), which have to be im-ported, can be found on the HiPath 4000 V4 in the directory

/opt/ncc/mib

EN4442EN00EN_0001© 2007 Siemens AG

19

TitleSiemens

20

These 2 files should be stored on the PC under:

Program Files -> <Browser-Name> -> mibbrowser -> mibs

MIB-import: e.g. in the ireasoning MIB browser (licence is needed for this program!), it is done by selecting the menue File -> Load MIBs

HiPath 4000 V4 configuration in the MIB-Browser (ireasoning: Tools -> Options):

3.3.1 General entries

Trap Port: 162

Max Token Number: 16

3.3.2 Default Values

Agent Port:161

Agent Read Communiy:hipath

Agent Write Communiy:hipath

Agent SNMP Version:1

3.3.3 Agents

IP-Address of the HiPath 4000

All other entries are taken from the "Defaukt Values"-folder

3.4 Starting SNMP-discovery

If SNMP queries are started to the HiPath 4000 Assistant, the returned values are taken from the Database. Most of the data is coming from the RMX side, so an update of the Database is necessary especially for the HIM-data to be up to date.

An update of the data can be stated in the MIB-browser by activating a master discovery:

● Select the hicomDiscovTable in the hicomMib -> hicomDiscov tree

● perform a "Get Subtree" operation

● select "hicomDiscovStatus.1" in the Result Table Window of the MIB browser


Title Siemens

● perform a "Set" operation and enter "13" as Value for Master Discovery"

● perform a "Get" operation to see, if Master Discovery is running (value "masterBusy" is dis-played) or has finished already with value "masterDone"

3.5 Query MIB-Data

MIB-Queries can be done by selecting a Table or single entry from the loaded MIB's and per-form any "Get" option:

● Get (show the value of the first entry)

● Get Next(show the value of the next entry of a table)

● Get Subtree(show values for all entries of a table)

● Walk (go trough the whole MIB and show all entries)

3.6 Trap receiver

With the MIB-browser it is possible to receive traps from the SNMP agents.

Traps are sent by the SNMP-agents on the HiPath 4000 if:

● an agent is started or stopped or an error occured

● to deliver alarm and error messages from the RMX

3.6.1 Settings in the HiPath 4000 V4 for the Trap receiver

3.6.1.1 CPTP

ADD-CPTP:DPCON,6,"DVANCCFM","192.0.2.5";

ADD-CPTP:APPL,6,"FAMAFR3","DVANCCFM","FM3",YES,102,102,"FM-HIC","FM-DMS";

3.6.1.2 AFR

ACTIVATE-AFR: AFR3 , LDU ;ACTIVATE-AFR: AFR3 , PROT ;ADD-AFR : AFR3 , LDU , 8 , 99 , 99 , 5 , 50 , 05-00 , 1 , 2 , 15 , 0 ;ADD-AFR : AFR3,TAB,"F5388",OUTSERV ,"F5389",INSERV ,1,10;


21

TitleSiemens

22

ADD-AFR : AFR3,TAB,"F5385",OUTSERV ,"F5404",INSERV ,1,10;ADD-AFR : AFR3,TAB,"F5385",OUTSERV ,"F5402",INSERV ,1,10;ADD-AFR : AFR3,TAB,"F5385",NOACT ,"F5426",NOACT ,1, 0;ADD-AFR : AFR3,TAB,"F5420",OUTSERV ,"F5402",INSERV ,1,10;ADD-AFR : AFR3,TAB,"F5420",NOACT ,"F5426",NOACT ,1, 0;ADD-AFR : AFR3,TAB,"F5424",OUTSERV ,"F5425",INSERV ,1,10;ADD-AFR : AFR3,TAB,"F5392",OUTSERV ,"F5393",INSERV ,1,10;ADD-AFR : AFR3,TAB,"F5398",OUTSERV ,"F5404",INSERV ,1,10;ADD-AFR : AFR3,TAB,"F5399",OUTSERV ,"F5400",INSERV ,1,10;AMO-AFR -111 AUTOMATIC FAULT REPORT

3.6.1.3 UW7

Im UW7 am Assistant muß der FM_AER_Daemon laufen, wenn nicht, starten mit

procadmin -s -g FM_SNMP


Hotfix Siemens

4 Usage of a Hotfixes in the HiPath V4

4.1 Download of the hotfixes from the SWS server

To enable the down loading of system software, applications and hotfixes a Intranet site can be used.

Username: e-mail address

Password: given by Brussels


23

24

HotfixSiemens


Hotfix Siemens

4.2 Transfer of the Hotfix

The hotfix will be transfered with File Transfer utility of the Expert Mode.

● Expert Mode --> HiPath 4000 --> HiPath 4000 Expert Access.


25

26

HotfixSiemens


Hotfix Siemens

● Select directory /var/hf and copy the hotfix from your fileserver to the HiPath

With a right mouse button click „Copy from“ in this field


27

28

HotfixSiemens

4.3 Activation of the hotfix

The activation of the hotfix will be done in the directory:

● Software Management --> Software Activation

If the activation was successful you will get a message.


Documents

k06 en4442en00en 0001 Assistant - Papagayo System h4000 ver 5/k06...© 2007 Siemens AG 1 Siemens Assistant 4000 ... TSDM is designed for HiPath 4000 systems with TDM OpenStage phones