All of these are transparent to you, as you still end up with a node that has the name you want.
所有这些对于您来说都是透明的，最终得到的是一个具有您所希望的名称的节点。
One of its purposes is to register for all notifications which occur on that cell, node, or server.
其目的之一就是注册该单元、节点或服务器上发生的所有通知。
Because node structures go in only one direction, they know nothing about the sequence of nodes that precede them.
由于节点结构只指向一个方向，所以它们完全不了解它们之前的节点的顺序。
在每个节点上部署RAR。
将显示一个节点。
The node appears in the node list.
该节点将出现在节点列表中。
Create cluster members on that node.
在该节点上创建集群成员。
Each node contains two cluster members.
每个节点包含两个集群成员。
Starts the custom node and proxy server.
启动定制节点和代理服务器。
Yeah. And what does this node look like?
太好了，那这个节点应该是怎样的呢？
选择节点作用域。
一个展开的节点。
Pick a node to be the SNMP management node.
选择一个节点作为SNMP管理节点。
This node doesn't have to be a master node.
这个节点不必是主节点。
启动节点。
Each such node can reference a content node.
每个这样的节点都可以引用一个内容节点。
Let the node reboot, and installation starts.
让节点重新启动，开始安装。
禁用节点。
启用节点。
Choose consistent patterns to apply to each node.
选择一致的模式应用到每个节点上。
Pick a GPFS cluster node to be the collector node.
选择一个GPFS集群节点作为收集器。
The capability of the node is managed at the node.
节点的功能在节点上管理。
This queue manager should be located on another node.
此队列管理器应位于另一个节点上。
Otherwise, iteration continues from the original node.
否则，迭代将从原始节点处继续。
Of course, not all node types have all these properties.
当然，并非所有节点类型都具有所有这些属性。
Copy directories and files from main node to the clone node.
将目录与文件从主节点复制到克隆节点。
Upon failure of the primary node the redundant node takes over.
在主节点发生故障时，冗余节点可以接管。
Each node can transfer data sets simultaneously to every other node.
每个节点可以同步地将数据集传输到其他节点。
A new node is created first as the only child of the container node.
首先创建的新节点作为容器节点的惟一子级。
The type of the parameter node corresponds to the node being visited.
参数节点的类型与访问节点对应。
应用推荐