Symptoms

Configure BMC and use a LAN or WAN interface and specify an IP that is previously used in the network in error.BMC can be configured to use LAN or WAN ethernet on RecoverPoint, thus can access the network RPA interfaces are on. If, by mistake, a duplicate IP is configured in BMC, RPA will propagate a mac-address and cause conflicts.In the example below, it shows BMC configured with LAN IP on WAN ethernet. It reulted in RPA to have an intermittent connection to VNX IPs: Cluster Name has a connectivity problem with managed array StorageName for these RPAs [RPA2] Naviseccli was intermittent in output; sometimes it works and sometimes it gives the below error: RecoverPoint-0x1c26edfsderdsfg-RPA2:/home/kos/navi# ./naviseccli -h 192.168.x.x -User admin -Password password -Scope 0 -Timeout 30 getagent10.188.71.Error occurred during response from the targetMessage : Socket stream invalidError occurred during HTTP request/response from the target: '192.168.x.x'.Message : End of data streamExit 255 Collecting TCPdump from eth1 showed that a duplicate IP appears, meaning the same IP but two different mac-addresses. The mac-address that was causing the issue had the value of 00:60:16:XX:XX:XX and it does not show up on any interface for command ip addrs show or ifconfig -a The value 00:60:16 at the start of Mac-address points to a EMC/DELL device.

Cause

BMC can now be configured on a RPA and use LAN or LAN Ethernet and will not show in system interface commands, it assigns a mac-address to it once created, and shows up in arp requests for WAN and LAN requests, if configured with an IP on the same network as WAN or LAN.

Resolution

Workaround: In version 5.1 and earlier, connect as boxmgmt.Go to > 2 Setup > 8 Advanced > 14 BMC > 2 Configure The below wizard then shows to specify an IP that will not cause conflict. SiteName RPA 2: 11. WAN2. LAN3. Dedicated BMC interfaceSelect BMC interface (1 to 3): 1** iDRAC Settings **MAC address: 00:60:16:xx:xx.xxIP Version Information: !IDRAC_ENABLED!NoIP address: 1.1.1.1Netmask: 255.255.255.0!GATEWAY!1.1.1.1DHCP enabled: No

Support Cases