nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

I need interfaces to capture the IP address assigned to them.

smartd

I would like any TCP addresses assigned to an interface to be captured during discovery, and there be a detailed page resource that would show the interface and assigned IPs.

This is different that IPAM, which I also own, that gives devices assigned to IP addresses.

Does this exist? Its hard to believe that it doesn't.

-=Dan=-

Find more posts tagged with

resources

Accepted answers

All comments

lchance

Yep - I agree - it's hard to believe it doesn't exist.

I have to do it using the Universal Device Poller and create it as a Table in the Node Details View. It's not pretty but that does work. Have you tried using UnDP yourself?

Congo

lchance,

What OID are you using for your UnDP?

smartd

Ok, I see that OID 1.3.6.1.2.1.4.20 gives the table of ipAddresses, but uses the interface index number. What's needed is to lookup the interface name in 1.3.6.1.2.1.2.2. Is there anyway in the existing resources to see the interface index number? How did you work out getting interface names?

-=Dan=-

lchance

As for interface names i used the ifDescr.

In the Node Details view UnDP table is slightly staggered but it works out seeing those with IP addresses.

smartd

I've got a single view that shows the IP address and the Interface Number, then another table that shows Interface number, and name. I'd like to do a JOIN on the two tables.

-=Dan=-

netlog

ip flow ingress infer-fields

If the Source IP address and Destination IP address are not seen in IP Flow
* The packets are blocked by an ACL.
* The packets are being process switched.
* Multicast traffic
* Packets destined for the router
* Tunnels (IPIP, GRE, IPSEC, L2TP) & WCCP
* Static route to null0
* DstIf is NULL when the traffic is dropped because of CAR.

ecklerwr1

I've been puzzled for a while now over this.... how could you NOT include the IP address of an interface on the details page! Is there ne real technical reason why this is??? I end up having to log into routers get the IP's when I need them quickly because NPM interface details doesn't show it... geeze.

Questionario

Yea...

I'd really like to see this integrated into Orion NPM but in a more advanced manner so that it would also be detected if one of those IPs were to be unreachable (for all I care also use up a node license for those IPs that you choose to monitor).

I would already like to implement it like this but I cannot just run SQL-updates like this all the time... also these IPs would not be up to date...