Hello.
first of all::: Provider-1 is just a centralized management GUI. It
has nothing got to do with Software maintenance (at least not in rev 4.1).
According to my understanding SiteManager-1 (as it real name is) is just
a stripped down Provider-1 and has nothing got to do with software maintenance
either.
If you can apply a patch remotely or not depends on your rulebase,
not on the management- software. I.e. you could allow scp/ssh from your
site to your customer's site.
To your understanding. With an enterprise management center you can
manage several Firewalls, but you have the targets and the network objects
of all the firewalls just as one big blob. They are not logically seperated
from each other. In provider-1 they are, so that every customer can use
the same private subnets and so on.
--Joerg
Hi,
Does anyone know of a place where I can
find some good info about Provider-1?
The situation is as follow's. We have
some clients that want us to take over their Firewall administration.
As for now we do that by going on-site and preforming the nessecary administration
there. But, that is very time-consuming. Because when a patch is needed,
or someting, we need to go on-site to patch it. We want to be able to
do this remotely. Also, stuff like checking logging, disk-usage (on NT
and Solaris firewall's), adding rules (on Nokia, NT and/or Solaris) and
stuff like upgrading IPSO versions. My thought was to do this using a
VPN, or dedicated ISDN lines and using the FW-1 GUI's. But I also heard
about Provider-1 and SiteAdministrator-1 With which all of this should
also be possible. Can anyone tell me something about it, pro/con's of
either sollutions. What can Provider-1 do that SiteAdministrator-1 can't?
stuff like that.
Thanks,
Greetz Vincent Ridderikhoff
