↧
Infoblox Details
↧
Current+Active+Alerts+by+Name.xml
↧
↧
Orion Polling Engine Load
↧
linuxatemyram
↧
Alerts that are giving me issues
uploads for thread Alert Reset Actions not firing
↧
↧
http to https redirection using URL rewrite
Switching over an Orion website from http to https is relatively simple. But to have it automagically redirect from http to https is a bit more involved.
1) Orion http to https
a) UPDATE dbo.Websites
SET SSLEnabled=1
WHERE WebSiteID=1
b) Create a CSR and have the client provide the certificate
c) Install the certificate
d) stop the default site (also change the binding to 8080 - just to be safe). create bindings for Orion for https using the imported certificate
2) http to https redirection using URL Rewrite
a) install URL rewrite for IIS and add a rule for redirection.
b) Configure rule
That's it.
One thing I have noticed is that if you're using additional web servers behind a load balancer - google maps may not work properly. You will have to rewrite the google maps code to use https.
Thanks
Amit
Loop1 Systems
↧
Routing Neighbor state view resource.. valid for NPM 10.7
I'm not sure if this has already been covered somewhere else and I know there are quite a few posts related to this but there aren't many resources in the content exchange.. This resource will display the current BGP peer sessions that are not Established. NPM now comes with routing neighbor polling which also includes OSPF and EIGRP. I have selected BGP as I already have another IGRP monitoring resource set up. The resource below is displayed on our NOC view as well and provides a great glance into your managed network. Now to the small bits.
The routing information is polled every 180 minutes by default and neighbors are also kept for 30 days by default. you can check your retention settings by running the following query on your sql server's NetPerfMon DB:
select * from Settings where SettingID like '%rout%'
and you will get your retention periods for flaps/neighbors/default route flaps and table polling intervals.
you will see that on the NPM_settings_routing neighbor_retain_days set. Now before we go any further I'll say that I had to open a ticket with Solarwinds on this because there is no easy way of figuring this all out and they instructed me to modify the retention periods as well as check/change db maint. schedules. If you are unsure about any of these settings please ask a member of the solarwinds support team or even a SCP to help.
UPDATE Settings SET CurrentValue=3 WHERE SettingID='NPM_Settings_RoutingNeighbor_Retain_Days' <-- change the #3 to whatever amount of days you'd like the retention to be set at for the routing neighbor retention.
The below query works just fine with the exception that it will show you ALL of the removed bgp peers as they will stay in the tables until otherwise stated. I say fine because if there is a BGP peer that goes down or is in any other state but Established it will show up and when the neighbor is Established again the peer information will be removed from this resource. We'll go a little further and just check to see the information that you're looking for actually exists..
###############
SELECT
dns,
rn.autonomoussystem,
NeighborIP,
rp.DisplayName,
rpsm.displayname,
rn.lastchange
FROM NPM_RoutingNeighbor rn
LEFT JOIN NPM_RoutingProtocolStateMapping rpsm
ON rn.ProtocolID=rpsm.ProtocolID
AND rn.ProtocolStatus=rpsm.ProtocolStatus
left join npm_routingProtocol rp on rn.ProtocolID=rp.ProtocolID
left join Nodes on rn.NodeID=nodes.NodeID
where rn.protocolstatus <5
order by rn.lastchange desc
###############
It's important to note that an understanding of the different stages/states of the individual routing protocols as we're querying multiple tables to form this information. The above returns all of the peers that are not in an Established state. Even if a peer is coming up and going through the connection process it would be listed. if we then formatted the query for swql(below) then you could use this as a resource as is but you'll find that your retention periods will come into play as listed above.
This is the SWQL for your resource.
SELECT
dns,
rn.autonomoussystem,
NeighborIP,
rp.DisplayName,
rpsm.displayname as "status",
rn.lastchange
FROM orion.routing.Neighbors rn
LEFT JOIN orion.routing.RoutingProtocolStateMapping rpsm
ON rn.ProtocolID=rpsm.ProtocolID
AND rn.ProtocolStatus=rpsm.ProtocolStatus
left join orion.routing.RoutingProtocol rp on rn.ProtocolID=rp.ProtocolID
left join orion.Nodes on rn.NodeID=nodes.NodeID
where rpsm.orionstatus !=1 <------ this !=1 means that in the routingprotocolstatemapping and if you query only the rspm table you'll see 1 is the FULL and ESTABLISHED # for both BGP and OSPF and anything else will be shown.
order by rn.lastchange desc <------ last time that the neighbors state changed.
####################
now we have the resource up there are a few things to go over.. There are two things(one listed above) which will impede this resource from displaying information properly and acting as it should. 1. is your retention time. Mine is currently set to 3 days as I don't really want to know about peers that have been removed/deleted from our network and quite frankly if a neighbor has been down for 3 days then there's more of a problem at hand. 2. check your database maintenance settings as this will also come into play. It's important to also have a regular maint. schedule to make sure the tables/views don't have any kind of stale information.
you can even go further and get the resource to display more information but this is just the starter. if anyone has questions let me know. It does sound like Solarwinds is looking into having this sort of setup as a 'feature request' as i think everyone would benefit from this in one way or another.
hope this proves helpful to others.
↧
NimbleStorage.UnDP
↧
Ruckus VS100.poller
↧
↧
Credentials Used By WMI Nodes
↧
GNS3 to SolarWinds NPM Integration Guide
↧
What We're Working on for NPM (Updated January 7th, 2016)
Since the release on NPM 11.5 we've been hard at working building the next round of exciting functionality and improvements in existing functionality. I'm pleased to share the following list of items we're working on:
- Updated UI Look and Feel - The UI is receiving some love this release, spanning across NPM, SAM, VMAN, and the other Orion based products.
- Deep Visibility into F5 load balancers - Covering things like connection counts by VIP and server. NPM F5 infoFEATURE REQUEST - F5 Load Balancers - Show Wide IP status, GTM Server List, etc - Case #448234
- Improved monitoring for Cisco Switch Stacks (3750, 3850, 2960S) - Covering things like stack master, stack ring health, enumerating members, tracking member changes, per member hardware health, and so on. Cisco Stack monitoring
- NetPath - Automatically discovers and monitors network paths for your on-premise, hybrid, and cloud-based applications (such as Salesforce.com). Provides multi-path visibility and hop-by-hop performance metrics so you can quickly identify and isolate network issues that are impacting your users.
- ServiceNow Integration - Automated ServiceNow incident creation, update, and closure out of the box. ServiceNow Integration
- Faster and web based simplified product upgrades and installation of hot fixes
- Integrated High Availability Engine
- Improvements performance of single poller (up to 4x) and website loading time decrease.
- Unmanage behavior improvements - Unmanage reason (like shutdown tracker in Windows 2008)Silence Alerts While Still MonitoringUnmanage reason (like shutdown tracker in Windows 2008)Show 'Unmanaged' durationSilence Alerts While Still Monitoring
Ongoing Initiatives:
- Real Multi-tenancy support
- Single page integration between NPM and NTA.
- New "small" remote poller.
↧
Monitoring 101 ebook
↧
↧
Wireless Client Connection Report
↧
NPM_silent_installer.zip
↧
Current - Hardware Status with Problems 11.5.OrionReport
↧
Bulk Node Name/Caption Change
I've seen this needed a few times here and with various clients so I find a spreadsheet similar to this comes in handy.
This spreadsheet can be used to create the SQL update queries to bulk update node names in the SolarWinds database.
Note: This query will only work on the newer Orion database structure (NPM 11.5+, SAM 6.2+, NCM 7.4+) as it references the 'NodesData' table. For older versions, change the table to 'Nodes'.
1. Get a list of the node captions and IP addresses that you need to update as two columns. There are a few ways to do this but try one of the below:
- Generate a report in the report writer - select the caption/nodename and IP address fields.
- Run a SQL query on the database (Using either SQL Management Studio or Database Manager on the SolarWinds server).
SELECT Caption, IP_Address FROM [dbo].[Nodes]
- Once you have your list, update the list with your new captions as well as any new IP addresses.
2. If you need to import these nodes into SolarWinds, run a discovery and import all of the nodes using the IP address list (manually add the nodes that don't respond as the discovery will only find your up nodes).
3. Use the attached spreadsheet to generate the SQL queries that you can use to update the database with the desired names (matching on IP address). Paste the captions and IP addresses into columns A and B. Column D contains the SQL queries.
4. Backup your SolarWinds database.
5. Paste the queries back into SQL Management Studio or Database Manager and execute to update the node names. E.g.
UPDATE NodesData SET Caption = 'Fred' WHERE IP_Address = '1.2.3.4' UPDATE NodesData SET Caption = 'Testname' WHERE IP_Address = '1.1.1.1'
Hope this helps!
Steve
↧
↧
NODES_Currently_Down_with_Duration_.OrionReport
↧
Using Custom Properties sending Alert emails
After receiving lots of queries i will try to explain in screen shots what steps needs to take if you wish to use custom properties logic to send email alerts to respective location / or team responsible for that node and group.
Basically when you have bunch of Nodes and you just wanted to send emails to the related department / Engineering Team only
Or You may have monitoring nodes for multiple customers where you would like to send emails to related customer for the nodes for that customer /
This post can help in order to configure .
Step #1 Creating Custom Property
Start with Custom properties
Settings > manager custom properties.
Add Custom Properties
Leave it blank and Submit
Step #2 Assigning email to the nodes
Go to Settings Manage Nodes.
(Select multiple Node you wish to assign the email ) and click Edit Properties.
Now assign the email you wish to assign so all the alerts will be sent to respected email for these nodes .
And Submit to save changes.
Step #3 Using Custom property name under Alert Trigger Condition
Now in Alert use the custom property name to send the email for required email address for each node.
Select the Alert you wish to Edit and Edit Trigger Action > Send an email /page.
Add Trigger Action
When the alert will trigger it will use the email you have assigned to the Node.
***** Adding CC you can create more custom properties to include CC emails such as an example below ****
${Email}
${EmailCC}
PLEASE NOTE:- THIS SOLUTION WILL NOT WORK FOR THE GROUPS
↧
SQL Jobs
↧
