Hardware-Assisted Takeover Support On Systems That Use Service Processor; Corrections To The Example In "Monitoring Ha Pair Status" Topic; Changes To The Network Management Guide; Changes To Information About Routed Daemon - IBM N Series Manual

Hardware-assisted takeover support on systems that use Service
Processor
Although the Data ONTAP 8.0 7-Mode High-Availability Configuration Guide
only mentions support for the hardware-assisted takeover feature on systems
with an RLM card, the feature is also supported on systems that use a Service
Processor for remote management.

Corrections to the example in "Monitoring HA pair status" topic

The cf status command output in the "Monitoring HA pair status" topic
does not provide information about the two links that constitute the HA
interconnect.
The example should read as follows:
Example
node1>cf status
Cluster enabled, node2 is up
RDMA Interconnect is up (Link 0 down, Link 1 up)
Note: Depending on the storage system model, the output might display
either RDMA interconnect or VIA interconnect in the last line.
Note: If the output shows that one link is down, you must configure the link
so that it is up while the other link is still active.

Changes to the Network Management Guide

New information has become available since the previous revision of the Data
ONTAP 8.0 7-Mode Network Management Guide.
v "Changes to information about routed daemon"
v "Supported SNMP versions in Data ONTAP" on page 134
v "TLS not supported in Data ONTAP 8.0" on page 134

Changes to information about routed daemon

The topic titled "When the routed daemon should be turned off" contains
incorrect information. In addition, the topic titled "The routed daemon" is
updated for information about RIPv2 authentication if routed daemon is on.
The information in the topic "When the routed daemon should be turned off"
is corrected as follows:
Unless you have dynamic routing requirements and understand network
routing configuration, you are advised to always keep the routed daemon
off. If you have dynamic routing requirements, you are advised to turn the
Changes to published documentation
133