Siemens Remote Service Software Installation of SRS
Siemens Remote Service Software Installation of SRS
e
s
o
M
Software
System
Installation of SRS
08380490
08080017
06601970
05756130
05756122
© Siemens AG 2003
The reproduction, transmission or use
of this document or its contents is not
permitted without express written
authority. Offenders will be liable for
damages. All rights, including rights
created by patent grant or registration
of a utility model or design, are
reserved.
Disclaimer
The installation and service of equipment described herein is to be performed by qualified
personnel who are employed by Siemens or one of its affiliates or who are otherwise
authorized by Siemens or one of its affiliates to provide such services.
Assemblers and other persons who are not employed by or otherwise directly affiliated
with or authorized by Siemens or one of its affiliates are directed to contact one of the
local offices of Siemens or one of its affiliates before attempting installation or service pro-
cedures.
Document description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
General and product-specific safety hints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Screenshots & graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Configuration of VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
8 _______ Troubleshooting________________________________________________ 38
This document describes where information can be obtained and where an active config-
uration has to be performed for Siemens Remote Service on syngo and Fluorospot Com-
pact systems.
Follow the guidelines of general and product-specific safety information when performing
maintenance and service work.
Additional information 0
For more information about Siemens Remote Service, the router, and the SRS server
concept, refer to "SRS Connectivity Toolkit" on the CS homepage http://cs.med.sie-
mens.de.
Three worldwide access servers make your system accessible to Siemens Remote Ser-
vice.
System management servers are located in the SRS server environment in Europe, Asia
and America. Systems report to these servers with statistical quality data and escalate
cases involving severe malfunction of the SP system.
In many countries, the SP system currently has to dial out internationally to contact the
server, e.g., for auto-reporting or system management reporting. For this reason, toll-free
numbers for accessing the servers have been established.
A personal account is required on the SRS portal to access data and to connect to sys-
tems. For accounts, contact your service center.
SP products are only designed for a router or VPN (Virtual Private Network) connection.
Router connection 0
The phone line must be a direct analog or ISDN line (not a switchboard). The phone
extension should allow international dial-in and dial-out calls to support the new SRS
server concept.
VPN 0
SRS over a VPN connection (Internet) requires a static IP address for the customer's end
point.
Network 0
An appropriate IP network address range within the customer LAN is required to connect
the router/VPN to the modality.
Router hardware 0
A current router hardware list and order form are available in the intranet under SRS Con-
nectivity Toolkit (http://cs.med.siemens.de).
To connect to an analog router, a country-specific modem is necessary. For detailed infor-
mation, refer to the SRS Planning Guide, SRS Connectivity Toolkit (http://cs.med.sie-
mens.de).
Router administration 0
1. The modality and the hospital SRS router are in the same subnet area.
Refer to paragraph.
2. The modality is on a different subnet area than the hospital SRS router.
The hospital network administrator configures the default gateway (example
192.168.170.1 to access the SRS access server in Fürth (Germany)).
Fig. 2: Modality and hospital SRS router not in the same subnet
The modality and the hospital SRS router are in the same subnet 0
For configuration, the hospital network administrator does not have to be involved.
Explanation:
The syngo system 157.163.200.222 uses the static route to the hospital SRS router
157.163.200.232 to reach the SRS access server 194.138.39.0 (Fürth, Timezone I) with-
out using the local gateway. The -p stands for permanent route.
NOTE Alternative: Configure the hospital SRS router as the default gate-
way under TCP/IP LAN gateways if the customer is not using a de-
fault gateway.
• In order to save the data, write down the line showing the route to the SRS target server
The modality and hospital SRS router are not in the same subnet 0
The hospital network administrator has to configure the default gateway for connectivity to
the SRS access server. This is done in conjunction with the SRS Help Desk (CHS IN,
Customer Health Service Imaging Network)
NOTE Only one gateway entry can be defined. Therefore, this procedure
applies to customers with only one default gateway used with the
syngo system.
• Enter the default gateway IP address for the local TCP/IP LAN parameter via "Network
connection" (FLC-based) or Configuration/TCP/IP LAN (syngo-based).
• Perform a connectivity test as described in the "Troubleshooting" section of this docu-
ment.
The modality (syngo system) is entered in the SRS database during router configuration
by the SRS Help Desk (CHS IN Customer Health Service Imaging Network) or the
responsible person in the country. The basis for the entry is the SRS checklist (R=refer to
the SRS Connectivity Toolkit on the intranet, http://cs.med.siemens.de/SRSToolkit)
2. Router configuration 0
The router is configured by the Siemens SRS Help Desk (CHS IN) or, if a customer router
exists, by the customer in conjunction with the Siemens SRS Help Desk (CHS IN). The
basis for the entry is the SRS checklist (refer to the SRS Connectivity Toolkit on the intra-
net, http://cs.med.siemens.de/SRSToolkit).
The Siemens remote access mode setting is not covered by the Backup & Restore func-
tion. After SW installation, the Siemens remote access mode has to be selected. For
syngo-based systems, select Options/Service/Remote service.
NOTE Depending on your syngo version and the system language, the
service options may differ slightly.
• Options/Remote service
• Options/Service/Remote service
• Options/Remote service
• Options/Service/Remote service
1. The modality and the hospital SRS router are in the same subnet area.
Refer to paragraph 4.1
2. The modality is on a different subnet area than the hospital SRS router.
Refer to paragraph 4.2
The hospital network administrator configures the default gateway 192.168.170.1 to
access the SRS access server in Fürth (Germany).
Fig. 5: Modality and hospital SRS router not in the same subnet
4.1 The modality and the hospital SRS router are in the same subnet
For configuration, the hospital network administrator does not have to be involved.
Explanation:
The syngo system 157.163.200.222 uses the static route to the hospital SRS router
157.163.200.232 to reach the SRS access server 194.138.39.0 (Fürth, Timezone I) with-
out using the local gateway. The -p stands for permanent route.
NOTE Alternative: Configure the hospital SRS router as the default gate-
way under TCP/IP LAN gateways if the customer is not using a de-
fault gateway.
• In order to save the data, write down the line showing the route to the SRS target server
• Perform the connectivity test described in section 5 of this chapter, SRS - configuration
4.2 The modality and hospital SRS router are not in the same subnet
The hospital network administrator has to configure the default gateway for the connec-
tivity to the SRS access server. This is done in conjunction with the SRS Help Desk (CHS
IN, Customer Health Service Imaging Network)
NOTE Only one gateway entry can be defined. Therefore, this procedure
applies to customers with only one default gateway used with the
syngo system.
Fig. 6: Gateway
• Click "Save" and "Home" and accept the reboot.
5. Connectivity test 0
Check the connectivity from the modality to the SRS access server.
Procedure:
• Enable the remote access mode for "Limited Access" or "Limited Access Permanent".
• Select "Utilities" from Service software/Local service/Home menu.
Time zone I (Europe, Africa) tracert 194.138.39.18 Trace route to the Fürth extranet
Time zone II (America) tracert 129.73.116.92 Trace route to the Newark extranet
Time zone III (Asia, Australia) tracert 194.138.243.178 Trace route to the Singapore extranet
NOTE A telephone line may need some time to establish the connection.
As a result, the tracert program may time out and output "Destina-
tion host is unreachable" or "Request time-out". Repeat the tracert
command and check the connection again.
Fig. 7: tracert ok
The tracert 194.138.39.18 command performs a connection test to the SRS server in the
Fürth extranet. All gateways used between the syngo system and the SRS router are
listed. In our example, gateway 157.163.200.223 is used to connect the SP syngo system
with the SRS router in Fürth.
What to do if the tracert command times out:
In some cases remote service uses data for the country code and customer ID.
Under Local service/Configuration/Site info, enter the following data:
• Country code "DE=Germany"
• Customer ID, 7 digits of the local customer ID
• Click "Save".
6.1. Configuration of the SRS target (host) used for FTP service
• Go to local service.
• Select "Configuration".
• On the configuration navigation page, select "FTP".
9. Autoreport 0
Refer to the specific product description. The default is that no "Autoreport" function is
used.
Prerequisites
The CS knowledge base is accessible from the syngo system for systems connected via a
router (analog or ISDN) or via VPN to the SRS server.
The SRS access server has to be configured as the proxy server in Internet Explorer.
Perform the Internet Explorer setup as described below.
• Enter Ctrl + N on the keyboard to open a new browser window via the taskbar or open
the browser by entering "iexplorer" in the command line (Utilities/Escape to OS).
• Enable "Use the same proxy server for all protocols" and save the entry with "OK".
• Bypass the subsequent pages with "OK" to access the CS knowledge base.
• Set the remote access mode to limited access or limited access permanent.
• Open local service by selecting Options/Local service or Options/Service/Local service.
• The service login platform is displayed. Enter Ctrl + N on the keyboard to open a new
browser window with the taskbar.
• Enter the address https://www-tdkb.med.siemens.de
• Reply to the security alert message window with "OK".
General 0
VPN stands for virtual private network. A “tunnel” is built up via the Internet between the
SRS server and the customer system. The beginning and end of this tunnel are defined
by so-called Internet security end points (security end points = IP addresses).
The SRS configuration for VPN is identical to the SRS configuration. Under VPN the
default gateway points to the Internet security end points instead of the SRS router, in
case of a router connection.
Configuration 0
The configuration of VPN is performed by the hospital network administrator and the Sie-
mens company responsible (e.g., SRS team from CHS IN (Customer Health Service
Imaging Network).
The basis for the entry is the SRS checklist.
The SRS checklist is available on the intranet:
CS homepage/SRS Connectivity Toolkit
The network administrator defines the hospital routing and provides the default gateway
used by the syngo system to reach the Internet security end point.
• This gateway has to be entered as the default gateway or as a static route if a default
gateway is already in use by the syngo system. Also refer to the SRS configuration sec-
tions in this document.
The Siemens company responsible enters the configuration parameters for the SRS
server and checks the connection.
The modality (syngo system) is entered in the SRS database during router configuration
by the SRS Help Desk (CHS IN Customer Health Service Imaging Network) or the
responsible person in the country. The basis for the entry is the SRS checklist (refer to the
SRS Connectivity Toolkit on the intranet, http://cs.med.siemens.de/SRSToolkit)
2. Router configuration 0
The router is configured by the Siemens SRS Help Desk (CHS IN) or, if a customer router
exists, by the customer in conjunction with the Siemens SRS Help Desk (CHS IN). The
basis for the entry is the SRS checklist (refer to the SRS Connectivity Toolkit on the intra-
net, http://cs.med.siemens.de/SRSToolkit).
Some service forms for Siemens Remote Service require customer data such as country
code and customer ID. Enter all appropriate data under XCU/Customer data using the
SSW (service software XCU).
• In the XCS-SSW, enter <Info> <Customer Data> and at least data for:
Part of the initial start-up of the product, e.g., for UROSKOP Access, SPL5-330.815...
- Customer Name:
- Country Code:
- Customer No:
- Site Ident No:
- System Serial No:
- System Part No:
1. The modality and the hospital SRS router are in the same subnet area.
Fig. 21: Modality and hospital SRS router in the same subnet
2. The modality is on a different subnet area than the hospital SRS router.
The hospital network administrator configures the default gateway (example
192.168.170.1 to access the SRS access server in Fürth (Germany)).
Fig. 22: Modality and hospital SRS router not in the same subnet
4.1 The modality and the hospital SRS router are in the same subnet
For configuration, the hospital network administrator does not have to be involved.
Explanation:
The syngo system 157.163.200.222 uses the static route to the hospital SRS router
157.163.200.232 to reach the SRS access server 194.138.39.0 (Fürth, time zone I) with-
out using the local gateway. The -p stands for permanent route.
NOTE Alternative: Configure the hospital SRS router as the default gate-
way under TCP/IP LAN gateways if the customer is not using a de-
fault gateway.
• In order to save the data, write down the line showing the route to the SRS target server
• Perform the connectivity test described in section 5 of this chapter, SRS - configuration
4.2 The modality and hospital SRS router are not in the same subnet
The hospital network administrator has to configure the default gateway for connectivity
to the SRS access server. This is done in conjunction with the SRS Help Desk (CHS IN,
Customer Health Service Imaging Network)
NOTE Only one gateway entry can be defined. Therefore, this procedure
applies to customers with only one default gateway used with the
syngo system.
5. Connectivity test 0
Check the connectivity from the modality to the SRS access server.
Procedure:
• In the service menu, press "Ctrl" and "ESC" at the same time.
• Select Start/Programs/Command prompt.
• Enter the following bold parameters, depending on the modalities of the access server
configuration:
Time zone I (Europe, Africa) tracert 194.138.39.18 Trace route to the Fürth extranet
Time zone II (America) tracert 129.73.116.92 Trace route to the Newark extranet
Time zone III (Asia, Australia) tracert 194.138.243.178 Trace route to the Singapore extranet
NOTE A telephone line may need some time to establish the connection.
As a result, the tracert program may time out and output "Destina-
tion host is unreachable" or "Request time-out". Repeat the tracert
command and check the connection again.
6.1. Configuration of the SRS target (host) used for FTP service
• In the service menu, select <Configuration><RDIAG>.
• Enter the SRS access server name from the table below.
• Enter the SRS access server IP address from the table below.
8. Autoreport 0
Refer to the specific product description. The default is that no "Autoreport" function is
used.
9. System management 0
The system management functionalities are available (CA Unicenter) for UROSKOP
Access FLC VE20 and higher and LITHOSKOP VE20 and higher.
The FLC imaging software contains the "Manage Node Package" for system manage-
ment.
System management configuration is therefore recommended.The enabled event man-
agement service continuously sends critical system information to the System Manage-
ment Center.The CA Unicenter servers are located in the SRS environment in Fürth,
Newark, and Singapore.
NOTE Before you open the system management tab card, the site-specif-
ic configuration of network data (local IP address) has to be com-
pleted and a system reboot must be performed.
Otherwise an incorrect IP address is adopted during system man-
agement installation!
Prerequisite
The SRS connectivity from the modality to the Siemens remote environment in your time
zone is available and tested.
A wideband connection via VPN should be used in particular.
Procedure
• Open the service menu.
• Select <System><System settings><Backup> and back up the configuration to a
blank CDR.
• Select <System><System management> in the service menu.
• Under Location of the system management server, select your time zone.
• The current local IP address of your system is shown under "Network adapter TCP/ IP".
• If NAT (Network Access Translation) is used, mark the "Network Access Translation"
checkbox and enter the IP address under "NAT TCP/IP address".
Fig. 23:
• Click <Ping> to check the connectivity to the SRS environment.
¹ Because of the reaction time of the router connectivity, repeat this step as appli-
cable.
Fig. 24:
• Start the installation with <Apply>.
¹ A DOS window appears. The installation takes about 25-30 minutes. A message
box prompts you to "Reboot the system".
During the reboot, the system-specific template is transferred within 15 minutes
from the system management server to the system.
• After the system reboot, open the service menu.
• Select <System><System management>.
¹ The system management status must be set to "Running" and a template ver-
sion must be visible within 15 min. of the system reboot.
Fig. 25:
Troubleshooting
If the system management installation fails, system management deinstallation is carried
out automatically.
Check the configured network data and XCS customer data again, check whether the
system management server is reachable (ping command), and attempt installation again.
More information is available in the log files accessible via "Show all logs" or contact the
SRS Help Desk.
Assume the figure below displays an example configuration of a customer. The modality
reports via the customer router 157.163.200.223 (syngo system and router are in the
same network) to the SRS server in Fürth/Germany, IP 194.138.39.18.
Error example 1:
The modality cannot reach the SRS router at the customer site.
C:\tracert 194.138.39.18
Tracing route to 194.138.39.18 over a maximum of 30 hops.
1 * * * Request timed out
2 * * * Request timed out
n * * * Request timed out
Destination host unreachable
Trace completed
What to do:
Error example 2:
The modality can reach the customer router but not the SRS router, e.g. the SRS router in
Fürth 194.138.39.9 at HQ. The connection should be established from the modality to the
router in the hospital, to the SRS router, or to the SRS access server.
C:\tracert 194.138.39.18
Tracing route to 194.138.39.18 over a maximum of 30 hops.
1 10ms <10ms <10ms 157.163.200.223
2 * * * Request timed out
n * * * Request timed out
157.163.200.232 reports: Destination host unreachable
Trace completed
What to do:
• Contact the hospital network administrator or the responsible Siemens personnel, de-
pending on who configured the router.
• Call the Uptime Service Center for support.
Error example 3:
The modality can reach the SRS router 194.138.39.9 (e.g. Fürth) at HQ but fails to contact
the SRS access server 194.138.39.18 (e.g. Fürth).
C:\tracert 194.138.39.18
Tracing route to 194.138.39.18 over a maximum of 30 hops.
1 10ms <10ms <10ms 157.163.200.232
2 200ms <200ms <200ms 194.138.39.9
n * * * Request timed out
157.163.200.232 reports: Destination host unreachable
Trace completed
What to do:
• Call the Uptime Service Center to check the system configuration on the SRS server.
• Try again later.
IP connection to the SRS server is ok, but the functional check FTP transfer fails.
Reason for Error:
- The FTP configuration is incorrect.
- The FTP port may be blocked by the firewall in the hospital network.
What to do:
• Check SRS target (host selection).
Go to "Local service/Configuration/FTP (RDIAG)" and check the IP address for your
access server.
• Check the ftp account and password settings.
Go to Configuration FTP target --> Local service --> Configuration -->FTP (RDIAG).
FTP account: rdiagftp Password: siemens (in line 1 and 2).
• Contact the hospital administrator to check whether the FTP port is blocked.
The intranet address entered from the CS knowledge base is not reachable.
Reason for Error:
- The intranet address entered is incorrect.
- The Internet Explorer configuration is incorrect.
What to do:
• Check intranet address.
Please note: the intranet address is an “https” connection.
• Check the intranet configuration as described in the CS knowledge database section in
this document.