Cisco Enhanced Device Interface User Guide 2.2.1 - Frequently Asked Questions [Cisco Enhanced Device Interface]

Table Of Contents

Frequently Asked Questions

Command Translator

Macro Command Manager

Command Modeler

Operational Data Modeler

Command Analyzer

Device Configuration Manager

General

Install-related FAQs

Frequently Asked Questions

This section answers common questions associated with:

•Command Translator

•Device Configuration Manager

•Macro Command Manager

•Command Modeler

•Command Analyzer

•Operational Data Modeler

•General

•Install-related FAQs

For the latest FAQs of Cisco Enhanced Device Interface, please check Cisco.com:

http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html

Command Translator

You can find the complete usage details of Command Translator in User Guide for Cisco Enhanced Device Interface, at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html

The following are the FAQs for Command Translator:

Q. The Command Translator reports translation errors for some of the lines in the converted Cisco IOS configuration file. How can I resolve these?

A. Some cases require more information than the configuration file provides. For example, many QoS configuration commands have dependencies on ACLs or policies. If these commands are not included, the tool cannot provide a complete translation.

In other cases, there simply is not a Cisco IOS equivalent command, as is the case with commands related to the CatOS sc0 interface.

Sometimes, a command is intentionally not translated in order to require you to make a conscious configuration for a critical setting, such as the AAA services.

For a list of CatOS commands that are not translated in this release, see the topic Untranslated CatOS Commands, in the section Translating Commands Using Command Translator, of the User Guide for Cisco Enhanced Device Interface at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html

Q. Why does the Command Translator translate both the set port name and the set port description CatOS commands into the port description Cisco IOS interface configuration command?

A. Cisco IOS does not have an equivalent to the CatOS set port name, but the set port name command is often used as a description. Therefore this command needs to translate to Cisco IOS. The dilemma occurs when both the set port name and the set port description CatOS commands are used, because ultimately only one command can be in effect in the Cisco IOS configuration. Both commands translate into the Cisco IOS translated configuration and you must delete whichever one is not needed.

Q. Why are my sc0 interface commands not translated?

A. Cisco IOS does not implement an sc0 interface. This is an architectural difference between CatOS and Cisco IOS. In Cisco IOS, any interface can be configured as a management interface.

Q. Why are my banner-related commands not translated?

A. The translation of the CatOS Banner into the Cisco IOS Banner is under consideration for a future release of the tool.

Q. Why are my AAA-related commands not translated?

A. These commands are critical in order to maintain access to the switch, therefore it is important to make a conscious effort to configure these parameters and not risk a blockage of access to the switch.

Q. I use a Hybrid operating system with both CatOS and Cisco IOS on the MSFC. Can the tool integrate my MSFC Cisco IOS configuration as well?

A. No, the tool cannot integrate the MSFC configuration into the translated CatOS configuration. Most of the MSFC Cisco IOS commands convert as-is into a new Cisco IOS switch configuration.

Q. Can I use the output from a show run for the CatOS input file or does this have to be a full copy of the configuration file downloaded from the switch?

A. You can use the show run output.

Q. Do I have to provide a show module output for every conversion?

A. The show module output is optional. The show module output only assists with certain set QoS commands.

Q. What are the minimum software versions for CatOS and Cisco IOS supported by the tool?

A. The Command Translator supports CatOS version 8.5.1 and earlier. The translated Cisco IOS configuration file can be based on Cisco IOS Software Release 12.2.18SXF3 or Cisco IOS Software Release 12.2.18.SXF5.

Q. Is there a list or database of known CatOS commands that do not translate into a Cisco IOS equivalent?

Yes. For a list of CatOS commands that are not translated in this release, see the topic Untranslated CatOS Commands, in the section Translating Commands Using Command Translator, of the User Guide for Cisco Enhanced Device Interface at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html.

Macro Command Manager

You can find the complete usage details of Macro Command Manager in User Guide for Cisco Enhanced Device Interface, at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html

The following are the FAQs for Macro Command Manager:

Q. The macros I created using the Macro Command Manager GUI were lost after the E-DI server stopped.

A. Once the GUI changes are done, ensure that you perform a Save Macro Changes operation. Unless your changes are saved, they are not updated to the server database, and if the server restarts, these changes are lost.

Q. Deploy macro command generates a message that the deploy was successful even though the command was not applied to the device. Why does this happen?

A. The deploy macro command creates a temp file and uploads the file to the device using TFTP. A temporary file will be generated in server/temp folder. Check the contents of the file to see if they are valid on the device.

Command Modeler

You can find the complete usage details of Command Modeler in Programmer's Guide for Cisco Enhanced Device Interface, at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html

The following are the FAQs for Command Modeler:

Q. What are the jar files needed for compiling the code generated by EDI?

A. nemo.jar, cliparser.jar, nodetypes.jar, log4j-1.2.8.jar, javolution.jar are needed for compilation. All these jar files are present under subfolders in the E-DI install directory.

Q. What is the use of toXml () method provided in the generated class?

A. The toXml () method generates the xml transformation of the CLI. This can be used along with the XML Programatic interface.

Q. The required device family is not available in the list of devices that can be selected for the creation of unified model. Why is this?

A. Device package for that particular device is not present in the device package directory specified in the Setup wizard. To get the required device package:

a. Check whether the device package is available at this URL: http://www.cisco.com/cgi-bin/tablebuild.pl/E-DI-2.0.

b. If it is present, download the device package. You need to have your Cisco.com user login to download these packages.

c. Re-enter the details in the Setup Wizard and submit it.

Q. Where are the generated Java files stored?

A. The generated Java files are stored in the Code Output Directory specified in the Setup Wizard.

Q. How do I enter the package name for the Java code generated by Command Modeler?

A. During generation of code, you are prompted to enter a package name for the Java code. In the current release, there is no support for a default package.

Operational Data Modeler

You can find the complete usage details of Operational Data Modeler in Programmer's Guide for Cisco Enhanced Device Interface, at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html

The following are the FAQs for Operational Data Modeler:

Q. Is ordering of elements important in a Spec file?

A. Yes, ordering of elements is important in a Spec file. Elements should be present in the same order as the order in which they appear in CLI from left to right and top to bottom.

Q. I am not sure where I am allowed to use dynamic option of <Container>.

A. Yes, you can use the dynamic option for looping data structures where multiple instances are possible for a particular data model. For example, in the output of show interfaces or show interface stats IOS commands, the data model will repeat itself for each interface instance. The structure of data (interface details) will remain same.

Only the values for the data elements (that is, the properties) will vary. Instead of repeating the same data model multiple times (where the number of repetition is also unknown), you can define a single data model and mark it dynamic for repeated occurrences of the same model. This is a looped data model, where the loop will be run for each instance.

Q. Are distance, length, start and end valid for both <Property> and <Header>?

A. Start and end are valid only for the <Header> tag. These start and end tags are used for specifying spatial information (that is, the starting and ending positions) of a particular column in tabular data. distance and length attributes are applicable only for the <Property> tag.

Q. Are <Option> elements valid within <Header> elements?

A. Yes, <Option> elements are applicable to both properties (<Property>) as well as column headers (<Header>).

Q. How do I come up with a length value in the <Property> tag?

A. The length value indicates the maximum words that can be combined to form the value. For example, in the CLI line: "Compiled Fri 22-Dec-06 03:12 by prod_rel_team", the keyword Compiled will have the date value which will always consist of 3 words "Fri 22-Dec-06 03:12" (day/date/time).

In this case length can have the value as 3 since the value will always consist of 3 words. If the value is -1, it means that all the words till end of the line or the start of the line, depending upon the direction of value with respect to keyword (whether value is in right or left of keyword specified), are combined to form a value.

Command Analyzer

You can find the complete usage details of Command Analyzer in Programmer's Guide for Cisco Enhanced Device Interface, at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html

The following are the FAQs for Command Analyzer:

Q. The required device family is not available in the list of devices that can be selected for the generation of report. Why is this?

A. The device package for that particular device may not be not present in the device package directory specified in the Setup wizard. To get the required device package:

a. Check whether the device package is available at this URL: http://www.cisco.com/cgi-bin/tablebuild.pl/E-DI-2.0.

b. If it is present, download the device package. You need to have your Cisco.com user login to download these packages

c. Re-enter the details in the Setup Wizard and submit it.

Q. How do I save the generated report?

A. After you have generated either the Commands Report or the Commands Comparison Report, use the Tools > Export to PDF option to save the generated report as PDF file in the file system.

Q. What do the colors in the report indicate?

A. To know more about the color indicators in the report, click on the hyperlink labeled Click here for the legends. The legends or colors being used in the report are described here.

Device Configuration Manager

You can find the complete usage details of Device Configuration Manager in User Guide for Cisco Enhanced Device Interface, at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html

Device Configuration Manager is also known as Config Manager.

The following are the FAQs for Device Configuration Manager (DCM):

Q. In the DCM Editor, syntax coloring does not appear. At times it appears to be incomplete. What should I do?

A. While you are working on the Editors, if the syntax coloring does not appear, or is incomplete, then you should refresh the Editor by right-clicking on the editor and selecting Refresh Editor, from the context menu.

Q. I cannot save the contents of the Editor. Why?

A. By default, you will not be able to save the contents of the Editor, unless you have made some changes to the content. If you want to save the contents, press the Enter key. Then right-click and select Save from the context menu. Your contents will be saved.

Q. How can one check the syntax of a configuration?

A. Open the command Editor in Device Configuration Manager and paste the contents of the configuration. Select the device type and OS version. The command Editor will highlight the content with the syntax colors. Any invalid configuration will be shown in red.

Q. How can Device Configuration Manager (DCM) be used for OS migration/upgradation?

A. One of the main tasks for the OS migration is to validate the current running configuration against the new OS Version.

The command Editor of DCM can be of help in this regard:

a. Open the command Editor and copy the current running configuration to this editor.

b. Select the target (new) DeviceType and OS Version from the version selector combo boxes.

The editor will highlight the contents with appropriate syntax colors. Any invalid configuration will be shown in red.

General

You can find the complete usage details of Cisco Enhanced Device Interface in:

•User Guide for Cisco Enhanced Device Interface

•Programmer's Guide for Cisco Enhanced Device Interface

at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html

The following are some Cisco E-DI FAQs:

Q. I am able to manage a device, but any device related operation fails.

A. Make sure that the firewall is disabled on the EDI server (use Linux commands iptables -L to list all the rules and iptables -F to clear on Linux). If eth0 and eth1 are in different subnet than the device, then add the default gateway to EDI configuration using ip default-gateway <ip address>. Do not assign any ipv6 address on eth0 and eth1. EDI supports only eth0 and eth1, it will not take the IP addresses that are allowed on any other interface.

Q. How can I find out what device packages are supported in this release?

A. To check the device packages that are supported in the current release of E-DI:

a. Start the E-DI service. To do this, see the procedure in the Installation and Setup Guide for Cisco Enhanced Device Interface 2.2.1.

b. Using the Telnet console, log into Cisco E-DI server using admin credentials.

c. At the prompt, enter sh server device-packages. The device packages are listed.

Q. I do not need all the device packages. How can I load only selected device packages? If I load only selected device packages, will it improve the performance of Cisco E-DI?

A. To load selected device packages:

a. Stop the E-DI service. To do this, see the procedure in the Installation and Setup Guide for Cisco Enhanced Device Interface 2.2.1.

b. Go to Cisco E-DI Install Location/dist/devpackages. This directory contains *.jdp files each for a given device family.

c. Rename the device packages that are not required, with the extension .old, for example.

d. Start the E-DI service. To do this, see the procedure in the Installation and Setup Guide for Cisco Enhanced Device Interface 2.2.1.

Yes, this will enhance the performance of Cisco E-DI in cases where you do not need all the device packages.

Q. If I need to download device packages from the IDU/Service Pack releases, where do I go?

A. You can download the device packages from: http://www.cisco.com/cgi-bin/tablebuild.pl/E-DI-2.0. You need

Install-related FAQs

You can find the installation and setup usage details of Cisco Enhanced Device Interface in:

•Installation and Setup Guide for Cisco Enhanced Device Interface 2.2.1, on Windows

•Installation and Setup Guide for Cisco Enhanced Device Interface 2.2, on Linux

at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html

Here are some FAQs related to Cisco E-DI installation:

Q. During the E-DI installation on Windows, I see that the postgress database setup has failed. What should I do?

A. Despite this message, continue with the installation. After completing the installation, uninstall E-DI. Stop security agent(s) if any are running, and then re-install E-DI. After successful installation, ensure that you start the security agents again.

Q. Database exceptions are being logged into /var/log/nemos.log. What should I do?

A. Stop and uninstall E-DI. Disable firewall settings if any, and install again. After installation, ensure that you enable the firewall settings again.

	Cisco Enhanced Device Interface User Guide 2.2.1
	Frequently Asked Questions
Cisco Enhanced Device Interface User Guide 2.2.1 Preface Introduction Using Cisco E-DI Maintaining the Network Managing Files Managing Security Configuring Devices Managing Inventories and Reports Scheduling Jobs Alarms Using Perl Scripts Creating and Using Macro Commands Translating commands using Command Translator Troubleshooting the Network Frequently Asked Questions Maintaining Cisco Enhanced Device Interface Cisco E-DI Commands and Associated Privileges Open Source Lincese Acknowledgment	Download this chapter Frequently Asked Questions Download the complete book User Guide for Cisco Enhanced Device Interface 2.2.1 on Windows (PDF - 6 MB) Feedback Table Of Contents Frequently Asked Questions Command Translator Macro Command Manager Command Modeler Operational Data Modeler Command Analyzer Device Configuration Manager General Install-related FAQs Frequently Asked Questions This section answers common questions associated with: •Command Translator •Device Configuration Manager •Macro Command Manager •Command Modeler •Command Analyzer •Operational Data Modeler •General •Install-related FAQs For the latest FAQs of Cisco Enhanced Device Interface, please check Cisco.com: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html Command Translator You can find the complete usage details of Command Translator in User Guide for Cisco Enhanced Device Interface, at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html The following are the FAQs for Command Translator: Q. The Command Translator reports translation errors for some of the lines in the converted Cisco IOS configuration file. How can I resolve these? A. Some cases require more information than the configuration file provides. For example, many QoS configuration commands have dependencies on ACLs or policies. If these commands are not included, the tool cannot provide a complete translation. In other cases, there simply is not a Cisco IOS equivalent command, as is the case with commands related to the CatOS sc0 interface. Sometimes, a command is intentionally not translated in order to require you to make a conscious configuration for a critical setting, such as the AAA services. For a list of CatOS commands that are not translated in this release, see the topic Untranslated CatOS Commands, in the section Translating Commands Using Command Translator, of the User Guide for Cisco Enhanced Device Interface at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html Q. Why does the Command Translator translate both the set port name and the set port description CatOS commands into the port description Cisco IOS interface configuration command? A. Cisco IOS does not have an equivalent to the CatOS set port name, but the set port name command is often used as a description. Therefore this command needs to translate to Cisco IOS. The dilemma occurs when both the set port name and the set port description CatOS commands are used, because ultimately only one command can be in effect in the Cisco IOS configuration. Both commands translate into the Cisco IOS translated configuration and you must delete whichever one is not needed. Q. Why are my sc0 interface commands not translated? A. Cisco IOS does not implement an sc0 interface. This is an architectural difference between CatOS and Cisco IOS. In Cisco IOS, any interface can be configured as a management interface. Q. Why are my banner-related commands not translated? A. The translation of the CatOS Banner into the Cisco IOS Banner is under consideration for a future release of the tool. Q. Why are my AAA-related commands not translated? A. These commands are critical in order to maintain access to the switch, therefore it is important to make a conscious effort to configure these parameters and not risk a blockage of access to the switch. Q. I use a Hybrid operating system with both CatOS and Cisco IOS on the MSFC. Can the tool integrate my MSFC Cisco IOS configuration as well? A. No, the tool cannot integrate the MSFC configuration into the translated CatOS configuration. Most of the MSFC Cisco IOS commands convert as-is into a new Cisco IOS switch configuration. Q. Can I use the output from a show run for the CatOS input file or does this have to be a full copy of the configuration file downloaded from the switch? A. You can use the show run output. Q. Do I have to provide a show module output for every conversion? A. The show module output is optional. The show module output only assists with certain set QoS commands. Q. What are the minimum software versions for CatOS and Cisco IOS supported by the tool? A. The Command Translator supports CatOS version 8.5.1 and earlier. The translated Cisco IOS configuration file can be based on Cisco IOS Software Release 12.2.18SXF3 or Cisco IOS Software Release 12.2.18.SXF5. Q. Is there a list or database of known CatOS commands that do not translate into a Cisco IOS equivalent? Yes. For a list of CatOS commands that are not translated in this release, see the topic Untranslated CatOS Commands, in the section Translating Commands Using Command Translator, of the User Guide for Cisco Enhanced Device Interface at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html. Macro Command Manager You can find the complete usage details of Macro Command Manager in User Guide for Cisco Enhanced Device Interface, at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html The following are the FAQs for Macro Command Manager: Q. The macros I created using the Macro Command Manager GUI were lost after the E-DI server stopped. A. Once the GUI changes are done, ensure that you perform a Save Macro Changes operation. Unless your changes are saved, they are not updated to the server database, and if the server restarts, these changes are lost. Q. Deploy macro command generates a message that the deploy was successful even though the command was not applied to the device. Why does this happen? A. The deploy macro command creates a temp file and uploads the file to the device using TFTP. A temporary file will be generated in server/temp folder. Check the contents of the file to see if they are valid on the device. Command Modeler You can find the complete usage details of Command Modeler in Programmer's Guide for Cisco Enhanced Device Interface, at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html The following are the FAQs for Command Modeler: Q. What are the jar files needed for compiling the code generated by EDI? A. nemo.jar, cliparser.jar, nodetypes.jar, log4j-1.2.8.jar, javolution.jar are needed for compilation. All these jar files are present under subfolders in the E-DI install directory. Q. What is the use of toXml () method provided in the generated class? A. The toXml () method generates the xml transformation of the CLI. This can be used along with the XML Programatic interface. Q. The required device family is not available in the list of devices that can be selected for the creation of unified model. Why is this? A. Device package for that particular device is not present in the device package directory specified in the Setup wizard. To get the required device package: a. Check whether the device package is available at this URL: http://www.cisco.com/cgi-bin/tablebuild.pl/E-DI-2.0. b. If it is present, download the device package. You need to have your Cisco.com user login to download these packages. c. Re-enter the details in the Setup Wizard and submit it. Q. Where are the generated Java files stored? A. The generated Java files are stored in the Code Output Directory specified in the Setup Wizard. Q. How do I enter the package name for the Java code generated by Command Modeler? A. During generation of code, you are prompted to enter a package name for the Java code. In the current release, there is no support for a default package. Operational Data Modeler You can find the complete usage details of Operational Data Modeler in Programmer's Guide for Cisco Enhanced Device Interface, at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html The following are the FAQs for Operational Data Modeler: Q. Is ordering of elements important in a Spec file? A. Yes, ordering of elements is important in a Spec file. Elements should be present in the same order as the order in which they appear in CLI from left to right and top to bottom. Q. I am not sure where I am allowed to use dynamic option of <Container>. A. Yes, you can use the dynamic option for looping data structures where multiple instances are possible for a particular data model. For example, in the output of show interfaces or show interface stats IOS commands, the data model will repeat itself for each interface instance. The structure of data (interface details) will remain same. Only the values for the data elements (that is, the properties) will vary. Instead of repeating the same data model multiple times (where the number of repetition is also unknown), you can define a single data model and mark it dynamic for repeated occurrences of the same model. This is a looped data model, where the loop will be run for each instance. Q. Are distance, length, start and end valid for both <Property> and <Header>? A. Start and end are valid only for the <Header> tag. These start and end tags are used for specifying spatial information (that is, the starting and ending positions) of a particular column in tabular data. distance and length attributes are applicable only for the <Property> tag. Q. Are <Option> elements valid within <Header> elements? A. Yes, <Option> elements are applicable to both properties (<Property>) as well as column headers (<Header>). Q. How do I come up with a length value in the <Property> tag? A. The length value indicates the maximum words that can be combined to form the value. For example, in the CLI line: "Compiled Fri 22-Dec-06 03:12 by prod_rel_team", the keyword Compiled will have the date value which will always consist of 3 words "Fri 22-Dec-06 03:12" (day/date/time). In this case length can have the value as 3 since the value will always consist of 3 words. If the value is -1, it means that all the words till end of the line or the start of the line, depending upon the direction of value with respect to keyword (whether value is in right or left of keyword specified), are combined to form a value. Command Analyzer You can find the complete usage details of Command Analyzer in Programmer's Guide for Cisco Enhanced Device Interface, at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html The following are the FAQs for Command Analyzer: Q. The required device family is not available in the list of devices that can be selected for the generation of report. Why is this? A. The device package for that particular device may not be not present in the device package directory specified in the Setup wizard. To get the required device package: a. Check whether the device package is available at this URL: http://www.cisco.com/cgi-bin/tablebuild.pl/E-DI-2.0. b. If it is present, download the device package. You need to have your Cisco.com user login to download these packages c. Re-enter the details in the Setup Wizard and submit it. Q. How do I save the generated report? A. After you have generated either the Commands Report or the Commands Comparison Report, use the Tools > Export to PDF option to save the generated report as PDF file in the file system. Q. What do the colors in the report indicate? A. To know more about the color indicators in the report, click on the hyperlink labeled Click here for the legends. The legends or colors being used in the report are described here. Device Configuration Manager You can find the complete usage details of Device Configuration Manager in User Guide for Cisco Enhanced Device Interface, at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html Device Configuration Manager is also known as Config Manager. The following are the FAQs for Device Configuration Manager (DCM): Q. In the DCM Editor, syntax coloring does not appear. At times it appears to be incomplete. What should I do? A. While you are working on the Editors, if the syntax coloring does not appear, or is incomplete, then you should refresh the Editor by right-clicking on the editor and selecting Refresh Editor, from the context menu. Q. I cannot save the contents of the Editor. Why? A. By default, you will not be able to save the contents of the Editor, unless you have made some changes to the content. If you want to save the contents, press the Enter key. Then right-click and select Save from the context menu. Your contents will be saved. Q. How can one check the syntax of a configuration? A. Open the command Editor in Device Configuration Manager and paste the contents of the configuration. Select the device type and OS version. The command Editor will highlight the content with the syntax colors. Any invalid configuration will be shown in red. Q. How can Device Configuration Manager (DCM) be used for OS migration/upgradation? A. One of the main tasks for the OS migration is to validate the current running configuration against the new OS Version. The command Editor of DCM can be of help in this regard: a. Open the command Editor and copy the current running configuration to this editor. b. Select the target (new) DeviceType and OS Version from the version selector combo boxes. The editor will highlight the contents with appropriate syntax colors. Any invalid configuration will be shown in red. General You can find the complete usage details of Cisco Enhanced Device Interface in: •User Guide for Cisco Enhanced Device Interface •Programmer's Guide for Cisco Enhanced Device Interface at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html The following are some Cisco E-DI FAQs: Q. I am able to manage a device, but any device related operation fails. A. Make sure that the firewall is disabled on the EDI server (use Linux commands iptables -L to list all the rules and iptables -F to clear on Linux). If eth0 and eth1 are in different subnet than the device, then add the default gateway to EDI configuration using ip default-gateway <ip address>. Do not assign any ipv6 address on eth0 and eth1. EDI supports only eth0 and eth1, it will not take the IP addresses that are allowed on any other interface. Q. How can I find out what device packages are supported in this release? A. To check the device packages that are supported in the current release of E-DI: a. Start the E-DI service. To do this, see the procedure in the Installation and Setup Guide for Cisco Enhanced Device Interface 2.2.1. b. Using the Telnet console, log into Cisco E-DI server using admin credentials. c. At the prompt, enter sh server device-packages. The device packages are listed. Q. I do not need all the device packages. How can I load only selected device packages? If I load only selected device packages, will it improve the performance of Cisco E-DI? A. To load selected device packages: a. Stop the E-DI service. To do this, see the procedure in the Installation and Setup Guide for Cisco Enhanced Device Interface 2.2.1. b. Go to Cisco E-DI Install Location/dist/devpackages. This directory contains .jdp files each for a given device family. c. Rename the device packages that are not required, with the extension .old, for example. d. Start the E-DI service. To do this, see the procedure in the Installation and Setup Guide for Cisco Enhanced Device Interface 2.2.1. Yes, this will enhance the performance of Cisco E-DI in cases where you do not need all the device packages. Q. If I need to download device packages from the IDU/Service Pack releases, where do I go? A. You can download the device packages from: http://www.cisco.com/cgi-bin/tablebuild.pl/E-DI-2.0. You need Install-related FAQs You can find the installation and setup usage details of Cisco Enhanced Device Interface in: •Installation and Setup Guide for Cisco Enhanced Device Interface 2.2.1, on Windows* •Installation and Setup Guide for Cisco Enhanced Device Interface 2.2, on Linux at: http://www.cisco.com/en/US/products/ps6456/tsd_products_support_series_home.html Here are some FAQs related to Cisco E-DI installation: Q. During the E-DI installation on Windows, I see that the postgress database setup has failed. What should I do? A. Despite this message, continue with the installation. After completing the installation, uninstall E-DI. Stop security agent(s) if any are running, and then re-install E-DI. After successful installation, ensure that you start the security agents again. Q. Database exceptions are being logged into /var/log/nemos.log. What should I do? A. Stop and uninstall E-DI. Disable firewall settings if any, and install again. After installation, ensure that you enable the firewall settings again.
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks