cancel
Showing results for 
Search instead for 
Did you mean: 

alternative to pulse one or how can we manage 20+ pcs with less effort

SOLVED
yutsi
Occasional Contributor

alternative to pulse one or how can we manage 20+ pcs with less effort

hello community,

 

today I more likely need a suggestion, less a solution... - maybe someone is facing the same problem.

 

due to covid, our customer is expanding, we got several gw's at several locations additionally.

all locations are not connected to each other,  the less locations are even cluster.

sadly we have to get sure, all locations should wear the same configuration.

 

due to reason bevore, push-config will not work, or most likely only for some gw's.

 

every one is telling me, that pulse one should be a solution, but do not recomment it at the same time?!

can you sirs tell me an hint, how we can manage these big amount of gw's with less effort?

 

thank you in advance.

 

br.

 

1 ACCEPTED SOLUTION

Accepted Solutions
zanyterp
Moderator

Re: alternative to pulse one or how can we manage 20+ pcs with less effort

the most effective solution will be push config as it allows you to control what is moved between sites while you have a master "control" node that is what owns the configuration
the secondary solution will be pulse one; however, it relies on communication from the other devices. if push config does not work, i am not sure pulse one will be viable for your environment
barring those two options, the next best solution is strict change control and manually make the changes on the devices or make the change on one device, export that XML change, and import it to the other devices.
the final solution will be to make changes, export the user.cfg, and then import it to the other devices

View solution in original post

1 REPLY 1
zanyterp
Moderator

Re: alternative to pulse one or how can we manage 20+ pcs with less effort

the most effective solution will be push config as it allows you to control what is moved between sites while you have a master "control" node that is what owns the configuration
the secondary solution will be pulse one; however, it relies on communication from the other devices. if push config does not work, i am not sure pulse one will be viable for your environment
barring those two options, the next best solution is strict change control and manually make the changes on the devices or make the change on one device, export that XML change, and import it to the other devices.
the final solution will be to make changes, export the user.cfg, and then import it to the other devices