01-09-2003 02:52 PM - edited 03-02-2019 04:04 AM
I've got a Cisco 1720 with 2 t1's at the central office. One goes to our internet t1( working fine). The other to a remote office( not working). The Siemens is set up to handle fram-relay, dlci 16, with an IP of 192.168.1.2.
On the cisco end, I have gone through many configuration and have found that setting the configuration to
interface Serial1
ip address 192.168.1.1 255.255.255.0
no ip directed-broadcast
encapsulation frame-relay IETF
no ip mroute-cache
frame-relay interface-dlci 16
frame-relay intf-type dce
will get the line to show serial up and protocol up.
The PVC also is shown as active when I do a show PVC.
I am unable to ping the loacal serial interface, and am unable to ping the remote serial interface.
Any help would be greatly appreciated.
Thanks in advance.
Phillip
01-09-2003 03:31 PM
You will not be able to ping the local interface address because this is a multipoint interface.
Alternatively you can use subinterfaces to make it appear as a point to point interface and make it pingable. See the following URL for an example -
01-10-2003 08:09 AM
OK, I have it set up as a point to point sub interface.
interface Serial1
no ip address
no ip directed-broadcast
encapsulation frame-relay IETF
no ip mroute-cache
frame-relay intf-type dce
!
interface Serial1.1 point-to-point
ip address 192.168.1.1 255.255.255.0
no ip directed-broadcast
frame-relay interface-dlci 50
gw#sh frame-relay map
Serial1.1 (up): point-to-point dlci, dlci 50(0x32,0xC20), broadcast
status defined, active
gw#sh frame-relay pvc
PVC Statistics for interface Serial1 (Frame Relay DCE)
Active Inactive Deleted Static
Local 1 0 0 0
Switched 0 0 0 0
Unused 0 0 0 0
DLCI = 50, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1.1
input pkts 0 output pkts 30 in bytes 0
out bytes 4201 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 7 out bcast bytes 2121
pvc create time 00:09:14, last time pvc status changed 00:06:50
gw#show int serial1
Serial1 is up, line protocol is up
Hardware is PQUICC with Fractional T1 CSU/DSU
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliablility 255/255, txload 1/255, rxload 1/255
Encapsulation FRAME-RELAY IETF, loopback not set
Keepalive set (10 sec)
LMI enq sent 212, LMI stat recvd 0, LMI upd recvd 0
LMI enq recvd 8253, LMI stat sent 7960, LMI upd sent 0, DCE LMI up
LMI DLCI 0 LMI type is ANSI Annex D frame relay DCE
FR SVC disabled, LAPF state down
Broadcast queue 0/64, broadcasts sent/dropped 52/0, interface broadcasts 0
Last input 00:00:04, output 00:00:04, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/26/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
10612 packets input, 273914 bytes, 0 no buffer
Received 234 broadcasts, 0 runts, 4 giants, 0 throttles
192 input errors, 45 CRC, 143 frame, 0 overrun, 0 ignored, 1 abort
1433392 packets output, 927600204 bytes, 0 underruns
0 output errors, 0 collisions, 109 interface resets
0 output buffer failures, 0 output buffers swapped out
13 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
gw#show int serial1.1
Serial1.1 is up, line protocol is up
Hardware is PQUICC with Fractional T1 CSU/DSU
Internet address is 192.168.1.1/24
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation FRAME-RELAY IETF
I still can't ping 192.168.1.1, nor the other end of the T1. Any thoughts?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: