Rollback from CPN-UPN Communication Solution to Standalone UPN
This section provides the steps to rollback from CPN-UPN Communication Solution to Standalone UPN and also clean up the configurations performed for the CPN-UPN Communication solution. If the CPN-UPN Communication fails due to some issues, you can roll back to the previous Standalone UPN Solution.
Follow the steps given below to roll back to Standalone UPN:
|
Step No |
Task |
Refer the following topics |
|---|---|---|
|
1. |
Remove CPN specific second level maps |
|
|
2. |
Remove vports configured for CPN |
|
|
3. |
Delete the first level maps configured for gpfcp messages
|
|
|
4. |
Delete other CPN specific first level maps |
|
|
5. |
Delete gsops attached to the CPN engine |
|
|
6. |
Delete IP interfaces for CPN UPN communication |
|
|
7 |
Delete the CPN gsgroup |
|
|
8 |
Remove gpfcp profile from UPN gsparams |
|
|
9 |
Remove the exporter configurations for both the CPN and UPN |
|
|
10 |
Delete all the configured gpfcp profiles |
|
|
11 |
Remove RAN and Network Slicing rules from UPN specific second level maps |
