Through our engineers research and development, we wish to compile the following list of advances and new concepts that we are either introducing from scratch or utilizing and refining through introducing new life and new ways of applying those concepts.
The list of concepts and a brief description on each is given below:
- SNMP Instruction Set (SIS) Language definition
- Autonomously Managed Zone (AMZ) definition
- User Levels and Roles definition
- Real-Time Journal reports
- Data Integrity and Summarization options
- Information Exchange Management
SNMP Instruction Set (SIS) Language definition
White Seagull solution is a “Higher-Level Manager” designed to understand, deal with, and cater to the complexity of the SNMP network management protocol structure. It introduces a proprietary SNMP Instruction Set (SIS) Language.
SISL is a ‘Management Scripting Language’ used to write ‘Management Scripts’ with each management script representing a set of instructions written in an executable non-native high-level language code which implements a management function.
The network administrator can hence modify any running management script and the list of managed devices as per the requirement of the network and the management policy adaptations or changing network conditions.
The introduction of SIS Language enables network administrators to understand, drive, and custom fit the under laying management processes to their prospective networks in accordance to their own (maybe) unique management requirements and policies. SIS Language could then be used to build intelligent solutions based on Event-Driven management combined with Result-Driven management solutions.
The introduction of our own SIS Language opens the door for a large number and a wide range of elaborate and creative management solutions. Solutions the industry has been seeking for a very long time. Solutions to say the least that interprets the current standards correctly before we could talk about new standards that could take years to implement and could cause a huge loss on investment on current management infrastructure implementations.
Traditionally NMS and the SNMP protocol have been synonymous with clear text open community strings being transferred on the wire as well as saved in the databases of NMS applications without any encryption. In other words; Known and widely used NMS applications are severely unsecured. Historically “compromised security” was sold to customers as the cost of doing network management.
Security of SNMP was introduced through SNMP Version 3. Hence the significance of SNMPv3 support is really critical for building secured solutions. It is interesting to mention here that NO serious SNMPv3 based NMS application solutions are available in the market today.
Autonomously Managed Zone (AMZ) definition
White Seagull uniquely allows network administrators to logically break large networks into a number of Autonomously Managed Zones (AMZ) to allow for a more scaled and consistent approach to management in terms of applying specific management processes to particular Zones and in accordance to pre-defined management policies. At the same time administrators could allow certain access rights and controls to different White Seagull Users, with each user administering their own respective AMZ.
The introduction of AMZs introduces new concept to network management systems today. All other known NMS applications behaves in a way that which ever devices present in their inventories will be polled by the running process of the NMS application. In other words, all NMS applications run a single management process and a single managed Zone when compared.
User Levels and Roles definition
White Seagull Application suites define different levels of Users. Each User Level is determined by its relation to:
- The network itself,
- The managed data,
- The Management Process, and
- The resulting Reports.
User Level support also varies amongst the different suites. Users are classified as either System or Zone related.
The introduction of User levels and their respective roles is not new to NMS applications available in the market today. However, White Seagull User levels takes the User concept much deeper and further than those NMS applications, White Seagull Users owns both running features within the NMS application as well as owning the actual information being polled from the managed device(s). The significance of this implementation is apparent when addressing issues as security, scalability, and reporting among other advantages.
Real-Time Journal reports
White Seagull allows for extensive monitoring of running Management Scripts. This is made possible as the SISLanguage syntax allows for the insertion of special message generating command statements that directs those messages to Process specific Journals in real-time after being inserted by the Zone Administrator into the desired point(s) within each management script. Appearing as logs in the specific Journals; entries are dated and time stamped.
Data Integrity and Summarization options
White Seagull Application suites preserves collected and calculated data and information integrity by archiving current data while concurrently providing the options to aggregate summarize and integrate with both a local and other remote White Seagull systems.
SNMP MIB Views
One useful notion that has been overlooked for a long time is the use of SNMP MIB Views supported by the SMI Standard of the different SNMP Protocol versions. Currently and widely available Network Management packages in the market today makes no use what so ever of this very useful feature on all managed devices that supports the above mentioned industry wide standard.
A MIB View could be looked at as a window to a subset of the total MIB tree hierarchy implemented on the managed device and with own access credentials, may it be an SNMP community or even a secured SNMPv3 User. To make use of this important feature within White Seagull; simply the administrator could create the desired view on the agent device and create a Management Zone in White Seagull that is representative of the particular MIB View and finally add the device into this new Zone.