Technical data

Architecture and System Requirements

EN4442EN00EN_0002

Siemens

Frequently, only explicitly familiar TCP/IP or UDP/IP port numbers are supported in the

customer LAN for security reasons. All others are then blocked in such cases. Precisely which

port numbers must be supported for the HiPath HG 3500 component in the network is

described in Section 16.1, “Gateway Port Allocation”.

2.4 Basic Configuration Requirements

For a HG 3500 line gateway to be operational on a live IP network the following parameters

have to be configured.

Every HG 3500 requires configuration data which must be coordinated with the network

administration of the customer, documented and configured precisely as agreed.

The following data must be specified for every new node in the customer LAN:

● IP address of the node

● Netmask for the network in which the new node is added

● Default router via which the other networks can be reached

Furthermore, the way in which Quality of Service is supported must be clarified for all networks

in which HiPath 4000 components are installed. As HiPath 4000 supports IP distributed

architecture processes for controlling the Quality of Service in a network on various protocol

layers, the following must be clarified:

● Is IEEE 802.1 p/q VLAN Tagging (Layer 2) supported?

To this end, it is crucial that all network components with which a HiPath 4000 component

communicates must support the standard and be configured accordingly. If the network

contains nodes (particularly switches and routers) which do not support IEEE 802.1 p/q,

VLAN tagging must remain deactivated. The traffic type is assigned a fixed priority value.

● If DiffServ pursuant to RFC 2474 is supported, which CodePoints can be utilized?

In the HiPath 4000 components, TOS bytes must be set to partially differing values for the

following traffic types. The default values assume DiffServ support on the part of the

network and realize the Quality of Service strategy of Siemens AG.