Frame Relay Signal Flow

Hi to all the experts here, I am learning the Frame Relay basic theoretically. Just wanna know, packets are assembled at router, transmit through indicated PVC. At the FRP, does the individual packets re-assembled again to meet IPX packet? What does IPX packet relates with the previous frame? Thanks ..

Packets are layer three. Frame Relay is Layer Two (like Ethernet) and so they use Frames.
Routers to not assemble or reassemble anything, they remove the packet from the frame at the ingress (incoming) interface, make decisions based on what it sees in the header of the packet, then (assuming all is correct) it puts the packet into a new frame and sends it out the appropriate egress (exit) interface.
Frames (even frame relay frames) are Layer Two, they deliver packets (Layer Three) that will be used to reconstruct segments (Layer Four) and the segments are passed up the stack, possibly interpreted or manipulated by the other layers as it passes through, to ultimately be delivered through the calling process of the application.
The Frames are switched, the packets are routed, because there is no "network" information in a Frame; "network" information is determined from the (in this case) IP (or IPX) address and mask in the packet.
The Frame Relay devices in the "cloud" have settings (look-up tables) that pass the frame relay frame from ingress PVC to egress PVC from the originating end to the destination end of the network.
Good Luck
Scott

Similar Messages

  • 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.

  • Map-class frame-relay , policy map

    Does a service-policy output have to be applied to an interface for qos to work?
    here is the config but there is nothing applied to the serial interface..
    Thanks for your help
    policy-map 256/128KVoice
    class 256/128KVoice
    priority 112
    class class-default
    fair-queue
    map-class frame-relay 256/128KVoice
    frame-relay cir 128000
    frame-relay bc 1280
    frame-relay be 600
    frame-relay mincir 128000
    no frame-relay adaptive-shaping
    frame-relay fair-queue
    frame-relay fragment 150
    frame-relay ip rtp priority 16384 16380 210
    interface Serial0/0
    bandwidth 1544
    ip address xxx.xxx.xxx.xxx 255.255.255.255
    ip route-cache flow
    no fair-queue
    service-module t1 timeslots 1-24

    Hello,
    Will QOS will work in this way  where class is put on WAN interface where it should be service  policy.
    router#sh run interface Se0/0/0.1
    Building  configuration...
    Current configuration : 239 bytes
    interface  Serial0/0/0.1 point-to-point
    bandwidth 2048
    ip address XXXX
    ip nat outside
    frame-relay  interface-dlci 555
      class COS-OUT-S0/0/0.1   
    end
    COS-OUT-S0/0/0.1 is defined as policy map  with class of voice and video.
    When checking on WAN int #sh policy-map  interface  Se0/0/0.1 , can see output of service policy input/output with policy map  recpective classes and packets match entries.Is  QOS working with this  configuration?
    Appreciate any input on this.
    Regards,
    Brajesh.

  • No modem conection with voip over frame-relay

    I'm trying to connect two modems through voip over frame-relay network using the modem passthrough command but that is no working. The voice calls is operating very well but the modems no connect between them. I'm using G-729 codec with ip header compression and data fragment in 80 bytes.

    There are some know issues with cisco dsps and V.90+ modems, but we have been able to get most modems to work correctly accross our network. If you are using g729 for all other voice calls you will want to use the modem passthrough command to have both gw's turn to modem passthrough. I typically set up each dial peer with the specific commands, since I have found the global commands are not consistently applied. Here is a sample dial peer config....
    dial-peer voice 3 voip
    description Default voip peer
    preference 1
    incoming called-number .T
    destination-pattern .T
    progress_ind setup enable 3
    progress_ind connect enable 8
    modem passthrough nse codec g711ulaw
    voice-class codec 1
    session protocol sipv2
    session target sip-server
    dtmf-relay rtp-nte
    fax rate disable
    fax protocol pass-through g711ulaw
    ip qos dscp cs3 signaling
    no vad
    Some of these commands are specific to the isdn signaling set up we have at this site. Also, we are using sip hence the sip session target. But the modem and fax passthrough commands are pretty much universal.
    Also, some of those commands are not supported until 12.2.13. You might want to think about an ios upgrade.

  • Voice over Frame-Relay

    Hi,
    Customer of me has several sites connected with leased lines. The leased lines have frame-relay encapsulation (frame-relay back-to-back)
    The line has two pvc's configured, one for voice and one for data. The voice PVC works fine. On the data pvc we want to put some QoS.
    Here is the partial configuration:
    interface Serial0
    bandwidth 2000
    no ip address
    encapsulation frame-relay
    no ip route-cache cef
    ip route-cache flow
    no ip mroute-cache
    frame-relay intf-type dce
    interface Serial0.1 point-to-point
    ip address 10.xx.xx.1 255.255.255.252
    no ip mroute-cache
    frame-relay interface-dlci 120
    interface Serial0.2 point-to-point
    ip address 10.0.0.1 255.255.255.252
    no ip mroute-cache
    frame-relay interface-dlci 100
    class VOICE
    vofr cisco
    map-class frame-relay VOICE
    frame-relay cir 512000
    frame-relay voice bandwidth 256000
    frame-relay fragment 320
    frame-relay fair-queue
    Question is can I just apply a service policy out to the data DLCI or doi i also have to enable frame-relay traffic shaping?
    Thanks,
    JH

    The disadvantage of shaping is that it will actually limit you bandwidth. That is, you won't be able to use the circuit at full capacity, because of the artificial limitation induced by shaping. This is particularly true for a situation like you where the actual circuits is a leased line, and not a FR network.
    A better approach would be to reconfigure for simple hdlc encap, and run VoIP instead. This way, you would have all the QOS features you need for voice and data, and be able to use the full capacity with a much simpler configuration.
    Actually, even if you want to retain the FR encapsulation and the voice over FR approach, still using a single PVC would be better, for the same reasons given above.
    Hope this helps, please rate post if it does!

  • Frame Relay Setup

    Greetings!
    I'm attempting to set up a Frame Relay (FR) lab with a few routers, and I'm running into some trouble.  The router I'm using as the FR switch is a 3825, which has two VWIC2-2MFT-T1/E1 cards installed.  The three other routers are 1841s with WIC-1DSU-T1 cards.  
    I'm getting the following message, when trying to apply clocking to the FR controllers: "This command applies only to DCE interfaces".  I read elsewhere that the "V" in "VWIC2" applies to Voice, and that DCE simply can't be done on them.  I'm very new to all of this, so I hope this isn't a ridiculous question: could I uninstall the VWICs from the FR router, put them on the 1841s, and then put the three WIC-1DSUs on the FR switch to make it work?  Again, I hope that's not utterly silly, and it's worth asking.  
    If I can't pull this off, may I get some suggestions?  
    Thanks, in advance! 

    Thanks very much for the breakdown, rhirani!  I made a few T1-crossover cables to connect the 1841s, so that's what's being used.  I ran "sh controller", and the FR switch gave me a ton of information:
    FR#sh controller T1
    T1 0/0/0 is down.
      Applique type is Channelized T1
      Cablelength is long 0db
      Transmitter is sending remote alarm.
      Receiver has loss of signal.
      alarm-trigger is not set
      Soaking time: 3, Clearance time: 10
      AIS State:Clear  LOS State:Clear  LOF State:Clear
      Version info Firmware: 20071011, FPGA: 13, spm_count = 0
      Framing is ESF, Line Code is B8ZS, Clock Source is Line.
      CRC Threshold is 320. Reported from firmware  is 320.
      Data in current interval (147 seconds elapsed):
         0 Line Code Violations, 0 Path Code Violations
         0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
         0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 147 Unavail Secs
      Total Data (last 67 15 minute intervals):
         0 Line Code Violations, 0 Path Code Violations,
         0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
         0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 60300 Unavail Secs
    T1 0/0/1 is up.
      Applique type is Channelized T1
      Cablelength is long 0db
      No alarms detected.
      alarm-trigger is not set
      Soaking time: 3, Clearance time: 10
      AIS State:Clear  LOS State:Clear  LOF State:Clear
      Version info Firmware: 20071011, FPGA: 13, spm_count = 0
      Framing is ESF, Line Code is B8ZS, Clock Source is Line.
      CRC Threshold is 320. Reported from firmware  is 320.
      Data in current interval (149 seconds elapsed):
         0 Line Code Violations, 0 Path Code Violations
         0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
         0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
      Total Data (last 67 15 minute intervals):
         0 Line Code Violations, 0 Path Code Violations,
         2 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
         2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 10 Unavail Secs
    T1 0/1/0 is up.
      Applique type is Channelized T1
      Cablelength is long 0db
      No alarms detected.
      alarm-trigger is not set
      Soaking time: 3, Clearance time: 10
      AIS State:Clear  LOS State:Clear  LOF State:Clear
      Version info Firmware: 20071011, FPGA: 13, spm_count = 0
      Framing is ESF, Line Code is B8ZS, Clock Source is Line.
      CRC Threshold is 320. Reported from firmware  is 320.
      Data in current interval (146 seconds elapsed):
         0 Line Code Violations, 0 Path Code Violations
         0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
         0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
      Total Data (last 67 15 minute intervals):
         0 Line Code Violations, 0 Path Code Violations,
         2 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
         2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 11 Unavail Secs
    T1 0/1/1 is up.
      Applique type is Channelized T1
      Cablelength is long 0db
      No alarms detected.
      alarm-trigger is not set
      Soaking time: 3, Clearance time: 10
      AIS State:Clear  LOS State:Clear  LOF State:Clear
      Version info Firmware: 20071011, FPGA: 13, spm_count = 0
      Framing is ESF, Line Code is B8ZS, Clock Source is Line.
      CRC Threshold is 320. Reported from firmware  is 320.
      Data in current interval (148 seconds elapsed):
         0 Line Code Violations, 0 Path Code Violations
         2 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
         2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
      Total Data (last 67 15 minute intervals):
         0 Line Code Violations, 0 Path Code Violations,
         607 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
         607 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 11 Unavail Secs
    I also ran a show-controller for one of the serial interfaces, in case it's at all relevant, here:
    FR#sh controller ser0/0/1:0
    Interface Serial0/0/1:0
    Hardware is GT96Kidb at 0x706FF898, driver data structure at 0x70700424
    wic_info 0x0
    There was a *lot* more that printed out for the serial interface, but I didn't paste all of it.  
    I hope this is enough to tell.....

  • 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.

  • 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 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?

  • Frame Relay point to point

    Hi All,
    I have configured below point to point link with FR switch in GNS 3.
    below is the configuration for the senario.
    R1#sh run int serial 0/0
    Building configuration...
    Current configuration : 144 bytes
    interface Serial0/0
    no ip address
    encapsulation frame-relay
    clock rate 2000000
    no frame-relay inverse-arp
    frame-relay lmi-type ansi
    end
    R1#sh run int serial 0/0.101
    Building configuration...
    Current configuration : 118 bytes
    interface Serial0/0.101 point-to-point
    ip address 10.1.1.1 255.255.255.252
    frame-relay interface-dlci 101
    end
    ==============================
    R2#sh run int serial 0/0
    Building configuration...
    Current configuration : 144 bytes
    interface Serial0/0
    no ip address
    encapsulation frame-relay
    clock rate 2000000
    no frame-relay inverse-arp
    frame-relay lmi-type ansi
    end
    R2#sh run int serial 0/0.201
    Building configuration...
    Current configuration : 118 bytes
    interface Serial0/0.201 point-to-point
    ip address 10.1.1.2 255.255.255.252
    frame-relay interface-dlci 201
    end
    ======================
    FR switch is port 1-101 for R1 serial 0/0 & Port 2-201 for R2 serial 0/0
    Below is the status for the sh frame-relay map
    R1#sh frame-relay map
    Serial0/0.101 (up): point-to-point dlci, dlci 101(0x65,0x1850), broadcast status defined, active
    R2#sh frame-relay map
    Serial0/0.201 (down): point-to-point dlci, dlci 201(0xC9,0x3090), broadcast status deleted
    Serial0/1.201 (administratively down): point-to-point dlci, dlci 201(0xC9,0x3090), broadcast status deleted
    Please let me know where i am making a mistake.

    Hello
    You mentioned a FR switch, if so these routers interfaces should not be clocking - as they should be both DTE's
    Delete the config (sub interfaces and default the serial interfaces ,also shut/no shut them and re apply the config)
    res
    Paul
    Please don't forget to rate any posts that have been helpful.
    Thanks.

  • Fram Relay hub and spoke scenario

    See the attachment please
    Requirements:
    1.Using only physical interfaces configure a Frame Relay hub-and-spoke network between RTA and RTB and RTC, RTB as the hub.
    2.Traffic from RTA destined for RTC should transit RTB, and vice versa.
    3.Use only the DLCIs specified in the diagram.
    4.Do not use any Dynamic layer 3 to layer 2 mappings over these frame Relay connections.
    5.Do not send any redundant broadcast traffic from the spokes to the hub.
    RTB (Hub):
    interface Serial0/0
    ip address 3.1.1.2 255.255.255.0
    encapsulation frame-relay
    frame-relay map ip 3.1.1.1 200 broadcast
    frame-relay map ip 3.1.1.3 300 broadcast
    no frame-relay inverse-arp
    RTA (Spoke):
    interface Serial0/0
    ip address 3.1.1.1 255.255.255.0
    encapsulation frame-relay
    frame-relay map ip 3.1.1.2 22 broadcast
    frame-relay map ip 3.1.1.3 22
    no frame-relay inverse-arp
    RTC (Spoke):
    interface Serial1/0
    ip address 3.1.1.3 255.255.255.0
    encapsulation frame-relay
    frame-relay map ip 3.1.1.2 33 broadcast
    frame-relay map ip 3.1.1.1 33
    no frame-relay inverse-arp
    My queries:
    A- Does he use these two statements because (frame-relay map ip 3.1.1.3 22 and frame-relay map ip 3.1.1.1 33 ) of requirement number 2 ?
    B- Doesn’t he use keyword “broadcast” in these two statements (frame-relay map ip 3.1.1.3 22 and frame-relay map ip 3.1.1.1 33) because of requirement 5?
    C- Does that mean if requirement 5 is not there we should have used “broadcast“ keyword ?
    D- Does not that contradict with what Cisco syas: “The broadcast keyword is commonly used with the frame relay map command” ?
    E- By using these two statements (frame-relay map ip 3.1.1.3 22 and frame-relay map ip 3.1.1.1 33) doesn’t my network become full mesh? but if you look to the diagram it is partial mesh ?

    Answers to your queries:
    A. Correct
    B. Correct
    C. That depends. In most cases, it is a good idea to have broadcasts on, especially when using routing protocols like OSPF which send traffic to multicast destinations. I would habe it on most times.
    D. The recommendation from Cisco is not contradictory. The lab scenario is making you do something quite specific so you have to follow that. You don't always have to follow requirements in order to make things work.
    E. No. Full-mesh refers to a full mesh of PVCs. If there was a PVC from A to C it would be full mesh.
    Hope that helps - pls rate the post if it does.
    Paresh

  • Signal flow chart for using DIO on 5640R

    Hi,
    There are a bunch of good templates to get me started with analog I/O but not for digital I/O. My project needs the host to send out a value through digital lines @10MHz. Now I have a few  basic questions regarding the standard procedures to work with DIO?
    1. what are the essential items in the signal flow chart on host? Open session->configuration->write->initialization->close session?
    2. What are the differences of opening a session using FPGA VI Reference.vi and 5640 init Generation Session.vi? They are not interchangable.
    3. Do I have to use a FIFO to transfer data between FPGA and host in this case?
    At last, I highly recommend ni group to create a working template for DIO. If easy modification to analog I/O template can work for DIO, please show to how, that'll be great.
    Thank you.
    Dan

    Hi Dan,
    The basic flow of programming on the Host for digital output would be similar to:
    Open FPGA Reference >> Configuration (as needed) >> Write to FPGA >> Close session
    You could use a FIFO to pass data between the host and the FPGA or you could just pass data via controls and indicators.  I have included an example project which passes data from the host to a control on the FPGA VI.  If you are transferring the data as a 32-bit unsigned integer then you will need to manually format and control the way it is output from the FPGA VI.  There is not a pre-made function to do that.
    As for testing, you can manually probe the pins on a connector with a DMM.  Here is the pinout for the AUX connector.
    Regards,
    Barron
    Barron
    Applications Engineering
    National Instruments
    Attachments:
    ni5640R Digital Output Example.zip ‏282 KB

Maybe you are looking for

  • How to set up email?

    I just got finished wiping my device because it had a previous owner. And I don't know how to set my yahoo account so I can get it on my phone. I have a curve 8310. Thanks for any help.:smileyhappy: 

  • How do I install photoshop 3.0 onto windows 7 pro? Error message says it's not compatible. I'm upgrading from Windows XP.

    I have to start with my first photoshop to upgrade to my latest version, but I can't because of incompatibility issues.  Is there a way around this?  Is there something that I need to change in windows 7 pro to accept photoshop 3.0?

  • Slide Animations Stopped Working

    Hello, Last night we had a program in which we were screen sharing a Windows Media Player video. The setup I had was a Content Pod with a PowerPoint file in the front, and the Screen Share Pod behind it. In a new layout I had the reverse setup, the C

  • Date mask after import

    Hi, After export -> import from one workspace to another in the same database (different schema) the date display is not correct on most pages in the application. In the old workspace the appears as '26-OCT-2009' and on the new it is '26-OCT-0009'. T

  • Spreadsheets Locking in Numbers

    Not only am I experiencing locking whilst working on a spreadsheet (has to reboot) but the new version of numbers under IOS7 is substantially slower and the find operation that I use significantly as a Sales Representative to look up stock on hand is