As Edwin explains there is not really a protocol of keepalive. Keepalive messages are generated on most router interfaces as a way to track the status of the interface. The basic logic is that the router should only forward traffic out an interface if it believes that the traffic will be successful through that interface. So the router attempts to identify interfaces that will not pass traffic by sending and receiving keepalive messages. If the keepalives fail the router marks the interface as protocol down and will not forward any traffic out that interface.
You may deploy your new network and disable keepalives if you decide that you want to do this. The result will be that all interfaces that are not administratively shut down and that have keepalive disabled will report themselves as up/up even if they are not capable of passing traffic. This creates the possibility of black holes in your network (you send traffic into them but nothing ever goes through - and there are no error messages about it).
Be aware that some interfaces (especially point to point serial interfaces) actually send keepalive packets and need to receive keepalive packets to maintain the interface. If you disable keepalive on one end but not on the other end, then the end that still is attempting to process keepalives will never receive a response and will declare itself up/down no matter whether the link is passing data traffic or not.
If it were me I would not disable keepalives on an interface unless I had a really good reason to want to do so.
1) Generally having non-Cisco equipment is not an issue for keepalives. On LAN media (Ethernet) no other device interacts with the keepalive. On WAN media if the device supports the protocol selected it will support the keepalive mechanism (whether it is HDLC or PPP or whatever).
2) Especially on HDLC links keepalives may be useful in detecting a looped condition. This is because within the HDLC keepalive there are sequence numbers (mineseen and yourseen). If the router sees packets being received with the same sequence numbers it can realize that it is seeing its own packets not packets from its neighbor.
3) In an Ethernet keepalive, if you look at the source MAC address you would see the address of the router - as you would expect. But if you look at the destination MAC address you would also see the router MAC address. So the source and destination are both the router. So the router is sending a message to itself.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...