000017775 - RSA Security Analytics core device cannot be pinged after swapping out disks to complete RMA

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Sep 24, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000017775
Applies ToRSA Product Set: Security Analytics
RSA Product/Service Type: Security Analytics Series 4S Appliance
Platform: CentOS
O/S Version: 6
Issue
  • RSA Security Analytics core device cannot be pinged after swapping out disks to complete RMA
  • Connectivity issues occur after an RSA Security Analytics Appliance RMA.
  • Appliance appears to be started normally, however, it cannot be pinged nor ping any other hosts that are even in the same subnet.
  • The ifconfig command shows no interface.
  • the dmesg command shows eth0, eth1, etc. instead of em1, em2, etc.
CauseThe OS in the new appliance is not configured to use emX as the interface name, and hence the interface becomes unavailable as it cannot locate the configuration file, ifcfg-emX.
Resolution

To resolve the issue, perform the following steps:



  1. Leave the configuration files as ifcfg-emX.
  2. Modify /etc/udev/rules.d/70-persistent-net.rules to add 'emX' to 'NAME=' for the corresponding MAC address.
  3. Reboot

If the interface name remains the same, backup and delete /etc/udev/rules.d/70-persistent-net.rules and reboot the appliance so the file can be regenerated. 



 



Alternatively, follow the steps below to work around the issue temporarily as "emX" naming convention is the new standard for the current Series 4S appliances.



  1. Rename 
    • '/etc/sysconfig/network-scripts/ifcfg-em1' to '/etc/sysconfig/network-scripts/eth0'  
    • '/etc/sysconfig/network-scripts/ifcfg-em2' to '/etc/sysconfig/network-scripts/eth1'
    • and so on for all interfaces.
  2. Modify 'DEVICE=emX' to 'DEVICE=ethX' for every ifcfg-ethX file.
  3. Restart the network service:

    # service network restart



If this does not solve your issue, please open a case with RSA Technical Support and reference this article so that we may better assist you.

WorkaroundAn RSA Security Analytics Core appliance underwent an RMA.
Legacy Article IDa65665

Attachments

    Outcomes