Jalasoft is Ready to Release New Service Pack 3 for Xian Network Manager. Xian NM Gives us accurate traffic analysis through Network monitoring. Xian Network Manager can helps our IT team to predict something is going to happen in our network and alert the required people. Netflow with Xian NM 2012, you really have a clearer picture of what traffic is passing through, where it comes from and where it goes to. So the key point is Xian NM 2012 is now fully capable to provide you a heads-up whenever traffic behaves out of the ordinary.
Try out Xian Network Manager via http://www.jalasoft.com/xian/networkmanager/try
Following are the Enhancement done on Xian Network Manager SP3
SFlow monitoring: SFlow support has been added so Xian NM can now properly receive and filter SFlow packets along with Netflow V5 and V9, so three of the most important and used flow technologies are supported and can be processed at the same time to generate alerts, performance graphs, and reports on OpsMgr related to the content of the network traffic.
New virtual center rules: to monitor the data storages associated to ESX hosts and virtual machines.
Environmental sensor rules for Cisco routers and ASA devices: to monitor the voltage, temperature, battery status, and more.
IP addresses resolving for Flow: the engine can now properly resolve any public IP address into its domain name and improve the performance to make sure no delays are happening while translating these IP addresses into something users can understand when seeing the corresponding alerts or performance counters in the OpsMgr console.
Flow monitor service: a new service has been included in Xian NM to explicitly monitor Flow data. This improves performance and functionality since it is now possible to have multiple Flow services installed and each of them can independently monitor Flow traffic from various sources and with independent databases, queues, and performance parameters.
SDK Loader: a new connector module and improved OpsMgr SDK communication has been implemented exclusively for OpsMgr 2012 so performance and reliability when talking to OpsMgr has been greatly improved. For backward compatibility, if you install NM on OpsMgr 2007, the previous SDK communication is loaded but if it detects OpsMgr 2012, the new one is used, therefore the name.