NimBUS Architecture Overview
For Managed Service Providers, the NimBUS service level management solution strikes a unique balance between ease of use, rapid client deployment, and monitoring sophistication. With NimBUS, all service level management functions are inherent functions; they are written collectively as a single architecture and single code base. The result for Managed Service Providers is easy installation, deployment, configuration, administration, and usability.
Follow the links to learn more about…
NimBUS’ Robust Product Architecture
The NimBUS product line was designed and written from the ground up with service level management in mind. Its lean, modular architecture offers the flexibility to accommodate a variety of network configurations, lending itself well to the Managed Service Provider business model. NimBUS provides highly scalable, resilient, and reliable monitoring capabilities for Managed Service Providers that wish to proactively manage their clients’ IT infrastructures and critical business services.
Nimsoft’s robust, nimble architecture offers…
-
High availability features that ensure client data is protected at all times, providing spooling capabilities that ensure network outages don’t compromise data availability, support for failover in multi-tier environments, and more.
-
Segmentation capabilities that enable secure, efficient partitioning of data for multiple clients within a single unified database and infrastructure.
-
Open APIs and out-of-the-box integration with a range of third party products, making it easy for Managed Service Providers to adapt Nimsoft solutions to any management tools and monitoring processes.
-
Reliable, secure, and efficient communications across distributed sites—using SSL tunneling to securely connect remote client infrastructures to Managed Service Provider operations and offering a publish-and-subscribe messaging bus for efficient and reliable data transmission.
Flexible, Agent and Agentless Monitoring
The architecture of NimBUS allows for extremely efficient monitoring and end-to-end service level measurement. By utilizing efficient software “robots” and “probes”, installed locally on managed servers, NimBUS provides an extremely high level of management functionality while imposing little to no stress on the managed devices themselves. This "onboard" monitoring also allows the managed device to be monitored, even when network problems prohibit the device from connecting with the rest of the NimBUS management system.
NimBUS also has the ability to monitor devices and applications from an "off board" or “agentless” standpoint. For example, NimBUS technology can function as a remote client in client-server environments. This is effective when attempting to manage transaction-based environments from an end-user’s perspective, for example, a customer login to a central database or similar network service. NimBUS can even simulate complex end-user transactions and collect the true end-to-end response time of those transactions and applications. NimBUS can also communicate with network devices via SNMP for performance reporting, and process SNMP traps from these devices.
NimBUS Architectural Advantages
The NimBUS architecture features several technological advances that enable effective, proactive IT management:
-
Guaranteed message transfer using spooling mechanisms. Utilizing robot (agent) technology installed on the managed devices allow critical management data to continue to be collected and safely stored, regardless of network connectivity to a central management console. This spooling ability guarantees that data will continually be collected and delivered when connectivity is restored.
-
Cost control on dialed-up lines (e.g. ISDN, modem). Traditional monitoring tools require LAN-level network bandwidth to utilize the management functions at an acceptable performance level. NimBUS was designed to provide an efficient management interface with minimal bandwidth requirements.
-
Message Suppression. NimBUS message suppression technology verifies and notifies network management staff of problematic issues as they occur. Residual alarms or alarms that result due to a parent cause are suppressed to allow administrators to focus on the real issue.
-
Multi-platform support. NimBUS provides monitoring capabilities for most major operating systems, databases, networking services, and traditional network management protocols. Gateways to other management tools enable NimBUS to interoperate with and leverage existing investments.
-
TCP/IP based. With its TCP/IP-based messaging, NimBUS offers a great deal of flexibility in managing remote devices and applications. Customizable socket transmission ensures NimBUS operability in secured and firewall environments.
-
Optional compression of data. Data compression capabilities provide the NimBUS administrator with extra confidence in knowing that the cost of bandwidth is at a minimum while using the NimBUS solution.
NimBUS’ Sophisticated Communication Model
Applications within the NimBUS domain communicate by exchanging messages. The use of a robust, high-volume messaging bus, implemented in software that serves as a network among all applications and platforms, makes NimBUS unique in managing the IT infrastructure environment. The NimBUS messaging bus provides the infrastructure for reliable TCP/IP-based communication across a Managed Service Provider’s multi-tenant deployment.
The NimBUS architecture includes the use of a publish/subscribe model, also known as push technology. When an application within a NimBUS domain has new data, it automatically publishes the data to the messaging bus and all associated applications (subscribers) receive it. A publisher submits messages with a specific subject and any listener can receive those messages by listening for messages with that subject. Traditional point-to-point client server systems require multiple copies of messages to be sent, one to each application, which is far more inefficient.
The NimBUS architecture provides for configuration of all publications and subscriptions via a single native management console or a Web-enabled interface.
NimBUS Components
NimBUS is comprised of several major software components. Each of these components communicates with one another via the NimBUS messaging bus. Following is an overview of the major NimBUS components.
Domain
A NimBUS domain is a logical collection of managed elements, for example, a Managed Service Provider’s full set of clients and their associated IT infrastructures. A domain will consist of several NimBUS subcomponents that perform a specific monitoring function. NimBUS administrators may wish to have multiple NimBUS domains, for example, in networks that span large geographic areas.
Hub
A NimBUS hub is the most important and major communication component involved within any NimBUS deployment. A hub receives all messages posted by a publishing entity, a NimBUS robot for example, and distributes these messages to a set of subscribers of the publishing subject. In a Managed Service Provider deployment a client hub receives messages from client-based robots and securely transmits those messages to the Managed Service Provider’s master hub. A NimBUS domain can have multiple hubs, which may likely correspond to multiple Managed Service Provider client deployments. Hubs can be designed with failover in mind, so that a secondary parallel hub can serve as hot standby in the instance a disruption occurs in a primary hub.
Distribution Server
NimBUS features an extremely powerful distribution engine that offers a fast and easy way to distribute software and monitoring functionality to managed devices. Utilizing a “drag-and-drop” interface, NimBUS probes can be quickly distributed across an entire service provider deployment from a single management interface.
NimBUS Manager
The NimBUS Manager is used to administer a NimBUS domain. This application is typically used as a management console for deploying, installing, and configuring NimBUS probes on managed devices. Additionally, the NimBUS manager is used to manage NimBUS user profiles and it also provides access to other NimBUS applications.
Robot
A NimBUS robot provides other NimBUS components with information about a managed device. A robot is installed on each managed server, desktop, or workstation and provides the basic communication functionality for a system to be monitored in a NimBUS domain. A robot also contains several important subcomponents:
-
Controller. The controller is the contact point of a robot as seen by other NimBUS components, such as the hub and other NimBUS clients. The controller maintains a set of probes that it starts and stops according to configuration settings.
-
Spooler. The spooler receives messages published by the probes (clients) and delivers these messages to the hub, unless it’s configured to spool (hold) the message until a certain criteria is met. If network connectivity with a hub is lost, the spooler can retain messages and deliver them once connectivity is restored.
Probe
NimBUS probes provide the intelligence to manage specific components on a device. For example, one common NimBUS probe, the CDM probe, is responsible for monitoring CPU, disk, and memory utilization on target hosts. Over 100 probes are available to manage a range of devices, applications, and platforms. Typically, administrators use the NimBUS manager to deploy probes running on the managed devices. Through the use of NimBUS toolkits (SDKs), custom probes can be written to manage homegrown applications as well.
NimBUS Alarm Server
The NimBUS alarm server (NAS) has the main responsibility of receiving and managing incoming alarm messages. The NAS also supports message suppression and provides clients with services such as update events, message filtering, automating actions, and mirroring capabilities.
The graphic below provides an overview of how select NimBUS components are installed in a Managed Service Provider environment.
Click image for a lager version.
Flexible NimBUS Deployment Options
NimBUS offers a lean, modular architecture that provides the flexibility to accommodate a variety of network configurations. Following are a few examples of some common Managed Service Provider deployment scenarios:
Deployment Option 1
In this scenario, the Managed Service Provider installs NimBUS on the customer premises and hands over the management interfaces and service level reports to their client’s internal IT staff. In this case, the customer would own the NimBUS software. A Nimsoft reseller would be more likely to take this approach than a Managed Service Provider.
Deployment Option 2
Depicted below is a traditional Managed Service Provider business deployment in which NimBUS SSL (secure socket layer) tunneling capabilities are used. In this scenario, the Managed Service Provider owns the NimBUS software and leases the managed service to its client. NimBUS probes are installed at the customer’s site to perform local monitoring tasks, and collect performance data.
NimBUS alarms and performance metrics are transported across the Internet. NimBUS secures this data transfer by creating and maintaining an SSL tunnel, a secure point-to-point connection between two locations. NimBUS SSL tunneling performs a task identical to a traditional VPN, but without the need to purchase and install a traditional VPN configuration.
Deployment Option 3
Depicted below is a traditional Managed Service Provider business deployment in which a traditional VPN is in place. In this scenario, the Managed Service Provider already has established a VPN connection with their client. NimBUS probes are installed at the customer site to perform local monitoring tasks, and collect performance data. NimBUS alarms and performance data is transported across the customer’s VPN to the Managed Service Provider for processing and problem resolution.
