[j-nsp] commit full

[Paul Goyette]

"commit full" basically marks the entire configuration as
"changed" so that all daemons are notified to process the
new configuration.

Under ideal situations, you would never need to use the
"commit full" command, since we're already supposed to
notify all _affected_ daemons based on what has actually
changed in the config.  But sometimes we discover that we
missed something.

If you have specific situations where a particular change
does not notify one or more affected daemons, please open
up a support case so we can identify it in the future.

Paul Goyette
Juniper Networks Customer Service
JTAC Escalation Engineer and
Security Incident Response Team 
PGP Key ID 0x53BA7731 Fingerprint:
  FA29 0E3B 35AF E8AE 6651
  0786 F758 55DE 53BA 7731 

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> Lukasz Trabinski
> Sent: Monday, December 18, 2006 1:20 PM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] commit full
> Importance: High
> 
> Hello
> 
> There is probably very stupid question, but what is
> precisely difference between commit and commit full.
> I have situation when some times after normal commit some changes in
> configuration are not applied to running router/system, for 
> example some
> changes in policer/firewall, changes in interfece description, changes
> in eterchannel options and many more. Why? It is JunOs bug or
> feature?  :)
> 
> -- 
> Lukasz
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>