IPSLA (Testing Jitter/Delay/Frame-Relay)

hey guys, testing my network using IPSLA but its strange how when i connect a router to the network and input the IPSLA commands it says it fails everytime? Im a student doing my project btw and am unsure why its not sending through the network. I have connectivity and can ping across the entire network. the commands i used were -
ip sla monitor 12
type jitter dest-ipaddr
192.168.0.10 dest-port 5060
frequency 300
exit
ip sla monitor schedule 12 start-time now live forever
then when i use the statistics command to show the output it says failed :S am i missing a step somewhere, or do i have to advertise the router in my network? im very confused :/

Could you include the config for the IP SLA receiver as well if you have it configured?
Excellent reading on the topic: http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipsla/configuration/15-mt/sla-15-mt-book/sla_udp_jitter.html

Similar Messages

  • Is Low MTU (ie 320) for VoIP over Frame-relay can be used to avoid serialization delay for large data packets?

    In order to provide voice quality for VoIP, is FR fragmentation equivalent to lowering the MTU size for the serial subinterface of a Frame relay subinterface?
    Is there any isues like stop communications, using Low MTU ?

    If the router belongs to any of the
    platform listed below, then use
    FRF12 for you fragmentation. The MTU size
    lowering also works but this can cause a high over
    head as it can't be specified on a per dlci level.
    With multiple dlci i.e. subinterfaces use per dlci fragmentation.. this helps reduce the overhead of changing the MTU size of the physical interface.
    Snip config example.( __Must be configured on both side of the termination___)
    PHONE 3333312---ROUTERA ----DLCI 100----ROUTERB ---PHONE 2111123
    ROUTER A
    dial-peer voice 1 voip
    destination-pettern 2T
    session target ipv4:10.10.10.2
    int ser 0/0
    encap frame-relay
    frame-relay traffic-shaping
    no ip address
    interface serial0/0.1 point-to-point
    ip add 10.10.10.1 255.255.255.252
    frame-relay interface-dlci 100
    class voice
    map-class frame-relay voice
    frame cir 64000
    frame bc 640
    frame mincir 64000
    frame-relay ip rtp priority 16384 16383 48
    frame fragment 80
    frame fair-queue 64 256 0
    ROUTER B
    dial-peer voice 3 voip
    destination-pettern 3T
    session target ipv4:10.10.10.1
    int ser 0/0
    encap frame-relay
    frame-relay traffic-shaping
    no ip address
    interface serial0/0.1 point-to-point
    ip add 10.10.10.2 255.255.255.252
    frame-relay interface-dlci 100
    class voice
    map-class frame-relay voice
    frame cir 64000
    frame bc 640
    frame mincir 64000
    frame-relay ip rtp priority 16384 16383 48
    frame fragment 80
    frame fair-queue 64 256 0
    This should help if your router is
    c2600, c3600, mc3810, c7200, c1750
    all running the right level of IOS.
    12.1(5)T and above should work well.

  • ASR1K 5xE1 MFR Frame relay traffic not forwarding in one direction

     Dear Techies, 
     Hope all is well !
    Im doing this inter-op testing with Alcatel device for frame-relay and MFRs and got stuck at this situation which is actually mind boggling and I think i might be missing something "silly" :-(
    Its a simple setup of
    1. My ASR 1002-X with a LAN (Gig0/0/0) port is connected to a traffic generator.(ixia).
    2. ASR WAN port is a 5xE1 bundled into a MFR circuit.
    3. WAN link goes to a Alcatel box giving me my FR-DCE with E1s over MFR.
    Issue is , I can send traffic to max throughput with  flow initiated from  LAN to WAN bit NOT the reverse flow initiated  from WAN side to LAN port. I see traffic coming into my 5xE1s (1.8 mbps each) but the traffic just wont go to the LAN side , somewhere it gets "stuck" or "dropped".
    PING works fine from both sides.......but sending traffic is not possible !!
    ASR CONFIG
    controller SONET 0/3/0
     framing sdh
     clock source line
     aug mapping au-4
     au-4 1 tug-3 1
      mode c-12
      tug-2 1 e1 1 unframed
      tug-2 1 e1 2 unframed
      tug-2 1 e1 3 unframed
      tug-2 2 e1 1 unframed
      tug-2 2 e1 2 unframed
      tug-2 2 e1 3 unframed
     au-4 1 tug-3 2
      mode c-12
      tug-2 1 e1 1 unframed
      tug-2 1 e1 2 unframed
      tug-2 1 e1 3 unframed
     au-4 1 tug-3 3
      mode c-12
    interface MFR1
     no ip address
     encapsulation frame-relay IETF
     load-interval 30
     frame-relay multilink bid 10MB-PiPe
     frame-relay multilink bandwidth-class a
     frame-relay lmi-type ansi
    interface MFR1.1 point-to-point
     ip address 10.10.17.2 255.255.255.0
     frame-relay interface-dlci 100   
    interface GigabitEthernet0/0/0
     no ip address
     load-interval 30
     negotiation auto
    interface GigabitEthernet0/0/0.110
     encapsulation dot1Q 110
     ip address 11.11.11.1 255.255.255.0
    interface Serial0/3/0.1/1/1/1:0
     no ip address
     encapsulation frame-relay MFR1
     frame-relay multilink lid First-Link
    interface Serial0/3/0.1/1/1/2:0
     no ip address
     encapsulation frame-relay MFR1
     frame-relay multilink lid Second-Link
    interface Serial0/3/0.1/1/1/3:0
     no ip address
     encapsulation frame-relay MFR1
     frame-relay multilink lid Third-Link
    interface Serial0/3/0.1/1/2/1:0
     no ip address
     encapsulation frame-relay MFR1
     frame-relay multilink lid Fourth-Link
    interface Serial0/3/0.1/1/2/2:0
     no ip address
     encapsulation frame-relay MFR1
     frame-relay multilink lid Fifth-Link
    SDH_FR#sh frame-relay mul
    SDH_FR#sh frame-relay multilink 
    Bundle: MFR1, State = up, class = A, fragmentation disabled
     BID = 10MB-PiPe
     Bundle links:
      Serial0/3/0.1/1/1/1:0, HW state = up, link state = Up, LID = First-Link
      Serial0/3/0.1/1/2/2:0, HW state = up, link state = Up, LID = Fifth-Link
      Serial0/3/0.1/1/2/1:0, HW state = up, link state = Up, LID = Fourth-Link
      Serial0/3/0.1/1/1/3:0, HW state = up, link state = Up, LID = Third-Link
      Serial0/3/0.1/1/1/2:0, HW state = up, link state = Up, LID = Second-Link
    SDH_FR#
    SDH_FR#
    SDH_FR#
    SDH_FR#sh fram
    SDH_FR#sh frame-relay pvc 100
    PVC Statistics for interface MFR1 (Frame Relay DTE)
    DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = MFR1.1
      input pkts 8045          output pkts 8044         in bytes 515748    
      out bytes 527920         dropped pkts 0           in pkts dropped 0         
      out pkts dropped 0                out bytes dropped 0         
      in FECN pkts 0           in BECN pkts 0           out FECN pkts 0         
      out BECN pkts 0          in DE pkts 0             out DE pkts 0         
      out bcast pkts 0         out bcast bytes 0         
      5 minute input rate 1000 bits/sec, 2 packets/sec
      5 minute output rate 1000 bits/sec, 2 packets/sec
      pvc create time 01:07:58, last time pvc status changed 01:07:58
      fragment type end-to-end fragment size 1400
    SDH_FR#
    SDH_FR#
    SDH_FR#
    SDH_FR#
    SDH_FR#
    SDH_FR#
    SDH_FR#ping 10.10.17.1-------------------------------------------------------------------------- THIS IS ALCATEL SIDE FROM TRAFFIC HAS TO COME.
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 10.10.17.1, timeout is 2 seconds:
    Success rate is 100 percent (5/5), round-trip min/avg/max = 3/3/4 ms
    SDH_FR#
    SDH_FR#
    SDH_FR#sh frame-relay traffic
    Frame Relay statistics:
            ARP requests sent 0, ARP replies sent 0
            ARP request recvd 0, ARP replies recvd 0
    SDH_FR#

    What is the access rate of the head end?
    Are you using a codec other than G711?
    How many total sites are involved, what protocols are you running?
    From the math, 32K is not enough CIR to ensure 4 calls proper Bandwidth. At what point is the voice degrading, is is choppy missing message, sound, jitter, echo or after 1, 2 or 3 calls.
    Even if you are using G729a, voice packets could be dropped. Not to say that it is here, but look at the FRS stats to see ip packets are being dropped.
    Traffic shaping is always recommended, rtp header compression will help, but the trade-off is around a 20% CPU hit.
    If you implement traffic shapping , it needs to be done throughout the network as queueing delays related to data on other slow links and at the headend (specifically here) could be the cause of the distortion alone. I would at least try traffic shapping first, then if the problem doen't go away, increase CIR for Voice, if there are still issues, implement LLQ.

  • Show Interfaces Output Errors / CRC (Frame Relay)

    Hi All,
    Looking at an Output of a show interfaces command there seems to be a high volume of Input errors - and they almost tally up with CRC on the line below. The line is heavily saturated - would this be the cause? Or could the CRC be causing an issue? It is a frame relay link (512K)
    Serial0/1/0 is up, line protocol is up
      Hardware is GT96K Serial
      MTU 1500 bytes, BW 512 Kbit/sec, DLY 20000 usec,
         reliability 255/255, txload 31/255, rxload 250/255
      Encapsulation FRAME-RELAY, loopback not set
      Keepalive set (10 sec)
      Restart-Delay is 0 secs
      LMI enq sent  110367, LMI stat recvd 110110, LMI upd recvd 0, DTE LMI up
      LMI enq recvd 0, LMI stat sent  0, LMI upd sent  0
      LMI DLCI 1023  LMI type is CISCO  frame relay DTE
      FR SVC disabled, LAPF state down
      Broadcast queue 0/64, broadcasts sent/dropped 18837/3, interface broadcasts 0
      Last input 00:00:00, output 00:00:00, output hang never
      Last clearing of "show interface" counters 1w5d
      Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 7976
      Queueing strategy: weighted fair
      Output queue: 0/1000/64/0 (size/max total/threshold/drops)
         Conversations  0/8/256 (active/max active/max total)
         Reserved Conversations 0/0 (allocated/max allocated)
         Available Bandwidth 384 kilobits/sec
      30 second input rate 502000 bits/sec, 62 packets/sec
      30 second output rate 64000 bits/sec, 64 packets/sec
         74014842 packets input, 2195212513 bytes, 0 no buffer
         Received 0 broadcasts, 0 runts, 101 giants, 0 throttles
         12589993 input errors, 12589924 CRC, 2758329 frame, 246617 overrun, 0 ignored, 3630022 abort
         69361072 packets output, 1961236740 bytes, 0 underruns
         0 output errors, 0 collisions, 0 interface resets
         0 output buffer failures, 0 output buffers swapped out
         108498 carrier transitions
         DCD=up  DSR=up  DTR=up  RTS=up  CTS=up

    Get the ISP to run a 4-hour Bit Error Rate test (aka BER test).

  • Troubleshooting Frame relay

    Dear Sir/Madam,
    I have Frame relay CIR 256 kps with configure as follow:
    factory#show run
    Building configuration...
    Current configuration : 2126 bytes
    version 12.2
    service timestamps debug uptime
    service timestamps log uptime
    no service password-encryption
    hostname factory
    enable secret xxx
    enable password xxx
    ip subnet-zero
    interface FastEthernet0/0
    ip address 192.168.0.1 255.255.254.0
    ip access-group 100 in
    duplex auto
    speed auto
    interface Serial0/0
    bandwidth 256
    no ip address
    encapsulation frame-relay
    no fair-queue
    traffic-shape rate 192000 24000 24000 1000
    frame-relay lmi-type ansi
    frame-relay ip rtp header-compression
    ip rtp reserve 16384 100 192
    interface Serial0/0.1 point-to-point
    description connected to Office
    ip address 192.168.50.2 255.255.255.0
    no cdp enable
    frame-relay interface-dlci 16
    interface Serial0/1
    no ip address
    shutdown
    interface Serial0/2
    no ip address
    shutdown
    ip classless
    ip route 0.0.0.0 0.0.0.0 192.168.50.1
    ip http server
    ip pim bidir-enable
    access-list 100 permit tcp any any eq www
    access-list 100 permit tcp any any eq smtp
    access-list 100 permit tcp any any eq ftp
    access-list 100 permit tcp any any eq pop3
    access-list 100 permit tcp any any eq ident
    access-list 100 permit tcp any any eq 443
    access-list 100 permit tcp any any eq 3389
    access-list 100 permit tcp any any eq ftp-data
    access-list 100 permit tcp any any eq 143
    access-list 100 permit tcp any any eq telnet
    access-list 100 permit tcp any any eq 161
    access-list 100 permit tcp any any eq domain
    access-list 100 permit udp any any eq domain
    access-list 100 permit tcp any any eq 139
    access-list 100 permit udp any any eq netbios-ns
    access-list 100 permit tcp any any eq 135
    access-list 100 permit udp any any eq snmp
    access-list 100 permit tcp any any eq 8080
    access-list 100 permit ip host 192.168.0.22 any
    access-list 100 permit ip host 192.168.0.23 any
    access-list 100 deny ip any any
    access-list 100 deny eigrp any any
    snmp-server community public RO
    line con 0
    line aux 0
    line vty 0 4
    password xxx
    login
    end
    factory#show int s0/0
    Serial0/0 is up, line protocol is up
    Hardware is PowerQUICC Serial
    MTU 1500 bytes, BW 256 Kbit, DLY 20000 usec,
    reliability 255/255, txload 61/255, rxload 56/255
    Encapsulation FRAME-RELAY, loopback not set
    Keepalive set (10 sec)
    LMI enq sent 8861, LMI stat recvd 8861, LMI upd recvd 0, DTE LMI up
    LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
    LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE
    Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0
    Last input 00:00:00, output 00:00:00, output hang never
    Last clearing of "show interface" counters 1d00h
    Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
    Queueing strategy: fifo
    Output queue :0/40 (size/max)
    5 minute input rate 57000 bits/sec, 13 packets/sec
    5 minute output rate 62000 bits/sec, 14 packets/sec
    663283 packets input, 419498487 bytes, 0 no buffer
    Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
    16 input errors, 9 CRC, 7 frame, 0 overrun, 0 ignored, 0 abort
    820043 packets output, 138740120 bytes, 0 underruns
    0 output errors, 0 collisions, 1 interface resets
    0 output buffer failures, 0 output buffers swapped out
    0 carrier transitions
    DCD=up DSR=up DTR=up RTS=up CTS=up
    factory#
    When show int s0/0 I see that:16 input errors, 9 CRC. I think errors from service provider? because I alway use under 100 kps but still have some errors.
    Thanks very much,
    NhuongPham

    When you're able, schedule some downtime for this circuit, and have your provide do some loopback testing on an off-hours time. Simply open a trouble ticket with them, indicating that you're taking CRC errors at the customer-premisis-equipment. 16 input hours per day doesn't seem like alot, but it's still worth checking out, especially since your WAN provider should do this for free.

  • "frame-relay fragment" causes link to stop working

    Hi people!
    I have a strange problem regarding the "frame-relay fragment xyz" command. I have the following configuration:
    interface Serial0/0
    description R3926704: phy. FrameRelay-Interface (Se0/0)
    bandwidth 512
    no ip address
    max-reserved-bandwidth 95
    encapsulation frame-relay IETF
    no ip mroute-cache
    load-interval 30
    no snmp trap link-status
    no fair-queue
    cdp enable
    frame-relay traffic-shaping
    frame-relay lmi-type q933a
    end
    interface Serial0/0.1 point-to-point
    description YYY: FR-Verbindung zum YY(Se0/0.1)
    bandwidth 512
    ip address A.A.A.A B.B.B.B
    frame-relay class egress_queue_512k
    frame-relay interface-dlci 16
    end
    map-class frame-relay egress_queue_512k
    frame-relay cir 486000
    frame-relay bc 48600
    frame-relay be 0
    frame-relay mincir 486000
    service-policy output egress_queue
    ... if i change the map-class to:
    map-class frame-relay egress_queue_512k_voice
    frame-relay cir 486000
    frame-relay bc 4860
    frame-relay be 0
    frame-relay mincir 486000
    service-policy output egress_queue
    frame-relay fragment 53
    ... no traffic goes over the link any more. no telnet no other traffic. the strange thing is, that i can ping the router!??
    does anyone know what's the problem here??
    thanks for any help!!
    Mario

    Mario,
    You need to base the fragment size on the lowest speed link between the 2 routers. If the lowest speed link is 512k, the recommended fragment size is 640 bytes.This is to achieve a 10ms serialization delay. The formula to compute this is Max Delay X Bandwidth. Please see Table 5 in the following link for recommended fragment sizes for 10ms serialization delay for different speed links.
    frame-relay fragment command
    http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/products_command_reference_chapter09186a008017cf52.html#wp1034268
    Hope this helps. If so, please rate the post.
    Brandon

  • Sub internface shutdown in Frame Relay point to point in GNS3

    Hello
    Please take a look on GNS3 file in attached, I'm sure already configured both routers s1/0 is no shut, but still status down, please help.

    R3:
    R3#show run
    Building configuration...
    Current configuration : 1261 bytes
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    no service password-encryption
    hostname R3
    boot-start-marker
    boot-end-marker
    no aaa new-model
    no ip icmp rate-limit unreachable
    ip cef
    no ip domain lookup
    frame-relay switching
    ip tcp synwait-time 5
    interface FastEthernet0/0
    no ip address
    shutdown
    duplex auto
    speed auto
    interface FastEthernet0/1
    no ip address
    shutdown
    duplex auto
    speed auto
    interface Serial1/0
    no ip address
    encapsulation frame-relay
    serial restart-delay 0
    no fair-queue
    frame-relay intf-type nni
    interface Serial1/0.1 point-to-point
    ip address 192.168.0.1 255.255.255.0
    frame-relay interface-dlci 241
    interface Serial1/1
    no ip address
    shutdown
    serial restart-delay 0
    interface Serial1/2
    no ip address
    shutdown
    serial restart-delay 0
    interface Serial1/3
    no ip address
    shutdown
    serial restart-delay 0
    no ip http server
    no ip http secure-server
    control-plane
    gatekeeper
    shutdown
    line con 0
    exec-timeout 0 0
    privilege level 15
    logging synchronous
    stopbits 1
    line aux 0
    exec-timeout 0 0
    privilege level 15
    logging synchronous
    stopbits 1
    line vty 0 4
    login
    end
    R3#show ip int brief
    Interface                  IP-Address      OK? Method Status                Protocol
    FastEthernet0/0            unassigned      YES NVRAM  administratively down down
    FastEthernet0/1            unassigned      YES NVRAM  administratively down down
    Serial1/0                  unassigned      YES NVRAM  up                    down
    Serial1/0.1                192.168.0.1     YES NVRAM  down                  down
    Serial1/1                  unassigned      YES NVRAM  administratively down down
    Serial1/2                  unassigned      YES NVRAM  administratively down down
    Serial1/3                  unassigned      YES NVRAM  administratively down down
    R4:
    R4#sh run
    Building configuration...
    Current configuration : 1251 bytes
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    no service password-encryption
    hostname R4
    boot-start-marker
    boot-end-marker
    no aaa new-model
    no ip icmp rate-limit unreachable
    ip cef
    no ip domain lookup
    frame-relay switching
    ip tcp synwait-time 5
    interface FastEthernet0/0
    no ip address
    shutdown
    duplex auto
    speed auto
    interface FastEthernet0/1
    no ip address
    duplex auto
    speed auto
    interface Serial1/0
    no ip address
    encapsulation frame-relay
    serial restart-delay 0
    no fair-queue
    frame-relay intf-type nni
    interface Serial1/0.1 point-to-point
    ip address 192.168.0.2 255.255.255.0
    frame-relay interface-dlci 240
    interface Serial1/1
    no ip address
    shutdown
    serial restart-delay 0
    interface Serial1/2
    no ip address
    shutdown
    serial restart-delay 0
    interface Serial1/3
    no ip address
    shutdown
    serial restart-delay 0
    no ip http server
    no ip http secure-server
    control-plane
    gatekeeper
    shutdown
    line con 0
    exec-timeout 0 0
    privilege level 15
    logging synchronous
    stopbits 1
    line aux 0
    exec-timeout 0 0
    privilege level 15
    logging synchronous
    stopbits 1
    line vty 0 4
    login
    end
    R4#sh ip int br
    Interface                  IP-Address      OK? Method Status                Protocol
    FastEthernet0/0            unassigned      YES NVRAM  administratively down down
    FastEthernet0/1            unassigned      YES NVRAM  up                    up
    Serial1/0                  unassigned      YES NVRAM  up                    down
    Serial1/0.1                192.168.0.2     YES NVRAM  down                  down
    Serial1/1                  unassigned      YES NVRAM  administratively down down
    Serial1/2                  unassigned      YES NVRAM  administratively down down
    Serial1/3                  unassigned      YES NVRAM  administratively down down

  • Frame relay switch

    can anyone tell me how to set up a frame relay switch on my 1700 roouter with 2 serial connections, I want this to act like my isp. I believe this can be done, it is for testing in my home lab
    thanks
    Carlos

    Hi Carl,
    Yes you can cofigure router as a frame relay switch.
    Check this link
    http://www.cisco.com/warp/public/125/fr_switching.pdf
    Just check the config for router Americas in that link and you will get to know how to switch the dlci.
    To get a complete know how about Frame Relay have a look at this link
    http://www.cisco.com/en/US/tech/tk713/tk237/tech_configuration_examples_list.html
    HTH, if yes please rate the post.
    Ankur

  • Video teleconferencing over frame-relay

    I have a user who requires using a polycom video teleconferencing unit at one of my sites that has a t-1 frame-relay circuit. The video is extremly choppy and sometimes completly freezes. I was wondering if there was any particular qos for frame-relay. I have no qOS at the moment. I have found some sample configs for atm and would like to see one for frame-relay. If you have any suggestions any help would be appreciated.

    QoS for video over frame relay can be difficult to achieve, although Cisco provides lots of tools to do the best you can. Typically you will want to keep the video traffic within the CIR of the frame circuit. This can be done through setting the TOS bits at the Polycom unit (or through the proxy feature on the Cisco MCM) and then using CBWFQ or other prioritization schemes with the ability to set the bandwidth.
    The difficult part comes in that frame-relay is a layer 2 technology and once the traffic goes into the frame-relay network, there is no prioritization of your traffic versus other customers' traffic at each FR switch. CIR will guarantee bandwidth but not necessarily delay constancy which is as important for live video.
    Some other considerations might include codec selection - H.264 gives good quality at lower bitrates if your Polycom unit supports it.
    Hope this helps,
    John

  • ISDN and FRAME-RELAY

    Hi All,
    I currently have two 2500 routers, to get my hands dirty on ISDN and FRAME-RELAY experiments do i need seperate routers for them?. Because i cannot see where to connect to in regards to the required connections i.e.
    2 x Asynchronous/Synchronous Serial Interfaces (DB60)
    4 x Serial Interfaces (DB60)
    1 x ISDN Interface (RJ45)
    1 x Token Ring interface (DB9 and RJ45)
    THat i normally hear about when refering to ISDN or FRAME RELAY.
    Somebody please put me through.
    Secondly i would like to connect my 2500 to the internet ...please put me through how.
    Many thanks in Advance

    Olu
    There are some challenges in what you want to do with this equipment. If each router has 1 x ISDN interface then you can use that for ISDN - but you will need some other piece of equipment to furnish the ISDN switch functionality. You can not just connect 2 ISDN interfaces back to back.
    You would be able to do some testing of Frame Relay if you connected the routers back to back - if one of the cables is a DCE cable and one cable is a DTE cable. The testing that you can do with 2 routers back to back is somewhat limited. You could do much better testing if you had a third router which could be configured as a frame relay switch.
    Connecting your routers to the Internet will be possible if you connect one of the serial interfaces to an Internet Service provider.
    The routers have token ring LAN interfaces. Unless you have some token ring MAUs to establish the connections you will not be able to do effective testing using the token ring LAN interfaces.
    HTH
    Rick

  • Can't ping routers across point-to-point frame-relay

    'evening,
      Really basic setup.  Designed with Packet Tracer, trying to ping routers across a point-to-point frame-relay.  I've designed this according to three different training sources who all say the same thing.  Yet, all pings failed.
    The shows:
    R1
    R1#copy run st
    Destination filename [startup-config]? 
    Building configuration...
    [OK]
    R1#show run
    Building configuration...
    Current configuration : 883 bytes
    version 12.2
    no service timestamps log datetime msec
    no service timestamps debug datetime msec
    no service password-encryption
    hostname R1
    no ip domain-lookup
    interface FastEthernet0/0
     no ip address
     duplex auto
     speed auto
     shutdown
    interface FastEthernet0/1
     no ip address
     duplex auto
     speed auto
     shutdown
    interface Serial1/0
     no ip address
     encapsulation frame-relay
    interface Serial1/0.12 point-to-point
     ip address 192.168.12.1 255.255.255.0
     frame-relay interface-dlci 102
    interface Serial1/0.13 point-to-point
     ip address 192.168.13.1 255.255.255.0
     frame-relay interface-dlci 103
    ip classless
    end
    R1#show frame-relay lmi
    LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 638       Num Status msgs Rcvd 638
     Num Update Status Rcvd 0       Num Status Timeouts 16
    LMI Statistics for interface Serial1/0.12 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 0         Num Status msgs Rcvd 0
     Num Update Status Rcvd 0       Num Status Timeouts 16
    LMI Statistics for interface Serial1/0.13 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 0         Num Status msgs Rcvd 0
     Num Update Status Rcvd 0       Num Status Timeouts 16
    R1#show frame-relay map
    Serial1/0.12 (up): point-to-point dlci, dlci 102, broadcast, status defined, active
    Serial1/0.13 (up): point-to-point dlci, dlci 103, broadcast, status defined, active
    R1#show frame-relay pvc
    PVC Statistics for interface Serial1/0 (Frame Relay DCE)
    DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.12
    input pkts 14055       output pkts 32795        in bytes 1096228
    out bytes 6216155      dropped pkts 0           in FECN pkts 0
    in BECN pkts 0         out FECN pkts 0          out BECN pkts 0
    in DE pkts 0           out DE pkts 0
    out bcast pkts 32795   out bcast bytes 6216155
    DLCI = 103, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.13
    input pkts 14055       output pkts 32795        in bytes 1096228
    out bytes 6216155      dropped pkts 0           in FECN pkts 0
    in BECN pkts 0         out FECN pkts 0          out BECN pkts 0
    in DE pkts 0           out DE pkts 0
    out bcast pkts 32795   out bcast bytes 6216155
    R2
    R2#SHOW RUN
    Building configuration...
    Current configuration : 772 bytes
    version 12.2
    no service timestamps log datetime msec
    no service timestamps debug datetime msec
    no service password-encryption
    hostname R2
    no ip domain-lookup
    interface Serial1/0
     no ip address
     encapsulation frame-relay
    interface Serial1/0.12 point-to-point
     ip address 192.168.12.2 255.255.255.0
     frame-relay interface-dlci 201
    ip classless
    end
    R2#show fr map
    Serial1/0.12 (up): point-to-point dlci, dlci 201, broadcast, status defined, active
    R2#show fr pvc
    PVC Statistics for interface Serial1/0 (Frame Relay DTE)
    DLCI = 201, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.12
    input pkts 14055       output pkts 32795        in bytes 1096228
    out bytes 6216155      dropped pkts 0           in FECN pkts 0
    in BECN pkts 0         out FECN pkts 0          out BECN pkts 0
    in DE pkts 0           out DE pkts 0
    out bcast pkts 32795   out bcast bytes 6216155
    R2#show fr lmi
    LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 679       Num Status msgs Rcvd 678
     Num Update Status Rcvd 0       Num Status Timeouts 16
    LMI Statistics for interface Serial1/0.12 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 0         Num Status msgs Rcvd 0
     Num Update Status Rcvd 0       Num Status Timeouts 16
    R3
    R3#show run
    Building configuration...
    Current configuration : 772 bytes
    version 12.2
    no service timestamps log datetime msec
    no service timestamps debug datetime msec
    no service password-encryption
    hostname R3
    interface Serial1/0
     no ip address
     encapsulation frame-relay
    interface Serial1/0.13 point-to-point
     ip address 192.168.13.2 255.255.255.0
     frame-relay interface-dlci 301
    ip classless
    end
    R3#show fr map
    Serial1/0.13 (up): point-to-point dlci, dlci 301, broadcast, status defined, active
    R3#show fr lmi
    LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 703       Num Status msgs Rcvd 702
     Num Update Status Rcvd 0       Num Status Timeouts 16
    LMI Statistics for interface Serial1/0.13 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 0         Num Status msgs Rcvd 0
     Num Update Status Rcvd 0       Num Status Timeouts 16
    R3#show fr pvc
    PVC Statistics for interface Serial1/0 (Frame Relay DTE)
    DLCI = 301, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.13
    input pkts 14055       output pkts 32795        in bytes 1096228
    out bytes 6216155      dropped pkts 0           in FECN pkts 0
    in BECN pkts 0         out FECN pkts 0          out BECN pkts 0
    in DE pkts 0           out DE pkts 0
    out bcast pkts 32795   out bcast bytes 6216155
      Any input would really be appreciated.
    Thanks

    Turns out the mistake was not adding a mask to the subnet. Ex:
    Router_2(config_router)# network 192.168.0.0 0.0.255.255
    Router_2(config_router)# network 172.27.0.0 0.0.255.255
    Doing that on both routers made the hosts capable of pinging each other.
    Thanks for the tips everyone 

  • Connection from remote sites (Frame Relay WAN) to AS/400 dissapears

    Hello,
    We have the following problem appearing in our environment:
    All connections from remote sites dissapears unexpected from AS/400. After 2-3 minutes remote users get normal connectivity again.
    The environment is the the following:
    Frame Relay/ATM WAN (Frame Relay on remote sites and ATM in datacenter) comes to Cisco 7204VXR router which connected to LAN switch with 10/100/1000 ports. AS/400 with Fast Ethernet interface also connected to the similar LAN switch. CEF is enabled on the router, IOS version 12.4.3a. We have ETHSTD *ALL parameter set on AS/400. Remote users uses TCP/IP and Telnet but there are a number of 5494 controllers wich uses SNA.
    We got the problem for the first time after we enabled CEF on the router.
    I suspect that the cause of problem is Ethernet frames of different standards due to ETHSTD *ALL, but can neither reproduce the problem nor understand why it behaves so.
    Have anybody had similar problem?
    I would be very thanksfull if somebody can help me to solve it.
    Thank you in advance.
    //Mikhail Galiulin

    Hi Martin,
    Cisco 7200 itself can access AS/400 as well as all other hosts in the same with AS/400 LAN. There is no any outage in communications which goes to another LAN segment via Netscreen firewall while the communication via Cisco is down. Only those hosts which connected via Cisco are experiencing the problem. I can not say where the traceroute from AS/400 stucks (there are other people who maintain the machine and they never could catch the exact moment of outage).
    To turn off CEF I treat as the last option actually and unfortunatelly there is no guarantee that software upgrade will help (we have 12.4.3a now).
    So first of all I'm trying to understan WHY it happens because I can not see any systematics in the problem appearance. It can happen 3 times under 2 days and then dissapear for 1-2 months...
    //Mikhail Galiulin

  • Configuring Frame-Relay and the Frame-Relay Switch To Participate in WAN Routing

    Hey,
    My WAN in my voice lab is currently functional between all of my routers HQ, BR1, and BR1 with full-mesh connectivity.  I am using my PSTN router for the frame-relay switching as is shown in the attached configs.  I have used the connect commands for the PVC routing logic.  
    connect HQ-BR1 Serial0/3/0 101 Serial0/2/0 201 
    connect HQ-BR2 Serial0/3/0 102 Serial0/2/1 301 
    connect BR1-BR2 Serial0/2/0 202 Serial0/2/1 302 
    My question concerns the possibility of getting the PSTN router to participate in the WAN and the OSPF routing process?  The connect command tells how the PVCs are to be connected and pass through the PSTN router.  Is there anyway to do it so that a PVC connects to the PSTN router itself?
    I would specifically like to create a connection between the HQ and PSTN router over the WAN.  If anyone has any insight on this I would really appreciate it.
    Thank you.

    Hello Adam,
    you don't need to do FR switching.
    You just need to configure a back to back PVC associated to a p2p subinterface under PSTN router interface se0/3/0 and HQ:se0/1/0. the new PVC can be 103 on both sides
    PSTN
    interface ser0/3/0.103 point-to-point
    ip address 10.1.13.1 255.255.255.0
    frame-relay interface-dlci 103
    HQ
    interface ser0/1/0.103 point-to-point
    ip address 10.1.13.1 255.255.255.0
    frame-relay interface-dlci 103
    note: I was able to do this using the older syntax frame-relay route under interface configuration on frame relay switch. I would expect to work for you too with newer syntax connect.
    Hope to help
    Giuseppe

  • 2621 as a Frame Relay switch & terminal server?

    Is it unwise to use a 2621 as a combined Frame Relay switch & terminal server in a home lab? Both functions seem to move a general-purpose router into the dedicated use category.
    Likewise, is it true than configuring a router to serve as a Frame Relay switch isn't memory intensive?
    If I am wrong in my assumptions, please feel free to correct my misperceptions.
    Thanks.

    Using the 2621 for frame and TS should be fine. I do it in my lab and have never had a problem.

  • Frame Relay Configuration

    All,
    Sorry for asking this, but I have been beating my head against the wall here. I am getting a T1 installed in my residence for internet connectivity. I am using an old wic-1-dsu-t1-v1 in a 2610 router. I am unable to get this configuration working. I have a very simple configuration so far on the router, but I am unable to get this to come up. I have put the show run below. Some of the commands are default and are not showing up. Obviously I have changed the ip's to generic ones below. Any ideas?
    version 12.1
    no service single-slot-reload-enable
    service timestamps debug uptime
    service timestamps log uptime
    no service password-encryption
    hostname JSS-2610-001
    memory-size iomem 10
    ip subnet-zero
    interface Ethernet0/0
     no ip address
     shutdown
    interface Serial0/0
     no ip address
     shutdown
    interface Serial0/1
     no ip address
     shutdown
    interface Serial0/2
     no ip address
     encapsulation frame-relay IETF
     frame-relay lmi-type ansi
    interface Serial0/2.21 point-to-point
     ip address 1.1.1.3 255.255.255.252
     frame-relay interface-dlci 16   
    ip classless
    ip route 0.0.0.0 0.0.0.0 1.1.1.2
    ip http server
    line con 0
     speed 115200
    line aux 0
    line vty 0 4

    Sorry when I transposed the ip's to post i made a mistake in them. 1.1.1.2 is my address and 1.1.1.1 is the gateway for them (their side of the t1). I have it configure correctly on my router with the real ip's.
    Here is the post to the rest of your questions:
    Serial0/2 is up, line protocol is up 
      Hardware is PQUICC with Fractional T1 CSU/DSU
      MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, 
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation FRAME-RELAY IETF, loopback not set
      Keepalive set (10 sec)
      LMI enq sent  16787, LMI stat recvd 16788, LMI upd recvd 0, DTE LMI up
      LMI enq recvd 0, LMI stat sent  0, LMI upd sent  0
      LMI DLCI 0  LMI type is ANSI Annex D  frame relay DTE
      FR SVC disabled, LAPF state down
      Broadcast queue 0/64, broadcasts sent/dropped 2812/0, interface broadcasts 15
      Last input 00:00:04, output 00:00:04, output hang never
      Last clearing of "show interface" counters 1d22h
      Input queue: 0/75/3/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: weighted fair
      Output queue: 0/1000/64/0 (size/max total/threshold/drops) 
         Conversations  0/1/256 (active/max active/max total)
         Reserved Conversations 0/0 (allocated/max allocated)
      5 minute input rate 0 bits/sec, 0 packets/sec
      5 minute output rate 0 bits/sec, 0 packets/sec
         16791 packets input, 249054 bytes, 0 no buffer
         Received 0 broadcasts, 0 runts, 1 giants, 0 throttles
         3350 input errors, 1097 CRC, 1758 frame, 0 overrun, 0 ignored, 495 abort
         19638 packets output, 1080335 bytes, 0 underruns
         0 output errors, 0 collisions, 2 interface resets
         0 output buffer failures, 0 output buffers swapped out
         6 carrier transitions
         DCD=up  DSR=up  DTR=up  RTS=up  CTS=up
    JSS-2610-001#show frame-relay pvc 
    PVC Statistics for interface Serial0/2 (Frame Relay DTE)
                  Active     Inactive      Deleted       Static
      Local          1            0            0            0
      Switched       0            0            0            0
      Unused         0            0            0            0
    DLCI = 16, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/2.21
      input pkts 0             output pkts 2834         in bytes 0         
      out bytes 844139         dropped pkts 0           in FECN pkts 0         
      in BECN pkts 0           out FECN pkts 0          out BECN pkts 0         
      in DE pkts 0             out DE pkts 0         
      out bcast pkts 2809       out bcast bytes 841611    
      pvc create time 1d22h, last time pvc status changed 15:31:28
    Is it possible the carrier just hasn't "activated" the circuit?

Maybe you are looking for