Redcell Device Driver Factory: FAQs
Get in the Driver Seat!
The Redcell Device Driver Factory tool provides the ability to create your own device drivers or enhance the functionality of an existing Redcell base device without having to write software code!
Device Drivers created with the DD Factory tool let Redcell discover network elements, show the condition of and report on their status, and configure network elements.
The DD Factory is available for developers who register.
Redcell Device Drivers
A device driver is component in Redcell, which directly communicates with a network device. The device driver allows for core management of your network devices using Redcell. Device Drivers are categorized into three levels, Base, Enhanced and Advanced.
- Base – provides basic, generic device driver features “out of the box”
- Enhanced – created using the device driver tool to add device specific features by enhancing a Base device driver
- Advanced – for drivers requiring forms, rules to support custom device discovery, resync, backup/restore and discrete Config functionality
The Redcell Device Driver Factory
The Driver Factory tool allows non-developers to create and test Redcell Device Drivers against their actual network elements that the driver is intended to support. The tool also allows for the creation and seeding of a device driver package that can be installed and deployed in a local or remote Redcell system. Once deployed in a Redcell system the driver now allows Redcell to support the following features:
- Device Discovery & Resync*
- Topology display
- SNMP Events & Syslog Management
- Backup/Restore/Firmware Deploy/Current Config/Compare
- Change Management
- Inventory Reports
- Direct Access
- Key Performance Indicators
- Custom Attributes
*SNMP – ifTable or Entity MIB based only. What is sometimes referred to as Deep Discovery requires an Advanced Device Driver to allow for custom work. For example, Deep Discovery could include the discovery and creation of Chassis, Cards, Modules, Slots, Ports, CPU’s, Flash, Power Supplies and Link Discovery
The tool kit package is approximately 565 MB in size (zipped) when downloaded.
The following are recommended operating systems and versions:
- Microsoft Windows®
Windows 2000(Pro, Server, Advanced Server), Windows 2003 (Standard, Enterprise and Web), Windows XP (Pro) with current patches applied, including SP2.
- Linux - Redhat® (Enterprise® version 4, 4r5 or 5)
SUSE® (version 9 or 10) Linux
- Sun Solaris® – v9 or v10
Hardware Recommendations include:
The Driver Factory package is installed as a dedicated, stand alone Single-Server system. It is not designed to be deployed on a Redcell production environment. Below are the minimum recommended configurations for a Single-Server installation:
- For MW Windows or Linux:
Intel Xeon or better, dual CPU w/dual core or quad core, 2GB RAM minimum, 40 GB minimum available disk space (or comparable)
- For Sun Solaris:
4 – 8 Core Ultra Sparc T-1 processor 8 GB RAM, 40 GB minimum available disk space (or comparable)
Yes, the following are system requirements for Windows and UNIX based installations. For more details consult the Redcell Installation Guide
- Windows Prerequisites:
This application requires a temp directory on the host where it is being installed. If the install launcher cannot extract a Java Virtual machine (JVM) then it cannot run. The launcher extracts a JVM to a temp directory and then starts the installer main using this temp JVM.
Although not always necessary, during installation or uninstalling best practice is to disable any virus protection software, and any other running applications.
This application cannot co-exist with other installations of Cygwin on the same Windows computer. Do no install it where Cygwin is already installed, either separately or as part of another application.
Windows 2000 installations require SP1 or higher. Firewall products should be disabled during initial installation and testing.
If they are present, turn off Microsoft Windows SNMP Services and Traps
- UNIX Prerequisites:
If you are installing on UNIX (Linux, Solaris) you must log in as a non-root user (with Oracle DBA rights, if you are installing on Oracle). UNIX installation prompts you to run some additional scripts as root.
When installing to UNIX, ensure you are installing as a user with the correct permissions, and are in the correct group. You must configure the installation directory so this user and group have all permissions (770, at least). You may install without any universal (“world” permissions. However, you must create a home directory for the installing user.
After downloading the package, in Windows, you can run win_install.exe from a file manager. To install on Linux or Solaris, run linux_install or sol_install.sh.
A dialog appears as the Setup program initializes InstallSheild. Then a Welcome Screen appears, listing the package you are about to install, and reminding you to shut down other running software (this may include anti-virus software). For additional installation and system configuration information consult the Redcell Installation Guide for details.
The Device Factory documentation:
For documentation click here.
Acquire Device Drivers:
Yes, to obtain a copy of one or more of the device drivers contact a Dorado Sales Representative @ email@example.com or call 1-800-555-1212.
Yes, using a source control system is independent of the tool itself. However, the tool does allow for some integration with a source control system by default. For details refer to the User Guide section of the Driver Toolkit documentation.
Yes, almost any IDE, which supports Java development, can be used in conjunction with the tool for advanced driver development. One of the most popular IDEs used internally at Dorado Software is Eclipse. For details on integrating and using Eclipse with the driver tool go to to the Driver Tool Kit documentation - Setting up Eclipse IDE for use with Device Drivers.
Samples of commonly used regular expressions are available on the web page. And there is a Regular Expression Tester available within the tool that includes a list of common regular expression commands. In the tool go to:
- Tools > Regular Expressions to open the tester.
Here are some things to gather before you begin:
- Device Access.
You should be able to ping the device and use telnet from the workstation intended for device driver development. If your network has firewalls then they need to permit both SNMP and Telnet port access to and from the network element and the workstation used for creating and testing the device driver
- At a minimum, the device must support some level of SNMP that provides a sysObjectId that uniquely maps to a device model
- Device IP Address
- SNMP Version (currently support is for versions 1 and 2c)
- SNMP Credentials for Read and Write Communities
- Device sysObjectId
- Enterprise MIBS
- Telnet Credentials. These are for command-line interface (CLI) transactions. They should include both user login and enable mode (privilege mode) needed to access device show and configure level commands
- Vendor Name and contact information
- Vendor-specific icon (16 x 16 pixels)
- Device Operating System version(s) to be supported
- Device's Command Reference Manual or access to on-line vendor's documentation
- Copy of device image file - the device's operating system file will be used for testing Deploy
There are several testing tools available from within the tool for testing SNMP and CLI based transactions. To fully test your driver simply register the driver with Redcell, start the application server, start the Redcell Client and run discovery against your target device.
You can contact Dorado Support by sending an email to firstname.lastname@example.org. Please provide the below information with your initial request. If any additional information regarding your issue is required we will contact you directly.
- Mention you are using the Driver Tool and describe your problem; be sure to include what action caused the problem and any results and or errors that may have occurred
- Provide the following information:
- Device Driver Editor Version – go to Help > About to get this information
- Device Vendor Name and Model of device
- Device OS version