Home > 3Com > Router > 3Com Router User Manual

3Com Router User Manual

    Download as PDF Print this page Share this page

    Have a look at the manual 3Com Router User Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 19 3Com manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    Page
    of 762
    							Configure IPX 377
    Ta b l e 416   Configure IPX SAP updating period
    By default, the updating period of IPX SAP is 1 tick (i.e. 1/18 seconds).
    cConfigure SAP aging period
    Perform the following task in system view.
    Ta b l e 417   Configure SAP aging period
    By default, the service information which is not updated in three update 
    periods will be deleted.
    If a service information table item is not updated after 3 updating periods, it 
    will be deleted from the server information table. 
    dConfigure size of SAP updating message
    Perform the following task in interface view.
    Ta b l e 418   Configure size of SAP maximum updated message
    By default, the Max. length of the service update packet is 480 bytes.
    eConfigure reply to SAP GNS request
    You can set the processing mode of SAP GNS request by router:
    ■whether to reply with the nearest service information or by polling all 
    service information known by the router
    ■whether to reply to SAP GNS request or not
    Usually, a router will reply to GNS request with the service information of the 
    nearest server. There may also be exceptions: if the nearest server is local server, 
    then the router will not reply to the GNS request from this network segment.
    Please configure ipx sap gns-round-robin command in system view, and 
    configure
     ipx sap gns-disable-reply command in interface view.
    Ta b l e 419   Configure reply to SAP GNS request
    By default, a router replies to GNS request with the service information of the 
    nearest server.
    fConfigure length of service information reserve queue
    OperationCommand
    Configure SAP updating periodipx sap timer update seconds
    Restore default value of SAP updating periodundo ipx sap timer update 
    OperationCommand
    Configure SAP aging periodipx sap multiplier multiplier
    Restore default value of SAP aging periodundo ipx sap multiplier
    OperationCommand
    Configure size of SAP maximum updated messageipx sap mtu bytes
    Restore default value of size of SAP maximum updated 
    messageundo ipx sap mtu
    OperationCommand
    Configure Process GNS request in Round Robin 
    algorithmipx sap gns-load-balance
    Disable replying to GNS requestipx sap gns-disable-reply 
    						
    							378CHAPTER 24: CONFIGURING IPX
    If the length of a service information reserve queue is 1, the system saves only 
    one service information. If the server to which the only service information 
    corresponds is faulty, system will delete this information, and you cannot find 
    any server to provide such service while searching for the substitute service 
    information. When the length of a service information reserve queue exceeds 
    1, if one service information is deleted, it will be replaced with the next service 
    information as soon as possible, so that you will have no trouble finding server. 
    However, increasing the length of the service information reserve queue means 
    in turn increases the system memory that will be occupied by IPX module.
    Ta b l e 420   Configure length of service information reserve queue
    5Configure Using Touch-Off for an Interface
    RIP and SAP of IPX send updating broadcast packets periodically. If you do not 
    want routers to send broadcast packets all the time, touch-off can be used on an 
    interface, so that updating messages will be sent only when the route or the 
    service information changes.
    Perform the following task in interface view.
    Ta b l e 421   Configure Using touch-off for an interface
    By default, touch-off is disabled on the interface.
    6Disable Split-Horizon
    Split-horizon algorithm can avoid generating route loop. Split-horizon means that 
    routes received from a specific interface are not to be sent from this interface. In 
    special circumstances, split-horizon shall be disabled, sacrificing efficiency to 
    achieve correct transmission of routes. It is recommended not to disable the RIP 
    split-horizon unless necessary. Disabling split-horizon has no effect on 
    point-to-point links. 
    Perform the following task in interface view.
    Ta b l e 422   Disable split-horizon
    By default, split-horizon is enabled on the interface. 
    7Configure the Delay of Interface Sending IPX Packets
    The delay indicates the speed at which an interface forwards IPX messages: long 
    delay means slow forwarding, and short delay means Fast forwarding. In this way, 
    the delay is important for the system to decide the best routing. You can adjust 
    the value of delay for the interface to send IPX messages.
    Perform the following task in interface view.
    OperationCommand
    Configure length of service information reserving 
    queueipx sap max-reserve-server 
    length
    Restore default value of length of service information 
    reserve queueundo ipx sap 
    max-reserve-server
    OperationCommand
    Configure Using touch-off for an interfaceipx update-change-only
    Configure Disabling touch-off on an interfaceundo ipx update-change-only
    OperationCommand
    Disable split-horizonundo ipx split-horizon
    Enable split-horizonipx split-horizon 
    						
    							Configure IPX 379
    Ta b l e 423   Configure the delay of interface sending IPX packets
    By default, the delay of Ethernet interface is 1 tick, For asynchronous serial port is 
    30 ticks and that for WAN port is 6 ticks. The range of ticks is: 0~30000.
    8Configure Management of IPX Packet
    By default, the router usually discards the broadcast packet of type 20, but you 
    can also enable such packet to be sent to other network segments by configuring 
    routers.
    Perform the following task in interface view.
    Ta b l e 424   Configure management of IPX packet
    9Modify Encapsulation Format of IPX Frame on Interface
    Ta b l e 425   Encapsulation format of IPX frame
    Perform the following task in interface view.
    Ta b l e 426   Modify encapsulation format of IPX frame on interface
    By default, the encapsulation format of IPX frame on Ethernet interface is Ethernet 
    802.3, and that on WAN interface is PPP.
    10Configure IPX on WAN
    In the 3Com Router series, commands such as dialer route, fr map and x25 
    map
    , can be used to configure mapping from IPX address to link layer address, so 
    as to run IPX on WAN. For detailed configurations, refer to relative chapters in  
    Link Layer Protocol.
    OperationCommand
    Configure the Delay of Interface Sending IPX Packetsipx tick ticks
    Restore default value of interface delayundo ipx tick
    OperationCommand
    Enable propagation of broadcast packet of type 20ipx netbios-propagation
    Disable propagation of broadcast packet of type 20undo ipx netbios-propagation
    Interface typeEncapsulation format supported
    Ethernet interfaceEthernet_SNAP
    Ethernet_II
    802.3
    802.2
    WAN interfacePPP
    FR
    X.25
    OperationCommand
    Modify encapsulation format of IPX frame on an 
    interfaceipx encapsulation [ dot3 | 
    dot2 | ethernet-2 | snap ]
    Restore default value of encapsulation format of IPX 
    frame on an interfaceundo ipx encapsulation 
    						
    							380CHAPTER 24: CONFIGURING IPX
    Display and Debug IPXTa b l e 427   Display and Debug IPX 
    Ty p i c a l  I P X  
    Configuration ExampleI. Networking Requirement
    Networking with Router A and Router B. Here, both Server1 and Server2 are 
    installed with NetWare 4.1. Server1 is the master server, its external network ID is 
    2, packet encapsulation format Arpa, and internal network ID 937f. Server2 is the 
    slave server, its network ID is 3, packet encapsulation format is Snap, and internal 
    network ID is 9300. The node of Ethernet interface of Router A is 00e0.fc01.0000, 
    and its telephone number is 8810122. The node of Ethernet interface of Router B 
    is 0.0c91.f61f, and its telephone number is 8810124.
    II. Networking Diagram
    Figure 137   Networking diagram of IPX configuration example
    III. Configuration Procedure
    1Configure Router A:
    aActivate IPX
    [Router] ipx enable
    bActivate IPX module on interface Ethernet0, the network ID being 2
    [Router] interface ethernet 0
    [Router-Ethernet0] ipx network 2
    cSet encapsulation format of packets on Ethernet interface to Ethernet_II.
    [Router-Ethernet0] ipx encapsulation ethernet-2
    [Router-Ethernet0] exit
    OperationCommand
    Display interface status and interface 
    parameters of IPXdisplay ipx interface [ type number ]
    Display IPX router information tabledisplay ipx routing-table [ network | 
    static | default ] [ verbose ]
    Display IPX server information tabledisplay ipx service-table [ type 
    service-type | name name | network 
    network |  socket socket | order { net 
    | type } ] [ verbose ]
    Display type and quantity of packets 
    received and transmitteddisplay ipx statistics
    Clear IPX statistical information.reset ipx statistics
    PSTN
    Sever1
    1000.e0.fc01.0
    Tel:
    8810122Tel:
    88101241000.0.0c91.f61f
    Sever2
    2.e0.fc01.03.0.0c91.f61f
    Hub
    ModemModem
    Hub
    Router ARouter B 
    						
    							Configure IPX 381
    dActivate IPX module on interface Serial0, the network ID being 1000. 
    Configuring BDR parameter
    [Router] interface serial 0
    [Router-Serial0] dialer enable-legacy
    [Router-Serial0] dialer-group 1
    [Router-Serial0] ipx network 1000
    eConfigure an address map to Router B
    [Router-Serial0] dialer route ipx 1000.0.0c91.f61f 8810124
    [Router-Serial0] quit
    fConfigure a static route to network ID 3
    [Router] ipx route 3 1000.0.0c91.f61f tick 10 hop 2
    gConfigure a static route to network ID 9300
    [Router] ipx route 9300 1000.0.0c91.f61f tick 10 hop 2
    hConfigure an information about Server2 file service
    [Router] ipx service 4 server2 9300.0000.0000.0001 451 hop 2
    iConfigure an information about Server2 directory service
    [Router] ipx service 26B tree 9300.0000.0000.0001 5 hop 2
    jConfigure dialing rules
    [Router] dialer-rule 1 ipx permit
    2Configure Router B:
    aActivate IPX module
    [Router] ipx enable
    bActivate IPX function on interface Ethernet0, the network ID being 3
    [Router] interface ethernet 0
    [Router-Ethernet0] ipx network 3
    cSet encapsulation format of packets on Ethernet interface to Ethernet_SNAP
    [Router-Ethernet0] ipx encapsulation snap
    [Router-Ethernet0] quit
    dActivate IPX module on interface Serial0, the network ID being 1000. 
    Configuring BDR parameter
    [Router] interface serial 0
    [Router-Serial0] dialer-group 1
    [Router-Serial0] ipx network 1000
    eConfigure an address map to Router A:
    [Router-Serial0] dialer route ipx 1000.00e0.fc01.0000 8810122
    [Router-Serial0] quit
    fConfigure a static route to network ID 2
    [Router] ipx route 2 1000.00e0.fc01.0000 tick 10 hop 2
    gConfigure a static route to network ID 9300
    [Router] ipx route 937f 1000.00e0.fc01.0000 tick 10 hop 2
    hConfigure an information about Server1 file service
    [Router] ipx service 4 server1 937f.0000.0000.0001 451 hop 2 
    						
    							382CHAPTER 24: CONFIGURING IPX
    iConfigure an information about Server1 directory service
    [Router] ipx service 26B tree 937f.0000.0000.0001 5 hop 2
    [Router] ipx service 278 tree 937f.0000.0000.0001 4006 hop 2 
    jConfigure dialing rules
    [Router] dialer-rule 1 ipx permit 
    						
    							25
    CONFIGURING DLSW
    This chapter contains information on the following topics:
    ■DLSw Protocol Overview
    ■Configuration of DLSw 
    ■Display and Debug DLSw
    ■Typical DLSw Configuration Example
    ■Diagnosis and Troubleshooting of DLSw Fault
    DLSw Protocol 
    OverviewData Link Switch Protocol (DLSw) is a method designed by Advanced Peer-to-Peer 
    Networking (APPN) Implementers Workshop (AIW) to load SNA through TCP/IP 
    (SNA is a network protocol introduced by IBM in 1970s and completely 
    correspondent with OSI reference model). DLSw technology is one of the solutions 
    for implementing the transmission across WANs via SNA protocol.
    The operating principle of DLSw is shown in the following diagram:
    Figure 138   DLSw principle diagram
    From the above diagram, you may find out the router with DLSw transforms the 
    frame in format LLC2 on the local SNA equipment into SSP frame which can be 
    encapsulated into TCP messages. Then it sends SSP frame to the remote end 
    through TCP channel across WANs, and transforms SSP frame into the 
    corresponding frame in LLC2 format at the remote end site, finally sends the latter 
    to the next-hop SNA equipment. In another words, DLSw makes the local 
    terminating equipment “think” the remote equipment locates in the same 
    network. With the differences from transparent bridge, DLSw transforms the 
    original LLC2 protocol frame into SSP protocol frame instead of 
    transparent-transmitting to the next hop directly, so as to encapsulate the existing 
    data into TCP messages. It features local acknowledgement mechanism, thus 
    reducing unnecessary data transmission (confirming frame and maintaining alive 
    frame) and resolving the overtime problem of data link control.
    With DLSw technology, the transmission across TCP/IP via SDLC link protocol can 
    also be implemented. The procedure is to transform the messages in SDLC format 
    into the messages in LLC2 format, then utilize DLSw to intercommunicate with the 
    remote end. DLSw also supports intercommunication of different media between 
    LAN and SDLC.
    SSP
    TCP/IP
    LLC2LLC2
    LANLANEnd SystemEnd SystemDLSwDLSw 
    						
    							384CHAPTER 25: CONFIGURING DLSW
    Configuration of 
    DLSw DLSw configuration includes:
    ■Create DLSw local peer entity
    ■Create DLSw remote end peer entity
    ■Configure Bridge set connecting to DLSw
    ■Configure to add Ethernet port to Bridge set
    ■Configure link layer protocol for interface encapsulation to be SDLC
    ■Configure SDLC role
    ■Configure SDLC virtual MAC address
    ■Configure SDLC address
    ■Configure SDLC peer entity
    ■Configure XID of SDLC
    ■Configure to add the synchronous interface encapsulated with SDLC to Bridge 
    set
    ■Configure to stop running DLSw
    ■Configure baud rate of synchronous interface
    ■Configure encoding view of synchronous interface
    ■Configure idle time encoding view of synchronous interface
    ■Configure parameters of DLSw timer
    ■Configure other parameters of LLC2
    ■Configure other parameters of SDLC
    1Create DLSw Local Peer Entity
    Creating TCP channel is the first step for establishing DLSw connection. To create 
    TCP channel, you have to firstly configure DLSw local peer entity in order to 
    specify the IP address of the local end for establishing TCP connection, then the 
    request sent by the remote end router can be received for establishing TCP 
    connection. One router can only configure one local peer entity.
    Please process the following configurations in the system view.
    Ta b l e 428   Create DLSw local peer entity
    No DLSw local peer entity is created by default.
    2 Create DLSw Remote Peer 
    You need to configure the remote peer to establish TCP channel after configuring 
    the local peer. The router will continuously attempt to establish TCP connection 
    with the remote router. One router can configure several remote peers. TCP 
    channels can be connected with several remote end routers by configuring several 
    remote peers.
    OperationCommand
    Create DLSw local peer entitydlsw local ip-address [ init-window 
    init-window-size ] [ max-frame 
    max-frame-size ] [ max-window 
    max-window-size ] [ permit-dynamic ] 
    [ vendor-id vendor-id ]
    Delete DLSw local peer entityundo dlsw local 
    						
    							Configuration of DLSw 385
    Please perform the following configurations in system view.
    Ta b l e 429   Create DLSw remote end peer entity
    No DLSw remote end peer entity is created by default.
    When creating remote backup-peer, note:
    When the remote backup peer is created, the tcp ip-address should be the IP 
    address of peer backup entity and the 
    backup backup-peer-address should be 
    the IP address of the remote master peer, which has established TCP connection. 
    That is, the user should ensure that TCP connection has been established between 
    the local peer and the remote peer before creating a remote backup peer. When a 
    remote peer is created for the first time, meanwhile, the remote backup peer is 
    also being created, the system will prompt the following information:
     Primary 
    peer ip address does not exist 
    This prompt indicates that the user should create a remote master peer before 
    creating the backup peer.
    If the TCP connection of the master link fails, the backup link can be used to 
    maintain the connection (the backup TCP connection link can be found via the 
    display dlsw remote command) until its linger minutes  timeout.
    3Configure Bridge set Connecting to DLSw
    DLSw technology is developed on the basis of bridge technology. Bridge set is a 
    unit for forwarding by bridge. Several Ethernet ports can be configured into a 
    Bridge set in order to forward messages among them. To forward the messages of 
    the specified Bridge set to the remote end over TCP connection, you need to use 
    this command to connect a local Bridge set to DLSw. In another words, the 
    messages of the local Bridge set can be forwarded to the remote end through TCP 
    channel. You can use the command several times to connect several Bridge sets to 
    DLSw, so that all of them can be forwarded through TCP channel. 
    Please process the following configurations in the system view.
    Ta b l e 430   Configure Bridge set connecting to DLSw
    No Bridge set connecting to DLSw is configured by default.
    4Configure to Add Ethernet Port to Bridge Set
    LLC2 message on an Ethernet port can be forwarded to the remote end peer 
    entity through the corresponding TCP channel after the Ethernet port is added to 
    the Bridge set.
    OperationCommand
    Create DLSw remote end peer entitydlsw remote ip-address [ backup 
    backup-peer-address ] [ priority 
    priority-value ] [ max-frame 
    max-frame-size ] [max-queue 
    max-queue-length ] [ linger minutes ] 
    [ compatible { 3com | nonstandard } ]
    Delete DLSw remote end peer entityundo dlsw remote ip-address
    OperationCommand
    Configure Bridge set connecting to DLSwdlsw bridge-set 
    Bridge-set-number
    Delete Bridge set connecting to DLSwundo dlsw bridge-set 
    Bridge-set-number 
    						
    							386CHAPTER 25: CONFIGURING DLSW
    Please process the following configurations in the Ethernet interface view.
    Ta b l e 431   Configure to add ethernet port to Bridge set
    No Ethernet port is added to Bridge set by default.
    5Configure Link Layer Protocol for Interface Encapsulation as SDLC
    SDLC is a link layer protocol relative to SNA. The working principle is very similar to 
    HDLC. To allow DLSw to operate normally, the encapsulation protocol of 
    synchronous interface link layer should be changed to SDLC.
    Please process the following configurations in the synchronous interface view.
    Ta b l e 432   Configure link layer protocol for Interface encapsulation to be SDLC
    By default, the link layer protocol of synchronous interface encapsulation is PPP.
    Note that SDLC link protocol cannot load IP protocol, so you should remove all of 
    the commands related with IP, such as delete interface IP address, before 
    encapsulating SDLC.
    6Configure SDLC Role
    SDLC is a link layer protocol in the unbalanced mode. In another words, the 
    connected equipment on the both ends does not have unequal priority. One of the 
    parts is the primary station that plays the leading role and controls the whole 
    connection process and its role is primary. The other part is the secondary station 
    that is controlled in a passive mode and its role is secondary. Subscribers need to 
    configure role for the interface encapsulated with SDLC protocol.
    Please process the following configurations in the synchronous interface view.
    Ta b l e 433   Configure SDLC role
    SDLC role shall be configured according to the role of SDLC equipment connecting 
    with this router. If SDLC equipment connecting with the interface is primary, the 
    interface should be set to secondary. If the connected equipment is secondary, the 
    interface should be set to primary.
    Generally, the central IBM mainframes are primary, and terminal equipment is 
    secondary, such as Unix host and ATM machine.
    7Configure SDLC Virtual MAC Address
    Originally, DLSw is designed for LLC2 type of protocol to establish the mapping 
    relationship of virtual circuit through MAC address. Thus, you have to specify MAC 
    address for SDLC virtual circuit in order to allow SDLC message to participate in 
    OperationCommand
    Configure to add Ethernet port to Bridge setbridge-set 
    bridge-set-number
    Delete the configuration of adding Ethernet port to 
    Bridge setundo bridge-set 
    Bridge-set-number
    OperationCommand
    Configure link layer protocol for interface encapsulation 
    to be SDLClink-protocol sdlc
    OperationCommand
    Configure SDLC rolesdlc status { primary | secondary }
    Delete SDLC roleundo sdlc status 
    						
    All 3Com manuals Comments (0)

    Related Manuals for 3Com Router User Manual