Service, SRS Config. in SOM 5 5.5 VB30 38 39 40 41 36 CSTD CT02-023.805.02 CT00-000.843.08

Common CT
Configuration
Service
SRS Config. in SOM/5/5.5 VB30/38/39/40/41/36
Valid for:
SOMARIS/5 VB30/38/39/40/41
SOMARIS/7 VA10/11/20
SOMARIS/5.5 VB36
Answers for life.

2 Document Version / Disclaimer / Copyright
Document Version
Siemens reserves the right to change its products and services at any time.
In addition, manuals are subject to change without notice. The hardcopy documents cor‐
respond to the version at the time of system delivery and/or printout. Versions to hard‐
copy documentation are not automatically distributed.
Please contact your local Siemens office to order a current version or refer to our website
http://www.healthcare.siemens.com.
Disclaimer
Siemens provides this documentation “as is” without the assumption of any liability under
any theory of law.
The content described herein requires superior understanding of our equipment and may
only be performed by qualified personnel who are specially trained for such installation
and/or service.
Copyright
“© Siemens, 2006” refers to the copyright of a Siemens entity such as:
Siemens Healthcare GmbH - Germany
Siemens Aktiengesellschaft - Germany
Siemens Shenzhen Magnetic Resonance Ltd. - China
Siemens Shanghai Medical Equipment Ltd. - China
Siemens Medical Solutions USA Inc. - USA
Siemens Healthcare Diagnostics Inc. - USA and/or
Siemens Healthcare Diagnostics Products GmbH - Germany
Common CT CT00-000.843.08.07.02 Page 2 of 57 © Siemens, 2006

06.13 H CX CS SD CR-CT
Table of Contents 3
1 General Information 5
1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1.1 Document overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1.2 Configuration Expectations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.1.3 Supported SRS infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1.4 Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.1.5 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 SRS Configuration 9
2.1 SRS configuration in Somaris (Navigator = syngo Acquisition Workplace) . . 9

2.1.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1.2 SRS configuration part 1 - SRS configurations. . . . . . . . . . . . . . . . 10
2.1.3 SRS configuration part 2 - SRS Function Check . . . . . . . . . . . . . . . 13
2.1.4 SRS configuration part 3 - System Management configuration . . 14
2.1.5 SRS configuration part 4 - Somatom LifeNet Contacts . . . . . . . . . 17
2.2 SRS configuration in Somaris (Wizard = syngo CT Workplace) . . . . . . . . . . . 20
2.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.2.2 SRS configuration part 1 - SRS configurations. . . . . . . . . . . . . . . . 20
2.2.3 SRS configuration part 2 - SRS Function Check . . . . . . . . . . . . . . . 20
2.2.4 SRS configuration part 3 - System Management configuration . . 20
2.2.5 SRS configuration part 4 - Somatom LifeNet Contacts . . . . . . . . . 20
2.3 Checking the SRS Services (syngo Aquisition and CT workplaces) . . . . . . . . 22
2.3.1 Remote Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3.2 Somatom LifeNet Extranet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3.3 CS Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4 SRS Configuration with Outside NAT - Optional (NAT = Network Address 26
Translation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4.2 Adding Outside NAT information to SRS Settings for e.g. Europe 26
2.5 Auto reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.5.1 Activate auto report Mon_HQ (syngo Aquisition and CT Work‐ 28
places) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6 Remote Application Support in Som/5 VB40 (syngo Acquisition and CT 30
workplaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.6.2 Legal requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.6.3 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.6.4 Enable/Disable Remote Application Support . . . . . . . . . . . . . . . . . 30
2.6.5 Starting a Remote Application Support session . . . . . . . . . . . . . . 30
2.7 EPS - Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.7.1 Enable/Disable Utilization Management . . . . . . . . . . . . . . . . . . . . 32
2.7.2 Enable/Disable Virus Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3 SRS Troubleshooting 33
3.1 SRS Troubleshooting description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.1.1 Error at SRS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.1.2 Error at SRS Function Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
© Siemens, 2006 CT00-000.843.08.07.02 Page 3 of 57 Common CT

4 Table of Contents
3.1.3 Troubleshooting System Management - HP OpenView (VB40, 37

VB38B_SP4, VB36). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.4 Troubleshooting System Management - CA Unicenter 38
(Somaris/5 VB30/38/39) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.5 Error at SRS configuration - Internal software errors . . . . . . . . . . 42
3.1.6 Corrective action for internal software errors . . . . . . . . . . . . . . . . 44
3.1.7 Port Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.1.8 Uninstalling and reinstalling the System Management agent . . . 46
4 Helpful hints 48
4.1 Configuration of the SRS gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

4.2 System Management information (CA Unicenter - VB30/38/39) . . . . . . . . . 50
4.2.1 How to deactivate or deinstall System Management (CA Unicen‐ 50
ter). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 System Management backup/restore strategy . . . . . . . . . . . . . . . 50
4.2.3 CA Unicenter pop-ups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.3 System Management information (HP OpenView) . . . . . . . . . . . . . . . . . . . . 52
4.3.1 How to deactivate System Management . . . . . . . . . . . . . . . . . . . 52
4.3.2 How to deinstall System Management . . . . . . . . . . . . . . . . . . . . 52
4.3.3 System Management backup/restore strategy . . . . . . . . . . . . . . . 52
4.3.4 HP pop-ups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.4 SRS Function Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.4.1 Functional description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5 Changes to Previous Version 55
6 List of Hazard IDs 56

General Information 1 5
1.1 General
This chapter provides helpful information regarding SRS in Somaris/5 VB30/38/39/40/41
and Somaris/5.5 VB36. It includes a document overview and describes the configuration
expectations from the point of view of headquarters. Instructions for configuring SRS are
given in the next chapter ( SRS Configuration / Page 9).
For Som/5 version VB38B_SP4 and versions VB40 and higher, and Som/5.5 versions VB36
 and higher, the System Management configuration is part of the SRS configuration page.
As a result, the configuration instructions differ slightly from previous versions. The sec‐
tion “VB40, VB38B_SP4 and VB36 changes” lists the changes.
 The System Management software HP OpenView uses 2 new ports (12061, 13001) com‐
pared to CA Unicenter. For details, refer to section Ports on next page.
The CS strategy is to replace the CA Unicenter System Management software with HP

 OpenView within the installed base. The replacement of CA Unicenter commenced with
software version VB38B_SP4.
1.1.1 Document overview
Chapter Function Status for CSE

1 General provides Information
n Document Overview
n Configuration Expectations
n Supported SRS Infrastructure
n Passwords
n Ports
2 SRS Configuration in Somaris (Navigator and Wizard) Mandatory

1. Prerequisites
2. SRS Configuration Part 1 - SRS Settings
3. SRS Configuration Part 2 - SRS Function Check
4. SRS Configuration Part 3 - System Management Config‐
uration (included in Part 1, not required for VB40, VB36,
or VB38B_SP4)
5. SRS Configuration Part 4- Somatom LifeNet Contacts
(not required in VB40 and VB36. Details in configuration
part 4.

6 1 General Information
Chapter Function Status for CSE

2 Checking the SRS Services Mandatory
1. Remote Diagnostic Access
2. Somatom LifeNet Extranet Access (not in VB40 and
VB36)
3. CS Knowledge Base Access
2 SRS Configuration with Outside NAT Mandatory if the

n Description of Outside NAT (information only) customer uses
this network en‐
1. Adding the Outside NAT Information to SRS Settings vironment
2 Auto reports Activate auto re‐
1. Activate auto report Mon_HQ port after con‐
sulting customer
2 Remote Application Support (RAS) in Som/5 VB40 and On USC request
Som/5.5 VB36. RAS is available at Navigator and Wizard. only
n General
n Legal requirements
n Prerequisites
n Enable/Disable Remote Application Support
n Starting a Remote Application Support session
2 EPS Services On USC request

n Enable/Disable Utilization Management only
n Enable/Disable Virus Protection
3 Helpful hints Information

n System Management information
n SRS Function Check description
4 SRS Troubleshooting description Information

n Error at SRS configuration
n Error at SRS Function Check
n Error at SRS Configuration internal software errors
n Troubleshooting System Management - HP OpenView
n Troubleshooting System Management - CA Unicenter
n Corrective action for internal software errors
1.1.2 Configuration Expectations

The following Standard SRS services shall be configured at every system:

General Information 1 7
n SRS Base: Provides the following function

- Reactive Remote Service: Remote access to system from headquarters and file trans‐
fer to SRS server via FTP protocol.
- Proactive Remote Service (auto reporting): If the customer IT environment supports
dial-out function, automatic file transfer to the SRS server is possible. The automatic
file transfer uses the FTP protocol.
n Somatom LifeNet: Provides the following function
- Displaying the actual newsticker at Somaris Startup
- Access to the Somatom LifeNet portal for, e.g., downloading trial licenses (custom‐
er function).
SomatomLifenet Extranet Access has been disabled in Som/5 VB40 and Som/5.5 VB36.
 Perform the Somatom LifeNet configuration, because it sets the https proxy used to
access the CS KB.
n System Management:Provides the following function

- Proactive Event Management: Sends a message to the Service Support Center for
predefined events occur.
- Remote software update: Allows for remote transfer and installation of software up‐
dates. Typically, the headquarter transfers the remote software update onto the
system. The customer or the CSE then installs the remote software update.
Additionally, the following Enhanced Productivity Services can be enabled.

n Utilization Management: The system generates workflow-related data and sends
them to headquarters for analysis. Based on these data, benchmarking with other cus‐
tomers is possible.
n Virus protection: A Trend Micro Scan engine is activated and checks the file system
for known viruses. The newest virus pattern is downloaded shortly after its release us‐
ing System Management - Remote Software Update.
 The customer must purchase the Enhanced Productivity Services. Enable the services on‐
ly if requested by the local Customer Service.
1.1.3 Supported SRS infrastructure

Som/5 VB30/38/39/40 and Som/5.5 VB36 only supports router (ISDN or analog = analog
router includes modem) or Internet (VPN = Virtual Private Network) connections.
SOM/5 VB30/38/39/40 and SOM/5.5 VB36 does not support a pure modem connection.

8 1 General Information
Siemens provides EPS (Enhanced Productivity Services) and RUH (Remote Update Han‐

dling) only for systems that are connected via Internet/VPN. We strongly recommend us‐
ing VPN connections only.
Line types ISDN or analog are fallback solutions only.
1.1.4 Passwords
When checking the SRS services, the login password for the Somatom Lifenet Extranet
portal is necessary as known from previous software (not necessary for Som/5 VB40 and
Som/5.5 VB36). The password is listed in the Knowledge Base.
1.1.5 Ports
HP OpenView uses 3 ports (8227, 8228, 12061) to communicate from the CT client to HP
OpenView server. Port 8226 and 13001 are used in the opposite direction.
Port 12061 and 13001 are HP proprietary ports, the other 3 ports were already used by
CA Unicenter. Port 12061 and 13001 must be enabled in the customer firewall to avoid
errors during configuration.

SRS Configuration 2 9
2.1 SRS configuration in Somaris (Navigator = syngo Acquisi‐

tion Workplace)
The branding for Navigator and Wizard has been changed.
 n
n
Navigator = syngo Aquisition Workplace
Wizard = syngo CT Workplace
2.1.1 Prerequisites
2.1.1.1 Enable Remote Access
1. Configuration of the Remote Access Mode under Options > Service > Remote Serv‐
ice
Fig. 1: Remote Access
n After consulting with the customer, enable the mode agreed upon; e.g. Limi‐
ted Access Permanent
 Backup & Restore does not restore the RDiag Access Mode Configuration. Re-Configure
the RDiag Access Mode e.g. “Limited Access Permanent” after software installation.
2.1.1.2 Configuration of the SRS gateway

Depending on the network environment at the customer, the IP routing from the CT sys‐
tem to the SRS gateway/router is set via a
n Static route (persistent route) or
n default gateway
For details refer to ( Configuration of the SRS gateway / Page 48)

10 2 SRS Configuration
2.1.2 SRS configuration part 1 - SRS configurations

In this section, the CSE enters the customer-specific SRS information and then performs
an automatic SRS configuration.
1. Define the Remote Service Center (SRS Target Host)
Fig. 2: Remote Service Center
n Select local_service > configuration > local_host > site_info

n Under Service, select the corresponding Remote Service Center from the
pull-down list
- Europe: For systems located in Timezone I (Europe, Africa)
- Asia: For systems located in Timezone III (Asia, Australia)
- USA: For systems located in Timezone II (North and South America)
Note: Remote Service Center Test_E and Test(not_for_Customer_Site) in
syngo VE32 = Som/5 VB40, Som/5.5 VB36 respectively are used in the fac‐
tory for testing only.
n Click <save> to store the configurations.

2. Enter the customer-specific configurations and SRS Functions
n Select Local_Service > Configuration > Service > SRS

Fig. 3: SRS Customer-Specific Settings
SRS Settings for e.g. Europe ( 1/Fig. 3 Page 11)

n Enable the checkbox Outside NAT only if the customer uses this network
environment. For details refer to ( SRS Configuration with Outside NAT -
Optional (NAT = Network Address Translation) / Page 26).
n Enable the checkbox Static Route to SRS only if the CT uses a static route
to reach the SRS Gateway. If applicable enter the IP Address of the SRS
gateway/router (IP 192.168.217.195 is only an example).
SRS Functions ( 2/Fig. 3 Page 11)

VB40, VB38B_SP4, and VB36 changes: The status and date of the last SRS
configuration performed have been added under "SRS Functions." The wording
"Somatom Life" has been changed to "HTTPs Proxy (Knowledge Base)".
n As default, the checkboxes SRS Base, Somatom Life/HTTPs Proxy (Knowl‐
edge Base), and System Management are enabled.
The customer purchases the services Utilization Management and/or Virus
Protection. Enable it only upon special request by the Customer Service.

3. Perform the SRS Configuration
 If the SRS configuration does not complete successfully, refer to ( SRS Troubleshooting
description / Page 33) for troubleshooting details.
Only for Somaris/5 VB40 and VB38B_SP4, and Somaris/5.5 VB36:

The last SRS configuration result is displayed under ( 1/Fig. 5 Page 13). If all “Desired”
 SRS functions display status “Configured”, SRS is successfully configured.

Each time a new SRS configuration is saved the program outputs the message “Function
Check pending. Please click ">". The SRS Function Check is necessary to check the func‐
tion of the configured SRS services.
n Select Local_Service > Configuration > Service > SRS

n Press <save> to perform the SRS configuration.
 VB30/38/39: This takes a few seconds, or about 1 minute in case
the service Virus Protection is enabled. If successful, the message
Site Data successfully saved is output.
 Som/5 VB40 and VB38B_SP4, and Som/5.5 VB36:
The SRS configuration progress is displayed on an html page
( Fig. 4 Page 13).
With Som/5 version VB38B_SP4 and versions VB40 and higher, and
Som/5.5 versions VB36 and higher, System Management is config‐
ured here automatically. As a result, the SRS configuration may take
up to about 10 minutes to complete.
If successful, the message Site Data successfully saved is output
and all SRS Functions display status “Configured”
( 1/Fig. 5 Page 13).
 If an attempted SRS configuration fails, then the message "Status
Failed" is displayed, followed by a detailed error description for Sys‐
tem Management (for VB40, VB38B_SP4,and VB36). For trouble‐
shooting, refer to ( SRS Troubleshooting description / Page 33)
for details.

Fig. 4: SRS_configuration_status Fig. 5: SRS_configuration_result
2.1.3 SRS configuration part 2 - SRS Function Check

1. The SRS Function Check performs a functional check of the configured SRS services.
Fig. 6: SRS Function Check
n On page Local_Service > Configuration > Service > SRS, click “ > ” to perform the
SRS Function check. This check includes an FTP and HTTPs login on the SRS server
and a check if System Management is activated and running. If Virus Protection is en‐
abled, the SRS Function Check checks if the real-time scan Process NtRtScan.exe is
running.
 The SRS configuration is successful if the actual status matches the desired
status. If the desired function cannot be established, an error description is
output ( 1/Fig. 6 Page 13)

For Somaris/5 VB30/38/39 (excluding VB38B_SP4) only:

At the initial SRS configuration ignore the message “CA Unicenter is not active ...” be‐
cause System Management has not yet been configured. The configuration is performed
in SRS configuration part 3. After configuration of System Management, the SRS Func‐
tion Check must run without error.
For Somaris/5 VB30/38/39 only:

If Virus Protection was enabled under SRS Functions, but the SRS Function Check for Sys‐
tem Management fails, Virus Protection is disabled automatically. In this case, configure
System Management first and then enable the checkbox Virus Protection under SRS
Functions again. The SRS Function Check shall now run without errors.
2.1.4 SRS configuration part 3 - System Management configuration
For Som/5 versions VB38B_SP4, VB40 and higher, and Som/5.5 version VB36 and higher,
skip SRS configuration part 3 because System Management is configured in SRS Configu‐
 ration part 1 ( Fig. 5 Page 13).

The configuration procedure described below is still valid but may be obsolete for VB40,
VB38B_SP4, and VB36.
For information only!
 For VB40, VB38B_SP4, and VB36, the product “HP OpenView” replaces the CA Unicenter
System Management software. The function and the installation procedure remains the
same. The time for installation and activation is shorter.
2.1.4.1 General information

The System Management configuration consists of 2 pages
n Master Settings: Provides a UI to enter site-specific parameters used for the System
Management configuration. Do not enter any data because the entries are filled in
automatically when pressing the save button on the SRS configuration page.
n Agent Controls: Provides a UI to execute the System Management configuration.
2.1.4.2 System Management Configuration
Prior to configuring System Management, perform the SRS Function Check. if the SRS
 Base function is OK, the system is then at least able to dial in to the SRS servers using the
FTP protocol.

 ( Helpful hints / Page 48) and ( SRS Troubleshooting / Page 33) provides detailed
information regarding System Management.
1. Configuring the System Management
Fig. 7: CA_offline_success
n Select Local_Service > Configuration > System Mgmt. > AgentControls

n Enable checkbox “Installed” and press <Go> to perform the installation
Note: Most likely the checkbox “Installed” is already enabled because the
System Management Offline Installation is performed automatically during
Somaris Installation.
n Enable checkbox “Activated” and press <Go> to complete the System
Management configuration. During this configuration step, the system
connects to the System Management server located in the SRS environ‐
ment.
 CA Unicenter: The configuration result is normally output after ap‐
prox. 10 minutes to 15 minutes. Check the result at next configura‐
tion step.
 HP OpenView: The configuration result is normally output after ap‐
prox. 6 minutes.
Somaris/5 VB30/38/39 (excluding VB38B_SP4) only:

Do not reboot or shut down the system for at least 15 minutes after having reached the
 running status.
During this time additional software is transferred to the system - reboots or other action
may slow down or even cancel this process.

2. Checking the configuration result
Fig. 8: CA success with template
(1) Status running indicates that System Management has been configured successfully
(2) Installed template version, downloaded at the end of System Management Configuration
n If successful, the installation takes approx. 8 minutes to 10 minutes for CA
Unicenter and approx. 6 minutes for HP OpenView.
 Both checkboxes are enabled and the Status is running
( 1/Fig. 8 Page 16)
 CA Unicenter, VB30/38/39: The template version
( 2/Fig. 8 Page 16) is not displayed immediately after completing
the System Management installation. The reason is that the tem‐
plate transfer is still running when the System Management config‐
uration completes.
You may have to wait approx. 10 minutes before the template ver‐
sion is displayed. Open page AgentControls to obtain the new tem‐
plate status.
 HP OpenView: The template version is displayed immediately at the
end of the configuration.
n If the configuration fails, the result is output between approx. 5 s and 20
minutes later, depending on the type of error.
 In case of error, the Status information is underlined and in bold let‐
ters (e.g. not running underlined). Click this link to get a more de‐
tailed error description.
 Beginning with syngo VE32 (used in Somaris VB40 and VB36), the
configuration logfile is displayed in the lower frame.
What to do if the configuration of System Management fails

CA Unicenter/HP OpenView is automatically rolled back. No action is necessary by the
CSE.

For troubleshooting, refer to ( Troubleshooting System Management - CA Unicenter (So‐

maris/5 VB30/38/39) / Page 38) and ( Troubleshooting System Management - HP
OpenView (VB40, VB38B_SP4, VB36) / Page 37) respectively.
2.1.5 SRS configuration part 4 - Somatom LifeNet Contacts
Skip this chapter in Somaris/5 VB40 and Somaris/5.5 VB36!
 Access to the Somatom LifeNet Extranet is not available in Somaris/5 VB40 and
Somaris/5.5 VB36. As a result, Siemens and customer contacts must not be filled in.
The configuration of Somatom LifeNet is performed automatically with the SRS configura‐
tion SRS.
Additionally, enter the Siemens and customer contacts to ensure that the persons respon‐
sible at the customer site and at Siemens are known. Fill in the data carefully to allow the
customer to display the Siemens contacts.

1. Entering the Siemens contacts
Fig. 9: Somatom_LifeNet Siemens Contacts
(1) Login to Somatom Lifenet Extranet Portal

(2) Administrator login to enter e.g. Siemens Contacts
n Select the Life tabcard to display the Somatom LifeNet menu
n To display the above page, login as Administrator (pos. 2) and select In‐
formation > Siemens Contacts
Note: The known Somatom LifeNet password is listed in the CS Knowl‐
edge Base.
n Fill in the data carefully. The above example displays the entry made for
the Uptime Service Center in Germany.
n Click <submit> to save the results.
n Logout from Adminstrator login (pos. 2)
For service contacts, go to Function and select: Service Engineer, and enter the data of
 the Customer Service responsible.

Do not enter your name.

2. Entering the Customer Information

The customer-specific data are necessary, prior to accessing the SOMATOM life Extra‐
net.
Contact the customer to obtain the requested data.
n Select on LifeNet homepage Information > Institution

Activate entry with <Submit>
n Select on LifeNet homepage Information > Contacts
Enter at least 1 contact person under Contacts. One of the contacts shall be
the chief technician or radiologist who can be contacted for technical issues.
Press <Submit> to save the entry.

2.2 SRS configuration in Somaris (Wizard = syngo CT Work‐

place)
2.2.1 Prerequisites
Follow the description for Navigator under ( Prerequisites / Page 9)
2.2.2 SRS configuration part 1 - SRS configurations

Follow the description for Navigator under ( SRS configuration part 1 - SRS configura‐
tions / Page 10)
2.2.3 SRS configuration part 2 - SRS Function Check

Follow the description for Navigator under ( SRS configuration part 2 - SRS Function
Check / Page 13)
2.2.4 SRS configuration part 3 - System Management configuration

Follow the description for Navigator under ( SRS configuration part 3 - System Manage‐
ment configuration / Page 14)

Beginning with VB40 and VB36, the System Management configuration is included in
( Fig. 5 Page 13).
Automatic configuration of System Management on the Wizard

If System Management is running on the Navigator but not on the Wizard, System Man‐
 agement is configured automatically at the Wizard during next power-up.
Prerequisites: The SRS Function Check for “SRS Basic Function” was successful on the
Wizard.
When checking the System Management status under System Mgmt. > Agent Controls,
 the message “Another System Management action is running already” may be displayed.
This message indicates that the automatic System Management configuration has been
started during Startup.
2.2.5 SRS configuration part 4 - Somatom LifeNet Contacts
Skip this chapter in Somaris/5 VB40 and Somaris/5.5 VB36!
 Access to the Somatom LifeNet Extranet is not available in Somaris/5 VB40 and
Somaris/5.5 VB36. As a result, Siemens and customer contacts must not be filled in.

If the Siemens and customer contacts have already been entered at the Navigator, you
can skip this section. If not or if you are not sure, follow the description under ( SRS con‐
figuration part 4 - Somatom LifeNet Contacts / Page 17).

2.3 Checking the SRS Services (syngo Aquisition and CT work‐

places)
2.3.1 Remote Diagnostic

Remote Diagnostic functions can be checked using 2 tests: The dial-in test (remote login
from the Service Center) and the dial-out test (ftp check).
n FTP Transfer
n Remote login from Service Center
2.3.1.1 FTP transfer

n From the home menu of the Service Software, select File & Image Tools
n Procedure
Source Select File

Action Select Transfer from System
File type Select Any file
Site directory C:\ Scroll down in the Site Directory and select e.g. file boot.ini
Start the file transfer Press <GO> (file transfer via FTP) ( Fig. 10 Page 22)
Fig. 10: FTP check Fig. 11: FTP success
n The transfer manager queue opens ( Fig. 11 Page 22) and displays the transfer sta‐
tus.
Done: 100%
Transfer status: "Transfer successfully finished" indicates that the FTP transfer was suc‐
cessful.

2.3.1.2 Remote login from Service Center

Call the Service Center (e.g. USC) to perform a remote login from the SRS server to the CT
system.
2.3.2 Somatom LifeNet Extranet
 Skip this check in Somaris/5 VB40 and Somaris/5.5 VB36 because the Somatom LifeNet
Extranet access is disabled.
Perform a login to the Somatom LifeNet Extranet from the syngo Aquisition and CT Work‐
places.
After the configuration of SOMATOM LifeNet via item “SRS”, a Somaris restart is necessa‐
 ry to update the Internet Explorer configurations. The Extranet login fails in case of the
restart has not been performed.

1. Login to the SOMATOM LifeNet Extranet
Fig. 12: Somatom_LifeNet Extranet
n Select the Life tabcard

n In the upcoming page select SOMATOM LifeNet online
The scanner now connects via the SRS server to the SOMATOM LifeNet Ex‐
tranet server, which may take a while.
If successful, the Extranet login page is displayed. Enter the site-specific
password to reach the Extranet home menu ( Fig. 12 Page 24). The pass‐
word is listed in the CS Knowledge Base.
n Forward the site-specific password to the customer.
2.3.3 CS Knowledge Base

Log in to the CS Knowledge Base from the Navigator and the Wizard.
2.3.3.1 Access to CS Knowledge Base in Somaris/5 and Somaris/5.5

n On Service Homepage click Help and select Knowledge Base ( 1/Fig. 13 Page 25)
 The CS Knowledge Base home menu is displayed indicating that the access to
the CS Knowledge Base was successful. Log in with your personal login.

Fig. 13: Access_to_CS KB
The link “Service Homepage > Reports > CS > Access to CS Knowledge Base” does not
 work correctly with the new CS Knowledge Base. The link has been removed in
Somaris/5 VB40 and Somaris/5.5 VB36.

2.4 SRS Configuration with Outside NAT - Optional (NAT =

Network Address Translation)
Perform this configuration only if the customer uses outside NAT functionality.
 For Som/5 versions VB38B_SP4 and VB40 and higher, and Som/5.5 versions VB36 and
higher (HP OpenView replaces CA Unicenter), new outside NAT addresses are required.
Details are given below.
2.4.1 Description
Outside NAT means that the customer defines certain IP addresses the CT system uses to
communicate with the Siemens environment (e.g. the SRS access server). If the customer
uses this function, the NAT addresses are configured on page SRS ( 1/Fig. 3 Page 11);
otherwise, SRS does not work.
The customer or the local Customer Service provides a NAT address for the following SRS
servers.
n SRS access server (for Fürth, Newark, or Singapore)
n System Management servers (CA servers for Som/5 VB30/38/39 and HP servers for
Som/5 VB40 / Som/5.5 VB36 respectively)
- CA Asset Management Server (for Fürth, Newark, or Singapore)
- CA Event Management Server (for Fürth, Newark, or Singapore)
- CA Software Distribution Server (for Fürth, Newark, or Singapore)
or
- HP Event Management Server (for Fürth, Newark, or Singapore)
- HP Software Distribution Server (for Fürth, Newark, or Singapore)
Note: Asset server is part of Software Distribution Server
2.4.1.1 To determine whether there is an outside NAT

There is no check available. Outside NAT requires major changes to the SRS configuration
that start in the router configuration. It therefore shall be communicated to the CSE prior
to performing the SRS configuration.
2.4.2 Adding Outside NAT information to SRS Settings for e.g. Europe
 The IP addresses shown in the figures below represent the configurations in Sweden and
are only valid there.
 Typically, the customer network administrator or the local Customer Service provides the
outside NAT IP addresses.

n Outside NAT addresses for HP OpenView (Som/5 VB40, VB38B_SP4, and Som/5.5
VB36)
The CA Unicenter Asset server was integrated into the CA Software Distribution server.
The HP Software Distribution server uses now the former IP address of the CA Asset serv‐
 er.
The HP Event Management server is still the same as known from the former Magic‐
Watch function used in Somaris/5 VA40-VA70.
n Select Local_Service > Configuration > SRS

n Enable checkbox Outside NAT and enter the IP addresses
Fig. 14: Outside_NAT_HP OpenView
n Outside NAT addresses in Som/5 VB30/38/39 (CA Unicenter)
n Select Local_Service > Configuration > SRS

n Enable checkbox Outside NAT and enter the IP addresses
Fig. 15: Outside_NAT CA Unicenter

2.5 Auto reports
2.5.1 Activate auto report Mon_HQ (syngo Aquisition and CT Workplaces)

The auto report Mon_HQ is preconfigured in Somaris and is used to transfer the even‐
tlogs to the SRS server. The eventlogs are analyzed in the head quarters to continously
improve the system quality. Please consult the customer prior to activate the auto report.
Activate auto report: Mon_HQ

n Within the Service home menu, select Auto Reporting
n Select the auto report Mon_HQ under REPORT, and enable the Active checkbox (item
2).
n Set the end date (item 4) to 2030. If the date cannot be set past 2011, this indicates
that the service pack FP52 has not been installed. Install FP52 and activate the auto
report as described here.

n Press Save (item 10) to save the new configurations.

Fig. 16: Mon_HQ
(1) Under Report, select Mon_HQ

(2) Active status
(3) Target: srs_mail is configured as mail target
(4) Ensure that the time period (Begin and End) is set correctly
(5) Sample source: Source: File
(6) Sample what: Filename:C:\Somaris\log\Eventlog\Evt*20*txt.gz Mode: Time Triggered
(7) Sample when: Continuously Sample times: 02:00;07:00;08:30;10:00
(8) Send what: Mail: as separate file(s) without mails FTP target: e.g. ftp2lux09505
(9) Send when: At once
(10) If you perform any changes, <Save> the Auto Report

2.6 Remote Application Support in Som/5 VB40 (syngo Acquis‐

ition and CT workplaces)
2.6.1 General
In Somaris/5 VB30/38/39, the customer uses Expert-i to share the desktop within its local
area network (LAN) or wide area network (WAN). A license key protects the Expert-i func‐
tion.
In Som/5 VB40, the Expert-i function was extended to share the desktop using the secure
SRS environment. In this case the license key is not checked, so that basically all systems
support the function “Remote Application Support”.
2.6.2 Legal requirements

The Expert-i function may not comply with country-specific legal requirements because
patient-relevant information such as patient name, and so on, is also displayed to the re‐
mote user.
Therefore the function Remote Application Support is currently deactivated as default.
 A site-specific release of the Remote Application Support function is easy via SRS / full
access mode.
2.6.3 Prerequisites
The following prerequisites must be met at the SRS server and on the system.
n The Application Profiles Expert-i (high, medium, and low) must be enabled for the cor‐
responding customer system.
n Remote Application Support must be enabled on the system.
 To use the function, the Remote Application Support checkbox must be ena‐
bled (not dimmed) under Options > Service > Remote Service.
If dimmed, Remote Application Support cannot be used.
2.6.4 Enable/Disable Remote Application Support

Remote Application Support shall be set only on request by the local Customer Service.
For enabling or disabling details, please contact your USC.
2.6.5 Starting a Remote Application Support session

A remote session is established interactively between the customer and the remote user
(Siemens). See details below:

n Siemens: connects to the system using the Expert-i application profile at the SRS
server. Different image resolutions (High, Medium, and Low) can be chosen to adapt
the performance to the available IT bandwidth.
n Siemens/Customer: Telephone contact between Siemens and the customer is re‐
quired
n Customer: Enable checkbox Remote Application Support via Options > Service >
Remote Service > Remote Service Access Control.
Press <Apply> or <OK> to activate it.
Note: The customer is informed via a pop-up ( Fig. 17 Page 31) that Siemens can
see patient-relevant information after sharing the desktop. The customer has to ac‐
knowledge this pop-up window with OK to continue.
Fig. 17: RAS_Customer Info Fig. 18: RAS_Access Password and Mode
n Customer: The Expert-i Access dialog window is displayed. The customer forwards
the one-time password ( 1/Fig. 18 Page 31) to the remote user.
n Siemens: Enter the given password at the Expert-i client window to share the desk‐
top
Remote Application Support is started as default in View Only Mode

 ( 2/Fig. 18 Page 31). If Full_Access is required, the customer has to enable it within a
new session.
Stopping the Remote Application Support session

n Remote user/Siemens: Click the X at the upper right corner to close the session.
n Customer: Click on the “Tray Icon” in the taskbar and then select the software button
“Terminate” in the window displayed.

2.7 EPS - Services

In CT, the following EPS Services can be configured within the software:
n Utilization Management
n Virus protection
2.7.1 Enable/Disable Utilization Management

Enabling and disabling of this service is performed via checkbox Utilization Management
under Local_Service > Configuration > SRS > SRS Functions ( 2/Fig. 3 Page 11).
 If the checkbox is enabled, the Utilization Management files (logs.zip) are transfer‐
red daily onto the SRS server.
One can check this function under Reports > Remote Diagnostics > SRS. In the
html page that is displayed, scroll down completely and check the transfer interval
of file logs.zip. Detailed information regarding Utilization Management is provided
in the document ( Utilization Management / CT00-000.843.10)
2.7.2 Enable/Disable Virus Protection

Enabling and disabling of this service is performed via the Virus Protection checkbox un‐
der Local_Service > Configuration > SRS > SRS Functions ( 2/Fig. 3 Page 11).
 If the checkbox is enabled, the Real Time Virus Scanner is enabled. Detailed infor‐
mation regarding virus protection is provided in the document ( Enabling Virus
protection within SOMARIS / CT00-000.843.06).

SRS Troubleshooting 3 33
3.1 SRS Troubleshooting description

SRS may fail during configuration of the SRS services or when testing the function at
the SRS Function Check. Therefore troubleshooting differentiate between
n Errors at SRS Configuration and
n Errors at SRS Function Check
3.1.1 Error at SRS configuration

Som/5 VB30/38/39: In case of error, the message window Error saving site data: e.g.
unable to save syngo host properties is output. This indicates an internal software/
configuration error. For details refer to ( Error at SRS configuration - Internal software
errors / Page 42)
More likely the SRS configuration fails at the System Management configuration. For de‐
tails, refer to ( Troubleshooting System Management - CA Unicenter (Somaris/5
VB30/38/39) / Page 38)
Som/5 VB40, VB38B_SP4 and Som/5.5 VB36: The status of the corresponding SRS func‐
tion is shown as Failed. The following table provides an error description and a corrective
action.

34 3 SRS Troubleshooting
Fig. 19: Example: SRS_Configuration_Failure_VB40_VB36
2
3
4
5
(1) In this example, the Customer uses a default gateway for SRS
(2) FTP, mail and IE proxy are configured successfully
(3) Troubleshooting guide provided in service OLH (VB40,VA30)
(4) If System Management fails, VirusProtection will not be configured
(5) Function check required after saving new SRS configuration
Tab. 1 SRS configuration result - failed
SRS Function Description and Corrective action

SRS Base Software was unable to configure SRS target host or
Configuration Status = Failed mail or FTP user.
For details, refer to ( Error at SRS configuration - Inter‐
nal software errors / Page 42)
HTTPs Proxy (Access to CS Status Failed is displayed if SRS Base is not configured
Knowledge Base) correctly.
Configuration= Failed If SRS Base is “Configured”, status Failed at HTTPs Proxy
shall never appear. If it does, the software might be
corrupted > contact the SRS Help Desk or headquarters.

SRS Function Description and Corrective action

Utilization Management (UM) Status Failed is displayed if SRS Base is not configured
Configuration Status = Failed correctly.
If SRS Base is “Configured”, status Failed at Utilization
Management shall never appear. If it does, the soft‐
ware might be corrupted > contact the SRS Help Desk
or headquarters.
System Management Refer to the troubleshooting instructions for System
Configuration Status = Failed Management (HP OpenView, see ( Troubleshooting
System Management - HP OpenView (VB40,
VB38B_SP4, VB36) / Page 37)).
Note: In VB30/38/39, System Management is config‐
ured via Configuration > SystemMgmt > AgentCon‐
trols. For troubleshooting refer to ( Troubleshooting
System Management - CA Unicenter (Somaris/5
VB30/38/39) / Page 38)
Virus protection Status Failed is displayed if System Management is not
Configuration Status = Failed configured correctly.
If System Management is “Configured” but status
“Failed” is output at Virus Protection, perform the fol‐
lowing checks:
n Check if the folder c:\Somaris\Tools\VirusScanner
is available and contains files: install.bat, and fold‐
er 32bit/64bit.
 If not available, the software installation was
incomplete. Contact SRS Help Desk or head‐
quarters.
 If available, restart the system and check
again. Contact SRS Help Desk or headquar‐
ters if it fails again.
3.1.2 Error at SRS Function Check

The program displays the desired and the actual status of the various SRS services. If a
desired service cannot be established, an error description is output for the user. The re‐
sult of the function test may be delayed due to timeouts within the tests. Possible causes
of error are:
Tab. 2 SRS Function Check - Error messages
SRS Function Possible error messag‐ Corrective action

es
SRS Base Network connection to It is most likely that the CT cannot dial out to
<SRS_IP> failed the SRS server. Check the IP routing within
the customer network using the command
tracert (e.g. tracert 194.138.39.18 to con‐
nect to the SRS server in Europe).


es
SRS Base FTP logon to <SRS IP> The login (username & password) is prede‐
failed (only in VB40 and fined within the software, therefore it is very
VB36) unlikely that this message appears. If it does,
an SRS server problem is most likely.
SRS Base FTP file transfer to <SRS The system is able to log into the SRS server
IP> failed (only in VB40 but fails to download a file. Most likely, the
and VB36) FTP protocol is not supported in the custom‐
er IT environment. Check with network ad‐
ministrator.
HTTPs Proxy (Ac‐ No connection to the The Somatom LifeNet Server is unreachable
cess to CS Somatom LifeNet extra‐ or the customer is blocking the https proto‐
Knowledge net server col/port (e.g. is protecting port 8080 with a
Base) user name and password to block surfing in
the Internet).
Perform a connection check to the CS
Knowledge Base via ( 1/Fig. 13 Page 25)
n If successful, the LifeNet server is cur‐
rently not available (try again in 10 mi‐
nutes).
n If not successful, check with the network
administrator.
Utilization Man‐ n.a. No UM-specific error message is available. If

agement (UM) SRS Base failes “FTP file transfer to <SRS_IP>
failed”, UM will be deactivated.
System Manage‐ CA Unicenter is not ac‐ Refer to Troubleshooting System Manage‐
ment (CA Uni‐ tive. Please install and ment (CA Unicenter) ( Troubleshooting
center) configure CA Unicenter System Management - CA Unicenter (Soma‐
ris/5 VB30/38/39) / Page 38)
The checkbox “actual” is disabled if System
Management has not been configured yet or
the configuration failed.


es
System Manage‐ HP OpenView is not ac‐ Refer to "Troubleshooting System Manage‐
ment (HP Open‐ tive. Please install and ment (HP OpenView)" ( Troubleshooting
View) configure it System Management - HP OpenView (VB40,
VB38B_SP4, VB36) / Page 37).
Virus protection Virus scanner service If System Management is configured cor‐
not running rectly this message indicates that the soft‐
ware was unable to start the Virus Scanner
real-time scan.
Check in the Task Manager for process
NTRtScan.exe. If it is not running, restart
the system and check again. If still not avail‐
able after restart, contact the SRS Help Desk.
3.1.3 Troubleshooting System Management - HP OpenView (VB40,

VB38B_SP4, VB36)
Use the given error message from the SRS configuration page and perform the corrective
action as described below:
Tab. 3 Explanation sysmgmt_install.log_HP
Error message and Descrip‐ Corrective action

tion
Failed reaching Management Perform the SRS Function Check.
Server n If the SRS Base check is OK, the system can dial-out
The system is unable to con‐ to the SRS server using the FTP protocol. Perform a
nect to the HP servers using HP port check as described in section ( Port
proprietary ports and protocols. Check / Page 45)
n If the SRS Base check fails, the system cannot dial-
out at all. Check network configuration (default
gateway or static route to SRS) and/or contact net‐
work administrator.
Failed to Get Backend Data Perform a port check as described in section ( Port
Indicates, that the system is un‐ Check / Page 45)
able to retrieve the customer- n If port check is not OK, contact the IT administrator.
specific data from the SRS serv‐ n
If port check is OK, repeat the System Management
er (CRSP).
configuration once. If it fails again, contact the SRS
Help Desk for assistance.


tion
Failed to Install Certificate of Perform a port check as described in section ( Port
Event Agent! Check / Page 45)
Download of the Certificate n If port check is not OK, contact the IT administrator.
fails due to a problem at the n If port check is OK, repeat the System Management
backend or because a port is
blocked.
Failed Installation of Tem‐ Perform a port check as described in section ( Port

plate Check / Page 45)
With “New node event sent”, n If port check is not OK, contact the IT administrator.
the backend is notified about n If port check is OK, repeat the System Management
the required template and then
transfers it to the system.
Failed starting System Man‐ Uninstall System Management and then reinstall sys‐
agement Base tem management as descibed under ( Uninstalling
The agents could not be started and reinstalling the System Management
correctly. agent / Page 46). If the error still appears, contact the
SRS Help Desk for assistance.
Any other error message Repeat the System Management configuration once. If
it still fails with this error message, contact SRS Help
Desk.
In some cases the uninstallation and reinstallation of the System Management agent sol‐
 ves errors that are occurring. Perform this procedure only once - if it does not succeed
network problems or server problems are more likely by the reason for problems.
3.1.4 Troubleshooting System Management - CA Unicenter (Somaris/5

VB30/38/39)
In Somaris/5 VB38B_SP4 the system management software was changed from CA Uni‐
 center to HP OpenView. For troubleshooting, refer to section ( Troubleshooting System
Management - HP OpenView (VB40, VB38B_SP4, VB36) / Page 37).
If the System Management Configuration completes with error, the Status information
displays e.g not running (underlined). A pop-up appears when clicking on this link, pro‐
viding additional information as shown in ( Fig. 20 Page 39). Use the given error mes‐
sage and perform the corrective action as described below. The result of the System Man‐
agement configuration is stored in logfiles. An example is shown under ( Log‐
files / Page 40).

 Status Sleeping: ( Tab. 4 Page 39) provides information for this error
Fig. 20: Installation failure
Tab. 4 Explanation sysmgmt_install.log_CA

tion
Failed reaching Management Perform the SRS Function Check.
Server (step 2 in n If the SRS Base check is OK, the system can dial-out
( Tab. 5 Page 40) to the SRS server using the FTP protocol. Port 1721
The CT system connects to the might be blocked. Contact SRS help desk.
System Management server us‐ n If the SRS Base check fails, the system cannot dial-
ing port 1721 (CA proprietary out at all. Check network configuration (default
protocol). gateway or static route to SRS) and/or contact net‐
work administrator.
Failed Init of the node (step 5 Most installations fail at this step.
in ( Tab. 5 Page 40) Uninstall System Management and then reinstall system
The INIT package is first down‐ management as descibed under ( Uninstalling and re‐
loaded from the backend serv‐ installing the System Management agent / Page 46). If
er and then executed at the the error still appears, contact the SRS Help Desk for as‐
system. sistance.
Failed starting System Man‐ Uninstall System Management and then reinstall system
agement Base (step 7 in management as descibed under ( Uninstalling and re‐
( Tab. 5 Page 40) installing the System Management agent / Page 46). If
The agents could not be star‐ the error still appears, contact the SRS Help Desk for as‐
ted correctly. sistance.


tion
Status Sleeping displayed at If a restart is performed while a template update is run‐
System Management Base ning, this error appears. To avoid this error, complete
Function the System Management configuration and wait at least
10 minutes prior to restarting the system.
Uninstall System Management and then reinstall system
management as descibed under ( Uninstalling and re‐
installing the System Management agent / Page 46). If
the error still appears, contact the SRS Help Desk for as‐
sistance.
Any other error message Uninstall System Management and then reinstall system
management as descibed under ( Uninstalling and re‐
installing the System Management agent / Page 46). If
the error still appears, contact the SRS Help Desk for as‐
sistance.
3.1.4.1 Logfiles
Each System Management installation creates a logfile of approx. 8-15 KB ( 2-3-kB logfiles
display status messages). The most current logfile starts with sysmgmt_install.log, fol‐
lowed by sysmgmt_install_old.log, and sysmgmt_install_old_01.log, and so on,
The logfiles are stored under c:\Temp.
Check in the log file for the first E = Error in the far left column, because it describes the
 reason for the failed installation.

Depending on the configuration step, perform the corrective action as described below.
Tab. 5 example of sysmgmt_install.log_CA
I 11/09/2006 09:23:31 ***********************************************

**********************
I 11/09/2006 09:23:31 System Management Managed Node Package - Version
VF10F(3.19)
I 11/09/2006 09:23:31 ***********************************************
**********************
I 11/09/2006 09:23:31 OS=Win2003
I 11/09/2006 09:23:31 READ IN THE OPTIONS
............................
Step 1: Starting installation and activation of System Management
I 11/09/2006 09:23:35 START Installation of System Management Base (Offline 2.
Part)

I 11/09/2006 09:23:35 START enable all CA services Communica

END enable all CA services
Communication-IP=192.168.186.116
I 11/09/2006 09:23:36 Check for valid IP address of Manager
Step 2: Connectivity check
I 11/09/2006 09:23:37 Check if Management Server is reachable. (timeout: 300
sec.)Scanning : e.g.194.138.39.22 port 1721Successful
reaching Management Server 194.138.39.22
I 11/09/2006 09:23:37 -------------------------
Step 3: Registration data
I 11/09/2006 09:23:37 This is an example for Sensation 64 with serial # 54777 and
Navigator IP 192.168.186.116, located in Germany
WSNAME= ct_neuro
Node_IP= 192.168.186.116
Node_Name= CT8377520-54777
Host name= ct_neuro
hostIP= 192.168.186.116
Modality= CT
System_Type= P30F
Product_Version= VB30A
Serial number= 54777
MaterialNumbe= 8377520
CUSTOMER_ID= ID
COUNTRY= DE
I 11/09/2006 09:23:37 START Installation of System Management Base
I 11/09/2006 09:23:37 START Modify the etc/hosts File
Successful entry in hosts file
END Modify the etc/hosts File
START Setting system variables
Successful setting system variables
END Setting system variables
Step 4: Start Registration with server
I 11/09/2006 09:23:41 Check if Management Server is reachable. (timeout: 300 sec.)
Scanning : e.g. 194.138.39.22 port 1721
Successful reaching Management Server 194.138.39.22

I 11/09/2006 09:23:44 Registering the Node: CT8377520-54777 with Manager

194.138.39.22 with message=[c:\sysmgmt\TND\BIN\cawto -n
194.138.39.22 -s CT8377520-54777 "New Node:
CT8377520-54777 App: CT_P30F_VB30A Site: DEn.a. Sour‐
ceIP: e.g. 192.168.186.116 " > C:\DOCUME~1\ADMINI~1\LO‐
CALS~1\Temp\log\cawto.txt 2>&1 ]
I 11/09/2006 09:23:45 Successful registration with server
END register with server
............................
Step 5: Download INIT package from server
I 11/09/2006 09:25:25 START init of the node
I 11/09/2006 09:25:25 Waiting up to 15 minutes for INIT of the node
E 11/09/2006 09:40:25 Failed init of the node:
............................
Step 6: Automatic rollback if activation of System Management failed
I 11/09/2006 09:40:25 START Automatic Rollback from System Management
............................
I 11/09/2006 09:41:26 END Automatic Rollback from System Management
Step 7: Status System Management Installation/Activation
E 11/09/2006 09:41:30 Failed installation of System Management Base (Failed init of
the node: )
3.1.5 Error at SRS configuration - Internal software errors
 These error types occur at the very beginning of the configuration of SRS Base or System
Management.
3.1.5.1 Known internal software errors

( Corrective action for internal software errors / Page 44) provides a more detailed de‐
scription for the following error examples
1. SRS Base configuration fails: Error saving site data: Unable to save syngo host
properties
- CSE presses the Save button within the SRS page and the error is output within 30
s.
- Affected software: all Som/5 and all Som/5.5 versions

Fig. 21: Error when saving SRS settings
2. System Management configuration fails: Corrupted file agent_actual_state.xml

- The CSE presses the Save button at the SRS page or navigates to configuration >
SystemMgmt > Master/AgentControl. The error is output immediately after start‐
ing the System Management Installation or Activation.
- This error can appear in all software version, indicated by a different pop-window.
The figure title shows the corresponding version.
Fig. 22: Corrupted_agent_actual_state_VA20/30 and VB40 at config. item SRS
Fig. 23: corrupted_agent_actual_state.xml_VA20/30 and VB40 at config. AgentControls
Fig. 24: corrupted_agent_actual_state_VB30/38/39 and VA11
3. System Management configuration fails: Too many Active Routes in the IP-Routing
table.
- The CSE navigates to configuration > SystemMgmt > Master/AgentControl. The
error message is output immediately.
- Affected Software: This error may occur in VB30/38/39.

Fig. 25: Too many Active routes in routing table
4. Checkbox Virus Protection disabled in Somaris/5 VB30 only

The SRS configuration completes successfully but the checkbox for Virus Protection is
removed.
3.1.6 Corrective action for internal software errors
3.1.6.1 Error saving syngo host properties (SRS Base)

Most likely the SRS host (e.g. lux09505) is already entered with another IP address, or the
IP address is already in use by another SRS host. Therefore, delete the SRS hosts entry.
Before you can delete the SRS hosts, delete the FTP and mail targets first.
Procedure
1. Deleting the FTP targets
- Select Local_Service > Configuration > Service > FTP
- In the menu that is displayed, press “ > ” to change to the next page
- Delete all FTP targets such as logical name ftp2lux09505
2. Deleting the FTP targets
- Select Local_Service > Configuration > Service > Mail
- In the menu that is displayed, press “ > ” to change to the next page
- Delete all mail targets such as logical name srs_mail
- Press “<” to return to Host Properties
3. Deleting the SRS Hosts
- Under Select Host, search for SRS hosts lux09505, srsacc1, or sgpt806 and delete
them.
 The customer-specific SRS settings.
3.1.6.2 Corrupted file agent_actual_state.xml

Procedure
n Wizard/Navigator
Use the file from the navigator/wizard, located at c:\somaris\service\mwtools.

n Navigator only
Request the file from the SRS Help Desk
3.1.6.3 Active Routes in the IP-routing table

Contact the SRS Help Desk or Headquarters for support. Most likely, the Rip_Listener serv‐
ice must be deactivated within the registry.
3.1.6.4 Checkbox Virus Protection disabled in Somaris/5 VB30 only

The checkbox “Desired” is set for Virus Protection and the SRS configuration is executed
with the <Save> button. The SRS configuration completes successfully but the checkbox
for Virus Protection is removed.
 Most likely the real-time scan virus scanner is already activated and the software is
displaying the wrong status.
Use the Task Manager to check whether the real-time scan service NTRtScan.exe
is available. If yes, the Virus Scanner is running correctly and only the display is in‐
correct.
If not, contact the SRS Help Desk or headquarters for support.
3.1.7 Port Check

n Select Local_Service > Configuration > SystemMgmt > Master Settings
n Click Test to start the port check. This test may take a few minutes before the result is
displayed at the Master page (Master is alive or not alive)
n Detailed test results are stored in the logfile c:\sysmgmt\Log\sysmgmt_install.log or
c:\sysmgmt\Log\sysmgmt_install_old.log
 The example shows a port check at the System Management release environ‐
ment, and shows that the 3 outgoing and 2 incoming ports are opened correct‐
ly.

Fig. 26: Result_Port_Check
 If the port check fails, please check with the customer network administrator.
3.1.8 Uninstalling and reinstalling the System Management agent

In some cases the uninstallation and reinstallation of the System Management agent sol‐
ves errors that are occurring. Perform this procedure only once - if it does not succeed
network problems or server problems are more likely by the reason for problems.
Perform the following steps to uninstall and reinstall the System Management agent
n Go to Configuration > System Mgmt > Agent Controls
 If the configuration > System Mgmt is not displayed, enable the checkbox System Man‐
agement under Configuration > Option List.
n Uncheck both checkboxes Activated and Installed

n Wait until “Ready” is displayed in the status bar (may take a few minutes)
n Click Finish and go back to Home
n Accept the reboot and restart the computer

Fig. 27: Configuring System Management
n Go to Local Host > Site Info

- check the Remote Service Center corresponding for your location (e.g. USA)
- Check entry Material No: A valid material number must be displayed. If material no.
111 is displayed, please contact the SRS help desk
- Check entry Serial No: Ensure that a valid serial number is entered. If serial no. 0 is
displayed, correct it or contact the SRS help desk.
- Click Save and then click Finish
n Go to Configuration > System Mgmt > Agent Controls
Note: Perform another reboot, if the software requests it.
n Enable checkbox Installed and press Go to perform the System Management installa‐
tion.
 The background installation should take appr. 5 minutes.
n Enable checkbox Activated and press Go to complete the System Management con‐
figuration.
 If the activation is successful after about 10 minutes (differs between CA Uni‐
center and HP OpenView) the status Running is indicated.
Only for VB30/38/39 (excluding VB38B_SP4):

Do not reboot or shut down the system for at least 15 minutes after having reached the
 running status.
During this time additional software is transferred to the system - reboots or other action
may slow down or even cancel this process.

48 4 Helpful hints
4.1 Configuration of the SRS gateway

Depending on the network environment at the customer, the IP routing from the CT sys‐
tem to the SRS gateway/router is set via a
n Static route (persistent route) or
n default gateway
When to use a static route or a default gateway
n Static Route: We recommend configuring the SRS gateway via a static

route in case the CT system and the SRS gateway are in the same net. In
this case, the customer can use the default gateway (configured via TCP/IP
LAN) for internal routing.
n Default Gateway: Involve the network administrator, if the CT and the SRS
are in different networks. The administrator configures the default gate‐
way to reach the SRS gateway (router). The CSE enters the IP address of
the default gateway under TCP/IP LAN.
1. Configuring a Static Route

The configuration of a static route is performed under Configuration > Service > SRS.
For details, refer to ( 1/Fig. 3 Page 11).

Helpful hints 4 49
2. Configuring a Default Gateway
Fig. 28: TCP/IP LAN
n Select Local_Service > Configuration > Local_Host > TCP/IP LAN

n Select the corresponding network interface card under Adapter.
n Under gateways, enter the IP address of the default gateway. As configured by the
network administrator, the default gateway is able to reach the SRS gateway.
n Click Save to save the results.

50 4 Helpful hints
4.2 System Management information (CA Unicenter -

VB30/38/39)
4.2.1 How to deactivate or deinstall System Management (CA Unicenter)

Deinstallation of the System Management is not necessary due to the implemented roll‐
back function. In other words, if the installation detects an error, the software is rolled
back automatically. If the installation succeeds, there is no need for deinstallation.
n Deactivation of System Management
Under Configuration > SystemMgmt > Agent Controls disable the checkbox System
Management Base - Activated - and press <Go> to deactivate CA Unicenter. All CA Uni‐
center services are stopped, and System Management is deactivated. In this status,
System Management does not use any system resources.
n Uninstalling System Management
Disable both checkboxes System Management - Activated and Installed - and press
<GO>. The CA Unicenter software is rolled back completely.
4.2.2 System Management backup/restore strategy

System Management is fully backed up (Backup/Restore) in Somaris. If the software rein‐
stallation takes place with backup/restore, the System Management Configuration is exe‐
cuted automatically at restore. The System Management configuration extends the re‐
store time by approx. 8 minutes to 10 minutes if the configuration succeeds, or even lon‐
ger if it fails.
4.2.3 CA Unicenter pop-ups

Here is a list of pop-ups that have appeared during the software integration and test
phase. The pop-ups appeared during software installation, including restore, or in regard
to installation or uninstallation of System Management. The pop-ups had no functional
impact.
1. Another System Management action is running already

During software Startup Syngo checks the actual and the desired status of System
Management. If both do not match, the configuration is started automatically.
When checking the System Management status under Local_Service > Configuration
> SysMgmt > AgentControls, a message may be displayed indicating that another
System Management installation is already running. This message may appear during

Helpful hints 4 51
software update, or when restoring the system tables (the “SW Settings” include the
System Management configuration file).
Fig. 29: Another_SystemManagement_running
Wait a maximum 15 minutes and check again.

2. tngboot.exe
This pop-up window may only appear during Somaris installation. It indicates that the
CA Offline installation was not performed correctly during software installation.
Fig. 30: CA_Offline_Popup
3. wtsutil.dll
If an escalation event is sent (due to e.g. too many restarts or continues) right after
the System Management configuration and before a reboot, this pop-up window may
appear. The reason is that some path variables have not yet been updated. Once the
system is rebooted the following pop-up does not appear anymore.
Fig. 31: CA_Popup
4. Agent_send
The pop-up Agent_Send appeared once in the field during Restore. If it appears, ac‐
knowledge it and continue.

52 4 Helpful hints
4.3 System Management information (HP OpenView)

In Som/5 VB40, VB38B_SP4, and Som/5.5 VB36, HP OpenView replaces the CA Unicenter

software. The System Management configuration procedure is now part of the SRS in‐
stallation procedure (item SRS) due to the faster configuration time.
Set the checkbox System Management to install and activation it via the SRS page.
4.3.1 How to deactivate System Management

n At SRS > SRS Settings e.g. Europe / SRS Function, deselect the checkbox System
Management and press <Save>.
 System Management is deactivated; the checkbox remains unchecked.
4.3.2 How to deinstall System Management

n At SystemMgmt > Agent Controls, disable both checkboxes System Management -
Activated and Installed - and press <GO>.
 System Management is de-installed. A system reboot is required to reinstall it.
4.3.3 System Management backup/restore strategy

System Management is fully backed up (Backup/Restore) in Somaris. If the software rein‐
stallation takes place with backup/restore, the System Management Configuration is exe‐
cuted automatically at restore. The System Management configuration extends the re‐
store time time by approx. 6 minutes to 7 minutes if the configuration succeeds, or even
longer if it fails.
4.3.4 HP pop-ups
Here is a list of pop-ups that have appeared during the software integration and test
phase. The pop-ups appeared during software installation, including restore, or in regard
to installation or deinstallation of System Management. The pop-ups had no functional
impact.
1. Another System Management action is running already

During software Startup Syngo checks the actual and the desired status of System
Management. If both do not match, the configuration is started automatically.
When checking the System Management status under Local_Service > Configuration
> SysMgmt > AgentControls, a message may be displayed indicating that another
System Management installation is already running. This message may appear during

Helpful hints 4 53
software update, or when restoring the system tables (“SW Settings” include the Sys‐
tem Management configuration file).
Fig. 32: Another_SystemManagement_running
2. radia.vbs
This pop-up window may appear after a failed installation during the next installation
attempt. There is no problem, just a run-key of the old installation, which cannot be
executed at this time. Later in the installation process the run-key is then successfully
executed. Acknowledge the pop-up window with OK to continue, no further action is
necessary.
Fig. 33: HP_popup_radia.vbs

54 4 Helpful hints
4.4 SRS Function Check
4.4.1 Functional description

As defined under Local_Service > Configuration > SRS / SRS Functions, the following steps
are performed during the SRS Function Check
n Remote Diagnostic Base
The CT system dials in to the SRS access server using the FTP login. If successful, the
Actual Status is enabled.
In Som/5 VB40 and Som/5.5 VB36, an FTP file transfer is added to check the file
transfer to SRS.
n Somatom LifeNet
If the FTP login is successful, the program calls up the start page on the Somatom Life‐
Net Extranet server (https check). If successful, the software automatically configures
the Internet Explorer proxy used for Somatom LifeNet Extranet and for access to the
CS Knowledge Base.
The checkbox “actual” is disabled as long as the SRS Base Function is disabled.
 The program requires a Somaris Application Restart to update the Internet Explorer with
the new proxy configuration.
n Utilization Management
If the checkbox is activated, System Utilization files are generated and forwarded to
HQ.
n System Management
The software checks if System Management is running by calling the agent status.
n Virus protection
The software checks if the Real Time scanner (process NtRtScan.exe) is running.
The Virus Protection function is disabled as long as System Management is not run‐
ning or SRS Base is disabled . Trend Micro Office Scan remains installed but real-time
scan is deactivated.

Changes to Previous Version 5 55
Version CT00-000.843.08.06 compared to version CT00-000.843.08.05 according to CR

567213.
Capter Changes
General information The document has been updated for the following topics:
n VB38B_SP4 uses HP OpenView System Management
software instead of CA Unicenter.
n Set new expiration date for Auto Report Mon_HQ
Chapter 1: General Informa‐ The HP OpenView System Management software replaces

tion CA Unicenter in software version VB38B_SP4. Corre‐
sponding information was added in this chapter.
Chapter 2: SRS Configuration The HP OpenView System Management software replaces
CA Unicenter in software version VB38B_SP4. Corre‐
sponding information was added in this chapter.
Activation of Auto Report Mon_HQ with new expiration
date was added.
Chapter 3: SRS Troubleshoot‐ VB38B_SP4 was added.
ing
Chapter 4: Helpful Hints VB38B_SP4 was added.
Chapter 5: Changes to Previ‐ see page
ous Version

56 6 List of Hazard IDs
There are no Hazard IDs in this document.

All documents may only be used for
rendering services on Siemens
Healthcare Products. Any document
in electronic form may be printed
once. Copy and distribution of elec‐
tronic documents and hardcopies is
prohibited. Offenders will be liable
for damages. All other rights are re‐
served.
healthcare.siemens.com/services
Siemens Healthcare Headquarters

Siemens Healthcare GmbH
Henkestr. 127
91052 Erlangen
Germany
Telephone: +49 9131 84-0
siemens.com/healthcare
Print No.: CT00-000.843.08.07.02 | Replaces: CT00-000.843.08.06.02

Doc. Gen. Date: 06.13 | Language: English
© Siemens Healthcare GmbH, 2006
siemens.com/healthcare

Service, SRS Config. in SOM 5 5.5 VB30 38 39 40 41 36 CSTD CT02-023.805.02 CT00-000.843.08

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Service, SRS Config. in SOM 5 5.5 VB30 38 39 40 41 36 CSTD CT02-023.805.02 CT00-000.843.08

Uploaded by

Copyright:

Available Formats

Common CT

Answers for life.

Common CT CT00-000.843.08.07.02 Page 2 of 57 © Siemens, 2006

2.1 SRS configuration in Somaris (Navigator = syngo Acquisition Workplace) . . 9

3.1 SRS Troubleshooting description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

© Siemens, 2006 CT00-000.843.08.07.02 Page 3 of 57 Common CT

3.1.3 Troubleshooting System Management - HP OpenView (VB40, 37

4.1 Configuration of the SRS gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

5 Changes to Previous Version 55

6 List of Hazard IDs 56

Common CT CT00-000.843.08.07.02 Page 4 of 57 © Siemens, 2006

The CS strategy is to replace the CA Unicenter System Management software with HP

1.1.1 Document overview

Chapter Function Status for CSE

2 SRS Configuration in Somaris (Navigator and Wizard) Mandatory

© Siemens, 2006 CT00-000.843.08.07.02 Page 5 of 57 Common CT

Chapter Function Status for CSE

2 SRS Configuration with Outside NAT Mandatory if the

2 EPS Services On USC request

3 Helpful hints Information

4 SRS Troubleshooting description Information

1.1.2 Configuration Expectations

Common CT CT00-000.843.08.07.02 Page 6 of 57 © Siemens, 2006

n SRS Base: Provides the following function

n System Management:Provides the following function

Additionally, the following Enhanced Productivity Services can be enabled.

1.1.3 Supported SRS infrastructure

© Siemens, 2006 CT00-000.843.08.07.02 Page 7 of 57 Common CT

Common CT CT00-000.843.08.07.02 Page 8 of 57 © Siemens, 2006

2.1 SRS configuration in Somaris (Navigator = syngo Acquisi‐

2.1.1.1 Enable Remote Access

Fig. 1: Remote Access

2.1.1.2 Configuration of the SRS gateway

© Siemens, 2006 CT00-000.843.08.07.02 Page 9 of 57 Common CT

2.1.2 SRS configuration part 1 - SRS configurations

1. Define the Remote Service Center (SRS Target Host)

Fig. 2: Remote Service Center

n Select local_service > configuration > local_host > site_info

Common CT CT00-000.843.08.07.02 Page 10 of 57 © Siemens, 2006

2. Enter the customer-specific configurations and SRS Functions

n Select Local_Service > Configuration > Service > SRS

SRS Settings for e.g. Europe ( 1/Fig. 3 Page 11)

SRS Functions ( 2/Fig. 3 Page 11)

© Siemens, 2006 CT00-000.843.08.07.02 Page 11 of 57 Common CT

3. Perform the SRS Configuration

Only for Somaris/5 VB40 and VB38B_SP4, and Somaris/5.5 VB36:

 SRS functions display status “Configured”, SRS is successfully configured.

n Select Local_Service > Configuration > Service > SRS

Common CT CT00-000.843.08.07.02 Page 12 of 57 © Siemens, 2006

Fig. 4: SRS_configuration_status Fig. 5: SRS_configuration_result

2.1.3 SRS configuration part 2 - SRS Function Check

Fig. 6: SRS Function Check

© Siemens, 2006 CT00-000.843.08.07.02 Page 13 of 57 Common CT

For Somaris/5 VB30/38/39 (excluding VB38B_SP4) only:

For Somaris/5 VB30/38/39 only:

2.1.4 SRS configuration part 3 - System Management configuration

 ration part 1 ( Fig. 5 Page 13).

For information only!

2.1.4.1 General information

2.1.4.2 System Management Configuration

Common CT CT00-000.843.08.07.02 Page 14 of 57 © Siemens, 2006

1. Configuring the System Management

n Select Local_Service > Configuration > System Mgmt. > AgentControls