Collapse AllExpand All

2.2.4. Network Data Previous topic Parent topic Child topic Next topic

This feature is used to configure additional nodes/IP gateways in the customer LAN. Every node/IP gateway 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/IP gateway 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 OpenScape 4000 components are installed. As OpenScape 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 an OpenScape 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 OpenScape 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. For more information on the TOS baytes please refer to Section 2.4.1, “TOS Byte”.
    There are a number of other common prioritization methods, which are managed in the affected routers:
  • Prioritization based on the IP address
  • The entire traffic from an interface is given (identical) priority. Traffic from IPDA components can thus be given a higher priority than other traffic by specifying the IP address.
  • Prioritization of a port (socket) range
  • In this case, the IPDA-specific ports (see Chapter 20, “IP Ports”) are given a higher priority than other ports in the network.
    It is essential that the signaling and payload ports be taken into account here. This method is not recommended given the size of the port range for payload.
  • Prioritization of specific services (TCP, UDP)
  • Although prioritization of UDP traffic, for example, in the network would have a positive effect on the payload, it would restrict signaling (TCP/IP). This type of signaling is therefore NOT suitable for IPDA. It impairs system availability.