maintain fixed IPv4-Adresses during Node-Splits |

You are here

maintain fixed IPv4-Adresses during Node-Splits

3 posts / 0 new
Last post
maintain fixed IPv4-Adresses during Node-Splits

Hello everybody,

current practice when doing node-splits (involving moving a cluster/node to another CMTS) is to call all affected customers with fixed public ipv4 addresses and inform them that their fixed public IPv4 address will change on a certain date.

I want to try to avoid this.
I am willing to accept a complex configuration and maybe routing /32 ipv4-prefixes through our backbone for business customers.

Currently we use ubr10k CMTS.
All routing is done using routing protocols. Sometimes static routing is used.
All fixed public IPv4-Adresses are being leased by our DHCP server.

Has anyone accomplished this?

It's possible but tricky

Hi, it's possible. Is a hell of scripting. The entry point is the CM On Off Trap/Inform message, which you can configure at the CMTS.
So the idea is that your backend is receiving the Off and On Events of the particular cable modem. If your cable modem has switched to another CMTS the backend will receive the On Event of this particular cable modem from the other source address, e.g. loopback0 or 1 (whatever you'd configured). So the systems know on which different CMTS the cable modem has come online now. Then the backend goes to the last known CMTS and deconfigure the /30 or /32 in the IP-Bundle interface and configure the same /30 or /32 on the new CMTS IP-Bundle interface. Of course your DHCP configuration has to be adapted, too.
If you don't want to use DHCP for fixed IP you can also use Source Address Verification (SAV) with the TLV (IPv4) or (IPv6). This gives you the chance for static IP configuration without disable DHCP-Authorization.

This is just to give you an idea. There are other ways possibe for sure but this is my example.

Best regards,

Yes it is a major pain

Yes it is a major pain

Many times I have wished our customer base was dynamic-ip only

Instead of moving half the split node to another CMTS, do you have any dynamic-ip only nodes that can be moved instead?