04-08-2011 04:34 AM
Hi,
Trying to set up an Operation form:
Monitor> Performance Settings> IPSLA> Operations:
When configuring the IPSLA UDP Jitter Operation, you must specify a target port number. But you can not specify a source port number used by this Operation.
To be sure that the UDP Jitter Operation hits the right QoS queue you need to controll both source and target port numbers.
Looking at the IPSLA config set up on the source device using LMS 4.0:
Entry number: 21340
Owner: ipm|NO000010SCWK02
Tag: F495_no005010nr
Type of operation to perform: udp-jitter
Target address/Source address: 10.20.142.1/172.20.21.73
Target port/Source port: 16475/0 !!!!!! Here the source port is set to "0" Zero.
Operation timeout (milliseconds): 5000
Codec Type: g729a
Codec Number Of Packets: 1000
Codec Packet Size: 32
Codec Interval (milliseconds): 20
Advantage Factor: 0
Type Of Service parameters: 0x0
Verify data: No
Vrf Name:
Control Packets: enabled
Schedule:
Operation frequency (seconds): 60 (not considered if randomly scheduled)
Next Scheduled Start Time: Start Time already passed
Group Scheduled : FALSE
Randomly 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
Enhanced History:
This result in traffic going in different QoS queues depending on the access-list used for classification of the traffic and mess up the graphs.
So my question is: Is there any way to specify the Source port number in a operation using LMS 4.0?
04-10-2011 09:17 AM
No, there is no way to specify the source port for an operation in IPM. You can manually adjust the QoS parameters (either ToS or DSCP) when defining the operation. You can also create the collector manually on the device, and then import it into IPM using the "ipm" command line tool:
NMSROOT/bin/ipm importcollector -u admin -p admin -source 10.1.1.1 -oper UDPJitter
09-08-2015 11:04 PM
this post could be redundant , but wondering if anyone had encountered a reporting problem
LMS 4.0 - 300 device count- currently managing around 100 odd devices
Configured 10 set of qos class IPSLA probes from each site to two responders
[ 5 per responder] - total no of probes to 235 - polling interval set to 5min-
worked fine for couple of months, then system started reporting error - for Daily, Weekly or monthly - Error- No data available - Hourly & minute stats/graphs is ok but the archiving feature stopped,
Even IP SLA system summary stopped working -
Server & service restarted, no change
Any idea why
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide