Avamar: Browse Isilon Fails After Entering Password, No "/ifs" Directory Display
Summary: Avamar user interface cannot browse Isilon; after entering the password the "/ifs" is not shown. Cause: missing or mis‑configured Network Data Management Protocol (NDMP) user. Ensure that the NDMP user exists, run avsetupndmp, and enter NDMP password; /ifs can be browsed. ...
Symptoms
Issue observed when browsing Isilon from Avamar user interface.
Symptoms reported by users include:
- After entering the browse password, the
/ifsdirectory does not appear in the Avamar user interface. - No error messages or warnings are displayed.
- The issue occurs on a fresh installation with default configuration.
- Running
avsetupndmp
- Selecting edit on the Accelerator node causes the client to fail authentication of the NDMP user.
Cause
Underlying misconfiguration leading to browse failure.
NDMP user not created or lacking permissions
The Avamar Accelerator attempts to authenticate to the Isilon using an NDMP user. If the NDMP user does not exist or does not have the required permissions, authentication fails causing the browse operation to stop responding after the password is entered.
- The NDMP user is absent from the Isilon configuration
- Existing NDMP user lacks authorization to run NDMP jobs
- Incorrect or mismatched NDMP password entered in
avsetupndmp
# isi ndmp user ls NDMP User --------- ndmpebadmin
NDMP protocol is not enabled on Isilon.
If the NDMP service is disabled in the Isilon user interface, the Accelerator cannot establish an NDMP session, resulting in authentication failure and the missing /ifs directory view.
- NDMP service checkbox is cleared under Isilon user interface > Data Protection > Protocol
- NDMP port not listening (default 10000)
# isi ndmp settings global view ndmp port 10000 dma: generic
Password Configuration Errors
Using an incorrect password for either the NDMP user or the Avamar browse admin account prevents successful authentication, leading to the observed unavailability.
- NDMP password entered does not match the password set for the NDMP user on Isilon
- Browse admin password is not synchronized with Isilon credentials
Resolution
Restore Isilon browsing in the Avamar user interface.
Prerequisites
- Administrator access to the Isilon cluster (root)
- Administrator access to the Avamar Accelerator node
- Network connectivity between the Accelerator node and the Isilon management IP.
Step‑by‑step resolution
- Confirm that NDMP service is enabled on the Isilon:
NDMP checkbox is selected. Click Save if any change is made.
- Verify that the NDMP user exists:
# telnet 23 login: root Password: ******** # isi ndmp user ls
The output should list a user such as
ndmpebadmin. If no user appears, create one (see step 5).
- Test HTTP access to the Isilon namespace:
curl request using the NDMP or root credentials:
curl -vk -u "root" -X GET 'https://:8080/namespace/ifs'
A JSON or XML directory listing indicates that the service is reachable.
- Check global NDMP settings:
# isi ndmp settings global view
Ensure the output shows ndmp port 10000 and dma: generic . Adjust if necessary using the Isilon user interface.
- Create an NDMP authorized user (if missing):
# isi ndmp user create ndmp --password
- Configure the NDMP client on the Avamar Accelerator:
# avsetupndmp
When prompted:
If the utility is already waiting for a password, type the NDMP password and press Enter.
- Accept the default settings up to the NDMP password request.
- Enter the password created for the NDMP user in step 5.
- Browse the Isilon client in Avamar:
/ifs directory is displayed and can be expanded.
Verification
- Successful
curlrequest returns a directory listing for/ifs - Avamar UI shows the
/ifsroot and allows navigation into subdirectories - No error messages appear when browsing or when running
avsetupndmp
Caution: Modifying NDMP users or settings can affect existing NDMP backup jobs. Verify that other backup schedules are still functional after changes.
Note: If the issue persists after completing the steps above, collect the
avsetupndmp logs and contact Dell Support with the log files and a description of the actions performed.