Skip navigation
1 2 3 4 Previous Next

Sentry Software

192 posts


Spring is the season of renewal!


Monitoring Studio, your essential and powerful monitoring tool now has a modern and intuitive web interface, thoughtfully laid-out and easy to navigate.


With Monitoring Studio X, see how you can easily interact with your PATROL agent (configure, test, troubleshoot, visualize it)!


Enjoy the journey... with Monitoring Studio X!



There seems to be a limitation in displaying the content of a file.

I cannot display a file bigger than 2 MB   (2097152 Bytes).  It's not a PSL limit but rather Agent Query.




FILE = "$PATROL_HOME/log/mylog.txt";

Size = 2097152;

timeout = 10;

catChan = popen("OS", "cat ".FILE);

timeouttime = time()+timeout;

do {


data = read(catChan,Size);


} until(!chan_exists(catChan) || data!="" || (time()>=timeouttime));



It will give the output with size = 2 MB.

  There won’t be anything displayed if I run the same script where Size = 2 MB + 1


See as well screen shot the script ran Size=2097152


If won't display anything,  if I run the same script with Size=2097153 (2^21 +1)



As you can see, Sentry Software, TrueSight Operations Mgmt|TrueSight Infrastructure Mgmt 's users, so much ground has been covered since 2009!


Configuring Process Monitoring

In 2009In 2019
2009 - Process Monitoring Wizard.png2019 - Process Monitoring Wizard.png



Monitoring the Weather

In 2009In 2019
2009-Monitoring-the-weather.png2019-Houston Weather.png


Monitoring Stock Quote

In 2009In 2019
2009 - Stock Quote.png2019-BMC Stock Quote.png


Thanks to all our users for sharing their feedback and help us improve our products.


Special thanks to the Sentry Team (Bertrand Martin, Marc Douguedroit, Ramassh Theivendran, Razeem Mohamed, Nathalie Leboul, Frederic Plouvier, Sam Truong, etc.)  for working so hard to make this new Monitoring Studio 10 happens!


Release is coming soon! Stay tuned!


We are pleased to announce that Monitoring Studio X beta 3 is now available!


In this beta 3, the last beta before the GA version, you will enjoy the following enhancements:

  • Ability to perform cookie based authentication in HTTP requests
  • Ability to embed script files in a Template configuration
  • Ability for other KMs to extend Monitoring Studio's Web UI with specific icons, online help, actions and even additional pages to provide configuration or reporting specific capabilities
  • Improved Console Web UI
  • Improved Tree view (Host and Host Groups now placed under the Monitoring Studio icon)
  • Improved Windows Performance Counter Monitoring
  • Improved Dynamic Object builder
  • Improved Value Map


Please don't hesitate to share your thoughts. Your feedback so far has been of great value to us.




So, thanks to the excellent feedback on the Beta 1 version, we're happy to announce the Beta 2 of Monitoring Studio X is available:

Monitoring Studio X | Sentry Software


What's New


  • Added Support for:
    • IBM AIX
    • Internationalized PATROL Agent (Chinese, Japanese, Korean)
  • New Monitor available: Parameter Combination (Multi-parameter Formula)

Fixed Issues

  • The toggles behavior has been fixed in the Web UI
  • Templates:
    • Templates were no longer applied to hosts when modified
    • An error occurred in the Dry Run after changing the "OS Type" of an existing template
  • Log File Monitoring: The Matching Line Count parameter was reset at the next polling
  • Java Settings: The configuration was not properly implemented
  • Ping check reported inaccurate host availability on Windows agents


Make sure to install this new version as it fixes many issues you guys may have encountered with the Beta 1.


Next around the corner: the Beta 3 with a reworked Console view, an easier Value Map UI, support for OAuth 2 or cookie-based authentication when querying a REST API, etc.


We're very grateful for your feedback! Thank you in helping us make this a great product!


-- Bertrand


If you've tried Monitoring Studio X and its new fancy Web UI, you may have wondered: why is the Web UI and REST API running on port 3443?


Being the main culprit for this decision, I owe us an explanation...


First, traditional ports like 8080 or 8000 were out of the question, simply because the PATROL Agent is supposed to be running on servers that may be running an application on port 8080 or 8000 (evidently, same goes for 80 and 443).


Or course, the PATROL Agent's port (3181) itself couldn't be reused as our Web UI is running as a separate process and cannot share the port with the PATROL Agent. I wouldn't take the risk of using 1987 either (as seasoned BMC users may recall, 1987 used to be the default port of the PATROL Agent, back in the days, that is: in the previous millennium... yeah, my age is showing here... :-D)


So, the logic was as follows:

  • All PATROL stuff is in the 3xxx, so the Web UI had to run in the 3xxx range
  • It's full HTTPS, so it should be obvious we're in HTTPS, so the port should say 443
  • Conclusion: 3xxx + 443 = 3443


Good thing: TCP/3443 appears not to be reserved by any widely-deployed application (Port 3443 (tcp/udp) - Online TCP UDP port finder - -- well, there used to be OpenView something, we don't care... ;-) ). Plus, it's really easy to type in! So, here's the way for you guys to remember the port number of the Web UI and REST API of Monitoring Studio X (and the PATROL Agent): 3xxx + 443 = 443!


Now, things get a bit tricky.


People often run several agents on the same system, running on different ports, typically 3181, 3182, 3184, 3185, etc. (why not 3183, I'll let you guess). As there is an instance of the Web UI for every PATROL Agent, we need a different port for every instance of the Web UI!


So, PATROL Agent running 3181 has a Web UI running on 3443.

Logically, PATROL Agent running on 3182 would have a Web UI running 3444.

And so on...


That's how we came up with this rule: the Web UI of Monitoring Studio runs on the PATROL Agent port number plus 262: 3181 + 262 = 3443


Of course you can customize the port the Web UI is running on, and we recommend that you always specify a "relative port", like the default +262.



Now you know everything about port 3443! :-)


Remember: once you've installed Monitoring Studio X on a PATROL Agent, use your browser to connect to port 3443!


-- Bertrand


We are very excited to announce that Monitoring Studio X beta is ready!


Monitoring Studio X is the next generation of Sentry Software well-known and powerful toolbox that you have widely adopted to shape and customize the monitoring of all your datacenters.



Today, we are proud to introduce some of Monitoring Studio X's most significant improvements and capabilities:

  • A modern Web interface to easily configure the monitoring of any component in your datacenter, see example below:

  • A live and user-friendly interaction with a PATROL Agent
  • A new REST API to query and interact with a PATROL Agent
  • A hot "Dry Run" feature to challenge your monitoring settings before implementing them


After months of hard work, this innovative and modern version of Monitoring Studio needs to pass the crucial test before its public release, which is to face its most demanding challenge... real-life users. That's why we would like you to try out the beta and contribute to the success of Monitoring Studio X.

Download Monitoring Studio X beta and share your experience with us through BMC Communities or our Web site before the end of December!

Short tutorials are available on our YouTube channel to walk you through basic concepts of the beta:


Thank you for your collaboration. We can't wait to hear what you think about the beta!

Monitoring Studio X is made available to allow a large user base to test and evaluate the next major version of our monitoring solution. Note that it is not recommended for production use at this stage.

Reminder: What is Monitoring Studio?

Monitoring Studio is a well-known, widely adopted, powerful and mature toolbox that allows TrueSight Operations Mgmt administrators to implement a tailored monitoring of all their datacenters components.


Monitoring Studio offers a set of various "Monitors" that allows you to:



  • File systems
  • Files
  • Folders
  • Processes
  • SNMP Traps
  • Windows Events
  • Windows performances counters
  • Windows services

Search for strings, extract numeric values

Run and analyze the output of...             

  • Commands and scripts
  • HTTP requests
  • SNMP polling
  • SQL queries
  • WBEM queries
  • Web services
  • WMI queries


And may other features...


With Monitoring Studio, you can monitor anything, anywhere. Yes, anywhere, because Monitoring Studio can perform queries remotely.


What is Monitoring Studio X?

Fans of Monitoring Studio have asked us to create an interface to be able to configure it very easily and quickly. We accepted the challenge, and while we were there, we extended this interface to interact with the PATROL agent, and even better, we developed a REST API to communicate with the PATROL Agent.


Monitoring Studio X new features are:


  • A new PATROL Agent web interface that shows an agent’s behavior, live! It is a responsive and reactive interface that provides immediate feedback of a PATROL Agent’s monitoring actions. -> Live interaction


  • A new Monitoring Studio web interface to configure the monitoring of any component of your datacenter. -> Easy configuration


  • A new REST API that you can use to query a PATROL Agent. -> Modern interaction


  • Icing on the cake: Monitoring Studio X offers a "Dry Run" feature to test your monitoring immediately and check whether the result matches what you expect.


How Does Monitoring Studio X Work?

Monitoring Studio X key concepts are Hosts, Templates and Monitors.


  • Host: A Host is a server or a group of servers that you define in Monitoring Studio in order to monitor it/them.


  • Template: A Template is a group of Monitors. It usually defines the monitoring (health and performance) of an application, like MySQL, RecoverPoint, etc. A Template is applied to one or several Hosts.


  • Monitor: A Monitor is a single monitoring action that is configured by the user. A monitor is part of a Template. A Monitor can be:
    •     Process monitoring
    •     File parsing
    •     HTTP request
    •     Database query
    •     SNMP polling
    •     Folder monitoring
    •     WBEM query
    •     WMI query
    •     Command line execution
    •     etc.


In a Nutshell

Monitoring Studio X will make your life much easier! It is not only a complete and mature toolbox to monitor any component of a datacenter, but also a powerful web interface to visualize a PATROL Agent’s information, that is intuitive, flexible, and reliable.


Park Place Technologies (PPT), the world’s largest pure-play third party maintainer of data center systems, chose the TrueSight Infrastructure Mgmt |TrueSight Operations Mgmt   platform and the Hardware Sentry KM to monitor the wide range of systems they support for their clients. With more than 30,000 datacenters for 11,000 customers over 100 countries to monitor and the thousands of systems to support, the ParkView project could seem ambitious. A close partnership with BMC and the expertise of Sentry Software made it possible!


Watch this video to learn how the ParkView project started, the technical challenges faced and how ParkPlace, BMC Software and Sentry Software worked together to provide proactive fault detection through ParkView and improve on their already impressive 97% customer satisfaction!



Hi TrueSight Operations Mgmt, TrueSight Infrastructure Mgmt, and TrueSight Capacity Optimization communities!


On behalf of the Sentry Support Team, I am happy to share with you the list of knowledge articles that have been recently published on Sentry's Website:


NEWCollecting an SNMP Walk/Dump                                                            
NEWEMC VNX monitoring not working because of special characters in the password                                    
NEWHow NetApp Filers KM for PATROL Reports 'Failed’ and ‘Degraded’ Status Values in the PATROL Console
NEWHow to manually set agent thresholds in a CMA policy      
NEWMonitoring HP Blade Chassis with Hardware Sentry
NEWProcessing Data From a REST API JSON Format
NEWSNMP Connectors stopped working
NEWUsing Database Query Analysis
NEWVerifying Database Connectivity
UPDATED          Enabling Debug for Sentry's KMs in TrueSight/BPPM and PATROL Classic Consoles                     
UPDATED          Monitoring Fails Due to SSL Handshake or Authentication Failures     
UPDATED          BMC TrueSight CO for Storage: Assessing the Requirements             
UPDATED          Generating Test Events with Hardware Sentry KM for PATROL                                  


Many other articles describing technical solutions and best practices to configure our products are also available in the Sentry's Knowledge Base.


Feel free to submit any topic you would like to be covered in our knowledge base.




In this previous post, Bertrand Martin showed the first screenshot gallery of the PATROL Agent Web UI. This was long before I gave the interface a makeover and come up to:


The UI is still under construction but your feedback is important! Feel to comment this post.


What are the servers remotely monitored? How to know whether the remote monitoring that I have configured is working correctly? How to turn the debug on? What is the version of Hardware Sentry KM? What is the build number?


You can have access to a wealth of information about your hardware monitoring by executing PSL Commands in the Agent Query Tool in TrueSight Operations Mgmt.


By modifying our code and providing access to some of our PSL functions, we now allow you to execute PSL scripts on a PATROL agent running Hardware Sentry KM in order to run global reports, host reports, queries and commands (in versions 10.0.00 and higher).


Here are some examples of information that you can gather.


See Remote Systems Monitored by an Agent

  • Command: requires MS_HW_q; hostsInfo();
  • Output:

Easily Enable the Debug Mode... by Host!

Enabling the debug mode is quick, easy, and you can target a specific host to get only the information you are interested in!

  • Command: requires MS_HW_q; setDebug(mode, numberOfMinutes, listOfHosts);
  • Output:

Check Connectors

You can check if connectors are monitoring correctly a remote host and not encountering any issue with the instrumentation layer(s).

  • Command: requires MS_HW_q; connectorsReport(hostID);
  • Output:

Force a Discovery

This can be very useful if you have made updates and don't want to wait for the next discovery.

  • Command: requires MS_HW_q; rediscover(hostID);
  • Ouptut:

Provide Information to the Customer Support

Providing accurate information to customer support will always help resolving an issue faster.The Product Report reports product information such as product version, KM information, installed libraries and connectors.

  • Command: requires MS_HW_q; productReport();
  • Ouptut:

And Many More!

Don't hesitate to have a look at all the other commands.

  • Command: requires MS_HW_q; help();
  • Ouptut (partial):


Reminder: how to run a query on a PATROL agent?

  1. Access the PATROL Agent.
    1. In the navigation pane of the TrueSight console, click Configuration and select Managed Devices. In the Managed Devices table, the PATROL Agents are displayed under the associated Integration Services that are displayed under the corresponding Infrastructure Management Servers.
    2. For the PATROL Agent that you want to access, click + against the associated Infrastructure Management server and the Integration Service to expand them. The PATROL Agent is displayed.
  2. Click the PATROL Agent action menu and select Query PATROL Agent. The Agent Query Tool opens in a new browser window.
  3. In the Command box, specify the query.


Note: These commands are available in PATROL Central as well.

Download Hardware Sentry KM on Sentry's Website!



Monitoring Studio X beta version is coming soon! Developers are working hard and we are all excited by this amazing new version. With Monitoring Studio X, you will have a new Web UI to interact easily with a PATROL agent and visualize quickly your configuration.



Would you like to share your ideas with designers and developers, have an impact on its conception?


This is a unique opportunity to participate in building a great product and help ensure the best quality! What you would like to see in it? Don't hesitate to tell us!


For people who don't know yet Monitoring Studio: it is the essential toolkit (for TrueSight Operations Mgmt and TrueSight Infrastructure Mgmt) for every monitoring administrator who wants to have a perfectly tailored monitoring of his data center, without any gap.


The beta version is planned to be available this summer. More information to come soon!


Discovery issues may have various causes that can sometimes be difficult to identify. The new Report monitor implemented in Hardware Sentry KM for TrueSight Operations Mgmt | TrueSight Infrastructure Mgmt provides an overview of the discovery progress, collect, status, and results for a specific host. Each monitored attribute can be configured to trigger alerts when their value reaches an unacceptable or abnormal level to help you quickly pinpoint a discovery or performance problem.



The Report monitor is displayed in the Monitor list of the Device Details in your TrueSight console:

Report Monitor.PNG

The Report graph provides a real-time view of the data collected on a specific host. The graph can be customized to display several attributes at a time.

Report Graph.PNG


The collected data is distributed in 5 categories:

  1. Counters
  2. Execution
  3. Protocol
  4. Size
  5. Other

Note: The availability of attributes may vary according to the components discovered and monitored on your device.


Counter Attributes

These attributes report on the number of components discovered and monitored on a host. Although thresholds are not set by default, you can easily configure your own custom thresholds to get notified when a counter is going suspiciously low which may suggest a discovery issue. A graph displaying some of the following counter-type attributes can help you focus on a specific type of data to analyze and isolate an issue:



Count - All

Sum of all objects reported by the Count-x attribute, except for Count-ConnectedPorts and Count-Missing.

Count - Battery

Count of all batteries discovered on the monitored host.

Count - Blade

Count of all blades discovered on the monitored host.

Count - Connected Ports

Count of all connected ports discovered on the monitored host

Count - CPU Cores

Count of all CPU cores discovered on the monitored host.

Count - CPU

Count of all CPUs discovered on the monitored host.

Count- Disk Controller

Count of all disk controllers discovered on the monitored host.

Count - Disk Enclosure

Count of all disk enclosures discovered on the monitored host.

Count - Enclosure

Count of all enclosures discovered on the monitored host.

Count - Fan

Count of all fans discovered on the monitored host.

Count - LED

Count of all LEDs discovered on the monitored host.

Count - Logical Disk

Count of all logical disks discovered on the monitored host.

Count - LUN

Count of all LUNs discovered on the monitored host.

Count - Memory

Count of all memory modules discovered on the monitored host.

Count - Missing

Count of all objects that are currently missing.

Count - Network

Count of all network interfaces discovered on the monitored host.

Count - Other

Count of all other devices discovered on the monitored host.
Count - Physical DiskCount of all physical disks discovered on the monitored host.

Count - Power Supply

Count of all power supplies discovered on the monitored host.

Count - Robotics

Count of all robotics discovered on the monitored host.

Count - Tape Library

Count of all tape libraries discovered on the monitored host.

Count - Temperature

Count of all temperature sensors discovered on the monitored host.
Count - Voltage

Count of all voltage sensors discovered on the monitored host.


For example, a Count-All attribute displaying a number of monitored components lower than 5 may indicate that the host monitoring is likely incomplete and requires investigation.



Execution Attributes

These attributes report on the number of successful executions performed on a host, by protocol (including OS Commands) based on data collected upon each discovery.


Execution - CommandCount of successful command executions performed on the monitored host.
Execution - HTTPCount of successful HTTP request executions performed on the monitored host.
Execution - IPMICount of successful IPMI command executions performed on the monitored host.
Execution - SNMPCount of successful SNMP query executions performed on the monitored host.
Execution - UCSCount of successful UCS commands executions performed on the monitored host.
Execution - WBEMCount of successful WBEM query executions performed on the monitored host.
Execution - WMICount of successful WMI query executions performed on the monitored host.


Overloaded systems may prevent Hardware Sentry from operating properly. When a sudden drop in the number of executions occurs, it is likely due to a lack of resources available to the monitoring solution for monitoring the host in an optimal manner. Hardware Sentry 10 enables you to closely watch the amount of successful commands or queries execution on a host to rapidly pinpoint any overload or unpredicted change in the system’s workload.

Execution per min.PNG


Protocol Attributes

These attributes report on the status of the connections between Hardware Sentry 10 and the monitored host. When the monitored host is the localhost, connection issues may be due to invalid credentials or a protocol interruption or failure (SNMP service or SSH daemon stopped for example). When a connection becomes degraded or fails, the connection-specific ProtocolStatus attribute triggers an alert to immediately notify you about the protocol that requires attention. Note that the attribute graph is also annotated to provide additional information regarding the protocol error.


ProtocolStatus-CommandStatus of the connection to the monitored device with the OS command protocol.
ProtocolStatus-SNMPStatus of the connection to the monitored device with the SNMP protocol.
ProtocolStatus-WBEMStatus of the connection to the monitored device with the WBEM protocol.
ProtocolStatus-WMIStatus of the connection to the monitored device with the WMI protocol.



Size Attributes

The size-type attributes report on the consolidated size, in gigabytes, of logical/physical disks and memory for the monitored host, giving you an overall view of the capacity potentially available on your device.

Size - Logical DiskSum of the size of all discovered logical disks on the monitored host.
Size - MemorySum of the size of all discovered memory modules on the monitored host.
Size - Physical DiskSum of the size of all discovered physical disks on the monitored host.


Other Attributes

Degrees Below WarningNumber of degrees before reaching the closest warning threshold.
Hardware Discovery StatusStatus of the discovery of all hardware components on the monitored host.
Hardware Discovery TimeTime taken to discover all hardware components on the monitored host.
Platform Detection TimeTime taken to detect the connectors that match the system. If connectors are pre-selected, the attribute value is '0'.
Power ConsumptionWattage consumed by all the discovered components on the monitored host.
Total Bandwidth

Sum of the values of all LinkSpeed attributes (only for plugged-in network cards).


Some of these attributes may anticipate critical situation and optimize the monitoring of your entire IT assets, for example:


The Degrees Below Warning attribute reports on the remaining number of degrees (C°) before the temperature reaches the closest warning threshold set on the temperature sensor of the device. Hardware Sentry 10 automatically sets thresholds according to the manufacturers' recommendation and the location of the temperature sensor. A continuous and close control of the temperature of your servers will help you optimize the overall temperature of your entire IT environment to avoid hardware overheating and keep your energy bill within budget.


The Hardware Discovery Status attribute can help you identify an unusual or suspicious workload on the agent monitoring a host.

A Hardware Discovery Status set to 1 (Waiting in Bottleneck), indicates that the discovery is waiting to be performed. A discovery process reported longer than a mere second in a bottleneck state (value at 1) is likely to indicate a resource issue. Although Hardware Sentry 10 handles these situations, splitting the configuration across other PATROL agents might help optimize the monitoring performance.

A Hardware Discovery Status set to 2 (On) can be trickier to analyze, since it may occur when the monitored host is slow or if the number of devices to discover is high. Typically, the graph should display a discovery status set to 1 when the host discovery starts, and then a value at 2 that should remain for the same duration from one discovery to another, meaning that Hardware Sentry 10 and host are behaving the same way from one discovery to another.


The Hardware Discovery Time attribute collects the time taken to discover the hardware components on a monitored host. The Hardware Discovery Time attribute of a specific host can be customized to alert you when sudden baseline deviation occurs and therefore help you isolate the root cause of the problem faster.



The Power Consumption attribute reports on the wattage consumed by all the discovered components on the monitored host. This measure makes it easier to determine which of your systems consumes the most or the less energy. The Power Consumption attribute provides a solid, overall view of a host power consumption and can help you better manage energy efficiency.


Monitoring the discovery and availability of critical components and processes, such as CPU, memory, battery, temperature, connections, etc.., is essential to maintain systems’ performance, anticipate critical hardware failure and minimize downtime. The Report monitor can help support the effort to maintain proactive problem detection policies by constantly monitoring critical key-performance indicators; it can also become a source of significant savings in terms of time and money by providing an overall portrait of systems health and performance and by quickly pinpoint the root cause of potentially critical issues.


Download Hardware Sentry KM on Sentry's Website!


2017 is Over!


It was a year marked with the release of several new products and updates. Just to make sure that you did not miss some of them, here is a short review of what was done in 2017:



5 Brand New Products

2 for TrueSight Capacity Optimization3 for TrueSight Operations Mgmt|TrueSight Infrastructure Mgmt
Released along with TSCO v11


11 New Configuration Templates

To support even more storage devices and applications in TrueSight Operations Management, Sentry Software developed new monitoring templates for Monitoring Studio:

8 Updated Products

ProductsMain Changes
Hardware Sentry KM 10.0.01
  • Easier infrastructure management:
    • identical systems configured in one operation
    • faulty devices better identified and perfectly located
  • More reliable hardware monitoring:
    • advanced self-monitoring feature
    • early detection of hardware discovery issues
  • Advanced diagnosis features to report, diagnose, debug, query, and manage.
Monitoring Studio KM 9.4.01
  • Support for Java 9
  • Group macros can be used in Host monitors and Group & Host macros can be used in all other monitors (ex: %{SEN_HOSTNAME})
  • Database Query: Microsoft SQL Server uses Microsoft's JDBC driver
  • Possible to connect and authenticate against a remote system with SSH and keyboard-interactive authentication
  • The new Value Map Monitor can extract values from result outputs of other Monitors and map these values to user-defined status that match your specific needs
  • The Command Line Monitor can execute command lines locally and remotely respectively
EMC Disk Arrays KM for PATROL 4.2.00
  • Support for EMC VMAX3 storage systems
Hitachi Disk Arrays KM for PATROL 1.5.00
  • Support for Hitachi Unified Storage VM (HUS VM) (through the Hitachi Embedded SMI-S Provider)
  • iSCSI-mapped volumes now discovered for HDS G-Series
NetApp Filers KM 3.3.01
  • Support for Data ONTAP v9
  • Additional information about the cluster nodes status
EMC NetWorker KM 3.0.00
  • Support for NetWorker 9.x
  • Support for remote monitoring
  • Consecutive backups monitored at save set level under each group client
  • Support for PATROL Agent v10+
  • Support for TrueSight Operations Management v10.x
Tivoli Storage Manager KM 3.0.00
  • Support for remote monitoring
  • Support for libraries controlled by ACSLS (StorageTek Automated Cartridge System Library Software)
  • Support for PATROL Agent v10+
  • Overall performance improved
Veritas File System KM 2.2.00
  • Support for PATROL Agent v10+
  • Support for TrueSight Operations Management v10.x
  • Support for regular expressions in all configuration menus


Coming Soon...

Veritas Cluster Server KM 3.0.00, Veritas File System KM 3.0.00, Veritas Volume Manager KM 3.0.00, which will all support remote monitoring. Stay tuned!


Thank you all for your support and trust.

Filter Blog

By date:
By tag: