Twitter Updates

    follow me on Twitter

    Friday, April 03, 2009

    AT&T Bonded NxT1 Internet Connection: MLFR Configuration

    ---------------Configuration Start---------------------
    ! we use two VWIC-2MFT-T1 cards in Cisco 2821 router,
    ! with 3 T1 from AT&T. We bonded them
    ! and get total 4.5MB internet bandwidth.
    ! Following is the actual configuration.
    ! Hope it helps.
    ! Please let me know if any questions.
    !
    no network-clock-participate wic 0
    no network-clock-participate wic 1
    !
    !
    voice-card 0
    no dspfarm
    !
    !
    controller T1 0/0/0
    framing esf
    linecode b8zs
    channel-group 0 timeslots 1-24
    !
    controller T1 0/0/1
    framing esf
    linecode b8zs
    channel-group 0 timeslots 1-24
    !
    controller T1 0/1/0
    framing esf
    linecode b8zs
    channel-group 0 timeslots 1-24
    !
    controller T1 0/1/1
    framing esf
    linecode b8zs
    channel-group 0 timeslots 1-24
    !
    !
    interface MFR0
    no ip address
    encapsulation frame-relay IETF
    frame-relay lmi-type ansi
    !
    interface MFR0.801 point-to-point
    description WAN
    ip address x.x.x.x 255.255.255.252
    no cdp enable
    frame-relay interface-dlci 801
    !
    ! Internal LAN interface
    !
    interface GigabitEthernet0/0
    ip address x.x.x.x 255.255.255.0
    duplex auto
    speed auto
    !
    interface Serial0/0/0:0
    no ip address
    !
    interface Serial0/0/1:0
    description Circuit ID: xxxxxxxxxxx
    no ip address
    encapsulation frame-relay MFR0
    no arp frame-relay
    frame-relay multilink lid link1
    !
    interface Serial0/1/0:0
    description Circuit ID: xxxxxxxxx
    no ip address
    encapsulation frame-relay MFR0
    no arp frame-relay
    frame-relay multilink lid link2
    !
    interface Serial0/1/1:0
    description Circuit ID: xxxxxxxxx
    no ip address
    encapsulation frame-relay MFR0
    no arp frame-relay
    frame-relay multilink lid link3
    !
    interface Serial0/3/0
    no ip address
    shutdown
    !
    ip route 0.0.0.0 0.0.0.0 x.x.x.x
    !
    ---------------Configuration End-------------------



    Here are some info from Cisco:
    ==========Quote start===========

    Configuring, Verifying, and Debugging Distributed Features

    This section covers the show and debug commands that are available to verify and debug each of the distributed features.

    Configuring and Verifying dMFR

    MFR Sample Configuration

    interface MFR1
    no ip address

    interface MFR1.1 point-to-point
    ip address 181.0.0.2 255.255.0.0
    frame-relay interface-dlci 16

    Note: The MFR interface is like another FR interface and hence supports most of FR configuration.

    interface Serial5/0/0/1:0
    no ip address
    encapsulation frame-relay MFR1
    tx-queue-limit 26

    interface Serial5/0/0/2:0
    no ip address
    encapsulation frame-relay MFR1
    tx-queue-limit 26

    interface Serial5/0/0/3:0
    no ip address
    encapsulation frame-relay MFR1

    Verify MFR Bundle Status on the RP

    show frame-relay multilink

    Bundle: MFR1, State = up, class = A, fragmentation disabled
    BID = MFR1
    Bundle links:
    Serial5/0/0/3:0, HW state = up, link state = Add_sent, LID = Serial5/0/0/3:0
    Serial5/0/0/2:0, HW state = up, link state = Up, LID = Serial5/0/0/2:0
    Serial5/0/0/1:0, HW state = up, link state = Up, LID = Serial5/0/0/1:0

    This indicates that two interfaces are added correctly, and one interface has not yet negotiated the MLFR LIP messages.

    To get more information on the MFR bundle and Member links, issue this command:

    show frame-relay multilink mfr1 detailed

    Bundle: MFR1, State = up, class = A, fragmentation disabled
    BID = MFR1
    No. of bundle links = 3, Peer's bundle-id = MFR1
    Rx buffer size = 36144, Lost frag timeout = 1000
    Bundle links:
    Serial5/0/0/3:0, HW state = up, link state = Add_sent, LID = Serial5/0/0/3:0
    Cause code = none, Ack timer = 4, Hello timer = 10,
    Max retry count = 2, Current count = 0,
    Peer LID = , RTT = 0 ms
    Statistics:
    Add_link sent = 35, Add_link rcv'd = 0,
    Add_link ack sent = 0, Add_link ack rcv'd = 0,
    Add_link rej sent = 0, Add_link rej rcv'd = 0,
    Remove_link sent = 0, Remove_link rcv'd = 0,
    Remove_link_ack sent = 0, Remove_link_ack rcv'd = 0,
    Hello sent = 0, Hello rcv'd = 0,
    Hello_ack sent = 0, Hello_ack rcv'd = 0,
    outgoing pak dropped = 0, incoming pak dropped = 0
    Serial5/0/0/2:0, HW state = up, link state = Up, LID = Serial5/0/0/2:0
    Cause code = none, Ack timer = 4, Hello timer = 10,
    Max retry count = 2, Current count = 0,
    Peer LID = Serial6/1/0/2:0, RTT = 32 ms
    Statistics:
    Add_link sent = 0, Add_link rcv'd = 0,
    Add_link ack sent = 0, Add_link ack rcv'd = 0,
    Add_link rej sent = 0, Add_link rej rcv'd = 0,
    Remove_link sent = 0, Remove_link rcv'd = 0,
    Remove_link_ack sent = 0, Remove_link_ack rcv'd = 0,
    Hello sent = 7851, Hello rcv'd = 7856,
    Hello_ack sent = 7856, Hello_ack rcv'd = 7851,
    outgoing pak dropped = 0, incoming pak dropped = 0
    Serial5/0/0/1:0, HW state = up, link state = Up, LID = Serial5/0/0/1:0
    Cause code = none, Ack timer = 4, Hello timer = 10,
    Max retry count = 2, Current count = 0,
    Peer LID = Serial6/1/0/1:0, RTT = 32 ms
    Statistics:
    Add_link sent = 0, Add_link rcv'd = 0,
    Add_link ack sent = 0, Add_link ack rcv'd = 0,
    Add_link rej sent = 0, Add_link rej rcv'd = 0,
    Remove_link sent = 0, Remove_link rcv'd = 0,
    Remove_link_ack sent = 0, Remove_link_ack rcv'd = 0,
    Hello sent = 7851, Hello rcv'd = 7856,
    Hello_ack sent = 7856, Hello_ack rcv'd = 7851,
    outgoing pak dropped = 0, incoming pak dropped = 0

    MFR Debug Commands

    These debugs are useful to troubleshoot issues where a link does not get added to the bundle.

    debug frame-relay multilink control

    Note: When a specific MFR interface or Serial interface is not specified, this enables debug for all MFR links. This can be overwhelming, if the router has a large number of MFR links.

    To debug MFR packets that are received at the RP, as well as to debug the MFR control activities, this debug is useful:

    debug frame-relay multilink

    Note: Under heavy traffic, this can overwhelm the CPU.

    Verify dMLFR Bundle Status on the LC

    show frame-relay multilink

    Note: Currently, this is not available on the LC, but it will soon be added. Until then, use show ppp multilink.

    Bundle MFR1, 2 members
    bundle 0x62DBDD20, frag_mode 0
    tag vectors 0x604E8004 0x604C3628
    Bundle hwidb vector 0x6019271C
    idb MFR1, vc 0, RSP vc 0
    QoS disabled, fastsend (mlp_fastsend), visible_bandwidth 3072
    board_encap 0x60577554, hw_if_index 0, pak_to_host 0x0
    max_particles 400, mrru 1524, seq_window_size 0x200
    working_pak 0x0, working_pak_cache 0x0
    una_frag_list 0x0, una_frag_end 0x0, null_link 0
    rcved_end_bit 1, is_lost_frag 0, resync_count 0
    timeout 0, timer_start 0, timer_running 0, timer_count 0
    next_xmit_link Serial0/0:1, member 0x3, congestion 0x3
    dmlp_orig_pak_to_host 0x603E7030
    dmlp_orig_fastsend 0x6035DBC0
    bundle_idb->lc_ip_turbo_fs 0x604A7750
    0 lost fragments, 0 reordered, 0 unassigned
    0 discarded, 0 lost received
    0x0 received sequence, 0x58E sent sequence
    DLCI: 16
    769719 lost fragments, 22338227 reordered,
    0 unassigned
    27664 discarded, 27664 lost received
    0xF58 received sequence, 0x8DE sent sequence
    timer count 767176
    Member Link: 2 active
    Serial0/0:0, id 0x1, fastsend 0x60191E34, lc_turbo 0x601913AC, PTH 0x603E7030, OOF 0
    Serial0/0:1, id 0x2, fastsend 0x60191E34, lc_turbo 0x601913AC, PTH 0x603E7030, OOF 0

    =============Quote end==============
    [ link (look for MLFR]

    Thursday, April 02, 2009

    Enable "telnet://" in your Internet Explorer.

    Just in case you need to enable "telnet://" in your Internet Explorer:
    --------------
    1.  Add the Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_DISABLE_TELNET_PROTOCOL
    2. Create a REG_DWORD (default) entry of name iexplore.exe
    3. Set that value to 0 (default).
    4. Restart IE

    -------------------------
    [ link ]

    Video Conferencing Test Sites

    ===========Quote Start==============

    IP TEST SITES:

    Dresden Germany 141.30.67.240

    Polycom Japan 61.197.225.89

    Polycom EMEA 140.242.46.50 - not always on

    Polycom Austin - lobby.austin.polycom.com - not always on

    Polycom also have a number of Ipower test systems 
    140.242.250 200
    140.242.250 201
    140.242.250 202

    Here's the test site for TANDBERG VIDEOCONFERENCING...
    TANDBERG 6000(HK)-203.194.77.168
    TANDBERG 7000 (HK)- 203.194.77.169
    TANDBERG 8000 (HK)- 203.194.77.167

    IP Address: 61.222.137.210 (Taiwan, Tandberg system). The machine may not be responding sometimes due to other use. Another one is always available. Pls dial 61.222.137.216 (DGT U&Me VideoPhone)

    Blue Star Conference Room   209.163.159.58

    LifeSize Conference Set-up 209.163.224.77
    Denver Cam (LifeSize)   64.15.104.134
    Denver Cam (Polycom VSX7000E)   64.15.104.142
    US CAPITOL 64.47.22.10
    Santiago, Chile 201.238.236.66
    Gumballs LifeSize  209.163.159.62
    Gumballs Tanberg Edge 95    209.163.159.46
    Gumballs Polycom HDX 9004   209.163.159.49
    Aquarium (Room)  209.163.159.60
    Aquarium (Express)  209.163.224.69
    TrainSize  209.163.224.76
    KittySize  209.163.224.75
    *VTC Test Callback  71.14.2.158 (Great for testing initial connections/configs.)
    HAMSTERsize: 207.114.244.82 and …83
    TOYsize: 207.114.244.85

    ===========Quote End==============