Skip to main content
Evening peak brings the CGNAT aggregator at the Wellington POP to 98 percent port-pool utilization. The ISP needs to expand the pool, tune per-subscriber port budgets, keep the abuse-contact registrations current so spam and law-enforcement lookups still work, and document the new IP plan in NetBox. Build the response around restoring subscriber service and confirming the capacity margin. An agent can assemble the incident evidence, coordinate engineering approval, track the authorized change, and prepare the customer and operations updates. The device actions below belong to the configured execution path or an engineer’s task in the support loop.

​
Systems involved

​
Technical playbook

1

Confirm the capacity problem

Copilot pulls port-pool utilization from the CGNAT platform for the last 14 days. Peak hours hit 98 percent; the distribution of per-subscriber port use is long-tailed — a small number of subscribers drive most of the consumption.
2

Plan the expansion

Add a /23 of public IPv4 to the pool. Recalculate ports-per-subscriber with the new capacity and the current subscriber count. Stage a mild reduction of the per-subscriber hard cap so the long-tail subscribers are not disproportionate.
3

Stage the CGNAT config

SSH into the CGNAT platform. Copilot drafts the configuration to add the new pool range and the new per-subscriber budget, stages it in the staging panel, and shows the expected effect on pool utilization.
4

Announce the new /23 via BGP

On the edge routers, announce the new /23. Verify the advertisement appears in the looking glass and that the ISP’s RPKI ROAs are updated so the prefix is valid.
5

Push the pool change

During the low-traffic window, push the CGNAT config. Monitor for session churn; most sessions continue because the new pool is additive. Only the subscriber-budget change causes a gentle re-NAT cycle.
6

Update IPAM

Update NetBox with the new /23 role, the pool ID, the ASN assignment, and the abuse contact. The IP plan artifact is regenerated and saved to the team drive.
7

Refresh abuse registrations

Through the RIR connectors, update the abuse-contact record for the new /23 so that subpoena requests and spam investigations route to the right ISP team. Draft the inter-carrier courtesy note through Gmail to major abuse partners.
8

Monitor and commit

Over the next three evenings, Copilot watches the pool utilization and flags the new peaks. Utilization settles at 71 percent with headroom for the projected next six months.

​
Support outcome

  • Current utilization and subscriber checks demonstrate the result of the approved capacity change.
  • Address records and required operational contacts reflect the pool actually deployed.
  • The incident closes with a verified service result or an escalation carrying the remaining capacity issue.

Procedures

CGNAT pool expansion with POP and prefix as arguments.

Memories and search

Save CGNAT platform quirks so they’re not relearned at 22:30.