B.4.3.2 Additional Protocols

B.4.3.2 Additional Protocols (Current)
Prev	B.4.3 Network Interfaces	Next

EXAMPLE-INTEGRATED-MODLALITY conforms to the System Management Profiles listed in the Table below. All requested transactions for the listed profiles and actors are supported. Support for optional transactions are listed in the Table below:

Table B.4.3-2. Supported System Management Profiles

Profile Name	Actor	Protocols Used	Optional Transactions	Security Support
Network Address Management	DHCP Client	DHCP	N/A
Network Address Management	DNS Client	DNS	N/A
Time Synchronization	NTP Client	NTP	Find NTP Server
Time Synchronization	DHCP Client	DHCP	N/A
DICOM Application Configuration Management	LDAP Client	LDAP	Client Update LDAP Server	See Section B.7

B.4.3.2.1 DHCP

DHCP can be used to obtain TCP/IP network configuration information. The network parameters obtainable via DHCP are shown in the Table below. The Default Value column of the table shows the default used if the DHCP server does not provide a value. Values for network parameters set in the Service/Installation tool take precedence over values obtained from the DHCP server. Support for DHCP can be configured via the Service/Installation Tool. The Service/Installation tool can be used to configure the machine name. If DHCP is not in use, TCP/IP network configuration information can be manually configured via the Service/Installation Tool.

Table B.4.3-3. Supported DHCP Parameters

DHCP Parameter	Default Value
IP Address	None
Hostname	Requested machine name
List of NTP servers	Empty list
List of DNS servers	Empty list
Routers	Empty list
Static routes	None
Domain name	None
Subnet mask	Derived from IP Address (see service manual)
Broadcast address	Derived from IP Address (see service manual)
Default router	None
Time offset	Site configurable (from Timezone)
MTU	Network Hardware Dependent
Auto-IP permission	No permission

If the DHCP server refuses to renew a lease on the assigned IP address all active DICOM Associations will be aborted.