DeviceExpert

-

Network Configuration Management Software

ManageEngine DeviceExpert - FAQ & Troubleshooting Tips

Network Configuration Management, Network Change and Configuration Management Software, Network Device Management, Configure Switches, Routers, Firewalls & Other Network Devices

Installation, Un-installation, Startup & Shutdown

Server-startup fails

Cause: During the previous run, if you had terminated the server abruptly or there was an unclean shutdown, some of the server processes would not have been terminated and the MySQL server instance would continue to run in the system.

Solution: Forcefully terminate the MySQL Server instance (mysqld-nt.exe in Windows, mysqld in Linux).

When I uninstall the product in windows, some folders are not getting deleted.  

Cause: This usually happens when you try to uninstall the product immediately after shutting down the DeviceExpert server.

Solution: Ensure that you uninstall the product only after the MySQL Server instance (mysqld-nt.exe process in Windows Task Manager) has been terminated completely after the server shutdown.

After DeviceExpert server startup, I am prompted to accept a security certificate. Why?

Cause & Solution: After DeviceExpert server startup, a browser is launched for connecting web interface. Since DeviceExpert uses secure http, the security certificate is prompted. You need to accept the security certificate for connecting to the client.

How do I move DeviceExpert installation from one machine to another?

If you want to move the DeviceExpert installed in one machine to another, follow the procedure detailed below:

Prerequisite:

Do not remove existing installation of DeviceExpert until the new installation works fine. This is to ensure backup, to overcome disasters/data corruption during the movement.

Procedure:

  • Stop DeviceExpert server / service, if running
  • Simply copy the entire DeviceExpert installation folder from one machine to another
  • Then, install it to run as service. (Refer "Installation Section of Help Documentation for details). In this option, you will not be able to uninstall the program through windows Add/Remove programs console. If you want to uninstall anytime, just delete the entire installation folder.
Web Interface

Can I change the default port 6060 occupied by DeviceExpert?

Yes, you can change the default port as explained below:
  • Go to <DeviceExpert_Installation_Folder>\conf directory and open the server.xml file
  • Replace the entry '6060' with the port number of your choice. Note that there will be 6060 entries within comments too and all should be replaced.

While trying to connect web-client, I see a blank page with five small square boxes on top. Why ?

Cause & Solution: In Internet Explorer, if you have tried to connect client using http://<host>:6060, this issue will arise. Since the DeviceExpert server and the Web Interface communicate through https, make sure that you connect to https://<host>:6060 (secure http).

I am unable to access DeviceExpert Web Interface (while starting the server thyrough tray-icon/commandline mode). Why?

Cause 1 & Solution: Incomplete server start-up

Ensure that the server has successfully started. This can be verified by the presence of the message "Server started in :: [xyz ms]" in the console. Connect to the web client after seeing this message.

Cause 2 & Solution: Wrong URL

DeviceExpert server and the Web Interface communicate through http. So ensure the URL contains HTTPS.
https://<hostname>:port/
For e.g. https://localhost:6060

Cause 3 & Solution: Do you see any "FAILED" message in the Server Console?

Check the log files available under <DeviceExpert_Home>/logs directory. If you find any exceptions, please send the log files to DeviceExpert Support.

While trying to connect web interface, I get the message "Problem in starting TFTP Server. Free the port "69".

Cause: TFTP port required by DeviceExpert is not free.

Solution: Free the port and then start DeviceExpert. In case, you are running ManageEngine OpManager or ManageEngine WiFiManager in the same machine as that of DeviceExpert, carryout the following changes to free the TFTP port.

Check if the TFTP service is running when OpManager/WiFiManager is running. If yes, comment out the following lines in NmsProcessesBE.conf located in <OpManager_Home>/conf or <WiFiManager_Home>/conf directory as shown below:

# java com.adventnet.nms.tftp.NmsTftpServer [TFTP_ROOT_DIRECTORY dir] [PORT portNo]
#PROCESS com.adventnet.nms.tftp.NmsTftpServer
#ARGS TFTP_ROOT_DIRECTORY /

Save the file and restart OpManager/WiFiManager. Then start DeviceExpert.

I forgot the password to login to Web Interface

You can a get a new password for an account using the Login Name and Email Id of that account (the Email id should match with the one that was configured for the user earlier)

  • Click 'Forgot Password?' link in the login screen
  • Provide the Login Name in the text filed
  • Provide the Email Id configured for the service
  • The password will be mailed to your mail account
  • Use that auto generated password for logging into the service which you can choose to change later

How do I change the password of my login account?

  • Login to the DeviceExpert Web Interface
  • Users with admin privileges can change their Login Password through the 'Edit Account Settings' functionality of "Admin" Tab. Ordinary users (that is, users who do not have admin privileges) can change their Login Password through the 'Edit Account Settings' functionality present in left-hand side of "Home" Page.
  • To Change Login Password,
    • click "Admin" tab >> "Change Password "
    • enter the old password
    • enter new password
    • confirm the new password
    • click "Save"
    • password is now reset

While invoking deviceexpert.bat portcheck or sh deviceexpert.sh portcheck, I get a message like the one below:

-----------------------------
Port Availability Module
-----------------------------
6060 No Client
43306 No mysql
69 No TFTP
514 No Syslog
####################################################
Server is already running
Connect to https://localhost:6060 to view the client
####################################################
Press any key to continue . . .

Cause & Solution: Since all the ports required by DeviceExpert are not free, it indicates that DeviceExpert
server is already running. Try connecting to https://localhost:6060 to view the web interface

My Web Interface looks crippled

Cause 1 & Solution: Incompatible Browser

Refer to the DeviceExpert System Requirements, and check whether your browser is supported.

Cause 2 & Solution: JavaScript not enabled

JavaScript has to be enabled in your browser to work with the Web Interface.

Alignment in web interface is not proper

Cause: This could be a problem with browser cache

Solution: Close all browser instances, clear cache and cookies and connect a new instance. If the problem still persists, contact DeviceExpert support.

Device Addition, Inventory & Change Detection

I have my devices listed in a text file. Can I import them to the inventory of DeviceExpert?

DeviceExpert provides the option to import devices from a text file and add them to the inventory. To import devices from a text file, DeviceExpert requires that the entries in the file conform to a specific format. For more details, refer to the section on "Device Addition" in help documentation.

Can I apply same set of credentials to multiple devices as a bulk operation?

Yes. You can apply the same set of credentials 'as they are' to multiple devices. In such cases, to avoid the cumbersome task of entering the credentials for each device separately, DeviceExpert offers the flexibility of creating common credentials and sharing the common credentials among multiple devices. This is called as 'Credential Profile'. For more details, click here.

How does DeviceExpert help me in keeping track of configuration changes?

One of the ways to detect configuration changes in a device is by monitoring syslog messages. Many devices generate syslog messages whenever their configuration undergoes a change. By listening to these messages, it is possible to detect any configuration change in the device. This comes in handy for administrators to keep track of the changes being made and to detect any unauthorized changes.

DeviceExpert leverages this change notification feature of devices to provide real-time change detection and tracking. A syslog server comes in-built with DeviceExpert. It occupies port 514.

Besides the real-time change detection, configuration changes could also be tracked through scheduled, periodic backup of device configuration. For more details refer to the section "Configuration Change Detection" in help documentation.

I have enabled syslog-based change detection for my device. But the product does not seem to detect any configuration changes.

Configuration change messages will be generated only at certain logging levels. So check if the logging level in the device is set to one of the values listed in the "Syslog Config for Change Detection" - logging level drop-down. Also, ensure if syslog server is running and the syslog port (514) is free for DeviceExpert's use.

Configuration Operations

Configuration Backup Fails (or) Credentials Test option fails

Cause & Solution:

(1) Check if the device is up and accessible to the DeviceExpert server

(2) The device is unable to transfer the configuration file to the TFTP server run by DeviceExpert. The reasons for this could be:

      • A firewall present between the device and DeviceExpert might be blocking the access. Check if it is so.
      • The device might be present outside the private network (i.e. the private IP of DeviceExpert is not resolved by the device). If you have NAT in your environment, this could occur. To resolve this, provide DeviceExpert's public IP (NAT'ed IP of DeviceExpert) as TFTP server's public IP in the Additional Credentials section.

(3)  Check if you are able to do a manual backup by connecting to the device directly:

    • From the DeviceExpert server, login to the device using standard Telnet/SSH client
    • Go into the Enable mode and execute the command to backup either startup or running configuration over TFTP
    • As part of the command , in place of TFTP server address, specify DeviceExpert server IP as TFTP Server runs along with the DeviceExpert server.
    • Check whether the backup is working. If it works, contact DeviceExpert Support with the logs generated by setting Admin --> LogLevel to DEBUG

Information on who changed the configuration is not available in reports for some devices. Why?

DeviceExpert registers information on 'who changed' the configuration in the following cases:

  • When configuration changes are carried out using DeviceExpert
  • When someone carries out a change outside of DeviceExpert, the 'who changed' information will be captured if real-time change detection for the device should is enabled in DevieExpert and if username has been configured in the device.

In other cases such as scheduled configuration backup and manual backup, 'who changed' information will not be available. At present, DeviceExpert does not support real-time change detection for Cisco CatOS devices. Hence, for those devices, if the changes are carried out outside of DeviceExpert, 'who changed' information will not be available.

When I use Telnet-TFTP option, configuration backup fails repeatedly. Why?

Cause: You would face this scenario if the device credentials are incorrect

Solution: Make sure that credentials are correct. Test the same using "Testing" option available in that screen. The test result will show which credentials are wrong. Change them accordingly. In case, you are not able to get it working even after ensuring this, send your log files to DeviceExpert Support for further assistance.


Security Aspects

How secure are our data in DeviceExpert? What is the encyption standard used by DeviceExpert for storing sensitive data in the database?

  • DeviceExpert offers a good level of security to your configuration as all the configuration information retrieved from devices are encrypted and stored in MySQL database bundled with DeviceExpert. Device credential information are also encrypted and stored in DB.
  • The DeviceExpert database accepts connections only from the host in which it runs and is not visible externally. So, access to the DeviceExpert database is restricted only to the local machine. No one can access it outside the machine.
  • For securely storing the configuration content, DeviceExpert leverages the encode functionality of MySQL. More details can be had from:  http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html#function_encode
  • DeviceExpert web-interface works over HTTPS, so the entire communication between DeviceExpert server and the webclient is absolutely secure.
  • Devices can be accessed over SSH to retrieve and push configuration in a secure way.

I want to prevent unauthorized configuration changes to my core devices.

You can make use of the 'Change Management' feature of DeviceExpert. For more details refer to the section "Configuration Change Management " in help documentation.

What happens when I click the 'Mark as EOL' link in the GUI of end-of-life report?

DeviceExpert collects EOL/EOS status of devices from the vendor websites and bulletins. In case, you find any of your device status incorrectly marked here, you can notify DeviceExpert support by clicking the "Mark as EOL" link in the GUI.

This will trigger an E-Mail to DeviceExpert support for marking the device status as EOL. The E-Mail contains only the series, model and vendor details and no other details are transferred. The E-Mail is also copied to the user, who triggers this alert. Until DeviceExpert marks it as EOL/EOS, it will be labeled as "Marked as EOL" in the local database.

Can we install our own SSL certificate? How?

Yes, you can install your own SSL certificates in DeviceExpert. Please follow the steps below to do that:

DeviceExpert runs as a HTTPS service. It requires a valid CA-signed SSL certificate with the principal name as the name of the host on which it runs. By default, on first time startup, it creates a self signed certificate. This self signed certificate will not be trusted by the user browsers. Thus, while connecting to DeviceExpert, you need to manually verify the certificate information and the hostname of DeviceExpert server carefully and should force the browser to accept the certificate.

To make the DeviceExpert server identify itself correctly to the web browser and the user:

  • you need to obtain a new signed certificate from a CA for the DeviceExpert host or
  • you can configure an existing certificate obtained from a CA with wild-card principal support for the DeviceExpert host

You can use OpenSSL or keytool (bundled with Java) to create your certificates, get them signed by a CA and use them with DeviceExpert. The choice of which tool to use is yours, based on what your security administrators say. Detailed instructions on using both the tools are provided here. If you already have a certificate signed by a CA, then we recommend using OpenSSL to create the keystore and configure it in DeviceExpert (steps 4 and 5 in the instructions below).


Using OpenSSL

OpenSSL is available bundled with most of the Linux distributions. If you have Windows and do not have OpenSSL installed, download it from http://www.slproweb.com/products/Win32OpenSSL.html . Make sure the 'bin' folder under the OpenSSL installation is included in the 'PATH' environment variable.

Step 1: The first step is to create the public-private key pair that will be used for the SSL handshake

  • Open the command prompt
  • Execute 'openssl genrsa -des3 -out <privatekey_filename>.key 1024'
    • <privatekey_filename> is the filename you specify to store the private key
  • This will prompt you to enter a pass-phrase for the private key. Enter 'deviceexpert' or a pass-phrase of your choice. (Though it is not documented, Tomcat has issues with passwords containing special characters, so use a password that has only alpha characters)
  • This will create a file named <privatekey_filename>.key in the same folder
Step 2: Create a Certificate Signing Request (CSR) for submission to a certificate authority to create a signed certificate with the public key generated in the previous step.
  • Execute 'openssl req -new -key <privatekey_filename>.key -out <certreq_filename>.csr'
    • <privatekey_filename>.key is the one used in the previous step
    • <certreq_filename>.csr is the filename you specify to carry the certificate creation request to the CA (certificate authority)
  • This will prompt you to enter a series of values that are part of the distinguished name (DN) of the server that will host DeviceExpert
  • Enter values as applicable to you and importantly for the 'Common Name' supply the fully qualified name of the server hosting DeviceExpert (with which it will be accessed through the browsers)
  • This will create a file name <certreq_filename>.csr in the same folder
Step 3 : Submit the CSR to a Certificate Authority (CA) to obtain a CA signed certificate
  • Some of the prominent CAs are Verisign (http://verisign.com), Thawte (http://www.thawte.com), RapidSSL (http://www.rapidssl.com). Check their documentation / website for details on submitting CSRs and this will involve a cost to be paid to the CA
  • This process usually takes a few days time and you will be returned your signed SSL certificate and the CA's root certificate as .cer files
  • Save them both in the the same working folder where files from steps 1 and 2 are stored
Step 4: Import the CA-signed certificate to a keystore
  • On a command prompt navigate to the same working folder
  • Execute 'openssl pkcs12 -export -in <cert_file>.cer -inkey <privatekey_filename>.key -out <keystore_filename>.p12 -name DeviceExpert -CAfile <root_cert_file>.cer -caname DeviceExpert -chain'
    • where
      • cert_file.cer is the signed SSL certificate with the .cer extention
      • privatekey_filename.key is the private key file with a .key extension
      • keystore_filename.p12 name is the keystore that will be generated with a .p12 extension
      • root_cert_file.cer is the CA's root certificate with a .cer extension
    • When prompted for password, enter the same password which you used in step 1 for the private key. Note that this requirement is due to an inherent limitation in tomcat, where these two passwords have to be the same
  • This will generate the keystore file <keystore_filename>.p12 on the same folder
Step 5: Finally, configure the DeviceExpert server to use the keystore with your SSL certificate
  • Copy this <keystore_filename>.p12 generated in the previous step to <DeviceExpert_Install_Folder>\conf folder
  • In a command prompt, navigate to <DeviceExpert_Install_Folder>\conf folder
  • Open the file server.xml and do the following changes
  • Search for the entry 'keystoreFile', which will have the default value set to "conf/server.keystore". Change the value to "conf/<keystore_filename>.p12"
  • Make sure the entry  for 'keystorePass' is set to "deviceexpert" or the password you specified in the previous step while creating the keystore
  • Add a new entry keystoreType="PKCS12" next to the keystorePass entry
  • Save the server.xml file
  • Restart the DeviceExpert server and connect through the web browser. If you are able to view the DeviceExpert login console without any warning from the browser, you have successfully installed your SSL certificate in DeviceExpert!

Using Keytool

Step 1: The first step is to create the public-private key pair that will be used for the SSL handshake

  • Go to <DeviceExpert_Home>/jre/bin folder
  • Execute the command "./keytool -genkey -alias DeviceExpert -keyalg RSA -keypass <privatekey_password> -storepass <keystore_password> -validity <no_of days> -keystore <keystore_filename>"
    • <keystore_password> is the password to access the keystore, <privatekey_password> is the password to protect your private key. Note that due to an inherent limitation in tomcat, these two passwords have to be the same. (Though it is not documented, Tomcat has issues with passwords containing special characters, so use a password that has only alpha characters)
    • <no_of_days> is the validity of the key pair in number of days, from the day it was created
  • The command will prompt you to enter details about you and your organization
    • For the 'first and the last name' enter the FQDN of the server running DeviceExpert
    • For other fields enter the relevant information
    • <keystore_password> is the password to access the keystore, <privatekey_password> is the password to protect your private key and <no_of_days> is the validity of the key pair in number of days, from the day it was created
  • This will create a keystore file named <keystore_filename> in the same folder, with the generated key pair

Step 2: Create a Certificate Signing Request (CSR) for submission to a certificate authority to create a signed certificate with the public key generated in the previous step.

  • Go to <DeviceExpert_Home>/jre/bin folder
  • Execute the command "keytool -certreq -keyalg RSA -alias DeviceExpert -keypass <privatekey_password> -storepass <keystore_password> -file <csr_filename> -keystore <keystore_filename>"
    • Note that the <csr_filename> that you choose should have .csr extension. The <privatekey_password>, <keystore_password> and <keystore_filename> are the ones used in the last step
  • This will create a CSR file named <csr_filename> in the same folder

Step 3 : Submit the CSR to a Certificate Authority (CA) to obtain a CA signed certificate

  • Some of the prominent CAs are Verisign (http://verisign.com), Thawte (http://www.thawte.com), RapidSSL (http://www.rapidssl.com). Check their documentation / website for details on submitting CSRs and this will involve a cost to be paid to the CA
  • This process usually takes a few days time and you will be returned your signed SSL certificate and the CA's certificate as .cer files
  • Save them both in the <DeviceExpert_Home>/jre/bin folder

Step 4: Import the CA-signed certificate to the DeviceExpert server

  • Import your SSL certificate into your keystore
  • Go to <DeviceExpert_Home>/jre/bin folder
  • Execute the command "keytool -import -alias DeviceExpert -keypass <privatekey_password> -storepass <keystore_password> -keystore <keystore_filename> -trustcacerts -file <your_ssl_certificate>"
  • <your_ssl_certificate> is the certificate you obtained from the CA, a .cer file saved in the previous step. The <privatekey_password>, <keystore_password> and <keystore_filename> are the ones used in the previous steps
  • Now copy the <keystore_filename> to the <DeviceExpert_Home>/conf folder

Step 5: Finally, configure the DeviceExpert server to use the keystore with your SSL certificate

  • Go to <DeviceExpert_Home>/conf folder
  • Open the file server.xml
  • Search for the entry 'keystoreFile', which will have the default value set to "conf/server.keystore". Change the value to "conf/<keystore_filename>" where <keystore_filename> is the one used in the previous steps
  • Also search for the entry 'keystorePass' (which will infact be next to keystoreFile), which will have the default value set to "deviceexpert". Change the value to "<keystore_password>" where <keystore_password> is the one used in the previous steps
  • Restart the DeviceExpert server and connect through the web browser. If you are able to view the DeviceExpert login console without any warning from the browser, you have successfully installed your SSL certificate in DeviceExpert!

Note : Tomcat by default accepts only the JKS (Java Key Store) and PKCS #12 format keystores. In case, the keystore is of PKCS #12 format, include the following option in the server.xml file along with the keystore name, keystoreType="PKCS12?This tells tomcat that the format is PKCS12. Restart the server after this change.

Installing an existing wild card supported SSL certificate

  • Go to <DeviceExpert_Home>/conf folder
  • Open the file server.xml
  • Search for the entry 'keystoreFile', which will have the default value set to "conf/server.keystore". Change the value to "conf/<keystore_filename>" where <keystore_filename> is the one belong to the existing wild-card certificate.
  • Also search for the entry 'keystorePass' (which will in fact be next to keystoreFile), which will have the default value set to "deviceexpert". Change the value to "<keystore_password>" where <keystore_password> is the one used to protected the existing wild-card certificate keystore.
  • Restart the DeviceExpert server and connect through the web browserconsole. If you are able to view the DeviceExpert login console without any warning from the browser, you have successfully installed your SSL certificate in DeviceExpert!
Note : Please refer your CA's documentation for more details and troubleshooting

Miscellaneous

When I try to import users from AD, the operation fails ...

Following are the possible causes for AD import failure:

  1. If you have added the domain by yourself, ensure that you have specified only the domain name portion and not the fully qualified domain name. For example, it should just be ZOHOCORP and not ZOHOCORPO.com
  2. The user name entered should just be the AD login name of the corresponding user and should not be of the format DOMAIN-NAME\USER_NAME. For example, specify the user name as bjohn instead of ZOHOCORP\bjohn
  3. It is recommended to use a non-administrator credential to query AD. So try with a different user who has read-only permission for the domain instead of 'Administrator'
  4. Try all these options for the domain controller name; the usual DNS name, fully qualified domain name and finally the IP address
  5. If you had selected SSL, make sure the domain controller root certificate is imported to the trust store of PMP

Can DeviceExpert be configured to use HTTP mode instead of HTTPS?

Yes, DeviceExpert can be configured to use HTTP instead of HTTPS. To do this, changes have to be made in the server.xml file present under <DeviceExpert_Installation_Folder>/conf directory . Follow the steps detailed below:

  1. Stop DeviceExpert server/service
  2. We have a server.xml file for HTTP mode in our website. Download the server.xml file and replace the existing server.xml file with the one you downloaded
  3. Start DeviceExpert server/service

I deleted a user that had created some of the groups and now the groups are gone.

Cause & Solution: The user might have created "Private DeviceGroups", which are user specific data. So, when you delete a user, the "Private DeviceGroups" created by that user will get deleted. However, the "Public DeviceGroups" created by the user will not get deleted.

Mail sent from product does not reach the intended recipient

Cause: Mail settings might be incorrect

Solution:(1) Verify Mail Server settings and test the same using "Test" option. (2) Also, check if the default from address is properly configured in Mail Settings page. Some mail servers will reject the mail if the from address is invalid or does not exist at all.
(3) Check if you are able to send emails from Reports ---> Email option. Mails will be sent instantly. If you do not receive mails, contact DeviceExpert support.

'Upload' button present in the 'View Draft Details' / 'View Config File Details' pages are shownn as 'disabled'

Cause & Solution:

The 'Upload' button will be shown as disabled in the following two scenarios:

(1) When the viewing configuration is a current configuration
(2) When the viewing configuration type Upload is not supported by the device

So, check if you have disabled it in the above scenarios.

Can I receive automatically generated reports on Device Configuration in my mailbox?

Yes, DeviceExpert provides option to mail reports to email IDs. You can schedule reports to be generated at any point of time and reports will be mailed to your email ID.

Can DeviceExpert generate email alerts?

Yes, DeviceExpert can be configured to send email alerts whenever there happens a change in configuration. For more details refer to the section "Change Management " in help documentation.

Does DeviceExpert maintain historical data about Device Configuration?

'Yes it maintains historical data of device configuration. The historical data are available in the device properties page of each device. For more details refer to the section "Device Configuration Details" in help documentation.

Can I replace the JRE bundled with DeviceExpert? How?

Yes, you can replace the bundled JRE with any other desired version.

  • Shut down DeviceExpert server, if already running
  • Go to <DeviceExpert_Installation_Folder>
  • Rename the existing 'jre' directory as, say, 'jre-old'
  • Put the new JRE directory under <DeviceExpert_Installation_Folder>. The folder should be named jre
  • Start DeviceExpert Server

Note: The JRE being replaced should correspond to the OS in which DeviceExpert is running. For example, if DeviceExpert is running in Windows, you need to install the JRE for Windows only.

I have created a scheduled task for DeviceExpert Database Backup. But, the task fails to execute. I get a notification saying "Error occurred while executing the scheduled database backup operation". Why?

During MySQL database backup, some temporary files are created by MySQL process, which are sometimes denied by the virus scanner softwares. Exempting DeviceExpert installation folder from virus scans should solve this issue. If it is not excluded, database backup might fail. In case, it is not possible to exclude the entire DeviceExpert installation directory from scans, exclude at least <DeviceExpert Installation Folder>/MySQL from scanning. Database backup will work fine.

If the issue persists even after ensuring the above, contact DeviceExpert Support.

Basic General Questions & Licensing

What is ManageEngine DeviceExpert?

ManageEngine DeviceExpert is a comprehensive Network Change and Configuration Management (NCCM) solution that enables the Network Administrator to efficiently and effortlessly manage the configurations of Network Devices. DeviceExpert offers multi-vendor network device configuration, continuous monitoring of configuration changes, notifications on respective changes, detailed operation audit and trails, examining device configurations for compliance to a defined set of policies and standards, real-time compliance status reporting, easy and safe recovery to trusted configurations, automation of configuration tasks and insightful reporting. For more details, click here.

What does DeviceExpert do?

DeviceExpert can manage network devices such as switches, routers, firewalls wireless access points and integrated access devices etc. from multiple vendors such as Cisco, HP, Nortel, Juniper, Force10, 3Com, D-link, Foundry, Dell, Aruba, Extreme, ADTRAN, Enterasys, Huawei, Blue Coat, Proxim, NetScreen, NETGEAR, FortiNet, ALAXALA, Brocade, Radware, DAX, H3C, Yamaha, Vanguard, Allied Telesis, Alcatel. It discovers network devices, builds up an inventory database and allows IT administrators to take control of configuring the devices from a central console. The web-based administrator console provides the User Interface to perform all the configuration operations. Additionally, it can be accessed from anywhere using any standard web browser.

Can DeviceExpert Manage the Configurations of Cisco Devices?

Yes, DeviceExpert can manage the configurations of cisco devices. Cisco router configuration, Cisco switch configuration and Cisco firewall configuration can be done using DeviceExpert. Apart from cisco devices, DeviceExpert can be used to manage the configurations of switches, routers, firewalls, wireless access points and integrated access devices from other vendors such as HP, 3com, Foundry, FortiGate and NetScreen.

Can DeviceExpert be used to manage router configuration / switch configuration / firewall configuration?

Yes, DeviceExpert can be used to manage router configuration, switch configuration and firewall configuration from multiple vendors such as Cisco, HP, Nortel, Juniper, Force10, 3Com, D-link, Foundry, Dell, Aruba, Extreme, ADTRAN, Enterasys, Huawei, Blue Coat, Proxim, NetScreen, NETGEAR, FortiNet, ALAXALA, Brocade, Radware, DAX, H3C, Yamaha, Vanguard, Allied Telesis, Alcatel.

What are the devices supported by DeviceExpert?

DeviceExpert at present supports switches, routers, firewalls, wireless access points and integrated access devices. For new device support, send your request.

What are the vendors supported by DeviceExpert?

DeviceExpert at present supports Cisco, HP, Nortel, Juniper, Force10, 3Com, D-link, Foundry, Dell, Aruba, Extreme, ADTRAN, Enterasys, Huawei, Blue Coat, Proxim, NetScreen, NETGEAR, FortiNet, ALAXALA, Brocade, Radware, DAX, H3C, Yamaha, Vanguard, Allied Telesis, Alcatel . For new vendor support, send your request.

Is DeviceExpert available for evaluation or direct purchasing?

DeviceExpert is available for both evaluation and direct purchase. Please contact our sales team at +1-888-720-9500 or email sales@manageengine.com.

Do I need any prerequisite software to be installed before using DeviceExpert?

There is no prerequisite software installation required to use DeviceExpert. MySQL, TFTP server and Syslog server are bundled with the product itself. If you want to received change management notifications via email, you need to configure an external SMTP server (optional).

What is the Licensing Policy for DeviceExpert?

  • Professional Evaluation Edition download valid for 30 days, capable of supporting a maximum of 50 devices. Free support would be offered during evaluation
  • Professional Edition - Licensing based on the number of devices support needed. Priority support would be offered. For more information / to get license, contact sales@manageengine.com.
  • Free Edition - download valid for ever, capable for supporting a maximum of two devices.

Do I have to reinstall DeviceExpert when moving to the Professional Edition?

No. You need not have to reinstall or shut down the server. You just need to enter the new license file in the "Register" link present in the top right corner of the DeviceExpert web interface.

I do not see "Register" link on the top-right hand corner of DeviceExpert GUI. How do I apply the license?

In DeviceExpert GUI, navigate to Admin >> Rebranding Settings and uncheck the textbox "Hide the links Register, About, Feedback". This would enable the Register button at the top right corner.

What are the browser versions supported by DeviceExpert?

Web Interface requires one of the following browsers** to be installed in the system:

  • IE 7 and above (on Windows)
  • Firefox 2.0 and above (on Windows and Linux)

** DeviceExpert is optimized for 1024 x 768 resolution and above

What are the System Configuration Requirements for DeviceExpert?

Refer to the information available in the System Requirements section.

 


 
Customer Speaks
 

"Ability to create and push network device configurations
in automated fashion saves us a great deal of time. DeviceExpert is a very powerful configuration management tool."

Kevin Spies, LightYear Network Solutions, LLC