But also committing and saving the changes the people wanted to allow you to follow, to behave like
a different Bible than as a complete Bible.
So remember when we were changing 90 percent of our management into peace, we have found that the IQ
test does not work until you actually you can see this.
So when we were thinking continuously, we make the changes on the firewall, but until we commit the
years, it was it was still not coming.
As a result, we have to make the changes and then it actually, you know, and then once you committed
successfully done it, actually, you know, I know you two can figure anything, but basically wise
reasoning.
Reasoning is actually I think Michael has already asked because if you if you look at this.
Michael, the thing is, whenever you make any changes, we have one which is called the basically gate
congressional monitoring competition in the system, we have any configuration and we have stock up.
So what we do is any time we make any changes in the conflict mode, we say no, it'll be if we pull
everything from there even to, you know, the and then you can you don't you just need to stay right.
Memory, which we only do in case of the final reportedly configuration, which is storing the evidence
should be come back, should be should be loaded into different configuration.
The running configuration mean, which is the active configuration which is active, which is currently
active in working condition.
Every time you make a change actually that has become and that is called a Kennedy configuration.
For example, when you just change the IP address name whose name, IP address, entity, DNS, any
change, anything you do to the firewall, if it is there it the in effect and it has no relevance for
the part where it does not impact the final to me, because that is called canidate configuration.
And candidate configuration is not life, it's not part of the application.
It's a separate configuration file.
OK, so any time you make a change, it does not impact state to me, for example, you might just go,
for example, I just I just want to put it up on the fire department.
So that's my plan.
Well, let's say I go to the device, I go to the management here in the setup, and I just change the
name.
Right now, you see, this is great.
If I go here and I see what is the name of my device and primary, I want to say I have this name.
OK, and I just applied this, yeah.
But what you can see is this come what?
This is a ready to do something, so we have changed the name, that name to change his name, at least
at the OK 23 year.
The.
Now, I change the name, but you can see in the dashboard the name of the device is considered.
And if I log into the device, actually, that name is Vincent.
Know what you can do, you look and see what happened to me.
You see this green sign is available now.
It was green before.
This shows that something has changed.
And I can show you, for example, if I go to the artist.
And in the complicated, I see any confusion of getting that information, so any confusion, which
means that can be effective communication, even you reboot the firewall, it still be affected.
OK, that is part of the firewall calculation right now.
So let's say I want to compare both of them.
Any time you make a change, the final has a new budget is in place.
But look at it.
But what happened?
Previously, name was be.
Now, these are the changes we made, which user has made, what time he had to make all of these all
different configuration.
However, these are not applied yet.
These are not applied yet.
They will not be effective until we actually do this.
We can make the changes.
Once you commit such a violent action behind the scene, check the syntax and everything that everything
is according to, you know, the firewall configuration.
And there is no conflict with things like the many things that are happening behind the scenes.
So the basic idea is if you make a blunder, you've blown the file desecration.
This will not be inspected.
Stephen, that's a very good sign from the from the devices perspective point of view that the configuration,
even it's not a place to be until you've committed what you do is there is a bottom here, OK, in the
bottom.
What you do is you can do the.
Night.
The changes this week and the previous committee have done on that Seelie, it's the same thing, but
this one we are doing from the GWI actually and the other one we're doing for Bookmarklet.
So you can see it takes some time and effectively bit of time the name will change, so.
Once the committee is successfully done.
Active spending, they take some time.
You see, the name is Killdeer.
You can see it goes up to 55 percent.
You can see up to 99 percent, 98 percent is successfully completed and the impact that would have made
any changes.
A configuration has successfully committed No.
Even I could close that, but you would see after a little bit of time, you see.
This is great, just great shows that the there is no pending configuration.
Nobody none of the user has made any changes.
We're.
OK, now you see, if I go to the config audit.
I will not if I have any information of any configuration, it doesn't it doesn't show up anything.
You see, the border positions are equal.
So there is no bending reconfiguration.
Now, if we look at our lab, if we look over the lab, what we have done.
Now, the name should be changed as well, for example, from here.
As part of our design.
If I go into our design committee, then saving the changes.
So here you can see any changes you made, it will be committing.
You can verify that change if you go to the taskbar here.
OK, you can see.
The conflict, you know, gets all of these things very far from here.
That's the success of.
I think the timing is not right at this point, we can get fixed the time as well.
But as of now, are you clear about the configuration between the new and the system configuration,
any configuration of the Kennedy configuration?
And this is exactly the same concept of Juniper as Juniper Buckley work, same as well.
Well, thanks, must.
Well, can I ask the question, please?