Asynchronous Digital Subscriber Line (ADSL) users connect to the Cisco 6510 and the service provider's network using a Windows application called the Dashboard. This application allows users to access one or more services.
If you purchased the Cisco User Control Point (UCP) product, the Dashboard installation program is provided in the Dashboard folder of the installation disk. If you are using the Cisco 6510 with another authentication, authorization, and accounting (AAA) server, the Dashboard is provided through another distribution medium. You might want to make the Dashboard available to end users as a download from the Internet.
The Dashboard folder contains the following files:
- dashboard.exe--Executable file for the Dashboard.
- dashboard.ini--Dashboard configuration file.
- dash_shl.exe--Dashboard shell executable. The dashboard shell appears as a tray icon on the Windows taskbar.
- dash_shl.ini--Dashboard configuration file.
- dashboard.hlp--Dashboard help file.
- dashboard.cnt--Dashboard help contents file.
- pktdump.txt--Packet information file used for debugging (optional).
- custom.gif--GIF image for customization.
- filecopy.avi--AVI file required by dashboard.exe.
- uninst.isu--Dashboard uninstallation file.
To customize the Dashboard installation program and make it available for download, complete the following steps:
Step 1 Edit the dashboard.ini file and specify the following:
- VegaLocation--Specify the IP address of the Cisco 6510.
- VegaPort--Specify the port of the Cisco 6510.
- Shared Secret--Specify a text string that represents the shared secret the Dashboard uses to communicate with the Cisco 6510.
- The following example shows lines from a dashboard.ini file with typical settings:
VegaLocation=128.100.58.100
Vegaport=1645
Shared Secret=secretstring10
Note These options can also be configured by starting Dashboard and selecting Dashboard Options from the Options menu.
Step 2 Compile the edited dashboard.ini and all other Dashboard files into a self-installing executable, such as dashboard.exe. See the "Creating a Self-installing Executable" section.
Step 3 Users always have access to the Cisco 6510. However, they cannot access any services unless they are authenticated. Use the DefaultServerIP parameter to specify an IP address that users can access without authentication.
Step 4 Make the executable available from this IP address.
Step 5 Instruct end users to download the executable by giving them the URL.
To create a self-installing executable, use an application such as InstallShield to peform the following tasks:
- Copy all files except oleaut32.dll to the target directory. The target directory can be any directory the user chooses.
- Copy the oleaut32.dll file to the System or System32 directory where Windows 95 or Windows NT is installed.
- Configure the Dashboard Shell to load on startup by placing a shortcut to the Dash_shl.exe file in the Startup folder.
- Write the full path of the Dashboard executable to the Dash_shl.ini file. For example:
[Options]
DashboardPath=C:\Dashboard\Dashboard.exe
- Start the Dashboard Shell immediately after installation.
Note Before creating a self-installing executable, you must modify the Dashboard.ini file to contain the correct entries for the VegaLocation, Vegaport, and Shared Secret parameters.
To install the Dashboard using the Cisco-supplied executable, follow these steps:
Step 1 Open Windows Explorer. Locate and double-click DashboardSetup.exe .
Step 2 Follow the on-screen instructions and, when prompted, reboot the system.
Step 3 Open the dashboard.ini file with a text editor and do the following:
- VegaLocation--Specify the IP address of the Cisco 6510.
- VegaPort--Specify the port of the Cisco 6510.
- Shared Secret--Specify a text string that represents the shared secret the Dashboard uses to communicate with the Cisco 6510.
- The following example shows lines from a dashboard.ini file with typical settings:
VegaLocation=128.100.58.100
Vegaport=1645
Shared Secret=secretstring10
Note These options can also be configured by starting Dashboard and selecting Dashboard Options from the Options menu.
Step 4 Save your changes and exit the file.
Step 5 Configure TCP/IP settings. Make sure to enter a domain name for resolving Domain Name System (DNS) requests that are not fully qualified.
