Example

The following example shows configuration of frame-relay map payload-compression using the data compression AIM daughtercard for compression mapping the destination address 1.1.1.2 to DLCI 16:

Router(config-if)# frame-relay map ip 1.1.1.2 16 broadcast payload-compression 
                   frf9 stac caim 0
 

Related Commands

debug compress
encapsulation frame-relay
compress frame-relay
frame-relay payload-compress packet-by-packet
frame-relay interface-dlci

frame-relay payload-compression frf9 stac

To configure frame-relay payload-compression for each frame-relay port, enter the frame-relay payload-compression interface configuration command. Enter the no form of this command to terminate this form of payload-compression over frame relay.

Syntax Description

Default

Disabled

Command Mode

Interface configuration mode

Usage Guidelines

The frame-relay payload-compress command first appeared in Cisco IOS Release 11.0. The packet-by-packet keyword first appeared in Cisco IOS Release 11.2. The frf9 stac keyword first appeared in Cisco IOS Release 11.3. The frame-relay payload-compression frf9 stac caim command first appeared in Cisco IOS Release 12.0(2)T.

Use the frame-relay payload-compress command to enable or disable payload compression on a point-to-point interface or subinterface. Use the frame-relay map command to enable or disable payload compression on a multipoint interface or subinterface.

Example

The following example shows configuration of frame-relay payload-compression using the data compression AIM daughtercard for compression:

Router(config-if)# frame-relay payload-compression frf9 stac caim 0
 

Using this command, frame relay has been configured to use payload-compression with the frf9 stac algorithm for CAIM hardware compression using the installed data compression Advanced Interface Module (AIM) as the source.

Related Commands

debug compress
encapsulation frame-relay
compress frame-relay
show compress
frame-relay interface-dlci

show pci aim

To show the IDPROM contents for each AIM board in the Cisco 2600, enter the show pic aim global configuration command.

Syntax Description

There are no optional or required keywords or variables for this command.

Default

Disabled

Command Mode

Global configuration mode

Usage Guidelines

This command first appeared in Cisco IOS Release 12.0(1)T.

This command shows the IDPROM contents for each AIM board present in the system, by AIM slot number (currently 0, since that is the only daughter board installed for version 12.0(1)T). The IDPROM is a small PROM built into the AIM board used to identify it to the system. It is sometimes referred to as an EEPROM because it is implemented using electrically erasable PROM.

Example

The following example shows the IDPROM output for the installed AIM daughtercard:

Router# show pic aim 0
AIM Slot 0: ID 0x012D
        Hardware Revision        : 1.0
        EEPROM format version 4
        EEPROM contents (hex):
          0x00: 04 FF 40 01 2D 41 01 00 FF FF FF FF FF FF FF FF
          0x10: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
          0x20: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
          0x30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
          0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
          0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
          0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
          0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

Related Commands

test aim eeprom
clear aim

show pas caim

To show debug information about data compression Advanced Interface Module (AIM) daughter-card, enter the show pas caim global configuration command.

Syntax Description

Default

Disabled

Command Mode

Global configuration mode

Usage Guidelines

This command first appeared in Cisco IOS Release 12.0(2)T.

This command displays performance statistics describing the operation of the CAIM. This command is primarily intended for engineering debug, but it can also be useful to Cisco support personnel and to Cisco customers in troubleshooting network problems. The output of this command consists of a number of fields as follows:

Value	Description
uncomp paks in	Number of packets containing uncompressed data input to the CAIME for compression.
comp paks out	Number of packets containing uncompressed data which were successfully compressed.
comp paks in	Number of packets containing compressed data input to the CAIM for compression.
uncomp paks out	Number of packets containing compressed data which were successfully decompressed.
uncomp bytes in / comp bytes out	Summarizes the compression performance of the CAIM. The "uncomp bytes in" statistic gives the total number of uncompressed bytes submitted to the CAIM for compression. The "Comp bytes out" statistic gives the resulting number of compressed bytes output by the CAIM. If one forms the ratio of "uncomp bytes in" to "comp bytes out", one obtains the average compression ratio achieved by the CAIM.
comp bytes in / uncomp bytes out	Summarizes the decompression performance of the CAIM. The "comp bytes in" statistic gives the total number of compressed bytes submitted to the CAIM for decompression. The "uncomp bytes out" statistic gives the resulting number of uncompressed bytes output by the CAIM. The average decompression ratio achieved can be computed as the ratio of "uncomp bytes out" to "comp bytes in". Note that each packet submitted for compression or decompression has a small header at the front which is always clear data and hence never compressed nor decompressed. The "comp bytes in / uncomp bytes out" and "uncomp bytes in / comp bytes out" statistics do not include this header.
uncomp paks/sec in	A time average of the number of packets per second containing uncompressed data submitted as input to the CAIM for compression. It is computed as the ratio of the "uncomp paks in" statistic to the "seconds since last clear" statistic.
comp paks/sec out	A time average of the number of packets per second containing uncompressed data which were successfully compressed by the CAIM. It is computed as the ratio of the "comp paks out" statistic to the "seconds since last clear" compressed by the CAIM. It is computed as the ratio of the "comp paks out" statistic to the "seconds since last clear" statistic.
comp paks/sec in	A time average of the number of packets per second containing compressed data submitted as input to the CAIM for decompression. It is computed as the ratio of the "comp paks in" statistic to the "seconds since last clear" statistic.
uncomp paks/sec out	A time average of the number of packets per second containing compressed data which were successfully decompressed by the CAIM. It is computed as the ratio of the "uncomp paks out" statistic to the "seconds since last clear" statistic. Note that the "uncomp paks/sec in", "comp paks/sec out", "comp paks/sec in", and "uncomp paks/sec out" statistics are averages over the entire time since the last "clear count" command was issued. This means that as time progresses, these statistics become averages over an ever larger time interval. As time progresses, these statistics become ever less sensitive to current prevailing conditions. Note also that the "uncomp paks in", "comp paks out", "comp paks in", and "uncomp paks out" statistics are 32-bit counters and can roll over from 0xffff ffff to 0. When they do so, the "uncomp paks/sec in", "comp paks/sec out", "comp paks/sec in", and "uncomp paks/sec out" statistics can be rendered meaningless. It is therefore recommend that one issue a "clear count" command before sampling these statistics.
uncomp bits/sec in	A time average of the number of bits per second of uncompressed data which were submitted to the CAIM for compression. It is computed as the ratio of the "uncomp bytes in" statistic, times 8, to the "seconds since last clear" statistic.
comp bits/sec out	A time average of the number of bits per second of uncompressed data which were successfully compressed by the CAIM. It is computed as the raio of the "comp bytes out" statistic, times 8, to the "seconds since last clear" statistic.
comp bits/sec in	A time average of the number of bits per second of compressed data which were submitted to the CAIM for decompression. It is computed as the ratio of the "comp bytes in" statistic, times 8, to the "seconds since last clear" statistic.
uncomp bits/sec out	A time average of the number of bits per second of compressed data which were successfully decompressed by the CAIM. It is computed as the ratio of the "uncomp bytes in" statistic, times 8, to the "seconds since last clear" statistic. Note again that these "bits/sec" statistics are time averages over the "seconds since last clear" statistics, and therefore become less and less sensitive to current conditions as time progresses. Also, these "bits/sec" statistics are computed from 32-bit counters, and when the counters roll over from the maximum 32-bit value to 0, the "bits/sec" statistics become inaccurate. It is again recommended that one issue the "clear count" command before sampling the "bits/sec" statistics.
The remaining statistics summarize operational state and error conditions encountered by the CAIM, and have the following interpretations:
holdq	gives the number of packets occupying the "hold queue" of the CAIM. The hold queue is a holding area, or "overflow" area, for packets to be processed by the CAIM. Normally, the CAIM is fast enough that no overflow into the hold queue occurs, and so normally this statistic should show zero.
hw_enable	This a flag indicating if the CAIM is disabled or not. Zero implies disabled, one implies enabled. The CAIM can become disabled if certain fatal hardware error conditions are detected. It can be re-enabled by issuing the "clear aim <aim-slot>" command.
src_limited	This is a flag indicating if the CAIM is in "source limited" mode. In source limited mode, the CAIM can only process a single command at a time. In non source limited mode, the CAIM can process several commands at a time using a pipeline built into the 9711 coprocessor. Note that the normal mode of operation is "non-source limited", and there is no command to place the CAIM in "source limited" mode. Hence, this statistic should always read zero.
num cnxts	This statistics gives the number of "contexts" which are currently open on the CAIM. Each interface configured for compression opens two contexts, one for each direction of data transfer.
no data	This statistic counts the number of times in which the CAIM performed either a compress or decompression operation, and the output data length was reported with a length of zero. In normal operation, this statistic should always read zero. A non-zero value is an indication of a malfunctioning CAIM.
drops	This statistic counts the total number of times in which the CAIM was forced to drop a packet it was asked to compress or decompress. This can happen for a number of reasons, and the remaining statistics summarize these reasons. This statistic indicates that the CAIM is being overloaded with requests for compression/decompression.
nobuffers	This statistic counts the total number of times the CAIM needed to allocate memory for buffers but could not obtain memory. The CAIM allocates memory for buffers for holding the results of compression or decompression operations. In normal operation, there is plenty of memory available for holding CAIM results. This statistic, if non-zero, indicates that there is a significant backup in memory, or perhaps a memory leak.
enc adj errs	Each packet compressed or decompressed involves an adjustment of the encapsulation of the packet between the LZS-DCP, FRF9, or MPPC encapsulation used to transport compressed packets to the standard encapsulation used to transport clear data. This statistic counts the number of times this encapsulation adjustment failed. In normal operation, this statistic should be zero. A non-zero value indicates that we are short in a specific memory resource referred to as "paktypes", and that packets are being dropped due to this shortage.
fallbacks	Number of times the data compression AIM card could not use its pre-allocated buffers to store compression results and had to "fallback" to using a common buffer pool.
no replace	Each time a compression or decompression operation is completed and the resultant data fill up a buffer, the CAIM software allocates a new buffer to replace the buffer filled. If no buffers are available, then the packet involved in this operation is dropped and the old buffer reused. This statistic thus represents the number of times such an allocation failure occurred. In normal operation there is plenty of memory available for these buffers. A non-zero value for this statistic is thus a serious indication of a memory leak or other backup in buffer usage somewhere in the system. num seq errs - This statistic is incremented when the CAIM produces results in a different order than that in which the requests were submitted. Packets involved in such errors are dropped. A non-zero value in this statistic indicates a serious malfunction in the CAIM.
num desc errs	This statistic is incremented when the CAIM reports error in a compression or decompression operation. Such errors are most likely bus errors, and they indicate a serious malfunction in the CAIM.
cmds complete	This statistic reports the number of compression/decompression commands completed. This statistic should steadily increase in normal operation (assuming that the CAIM is continuously being asked to perform compression or decompression). If this statistic is not steadily increasing or decreasing when a steady stream of compression/decompression is expected, then this is an indication of a malfunctioning CAIM.
bad reqs	This statistic reports the number of compression/decompression requests that the CAIM software determined it could not possibly handle. This occurs only if a severely scattered packet (with more than 64 "particles", or separate buffers of data) is handed to the CAIM to compress or decompress. This statistic should not increment during normal operation. A non-zero value indicates a software bug.
dead cntxts	The number of times a packet was successfully compressed or decompressed, only to find that the software "context", or stream sourcing the packet, was no longer around. In such a case the packet is dropped. This statistic can be incremented at times when a serial interface is administratively disabled. If the timing is right, the CAIM may be right in the middle of operating on a packet from that interface when the disable takes effect. When the CAIM operation completes, it finds that the interface has been disabled and all "compression contexts" pertaining to that interface have been deleted. Another situation in which this can occur is when a Frame Relay DLC goes down. This is a normal and tolerable. If this statistic is incrementing when no such situations exist, it is an indication of a software bug.
no paks	If a packet to be compressed or decompressed overflows into the hold queue, then it must undergo an operation called "reparenting". This involves the allocation of a "paktype" structure for the packet. If no paktype structures are available, then the packet is dropped and this statistic is incremented. A non-zero value of this statistic indicates that the CAIM is being overtaxed, i.e, it's being asked to compress/decompress at a rate exceeding its capabilities.
enq errors	This statistic is closely related to the "no paks" statistic. The hold queue for the CAIM is limited in length, and if the hold queue grows to this length, no further packets may be placed on it. A non-zero value of this statistic therefore also indicates that the CAIM is being overtaxed.
rx pkt drops	This statistic contains the total number of packets dropped due to "no paks" or "enq errors", which were destined to be decompressed.
tx pkt drops	This statistic contains the total number of packets dropped due to "no paks" or "enq errors", which were destined to be compressed
dequeues	This statistic indicates the total number of packets which were removed from the CAIM hold queue when the CAIM became available for servicing its hold queue.
requeues	This statistic indicates the total number of packets which were removed from the hold queue, only to find that the necessary CAIM resources were not available (it is not possible to determine whether CAIM resources are available until the packet is dequeued). Such packets are requeued onto the hold queue, with order in the queue preserved.
drops disabled	This statistic indicates the total number of packets which were submitted for compression or decompression, but which were dropped because the CAIM was disabled.
clears	This statistic indicates the number of times the CAIM was reset using the "clear aim <aim-slot>" command.
# ints	This statistic indicates the number of interrupts serviced by the CAIM software. This statistic should steadily increase (assuming the CAIM workload is steady). If this statistic is not incremented when expected, it indicates a severe CAIM malfunction.
# purges	This statistic indicates the total number of times the compression history for a session had to be purged. This statistic is incremented a couple of times at startup. Thereafter, any increase in this statistic is an indication that the other side of the serial link detected bad data or gaps in the compressed packets being passed to it, and hence signalled a request to purge compression history in order to get back in synchronization. This can indicate that the CAIM is being overtaxed, or that the serial interface is overtaxed and being forced to drop output packets.
no cnxts	This statistic indicates the total number of times a request was issued to open a context, but the CAIM could not support any more contexts. Recall that two contexts are required for each interface configured for compression. bad algos - This statistic indicates the total number of times a request was issued to open a context for a compression algorithm not supported by the CAIM. Recall that the CAIM supports the LZS and MPPC algorithms only.
no crams	This statistic indicates the total number of times a request was issued to open a context but there was insufficient compression DRAM to open another context. The CAIM software is set up to run out of contexts before it runs out of compression DRAM, so this statistic should always be zero.
bad paks	This statistic indicates the total number of times a packet was submitted for compression or decompression to the CAIM, but the packet had an invalid size.
# opens	Indicates the total number of times a context was opened.
# closes	Indicates the total number of times a context was closed.
# hangs	Indicates the total number of times a CAIM appeared hung up, necessitating a clear of the CAIM.

The show pas caim rings element-number form of this command displays the current state of the DMA ring buffers maintained by the CAIM software. These rings feed the CAIM with data and commands. It is intended for Engineering debug of the compression AIM. It produces the following output:

CAIM Command Ring: 0x01A2BC00  Stack: 0x01A2BE40  Shadow: 0x80F88BAC
 Head: 0021  Tail: 0021  Count: 0000
CAIM Source Ring:  0x01A2C900  Shadow: 0x80F88BAC
 Head: 0021  Tail: 0021  Num: 0000
CAIM Results Ring: 0x01A2C280  Stack: 0x01A2C4C0
 Head=021  Tail=021
CAIM Dest Ring:    0x01A2CB40  Shadow: 0x80F892D8  Head=021  Tail=000
  Desc: 0x01A2CBE8  flags: 0x8000060C  dptr: 0x019E7EB8  part: 0x80F84BE0
  Desc: 0x01A2CBF0  flags: 0x8000060C  dptr: 0x019FC63C  part: 0x80F85240
----cut----
 

The CAIM Command Ring feeds commands to the CAIM. The Address of the command ring is displayed first. The Stack is a ring which feeds additional commands to the CAIM, and its address is displayed next. The Shadow is a software ring which stores additional information about each command. The Head field is an index into the Source Ring, specifying where the next entry will be extracted from. The Tail field is an index into the Source Ring which specifies where the next entry will be inserted. Refer to the Jupiter DMA specification and the Hifn 9711 Data Sheet for more information.

The CAIM Source Ring feeds information about input data to the CAIM. The address of the Source Ring is displayed first. The Source Ring Shadow is a ring which contains additional information about each source buffer. The Head field specifies where the next entry will be extracted, and the Tail field specifies where the next entry will be inserted. Refer to the Jupiter DMA specification and the Hifn 9711 Data Sheet for more information.

The CAIM Results Ring receives information about each CAIM command as it is completed. The address of the ring is displayed first. The Stack is a ring which receives additional information about each completed command, and its address is next displayed. The Head field specifies where the next entry will be extracted, and the Tail field specifies where the next entry will be inserted. Refer to the Jupiter DMA specification and the Hifn 9711 Data Sheet for more information.

The CAIM Dest Ring holds information about the buffers available to the CAIM for output data. The address of the Dest Ring is displayed first. The Dest Shadow is a ring which holds additional information about each output buffer. The Head field specifies where the next entry will be extracted, and the Tail field specifies where the next entry will be inserted. Refer to the Jupiter DMA specification and the hifn 9711 Data Sheet for more information.

There now follows a line of information about each output data buffer. The desc field is the address of a so-called descriptor, used by the Jupiter DMA engine. The flags field contains flags describing attributes of the buffer. The dptr field displays the actual address of the output buffer. The part field displays the address of the corresponding particletype structure, a software defined structure which describes a buffer when its a component of a network data buffer. Refer to the Jupiter DMA specification and the hifn 9711 Data Sheet for more information.

The show pas caim dma element-number form of this command displays the registers of the Jupiter DMA Controller. These registers control the operation of the Jupiter DMA Controller. This command is intended for Engineering debug of the CAIM. Detailed descriptions of the various fields may be found in the Jupiter DMA Controller specification. The output of this command consists of:

Jupiter DMA Controller Registers: (0x40200000
        Cmd Ring: 0x01A2BCA8  Src Ring: 0x01A2C9A8
        Res Ring: 0x01A2C328  Dst Ring: 0x01A2CBE8
        Status/Cntl: present: 0x80808084  last int: 0x80808084
        Inten: 0x10100000  config: 0x00100003
        Num DMA ints: 143330469
 

The show pas caim compressor element-number form of this command displays the registers of the Hifn 9711 compression coprocessor. These registers control the operation of the Hifn 9711 part. This command is intended for Engineering debug of the CAIM. Detailed descriptions of the various fields may be found in the Hifn 9711 data book. The output of this command consists of:

Hifn9711 Data Compression Coprocessor Registers (0x40201000):
        Config: 0x000051D4  Inten: 0x00000E00
        Status: 0x00004000  FIFO status: 0x00004000
        FIFO config: 0x00000101
 

The address of the registers in the address space of the processor is displayed first. The Config field displays the current contents of the 9711 configuration register. The Inten field displays the contents of the 9711 interrupt enable register. The Status field displays the contents of the 9711 status register. The FIFO status field displays the contents of the 9711 FIFO Status register.

The show pas caim cnxt_table element-number form of this command displays the context table for the specified CAIM element. The context is a table of information concerning each compression context. The display has the following appearance:

CAIM0 Context Table
Context: 0x8104F320  Type: Compr   Algo: Stac
    Hdrlen: 0006  History: 0x0000
    Callback: 0x8011D68C  Shutdown: x8011EBE4  Purge: N
    Comp_db: 0x81034BC0  idb: 0x81038084  ds: 0x8104E514
Context: 0x8104F340  Type: Decomp  Algo: Stac
    Hdrlen: 0002  History: 0x0000
    Callback: 0x8011E700  Shutdown: x8011EBE4  Purge: N
    Comp_db: 0x81034BC0  idb: 0x81038084  ds: 0x8104E514
 

The Context field is a numeric internal reference for the compression context. The Type field gives the type of context, either "Compr" for a compression context or "Decomp" for a decompression context. The Algo field gives the compression algorithm used, either "Stac" or "Mppc". The Hdrlen field gives the number of bytes in the compression header for each compressed packet. The History field gives the 16 Kbyte page number in compression RAM for the context. The Callback, Shutdown, Comp_db, idb, and ds fields give internal numeric references for various control structures and procedures to facilitate debugging. The Purge field indicates whether the compression context has been flagged to have its history purged.

The show pas caim page_table element-number form of this command displays the page table for the selected CAIM element. The page table is a table of entries describing each page in compression RAM. The display appears as follows:

CAIM0 Page Table
    Page  0x0000 Comp cnxt: 8104F320  Decmp cnxt: 8104F340  Algo: Stac

The Page field is the 16 Kbyte page number of the page. The Comp cnxt and Decmp cnxt fields contain internal numeric references to the context structures using this page. The Algo field gives the compression algorithm used, either "Stac" or "Mppc".

Example

The following example shows stats of an active data compression AIM session:

Router# show pas caim stats 0
 
CompressionAim0
    ds:0x80F56A44 idb:0x80F50DB8
        422074 uncomp paks in -->       422076 comp paks out
        422071 comp paks in   -->       422075 uncomp paks out
     633912308 uncomp bytes in-->     22791798 comp bytes out
      27433911 comp bytes in  -->    633911762 uncomp bytes out
           974 uncomp paks/sec in-->       974 comp paks/sec out
           974 comp paks/sec in  -->       974 uncomp paks/sec out
      11739116 uncomp bits/sec in-->    422070 comp bits/sec out
        508035 comp bits/sec in  -->  11739106 uncomp bits/sec out
    433 seconds since last clear
    holdq: 0  hw_enable: 1  src_limited: 0  num cnxts: 4
    no data: 0  drops: 0  nobuffers: 0  enc adj errs: 0  fallbacks: 0
    no Replace: 0  num seq errs: 0  num desc errs: 0  cmds complete: 844151
    Bad reqs: 0  Dead cnxts: 0  No Paks: 0  enq errs: 0
    rx pkt drops: 0  tx pkt drops: 0  dequeues: 0  requeues: 0
    drops disabled: 0  clears: 0  ints: 844314  purges: 0
    no cnxts: 0  bad algos: 0  no crams: 0  bad paks: 0
    # opens: 0  # closes: 0 # hangs: 0
 

Related Commands

show compress
debug compress

test aim eeprom

To test the data compression Advanced Interface Module (AIM) after it is installed in your Cisco 2600, enter the test aim eeprom global configuration command. Using this command can erase all locations in EEPROM memory.

Syntax Description

There are no optional or required keywords or variables for this command.

Default

Disabled

Command Mode

Global configuration mode

Usage Guidelines

This command first appeared in Cisco IOS Release 12.0(2)T.

This command is the AIM counterpart of the "test pas eeprom" command which performs similar tasks for port modules. The following lines are displayed:

At any time you can use these commands:

Dump EEPROM Contents	This command results in the display of the contents of the EEPROM in hex.
Erase EEPROM	This command results in the erasure of the entire EEPROM (all bytes set to 0xff).
Primitive Access	This command allows you to erase the EEPROM.
Exit EEPROM Test	This command causes the "test aim eepromp" command dialog to exit back to the CLI.
Zero EEPROM	This command causes the entire EEPROM to be zeroed out.

During your session with the test dialog, you have access to the following commands:

Example

The following example displays the test aim eeprom command's user dialog

Router# test aim eeprom
 AIM Slot [0]: 0
 Use NMC93C46 ID EEPROM [y]: y
 AIM Slot 0 eeprom (? for help)[?]:  ?
  d - dump eeprom contents
  e - erase all locations (to 1)
  p - primitive access
  q - exit eeprom test
  z - zero eeprom
 
  'c' rules of radix type-in and display apply.
 
 AIM Slot 0 eeprom (? for help)[?]: 
 

Debug Commands

The following modified debug commands are provided for the data compression AIM:

• debug compress

debug compress

To debug compression, enter the debug compress global configuration command. To disable debugging output, use the no form of this command.

Syntax Description

There are no optional or required keywords or variables for this command.

Default

Disabled.

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

Use this command to display output from the compression and decompression configuration you made. Live traffic must be configured through the Cisco 2600 with a data compression Advanced Interface Module (AIM) installed for this command to work.

Sample Display

The following example is output from the debug compress command, which shows that compression is taking place on a Cisco  2600 Access Router using data compression Advanced Interface Module (AIM) hardware compression is configured correctly.

For a description of the debug output, see Table 1.

Router# debug compress
COMPRESS debugging is on
Router#compr-in:pak:0x810C6B10 npart:0 size:103
pak:0x810C6B10 start:0x02406BD4 size:103 npart:0
compr-out:pak:0x8118C8B8 stat:0x00000000 npart:1 size:71 lcb:0xED
pak:0x8118C8B8 start:0x0259CD3E size:71 npart:1
    mp:0x8118A980 start:0x0259CD3E size:71
 
decmp-in:pak:0x81128B78 start:0x0255AF44 size:42 npart:1 hdr:0xC035
pak:0x81128B78 start:0x0255AF44 size:42 npart:1
    mp:0x81174480 start:0x0255AF44 size:42
decmp-out:pak:0x8118C8B8 start:0x025B2C42 size:55 npart:1 stat:0
pak:0x8118C8B8 start:0x025B2C42 size:55 npart:1
    mp:0x8118B700 start:0x025B2C42 size:55
 

Table 1: Debug Compress Field Descriptions

Field	Description
compr-in	Indicates that a packet needs to be compressed.
compr-out	Indicates completion of compression of packet.
decmp-in	Indicates receipt of a compressed packet which needs to be decompressed.
decmp-out	Indicates completion of decompression of packet.
pak:0x810c6b10	Provides the address in memory of a software structure which describes the compressed packet.
start:0x02406bd4 size:103 npart:0	The 'npart:0' indicates that the packet is contained in a single, contiguous area of memory. The start address of the packet is0x02406bd4 and the size of the packet is 103.
start:0x0259cd3E size:71 npart:1	The npart:1 indicates that the packet is contained in 1 or more regions of memory. The start address of the packet is 0x0259cd3e and the size of the packet is 71.
mp:0x8118a980 start:0x0259cd3e size:71	Describes one of these regions of memory.
mp:0x8118a980	Provides the address of a structure describing this region.
start 0x0259cd3e	Provides the address of the start of this region.

Related Commands

debug frame-relay
debug ppp
show compress
show diag

What to Do Next

For additional software configuration information, see the following publications:

• Cisco IOS Command Reference Version 12.0 for the following commands:

  • frame-relay map ip compress command

  • frame-relay payload-compress command

  • frame-relay payload-compress packet-by-packet command

  • compress command

• data compression AIM Configuration Note

• Cisco IOS Interface Command Reference, Release 12.0
  http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/inter_r/index.htm

• Cisco 2600 Series Routers
  http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis2600/index.htm

  • Quick Start Guide Cisco 2600 Series Cabling and Setup

  • Cisco 2600 Series Hardware Installation Guide

  • Network Module Hardware Installation Guide

  • Update to Network Module Hardware and Software Guides

  • Cisco WAN Interface Cards Hardware Installation Guide

  • Update to WAN Interface Cards Hardware Installation Guide

  • Software Configuration Guide for Cisco 3600 and Cisco 2600 Series Routers

  • Cisco 2600 - Release Notes for Release 11.3 XA1

  • Cisco 2600 - Release Notes for Release 11.3(6)T

  • New and Changed Show Commands for the Cisco 2600 Series Routers

• How to download a Software Image to a Cisco 2600 via TFTP Using the tftpdnld
  ROMMON Command http://www.cisco.com/warp/public/471/76.html

• How to Download a Software Image to a Cisco 2600 via the Console Port Using the
  xmodem ROMMON Command http://www.cisco.com/warp/public/471/77.html

Posted: Thu May 25 16:26:12 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.