Configuration Guide GSN Configuration
Precautions for GSN Configuration
Supported GSN Entry Number
Since the implementation of the GSN policy installation is by the hardware filtering, the
supported policy numbers are different for different product chips. Besides, for the
reason that the hardware entry resources used by GSN may be occupied by other
modules, enabling the relevant functions(for example, anti-arp-spoofing, ect) also
reduces the available entry number, and so does the GSN-supported entry number. To
support more dynamic policies and enhance the GSN control capability, it is
recommended not to enable other functions consuming the hardware entry when
enabling GSN.
Some Functions Conflicted with GSN
Due to the GSN application features, GSN conflicts with the following functions:
1) GSN can not be co-used with 802.1x IP authorization;
2) GSN can not be co-used with port security;
3) GSN does not support the policy installation on the AP port, and the port with
policy installed can not join in the AP port. The installed policy on the
corresponding port shall be removed before adding a port with GSN policy
installed to the AP port,
Other Precautions
The following configurations may influence the GSN usage because the hardware
filtering is used to implement the GSN configuration:
IP+MAC binding globally: after configuring a global IP+MAC binding, a MAC user
is released, and the MAC user isolation by the GSN may be invalid.
ACL：the conflict of the ACL entry content and assigned GSN policy also leads to the
GSN invalidness. It is recommended not to enable ACL when enabling GSN.
To Next Page
Loading...
