Disabling Next Hop or ARP Port Movement Syslog Message Generation
This may cause Flooding of the syslog server or
console with syslog messages may occur in certain deployments where next hop or ARP
port
movement occurs continuously. In such scenarios, the default behavior can be disabled
and
syslog messages can be prevented from being generated with every port movement for
ARP
entries using the no ip arp
port-move-syslog command.
The status of the next hop or ARP port movement
syslog message (enabled or disabled) can be viewed in the output of the show ip command.
The following example shows sample output of the
show ip command in which the status of the next hop or ARP port movement syslog message (enabled)
is displayed.
device(config)# show ip ttl: 64, arp-age: 10, bootp-relay-max-hops: 4 router-id : 10.1.1.1 enabled : BGP4 UDP-Broadcast-Forwarding Source-Route Load-Sharing RARP VSRP arp-port-move-syslog disabled: Route-Only Directed-Broadcast-Forwarding IRDP Proxy-ARP RIP OSPF VRRP VRRP-Extended ICMP-Redirect add-host-route-first device(config)# no ip arp port-move-syslog device(config)# show ip Global Settings ttl: 64, arp-age: 10, bootp-relay-max-hops: 4 router-id : 10.1.1.1 enabled : BGP4 UDP-Broadcast-Forwarding Source-Route Load-Sharing RARP VSRP disabled: Route-Only Directed-Broadcast-Forwarding IRDP Proxy-ARP RIP OSPF VRRP VRRP-Extended ICMP-Redirect add-host-route-first arp-port-move-syslog
The following example shows sample output of the
show ip command in which the status of the next hop or ARP port movement syslog message (disabled)
is displayed.
device(config)# no ip arp port-move-syslog device(config)# show ip Global Settings ttl: 64, arp-age: 10, bootp-relay-max-hops: 4 router-id : 10.1.1.1 enabled : BGP4 UDP-Broadcast-Forwarding Source-Route Load-Sharing RARP VSRP disabled: Route-Only Directed-Broadcast-Forwarding IRDP Proxy-ARP RIP OSPF VRRP VRRP-Extended ICMP-Redirect add-host-route-first arp-port-move-syslog