安装或升级参考配置文件 (RCF)
建议更改
PDF
首次设置 Nexus 3132Q-V 交换机后，请按照以下步骤安装 RCF。您也可以使用此过程升级您的 RCF 版本。
审查要求
-
交换机配置的当前备份。
-
一个功能齐全的集群（日志中没有错误或类似问题）。
-
当前参考配置文件（RCF）。
-
安装 RCF 时需要将控制台连接到交换机。如果您已使用知识库文章，则此要求为可选。 "如何在保持远程连接的情况下清除Cisco互连交换机上的配置"事先清除配置。
-
"Cisco以太网交换机"。请查阅交换机兼容性列表，了解支持的ONTAP和 RCF 版本。请注意，RCF 中的命令语法与 NX-OS 版本中的命令语法之间可能存在命令依赖关系。
-
"CiscoNexus 3000 系列交换机"。有关Cisco交换机升级和降级程序的完整文档，请参阅Cisco网站上提供的相应软件和升级指南。
安装文件
本流程中的示例使用以下开关和节点命名规则：
-
这两台Cisco交换机的名称是：
cs1`和 `cs2。 -
节点名称是
cluster1-01，cluster1-02，cluster1-03， 和cluster1-04。 -
集群 LIF 名称为
cluster1-01_clus1，cluster1-01_clus2，cluster1-02_clus1，cluster1-02_clus2，cluster1-03_clus1，cluster1-03_clus2，cluster1-04_clus1， 和cluster1-04_clus2。 -
这 `cluster1::*>`prompt 指示集群名称。
该过程需要同时使用ONTAP命令和Cisco Nexus 3000 系列交换机命令；除非另有说明，否则使用ONTAP命令。
在此过程中不需要任何可操作的交换机间链路 (ISL)。这是设计使然，因为 RCF 版本的更改可能会暂时影响 ISL 连接。为确保集群运行不中断，以下步骤将所有集群 LIF 迁移到运行伙伴交换机，同时在目标交换机上执行相应步骤。
务必完成以下步骤"准备安装 NX-OS 软件和参考配置文件"然后按照以下步骤操作。
步骤 1：检查端口状态
-
显示每个节点上连接到集群交换机的集群端口：
network device-discovery show显示示例
cluster1::*> network device-discovery show Node/ Local Discovered Protocol Port Device (LLDP: ChassisID) Interface Platform ----------- ------ ------------------------- ---------------- ------------ cluster1-01/cdp e0a cs1 Ethernet1/7 N3K-C3132Q-V e0d cs2 Ethernet1/7 N3K-C3132Q-V cluster1-02/cdp e0a cs1 Ethernet1/8 N3K-C3132Q-V e0d cs2 Ethernet1/8 N3K-C3132Q-V cluster1-03/cdp e0a cs1 Ethernet1/1/1 N3K-C3132Q-V e0b cs2 Ethernet1/1/1 N3K-C3132Q-V cluster1-04/cdp e0a cs1 Ethernet1/1/2 N3K-C3132Q-V e0b cs2 Ethernet1/1/2 N3K-C3132Q-V cluster1::*> -
检查每个集群端口的管理和运行状态。
-
确认集群所有端口均已启动且状态正常：
network port show -ipspace Cluster显示示例
cluster1::*> network port show -ipspace Cluster Node: cluster1-01 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ----------- -------- ------ e0a Cluster Cluster up 9000 auto/100000 healthy false e0d Cluster Cluster up 9000 auto/100000 healthy false Node: cluster1-02 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ----------- -------- ------ e0a Cluster Cluster up 9000 auto/100000 healthy false e0d Cluster Cluster up 9000 auto/100000 healthy false 8 entries were displayed. Node: cluster1-03 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ----------- -------- ------ e0a Cluster Cluster up 9000 auto/10000 healthy false e0b Cluster Cluster up 9000 auto/10000 healthy false Node: cluster1-04 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ----------- -------- ------ e0a Cluster Cluster up 9000 auto/10000 healthy false e0b Cluster Cluster up 9000 auto/10000 healthy false cluster1::*> -
确认所有集群接口（LIF）都位于主端口上：
network interface show -vserver Cluster显示示例
cluster1::*> network interface show -vserver Cluster Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- ------------------ ---------- ----------------- ------------ ------- ---- Cluster cluster1-01_clus1 up/up 169.254.3.4/23 cluster1-01 e0a true cluster1-01_clus2 up/up 169.254.3.5/23 cluster1-01 e0d true cluster1-02_clus1 up/up 169.254.3.8/23 cluster1-02 e0a true cluster1-02_clus2 up/up 169.254.3.9/23 cluster1-02 e0d true cluster1-03_clus1 up/up 169.254.1.3/23 cluster1-03 e0a true cluster1-03_clus2 up/up 169.254.1.1/23 cluster1-03 e0b true cluster1-04_clus1 up/up 169.254.1.6/23 cluster1-04 e0a true cluster1-04_clus2 up/up 169.254.1.7/23 cluster1-04 e0b true cluster1::*> -
确认集群显示两个集群交换机的信息：
system cluster-switch show -is-monitoring-enabled-operational true显示示例
cluster1::*> system cluster-switch show -is-monitoring-enabled-operational true Switch Type Address Model --------------------------- ------------------ ---------------- --------------- cs1 cluster-network 10.0.0.1 NX3132QV Serial Number: FOXXXXXXXGS Is Monitored: true Reason: None Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 9.3(4) Version Source: CDP cs2 cluster-network 10.0.0.2 NX3132QV Serial Number: FOXXXXXXXGD Is Monitored: true Reason: None Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 9.3(4) Version Source: CDP 2 entries were displayed.
对于ONTAP 9.8 及更高版本，请使用以下命令 system switch ethernet show -is-monitoring-enabled-operational true。 -
-
禁用集群 LIF 的自动回滚功能。
cluster1::*> network interface modify -vserver Cluster -lif * -auto-revert false
运行此命令后，请确保禁用自动还原功能。
-
在集群交换机 cs2 上，关闭连接到节点集群端口的端口。
cs2> enable cs2# configure cs2(config)# interface eth1/1/1-2,eth1/7-8 cs2(config-if-range)# shutdown cs2(config-if-range)# exit cs2# exit
显示的端口数量取决于集群中的节点数量。 -
确认集群端口已迁移到集群交换机 cs1 上托管的端口。这可能需要几秒钟。
network interface show -vserver Cluster显示示例
cluster1::*> network interface show -vserver Cluster Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- ----------------- ---------- ------------------ ------------- ------- ---- Cluster cluster1-01_clus1 up/up 169.254.3.4/23 cluster1-01 e0a true cluster1-01_clus2 up/up 169.254.3.5/23 cluster1-01 e0a false cluster1-02_clus1 up/up 169.254.3.8/23 cluster1-02 e0a true cluster1-02_clus2 up/up 169.254.3.9/23 cluster1-02 e0a false cluster1-03_clus1 up/up 169.254.1.3/23 cluster1-03 e0a true cluster1-03_clus2 up/up 169.254.1.1/23 cluster1-03 e0a false cluster1-04_clus1 up/up 169.254.1.6/23 cluster1-04 e0a true cluster1-04_clus2 up/up 169.254.1.7/23 cluster1-04 e0a false cluster1::*> -
验证集群是否运行正常：
cluster show显示示例
cluster1::*> cluster show Node Health Eligibility Epsilon -------------------- ------- ------------ ------- cluster1-01 true true false cluster1-02 true true false cluster1-03 true true true cluster1-04 true true false cluster1::*>
步骤 2：配置并验证设置
-
如果您尚未保存当前交换机配置，请将以下命令的输出复制到文本文件中：
show running-config -
记录当前运行配置和正在使用的 RCF 文件之间的任何自定义添加。
-
保存基本配置详细信息 `write_erase.cfg`启动闪存上的文件。
升级或应用新的 RCF 时，必须清除交换机设置并执行基本配置。您必须连接到交换机串行控制台端口才能重新设置交换机。 cs2# show run | section "switchname" > bootflash:write_erase.cfgcs2# show run | section "hostname" >> bootflash:write_erase.cfgcs2# show run | i "username admin password" >> bootflash:write_erase.cfgcs2# show run | section "vrf context management" >> bootflash:write_erase.cfgcs2# show run | section "interface mgmt0" >> bootflash:write_erase.cfg -
对于 RCF 版本 1.12 及更高版本，请运行以下命令：
cs2# echo "hardware access-list tcam region vpc-convergence 256" >> bootflash:write_erase.cfgcs2# echo "hardware access-list tcam region racl 256" >> bootflash:write_erase.cfgcs2# echo "hardware access-list tcam region e-racl 256" >> bootflash:write_erase.cfgcs2# echo "hardware access-list tcam region qos 256" >> bootflash:write_erase.cfg请参阅知识库文章"如何在保持远程连接的情况下清除Cisco互连交换机上的配置"更多详情请见下文。
-
确认 `write_erase.cfg`文件已按预期填充：
show file bootflash:write_erase.cfg -
问题 `write erase`清除当前已保存配置的命令：
cs2# write eraseWarning: This command will erase the startup-configuration.Do you wish to proceed anyway? (y/n) [n] y -
将之前保存的基本配置复制到启动配置中。
cs2# copy bootflash:write_erase.cfg startup-config -
重启交换机：
cs2# reloadThis command will reboot the system. (y/n)? [n] y -
使用以下传输协议之一将 RCF 复制到交换机 cs2 的 bootflash：FTP、TFTP、SFTP 或 SCP。有关Cisco命令的更多信息，请参阅相应的指南。"Cisco Nexus 3000 系列 NX-OS 命令参考"指南。
显示示例
cs2# copy tftp: bootflash: vrf management Enter source filename: Nexus_3132QV_RCF_v1.6-Cluster-HA-Breakout.txt Enter hostname for the tftp server: 172.22.201.50 Trying to connect to tftp server......Connection to Server Established. TFTP get operation was successful Copy complete, now saving to disk (please wait)...
-
将之前下载的 RCF 文件应用到启动闪存中。
有关Cisco命令的更多信息，请参阅相应的指南。"Cisco Nexus 3000 系列 NX-OS 命令参考"指南。
显示示例
cs2# copy Nexus_3132QV_RCF_v1.6-Cluster-HA-Breakout.txt running-config echo-commands
-
检查横幅输出 `show banner motd`命令。您必须阅读并遵循“重要提示”下的说明，以确保交换机的正确配置和运行。
显示示例
cs2# show banner motd ****************************************************************************** * NetApp Reference Configuration File (RCF) * * Switch : Cisco Nexus 3132Q-V * Filename : Nexus_3132QV_RCF_v1.6-Cluster-HA-Breakout.txt * Date : Nov-02-2020 * Version : v1.6 * * Port Usage : Breakout configuration * Ports 1- 6: Breakout mode (4x10GbE) Intra-Cluster Ports, int e1/1/1-4, * e1/2/1-4, e1/3/1-4,int e1/4/1-4, e1/5/1-4, e1/6/1-4 * Ports 7-30: 40GbE Intra-Cluster/HA Ports, int e1/7-30 * Ports 31-32: Intra-Cluster ISL Ports, int e1/31-32 * * IMPORTANT NOTES * - Load Nexus_3132QV_RCF_v1.6-Cluster-HA.txt for non breakout config * * - This RCF utilizes QoS and requires specific TCAM configuration, requiring * cluster switch to be rebooted before the cluster becomes operational. * * - Perform the following steps to ensure proper RCF installation: * * (1) Apply RCF, expect following messages: * - Please save config and reload the system... * - Edge port type (portfast) should only be enabled on ports... * - TCAM region is not configured for feature QoS class IPv4... * * (2) Save running-configuration and reboot Cluster Switch * * (3) After reboot, apply same RCF second time and expect following messages: * - % Invalid command at '^' marker * * (4) Save running-configuration again * * - If running NX-OS versions 9.3(5) 9.3(6), 9.3(7), or 9.3(8) * - Downgrade the NX-OS firmware to version 9.3(5) or earlier if * NX-OS using a version later than 9.3(5). * - Do not upgrade NX-OS prior to applying v1.9 RCF file. * - After the RCF is applied and switch rebooted, then proceed to upgrade * NX-OS to version 9.3(5) or later. * * - If running 9.3(9) 10.2(2) or later the RCF can be applied to the switch * after the upgrade. * * - Port 1 multiplexed H/W configuration options: * hardware profile front portmode qsfp (40G H/W port 1/1 is active - default) * hardware profile front portmode sfp-plus (10G H/W ports 1/1/1 - 1/1/4 are active) * hardware profile front portmode qsfp (To reset to QSFP) * ******************************************************************************
-
请确认 RCF 文件是否为最新版本：
show running-config检查输出结果以验证是否拥有正确的 RCF 时，请确保以下信息正确：
-
RCF横幅
-
节点和端口设置
-
定制
输出结果会根据您的网站配置而有所不同。检查端口设置，并参考发行说明，了解您安装的 RCF 版本是否有任何特定更改。
有关在 RCF 升级后如何将 10GbE 端口上线的步骤，请参阅知识库文章。 "Cisco 3132Q 集群交换机上的 10GbE 端口无法联机" 。 -
-
确认 RCF 版本和交换机设置正确后，将运行配置文件复制到启动配置文件。
有关Cisco命令的更多信息，请参阅 "Cisco Nexus 3000 系列 NX-OS 命令参考"指南。
显示示例
cs2# copy running-config startup-config [########################################] 100% Copy complete
-
重启交换机cs2。您可以忽略交换机重启期间节点上报告的“集群端口关闭”事件和错误。 `% Invalid command at '^' marker`输出。
显示示例
cs2# reload This command will reboot the system. (y/n)? [n] y
-
应用相同的 RCF 并再次保存运行配置。这是必要的，因为 RCF 利用 QoS，需要重新配置 TCAM，这涉及到对 RCF 进行两次加载，中间需要重启交换机。
显示示例
cs2# copy Nexus_3132QV_RCF_v1.6-Cluster-HA-Breakout.txt running-config echo-commands cs2# copy running-config startup-config [########################################] 100% Copy complete
-
将之前对交换机配置所做的任何自定义设置重新应用。请参阅"审查布线和配置注意事项"有关任何后续变更的详细信息。
-
检查集群上集群端口的运行状况。
-
确认集群中所有节点的集群端口均已启动且运行状况良好：
network port show -ipspace Cluster显示示例
cluster1::*> network port show -ipspace Cluster Node: cluster1-01 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ----------- -------- ------ e0a Cluster Cluster up 9000 auto/10000 healthy false e0b Cluster Cluster up 9000 auto/10000 healthy false Node: cluster1-02 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ----------- -------- ------ e0a Cluster Cluster up 9000 auto/10000 healthy false e0b Cluster Cluster up 9000 auto/10000 healthy false Node: cluster1-03 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ----------- -------- ------ e0a Cluster Cluster up 9000 auto/100000 healthy false e0d Cluster Cluster up 9000 auto/100000 healthy false Node: cluster1-04 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ----------- -------- ------ e0a Cluster Cluster up 9000 auto/100000 healthy false e0d Cluster Cluster up 9000 auto/100000 healthy false -
从集群中验证交换机的运行状况。
network device-discovery show -protocol cdp显示示例
cluster1::*> network device-discovery show -protocol cdp Node/ Local Discovered Protocol Port Device (LLDP: ChassisID) Interface Platform ----------- ------ ------------------------- ----------------- -------- cluster1-01/cdp e0a cs1 Ethernet1/7 N3K-C3132Q-V e0d cs2 Ethernet1/7 N3K-C3132Q-V cluster01-2/cdp e0a cs1 Ethernet1/8 N3K-C3132Q-V e0d cs2 Ethernet1/8 N3K-C3132Q-V cluster01-3/cdp e0a cs1 Ethernet1/1/1 N3K-C3132Q-V e0b cs2 Ethernet1/1/1 N3K-C3132Q-V cluster1-04/cdp e0a cs1 Ethernet1/1/2 N3K-C3132Q-V e0b cs2 Ethernet1/1/2 N3K-C3132Q-V cluster1::*> system cluster-switch show -is-monitoring-enabled-operational true Switch Type Address Model --------------------------- ------------------ ---------------- ----- cs1 cluster-network 10.233.205.90 N3K-C3132Q-V Serial Number: FOXXXXXXXGD Is Monitored: true Reason: None Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 9.3(4) Version Source: CDP cs2 cluster-network 10.233.205.91 N3K-C3132Q-V Serial Number: FOXXXXXXXGS Is Monitored: true Reason: None Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 9.3(4) Version Source: CDP 2 entries were displayed.
对于ONTAP 9.8 及更高版本，请使用以下命令 system switch ethernet show -is-monitoring-enabled-operational true。
根据交换机上先前加载的 RCF 版本，您可能会在 cs1 交换机控制台上看到以下输出：
2020 Nov 17 16:07:18 cs1 %$ VDC-1 %$ %STP-2-UNBLOCK_CONSIST_PORT: Unblocking port port-channel1 on VLAN0092. Port consistency restored. 2020 Nov 17 16:07:23 cs1 %$ VDC-1 %$ %STP-2-BLOCK_PVID_PEER: Blocking port-channel1 on VLAN0001. Inconsistent peer vlan. 2020 Nov 17 16:07:23 cs1 %$ VDC-1 %$ %STP-2-BLOCK_PVID_LOCAL: Blocking port-channel1 on VLAN0092. Inconsistent local vlan.+
集群节点最多可能需要 5 分钟才能报告为健康状态。 -
-
在集群交换机 cs1 上，关闭连接到节点集群端口的端口。
显示示例
cs1> enable cs1# configure cs1(config)# interface eth1/1/1-2,eth1/7-8 cs1(config-if-range)# shutdown cs1(config-if-range)# exit cs1# exit
显示的端口数量取决于集群中的节点数量。 -
确认集群 LIF 已迁移到交换机 cs2 上托管的端口。这可能需要几秒钟。
network interface show -vserver Cluster显示示例
cluster1::*> network interface show -vserver Cluster Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- ------------------ ---------- ------------------ ------------------- ------- ---- Cluster cluster1-01_clus1 up/up 169.254.3.4/23 cluster1-01 e0d false cluster1-01_clus2 up/up 169.254.3.5/23 cluster1-01 e0d true cluster1-02_clus1 up/up 169.254.3.8/23 cluster1-02 e0d false cluster1-02_clus2 up/up 169.254.3.9/23 cluster1-02 e0d true cluster1-03_clus1 up/up 169.254.1.3/23 cluster1-03 e0b false cluster1-03_clus2 up/up 169.254.1.1/23 cluster1-03 e0b true cluster1-04_clus1 up/up 169.254.1.6/23 cluster1-04 e0b false cluster1-04_clus2 up/up 169.254.1.7/23 cluster1-04 e0b true cluster1::*> -
验证集群是否运行正常：
cluster show显示示例
cluster1::*> cluster show Node Health Eligibility Epsilon -------------------- -------- ------------- ------- cluster1-01 true true false cluster1-02 true true false cluster1-03 true true true cluster1-04 true true false 4 entries were displayed. cluster1::*>
-
在交换机 cs1 上重复步骤 1 至 17。
-
启用集群 LIF 的自动回滚功能。
显示示例
cluster1::*> network interface modify -vserver Cluster -lif * -auto-revert True
-
重启交换机cs1。这样做是为了触发集群 LIF 恢复到它们的源端口。交换机重启期间，您可以忽略节点上报告的“集群端口关闭”事件。
cs1# reload This command will reboot the system. (y/n)? [n] y
步骤 3：验证配置
-
确认连接到集群端口的交换机端口已开启。
show interface brief | grep up显示示例
cs1# show interface brief | grep up . . Eth1/1/1 1 eth access up none 10G(D) -- Eth1/1/2 1 eth access up none 10G(D) -- Eth1/7 1 eth trunk up none 100G(D) -- Eth1/8 1 eth trunk up none 100G(D) -- . .
-
验证 cs1 和 cs2 之间的 ISL 连接是否正常：
show port-channel summary显示示例
cs1# show port-channel summary Flags: D - Down P - Up in port-channel (members) I - Individual H - Hot-standby (LACP only) s - Suspended r - Module-removed b - BFD Session Wait S - Switched R - Routed U - Up (port-channel) p - Up in delay-lacp mode (member) M - Not in use. Min-links not met -------------------------------------------------------------------------------- Group Port- Type Protocol Member Ports Channel -------------------------------------------------------------------------------- 1 Po1(SU) Eth LACP Eth1/31(P) Eth1/32(P) cs1# -
确认集群 LIF 已恢复到其原端口：
network interface show -vserver Cluster显示示例
cluster1::*> network interface show -vserver Cluster Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- ------------------ ---------- ------------------ ------------------- ------- ---- Cluster cluster1-01_clus1 up/up 169.254.3.4/23 cluster1-01 e0d true cluster1-01_clus2 up/up 169.254.3.5/23 cluster1-01 e0d true cluster1-02_clus1 up/up 169.254.3.8/23 cluster1-02 e0d true cluster1-02_clus2 up/up 169.254.3.9/23 cluster1-02 e0d true cluster1-03_clus1 up/up 169.254.1.3/23 cluster1-03 e0b true cluster1-03_clus2 up/up 169.254.1.1/23 cluster1-03 e0b true cluster1-04_clus1 up/up 169.254.1.6/23 cluster1-04 e0b true cluster1-04_clus2 up/up 169.254.1.7/23 cluster1-04 e0b true cluster1::*> -
验证集群是否运行正常：
cluster show显示示例
cluster1::*> cluster show Node Health Eligibility Epsilon -------------------- ------- ------------- ------- cluster1-01 true true false cluster1-02 true true false cluster1-03 true true true cluster1-04 true true false cluster1::*>
-
验证远程集群接口的连接性：
你可以使用 `network interface check cluster-connectivity`执行命令以启动集群连接性检查，然后显示详细信息：
network interface check cluster-connectivity start`和 `network interface check cluster-connectivity show
cluster1::*> network interface check cluster-connectivity start
*注意：*运行 show 命令显示详细信息之前，请等待几秒钟。
cluster1::*> network interface check cluster-connectivity show
Source Destination Packet
Node Date LIF LIF Loss
------ -------------------------- ------------------- ------------------- -----------
cluster1-01
3/5/2022 19:21:18 -06:00 cluster1-01_clus2 cluster1-02_clus1 none
3/5/2022 19:21:20 -06:00 cluster1-01_clus2 cluster1-02_clus2 none
cluster1-02
3/5/2022 19:21:18 -06:00 cluster1-02_clus2 cluster1-01_clus1 none
3/5/2022 19:21:20 -06:00 cluster1-02_clus2 cluster1-01_clus2 none
对于所有ONTAP版本，您也可以使用 `cluster ping-cluster -node <name>`检查连接性的命令：
cluster ping-cluster -node <name>
cluster1::*> cluster ping-cluster -node local
Host is cluster1-02
Getting addresses from network interface table...
Cluster cluster1-01_clus1 169.254.209.69 cluster1-01 e0a
Cluster cluster1-01_clus2 169.254.49.125 cluster1-01 e0b
Cluster cluster1-02_clus1 169.254.47.194 cluster1-02 e0a
Cluster cluster1-02_clus2 169.254.19.183 cluster1-02 e0b
Local = 169.254.47.194 169.254.19.183
Remote = 169.254.209.69 169.254.49.125
Cluster Vserver Id = 4294967293
Ping status:....
Basic connectivity succeeds on 4 path(s)
Basic connectivity fails on 0 path(s)
................
Detected 9000 byte MTU on 4 path(s):
Local 169.254.19.183 to Remote 169.254.209.69
Local 169.254.19.183 to Remote 169.254.49.125
Local 169.254.47.194 to Remote 169.254.209.69
Local 169.254.47.194 to Remote 169.254.49.125
Larger than PMTU communication succeeds on 4 path(s)
RPC status:
2 paths up, 0 paths down (tcp check)
2 paths up, 0 paths down (udp check)