Frame Relay question

havenladhavenlad Member Posts: 27 ■□□□□□□□□□
If looking at the output from a "#show interface" command, what would indicate you are looking at Frame Relay as opposed to any other WAN protocol?

Comments

  • TurK-FXTurK-FX Member Posts: 174
    Encapsulation Frame-Relay line indicates that it is frame relay
    WGU classes: Transferred -> AGC1, CLC1, TBP1, CJC1, BVC1, C278, CRV1, IWC1, IWT1, C246, C247, C132, C164, INC1, C277. Appealed -> WFV1 and C393.
    What is Left to take - > EUP1, EUC1, C220, C221, BNC1, GC1, C299, CTV1, DJV1, DHV1, CUV1, CJV1, TPV1, C394
    Currently Studying -> CCNA security (Designing Customized Security & Security)
  • havenladhavenlad Member Posts: 27 ■□□□□□□□□□
    There's no encapsulation line on the screen. I think they took it out so make us think outside the box so to speak
  • TheNewITGuyTheNewITGuy Member Posts: 169 ■■■■□□□□□□
    You can also show a show frame-relay pvc and it'll show you the interface(s)


    Router#



    show frame pvc


    PVC Statistics for interface Serial0/0/0 (Frame Relay DTE)


    Active Inactive Deleted Static
    Local 1 0 0 0
    Switched 0 0 0 0
    Unused 3 0 0 0



    example:


    Router#show interface serial1/2
    Serial1/2 is up, line protocol is up
    Hardware is CD2430 in sync mode
    Internet address is 172.16.1.1/24
    MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,
    reliability 255/255, txload 1/255, rxload 1/255
    Encapsulation FRAME-RELAY, loopback not set <-- here
    Keepalive set (10 sec)
    LMI enq sent 131, LMI stat recvd 116, LMI upd recvd 0, DTE LMI up <-- LMI reference
    LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
    LMI DLCI 1023 LMI type is CISCO frame relay DTE <-- DLCI reference
    FR SVC disabled, LAPF state down <-- FR SVC
    Broadcast queue 0/64, broadcasts sent/dropped 9/0, interface broadcasts 0
    Last input 00:00:03, output 00:00:03, output hang never
    Last clearing of "show interface" counters 00:24:10
    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 0 bits/sec, 0 packets/sec
    5 minute output rate 0 bits/sec, 0 packets/sec
    241 packets input, 8933 bytes, 0 no buffer
    Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
    164 packets output, 2865 bytes, 0 underruns
    0 output errors, 0 collisions, 10 interface resets
    0 output buffer failures, 0 output buffers swapped out
    2 carrier transitions
    DCD=up DSR=up DTR=up RTS=up CTS=up
  • rscrtrscrt Member Posts: 62 ■■□□□□□□□□
    LMI statistics could be the hint?
  • havenladhavenlad Member Posts: 27 ■□□□□□□□□□
    That's it.....was going to put a whole page of junk that would've taken ages but you've saved me the hassle. Thanks. There's an LMI status message...just looking this up now and it seems Jeremy has missed a lot out if it goes into the depth Chris Bryant seems to suggest regarding frame relay on the ICND1

    Thanks for the input
  • d6bmgd6bmg Member Posts: 241
    havenlad wrote: »
    If looking at the output from a "#show interface" command, what would indicate you are looking at Frame Relay as opposed to any other WAN protocol?

    Use the global command:
    show interface serial 1/0 (or the corresponding interface you are applying frame relay on).

    In the output:
    Serial1/0 is up, line protocol is up
      Hardware is M4T
      Internet address is 192.168.15.1/24
      MTU 1500 bytes, BW 1544 Kbit/sec, DLY 20000 usec,
         reliability 255/255, txload 1/255, rxload 1/255
     [B] Encapsulation FRAME-RELAY[/B], crc 16, loopback not set
      Keepalive set (10 sec)
      Restart-Delay is 0 secs
    
    [ ]CCDA; [ ] CCNA Security
Sign In or Register to comment.