• commons-lang.jar
• commons-collections.jar
• commons-logging.jar
• commons-codec.jar
• dom4j.jar

• csu-1.0.jar is the main Cisco Smart Update JAR distribution. It contains the core toolkit functionality. Customers who use this distribution will be required to furnish their own required third-party JAR libraries as listed previously.
• csu-1.0-with-dependencies.zip contains the main Cisco Smart Update JAR distribution as well as required dependent third-party libraries. The following are the third-party library versions that are included in this distribution: commons-lang.jar 2.3, commons-collections.jar 3.2, commons-logging.jar 1.1, commons-codec.jar 1.3, and dom4j.jar 1.6.1. Many prior versions of these libraries should also work if required, however, customers should check with Fox Smart if a specific version of a library is supported.
• csu-1.0-docs.zip contains the Cisco Smart Update documentation (e.g. Javadoc). No libraries are included in this distribution.
• csu-1.0-all.zip contains the entire Cisco Smart Update distribution including everything in the other distributions (i.e. the toolkit library, third-party libraries, and documentation).

  -DFOXSMART_LICENSE_URL="file:///C:\temp\license.foxsmart.perm"

1. Obtain a copy of the CSU toolkit and an evaluation license from Fox Smart.
2. Place the csu.jar distribution and the third-party library distributions in your classpath.
3. Ensure the license file is in the JVM startup directory.
4. Create a test driver that connects to the router and display its running configuration.
5. Run the test driver.

  // Create a router object
  CiscoRouter router = new CiscoRouter("hostname", "password", "enablePassword");

  // Connect and login to the router
  router.login();

  // Get the router configuration
  CiscoRouterConfig routerConfig = router.getRunningConfiguration();

  // Disconnect from the router
  router.logout();

  // Display the configuration
  System.out.println("Router configuration: " + routerConfig.getOriginalIos());

• WARN displays information when problems are encountered that are not severe enough to thrown an exception.
• INFO displays useful runtime information such as router interaction, runtime parameters, configuration information, etc. that can be useful to monitor the toolkit's main functionality. Note that this log level (or any more detailed log level) will display router commands including sent passwords. As such, it is highly recommended not to use this debug level in a production environment.
• DEBUG displays extra information that helps monitor the toolkit flow (e.g. key method entry and exit points).
• TRACE displays detailed debugging information that includes raw data read from the router. This log level will produce a lot of output so it should typically only be used when debugging low level router communication issues.

  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">

  <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false">
     <!-- Console Appender -->
     <appender name="console.appender" class="org.apache.log4j.ConsoleAppender">
        <layout class="org.apache.log4j.PatternLayout">
           <param name="ConversionPattern"
                  value="%d{MMM dd yyyy HH:mm:ss} [%C{1}.%M] %m%n"/>
        </layout>
     </appender>

     <!-- Fox Smart Logging Configuration -->
     <logger name="com.foxsmart" additivity="false">
        <level value="info"/>
        <appender-ref ref="console.appender"/>
     </logger>

     <!-- Root Configuration -->
     <root>
        <level value="warn"/>
        <appender-ref ref="console.appender"/>
     </root>
  </log4j:configuration>

• Invalid Hostname: When an IP address can't be determined for the specified hostname, a java.net.UnknownHostException will be typically be thrown. When this happens, ensure an IP address can be determined for the specified hostname. A quick way to test if the hostname is recognized is to ping the hostname on your local machine. If the hostname can't be resolved, contact your network administrator.
• Connection Problem: If an IP address is specified or if an IP address can be successfully determined from the specified hostname, it is possible that a connection to the router can't be established. This will typically result in a java.io.IOException. Possible reasons for this type of exception could be that the IP address is not a Cisco router or the device with the specified IP address is down or does not exist. Another possible reason could be a firewall that is blocking the connection. CSU uses the telnet protocol to connect to and communicate with the router so a good test is to manually telnet to the router to ensure connectivity can be established.
• Invalid Username or Password: If the router requires a username or password for standard access and/or an enable password for “enable” access, these passwords must be passed to the CiscoRouter class. If the standard password is incorrect, a com.foxsmart.csu.AuthenticationFailedException will be thrown. If the enable password is incorrect, a com.foxsmart.csu.InvalidEnablePasswordException will be thrown. When this happens, ensure the username and passwords are correct and try again. This can be verified by connecting directly to the router using telnet or SSH, logging in, and gaining enable access with the specified username and passwords.
• License Exception: When CSU is run, it will ensure the license and usage is valid. This consists of a series of checks including whether the license file is valid, whether the license is expired, whether the device(s) being connected to are part of the license, etc. If any of these checks fail, a java.lang.Exception will be thrown. Note that an evaluation license will instruct the SDK to validate itself by contacting the Fox Smart web site at www.FoxSmart.com. As such, the Fox Smart web site must be network accessible or the toolkit will not function. This validation process occurs periodically (approximately once a day).

 C:\>java -DproxySet="true" -DproxyHost="proxy.domain.com" -DproxyPort="8080" ...

1. The Cisco router module and hardware configuration.
2. The output of the "show version" command on the router.
3. The output of the "show run" command on the router.