Options

Why Metric Of 2?

Here is the show ip route of R2 on my rack:

R2_1760#show ip route
1.0.0.0/32 is subnetted, 1 subnets
R 1.1.1.1 [120/1] via 10.35.1.1, 00:00:25, Serial0/0
2.0.0.0/32 is subnetted, 1 subnets
C 2.2.2.2 is directly connected, Loopback0
33.0.0.0/32 is subnetted, 1 subnets
R 33.3.3.3 [120/2] via 10.35.1.3, 00:00:25, Serial0/0
3.0.0.0/32 is subnetted, 1 subnets
R 3.3.3.3 [120/2] via 10.35.1.3, 00:00:25, Serial0/0
55.0.0.0/32 is subnetted, 1 subnets
R 55.5.5.5 [120/2] via 10.35.1.3, 00:00:25, Serial0/0
10.0.0.0/16 is subnetted, 1 subnets
C 10.35.0.0 is directly connected, Serial0/0
44.0.0.0/32 is subnetted, 1 subnets
R 44.4.4.4 [120/2] via 10.35.1.3, 00:00:03, Serial0/0

When I ping 3.3.3.3, 33.3.3.3, 44.4.4.4, 55.5.5.5 it comes back failed. Why would this be? I can ping those IPs from any other router. Why is the metric 2 to those routes, but 1.1.1.1 which is on my R1 router has a metric of 1?

I am using RIPv2 with no auto-summary.

Comments

  • Options
    Morty3Morty3 Member Posts: 139
    Cant tell why you cant ping since no configs are posted. Maybe failed at encapsulation or no set clockrate somewhere?
    CCNA, CCNA:Sec, Net+, Sonicwall Admin (fwiw). Constantly getting into new stuff.
  • Options
    boostinbadgerboostinbadger Member Posts: 256
    Clock rates are fine. I can ping from serial to serial on all three routers, but I can't ping loopbacks from r2. I will have to post the configs when I get home this evening.
  • Options
    boostinbadgerboostinbadger Member Posts: 256
    Here are the configs:

    R1_1760#show conf
    Using 929 out of 29688 bytes
    !
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    !
    hostname R1_1760
    !
    boot-start-marker
    boot system flash c1700-ipbasek9-mz.124-23.bin
    boot-end-marker
    !
    no aaa new-model
    ip cef
    !
    no ip domain lookup
    !
    interface Loopback0
    ip address 1.1.1.1 255.255.255.255
    !
    interface FastEthernet0/0
    no ip address
    speed auto
    !
    interface Serial0/0
    ip address 10.35.1.1 255.255.0.0
    encapsulation frame-relay
    no fair-queue
    !
    interface Serial0/1
    no ip address
    shutdown
    !
    router rip
    version 2
    network 1.0.0.0
    network 10.0.0.0
    no auto-summary
    !
    ip forward-protocol nd
    !
    no ip http server
    no ip http secure-server
    !
    control-plane
    !
    line con 0
    exec-timeout 0 0
    logging synchronous
    login
    line aux 0
    line vty 0 4
    login
    !
    end



    R2_1760#show conf
    Using 914 out of 29688 bytes
    !
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    !
    hostname R2_1760
    !
    boot-start-marker
    boot system flash c1700-ipbasek9-mz.124-23.bin
    boot-end-marker
    !
    no aaa new-model
    ip cef
    !
    no ip domain lookup
    !
    interface Loopback0
    ip address 2.2.2.2 255.255.255.255
    !
    interface FastEthernet0/0
    no ip address
    speed auto
    !
    interface Serial0/0
    ip address 10.35.1.2 255.255.0.0
    encapsulation frame-relay
    !
    interface Serial0/1
    no ip address
    shutdown
    !
    router rip
    version 2
    network 2.0.0.0
    network 10.0.0.0
    no auto-summary
    !
    ip forward-protocol nd
    !
    no ip http server
    no ip http secure-server
    !
    control-plane
    !
    !
    line con 0
    exec-timeout 0 0
    logging synchronous
    login
    line aux 0
    line vty 0 4
    login
    !
    end



    R3_1760#show conf
    Using 1098 out of 29688 bytes
    !
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    !
    hostname R3_1760
    !
    boot-start-marker
    boot-end-marker
    !
    no aaa new-model
    ip cef
    !
    no ip domain lookup
    !
    interface Loopback0
    ip address 3.3.3.3 255.255.255.255
    !
    interface Loopback1
    ip address 33.3.3.3 255.255.255.255
    !
    interface Loopback2
    ip address 44.4.4.4 255.255.255.255
    !
    interface Loopback3
    ip address 55.5.5.5 255.255.255.255
    !
    interface FastEthernet0/0
    no ip address
    speed auto
    !
    interface Serial0/0
    ip address 10.35.1.3 255.255.0.0
    encapsulation frame-relay
    !
    interface Serial0/1
    no ip address
    shutdown
    !
    router rip
    version 2
    network 3.0.0.0
    network 10.0.0.0
    network 33.0.0.0
    network 44.0.0.0
    network 55.0.0.0
    no auto-summary
    !
    ip forward-protocol nd
    !
    no ip http server
    no ip http secure-server
    !
    control-plane
    !
    line con 0
    exec-timeout 0 0
    logging synchronous
    login
    line aux 0
    line vty 0 4
    login
    !
    end

    R1 can ping all interfaces including loopbacks. R2 and R3 can ping R1 but no interfaces between them.
  • Options
    gojericho0gojericho0 Member Posts: 1,059 ■■■□□□□□□□
    when you do a traceroute does it get to the other routers serial addresses?

    you can also do a debug ip packet detail on both ends to see if there is a problem as well
  • Options
    dtlokeedtlokee Member Posts: 2,378 ■■■■□□□□□□
    Looks like you are using a frame relay are all of the routers fully meshed? What does your "sh frame pvc" output look like?
    The only easy day was yesterday!
  • Options
    boostinbadgerboostinbadger Member Posts: 256
    FRS_2612#show frame pvc

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

    Active Inactive Deleted Static
    Local 0 0 0 0
    Switched 2 0 0 0
    Unused 0 0 0 0

    DLCI = 122, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial0/0

    input pkts 9281 output pkts 9284 in bytes 1538186
    out bytes 1539314 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
    30 second input rate 0 bits/sec, 0 packets/sec
    30 second output rate 0 bits/sec, 0 packets/sec
    switched pkts 9281
    Detailed packet drop counters:
    no out intf 0 out intf down 0 no out PVC 0
    in PVC down 0 out PVC down 0 pkt too big 0
    shaping Q full 0 pkt above DE 0 policing drop 0
    pvc create time 6d19h, last time pvc status changed 5d01h

    DLCI = 123, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial0/0

    input pkts 9323 output pkts 9311 in bytes 1542114
    out bytes 1541402 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
    30 second input rate 0 bits/sec, 0 packets/sec
    30 second output rate 0 bits/sec, 0 packets/sec
    switched pkts 9323
    Detailed packet drop counters:
    no out intf 0 out intf down 0 no out PVC 0
    in PVC down 0 out PVC down 0 pkt too big 0
    shaping Q full 0 pkt above DE 0 policing drop 0
    pvc create time 6d19h, last time pvc status changed 5d01h

    PVC Statistics for interface Serial0/1 (Frame Relay DCE)

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

    DLCI = 221, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial0/1

    input pkts 9286 output pkts 9281 in bytes 1539524
    out bytes 1538186 dropped pkts 2 in pkts dropped 2
    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
    30 second input rate 0 bits/sec, 0 packets/sec
    30 second output rate 0 bits/sec, 0 packets/sec
    switched pkts 9285
    Detailed packet drop counters:
    no out intf 0 out intf down 0 no out PVC 0
    in PVC down 0 out PVC down 2 pkt too big 0
    shaping Q full 0 pkt above DE 0 policing drop 0
    pvc create time 6d19h, last time pvc status changed 5d01h

    PVC Statistics for interface Serial0/2 (Frame Relay DCE)

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

    DLCI = 321, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial0/2

    input pkts 9312 output pkts 9323 in bytes 1541436
    out bytes 1542114 dropped pkts 2 in pkts dropped 2
    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
    30 second input rate 0 bits/sec, 0 packets/sec
    30 second output rate 0 bits/sec, 0 packets/sec
    switched pkts 9311
    Detailed packet drop counters:
    no out intf 0 out intf down 0 no out PVC 0
    in PVC down 0 out PVC down 2 pkt too big 0
    shaping Q full 0 pkt above DE 0 policing drop 0
    pvc create time 6d19h, last time pvc status changed 5d01h
  • Options
    dtlokeedtlokee Member Posts: 2,378 ■■■■□□□□□□
    So you're not using a frame relay switch between these routers?
    The only easy day was yesterday!
  • Options
    phoeneousphoeneous Member Posts: 2,333 ■■■■■■■□□□
    Can these masks be used?
    interface Loopback0
    ip address 3.3.3.3 255.255.255.255
    !
    interface Loopback1
    ip address 33.3.3.3 255.255.255.255
    !
    interface Loopback2
    ip address 44.4.4.4 255.255.255.255
    !
    interface Loopback3
    ip address 55.5.5.5 255.255.255.255
    
  • Options
    kalebkspkalebksp Member Posts: 1,033 ■■■■■□□□□□
    phoeneous wrote: »
    Can these masks be used?
    interface Loopback0
    ip address 3.3.3.3 255.255.255.255
    !
    interface Loopback1
    ip address 33.3.3.3 255.255.255.255
    !
    interface Loopback2
    ip address 44.4.4.4 255.255.255.255
    !
    interface Loopback3
    ip address 55.5.5.5 255.255.255.255
    

    Yes, they are masks for a subnet with only a single host.

    boostinbadger, you should add frame-relay maps to the spoke routers. They don't know how to contact each other because they have no DLCI to IP mapping. They're able to contact the hub router because of inverse arp.

    So, on R2 add "frame-relay map ip 10.35.1.3 221 broadcast" and on R3 "frame-relay map ip 10.35.1.2 321 broadcast".
  • Options
    boostinbadgerboostinbadger Member Posts: 256
    I am using frame relay.

    I have "no inverse arp" on all interfaces on the frame relay switch.

    R1 can ping R2 and R3 through the frame switch
    R2 can ping R1 but not R3 and vice versa

    Here is the frame switch config:

    FRS_2612#show conf
    Using 1537 out of 29688 bytes
    !
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    !
    hostname FRS_2612
    !
    boot-start-marker
    boot-end-marker
    !
    no aaa new-model
    ip cef
    !
    no ip domain lookup
    frame-relay switching
    !
    interface Ethernet0/0
    no ip address
    shutdown
    half-duplex
    !
    interface Serial0/0
    no ip address
    encapsulation frame-relay
    logging event subif-link-status
    logging event dlci-status-change
    clock rate 56000
    no frame-relay inverse-arp
    frame-relay intf-type dce
    frame-relay route 122 interface Serial0/1 221
    frame-relay route 123 interface Serial0/2 321
    !
    interface TokenRing0/0
    no ip address
    shutdown
    ring-speed 16
    !
    interface Serial0/1
    no ip address
    encapsulation frame-relay
    logging event subif-link-status
    logging event dlci-status-change
    clock rate 56000
    no frame-relay inverse-arp
    frame-relay intf-type dce
    frame-relay route 221 interface Serial0/0 122
    !
    interface Serial0/2
    no ip address
    encapsulation frame-relay
    logging event subif-link-status
    logging event dlci-status-change
    clock rate 56000
    no frame-relay inverse-arp
    frame-relay intf-type dce
    frame-relay route 321 interface Serial0/0 123
    !
    interface Serial0/3
    no ip address
    shutdown
    !
    ip forward-protocol nd
    !
    ip http server
    no ip http secure-server
    !
    control-plane
    !
    line con 0
    exec-timeout 0 0
    logging synchronous
    login
    line aux 0
    line vty 0 4
    !
    end
  • Options
    kalebkspkalebksp Member Posts: 1,033 ■■■■■□□□□□
    Inverse ARP is disabled on the routers, not the frame relay switch. A frame relay interface will send inverse ARP replies even if inverse ARP is disabled.
  • Options
    boostinbadgerboostinbadger Member Posts: 256
    That doesn't explain why only R2 and R3 can't communicate and R1 can ping all interfaces including loopbacks.
  • Options
    kalebkspkalebksp Member Posts: 1,033 ■■■■■□□□□□
    As I said in one of my previous replies, it's because R2 and R3 don't have an IP to DLCI mapping for each other.

    The reason that R1 can ping everything is because inverse ARP automatically creates those mappings. When you try to ping R3 from R2, R2 looks in it's ARP cache/mappings to find R3's L2 address (DLCI, since you're using frame relay) based on it's IP. Since it doesn't have a mapping for R3's IP address the ping fails. You can use "show frame-relay mapping" to see the DLCI to IP mappings.

    To correct this see my other reply which includes the appropriate frame-relay map commands.
  • Options
    boostinbadgerboostinbadger Member Posts: 256
    Ok. I understand what you are saying now. Forgive me for not getting it the first time. I put the two commands on r2 and r3 and it works now. Should I add the commands to r1 so that it won't strictly rely on inverse arp or does it matter?
  • Options
    boostinbadgerboostinbadger Member Posts: 256
    Nevermind. I see that R1 has its mappings set to dynamic (using inverse arp) and when I put in the static mappings, it now reads static.

    Thanks for the help kalebksp.
  • Options
    phoeneousphoeneous Member Posts: 2,333 ■■■■■■■□□□
    kalebksp wrote: »
    Yes, they are masks for a subnet with only a single host.

    I thought /31 was. I guess I was wrong.
  • Options
    phoeneousphoeneous Member Posts: 2,333 ■■■■■■■□□□
    phoeneous wrote: »
    I thought /31 was. I guess I was wrong.

    This has helped me understand it more for using /32 for single hosts. Useful for summarization.

    How /30 and /32 bit IP subnet masks can help you with Cisco Networking
  • Options
    boostinbadgerboostinbadger Member Posts: 256
    Somehow the config got erased from R3 so I had to reconfigure it. Now I can't ping serial interfaces between R2 and R3 again. However, I can ping R3's loopback from R2 and vice versa. I believe this works because of the ether channel link I have setup between the two switches that are hanging off each router's fa.

    Here is R2's config:
    R2_1760#show conf
    Using 1161 out of 29688 bytes
    !
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    !
    hostname R2_1760
    !
    boot-start-marker
    boot-end-marker
    !
    no aaa new-model
    ip cef
    !
    no ip domain lookup
    !
    interface Loopback0
    ip address 2.2.2.2 255.255.255.255
    !
    interface FastEthernet0/0
    ip address 172.23.23.2 255.255.255.224
    speed auto
    !
    interface Serial0/0
    no ip address
    encapsulation frame-relay
    no frame-relay inverse-arp
    frame-relay lmi-type cisco
    !
    interface Serial0/0.123 multipoint
    ip address 172.12.123.2 255.255.255.0
    frame-relay map ip 172.12.123.1 221 broadcast
    !
    interface Serial0/1
    no ip address
    shutdown
    !
    interface Serial1/0
    no ip address
    shutdown
    !
    interface Serial1/1
    no ip address
    shutdown
    !
    router rip
    version 2
    network 2.0.0.0
    network 172.12.0.0
    network 172.23.0.0
    no auto-summary
    !
    ip forward-protocol nd
    !
    no ip http server
    no ip http secure-server
    !
    control-plane
    !
    line con 0
    exec-timeout 0 0
    logging synchronous
    line aux 0
    line vty 0 4
    login
    !
    end

    Here is R3's config:
    R3_1760#show conf
    Using 1126 out of 29688 bytes
    !
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    !
    hostname R3_1760
    !
    boot-start-marker
    boot-end-marker
    !
    no aaa new-model
    ip cef
    !
    no ip domain lookup
    !
    interface Loopback0
    ip address 3.3.3.3 255.255.255.255
    !
    interface FastEthernet0/0
    ip address 172.23.23.3 255.255.255.224
    speed auto
    !
    interface Serial0/0
    no ip address
    encapsulation frame-relay
    no frame-relay inverse-arp
    frame-relay lmi-type cisco
    !
    interface Serial0/0.31 point-to-point
    ip address 172.12.123.3 255.255.255.0
    frame-relay interface-dlci 321
    !
    interface Serial0/1
    ip address 172.12.13.3 255.255.255.0
    !
    interface Serial1/0
    no ip address
    shutdown
    !
    interface Serial1/1
    no ip address
    shutdown
    !
    router rip
    version 2
    network 3.0.0.0
    network 172.12.0.0
    network 172.23.0.0
    no auto-summary
    !
    ip forward-protocol nd
    !
    no ip http server
    no ip http secure-server
    !
    control-plane
    !
    line con 0
    exec-timeout 0 0
    logging synchronous
    line aux 0
    line vty 0 4
    login
    !
    end

    Here is a show frame route from the FRS:
    2620XM_FRS#show frame-relay route
    Input Intf Input Dlci Output Intf Output Dlci Status
    Serial0/0 122 Serial0/1 221 active
    Serial0/0 123 Serial0/2 321 active
    Serial0/1 221 Serial0/0 122 active
    Serial0/2 321 Serial0/0 123 active

    I believe I am looking past something simple again.
  • Options
    kalebkspkalebksp Member Posts: 1,033 ■■■■■□□□□□
    What is R1's config? First thing that strikes me is that you have R2 configured as multipoint and R3 configured as point-to-point.
  • Options
    boostinbadgerboostinbadger Member Posts: 256
    mulipoint and point to point is how I am told to configure it.

    Here is the config:
    R1_1760#show conf
    Using 1160 out of 29688 bytes
    !
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    !
    hostname R1_1760
    !
    boot-start-marker
    boot-end-marker
    !
    no aaa new-model
    ip cef
    !
    no ip domain lookup
    !
    interface Loopback0
    ip address 1.1.1.1 255.255.255.255
    !
    interface FastEthernet0/0
    no ip address
    shutdown
    speed auto
    !
    interface Serial0/0
    ip address 172.12.123.1 255.255.255.0
    encapsulation frame-relay
    frame-relay map ip 172.12.123.2 122 broadcast
    frame-relay map ip 172.12.123.3 123 broadcast
    no frame-relay inverse-arp
    frame-relay lmi-type cisco
    !
    interface Serial0/1
    ip address 172.12.13.1 255.255.255.0
    clock rate 56000
    !
    interface BRI1/0
    no ip address
    encapsulation hdlc
    shutdown
    !
    router rip
    version 2
    network 1.0.0.0
    network 172.12.0.0
    no auto-summary
    !
    ip forward-protocol nd
    ip route 0.0.0.0 0.0.0.0 172.12.123.2
    !
    no ip http server
    no ip http secure-server
    !
    control-plane
    !
    line con 0
    exec-timeout 0 0
    logging synchronous
    line aux 0
    line vty 0 4
    login
    !
    end
  • Options
    gojericho0gojericho0 Member Posts: 1,059 ■■■□□□□□□□
    up between the two switches that are hanging off each router's fa.

    Here is R2's config:


    !
    interface Serial0/0
    no ip address
    encapsulation frame-relay
    no frame-relay inverse-arp
    frame-relay lmi-type cisco
    !
    interface Serial0/0.123 multipoint
    ip address 172.12.123.2 255.255.255.0
    frame-relay map ip 172.12.123.1 221 broadcast

    Based on the IPs it looks like R2 and R3 are directly connected. Instead of the frame-relay map command for the serial interface try frame-relay interface dlci (local DLCI for this subint)

    Someone correct me if i'm wrong, but I believe you need to use that command since the DLCIs land on the physical interface so you have to statically assign which DLCI goes on which subinterface
  • Options
    boostinbadgerboostinbadger Member Posts: 256
    They aren't physically directly connected.
  • Options
    tech-airmantech-airman Member Posts: 953
    They aren't physically directly connected.

    boostinbadger,

    What's the physical topology for your network?
  • Options
    boostinbadgerboostinbadger Member Posts: 256
    R1, R2, and R3 are connected through a frame relay switch.

    Here is the topology minus the ISDN (for now).

    Rack Rentals For CCNA Certification Prep, Cisco CCNP Exam
  • Options
    tech-airmantech-airman Member Posts: 953
    R1, R2, and R3 are connected through a frame relay switch.

    Here is the topology minus the ISDN (for now).

    Rack Rentals For CCNA Certification Prep, Cisco CCNP Exam

    boostinbadger,

    Questions:
    1. What is your IP scheme for that given network?
    2. What loopback(s) are on R1 and their assigned IP address(es) and subnet mask(s)?
    3. What loopback(s) are on R2 and their assigned IP address(es) and subnet mask(s)?
    4. What loopback(s) are on R3 and their assigned IP address(es) and subnet mask(s)?
    5. Is the "Direct Connection via Serial Int." link being used?
  • Options
    boostinbadgerboostinbadger Member Posts: 256
    R1 - R3 use 172.12.123.x/24 where x is the router number

    Each router has a loopback interface. ex. 1.1.1.1/32 for R1, etc

    I took out the multipoint interface and stuck with point to point and put static frame maps in place again. It is now working again.
  • Options
    tech-airmantech-airman Member Posts: 953
    boostinbadger,
    R1 - R3 use 172.12.123.x/24 where x is the router number

    What is your design IP subnetting plan for the 172.12.123.0/24 IP network for the given network topology?
    Each router has a loopback interface. ex. 1.1.1.1/32 for R1, etc

    If "...each router has a loopback interface. ex. 1.1.1.1/32 for R1, etc..." then what is the purpose for the following IP addresses: 1) 33.3.3.3, 2) 44.4.4.4, 3) 55.5.5.5?
    I took out the multipoint interface and stuck with point to point and put static frame maps in place again. It is now working again.
Sign In or Register to comment.