This is a tracking issue for the remaining work that needs to be done to completely migrate our network configuration to RPWs.

Currently we are only handing post-Nexus NAT configuration with RPWs. We now need to ensure that pre-Nexus NAT information is managed via RPW. We also need to move all other network configuration items, pre- and post-Nexus, to RPWs.

The "novel" part of this project is that we will also need to determine how to perform synchronization of post-Nexus state to bootstore, meaning that we have some bi-directional synchronization occurring:

1. Cold boot process performs initial configuration
2. Initial configuration is passed to Nexus for recording in RPW tables
3. If any relevant changes happen after Nexus is up, that must be updated in the RPW tables and the bootstore

Currently, it seems that all service zone NAT uses VNI 100, so if we can be sure that is a long term design decision that will not change, we can use that (or a similar mechanism) to differentiate which NAT entries need to be recorded in the bootstore vs. which ones should wait for post-Nexus mechanism to kick in.

At the moment, it is my understanding that all link and BGP configuration will need to be persisted in both mechanisms.

TODO

• Pre-Nexus NAT should also be persisted via RPW
• Link / Port Configurations should be persisted via RPW
• BGP Configurations should be persisted via RPW

Related Issues

Closes #4650
Closes #3631