Dell DX6012S Kurulum ve Yapılandırma Kılavuzu - Sayfa 25

Depolama Dell DX6012S için çevrimiçi göz atın veya pdf Kurulum ve Yapılandırma Kılavuzu indirin. Dell DX6012S 43 sayfaları. Rack installation instructions — static rails
Ayrıca Dell DX6012S için: Tamamlayıcı Kılavuz (4 sayfalar), Donanım Kurulum Talimatları (2 sayfalar), Kullanıcı Kılavuzu (46 sayfalar), Kurulum ve Yapılandırma Kılavuzu (35 sayfalar), Başlangıç Kılavuzu (28 sayfalar), Uyarı (28 sayfalar), Uyarı (20 sayfalar), Genel Bakış (19 sayfalar), Yapılandırma Kılavuzu (9 sayfalar), Yapılandırma Kılavuzu (9 sayfalar), Yayın Notu (8 sayfalar), Yapılandırma Kılavuzu (7 sayfalar), Yayın Notu (6 sayfalar), Yayın Notu (5 sayfalar), Sürüm Notları (5 sayfalar), Başlangıç Kılavuzu (47 sayfalar), Kurulum (2 sayfalar), Raf Kurulumu (2 sayfalar)

the cause is unknown or a configuration or connectivity issue has been resolved, administrators

may wish to consider Republishing the subscription.

• Last Connection: the amount of time elapsed since the subscriber queried the Publisher for

stream events

• Last Transmit: the amount of time elapsed since the subscriber last retrieved at least one

stream event from the Publisher

• Republish buttons:

• Republish All: this button in the top right of the screen reruns all configured rules for all

subscribers, including any new or updated rules. It will then restart all existing subscribers.

• Subscriber Republish: this button next to each subscriber restarts the subscriber. Since the

Publisher has no way of knowing the Subscriber's status for each event, all stream events that

have been previously sent to the subscriber will be retransmitted as well as any new events.

Administrators may wish to republish a subscription if the Subscriber has failed and needs

a completely fresh list of events or, in the case of a Replicator, if there are a high number of

unexplained dropped events.

5.5. HTTP Status Reporting for Publisher and Replicator

Both the Publisher and the Replicator will provide basic status information in response to a GET

request from any HTTP client as follows:

For Publisher: GET http://<PublisherIP>:PublisherConsolePort/status

For Replicator: GET http://<ReplicatorIP>:ReplicatorConsolePort/status

The response to the request is a standard HTTP response but the response body differs slightly for

each service. All active enumerators will be included in the response in the same order with every

request. Enumerators may be deleted, however, so the index may change.

If either DX Content Router service is installed on a Cluster Services Node (CSN), the response

from the request is used to populate the SNMP MIB for the respective service on the CSN.

The data in the Publisher response corresponds to the same fields available on the Publisher

console.

[settings]

hostip={publisher ip address or host name}

sourceCluster={source cluster multicast group}

[stats]

version={publisher software version}

upTime={seconds since Publisher started}

eventsFound={number of distinct stream events heard by Publisher}

filterBacklog={number of stream events remaining to be info-ed and filtered}

diskMBAvailable={total disk space available on Publisher data store file system}

diskMBCapacity={total disk space capacity on Publisher data store file system}

cycleTime={seconds elapsed for most recent completed data store merge cycle}

cycleStart={start of current data store merge cycle}

cycleNumber={data store merge cycle count during current Publisher run}

Version 2.2

December 2010