How can I tell if it is a 56 kbps or 64 kbps circuit?

dagates · ‎04-30-2004

I don't trust the telco and am having the same exact problem with two sites. Both sites have 1721s with WIC-2A/S's. 1,000 1,000 byte PINGs has about 96% successful.

Config:

interface Serial0

description test circuit

bandwidth 64

no ip address

encapsulation frame-relay

logging event subif-link-status

logging event dlci-status-change

frame-relay lmi-type ansi

show controller serial 0

Interface Serial0

Hardware is PowerQUICC MPC860

DTE V.35 TX and RX clocks detected.

idb at 0x81842A84, driver data structure at 0x818453F0

SCC Registers:

General [GSMR]=0x2:0x00000030, Protocol-specific [PSMR]=0x8

Events [SCCE]=0x0000, Mask [SCCM]=0x001F, Status [SCCS]=0x06

Transmit on Demand [TODR]=0x0, Data Sync [DSR]=0x7E7E

Interrupt Registers:

Config [CICR]=0x00365F80, Pending [CIPR]=0x00008004

Mask [CIMR]=0x48204002, In-srv [CISR]=0x00000000

Command register [CR]=0x6C0

Port A [PADIR]=0x5400, [PAPAR]=0xFFFF

[PAODR]=0x0000, [PADAT]=0x22FE

Port B [PBDIR]=0x0FC0F, [PBPAR]=0x0600E

[PBODR]=0x00000, [PBDAT]=0x1613C

Port C [PCDIR]=0x00C, [PCPAR]=0x000

[PCSO]=0xBE0, [PCDAT]=0x7CC, [PCINT]=0x000

Receive Ring

rmd(FF002430): status 9000 length 2E address 383F6C4

rmd(FF002438): status B000 length 40 address 38403C4

Transmit Ring

tmd(FF0024B0): status DC00 length 25C address 37041D4

tmd(FF0024B8): status 5C00 length 2D address 3876754

tmd(FF0024C0): status 5C00 length 2D address 3703E94

tmd(FF0024C8): status 5C00 length 2D address 3705554

tmd(FF0024D0): status 5C00 length 2D address 3704514

tmd(FF0024D8): status 5C00 length 2D address 3704854

tmd(FF0024E0): status 5C00 length 2D address 3704B94

tmd(FF0024E8): status 5C00 length 2D address 3877114

tmd(FF0024F0): status 5C00 length 2D address 3706254

tmd(FF0024F8): status 5C00 length 2E address 3703B54

tmd(FF002500): status 5C00 length 30 address 3702694

tmd(FF002508): status 5C00 length 2C address 3701A14

tmd(FF002510): status 5C00 length 2E address 37036D4

tmd(FF002518): status 5C00 length A9 address 387CA14

tmd(FF002520): status 5C00 length 2C address 3875214

tmd(FF002528): status 7C00 length 2C address 37022D4

tx_limited=1(2)

SCC GENERAL PARAMETER RAM (at 0xFF003C00)

Rx BD Base [RBASE]=0x2430, Fn Code [RFCR]=0x18

Tx BD Base [TBASE]=0x24B0, Fn Code [TFCR]=0x18

Max Rx Buff Len [MRBLR]=1548

Rx State [RSTATE]=0x18008440, BD Ptr [RBPTR]=0x2438

Tx State [TSTATE]=0x18800511, BD Ptr [TBPTR]=0x24B0

SCC HDLC PARAMETER RAM (at 0xFF003C38)

CRC Preset [C_PRES]=0xFFFF, Mask [C_MASK]=0xF0B8

Errors: CRC [CRCEC]=332, Aborts [ABTSC]=10, Discards [DISFC]=0

Nonmatch Addr Cntr [NMARC]=0

Retry Count [RETRC]=0

Max Frame Length [MFLR]=1608

Rx Int Threshold [RFTHR]=0, Frame Cnt [RFCNT]=62102

User-defined Address 0000/0000/0000/0000

User-defined Address Mask 0x0000

buffer size 1524

PowerQUICC SCC specific errors:

10 input aborts on receiving flag sequence

0 throttles, 0 enables

0 overruns

0 transmitter underruns

0 transmitter CTS losts

Could this be an issue where the circuit being provided is 56 kbps and not 64 kbps?

The local telco reports that the circuit test clean. The frame relay carrier does not see any errors. Only getting input errors on the remote site (site with 64 kbps circuit). Host site with T1s do not report any errors.

Any help would be appreciated!

sstudsdahl · ‎04-30-2004

What is the CIR for your circuit? You may have a 64K circuit but only has a CIR of 32K. You may be able to get the CIR by issuing the "show frame-relay map" command. Based upon the CIR, that may explain you ping failures if you are exceeding your CIR and the carrier is discarding frames due to congestion. You should be able to see if you are exceeding your CIR by looking at the output from the command "show frame-relay pvc". Pay attention to the "in DE pkts" and "out DE pkts" fields. If these counters increment, then your are going above what you are guaranteed through your CIR and will have traffic subject to discard during congestion periods on the frame-relay infrastructure.

dagates · ‎05-06-2004

The Frame Relay service is being provided by Sprint Link. They have no specified CIR. With CRC and Frame errors at the physical layer I do not think this is a CIR issue. I could be wrong. I am working with Sprint and the PTT to troubleshoot the issue.