WAN PORT SETUP GUIDE:

This document is for AB500 & AB600 (formerly Sonix Arpeggio family) and OfficeConnect 530.

The following is a collection of frequently asked questions, notes and guide to Wan port setup.

CABLE INFORMATION:

25pin male D-type to V.35; 34 pin male D-type (3c409001) is for many DSU/CSU connectors - most brands should work with our units.

25pin male D-type to V.24; 25 pin male D-type (3c409000) is for some DSU/CSU with RS232 25pin Female connectors. This is the default driver on the Wan port.

25 pin male D-type to X.21; 15 pin male D-type (3C409004) allows data transfer rates of up to 2.048Mb/s The V.24 will not work with just a gender changer - you need to use a V.24 cable specified in the user guide or buy it from a 3Com reseller. The units have pins strapped that detect X.21, V.35 or V.24 and invoke the correct port drivers so the appropriate cable must be used!

The WAN port lights will flash when the WAN is down or not connected properly. The strapping is necessary for Wan port auto detection. V.24/RS232 is the default driver, but it still needs the proper cable pinout per the manual to do the auto detection.

The WAN port on the unit is a standard RS232 25 pin female DTE port and it runs synchronous data, ( it needs clocking externally) and DTR is currently raised all the time.

NON-LEASE LINE CONNECTIONS:

AB600 can dial out using asynch AT commands and switching to synch on receipt of DCD (carrier detect signal). Go to TYPE on the Wan Port and select DIAL. All others units (AB500 & OfficeConnect Remote 530) would have to use Synchronize modems that can autodial themselves to use a dial up connection rather than a Leased Line. That means the phone number is stored in that synchronize modem’s memory (since these units will not generated by AT dial commands ) which calls the other modem when DTR is raised. So you would power up the receive modem first then power up the dial modem. Note: the 3Com Impact will not work on this port since it does not have the auto dial feature.

TROUBLESHOOTING:

Examine the Wan1 port, go to CO PO highlight the WAN port, Type EX (return)

Status: up or down In Signals: DSR=DCD:CTS (AB600 In Signal = DSR:CD)

Physical: v.35 or v.24 Out Signals: DTR:RTS

The status should be up and the WAN LED light should be solid, if the connection to DSU/CSU and between the DSU/CSU’s are correctly established. To verify where the problem is you can a loopback between DSU/CSU’s themselves, then on each side between DSU/CSU & Unit. For a more detail description of how to do a Loopback test, download our document on our 3Com.com Web site under Support, ISDN, Support Tips, "Loopback Tests on the AB400/500/600 and Office Connect Routers"

BASIC UNIT SETUP FOR A WAN CONNECTION;

QC NAME, name the unit (case sensitive), IP Address of this unit’s LAN port with a correct

subnet mask, you can use defaults if you are bridging.

CO PO, Highlight & Edit WAN PORT, you can leave at defaults or edit to your specifications.

FOR IPX: go to CO PO, Highlight & Edit LAN PORT, and enter correct Network numbers and Frame types.

This should be all you need for IP or IPX bridging. If you are on different networks then you

will need to setup for routing. The following is a step by step guide:

SETTING UP IP/IPX ROUTING OVER WAN LINKS:

This document is for AB500, AB600 (formerly Sonix Arpeggio) and Office Connect 530.

The following section provides a step-by-step guide to setting up IP and/or IPX routing over fixed WAN links. It is assumed the WAN link is already successfully established.

1. Give the unit a name: Connect to the local unit and change the name on the QC NAME screen.

2. Configure the LAN port: Edit the LAN port configuration via the CO PO screen. Set the IP address & subnet mask and/or IPX network address for this LAN port. If necessary, change the frame type used by IPX to the same type as used on the directly connected network.

3. Configure the WAN port(s): Set the IP address & subnet mask and/or IPX network address for the WAN port(s) to the desired network address (see diagram for an example of a numbered link).

Change the name in the port name field to the remote units name (this case sensitive).

For IPX: Set the frame type used by IPX to the same type as used on the directly connected network.

4. Save the configuration: Save the address information before the routing functionality is enabled.

5. REM to the remote unit (NoName): Use the REM facility to telnet into the remote unit.

At the command prompt type REM, at REM menu highlight the remote unit and type REM again,

the remote unit should respond with "Enter Password" type in the default which is "PASSWORD"

Repeat steps 2 to 4 for the remote unit.

Note! The telnet connection will when you change IP address will be lost during this process. Press CTRL D to get back to your local unit. Repeat the REM when necessary. Save the configuration.

6. Enable Routing on the remote unit *

Enable routing on this (the remote) unit in CO RO PA screen.

If routing to both IP and IPX, enable IPX first

*Note! 1) When enabling IP routing, the connection will be lost again. You will not be able to get back into the unit until the IP routing information has been learned by both units.

2) If Routing Unnumbered, a Static Route MUST be entered in the IP Routing table of the remote unit BEFORE IP routing is enabled, otherwise you will lose the connection

USING UNNUMBERED LINKS: You can use an unnumbered link, but in that case you will need to add a static route to each of the unit’s IP routing table:

CO RO IP, Add - using our example IP & unit information the screen for SITEA would be:

Target: 140.200.10.0 (use the beginning number of the entire network)

Subnet Mask: 255.255.0.0

Router: SITEB

Hop Count: 1

Advertise Route: ENABLED

Permentant: ENABLED

CO RO IP, Add - using our example IP & unit information the screen for SITEB would be:

Target: 206.100.100.0 (use the beginning number of the entire network)

Subnet Mask: 255.255.255.0

Router: SITEA

Hop Count: 1

Advertise Route: ENABLED

Permentant: ENABLED

With a numbered link, as in this example the routes should already show up in the IP routing table after they have been learned from both sides, you verify the routes in the IP and/or IPX table. The IP routes are necessary to allow the ability to use the REM feature for remote management of the units set up for routing.

7. Enable Routing on the local unit: CO RO PA

8. Wait for the Routing Table to be updated: Go to the IP routing table CO RO IP screen and wait until the screen is dynamically updated with the routes learned from the remote unit. This will not happen with unnumbered links.

9. Save the configurations: Save the updated configurations for both the local and remote units

10. The following is an simple IP/IPX routing example; you will need to substitute your correct network information:

IP/IPX Routing WAN