Distributed,
Scalable, Peer to Peer Architecture
One of the biggest reasons people choose AutoNOC is because of it's distributed,
peer-to-peer architecture that makes scaling the management solution to a large network
very easy. In fact, it requires linear effort per portal, to grow the solution, which is
not true for legacy management software.So how does it work? How do you scale your model? Would you believe
it is as simple as setting up portals wherever you need them on the network and filling in
a dialog box? Simply select a name for the portal, assign it a unique portal ID number,
and then specify the IP address and port of the nearest neighboring portal. That is all
there is to scaling AutoNOC to large networks!
All the details are handled automatically and behind the scenes.
AutoNOC uses the neighboring portal as a
proxy to get to other portals. Backbone portals are automatically assigned as hubs for
comparative and correlation purposes.
Set, report, user, and all other objects
(except for devices and device children) are synchronized across the global network.
Devices and their children are stored only on the local portal, as is all historical
information related to the devices. AutoNOC's peer to peer scalability provides the
perfect blend of easy deployment and while maximizing the integrated nature of the
portals.
Synchronization between portals occurs
by passing version tracked representations of the object model
between portals. This is a fast and highly adapted efficient method of keeping all portals
up to data in a distributed environment. |