[c-nsp] EIGRP problems

james edwards hackerwacker at cybermesa.com
Mon Oct 24 12:58:09 EDT 2005


I have 2 routers (SFcolo-dsl & ESPNXC-router); a DS3 is the only connection
between them. Try as I might they will not talk EIGRP between them. I'm
hoping I have missed something basic here. The DS3 is ATM one side & FR on
the other; there is a CBX-500 FR/ATM switch between them to do the FRF-x FR
to ATM conversion.

IP classless & ip subnet-zero are set on both routers.

Here is the SFcolo-dsl router, ATM5/0.2000 is the connection in question,
c7200-js-mz.122-15.T13.bin, on a 7206 NPE-400:

!
interface ATM5/0.2000 point-to-point
 description DS3 to ESPNXC, ESPNXC-router
 bandwidth 44210
 ip address 65.19.34.62 255.255.255.252
 no ip redirects
 no ip unreachables
 no ip proxy-arp
 ip pim dense-mode
 pvc 3/32
  protocol ip 65.19.34.61
  no broadcast
  encapsulation aal5snap
 !

!
router eigrp 101
 redistribute connected
 redistribute static
 passive-interface ATM5/0.1001
 passive-interface ATM5/0.1022
 passive-interface ATM5/0.1033
 network 65.0.0.0
 default-metric 44000 2000 255 1 1500
 distribute-list prefix sfcolo out
 no auto-summary

ATM5/0.2000 is not in the "eigrp neighbors" table:

SFcolo-dsl#sho ip eigrp neighbors
IP-EIGRP neighbors for process 101
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
Type
                                            (sec)         (ms)       Cnt Num
0   65.19.0.5               AT3/0.1           11 5d03h       4   200  0
3269226
3   65.19.0.173             AT5/0.1018        12 1w1d        1   200  0
71989
4   65.19.0.65              AT5/0.1044       143 1w3d       20   200  0
153811
2   65.19.0.73              AT5/0.1008       163 1w3d       16   200  0
216030
SFcolo-dsl#

Only the connected prefix is in the topology table and RIB:

SFcolo-dsl#sho ip eigrp topology | include ATM5/0.2000
         via Connected, ATM5/0.2000

SFcolo-dsl#sho ip eigrp topology | begin 65.19.34.60
P 65.19.34.60/30, 1 successors, FD is 67584
         via Connected, ATM5/0.2000

SFcolo-dsl#sho ip route | include ATM5/0.2000
C       65.19.34.60/30 is directly connected, ATM5/0.2000
SFcolo-dsl#





Here is the other side of the DS3, on ESPNXC-router,
c7200-js-mz.122-18.S10.bin on a
7206 NPE-300, Serial2/0 is the link to to other side, SFcolo-dsl router:


!
interface Serial2/0
 description DS3 to SFMN, SFcolo-dsl router
 bandwidth 44210
 ip address 65.19.34.61 255.255.255.252
 ip pim dense-mode
 encapsulation frame-relay IETF
 ntp multicast client
 dsu bandwidth 44210
 framing c-bit
 cablelength 100
 serial restart-delay 0
 frame-relay map ip 65.19.34.62 17 broadcast
 frame-relay interface-dlci 17

!
router eigrp 101
 redistribute connected
 default-metric 1500 2000 255 1 1500
 passive-interface FastEthernet0/0
 distribute-list prefix ESPN-out out
 no auto-summary

!
ip prefix-list ESPN-out seq 5 permit 65.19.0.78/32
ip prefix-list ESPN-out seq 10 permit 65.19.29.0/24
ip prefix-list ESPN-out seq 15 permit 65.19.34.60/30
!



ESPNXC-router#sho ip route
Gateway of last resort is 65.19.34.62 to network 0.0.0.0

     65.0.0.0/8 is variably subnetted, 6 subnets, 3 masks
C       65.19.0.78/32 is directly connected, Loopback0
S       65.19.16.3/32 [1/0] via 65.19.34.62
C       65.19.34.60/30 is directly connected, Serial2/0
C       65.19.29.0/24 is directly connected, Loopback1
S       65.19.5.0/24 [1/0] via 10.123.9.1
S       65.19.56.22/32 [1/0] via 10.123.9.1
     xx.xx.0.0/8 is variably subnetted, 2 subnets, 2 masks
S       xx,xx.0.0/16 [1/0] via 10.123.9.1
C       xx.xx.9.0/24 is directly connected, FastEthernet0/0
S*   0.0.0.0/0 [1/0] via 65.19.34.62
ESPNXC-router#

(xx.xx.0.0/8 are management IP's and should be filtered out via prefix-list
ESPN-out, so I am not disclosing what network I use for management. I am
leaving the rest in the clear so troubleshooting is easier)


I'm getting nothing for all "sho ip eigrp <whatever>" commands

ESPNXC-router#sho ip eigrp neighbors
IP-EIGRP neighbors for process 101
ESPNXC-router#

ESPNXC-router#sho ip eigrp interfaces
IP-EIGRP interfaces for process 101

                        Xmit Queue   Mean   Pacing Time   Multicast
Pending
Interface        Peers  Un/Reliable  SRTT   Un/Reliable   Flow Timer
Routes
ESPNXC-router#

ESPNXC-router#sho ip eigrp traffic
IP-EIGRP Traffic Statistics for AS 101
  Hellos sent/received: 0/0
  Updates sent/received: 0/0
  Queries sent/received: 0/0
  Replies sent/received: 0/0
  Acks sent/received: 0/0
  Input queue high water mark 0, 0 drops
  SIA-Queries sent/received: 0/0
  SIA-Replies sent/received: 0/0

ESPNXC-router#

ESPNXC-router#sho ip eigrp topology
IP-EIGRP Topology Table for AS(101)/ID(65.19.29.1)
ESPNXC-router#


So it does not seem like either router is talking EIGRP with the other. Why
?









More information about the cisco-nsp mailing list