Frame Relay v3.0 Problem

dentrydentry Member Posts: 42 ■■□□□□□□□□
in CCNP Collaboration
I am using all Vwic-2mft's. I have the voice t1's making calls between sites using the PSTN. I am having an issue with getting frame relay up. I have matched the configuration from configs found on the web, and done my frame relay research. I am getting green link lights on all my frame relay interfaces but showing down, down. I cannot ping the local frame relay sub interface from the local router BTW. I am using the same pinout for both my t1 rj-45's, as well as my Frame relay rj-45's as well. Below is the configuration from my PSTN, and R3 routers.

PSTN:
interface Serial0/0/0:23
description ***Voice to R1***
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn protocol-emulate network
isdn incoming-voice voice
no cdp enable
!
interface Serial0/0/1:0
description ***Data to R1***
no ip address
encapsulation frame-relay IETF
frame-relay lmi-type ansi
frame-relay intf-type dce
!
interface Serial0/1/0:23
description ***Voice to R2***
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn protocol-emulate network
isdn incoming-voice voice
no cdp enable
!
interface Serial0/1/1:0
description ***Data to R2***
no ip address
encapsulation frame-relay IETF
frame-relay lmi-type ansi
frame-relay intf-type dce
!
interface Serial0/2/0:15
description ***Voice to R3***
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn protocol-emulate network
isdn incoming-voice voice
no cdp enable
!
interface Serial0/2/1:0
description ***Data to R3***
no ip address
encapsulation frame-relay IETF
frame-relay lmi-type ansi
frame-relay intf-type dce


interface Serial0/1/1:0
description frame-relay link to R2
no ip address
encapsulation frame-relay
no fair-queue
clock rate 128000
frame-relay lmi-type cisco
frame-relay intf-type dce
frame-relay route 301 interface Serial0/0/1 103
!
interface Serial0/0/1:0
description frame-relay to R1
no ip address
encapsulation frame-relay
clock rate 128000
frame-relay lmi-type cisco
frame-relay intf-type dce
frame-relay route 102 interface Serial0/1/0 201
frame-relay route 103 interface Serial0/0/0 301
!
interface Serial0/2/1:0
description frame-relay link to R3
no ip address
encapsulation frame-relay
clock rate 128000
frame-relay lmi-type cisco
frame-relay intf-type dce
frame-relay route 201 interface Serial0/0/1 102

R3:

interface Serial0/1/0:15
description ***Voice to PSTN***
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn incoming-voice voice
no cdp enable
!
interface Serial0/1/1:0
description ***Data to PSTN***
no ip address
encapsulation frame-relay IETF
frame-relay lmi-type ansi


interface Serial0/1/1:0 201 point-to-point
description frame relay to R1
ip address 177.0.201.2 255.255.255.252
ip ospf network point-to-point
snmp trap link-status
frame-relay interface-dlci 201
· Share on FacebookShare on Twitter

Comments

  • EdTheLadEdTheLad Member Posts: 2,111 ■■■■□□□□□□
    First have to confirmed with the "show controllers" which side is the DCE and put the clock rate on the DCE side?
    Second, can you post the config of the ports in question and what is connected where. I'm not going to spend 10 minutes looking through your config trying to work out which ports you are having issues with.
    Networking, sometimes i love it, mostly i hate it.Its all about the $$$$
    · Share on FacebookShare on Twitter
  • dentrydentry Member Posts: 42 ■■□□□□□□□□
    The clock rate is on the PSTN side, it shows it in the config.
    · Share on FacebookShare on Twitter
  • EdTheLadEdTheLad Member Posts: 2,111 ■■■■□□□□□□
    It would have been nice if you distinguished between the FR interfaces, but anyway i've worked out your topology.
    Firstly from a cosmetic point of view you should switch the interfaces around because at the moment you have dlci 102 on router 3 and dlci 103 on router 2.

    1) You have lmi type cisco on your FR switch and ansi on your router interfaces, if you remove the lmi config the routers will negotiate the lmi themselves, otherwise set both identical how you like.
    2) Since all devices seem to be cisco you dont need ietf encapsulation, encapsulation frame-relay will do, but since both sides have ietf configured it wont break anything.

    If it still doesn't come up verify that the physical cables connected to the PSTN router are DCE, the clockrate goes on the DCE end, "show controllers" will tell you.
    Networking, sometimes i love it, mostly i hate it.Its all about the $$$$
    · Share on FacebookShare on Twitter
  • dentrydentry Member Posts: 42 ■■□□□□□□□□
    Thanks for the pointers Ed, I have not had a chance to get to the lab to verify anything. I should be posting tommorrow morning.
    · Share on FacebookShare on Twitter
  • dentrydentry Member Posts: 42 ■■□□□□□□□□
    hostname PSTN
    !
    !
    card type t1 0 0
    card type t1 0 1
    card type e1 0 2
    !
    !
    network-clock-participate wic 0
    network-clock-participate wic 1
    network-clock-participate wic 2
    !
    !
    !
    controller T1 0/0/0
    clock source internal
    cablelength long 0db
    pri-group timeslots 1-3,23-24
    description ***Voice to R1***
    !
    controller T1 0/0/1
    clock source internal
    cablelength long 0db
    channel-group 0 timeslots 1-24
    description ***Data to R1***
    !
    controller T1 0/1/0
    clock source internal
    cablelength long 0db
    pri-group timeslots 1-3,23-24
    description ***Voice to R2***
    !
    controller T1 0/1/1
    clock source internal
    cablelength long 0db
    channel-group 0 timeslots 1-24
    description ***Data to R2***
    !
    controller E1 0/2/0
    framing NO-CRC4
    clock source internal
    linecode ami
    pri-group timeslots 1-3,16,24
    description ***Voice to R3***
    !
    controller E1 0/2/1
    framing NO-CRC4
    linecode ami
    channel-group 0 timeslots 1-24
    description ***Data to R3***
    !
    interface Serial0/0/0:23
    description ***Voice to R1***
    no ip address
    encapsulation hdlc
    isdn switch-type primary-ni
    isdn protocol-emulate network
    isdn incoming-voice voice
    no cdp enable
    !
    interface Serial0/0/1:0
    description frame-relay to R1
    no ip address
    encapsulation frame-relay
    frame-relay lmi-type cisco
    frame-relay intf-type dce
    frame-relay route 102 interface Serial0/1/1:0 201
    frame-relay route 103 interface Serial0/2/1:0 301
    !
    interface Serial0/1/0:23
    description ***Voice to R2***
    no ip address
    encapsulation hdlc
    isdn switch-type primary-ni
    isdn protocol-emulate network
    isdn incoming-voice voice
    no cdp enable
    !
    interface Serial0/1/1:0
    description frame-relay link to R2
    no ip address
    encapsulation frame-relay
    no fair-queue
    frame-relay intf-type dce
    frame-relay route 201 interface Serial0/0/1:0 102
    !
    interface Serial0/2/0:15
    description ***Voice to R3***
    no ip address
    encapsulation hdlc
    isdn switch-type primary-net5
    isdn protocol-emulate network
    isdn incoming-voice voice
    no cdp enable
    !
    interface Serial0/2/1:0
    description frame-relay link to R3
    no ip address
    encapsulation frame-relay
    frame-relay intf-type dce
    frame-relay route 301 interface Serial0/0/1:0 103
    !
    !
    voice-port 0/0/0:23
    !
    voice-port 0/1/0:23
    !
    voice-port 0/2/0:15
    !
    !

    Here is R1 (HQ):

    hostname R1
    !
    !
    card type t1 0 3
    !
    !
    network-clock-participate wic 3
    network-clock-select 1 T1 0/3/0
    !
    !
    controller T1 0/3/0
    cablelength long 0db
    pri-group timeslots 1-3,24
    description ***Voice to PSTN
    !
    controller T1 0/3/1
    cablelength long 0db
    channel-group 0 timeslots 1-24
    description ***Data to PSTN***
    !
    interface Serial0/3/0:23
    description ***Voice to PSTN***
    no ip address
    encapsulation hdlc
    isdn switch-type primary-ni
    isdn incoming-voice voice
    no cdp enable
    !
    interface Serial0/3/1:0
    description ***Data to PSTN***
    no ip address
    encapsulation frame-relay IETF
    frame-relay lmi-type ansi
    !
    interface Serial0/3/1:0.102 point-to-point
    description frame relay link to R2
    ip address 177.0.201.1 255.255.255.252
    ip ospf network point-to-point
    frame-relay interface-dlci 102
    !
    interface Serial0/3/1:0.103 point-to-point
    description frame relay link to R3
    ip address 177.0.101.1 255.255.255.252
    ip ospf network point-to-point
    frame-relay interface-dlci 103
    !
    !
    !
    router ospf 1
    router-id 1.1.1.1
    network 177.0.0.0 0.0.255.255 area 0
    network 177.1.10.0 0.0.0.255 area 1
    network 177.1.11.0 0.0.0.255 area 1
    network 177.1.12.0 0.0.0.255 area 1
    !


    Here is R3 (misc Branch Router)


    hostname R3
    !
    !
    !
    card type e1 0 1
    !
    !
    network-clock-participate wic 1
    !
    !
    controller E1 0/1/0
    framing NO-CRC4
    linecode ami
    pri-group timeslots 1-3,16,24
    description ***Voice to PSTN***
    !
    controller E1 0/1/1
    framing NO-CRC4
    linecode ami
    channel-group 0 timeslots 1-24
    description ***Data to PSTN***
    !
    !
    interface Serial0/1/0:15
    description ***Voice to PSTN***
    no ip address
    encapsulation hdlc
    isdn switch-type primary-net5
    isdn incoming-voice voice
    no cdp enable
    !
    interface Serial0/1/1:0
    description ***Data to PSTN***
    no ip address
    encapsulation frame-relay IETF
    frame-relay lmi-type ansi
    !
    interface Serial0/1/1:0.301 point-to-point
    description frame relay to R1
    ip address 177.0.201.2 255.255.255.252
    ip ospf network point-to-point
    snmp trap link-status
    frame-relay interface-dlci 301
    !
    !
    router ospf 1
    router-id 3.3.3.3
    network 3.3.3.0 0.0.0.255 area 3
    network 177.0.201.0 0.0.0.255 area 0
    network 177.3.11.0 0.0.0.255 area 3
    network 177.3.12.0 0.0.0.255 area 3
    !
    !
    voice-port 0/1/0:15
    !
    · Share on FacebookShare on Twitter
  • dentrydentry Member Posts: 42 ■■□□□□□□□□
    Above I have posed the three running configs for the PSTN, HQ, and a branch router. I pulled out anything that was not related to voice. Below I will paste the show controllers from the frame relay serial ports.

    PSTN#show controller T1 0/0/1
    T1 0/0/1 is up.
    Applique type is Channelized T1
    Cablelength is long 0db
    Description: ***Data to R1***
    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: 20100222, FPGA: 13, spm_count = 0
    Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
    CRC Threshold is 320. Reported from firmware is 320.
    Data in current interval (633 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
    Data in Interval 1:
    12889 Line Code Violations, 12 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs, 18 Unavail Secs
    Data in Interval 2:
    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 2 15 minute intervals):
    12889 Line Code Violations, 12 Path Code Violations,
    2 Slip Secs, 0 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins,
    2 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs, 18 Unavail Secs

    PSTN#show controller T1 0/1/1
    T1 0/1/1 is up.
    Applique type is Channelized T1
    Cablelength is long 0db
    Description: ***Data to R2***
    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: 20100222, FPGA: 13, spm_count = 0
    Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
    CRC Threshold is 320. Reported from firmware is 320.
    Data in current interval (659 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
    Data in Interval 1:
    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
    Data in Interval 2:
    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 2 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, 0 Unavail Secs

    PSTN#show controller E1 0/2/1
    E1 0/2/1 is up.
    Applique type is Channelized E1 - balanced
    Description: ***Data to R3***
    No alarms detected.
    alarm-trigger is not set
    Version info Firmware: 20100222, FPGA: 13, spm_count = 0
    Framing is NO-CRC4, Line Code is AMI, Clock Source is Line.
    Data in current interval (684 seconds elapsed):
    0 Line Code Violations, 0 Path Code Violations
    111 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    111 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    Data in Interval 1:
    0 Line Code Violations, 0 Path Code Violations
    146 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    146 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    Data in Interval 2:
    3 Line Code Violations, 58 Path Code Violations
    147 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins
    148 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    Total Data (last 2 15 minute intervals):
    3 Line Code Violations, 58 Path Code Violations,
    293 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins,
    294 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    · Share on FacebookShare on Twitter
  • EdTheLadEdTheLad Member Posts: 2,111 ■■■■□□□□□□
    Hi Dentry,
    Before requesting help, can you spend the time to check your config is correct, i expect a CCNA at the very least to be able to do a sanity check. Look a the below config R3 connects to R1, if i go by your descriptions the FR interfaces are on different networks.
    I cant understand why you cant ask a simple question like:
    I have 3 routers connected, router a,b and c. Ra ser0/0/1 is connected to Rb ser1/1/1, Ra ser0/0/2 is connected to Rc ser2/2/1. The port between Ra and Rc is down and wont come up.
    Instead you paste configs lots of interface configs where the dlci's and descriptions don't match up, i'm here to help but not do your job.So i'm not looking at this anymore!



    R3
    interface Serial0/1/1:0.301 point-to-point
    description frame relay to R1
    ip address 177.0.201.2 255.255.255.252
    ip ospf network point-to-point
    snmp trap link-status
    frame-relay interface-dlci 301
    !


    R1
    interface Serial0/3/1:0.102 point-to-point
    description frame relay link to R2
    ip address 177.0.201.1 255.255.255.252
    ip ospf network point-to-point
    frame-relay interface-dlci 102
    !
    interface Serial0/3/1:0.103 point-to-point
    description frame relay link to R3
    ip address 177.0.101.1 255.255.255.252
    ip ospf network point-to-point
    frame-relay interface-dlci 103
    Networking, sometimes i love it, mostly i hate it.Its all about the $$$$
    · Share on FacebookShare on Twitter
  • dentrydentry Member Posts: 42 ■■□□□□□□□□
    Sorry Ed, I was trying to provide as much Voice config related information as possible. I matched the DLCI's numbering to their respective routers as you requested. I wasnt aware of an exact format for questions.
    · Share on FacebookShare on Twitter
  • dentrydentry Member Posts: 42 ■■□□□□□□□□
    No thanks to Ed, I figured out what was wrong. Turns out the LMI command is needed.
    · Share on FacebookShare on Twitter
Sign In or Register to comment.