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

DHCP Monitor Source Address?

I've just installed 3.0 and have been playing with it for a little while. This will probably be the first of many posts. But I'll start with this one.

The wizard does not allow you to specify a source address for DHCP monitors. In my case it defaulted to the IP on Loopback 0 for which a scope does not exist on our DHCP server. I've configured these manually for now but the wizard really should have this under the "advanced" tab.

Find more posts tagged with

ip_sla

cisco

Accepted answers

macnugetz

warbird,

We made changes in 3.1 that now allow you to set the source IP for each operation vs. globally on the node as derhally described. You can do this for existing operations, as well as newly created ones.

HTH,

Craig

All comments

derhally

By default we use the ip address that Orion knows about. We do allow you to specify the source ip address by editing the node properties in the ip sla node admin area.

If you are on the IP SLA summary view, click on IP SLA Manager Settings
Click on Manage IP SLA Nodes
Check the node you want to change the ip address of
Click "Edit Node" in the toolbar

You can now specify the Source IP Address. This will set the source IP Address for any operations created on that device.

I'm going to assume you would like to be able to set it per operation instead of just having it as a global setting?

kahmeelyon

By default we use the ip address that Orion knows about. We do allow you to specify the source ip address by editing the node properties in the ip sla node admin area.
If you are on the IP SLA summary view, click on IP SLA Manager Settings
Click on Manage IP SLA Nodes
Check the node you want to change the ip address of
Click "Edit Node" in the toolbar
You can now specify the Source IP Address. This will set the source IP Address for any operations created on that device.
I'm going to assume you would like to be able to set it per operation instead of just having it as a global setting?

Thanks! The only thing I have to say here is that it's not obvious that you can click "Manage IP SLA Nodes". It looks more like a heading.

kahmeelyon

Well that didn't seem to solve the problem and I'm not sure why. I don't think it's a Solarwinds issue. Has anyone got this to work? On the Cisco side I only get "Internet Errors":

a1h03c#sh ip sla monitor collection-statistics
Entry number: 40000
Start Time Index: 11:32:02.827 EDT Wed Sep 30 2009
Number of successful operations: 0
Number of operations over threshold: 0
Number of failed operations due to a Disconnect: 0
Number of failed operations due to a Timeout: 0
Number of failed operations due to a Busy: 0
Number of failed operations due to a No Connection: 0
Number of failed operations due to an Internal Error: 56
Number of failed operations due to a Sequence Error: 0
Number of failed operations due to a Verify Error: 0

Here's the config:

SA Agent, Infrastructure Engine-II

Entry number: 40000
Owner: SW.IpSla.A1PNMS01.SolarWinds
Tag:
Type of operation to perform: dhcp
Target address/Source address: 172.29.210.100/172.29.120.1
Operation timeout (milliseconds): 36000
Dhcp option:
Schedule:
    Operation frequency (seconds): 60
    Next Scheduled Start Time: Start Time already passed
    Group Scheduled : FALSE
    Life (seconds): Forever
    Entry Ageout (seconds): 3600
    Recurring (Starting Everyday): FALSE
    Status of entry (SNMP RowStatus): Active
Threshold (milliseconds): 5000
Distribution Statistics:
    Number of statistic hours kept: 2
    Number of statistic distribution buckets kept: 1
    Statistic distribution interval (milliseconds): 20
History Statistics:
    Number of history Lives kept: 0
    Number of history Buckets kept: 15
    History Filter Type: None

The address 172.29.120.1 is on a VLAN interface on the closet switch. There is a scope for 172.29.120.0/24 on the DHCP server.

Any help on this is appreciated!

derhally

I would try using the "debug ip sla monitor error" command to see if it can shed some more light on the Internal Errors.

The syntax for it would be

debug ip sla error [operation-number]

once you are done debugging it you can disable debugging by running

no debug ip sla error [operation-number]

macnugetz

Thanks for the feedback, kahmeelyon... good stuff. We understand that this is not obvious, and are looking at how to make the process of setting the source IP a little easier in a future release.

Question... would you ever need to set different source IP's for different operations on the same node? Currently you can set the IP per node, but it will be the same for every operation created on that node.

Thanks!

kahmeelyon

Question... would you ever need to set different source IP's for different operations on the same node? Currently you can set the IP per node, but it will be the same for every operation created on that node.

Yes! For instance, I might want to use a user VLAN interface as the source for DHCP queries. But for VoIP I want to user a different interface because the routing paths are different. I can think of lots of other examples as well. Right now I'm doing everything manually. I believe that source IP should be part of the wizard (under advanced?) for each type of operation.

glenjohnson

Question... would you ever need to set different source IP's for different operations on the same node? Currently you can set the IP per node, but it will be the same for every operation created on that node.

Okay, here's another permutation of this same issue (setting the source ip-address for operations). I use VRFs, to keep management and customer traffic separate (from a routing point of view). To simplify the cisco configuration -- and also the IOS doesn't support vrf for dhcp ip sla operations -- the customer interfaces (from which ip sla operations originate) are configured as the default VRF (e.g. no "ip vrf forwarding ..." statement applied). However Orion IP SLA insists on setting a source address per operation -- which causes the cisco ip sla operation to fail, as the routing for the address it chooses has no route. It's great we can specify the vrf, but .... maybe the best Orion IP SLA "default" source address is <nothing> -- same as the cisco default, in the config term cli.

warbird

This does not appear to change already existing operations?

By default we use the ip address that Orion knows about. We do allow you to specify the source ip address by editing the node properties in the ip sla node admin area.
If you are on the IP SLA summary view, click on IP SLA Manager Settings
Click on Manage IP SLA Nodes
Check the node you want to change the ip address of
Click "Edit Node" in the toolbar
You can now specify the Source IP Address. This will set the source IP Address for any operations created on that device.
I'm going to assume you would like to be able to set it per operation instead of just having it as a global setting?

macnugetz

warbird,

HTH,

Craig