Error Messages

Chapter 1: Layer 3 Access Control List (ACL) Error Messages
%ACL-E-HSTFLOWMODE Interface ’%s’ has a port in Host Flow Mode.
Explanation:
The user is trying to attach an ACL to an interface which has one or more ports in Host Flow based
routing mode. An inbound ACL cannot be applied to such interfaces because the ACL may have
Source Port or Destination Port fields in its parameters.
Recommended Action:
Either the ports associated with the interface should not be in Host Flow based mode or the ACL
should only contain Destination IP address and Source IP address in its parameters.
%ACL-E-HSTFLOWSERVICEACL Service ACL has incompatible rules
for Host Flow based routing.
Explanation:
The user is trying to change the port mode to Host Flow based, where there is a service ACL in the
system. A service ACL requires that all ports not be in either Destination or Host Flow based
modes because a service ACL requires to compare the Destination Port number in the packet and a
port in Destination flow mode would produce a flow block with only the Destination and Source IP
addresses.
Recommended Action:
Cannot change port mode to Host Flow based mode if a service ACL is present in the system. The
ACL could be detached from the services if the port needs to be in Host Flow based mode.
%ACL-E-HWNOTSFR Slot %d of interface '%s' is not SFR compliant.
Explanation:
An ACL created with the 'tcp established' option will check for a sin/fin/reset bit (SFR) in TCP
packets without an accompanying ACK bit and send any such packets to the CPU for processing.
This helps prevent against SYN attacks.
Recommended Action:
This functionality exists only in the SIPP (i.e., T-series cards)—the XP does not allow the use of an
established ACL with a module that uses an IPP.
6 Enterasys X-Pedition Error Reference Manual