I have a script that logs into a server and pings several other servers in order to verify IP path between servers.
The output can look like this, if good pings:
Response from 1.1.1.4;_id=0, vlan_prio=0): seq=0 time=91.547 ms.
Response from 1.1.1.4;_id=0, vlan_prio=0): seq=1 time=61.176 ms.
Response from 1.1.1.4;_id=0, vlan_prio=0): seq=2 time=60.904 ms.
I found a thread in this forum (now closed) that allowed for pattern matching on the "packet loss" and to print the previous line (so my log will show IP address as well as result, since this system doesn't include them on the same line.)
(Thanks Marco!)
But I need an additional snippet in there somehow to EXCLUDE lines that show "0% packet loss"...i.e. only match on lines that show some kind of packet loss. Not 0% packet loss.
In a nutshell, I need to work out how to return the last matching pattern from an awk //,// search. I can bring back the first, but am unsure how to obtain the last, and a simple tail won't work as the match could be over multiple lines.
Secondly I would like some way of pattern matching, a... (10 Replies)
Dear Team,
How do we match two patterns on the same line using awk?Are there any logical operators which i could use in awk like awk '\gokul && chennai\' <filename>
Eg:
Input file:
gokul,10/11/1986,coimbatore.
gokul,10/11/1986,bangalore.
gokul,12/04/2008,chennai.... (2 Replies)
Hi,
How can I tell awk to print all lines/columns if column number 5 contains the word Monday?
I have tried
nawk -F, '$5==Monday' OFS=, myfile > outputfile
but that doesn't work (I am a newb!!)
Thanks, (7 Replies)
Find bumblebee and Megatron patterns (input2) in input1.
If it is + read input1 patterns from Left to Right
if it is - read input1 patterns from Right to Left
Y= any letter (A/B/C/D)
input1
c1 100 120 TF01_X1 + AABDDAAABDDBCADBDABC
c2 100 120 TF02_X2 - AABDDAAABDDBCBACDBBC... (2 Replies)
Dear Friends,
I have a flat file. To pick certain details we have written an awk where we are facing difficulty.
Sample of flat file.
line 1
line 2
line 3
line 4
line 5
line 6
line 7
line 8
line 9
line 10
line 11
line 12
line 13
line 14 (Matching pattern "Lkm_i-lnr:"can be... (4 Replies)
Hello all,
I am trying to sort thru a database and print all the customers whose first names are only four characters. I just want to pull the first name only from the database.
the database records appear like this in file:
Mike Harrington:(510) 548-1278:250:100:175; first is name Mike... (4 Replies)
Hi,
I am still a beginner on shell scripting so please bear with me.
What i am trying to do is filter my logfile based on some ID on field 24 which is defined in array. The filter result output will be moved to my log folder with the same name. The problem is when not using loop, this command... (2 Replies)
can somebody provide me with some ksh code that will return true if my the contents in my variable match anyone of these strings ORA|ERROR|SP2
variable="Error:ORA-01017: Invalid username/password; logon denied\nSP2-0640:Not connected"
I tried this and it does not seem to work for me
... (3 Replies)
Hi I am trying to find a pattern match with column one containing 3 numbers.
input file tmp.lst
abcd456|1|23123|123123|23423
kumadff|a|dadfadf|adfd|adfadfadf
xxxd999|d|adfdfs|adfadf|adfdasfadf
admin|a|dafdf|adfadfa|||
output file tmp4.lst
abcd456|1|23123|123123|23423... (3 Replies)
I have two files, want to compare file1 data with file2 second column and print line which are not matching. Need help in matching the pattern, file2 second column number can be leading 0 or 00 or 000.
Example:
file1
1
2
3
file2
a,0001
b,02
c,000
d,01
e,2
f,0005
Expected output:... (20 Replies)
Discussion started by: vegasluxor
20 Replies
LEARN ABOUT DEBIAN
smokeping_probes_dismanping
Smokeping_probes_DismanPing(3) SmokePing Smokeping_probes_DismanPing(3)NAME
Smokeping::probes::DismanPing - DISMAN-PING-MIB Probe for SmokePing
SYNOPSIS
*** Probes ***
+DismanPing
offset = 50%
pings = 15
step = 300
# The following variables can be overridden in each target section
ownerindex = smokeping
packetsize = 56
pinghost = pinger@router.example.com # mandatory
pingsrc = 192.0.2.9
# [...]
*** Targets ***
probe = DismanPing # if this should be the default probe
# [...]
+ mytarget
# probe = DismanPing # if the default probe is something else
host = my.host
ownerindex = smokeping
packetsize = 56
pinghost = pinger@router.example.com # mandatory
pingsrc = 192.0.2.9
DESCRIPTION
Uses the DISMAN-PING-MIB to cause a remote system to send probes.
VARIABLES
Supported probe-specific variables:
offset
If you run many probes concurrently you may want to prevent them from hitting your network all at the same time. Using the probe-
specific offset parameter you can change the point in time when each probe will be run. Offset is specified in % of total interval, or
alternatively as 'random', and the offset from the 'General' section is used if nothing is specified here. Note that this does NOT
influence the rrds itself, it is just a matter of when data acqusition is initiated. (This variable is only applicable if the variable
'concurrentprobes' is set in the 'General' section.)
Example value: 50%
pings
How many pings should be sent to each target. Note that the maximum value for DismanPing MIP is 15, which is less than the SmokePing
default, so this class has its own default value. If your Database section specifies a value less than 15, you must also set it for
this probe. Note that the number of pings in the RRD files is fixed when they are originally generated, and if you change this
parameter afterwards, you'll have to delete the old RRD files or somehow convert them.
Example value: 15
Default value: 15
step
Duration of the base interval that this probe should use, if different from the one specified in the 'Database' section. Note that the
step in the RRD files is fixed when they are originally generated, and if you change the step parameter afterwards, you'll have to
delete the old RRD files or somehow convert them. (This variable is only applicable if the variable 'concurrentprobes' is set in the
'General' section.)
Example value: 300
Supported target-specific variables:
ownerindex
The SNMP OwnerIndex to use when setting up the test. When using VACM, can map to a Security Name or Group Name of the entity running
the test.
By default this will be set to
Example value: smokeping
packetsize
The packetsize parameter lets you configure the packet size for the pings sent. The minimum is 8, the maximum 65507. Use the same
number as with fping if you want the same packet sizes being used on the network.
Default value: 56
pinghost
The (mandatory) pinghost parameter specifies the remote system which will execute the pings, as well as the SNMP community string on
the device.
Example value: pinger@router.example.com
This setting is mandatory.
pingsrc
The (optional) pingsrc parameter specifies the source address to be used for pings. If specified, this parameter must identify an IP
address assigned to pinghost.
Example value: 192.0.2.9
AUTHORS
Bill Fenner <fenner@research.att.com>, Tobi Oetiker <tobi@oetiker.ch>
NOTES
MENU NAMES
This probe uses the menu name of a test as part of the unique index. If the menu name is longer than 32 characters, the last 32 characters
are used for the index. Collisions are *not* detected and simply cause one test's results to be used for all colliding names.
CONFIGURATION
This probe requires read/write access to the pingCtlTable. It also requires read-only access to the pingResultsTable and the
pingHistoryTable. The DISMAN-PING-MIB is structured such that it is possible to restrict by pingCtlOwnerIndex. This probe uses a
pingCtlOwnerIndex of "SP on hostname" as ownerindex by default; use ownerindex to configure this if needed.
SAMPLE JUNOS CONFIGURATION
This configuration permits the community "pinger" read-write access to the full DISMAN-PING-MIB, but only when sourced from the manager at
192.0.2.134.
snmp {
view pingMIB {
oid .1.3.6.1.2.1.80 include;
}
community pinger {
view pingMIB;
authorization read-write;
clients {
192.0.2.134/32;
}
}
}
SAMPLE CONFIGURATIONS NOTE
This configuration allows the "pinger" community full access to the DISMAN-PING-MIB. There is information in the description of
pingCtlOwnerIndex in RFC 4560 (<http://tools.ietf.org/html/rfc4560>) about using the vacmViewTreeFamilyTable to further restrict access.
The author has not tried this method.
2.6.8 2013-03-17 Smokeping_probes_DismanPing(3)