Confirm the CLI credentials within the Netsight Policy are correct:
1. Launch Inventory Manager
2. Highlight the Switch under Network Elements, and click on the General tab
3. Note the Netsight Server Profile:
4. Click on the Tools menu, and select Authorization/Device Access
5. Click on the Profiles/Credentials tab and highlight the Profile used by the device as seen as highlighted in step #4 above. In this example, the profile is: public_v1_profile
Note the CLI Credential Column:
6. Click on the CLI Credentials tab at the bottom of the screen, and highlight the Description column that matches the CLI Credential column from step #5 above. In this example, it is using the CLI Credential 'Default'
In this window, you will see the username/password and the client used by Netsight to connect to the XOS switch and begin the archive. Using the example above, you should be able to telnet from the Netsight server machine to the switch and login as the user 'admin' with no password. If you cannot login using a telnet client (or ssh/putty if using ssh) using these credentials, the archives of this device will fail.
Once the CLI/Profile Credentials within Netsight are confirmed as accurate, you can then confirm the tftp settings:
1. Navigate to the Tools menu, and select Options and then Services for Netsight Server. Note the two variables in this window.
2. SSH to the Netsight server machine, and confirm that the TFTP Root Directory defined in window above exists and has the correct permissions:
3. Confirm that the TFTP daemon on the Netsight machine has the correct Root directory defined. This directory needs to match the TFTP Root Directory settings in step on above.
The command is: more /usr/local/Extreme_Networks/NetSight/services/nstftpd.cfg
Confirm the MIBs for this device is set properly within Netsight:
**Note: If the settings within Netsight in step #1 or the file in step #3 needs to be modified, you will need to restart the TFTP daemon manually. The command to restart is: /etc/init.d/nstftpd restart
1. Within Inventory Manager, highlight the device and click on the Image Information tab. Confirm that the Configuration MIB and Firmware Download MIB settings are set to 'Controlled by this Device'. If this setting is set to Disabled, the Archive will fail:
If the archive is unsuccessful after confirming the above settings, you can enable debug to get more information:
1. Log into the Extreme Management web interface
2. Click on the Administration tab
3. Change the 'Level' drop down menu to 'Diagnostic'
4. Expand the Server menu option and select the 'Server Diagnostics'
5. In the right menu, locate the variable Telnet/SSH Command Shell' option, and change it to 'Verbose'
6. Click OK
7. Rerun the Archive.
This procedure will place debug information within the server.log file pertaining to the archive attempt.
You can access this file through the 'Server Log' option in the above web interface.
To confirm the connectivity of the TFTP traffic between Netsight and the switch, you can run the following command on the Netsight server machine:
tcpdump -i <mgmt interface> port 69 and host <ip of the switch>
Relaunch the archive with this command running. You should see the traffic to/from the switch to netsight. If you only see Netsight sending the tftp traffic and no responses from the switch, this could indicate an issue between the two devices, such as a firewall, blocking port 69 traffic.