DICOM PS3.2 2018a - Conformance

H.4.3.2 Additional Protocols
Prev | H.4.3 Network Interfaces | Next

#### H.4.3.2 Additional Protocols

EXAMPLE-MEDICATION-SYSTEM-GATEWAY conforms to the System Management Profiles listed in Table F.4.3-2. All requested transactions for the listed profiles and actors are supported. It does not support any optional transactions.

Table H.4.3-2. Supported System Management Profiles

Profile Name | Actor | Protocols Used | Optional Transactions | Security Support
--- | --- | --- | --- | ---
Network Address Management | DHCP Client | DHCP | N/A |
DNS Client | DNS | N/A |

##### H.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 Table F.4.3-3. 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 H.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 Time zone)
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.

Prev | Up | Next
H.4.3 Network Interfaces | Home | H.4.3.2.2 DNS

DICOM PS3.2 2018a - Conformance