4 rip troubleshooting, Roubleshooting – PLANET XGS3-24040 User Manual
Page 266

Chapter 35 RIP
35-11
As the above network topology, S2 is connected to S1 through interface vlan1, there are other 4 subnet
routers of S2, which are 192.168.21.0/24, 192.168.22.0/24, 192.168.23.0/24, 192.168.24.0/24. S2 supports
route aggregation, and to configure aggregation route 192.168.20.0/22 in interface vlan1 of S2, after that,
sending router messages to S1 through vlan1, and put the four subnet routers aggregated to one router as
192.168.20.0/22, and send to S1, and not send subnet to neighbor. It can reduce the router table of S1, save
the memory.
S1 configuration list:
S1(config)#router rip
S1(config-router) #network vlan 1
S2 configuration list:
S2(config)#router rip
S2(config-router) #network vlan 1
S2(config-router) #exit
S2(config)#in vlan 1
S2(Config-if-Vlan1)# ip rip agg 192.168.20.0/22
35.4 RIP Troubleshooting
The RIP protocol may not be working properly due to errors such as physical connection, configuration error
when configuring and using the RIP protocol. So users should pay attention to following:
Enabling dot1q-tunnel on Trunk port will make the tag of the data packet unpredictable which is not
required in the application. So it is not recommended to enable dot1q-tunnel on Trunk port except the
VLAN-translation is in operation .
Configuring in port-channel is not supported.
Enabled with STP/MSTP is not supported.
Enabled with PVLAN is not supported.
If MAC address binding cannot be enabled for a port, make sure the port is not enabling port
aggregation and is not configured as a Trunk port. MAC address binding is exclusive to such
configurations. If MAC address binding is to be enabled, the functions mentioned above must be
disabled first.
If a secure address is set as static address and deleted, that secure address will be unusable even
though it exists. For this reason, it is recommended to avoid static address for ports enabling MAC
address.
DHCP option 82 is implemented as a sub-function module of DHCP Relay Agent. Before using it, users
should make sure that the DHCP Relay Agent is configured correctly.
DHCP option 82 needs the DHCP Relay Agent and the DHCP server cooperate to finish the task of
allocating IP addresses. The DHCP server should set allocating policy correctly depending on the
network topology of the DHCP Relay Agent, or, even the Relay Agent can operate normally, the
allocation of addresses will fail. When there is more than one kind of Relay Agent, please pay attention
to the retransmitting policy of the interface DHCP request messages.
To implement the option 82 function of DHCP Relay Agent, the “debug dhcp relay packet” command