Wildcard in a netconfig job?

jpazahanick · ‎06-17-2009

I was wondering if there was a way to specify a wildcard in a Netconfig job...

For example, here is a snip of the current config;

interface GigabitEthernet1/0/0.12300074

encapsulation dot1Q 1230 second-dot1q 74

ip unnumbered Loopback1200

ip helper-address 172.30.31.3

ip helper-address 172.30.31.4

no cdp enable

service-policy type control DHCP-NAS

ip subscriber l2-connected

initiator dhcp class-aware

!

interface GigabitEthernet1/0/0.12300075

encapsulation dot1Q 1230 second-dot1q 75

ip unnumbered Loopback1200

ip helper-address 172.30.31.3

ip helper-address 172.30.31.4

no cdp enable

service-policy type control DHCP-NAS

ip subscriber l2-connected

initiator dhcp class-aware

!

interface GigabitEthernet1/0/0.12300076

encapsulation dot1Q 1230 second-dot1q 76

ip unnumbered Loopback1200

ip helper-address 172.30.31.3

ip helper-address 172.30.31.4

no cdp enable

service-policy type control DHCP-NAS

ip subscriber l2-connected

initiator dhcp class-aware

There are close to 4000 subinterfaces like these.. I would like to be able to create a job to say remove the ip helper addresses of all 4000 subinterfaces. Is this possible?

Marvin Rhoads · ‎06-17-2009

Netconfig jobs should accept the asterisk (*) as a wildcard.

I recommend you take a look at the "Features of Baseline Templates" section of the RME User Guide for some further pointers on using wildcards to check and enforce template compliance - the task you seem to be investigating.