Help w/ Frame Relay and subinterfaces

[duboismatthew]

I am a CCNA and starting to work on my CCNP, I just started working for a new company and my first project is to find out what was wrong with their Frame Relay connection and FIX IT!. I have pasted the config below that was done by somebody else.

Can somebody help me figure this out?

Thanks in advance,

Matt

Notes:

This is new and was configured by somebody else but has never worked. (I noticed that the PVC has been deleted...Could that be it and what command would turn it on?)

-----------------------------------------

sh run

Building configuration...

Current configuration : 871 bytes

!

version 12.1

!

interface Serial0/0

no ip address

encapsulation frame-relay

frame-relay lmi-type ansi

!

interface Serial0/0.1 point-to-point

ip address 10.20.63.2 255.255.255.0

frame-relay interface-dlci 110

!

interface FastEthernet0/1

no ip address

shutdown

duplex auto

speed auto

!

ip classless

no ip http server

!

snmp-server community public RO

!

end

---------------------------------------

sh frame pvc

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

Active Inactive Deleted Static

Local 0 0 1 0

Switched 0 0 0 0

Unused 0 0 0 0

DLCI = 110, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE = Serial0/0.1

input pkts 0 output pkts 12 in bytes 0

out bytes 1947 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 3 out bcast bytes 1011

pvc create time 16:27:10, last time pvc status changed 15:17:52

----------------------------------------

sh frame map

Serial0/0.1 (down): point-to-point dlci, dlci 110(0x6E,0x18E0), broadcast

status deleted

----------------------------------------

sh ip int br

Serial0/0 unassigned YES manual up down

Serial0/0.1 10.20.63.2 YES manual down down

[MickPhelps]

Don't worry about the BW at this time. Its only used to determine metrics for routing protocols (for the most part). It won't affect your connectivity.

We'll wait for tomorrow to see the info off the remote router then.

Mick.

[duboismatthew]

Thanks so much for your time and help. I was able to compare configs and fix the problem first thing this morning.

Thanks again,

matt

[mariont]

BW(Bandwidth)is also used for Network Management, through of SNMP protocol, for calculate utilization Interface rate.

[duboismatthew]

Mick if you are still there, I have one more question, I am able to see and ping the remote router from my router, but I cannot ping the remote router from any workstations. We are using static routes. Any suggestions?

Thanks again,

matt

[MickPhelps]

First try to ping the ethernet address of the far router. If you can't ping it, it is because you don't have a route to it on your router.

Next go to your router and type PING with no address.

enter the destination address as the remote router and the protocol as IP.

Press for everything until you get to "extended commands" then press "y"

Make the source IP address your ethernet interface of your router.

If the ping fails, it is because the far router doesn't have a route back to your ethernet.

Mick.

[duboismatthew]

One problem after another... but I am learning alot.

That worked, I was able to ping the remote eth int from my router, but I just tried to ping my PC from the Frame-Relay WAN sub-interface and I am unable to, although I can ping the eth int from the WAN sub-int.

Thanks,

Matt

[MickPhelps]

That would mean that the default gateway set on your PC doesn't have a route to the FR.

Mick.

[duboismatthew]

Thanks so much again to Mick and Marion for all your help. I had figured that it was probably the default gateway, but I wasn't sure and you confirmed it for me. Everything is up and running great now. Thanks again for your time and patience.

Matt

[mariont]

You must to configure a static route for Network Address of the LAN workstations.

In border router, configure route for Address Network of LAN.