Any Cisco frame-relay gurus in here?

[HardDrive]

These puppys will not talk.
Why is the line protocol up, but they won't transfer traffic?
Does it matter that the DLCI is the same?

R1
Serial1 is up, line protocol is up
Hardware is HD64570
Internet address is 192.168.100.129/26
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation FRAME-RELAY, loopback not set
Keepalive set (10 sec)
LMI enq sent 69, LMI stat recvd 0, LMI upd recvd 0
LMI enq recvd 1132, LMI stat sent 1071, LMI upd sent 0, DCE LMI up
LMI DLCI 1023 LMI type is CISCO frame relay DCE
FR SVC disabled, LAPF state down
Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0
Last input 00:00:09, output 00:00:09, output hang never
Last clearing of "show interface" counters 03:10:23
Input queue: 0/75/13/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/1/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1307 packets input, 20325 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles


R2
Serial0 is up, line protocol is up
Hardware is HD64570
Internet address is 192.168.100.130/26
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation FRAME-RELAY, loopback not set
Keepalive set (10 sec)
LMI enq sent 1140, LMI stat recvd 1083, LMI upd recvd 0, DTE LMI up
LMI enq recvd 57, LMI stat sent 0, LMI upd sent 0
LMI DLCI 1023 LMI type is CISCO frame relay DTE
FR SVC disabled, LAPF state down
Broadcast queue 0/64, broadcasts sent/dropped 155/0, interface broadcasts 0
Last input 00:00:02, output 00:00:02, output hang never
Last clearing of "show interface" counters 03:10:14
Input queue: 0/75/5/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/1/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1300 packets input, 21850 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

[911skb]

It's been awhile since I've done a config like that, but I'll give it a shot.

The DLCI 1023 is only for exchanging LMI status enquiries and responses, same as DLCI 0 if you used the Ansi-AnnexD LMI flavor.

You need to build the sub-interface, assing a DLCI to the sub-interface, use DLCI 100 for example and map the IP address.

Hope that helps, it's been a long time since I've configured something similar.

Good luck.

[masraum]

I'm a Cisco dude, can you send the int configs?

[KFC911]

Originally posted by masraum
I'm a Cisco dude, can you send the int configs?

"Cisco dude, was a friend of mine,
Cisco dude, was a friend of mine...."

I'm sorry, but I've got WAR on my mind this morning....

ps: The band, not the fiasco

[masraum]

Originally posted by 911skb
The DLCI 1023 is only for exchanging LMI status enquiries and responses, same as DLCI 0 if you used the Ansi-AnnexD LMI flavor.

You need to build the sub-interface, assing a DLCI to the sub-interface, use DLCI 100 for example and map the IP address.
Good luck.

Like you said, 1023 is used for LMI, and that's what you're seeing, not his configured DLCI which probably is something different. A Cisco router won't let you configure anything above 1007.

You need to send the interface configs, the output of "sho int" doesn't give us enough info.

[HardDrive]

Thanks guys. I'm off on another disaster, but I will see if I can post configs later.