Skip navigation

Our development team has been very active since the initial release of UDT earlier this year. There are a ton of new items in this release, but this post will cover the top features and fixes. If you are interested in participating in the beta and you have active maintenance, simply fill out this survey and I’ll send the beta to you. Remember, betas are not supported in production so you will need to install this on a separate server than your current production UDT server.

 

1. Adding the “User” to User Device Tracker

 

We have added support for collecting user information from Active Directory. This allows you to quickly see who is logged in to a specific machine and what port the machine and user are connected to. Simply add your active directory domain controllers and we will poll the server’s event log for login events. These events will be stored in the UDT database so when you search for a user or run reports, we simply search the UDT database for this information. Here are some screenshots of the new features.

 

The All User Log Ins resource is available on summary (ie: UDT Home) and detail pages (ie: Node Details or Endpoint Details).

 

image

 

We also added the concept of UDT detail pages. Here is screenshot of the detail page. Although this screenshot doesn’t show it off, many of the values from AD are pulled in and added to this user detail page.

 

image

 

2. Improved back end topology using CDP and LLDP

 

To provide the data you need, UDT relies on accurate network topology information. In 1.0 the topology was created based on mapping ports to each other. In 2.0 we’ve added support for CDP and LLDP. When we poll the node, we will collect the CDP and LLDP information from the node (if available) and will use that topology information to create the connections on the back end. Although there aren’t any resources that will actually show off this new information now, you should see the results in the data accuracy.

 

3. Reports and Alerts

 

In 2.0 we’ve added several reports and alerts. Although we still have a lot of improvements to make, this should help with the most common requests for reports and alerts.

 

We now ship the following reports: All endpoints by VLAN, Port Capacity by Switch, All endpoints with details, Number of Connected devices by port, List of all IPv6 Addresses in your network, OUI Summary Report, Unused Port Report.

 

For alerts, we added a few alerts that will notify you when a new device is connected to the network. This will primarily be based on seeing a new MAC address on the network.

 

4. Changes to search

 

Search is often used for more than what is was intended for. Search should help you to quickly find where something is connected. It turns out, having all of that information is really handy! Unfortunately, large environments often experience timeouts and long delays when searching because of the amount of data available. To help users find what they are looking for quickly, we have split out the detailed results from search. Now, when you search, if there is one exact match, you will be taken directly to a a detail page (user or endpoint). If there are multiple matches, they will be shown in the list and you can quickly select the one that you are looking for to go to its detail page. But you really liked all of the data from the original search? No problem. We have moved this to Ad-hoc reporting. This better captures the workflow for running reports against the data in UDT.

 

5. Endpoint detail pages

 

Similar to the concept of User detail pages, we’ve added an endpoint detail page that will give you all of the information you need about specific endpoints. For example, if you search for a computer (IP, MAC, or hostname) then you will be taken to the endpoint detail page which will give you detailed port information as well as connection information.

 

image

This post compiles important information you need to know about the "New Poller" metrics and performance measurement.

We implemented a brand new polling mechanism that is responsible for scanning (SNMP,ICMP and WMI queries) Nodes, Volumes and Interfaces in NPM 10.2. The old poller was able to use only single thread (so performance and scalability was limited) which was one of the main drivers why we implemented totally new poller that can use multi-threaded (core) environments. Since the new poller is highly scalable we would like to give you few tips about how to measure and control the poller’s overall performance.

Regarding the new poller you could hear the "Collector" term so let me clarify all the wording before you dive into the details. New poller represents generic term of new polling mechanism and you can understand that as set of services and components where Collector is the controller of the general polling activity and maintains all polling schedules and also it stores poll results into database. For the execution of polling (SNMP, ICMP, WMI request) Collector communicate with Job Engine which is service that runs polling jobs and returns the results back to the Collector.

What are the new metrics I can use to monitor the new poller?

When we introduced the new poller we also added new important metrics that you can monitor in main Orion web console and which can give you control of overall polling performance.

There are three new important metrics you may watch (click on settings -> polling engines to see screen bellow):

Polling Completion – represents percentage delay in the primary polling mechanism (it represents all product polling - NPM, APM, UDT...). This metric is computed from delay of every single poll job and it means that polling jobs are delayed but they are NOT discarded in case that value is lower than 100. For example if you see that polling completion is 80% it means that polling is in average 20 seconds behind. So you can see that 1% represents 1 second of delay in polling schedule in 10.2 release (this ratio may be changed in the future). Polling completion is changed frequently since it reflects average of last 100 polling jobs. Polling completion is mostly impacted by CPU and memory resource so if see polling completion significantly lower than 100% you should check your CPU and memory utilization.

Total Job Weight (Total Job Weight for NPM Jobs) - represents complexity of actual polling plan and it serves as the base value for getting polling rate. It is combination of all elements managed by Orion and their polling frequencies.

Total Job Weight is basically the sum of the “True Job Weight” for each job in the Job Engine. For getting the "True Job Weight" we use following formulas where every type of polling job has predefined "weight" and polling frequency. Let's assume we have a job with weight of 100 and polling interval of 10 minutes:

10 minutes(interval) / 1 minute(throttle ratio unit of time) = 10

100(job weight) / 10(from above, interval/throttle ratio unit of time) = 10 (True Job Weight)

We apply this for each job defined in the throttle group and summarize the true weights of each job. For example let's say we have 300 jobs with the same job weight and polling interval:

10(True weight for Job 1) + ... + 10(True weight for Job 300) = 3000 (Total Job Weight)

Currently only the NPM jobs currently have a weight larger than “1”. For instance APM poll jobs won’t have a really big impact at the scale factor until there will be a lot of them. Right now, this is really just a number that tells us how much “weight” is going through the system per unit time. We don’t have a number that would represent the high end of what can be run per unit time.

Polling Rate – this will tell you what the current utilization of your Nodes, Volumes and Interfaces polling capacity is. Any value below 100 is OK. If it exceeds 85% then you are approaching the maximum amount of polling your server can handle and you will see notification banner in your Orion web console (see below). If the polling load is more than what the new poller can handle (i.e. more than 100%), the polling intervals will automatically be increased to handle the higher load. That means even if your CPU is not fully used new poller will increase polling frequencies if you reach the polling rate limit. Polling rate uses Job Total Weight as the base value. For example if there will be only NPM polling jobs with total weight 3000 then we use following formula for getting polling rate value:

(3000 (Total Job Weight)/2600 (Maximum polling load for NPM jobs)) x 100 = 115% (polling rate).

And because in this case value exceeded 100% then we apply throttling which means we multiply frequencies of all NPM jobs by 1.15.

As I mentioned the old poller was single threaded but the new poller is multi-thread capable so we had to introduce throttling mechanism which prevents new poller to consume all available resources for Nodes/Volumes/Interfaces polling only. Thanks to the throttling mechanism your system should have enough resources for other applications like Solarwinds APM or UDT and also for Orion web console performance.

You can also check this KB article.

If you are the real geek you probably guess that there is something more you can follow than just those three metrics. And you are right. Our development team brought a really nice set of details about polling engine you can monitor in real time so keep reading.

Advanced monitoring of new poller performance

If you really want to understand what is behind the new poller then the best way to monitor performance of polling, results processing and storing results to DB are performance counters.

This is the complete list of all available counters related to the new poller. If you need to double check your performance status you should watch mainly following items:

DPPL waiting items – this counter should not be growing constantly in time. Ideally it should  go to zero in between polling intervals. If this value keeps growing your polling results are not being proceed in the expected time and you can see gaps in charts or in poll reports. This is usually caused by slow hardware. (DDPL means Date Processor Pipe Line)

DPPL Avg. Time to Process item – reflect the time of writing polling results to DB. The optimal value should be less than 0.500(ms) otherwise you will experience noticeable delays between result processing and storage to database.

Scale Factor: Orion.Standard.Polling - represents scale factor/polling rate I mentioned above. It can tell you if the system is using throttling or not and what the current utilization is.

Messages in Queue – if this value is persistently growing then it means you are not able to process all poll results on time. This is usually because of slow hardware. But also database connectivity and performance play a key role in the ability for the collector to store results and can result in a queue backup.

If you run “perfmon” from windows start menu command line and paste (use CTRL+C and CTRL+V) attached counter list into performance monitor window on your Orion server you will see all the counters related to polling performance:

[View:/cfs-file.ashx/__key/CommunityServer.Components.UserFiles/00.00.03.32.84/countersProperties.txt]

We are currently looking at several enhancements to IP SLA Manager, including:


 


·      Updating supported Call Manager versions


 


·      VoIP calls troubleshooting based on CDR and CMR data. This should include use case where you will be able to do multi-criteria filtering/searching and sorting based on CDR and CMR data e.g. “give me calls with the same reason code, same extension pattern, same time frame, same geography or termination reason code”.


We are still collecting more input on performance and scale requirements like number of phones, amount of CDR’s generated during the day, average amount of calls during day or number of Call Managers in your environment. Please feel free to raise your voice if there is something you would like to tell us.


 


·      Better support of creating TCP operations in firewalled environment.  This is mainly related to case when you are trying to set up IP SLA operation between an internal router and external device where traffic is going through a firewall. We would like to add support of “Control Enable” parameter in case you want to create TCP and UDP IPSLA operations.


 As a second priority we are also researching deeper functionality around:


 


·         PRI channel utilization


·         Support of Avaya call managers



PLEASE NOTE:  We are working on these items based on this priority order, but this is NOT a commitment that all of these enhancements will make the next release.  We are working on a number of other smaller features in parallel.   If you have comments or questions on any of these items (e.g. how would it work?) or would like to be included in a preview demo, please let us know!

Nandish

Device Support

Posted by Nandish Oct 20, 2011

This blog post is a supplement to denny.lecompte’s “Orion MIB Database – What Is It Good For?” which answers the most puzzling questions and clarifies common misconceptions about the Orion MIB database. Re-reading Denny’s blog will help you best grasp this blog post.

In a nut-shell, Denny’s blog post discusses:

  • What is the Orion MIB database primary use?
  • How else is the MIB database used?
  • What is the most common misconception surrounding UnDP?
  • What do you do if you don’t know the OID you need?
  • How is the MIB database not utilized, though most people think it is?
  • And why do we have two databases?

Supplementing Denny’s blog post, here are answers to concrete “How-to” questions.

How to add device vendor identification for your “unknown” devices?

With the assumption that you have a clear understanding of the Orion MIB database, it becomes essential to know how to get a SysObjectID and, subsequently, the MIB database updated. A SysObjectID is the unique Object Identifier (OID) used to recognize a device’s vendor during the discovery process. Discovered devices that don’t have a SysObjectID listed in Orion’s built-in database are listed as Unknown in the Orion Summary Home page, as shown in the image below.

clip_image002

In order to add the SysObjectID to Orion’s built-in database, post the SysObjectID and the device information Tell us your "Unknown" devices!. Every point release of Orion NPM will have the published SysObjectID added to the Orion’s built-in database.

How to add new MIB’s to the MIB database before creating custom UnDP pollers?

In order to add a new MIB to Orion’s built-in database, open a support case here. A weekly download of the Orion MIB Database file from the customer portal will include the updated MIB database. Those who are not SolarWinds customers without a valid SWID like prospects/evaluators and device manufacturers can forward the MIBs to mibs@solarwinds.com .The following image shows the Customer Portal where the Orion MIB Database is highlighted.

clip_image004

By clicking Orion MIB Database, the MIBs.zip file will be available for a download. After downloading the MIBs.zip to the Orion server, it has to be uploaded to the MIB database. Before uploading, extract the MIBs.cfg file and the Readme.txt file. The Readme.txt file has step by step instructions on how to upload the MIBs.cfg file to the Orion MIB Database. The information in the Readme.txt file will be similar to the instructions pasted below.

clip_image006

After completing the procedure, you should have an updated Orion MIB Database on the server. You can verify this by selecting the Browse MIB tree option in the Orion Universal Device Poller New Universal Device Poller dialog. Then, scroll down to the newly added MIB. The following sequence of images gives direction to look for the newly added MIB.

clip_image008

How to create custom UnDP pollers?

The Orion Administrator Guide explains the process to create a custom UnDP poller in Chapter12.This video tutorial link is also very informative and explains custom UnDP pollers in detail.

 

 

How to find MIBs if you don’t or can’t find them in order to create custom UnDP pollers?

The SNMPWALK result will help you find out the MIBs if you don’t or can’t find them. This SNMPWALK application from SolarWinds is very easy to install and use. The following image shows the application.

clip_image010

It is strongly recommended to run this SNMPWALK application from the Orion installed server, so that the results of the snmpwalk do not get timed out or interrupted while scanning. This way, the MIBs configured on the device are being captured ensuring none is missed out. After SNMPWALK completes scanning, it automatically directs the results to be written on a notepad which can be saved, and viewed later. The following image shows the SNMPWALK results with the MIBs on the left and their corresponding values on the right.

clip_image012

From the above results, you can easily trace out the required MIB by looking for its corresponding values.

Don’t think for even a second that we’ve been resting on our laurels with the release of APM 4.2. In fact, I’m fairly certain the APM development team hasn’t slept a wink since they began plugging away on all the great new features we have in store for the SolarWinds APM–What’s on tap for vNext?.

In the meantime, all those sleepless nights of chugging Mountain Dew and Red Bull hasn’t gone unnoticed. Since the release of APM 4.2, the team has cranked out over 30 new expert templates, not to mention added support for over 15 new applications! These new applications range from database platforms such as Sybase and IBM’s DB2, to critical infrastructure applications like DNS and DHCP.  It doesn’t matter if you’re a small to mid-sized company or a fortune 500 enterprise, it’s very likely that you’re running one of the applications listed below in your organization.

Windows

Databases

Windows Media Server 9

Oracle Database (Updated)

Log Parser (PowerShell)

PostgreSQL

Microsoft Windows Update

Sybase ASE Database

Windows Server 2003 Domain Controller Security

MySQL Server

Windows Server 2008-2012 Domain Controller Security

IBM DB2

Microsoft BizTalk Server 2010 Adapters Performance Counters

IBM Informix

Microsoft BizTalk Server 2010 Host Throttling Performance Counters

Microsoft BizTalk Server 2010 Message Box and Orchestrations Performance Counters

Unix/Linux

Active Directory Group Policy

Log Parser (Perl)

Distributed File System (DFS)

DNS ISC/Internet Systems Consortium BIND

Windows DNS Server

DHCP ISC/Internet Systems Consortium

Windows DHCP Server (updated)

OpenLDAP

Citrix XenApp 6.0 Core Counters

 

Citrix XenApp 6.0 ICA Session

 

Citrix XenApp 6.0 Presentation Server

 

Citrix XenApp 6.0 Services

 

Microsoft Forefront Threat Management Gateway 2010

 

Microsoft Network Policy Server RADIUS Server

 

Microsoft Network Policy Server RADIUS Proxy

 

Microsoft Network Policy Server Events

 

The best part is you don’t need to wait until the next release of APM to start monitoring these applications. All of these new expert templates are available today and can be installed with just a few mouse clicks without ever leaving the APM web console.

To add any of these new templates click Settings in the top right of the APM web interface. Then, click APM Settings under the Settings category. From there click on Shared thwack Templates under Thwack Community.

Official

On the left side select Official from Select tag to filter by to the view only SolarWinds officially created expert templates. Then, select the templates using the checkbox next to the application name. Finally, click the green Import button. Now you can assign these official application templates to your nodes the same way you always have.

We’re continuously working on new application templates, so keep your eyes peeled for new templates in the “Application Monitor Templates” section of the Content Exchange on Thwack.com. We’d love to hear your feedback on these new application templates, as well as suggestions for new application templates. Please post this feedback in the comments section below.

Note: You will need a valid Thwack.com username and password to download content from the SolarWinds Thwack Content Exchange.

If you don't already own SolarWinds Application Performance Monitor, you can download a free 30 day evaluation and start monitoring any of these apps today. 

Did you know there are some hidden and not so hidden features in Toolset to improve your productivity, make your life easier and just maybe brighten your day?

 

EVENTS      
Let’s start with events. Did you know you can clear, export, and filter events? Exporting events is good for cases where you need to record an event, say to close a helpdesk ticket. You will probably use clearing and filtering of events most while researching recent or trending events.

 

1. Right click anywhere on the event grid to get access the event actions menu

 

2. Select the feature you would like to use clear, export, filter or change your event settings

 

clip_image002

 

 

 

TABS      
One thing that irritates me about tab browsing in Chrome and in Firefox is finding a specific tab when you have multiple tabs open. You can do this easily in Toolset. This comes in handy when you have more than a handful of tabs open and can no longer read the tab title.

 

1. Right click on a tab header in the explorer

 

2. Select show gadget

 

3. Choose which gadget to show (the gadget will be shown with a temporary highlight)

 

clip_image004

 

clip_image006

 

 

 

    
NEEDLE IN A HAYSTACK      
If you have a large number of devices, sometimes it can be a pain to locate a specific device or a handful with some specific characteristic. With “Group By” and “Filtering” options in the device manager you can elevate this problem.

 

1. Click the “Group By” or “Filtering” dropdowns

 

2. Select the option that best fits your needs (Group By > Status)

 

clip_image008

 

  
   
GOT FLAPPING?     
If your environment has a lot of flapping you might want to adjust how many bad ICMP polls happen before the Workspace Studio (WSS) starts to notify you that there may be a problem.

 

1. Shutdown Workspace Studio open the settings file. It should be found here:   
<Profile>\Local Settings\Application Data\SolarWinds\Dashboard\MainSettings.xml

 

2. If you don’t’ see the following setting you will need to enter it yourself:

 

<Setting Name="BadConsecutivePingsThreshold" Value="4" Type="System.Int32" />

 

3. Increase the number in the “Value” field to fit your need

 

4. Save and start Workspace Studio (WSS)

 

  
   
TO SNMP POLL OR NOT TO SNMP POLL      
Did you know you can adjust the settings to determine if the Workspace Studio (WSS) will SNMP poll a device that failed an ICMP poll? The default value ‘0’ means do not poll non-responders, but setting it to any other value means it will poll non-responders.

 

1. Shutdown Workspace Studio open the settings file. It should be found here:   
<Profile>\Local Settings\Application Data\SolarWinds\Dashboard\MainSettings.xml

 

2. If you don’t see the following setting you will need to enter it yourself:  
<Setting Name="PollNonResponders" Value="0" Type="System.Int32" />

 

3. Increase the number in the “Value” field to anything but zero

 

5. Save and start WSS

 

  
   
TELNET/SSH DEBUGGING      
If you are having problems with a Telnet/SSH session you can make a simple change so that Telnet/SSH tool will provide debugging information.

 

1. Shutdown Workspace Studio open the settings file. It should be found here:   
<Profile>\Local Settings\Application Data\SolarWinds\Dashboard\MainSettings.xml

 

2. If you don’t see the following setting you will need to enter it yourself:  
<Setting Name="DebugSSHFilename" Value="" Type="System.String" />

 

3. Put a valid filename in the “Value” field such as Value=”C:\MyCoolPath\myCoolFileName.txt”

 

4. Save and start WSS

 

  
   
NUMBER OF DEVICES SHOWN      
Did you know there is an undocumented way set the initial number of devices shown and the amount by which they are incremented when ‘Click to see more devices’ is selected? The current defaults are 200 at the start and increment by 100. Note: Workspace Studio must be completely shut down in order for the settings changes to take effect on re-start. This means the WSS itself as well as and command line instances or detached gadgets. Also remember the more devices you show the less responsive the tree will become (it has been tested up to 2000).      

 

1. Shutdown Workspace Studio open the settings file. It should be found here:   
<Profile>\Local Settings\Application Data\SolarWinds\Dashboard\MainSettings.xml

 

2. Add the following two lines to the MainSettings file anywhere between the opening and closing DashboardSettings node of the xml file:  
<Setting Name="DeviceTrees_MaxItemsVisibleAtStart" Value="500" Type="System.Int32" />   
<Setting Name="DeviceTrees_MaxItemsIncrement" Value="100" Type="System.Int32" />

 

3. Save and start WSS

 

  
   
THEMES      
Did you know you can change the theme of the entire UI in Toolset? I show you this with the trust you will never ever abuse this power and create an Aggies or Longhorn theme, but then again we do have a Hello Kitty theme which is close enough. J

 

1. Shutdown Workspace Studio open the settings file. It should be found here:   
<Profile>\Local Settings\Application Data\SolarWinds\Dashboard\MainSettings.xml

 

2. Save a copy of the original MainSettings.xml file in a safe place

 

3. Replace the current theme settings with the following Superman theme (see below for more):  
<Setting Name="GroupHeader_BackColor1" Value="16711680" Type="System.Int32" />   
<Setting Name="GroupHeader_BackColor2" Value="16711680" Type="System.Int32" />   
<Setting Name="GroupHeader_ForeColor" Value="16776960" Type="System.Int32" />   
<Setting Name="GroupHeader_BorderColor" Value="4210752" Type="System.Int32" />   
<Setting Name="Mdi_BackColor1" Value="4210943" Type="System.Int32" />   
<Setting Name="Mdi_BackColor2" Value="192" Type="System.Int32" />   
<Setting Name="Mdi_ForeColor" Value="16776960" Type="System.Int32" />   
<Setting Name="Mdi_BorderColor" Value="4210752" Type="System.Int32" />   
<Setting Name="ActiveTab_BackColor1" Value="16711680" Type="System.Int32" />   
<Setting Name="ActiveTab_BackColor2" Value="16711680" Type="System.Int32" />   
<Setting Name="ActiveTab_ForeColor" Value="16776960" Type="System.Int32" />   
<Setting Name="ActiveTab_BorderColor" Value="4210752" Type="System.Int32" />   
<Setting Name="PnlTitle_BackColor1" Value="16776960" Type="System.Int32" />   
<Setting Name="PnlTitle_BackColor2" Value="16776960" Type="System.Int32" />   
<Setting Name="PnlTitle_ForeColor" Value="255" Type="System.Int32" />   
<Setting Name="PnlTitle_BorderColor" Value="4210752" Type="System.Int32" />   
<Setting Name="ActivePnlTitle_BackColor1" Value="16711680" Type="System.Int32" />   
<Setting Name="ActivePnlTitle_BackColor2" Value="16711680" Type="System.Int32" />   
<Setting Name="ActivePnlTitle_ForeColor" Value="255" Type="System.Int32" />   
<Setting Name="ActivePnlTitle_BorderColor" Value="4210752" Type="System.Int32" />   
<Setting Name="XbarHdr_BackColor1" Value="8421631" Type="System.Int32" />   
<Setting Name="XbarHdr_BackColor2" Value="8421504" Type="System.Int32" />   
<Setting Name="XbarHdr_ForeColor" Value="16776960" Type="System.Int32" />   
<Setting Name="XbarHdr_BorderColor" Value="4210752" Type="System.Int32" />   
<Setting Name="XbarHotTrack_BackColor1" Value="4210943" Type="System.Int32" />   
<Setting Name="XbarHotTrack_BackColor2" Value="4210752" Type="System.Int32" />   
<Setting Name="XbarHotTrack_ForeColor" Value="16776960" Type="System.Int32" />   
<Setting Name="XbarHotTrack_BorderColor" Value="4210752" Type="System.Int32" />   
<Setting Name="XbarActiveHdr_BackColor1" Value="4210943" Type="System.Int32" />   
<Setting Name="XbarActiveHdr_BackColor2" Value="4210752" Type="System.Int32" />   
<Setting Name="XbarActiveHdr_ForeColor" Value="16711680" Type="System.Int32" />   
<Setting Name="XbarActiveHdr_BorderColor" Value="4210752" Type="System.Int32" />

 

4. Save and start WSS (you should see your new theme, which in this case is Superman)

 

clip_image010

 

  
   
   
   
   
More themes:

 

Hello Kitty

 

  <Setting Name="GroupHeader_BackColor1" Value="16752895" Type="System.Int32" />

 

  <Setting Name="GroupHeader_BackColor2" Value="15777984" Type="System.Int32" />

 

  <Setting Name="GroupHeader_ForeColor" Value="16711680" Type="System.Int32" />

 

  <Setting Name="GroupHeader_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="Mdi_BackColor1" Value="16768767" Type="System.Int32" />

 

  <Setting Name="Mdi_BackColor2" Value="16777215" Type="System.Int32" />

 

  <Setting Name="Mdi_ForeColor" Value="16711680" Type="System.Int32" />

 

  <Setting Name="Mdi_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="ActiveTab_BackColor1" Value="16752895" Type="System.Int32" />

 

  <Setting Name="ActiveTab_BackColor2" Value="16777215" Type="System.Int32" />

 

  <Setting Name="ActiveTab_ForeColor" Value="8388608" Type="System.Int32" />

 

  <Setting Name="ActiveTab_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="PnlTitle_BackColor1" Value="16772863" Type="System.Int32" />

 

  <Setting Name="PnlTitle_BackColor2" Value="15658734" Type="System.Int32" />

 

  <Setting Name="PnlTitle_ForeColor" Value="16711680" Type="System.Int32" />

 

  <Setting Name="PnlTitle_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_BackColor1" Value="16761087" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_BackColor2" Value="12632256" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_ForeColor" Value="16711680" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="XbarHdr_BackColor1" Value="16768767" Type="System.Int32" />

 

  <Setting Name="XbarHdr_BackColor2" Value="13158600" Type="System.Int32" />

 

  <Setting Name="XbarHdr_ForeColor" Value="16711680" Type="System.Int32" />

 

  <Setting Name="XbarHdr_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_BackColor1" Value="16752895" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_BackColor2" Value="12632256" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_ForeColor" Value="16711680" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_BackColor1" Value="16752895" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_BackColor2" Value="12632256" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_ForeColor" Value="8388608" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_BorderColor" Value="4210752" Type="System.Int32" />

 

    
     
Mint Sherbert

 

  <Setting Name="GroupHeader_BackColor1" Value="32768" Type="System.Int32" />

 

  <Setting Name="GroupHeader_BackColor2" Value="0" Type="System.Int32" />

 

  <Setting Name="GroupHeader_ForeColor" Value="15790288" Type="System.Int32" />

 

  <Setting Name="GroupHeader_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="Mdi_BackColor1" Value="14614494" Type="System.Int32" />

 

  <Setting Name="Mdi_BackColor2" Value="16777215" Type="System.Int32" />

 

  <Setting Name="Mdi_ForeColor" Value="16384" Type="System.Int32" />

 

  <Setting Name="Mdi_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="ActiveTab_BackColor1" Value="32768" Type="System.Int32" />

 

  <Setting Name="ActiveTab_BackColor2" Value="16777215" Type="System.Int32" />

 

  <Setting Name="ActiveTab_ForeColor" Value="15790288" Type="System.Int32" />

 

  <Setting Name="ActiveTab_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="PnlTitle_BackColor1" Value="15663086" Type="System.Int32" />

 

  <Setting Name="PnlTitle_BackColor2" Value="15658734" Type="System.Int32" />

 

  <Setting Name="PnlTitle_ForeColor" Value="16384" Type="System.Int32" />

 

  <Setting Name="PnlTitle_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_BackColor1" Value="12648384" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_BackColor2" Value="12632256" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_ForeColor" Value="16384" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="XbarHdr_BackColor1" Value="14614494" Type="System.Int32" />

 

  <Setting Name="XbarHdr_BackColor2" Value="13158600" Type="System.Int32" />

 

  <Setting Name="XbarHdr_ForeColor" Value="5605461" Type="System.Int32" />

 

  <Setting Name="XbarHdr_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_BackColor1" Value="10551200" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_BackColor2" Value="12632256" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_ForeColor" Value="5605461" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_BackColor1" Value="10551200" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_BackColor2" Value="12632256" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_ForeColor" Value="16384" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_BorderColor" Value="4210752" Type="System.Int32" />

 

 

 

Royal

 

  <Setting Name="GroupHeader_BackColor1" Value="8388736" Type="System.Int32" />

 

  <Setting Name="GroupHeader_BackColor2" Value="0" Type="System.Int32" />

 

  <Setting Name="GroupHeader_ForeColor" Value="15782128" Type="System.Int32" />

 

  <Setting Name="GroupHeader_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="Mdi_BackColor1" Value="10485920" Type="System.Int32" />

 

  <Setting Name="Mdi_BackColor2" Value="4473924" Type="System.Int32" />

 

  <Setting Name="Mdi_ForeColor" Value="15782128" Type="System.Int32" />

 

  <Setting Name="Mdi_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="ActiveTab_BackColor1" Value="8388736" Type="System.Int32" />

 

  <Setting Name="ActiveTab_BackColor2" Value="4473924" Type="System.Int32" />

 

  <Setting Name="ActiveTab_ForeColor" Value="15782128" Type="System.Int32" />

 

  <Setting Name="ActiveTab_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="PnlTitle_BackColor1" Value="16752895" Type="System.Int32" />

 

  <Setting Name="PnlTitle_BackColor2" Value="12632256" Type="System.Int32" />

 

  <Setting Name="PnlTitle_ForeColor" Value="4194368" Type="System.Int32" />

 

  <Setting Name="PnlTitle_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_BackColor1" Value="16744703" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_BackColor2" Value="4473924" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_ForeColor" Value="4194368" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="XbarHdr_BackColor1" Value="16768767" Type="System.Int32" />

 

  <Setting Name="XbarHdr_BackColor2" Value="13158600" Type="System.Int32" />

 

  <Setting Name="XbarHdr_ForeColor" Value="8934792" Type="System.Int32" />

 

  <Setting Name="XbarHdr_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_BackColor1" Value="16752895" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_BackColor2" Value="12632256" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_ForeColor" Value="8934792" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_BackColor1" Value="16752895" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_BackColor2" Value="6316128" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_ForeColor" Value="4194368" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_BorderColor" Value="4210752" Type="System.Int32" />

 

 

 

Royal Kitty

 

  <Setting Name="GroupHeader_BackColor1" Value="8388736" Type="System.Int32" />

 

  <Setting Name="GroupHeader_BackColor2" Value="0" Type="System.Int32" />

 

  <Setting Name="GroupHeader_ForeColor" Value="15782128" Type="System.Int32" />

 

  <Setting Name="GroupHeader_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="Mdi_BackColor1" Value="16768767" Type="System.Int32" />

 

  <Setting Name="Mdi_BackColor2" Value="16777215" Type="System.Int32" />

 

  <Setting Name="Mdi_ForeColor" Value="4194368" Type="System.Int32" />

 

  <Setting Name="Mdi_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="ActiveTab_BackColor1" Value="8388736" Type="System.Int32" />

 

  <Setting Name="ActiveTab_BackColor2" Value="16777215" Type="System.Int32" />

 

  <Setting Name="ActiveTab_ForeColor" Value="15782128" Type="System.Int32" />

 

  <Setting Name="ActiveTab_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="PnlTitle_BackColor1" Value="16772863" Type="System.Int32" />

 

  <Setting Name="PnlTitle_BackColor2" Value="15658734" Type="System.Int32" />

 

  <Setting Name="PnlTitle_ForeColor" Value="4194368" Type="System.Int32" />

 

  <Setting Name="PnlTitle_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_BackColor1" Value="16761087" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_BackColor2" Value="12632256" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_ForeColor" Value="4194368" Type="System.Int32" />

 

  <Setting Name="ActivePnlTitle_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="XbarHdr_BackColor1" Value="16768767" Type="System.Int32" />

 

  <Setting Name="XbarHdr_BackColor2" Value="13158600" Type="System.Int32" />

 

  <Setting Name="XbarHdr_ForeColor" Value="8934792" Type="System.Int32" />

 

  <Setting Name="XbarHdr_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_BackColor1" Value="16752895" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_BackColor2" Value="12632256" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_ForeColor" Value="8934792" Type="System.Int32" />

 

  <Setting Name="XbarHotTrack_BorderColor" Value="4210752" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_BackColor1" Value="16752895" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_BackColor2" Value="12632256" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_ForeColor" Value="4194368" Type="System.Int32" />

 

  <Setting Name="XbarActiveHdr_BorderColor" Value="4210752" Type="System.Int32" />

With our release Orion APM 4.2, we have added some awesome new features, and Josh Stephens and I can’t wait to show them off. These features are all added with the central theme of making your life easier. From supplying you with new ways to monitor applications to making it easier to work with the information you collect. During this 60 minute webinar we will be discussing:

  • Java Monitoring Capabilities such as JBoss, GlassFish, Apache Tomcat and more
  • New Expert Templates including SharePoint® 2010, Citrix™ XenApp 6.0, MySQL and many more
  • New Template Options
  • New Ways to Sort and Combine Statistical Data

 

This session will feature live product demonstrations of the features and we would like to make it as interactive as possible. Ask a lot of questions, we’d be happy to show you how it all works!

INTENDED AUDIENCE:

This webinar will be most useful to existing and new users of SolarWinds Orion APM or those thinking of deploying APM.

WHENThursday, October 27, 2011, 11:00 CDT

Click Here to register for this event. 

Title: VMworld US Takeaways, Insights and Best Practices

Link: http://www.solarwinds.com/resources/webcasts/vmworld-us-takeaways-insights-and-best-practices.html

Description:

Join SolarWinds for this special Geek Speak series webcast: You’ll learn why Virtualization Manager won the Best of VMworld 2011 Gold Award for Virtualization Management and how to solve the issues affecting you the most. 

We've all had the situation of a troublesome interface. In those cases, it's super helpful to know bandwidth at a granular level, especially when troubleshooting or making network changes. Real-Time Bandwidth Monitor is our newest free tool that is designed to help you keep an eye on those interfaces with configurable polling, with intervals down to every half-second. 

Here's the scoop: 

·        Monitor multiple interfaces simultaneously

·        See interface bandwidth usage by actual and percentage

 

·        View traffic in and traffic out on each interface

·        Set warning and critical thresholds and instantly see when usage is out of bounds

·        Specify data collection time frame or data point thresholds

·        Poll  at configurable intervals, as frequently as every half-second 

 

Like all our free tools, it's *free* and it only takes a jiffy to download it and get it installed and running. You can use Real-Time Bandwidth Monitor whenever you need to keep a close eye on an interface... or two. It's a generally handy tool to have around. 

We hope you'll try it out and send us some feedback or review it online. 

SeUM v1.0 was born just a few short months ago, and already the development team is plugging away on the next release. With lots of feedback from our Beta, RC, and Pre-release customers we drafted our “to-do” list for this release to address the most frequently requested features customers requested.

 
      
  • Account limitation support
  •    
          
    • Restrict users on a per-transaction or per-location basis      
       
    •   
       
  • Leverage the power of the public cloud  to address geographical dispersed monitoring needs
  •    
          
    • In-product integration of Amazon EC2 and Rackspace as deployment options for pre-configured remote players      
       
    •   
       
  • Provide alternative player communications method
  •    
          
    • Simplify SeUM remote player deployment by reducing/eliminating the need to change Firewall/NAT Policies.      
       
    •   
       
  • Support interacting with Adobe Flash and Microsoft’s Silverlight Technologies within the SeUM Recorder and SeUM player.
 

PLEASE NOTE:  We are working on these items based on this priority order, but this is NOT a commitment that all of these enhancements will make the next release.  We are working on a number of other smaller features in parallel.   If you have comments or questions on any of these items (e.g. how would it work?) or would like to be included in a preview demo, please let us know!

Filter Blog

By date: By tag: