--------------------------------------------------------------------------- --** Gandalf 5242i EdgeRouter FAQ version: 0.1 **-- --------------------------------------------------------------------------- v0.1: Two confirmed bugs and counting! --- Disclosure: This document is presented to you to try and reduce the initial confusion of this new software. I hope you can get everything running the first time but if you don't... don't even try to blame me! All normal disclosures apply. Assumptions: ** This document is designed to explain how to make a 5242 EdgeRouter lock up two B-channels (128K) forever. I will try to make notes in this document for a setup to initially connect up one B-channel and use the second B-channel for bandwidth-on-demand. (much more common configuration) ** This FAQ assumes your are somewhat familiar with MS Windows, TCP/IP and the Gandalf 5242i ISDN unit. ** I have written this document with a full example for illustrative purposes and there is an ASCII diagram at the end of this FAQ to refer to if you get confused. ** You must have a STATIC route made on your source router for your new network to work correctly. For this document, I made a static route in the router tables for the 132.241.254.X to be reachable via the ISDN server (132.241.160.10). Many of you SHOULD be asking why isn't the static route pointing to the ISDN WAN IP address? Good Question! Gandalf's documentation tells you to do this, but it DOESN'T work! Until I've been told or shown otherwise, you need to do it this way. To Do: Include a full command-line text file of this example for all you Non-Windows enabled people out there. [ Syntax of this document ] ** = This means to definately take note * = Usually means an action to be taken, "Click on [OK]" kind of thing. +-----------------------------------------------------------------------+ | This document is very rough and might be down right poorly written | | (hey, I'm an engineer!) but I would have REALLY appreciated a FAQ like| | this when I was dealing with all this. So, if you have suggestions, | | comments, etc, feel free. | | | | David Ranch: E-mail: dranch@ecst.csuchico.edu | | WWW: http://www.ecst.csuchico.edu/~dranch | +-----------------------------------------------------------------------+ --------------------------------------------------------------------------- ## Step 1 ## --------------------------------------------------------------------------- --Using the Express Windows console-- (requires just a serial cable) ** The express setup software "supposedly" works under Windows 95 and actually worked for me ONCE but broke after that. I recommend you use Windows v3.x until they release a true Win95 client. So go ahead and load up "xsetup.exe" Choose to CONTINUE with the express setup and configure the unit as follows: * 5242 Operation: IP Edge Router | +-IP Addresses: (See below for a ASCII illustration of this example | configuration) | +--Local Address: The TCP/IP address of the 5242ER for the Ethernet | | interface. Since the 5242ER is going to act as | | your offical router, give it a router-like IP | | number, ie "132.241.254.1" | | | +--Local NetMask: Anything you choose. | Ie. "255.255.255.0" for a Class C network | +--Remote Address: The static TCP/IP address that the remote ISDN | | server will communicate ALL data traffic through. | | ie. "132.241.160.35" | | | +--Remote NetMask: Anything you choose. | Ie. "255.255.255.0" for a Class C network | +-Default Gateway: The Default gateway of the remote network. This is for when the 5242ER has data traffic that it doesn't know what to do with, it will forward it to this interface. * Click on "OK" * ISDN Setup: Choose the ISDN Service type that your local ISDN provider gave you. We typically choose "AT&T Point-to-Point" for our ISDN lines. * Click on "OK" * Numbers to Dial: | +-- Primary Number: the ISDN number that your tring to connect to. | Ie. "5021" for our Pacific Bell centrex. | +-- Overflow Number: the same number as above if your allowed to do bandwidth-on-demand or lockup a full 128K pipe. * Click on "OK" * Security Setup: Type of Security: | +-- NONE: This is NOT a good option, don't use it. | +-- PAP: A decent authentication but the Gandalf Xpressway | RLAN can NOT connect to a remote 5242 EdgeRouter | without CHAP authentication! | +-- CHAP: The best and most secure authentication. You must use this for bi-directional dial-on-demand connections to 5242 EdgeRouters and Gandalf Xpressway RLANs. Security Secrets: | +-- Local Name: The name you have given to the EdgeRouter | and also to the account name on the | Xpressway. ie: "5242ER-dranch" | +-- Remote Name: The name you have given to your remote | Xpressway ISDN server. | ie: "Xpressway-BRI" | +-- System Secret: The PAP/CHAP password that will be used for authentication. Though the EdgeRouter will let you put in a long password, the Xpressway RLAN software will only take a 8-character password. ie: "PaSswd19" NOTE: CASE matters!!! * Click on "OK" * Setup Summary: | +-- Make sure everything looks correct and then go ahead | and click on: "Export to 5242i". | | | +-- Select Comm Port: Your serial port to the EdgeRouter | | Ie. "COMM2" and | | | +-- Click on "OK" You can also save the configuration to a file for multiple setups if you wish. If everything goes well, you will be shown a little status box that will tell you roughly what the software is doing and then tell you: "Your 5242i has been successfully configured." Click on "Ok" and get ready for the next step. --------------------------------------------------------------------------- ## Step 2 ## --------------------------------------------------------------------------- --Using the full Windows console-- (requires a configured ethernet card and and PC running Windows with a TCP/IP address on the same network as your 5242 EdgeRouter. Ie. My PC's TCP/IP address is 132.241.254.2 and the EdgeRouter address is 132.241.254.1 * Ok, go ahead and load up "5242.exe" You will be prompted for a password, go ahead and click on "OK" * Goto "File", "Setup Comm": | +-- Brouter IP address: enter in your 5242ER's IP address. | ie. "132.241.254.1" | +-- Community Name: leave this as "system". This has to do with SNMP and this document does not discuss this. * Click on "OK" If the software connects ok, you will notice the title bar will change to the MAC-layer address of the EdgeRouter and the TCP/IP address of the EdgeRouter. If this doesn't happen, make sure you can ping the EdgeRouter from Windows. If you can't, most likely, your TCP/IP stack is mis-configured. See the top of this document for a hint! * Goto "View", "System Info": | +-- Name: Give the EdgeRouter a name. I recommend to stay consistant | with the common setup. ie. "5242ER-dranch" | +-- Location: You can enter in the location of the ISDN unit if you | wish. ie. "CSU Chico" | +-- Contact Person: Like above, you can enter in who is responcible for | the unit. ie. "David Ranch : CSRV : x5511" | ** | Date and Time: As of 2/29/96, the date and time will NOT save into | the bridge's NV-RAM. This bug has been reported. | +-- Micro Console Password: You can put a password into the EdgeRouter so users cannot see or screw-up your setup. ie. "goaway" * Click on "OK" * Next, goto "View", "Destination Table" Here, you will see the EdgeRouter's local Ethernet interface named "NET1". Below that, you will see ten destination entries for remote ISDN sites. You can have the EdgeRouter dial-on-demand to up to ten different sites. A pretty cool feature but most people won't need ten entries. ** This document is designed to explain how to make a 5242 EdgeRouter lock up two B-channels (128K) forever. I will try to make notes in this document for a setup to initially connect up one B-channel and use the second B-channel for bandwidth-on-demand. * Ok, double-click on "Net 1" | +--Destination Name: I would recommend to change this name to be | | consistant with the naming convention in this | | document. ie. "5242ER-dranch" | | * | +--Click on "Apply" to save it. | | * | +--Click on "Close" | * Double-click on "Destination 1" | +--Destination Name: Again, I would recommend to change this name | | to be consistant with both the naming convention | | in this document and how the ISDN system works. | | ie. "Xpressway-BRI" | | * | +--Click on "Apply" to save it. | * +--Click on "Bandwidth Managment" ** This is the main screen where you can change options such as data compression, IPX spoofing, etc. As mentioned above, this document is limited in scope and is intended for a permanent link. This document does not cover any bridged or spoofing aspects of the Gandalf 5242i units. ** If you plan to do Bandwidth-on-Demand, then just change the "Threshhold overflow and Backup" parameters as you like. Once you have changed these options, you can skip the rest of this and the following sections. If your not sure of what these three parameters are, here is a breif look: | +-- Threshhold: The percentage of the first B-channel | being completely used before it dials | up the other B-channel. The default | is 75%. | +-- Overflow Connect: This determins a delay period | that the the Threshold level is | being exceeded before it actually | dials the second line. | +-- Idle/Underflow: Like above, this is a delay period that once two B-channels are dialed up but the first B-channel is not exceeding the Threshold level, that the EdgeRouter will dis-connect the second B-channel connection. ** For a locked-up 128K connection, de-select "Threshold Overflow and Backup" Authentication Protocol: | | This is displayed as configured from the | ExpressSetup. It should be fine as-is. | Note: | +-- Peer Identity: This is the DESTINATION PAP/CHAP | name. ie. "Xpressway-BRI" | +-- Peer Secret: This is the PAP/CHAP secret. ie: "PaSswd19" Network Control Protocols: Don't worry about these. Wide Area Network Selection List: | * +-- Double-click on the top "Pool 1" entry. | | * | +-- Under "WAN Type", select, "Permanent" | | * | +--Click on "Apply" and then "Close" | * +-- Double-Click on the bottom "Pool1" entry | * +-- First, un-select the "enable" box | at the top of the window. | | * | +--Click on "Apply" and then "Close" | * +-- Again, double-click on the bottom "Pool1" entry | * +--RE-select the "enable" box at the top | of the window. | * +--Change the name of the "Resource Pool" | from "Pool 1" to "Pool 2" | * +--Under "Wan Type", select "Permanent" | * +--Click on "Apply" and then "Close" * Click on "Refresh" to make sure everything updated ok. * Click on "Apply" and then "Close" * Click on "Refresh" to make sure everything updated ok. * Click on "Apply" and then "Close" * Again, click on "Refresh" to make sure everything updated ok. * Click on "Close" (This following section is only for the 128K Permanent connection configuration) * Goto "View", "Interface Table" | * +-- Double click on "Link 2" | | * | +-- Un-Check the "Enable" box at the top of the window | | * | +-- Click on "Apply" and then "Close" | * +-- Again, double-click on "Link 2" | | * | +-- Change the name in the "Resource Pool" field from | | "POOL 1" to "POOL 2" | | | * | | +-- Now click on the "Enable" box at the top of the | | window | | * | +-- Click on "Apply" and then "Close" | * +-- Click on "OK" * Goto "Protocol", "802.1D" | ** +-- Make sure that the "Enable 802.1D Bridging" box is un-checked | * +-- Click on "Apply" and then "Close" * Goto "Protocol", "IP" | ** +-- Make sure "IP Routing" is enabled | | You will notice that your IP Default Gateway is "0.0.0.0". Again, | this is another bug and Gandalf has been notified. | * +-- So go ahead and change this to the default gateway of your | ISDN server. Ie. "132.241.160.1" | * +-- Click on "Apply" and then "Close" * Goto "File", "Save". Click on "OK" to save these new changes to the EdgeRouter's NV-RAM. * Finally, goto "Maintinance", "Reset", and click on "OK" to restart your bridge and let the new changes take effect. Thats it! Now the bridge should reset and lock up the channels as expected. If it doesn't work, check out the logs on the 5242i and on the ISDN server. Most likely you will just have authentication problems if any. --David ( ASCII Diagram) ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: +------------------------------------------------+ | Cisco 7000 router | | | | Ethernet IP: 132.241.160.1 | | | | Static Route: 132.241.254.0 via 132.241.160.10 | +------------------------------------------------+ | | Ethernet LAN | +---------------------------+ | Gandalf RLAN Xpressway | | Name: Xpressway-BRI | | IP: 132.241.160.10 | +---------------------------+ I | <--(Pacific Bell Centrex ISDN #: 5021) S | D | N | | <-- Static WAN (ISDN) IP address: 132.241.160.35 L | I | N | E | <--(Pacific Bell Centrex ISDN #: 4281) +---------------------+ | 5242ER | | |<----> 132.241.254.X network | IP: 132.241.254.1 | | Name: 5242ER_dranch | +---------------------+ ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Inital Micro-Console commands: (VERY incomplete) * To show current dial-out options: destination * To show current Bridge/Router options: 802.1d * The Gandalf Edge Router uses a term called "IfIndex" which is a table for the various interfaces: Local LAN : 1 Primary Link : 2 Secondary Link : 3 Destination : 4 To disable Spanning tree Bridging: 802.1d,modify,disable To modify the PPP name and password: ppp,modify,pppname,ppppasswd ie. "ppp,modify,5242ER-dranch,PaSswd19" -----