Configuration Of Ip Binding - UTStarcom iSpirit 3026 Manual

can visit Internet through Port B. Refer to Figure 1 suppose that port 1 is bound with IP Add of
192.168.0.100 but port 2 is not bound with IP Add., user 1 can visit the Internet through port 2.
The switch realizes the IP Add. binding through FFP of the port, which will not influence the
forwarding efficiency of data flow of the IP Add. the data flow can be speed fordwarded. For
there is limited volume of FFP, IP Add to be bound is limited accordingly. One port can be only
bound with 127 IP Add max. but if FFP is applied by others, the IP Add is even less.
IP Binding is exclusive against ACLfiltration and Untrust port of QoS. The port cannot be bound
if it has been carries out with Acl filtration. Also the port cannot be bound if it is Untrust port of
QoS.
IP binding available but without 127 IP Add. indicates that FFP resource is applied by others,
which maybe trust port of QoS, IGMP SNOOPING protocol and 802.1x protocol.

10.2 Configuration of IP Binding

iSpirit 3026 switch only supports manual binding with IP Add, i.e. one port bound with one or
more IP Add are all input by manual work.
Under iSpirit 3026 Switch default condition no port is bound with IP Add.
ip bind <port> <ip-address>
Following command under global CONFIG mode one port is bound with IP Add., this command
(ip bind <port> <ip-address>) should be repeated if one port needs to be bound with more Add.
Notes:
If this port was not bound with IP Add before this command is input, maybe caused by:
1. This port has been carried out with ACL filtration
2. The port has been the Untrust port of QoS
If this port was bound with IP Add before this command is input, maybe caused by:
1. The IP address has been bound with this port
2. FFP resource is not enough maybe the port is the trust port of QoS or/and IGMP
SNOOPING protocol has started or/and this port is under Auot mode of 802.1x.