Bandwidth Gauge & Community Strings

I've searched and can't find anything like my problem, so I'll ask the forum...

I'm trying to open bandwidth gauges from various web page views of Orion. What works on one view doesn't work on others.

I can successfully open a bandwidth gauge from the Top 10 view, but not from the Node Detailed view. I've made modifications to neither page. I've tried several interfaces on several routers, same results.

Under Top 10 view, I can open a gauge, and it will ask for my community string (if not defined), and open the gauge. Looking at the gauge's properties sees the communitry string I entered. Looking at (right click hyperlink) Settings sees the community string I entered. So, the Toolset is "seemingly" properly integrated.

I go to the Node Detail view and try to open a bandwidth gauge for the same interface, it doesn't ask for a community string (whether it's been defined or not), it opens the gauge, but it times out. Looking at the gauge's properties finds a community string that is about 36 characters long and looks random. Looking at the (right click hyperlink) Settings finds the community string I entered on the Top 10 view (or blank if it wasn't already defined from the Top 10 view).

I'm running Bandwidh Gauges v9.2.0.1 and Orion v9.1.0.

Any info would be appreciated. Thanx!

Find more posts tagged with

community_string

orion_8.5

orion_9.1

engineers_toolset_v9.2

bandwidth_gauges

Accepted answers

All comments

tdanner

So you get the toolset's right-click menu in both places, but the gauges only work when launched from top 10?

If you're comfortable with html, you could do a view-source on the two web pages and find the links (<a href> tags) for the interfaces. There should be some special attributes for the node's ip address, the interface index, etc. Do they look similar?

MWeeks

Yes, the toolset's right click menu appears on both views.

This code from Top 10 works (X-ed out possible private info):

<td class="Property"><a IP="172.XXX.YYY.ZZZ" NodeHostname="RTR_NAME" Community="GUID{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}" IFName="Serial0/1" IFIndex="2" href="">thwack.solarwinds.com/.../View.asp </td>

This code from Node Details does not:

<td class="Property"><a href="">thwack.solarwinds.com/.../InterfaceDetails.aspx IP="172.XXX.YYY.ZZZ" NodeHostname="RTR_NAME" Community="XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" IFName="Serial0/1" IFIndex="2">Serial0/1</a> </td>

The community string I've X-ed out is what appears in the gauge properties window of the Node Details. Not sure where it comes from unless it's my router's community string that has been encrypted somehow (that's why I X-ed it out). But it's the same on both views (one is all upper case, the other all lower case).

tdanner

This is a bug.

To avoid putting the actual community string on the web, we replace it with a randomly generated GUID. The Toolset tools will prompt you for the actual community string the first time, then remember the association between the GUID and the string you type in so they don't need to prompt you again (for that node) next time.

The problem is that the Community= attribute should have GUID{...} around the GUID (as it does in the first link).

I'll get this entered into our bug tracking system.

MWeeks

Okay, great. Let me know if you need any more info or the files for your bug report.