Dell Precision R5400 Manuale - Pagina 13

Sfoglia online o scarica il pdf Manuale per Server Dell Precision R5400. Dell Precision R5400 25. Technical guide
Anche per Dell Precision R5400: Specifiche tecniche (2 pagine), Opuscolo (2 pagine), Manuale (13 pagine), Manuale tecnico (36 pagine)

Stampa la pagina

PCoIP Technology User Guide (Vol I)

endpoints can advertise to the primary CMS

first, and in the event of a transmit failure,

advertise to a secondary CMS.

Unlike Service Location Protocol, DNS-SRV

discovery does not use multicast IP traffic, and

as a result DNS-SRV discovery works across

subnets. Typically routers, by default, block

multicast IP traffic so the CMS cannot use SLP

to discover endpoints located on different

subnets.

DNS-SRV provides a standardized approach for

the endpoint to query the DNS server for a CMS

service.

Requirements

DNS-SRV discovery requires the following:

• DNS zone data must have a DNS-SRV RR

with the format described by RFC 2782:

_Service._Proto.Name TTL Class

SRV Priority Weight Port Target

Where:

_Service=_pcoip-broker,

_Proto=_tcp,

Name = hierarchical domain name

• Endpoint must have access to a DHCP server

in order to get the domain name and

hostname (to get DHCP options 15 and 12

respectively)

• DHCP server must support either DHCP

options 12 (hostname), 15 (domain name), or

both. If the DHCP server only supports DHCP

options 12, the hostname string must contain

the domain name.

Discovery Using Service Location

Protocol

The endpoint can be configured to use Service

Location Protocol (SLP) discovery. Depending

on the deployment, the endpoint uses SLP

discovery as follows:

Unmanaged deployments:

• Host and Portal advertise services so that

another network SLP-aware entity can

discover the endpoint

• When host discovery is enabled on Portal,

Portal dynamically discovers Hosts

Managed deployments:

TER0806003 Issue 1

• Host and Portal advertise services so that the

CMS can discover the endpoint

The endpoint uses the Service Location Protocol

(SLPv2) as defined in RFC2608. The endpoint

advertises a service to either a SLP directory

agent or an endpoint/CMS (if a Directory Agent

is not present).

SLP over Multiple Subnets

When endpoints, CMS (if present), and Directory

Agent (if present) are on the same subnet, SLP

uses multicast/broadcast SLP messaging to

when any endpoint or CMS is on a different

subnet, routers must be configured to allow

packets destined for the SLP multicast group

239.255.255.253 to pass through.

Multicast reduces network congestion by

directing SLP messages to endpoints registered

with the standard SLP multicast group. The

endpoint uses the IGMP (Internet Group

Management Protocol) to 'join' the standard SLP

multicast group. Packets sent to IP address

239.255.255.253 are multicast to the endpoints

registered with the group.

A User Agent multicasts a service request (to

the SLP multicast group) and a Service Agent

responds via a unicast connection. If the PCoIP

System is deployed over multiple subnets, the

multicast enabled routers must not filter packets

destined for the SLP multicast group

Page 13 of 25