|
|
This chapter describes how to develop a CFG file. The CFG file has the advantage of being able to control the windows displayed to the end user and to test the connections. The disadvantage is that you are limited to the scenarios supported by Cisco 800 Fast Step Setup.
The recommended procedure for developing CFG files is as follows:
Step 2 Save the drafted CFG file by using the Save File As window.
Step 3 Open the CFG file in a text editor.
Step 4 Change the parameters to the custom configurations.
Step 5 Save the file as Cisco 800 Fast Step CFG file. (This option is offered after you have developed the configuration.)
You can distribute the file by placing the CFG file:
The result is that end users cable their routers, run Setup, select the configuration file, and they are done.
This section describes some of the CFG file modifications that can be made to control the behavior of Setup and the configuration output to the router.
[PC to Router Connection] ConnectionType=
If the flag value is set to 2, the connection type defaults to Ethernet.
If the flag value is set to 3, the connection type defaults to the console cable.
You can force the end user to skip all data-entry windows and go directly to the configuration test. If you have created a configuration that provides all the configuration parameters and you want the end user to only use Setup to test the connection, you can skip all screens and display the Test window. The flag syntax is as follows:
[Skipped Dialogs] SkipToSetupandTest=
If the flag value is set to 0 or blank, the windows are displayed.
If the flag value is set to 1, Setup skips to the Test window.
You can skip testing and download the configuration to the router. This flag is often used when IOS commands that do not follow the predefined Cisco 800 Fast Step scenarios are included in the configuration. Although the configuration might be valid, it might fail testing because it is not based on a recognized Cisco 800 Fast Step scenario. If you skip testing, the configurations are assumed to be correct and are downloaded to the router. The flag syntax is as follows:
[Setup Type] SetSkipTesting=
If the flag value is set to 0 or blank, the connections are tested.
If the flag value is set to 1, all the testing in Setup is skipped.
[SkippedDialog] ReviewSettings= 1
The flags used to skip windows are as follows:
[SkippedDialog] SkipToSetupandTest= ReviewSettings= RemoteConnectionType= TypeOfProtocolsServices= RouterTypeDeviceSetupMethod= CostControlSettings= YourISDNPhoneNumbers= ISDNSettings= RemotePhoneNumbersISP= RemotePhoneNumbersRCN= PPPUsernameAndPasswordISP= PPPUsernameAndPasswordRCN= TestingInterfaceConnectionISP= TestingInterfaceConnectionRCN= IPAddressRangeGivenByYourISP= WANIPAddressAndMaskISP= WANIPAddressAndMaskRCN= IPXWANAddressRCN= NextConnection= InternetServerConnection= InternetServerTypeSelection= InternetServersIPAddressesGivenbyISP= LocalInternetServers= LANTrafficControl= LANIPAddressAndMaskForEthernet0= IPXLANAddressAndFrameTypeForEthernet0= DomainNameServerSettings= WINSSettings= StartRouterSetup= SaveFileAs= StartMonitoring= DLCINumberISP= DLCINumberRCN= FrameRelayDLCINumberISP FrameRelayDLCINumberRCN PCToRouterConnection= RestartToCompleteSetupInitial= RestartToCompleteSetupFinal=
If the flag value is set to 0 or blank, the window is displayed.
If the flag value is set to 1, Setup skips the window.
Typically, when there is a single ISDN connection, it is not necessary to enter a central router name parameter. The prompt for this parameter can be hidden from the end user. The flag syntax is as follows:
[PPPSettings] HideCentralRouternameISP= HideCentralRouternameRCN=
If the flag value is set to 0 or blank, the central router name is hidden.
If the flag value is set to 1, the central router name is shown.
 |
Note The flag ISP extension refers to Internet service provider (ISP). The flag RCN extension refers to remote corporate network (RCN). |
You can use this flag to force the router to reset to the factory default configuration. The flag syntax is as follows:
[Setup Type] SetRouterToDefaultConfig=
If the flag value is set to 1, the router is write-erased and rebooted without prompting the end user.
If the flag value is set to 0 or blank, after a connection to the router is established, Setup prompts the user to append or erase the existing configuration.
Advice-Of-Charge (AOC) time-outs for the user connected to the NET3 switches is supported and controlled using the flags SetAOCTimeout, which determines AOC timeout in seconds, and AOCShortHoldTimeout, which determines the minimum idle time before the line is dropped. The default is 120 seconds.
The flag syntax is as follows:
[ISDNSettings] IdleTimeoutISP= IdleTimeoutRCN= SetAOCTimeout= AOCShortHoldTimeout=
If the IdleTimeoutISP flag is set to 1, the router disconnects from the dialer when there in no traffic to the ISP.
If the IdleTimeoutRCN flag is set to 1, the router disconnects from the dialer when there in no traffic to the remote corporate network.
If the value of the SetAOCTimeout flag is set to 1, the dialer ISDN short-hold value time command (where time is the number of seconds) is placed in the dialer map-class with a value equal to the AOCShortHoldTimeout flag.
If AOC is not supported on the network and the SetAOCTimeout flag is set to 1, timeout duration set by the IdleTimeoutISP flag or the IdleTimeoutRCN flag is applied.
If the value of the SetAOCTimeout flag is set to 0 or blank, Advice of Charge is not supported.
The flags in the CFG file that manage the cost-control features are described in this section.
Restrict data transfers to one channel by disabling the multilink feature of Point-to-Point Protocol (PPP). The flag syntax is as follows:
[Cost Control Settings] SetRestrictToOneDataChannel=0
If the flag value is set to 1, PPP multilink is disabled, and the data transfers through one B channel.
If the flag value is set to 0 or blank, PPP multilink is enabled, and data transfers through two B channels.
Data transfers through the ISDN service can be restricted to specific times of the day and time duration. The flag syntax is as follows:
[Cost Control Settings] SetRestrictTimeOfDayWhenDataCallsCanBeMade=0 SetStartTime= SetEndTime=
If the flag value is set to 1, data transfer is allowed during the time of the day specified by the SetStartTime and the SetEndTime flags.
If the flag value is set to 0 or blank, the data connection is allowed at all the times of the day.
SetStartTime indicates the time the router begins allowing data through the connection. The parameter is indicated in 24-hour format.
SetEndTime indicates the time the router stops allowing data through the connection. The parameter is indicated in 24-hour format.
When using an ISP-only configuration to a single destination, with or without the firewall filters, the preferred configuration is to prevent NetBIOS traffic from needlessly bringing up the ISDN line. This prevents broadcast WAN and LAN messages from wasting money. The flag syntax is as follows:
[Remote Network Interface Settings] SetNetBiosFilterOnISP [Local LAN Ethernet0 Settings] SetNetBiosFilterOnE0=
If a flag value is set to 1 (default), the NetBIOS filter is enabled. The IOS access-list commands added to the current dialer access list will be as follows:
access-list <<number>> deny udp any any eq netbios-ns access-list <<number>> deny udp any any eq netbios-dgm access-list <<number>> deny tcp any any eq 139
If a flag value is set to 0 or blank, the NetBIOS filter is disabled.
The Success window appears when the Service Selection feature is enabled. This window provides the end user with the option to test the connections and to display technical support information.
The flag syntax and default parameters are as follows:
[Service Selection] ISPSuccessText1= Your file has been successfully created. ISPSuccessText2= Setup another router using Cisco Fast Step ISPSuccessText3= Change the setup on this router by rerunning Cisco Fast Step Setup and selecting the router named <<fill in name here>> ISPSuccessText4= Setup routers for others using a Cisco Fast Step setup file (Press the Help button for more information)
The Success window displays the text strings indicated by the ISPSuccessTextX flags, where X is line 1 through 4. (There is no on-screen help topic for this window.)
The technical support information displayed in the Technical Support window is customized by modifying the text string for the related flag. For example, the following entry displays a telephone number:
[TechSupportInfoDetail] Title= PhoneDescription1="ISP Technical Support" Phone1=408.408.4081
The flag syntax is as follows:
[TechSupportInfoDetail] Title= PhoneDescription1= PhoneDescription2= PhoneDescription3= PhoneDescription4= Phone1= Phone2= Phone3= Phone4= EmailAddress= ServiceProviderURL=
The Title flag is not the title of the Technical Support window in Monitor. The flag describes the assistance center whose e-mail address, phone numbers, and URL are given. By default this flag has the value CISCO Technical Assistance center.
PhoneDescriptionX flags provide telephone technical support contact information, where X is the line 1 through 4.
PhoneX flags provide telephone numbers, where X is the line 1 through 4.
EmailAddress flag provides e-mail technical support contact information.
ServiceProviderURL flag provides Web site technical support information.
You can include IOS commands to the router in the [Additional IOS Commands] section of the CFG file. You cannot enter show, debug, interactive commands, or any command that alters the LAN side IP or IPX addressing. The flag syntax is as follows:
[Additional IOS Commands] cmd1=
Enter an IOS command as if you were typing it on a command line during a Telnet session and cmdn= is the prompt. Commands are sequenced by the cmdn= string, where the n is an integer number that determines the sequence of the commands, for example, cmd1=, cmd2=, and so forth.
The first command in the Additional IOS Commands section must be cmd1=configure terminal. Then list the remaining global configuration mode commands.
To enter commands for a specific interface (say the Ethernet0 interface), enter the command cmdn=interface ethernet 0.
For example:
[Additional IOS Commands] cmd1=configure terminal cmd2=access-list 30 permit any cmd3=interface ethernet 0 cmd4=keepalive 100 cmd5=end
Setup configures the IP stack of the PC and the IP address of the router for the end user. You can modify the IP addressing parameters by using the CFG flags.
It is assumed that the end-user PC used to configure the router is the same PC as the one that will be used to communicate over the WAN. Before running Cisco 800 Fast Step, the end-user PC can be in one of three states:
If there is no IP stack in Windows 95, Setup asks Windows to install an IP stack. The new IP stack defaults to DHCP without a leased IP address.
Windows 98 and Windows 2000 use a modified algorithm that gives the PC a temporary, unique static address when no DHCP server is found. Setup assumes that no leased IP address exists and treats all operating systems the same.
The router requires the Ethernet interface to have an IP address to communicate with the PC over Telnet, yet it has only the factory-default configuration at this stage. This creates a state where neither the PC nor the router has an IP address. To overcome this, an algorithm temporarily assigns an address to the Ethernet interface. (The PC must have a functioning IP stack for the algorithm to work.)
A PC running Setup sends a DNS request to new-router.cisco.com, a request that the router is listening for. The router takes the originating IP address and uses the Address Resolution Protocol (ARP) to find a free address, either above or below the originating address.
Where there is no IP stack or no DHCP address, Setup assigns a temporary static address to the PC and later resets the PC to DHCP.
Unless you are using Windows 2000, changing the PC addressing requires that the PC be rebooted twice, once when Setup configures the PC IP stack and once after router setup and testing are complete. (If you are using Windows 2000, it is not necessary to reboot the PC.) If the PC has no IP stack, the LAN has never had an IP addressing scheme, so Setup imposes the most logical configuration:
Setup uses the same scheme for a PC that is set as a DHCP device with no IP address. We suggest that you use this scheme for the majority of installations.
If the PC has DHCP with a valid address, Setup assumes there is a DHCP server on the LAN, and the PC IP stack remains untouched. The router searches for a temporary IP address by using ARP, starting at the PC IP address. The IP stack remains untouched. Because the DHCP server is local, it could assign public IP addresses because the IP addressing scheme could be chosen at random. Setup uses (PAT) to hide the DHCP server IP addresses from the ISDN interface.
If the PC has a static IP address, it is assumed that the IP address of the PC is part of the intended network design. The router uses ARP to find a free, temporary IP address, starting at the first IP address that allows communication between the router and the PC. However, communication between the PC and the Internet or intranet only occurs if the default gateway of the PC is set to the IP address of the router Ethernet interface. Setup alters the PC's default gateway to match the router default gateway after setup and test.
Setup changes the IP stack settings on the PC to match the settings on the router, so you can test the connection from the PC to the Internet. It does this by checking:
If necessary, it also changes the stack settings to the appropriate values.
You can override the way Setup changes the PC IP stack and router LAN IP settings by changing appropriate settings in the CFG file.
When delivering thousands of routers, the most scalable LAN addressing scheme should be chosen. We suggest using PAT with the PC as the client, the router as the server, and DHCP enabled.
You can change the behavior of Cisco Fast Step so that the PC IP stack is modified as determined by the program code. The flag syntax is as follows:
[PC Settings] SetAutomaticChangeIPStackWhenNeededByFastStep=
If this flag is set to 1, the automatic IP stack configuration algorithm is used. The IP stack changes are made according to the algorithm described in the "Default Behavior" section.
If this flag is set to 0 or blank, IP stack configuration proceeds according to the other flags listed under the PC Settings heading. For example:
[PC Settings] SetForceStaticAddressOnPCAlways=0 ForceStaticIPAddress= ForceStaticIPMask= UseRouterLANIPAsPCGateway=0
If the default gateway IP address is on the same subnet as the PC, the LAN IP address of the router takes the value of the default gateway of the PC.
If the default gateway is not on the same subnet as the PC and the router LAN IP address is on the same subnet as the PC, the default gateway takes the value of the router LAN IP address.
If the default gateway is not on the same subnet as the PC and the router LAN IP address is not on the same subnet as the PC, the default gateway of the PC is not modified, and the router is configured with the IP address entered by the end-user.
The flag is automatically enabled when Setup connects the PC to the router by using a Telnet session. If the PC is connected to the router by using the console cable, this flag is implemented only if the SetAutomaticChangeIPStackWhenNeededByFastSTep flag is set to 0 and the SetChangeIPStackOnConsole flag is set to 1.
The flag syntax is as follows:
[PC Settings] UsePCGatewayAsRouterLANIP=
If this flag is set to 0 or blank, the PC gateway address is not set to the router LAN IP address.
If this flag is set to 1, the PC gateway address is set to the router LAN IP address.
This flag sets the router LAN IP address to the PC default gateway address, so the PC can communicate with the router. If the router LAN IP address is not on the same subnet as the PC, this flag is ignored, and nothing is changed.
If the flag UsePCGatewayAsRouterLANIP is set to 1 and the UseRouterLANIPAsPCGateway flag is set to 1, the UsePCGatewayAsRouterLANIP flag is given the preference, and the UseRouterLANIPAsPCGateway flag is ignored.
For a Telnet connection, if the DHCP server is not enabled on the router and this flag is set to1, Setup checks the PC default gateway IP Address and the router LAN IP address. If they are different, Setup sets the PC gateway with the router LAN IP address.
For a console cable connection, Setup checks the SetChangeIPStackOnConsole flag. If it is set to 1 and the UseRouterLANIPAsPCGateway flag is set to 1, Setup sets the router LAN IP address as the PC default gateway. If DHCP server is enabled on the router, this flag is not used.
The flag syntax is as follows:
[PC Settings] UseRouterLANIPAsPCGateway=
If this flag is set to 0 or blank, the router LAN IP address is not set to the PC gateway address.
If this flag is set to 1, the router LAN IP address is set to the PC gateway address.
Setup can configure the DHCP relay on the router. This can only be configured by using the CFG file; the user is not prompted for this information, and it cannot be configured through a TPL file.
The SetDHCPRelay flag turns DHCP relay on, and the RemoteDHCPServerAddress flag sets the IP address of the DHCP server. The command-line syntax is as follows:
RemoteDHCPServerAddress
We recommend that you force the PC to be a DHCP client and not to show the LAN IP addressing dialogs. The flag syntax is as follows:
[DHCP Relay Settings] SetDHCPRelay= RemoteDHCPServerAddress=
If the value of SetDHCPRelay the flag is set to 0 or blank, the end-user PC is configured as a DHCP client, but with the DHCP server present across the WAN. The remote DHCP server is indicated in the RemoteDHCPServerAddress flag. (This is the typical Cisco telecommuter setup.)
If the SetDHCPRelay flag value is set to 1, the flags are ignored.
You can force static addressing on the PC. For this feature to be active, the SetAutomaticChangeIPStackWhenNeededByFastStep flag should be set to 0.
[PC Settings] SetForceStaticAddressOnPCAlways= ForceStaticIPAddress= ForceStaticIPMask=
For a Telnet connection, if the SetForceStaticAddressOnPCAlways flag is set to 1, Setup sets the PC with the IP address and subnet mask as indicated in the ForceStaticIPAddress and ForceStaticIPMask flags. Setup sets the PC default gateway IP address by using the router LAN IP address.
If the SetForceStaticAddressOnPCAlways and SetRouterAsDHCPServerOnE0 flags are both set to 1, the SetForceStaticAddressOnPCAlways flag is ignored, and the SetRouterAsDHCPServerOnE0 flag is given preference.
The following is an example of a CFG file that configures a Cisco 804 router:
[PC to Router Connection] ConnectionType=2 [DHCP Server in Router] SetRouterAsDHCPServerOnE0=0 [DHCP Relay Settings] SetDHCPRelay=0 RemoteDHCPServerAddress= [PC Settings] UsePCGatewayAsRouterLANIP=0 SetAutomaticChangeIPStackWhenNeededByFastStep=1 SetChangeIPStackOnConsole=0 SetForceStaticAddressOnPCAlways=0 ForceStaticIPAddress= ForceStaticIPMask= UseRouterLANIPAsPCGateway=0 SetAdjustPCStackSettings=1 [Belle Systems] SetBelleSystemSupport=0 RebootCount=-1 ISPSetupURL=http://www.cisco.com/go/faststep ISPLocalURL=http://www.cisco.com UniqueID=4 [Service Selection] ShowTestConnectionButton=1 ShowTechSupportInfoButton=1 ISPSuccessText1= ISPSuccessText2= ISPSuccessText3= ISPSuccessText4= UniqueID=5 [Local LAN Ethernet0 Settings] SetNetBiosFilterOnE0=0 LANIPAddressE0=192.135.243.111 LANIPSubnetMaskE0=255.255.255.0 [Router Security] RouterName=Router804 ReadonlyPassword=Password EnablePassword=SuperSecret [Setup Type] SetRouterToDefaultConfig=1 SetSkipTesting=0 SetRunMonitorNow=0 [ISDN Settings] EnableAOCTimeout=0 AOCShortHoldTimeOut=120 SwitchType=5 SwitchSpeed=3 SPID1= SPID2= IdleTimeoutISP=300 LoadThresholdISP=10 HoldQueueISP=10 [Remote Phone] RemotePhoneNumberISP1=9506000 RemotePhoneNumberISP2= [PPP Settings] HideCentralRouternameISP=0 UserNameISP=remote PasswordISP=lab CentralRouterISP= [NAT Settings] HidePAT=0 HideAddressRange=0 HideNetworkAddress=0 [Remote Network Interface Settings] SetNetBiosFilterOnISP=0 WANIPAddressISP=0.0.0.0 WANIPSubnetMaskISP=255.255.255.0 AutomaticWANIPAddressDiscoverISP=6 [Skipped Dialogs] SkipToSetupandTest=0 PCToRouterConnection=0 ReviewSettings=0 SaveFileAs=0 StartMonitoring=0 TestingInterfaceConnectionISP=0 RemoteConnectionType=0 ISDNSettings=0 RemotePhoneNumbersISP=0 PPPUserNameAndPasswordISP=0 WANIPAddressAndMaskISP=0 NextConnection=0 LanIPAddressAndMaskForEthernet0=0 UniqueID=6 [TechSupportInfoDetail] Title= PhoneDescription1= PhoneDescription2= PhoneDescription3= PhoneDescription4= Phone1= Phone2= Phone3= Phone4= EmailAddress= ServiceProviderURL= [Additional IOS Commands] cmd1= ;************************************************************************************ ;The flags below this line are private to Cisco Fast Step. Please do not modify them. ;************************************************************************************
Posted: Mon May 22 14:06:54 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.