A Remote Agent for Linux and Unix Servers (RALUS) does not show up in the list of backup devices because the agent does not advertise itself to the media server.

Article:TECH66261  |  Created: 2008-01-23  |  Updated: 2012-09-17  |  Article URL http://www.symantec.com/docs/TECH66261
Article Type
Technical Solution

Product(s)

Environment

Issue



A Remote Agent for Linux and Unix Servers (RALUS) does not show up in the list of backup devices because the agent does not advertise itself to the media server.


Solution



When RALUS first starts up, it advertises its TCP/IP interface information to the media servers configured in the RALUS.CFG file.  During this process, it needs to identify the local network device names.  If it encounters a network device name that contains numbers in it (e.g. e1000g), the enumeration of the network devices fails. This results in the agent not sending out an advertisement, and thus the agent does not automatically show up in at the media server.

Other than not showing up automatically in the list of backup devices under the Linux/Unix node in the Backup Exec user interface, this problem can be confirmed by putting RALUS into debug logging mode and restarting the agent.  During the NRDS advertisement that occurs near the end of the initial startup of the agent, the following text shows up:

NrdsAdvertiserThread: EnumSelfDLE for file system 22 returned -1(0xFFFFFFFF) and 0 DLEs

 
Workaround:

In cases where the agent advertisement does not work such as this case, or in cases where a firewall prevents the advertisement from reaching the media server, the solution is to use the User Defined Selections feature in the Backup Exec user interface.

Right click on the User Defined Selections node in the Backup Selections window and choose the Manage User Defined Selections menu option.  Then, add the address of the RALUS server in the name field.  Note that the IP address of the server (e.g. \\10.23.0.92) can be used in this field, but it is preferable to have the DNS name of the server.
 
Another workaround would be to change the NIC or NIC driver to one that does not have numbers in that rather than seeing /dev/e1000g0 device one might see /dev/elg0 as an example.  The issue being the numerical digits between, and not the instance number at the end.

This issue has been resolved in the Backup Exec 2010 release.
 

 


Supplemental Materials

Value1481985
Description

RALUS unable to advertise when using NIC drivers with numbers



Legacy ID



316840


Article URL http://www.symantec.com/docs/TECH66261


Terms of use for this information are found in Legal Notices