text: 1. This message occurs when a subaddress is configured. When this subaddress is combined with the X.121 address of the interface, the total address exceeds the limit of 15 characters.\n\n2. The X.25 configuration of the interface is not valid. The existing configuration was not changed.\n\n3. You have attempted an invalid configuration.\n\n4. A virtual circuit has been set up using the default maximum packet sizes, but the data terminal equipment (DTE) and data communications equipment (DCE) are not configured with the same default values. A packet was received that had the M-bit set, signifying that more data follows, but the packet did not carry the maximum number of bytes allowed. Such partial data packets must have the M-bit cleared. The resulting loss of a message boundary might cause problems for the data recipient.\n\n5. An internal software error has occurred.\n\n6. A stacker compression algorithm internal error or a shortage of buffer space was encountered during a compression operation.\n\nNote: This error should never happen.\n\n7. An internal software error has occurred.\n\n8. You have used an invalid configuration ID.\n\n9. The default packet sizes or outgoing packet size facility values of the interface are too large to be carried by Link Access Procedure, Balanced (LAPB). The router will negotiate lower packet size values automatically.\n\n10. A decompression buffer was not available for an incoming compressed packet. This message is a warning only (the compressed packet was not lost). However, an X.25 packet layer RNR (wait) was generated, and packet-level transmission on the logical channel number (LCN) will not resume (RR issued) until a decompression buffer becomes available.\n\n11. An incoming X.25 call specified a protocol that was assigned to a multiprotocol map; the virtual circuit (VC) will not be able to carry the full set of protocols specified by the map.\n\n12. Compression is not enabled because D-bit support is configured for the local channel identifier (LCI).\n\n13. An X.25 interface has been configured to use an X.25 profile that does not exist.\n\n14. You have used an outdated method to specify a virtual circuit range. (An outgoing-only or incoming-only virtual circuit range exactly overlaps the two-way virtual circuit range.)\n\n15. An internal software error has occurred. The PBP header has an uncompressed packet size field. Each uncompressed packet size is checked against this field.