Why Isn't There a Compression Tunnel?

If the Tunnel Status in the setup compression show output indicates that the Tunnel is not up for a specific host or partner, you can use the setup compression show <ip-addr> command to get further information on why the tunnel couldn't be created.

  1. Issue the setup compression show <ip-addr> command, where <ip-addr> is the IP address of the host or partner that lists a Tunnel Status of Tunnel is not up. For example:

    setup comp show 172.21.24.11

    IP Address: 172.21.24.11 OUTSIDE
    Compression Type: Shaper
    Tunnel Status: Tunnel is not up.
    Compression Status: Disabled because shaper is not in allowed partner list.

  2. Look at the Compression Status field and look up the message in the table below.
Message Description
Disabled because compression is off. The data from the specified host will not be compressed because the compression feature has been turned off on the active PacketShaper. Use the setup compression on command to enable compression.

Disabled because shaper is not in allowed partner list.

or

Disabled because shaper x.x.x.x is not in allowed partner list.

 The data from the specified host will not be compressed because the tunnel partner has not been configured to use the compression facility. To see which partners (that is, PacketShaper Xpress units) have been configured to use compression, type setup compression show hosts. To add a PacketShaper Xpress unit to the list of allowed partners, use the setup compression partners command.
Disabled because host is not in list of allowed hosts. The data from the specified host will not be compressed because it is not configured to use the compression facility. To see which hosts have been configured to use compression, type setup compression show hosts. To add a host to the list of allowed hosts, use the setup compression hosts command.
Disabled because host appears to be on both sides. There might be a loop in the network so the host appears on both sides. Alternatively, this message could mean that the host is trying to be an initiator and recipient at the same time, a situation that is not allowed. Resetting the unit should resolve this problem.
Process started, probe sent __ ago, no answer, resend in __. A probe packet was sent to look for a tunnel partner, but a PacketShaper Xpress unit did not reply; another probe will be sent in the specified number of seconds/minutes.
Compression was restarted, can probe now. Compression was turned off and then turned back on and there currently aren't any flows going through PacketShaper Xpress; a probe will be sent to look for a tunnel partner.
Host can probe now. The host has been identified, but a probe packet has not yet been sent to see if a tunnel partner exists.
Probe sent __ ago, can probe now. A probe packet was sent, but a tunnel partner did not reply; another probe will be sent. If you want to force a probe, use the setup compression reprobe command.


        

PacketGuide™ for PacketWise® 7.5