show running-config omits the VLAN table, DHCP pools, DNS zones and VRRP groups #1232

Closed
opened 2026-11-09 16:35:42 +00:00 by jaylouisw · 0 comments
Owner

What happens

show running-config prints the interfaces, the ACLs, the static routes and the default gateway — and
nothing else. Four things you can configure through the CLI are missing from the output entirely:

Configured with Stored as In running-config
vlan 42 omitcheck config.vlans[42].name no
ip dhcp pool OMITCHK … config.dhcpPools[] no
dns zone x.test / dns add www A … config.dnsZones[] no
vrrp 42 ip 10.1.2.1 (in an interface) config.vrrp[] no

Since #1231 the output is tested to be replayable — but the round-trip test only seeds fields the
printer already printed, so it cannot notice that a whole object was never written. A "backup" taken
today silently drops the VLAN table, every DHCP pool, every DNS zone and every VRRP group.

Steps to reproduce

enable
configure terminal
vlan 42 omitcheck
ip dhcp pool OMITCHK
network 10.70.0.0 255.255.0.0
range 10.70.0.10 10.70.0.200
exit
dns zone omitcheck.test
dns add www A 10.1.2.50
interface Gi0/0/0
vrrp 42 ip 10.1.2.1
exit
end
show running-config

The output contains hostname, one block per interface, and nothing about VLAN 42, the pool, the zone
or the VRRP group — while show vlan, show ip dhcp pool/leases, show hosts and show vrrp all
report them. Pasting the config into a fresh device produces a device that answers DHCP and DNS
differently from the one the config came from.

How it was found

A completeness sweep: configure a device through the CLI, then look for every configured value in the
printed text. The values that never appear are the omissions. (The same sweep correctly ignores
physical inventory — cage type, speed caps, media — which is device spec, not configuration.)

Expected

  • Every object the CLI can configure appears in show running-config, in a form the parser accepts
    back (the #1231 invariant: paste it in, get the same running-config, with the same state).
  • Where a field has no command syntax, it is documented rather than silently dropped — a DNS record
    TTL, for instance, is not settable from the CLI today.

Not affected

show running-config output for interfaces, addresses, descriptions, shutdowns, access-groups, ACLs,
static routes and the default gateway: complete, and covered by the round-trip test.

## What happens `show running-config` prints the interfaces, the ACLs, the static routes and the default gateway — and nothing else. Four things you can configure through the CLI are **missing from the output entirely**: | Configured with | Stored as | In running-config | |---|---|---| | `vlan 42 omitcheck` | `config.vlans[42].name` | no | | `ip dhcp pool OMITCHK` … | `config.dhcpPools[]` | no | | `dns zone x.test` / `dns add www A …` | `config.dnsZones[]` | no | | `vrrp 42 ip 10.1.2.1` (in an interface) | `config.vrrp[]` | no | Since #1231 the output is tested to be *replayable* — but the round-trip test only seeds fields the printer already printed, so it cannot notice that a whole object was never written. A "backup" taken today silently drops the VLAN table, every DHCP pool, every DNS zone and every VRRP group. ## Steps to reproduce ``` enable configure terminal vlan 42 omitcheck ip dhcp pool OMITCHK network 10.70.0.0 255.255.0.0 range 10.70.0.10 10.70.0.200 exit dns zone omitcheck.test dns add www A 10.1.2.50 interface Gi0/0/0 vrrp 42 ip 10.1.2.1 exit end show running-config ``` The output contains `hostname`, one block per interface, and nothing about VLAN 42, the pool, the zone or the VRRP group — while `show vlan`, `show ip dhcp pool`/leases, `show hosts` and `show vrrp` all report them. Pasting the config into a fresh device produces a device that answers DHCP and DNS differently from the one the config came from. ## How it was found A completeness sweep: configure a device through the CLI, then look for every configured value in the printed text. The values that never appear are the omissions. (The same sweep correctly ignores physical inventory — cage type, speed caps, media — which is device spec, not configuration.) ## Expected * Every object the CLI can configure appears in `show running-config`, in a form the parser accepts back (the #1231 invariant: paste it in, get the same running-config, with the same state). * Where a field has no command syntax, it is documented rather than silently dropped — a DNS record TTL, for instance, is not settable from the CLI today. ## Not affected `show running-config` output for interfaces, addresses, descriptions, shutdowns, access-groups, ACLs, static routes and the default gateway: complete, and covered by the round-trip test.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge#1232
No description provided.