Sponsored Content
Full Discussion: network madness
Special Forums IP Networking network madness Post 27584 by cubicle^dweller on Wednesday 4th of September 2002 01:05:38 AM
Old 09-04-2002
the ports are fine ... thanks for the link ... is it becoz of the distance .. there may be packet dropping ? its abt 125 meters ...
 

8 More Discussions You Might Find Interesting

1. Programming

Help in developing a Network Appliation to monitor pc in a network

I am developing a Network Appliation to monitor computers in a network. Specs are App monitors the current web page viewed in each system App also can shutdown the computer in the network App can show all process run by each computer in the network I am now confused how to start my... (2 Replies)
Discussion started by: valaparambil88
2 Replies

2. IP Networking

ssh server is attachable from local network not from another network

hello i have a ubuntu ssh server that i can acess from any of my comnputers but only if they are on the same wireless network as the server. i tested trhis my tehtehring my samsung blackjack to my windows partition and installing openssh to windows it works when windows is on the wireless but no... (1 Reply)
Discussion started by: old noob
1 Replies

3. Shell Programming and Scripting

2 versions, 1 script (A tale of madness.)

So, I have a machine running solaris (x86) and it has two different versions of Math::BigInt installed on it. The older version is 1.77. The newer version is 1.87 (via activeperl). When I run my code, one of the modules I use needs at least version 1.78. Somehow, it defaults to looking at the... (5 Replies)
Discussion started by: mrwatkin
5 Replies

4. What is on Your Mind?

Interview madness

A discussion elsewhere got me thinking: What where the most insane/amusing/strange interview questions or answers you got/gave? Not overly technical stuff, but questions that made you go "Huh?" (And keeping with this forums main Idea: "No technical Q&A") I'll start... (6 Replies)
Discussion started by: pludi
6 Replies

5. Solaris

configure zones to have different network interface and network

i need to configure a zone to use different interface (bge2) than global and have connected to completely different network switch & to use its own defaultrouter and hosts file .. is it possible ..if so ..how ? Thanks (9 Replies)
Discussion started by: skamal4u
9 Replies

6. UNIX and Linux Applications

Access to network interface (Mac-network)

Hi, I'm a italian student. For my thesis I develop a gateway with protocol 6lowpan. For that I must access to network interface to develope my personal stack based on standard 802.15.4. Can you help me? I need an explanation for that. (0 Replies)
Discussion started by: berny88
0 Replies

7. Solaris

No network cable But Network interface is UP and Running

I've one Netra 240 After changing main board and system configuration card reader, Network is not accessible any more, Network interfaces are always UP and Running even when there is no cable connected to Network interfaces. I tried to restart and plumb/unplumb with no luck. ifconfig -a... (7 Replies)
Discussion started by: samer.odeh
7 Replies

8. Red Hat

Network becomes slow and return fast only after restart network

Hi, I have 2 machines in production environment: 1. redhat machine for application 2. DB machine (oracle) The application doing a lot of small read&writes from and to the DB machine. The problem is that after some few hours the network from the application to the DB becomes very slow and... (4 Replies)
Discussion started by: moshesa
4 Replies
Smokeping_probes_CiscoRTTMonDNS(3)				     SmokePing					Smokeping_probes_CiscoRTTMonDNS(3)

NAME
Smokeping::probes::CiscoRTTMonDNS.pm - Probe for SmokePing SYNOPSIS
*** Probes *** +CiscoRTTMonDNS forks = 5 offset = 50% step = 300 timeout = 15 # The following variables can be overridden in each target section ioshost = RTTcommunity@Myrouter.foobar.com.au # mandatory iosint = 10.33.22.11 name = www.foobar.com.au # mandatory pings = 5 timeout = 15 # [...] *** Targets *** probe = CiscoRTTMonDNS # if this should be the default probe # [...] + mytarget # probe = CiscoRTTMonDNS # if the default probe is something else host = my.host ioshost = RTTcommunity@Myrouter.foobar.com.au # mandatory iosint = 10.33.22.11 name = www.foobar.com.au # mandatory pings = 5 timeout = 15 DESCRIPTION
A probe for smokeping, which uses the ciscoRttMon MIB functionality ("Service Assurance Agent", "SAA") of Cisco IOS to time ( recursive, type A) DNS queries to a DNS server. VARIABLES
Supported probe-specific variables: forks Run this many concurrent processes at maximum Example value: 5 Default value: 5 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% 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 timeout How long a single 'ping' takes at maximum Example value: 15 Default value: 5 Supported target-specific variables: ioshost The (mandatory) ioshost parameter specifies the Cisco router, which will send the DNS requests, as well as the SNMP community string on the router. Example value: RTTcommunity@Myrouter.foobar.com.au This setting is mandatory. iosint The (optional) iosint parameter is the source address for the DNS packets. This should be one of the active (!) IP addresses of the router to get results. IOS looks up the target host address in the forwarding table and then uses the interface(s) listed there to send the DNS packets. By default IOS uses the (primary) IP address on the sending interface as source address for packets originated by the router. Example value: 10.33.22.11 name The (mandatory) name parameter is the DNS name to resolve. Example value: www.foobar.com.au This setting is mandatory. pings How many pings should be sent to each target, if different from the global value specified in the Database section. 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: 5 timeout How long a single RTTMonDNS 'ping' take at maximum plus 10 seconds to spare. Since we control our own timeout the only purpose of this is to not have us killed by the ping method from basefork. Example value: 15 Default value: 15 AUTHORS
Joerg.Kummer at Roche.com NOTES
host parameter The host parameter specifies the DNS server, which the router will use. IOS VERSIONS This probe only works with IOS 12.0(3)T or higher. It is recommended to test it on less critical routers first. INSTALLATION To install this probe copy ciscoRttMonMIB.pm to ($SMOKEPINGINSTALLDIR)/lib/Smokeping and CiscoRTTMonDNS.pm to ($SMOKEPINGINSTALLDIR)/lib/Smokeping/probes. The router(s) must be configured to allow read/write SNMP access. Sufficient is: snmp-server community RTTCommunity RW If you want to be a bit more restrictive with SNMP write access to the router, then consider configuring something like this access-list 2 permit 10.37.3.5 snmp-server view RttMon ciscoRttMonMIB included snmp-server community RTTCommunity view RttMon RW 2 The above configuration grants SNMP read-write only to 10.37.3.5 (the smokeping host) and only to the ciscoRttMon MIB tree. The probe does not need access to SNMP variables outside the RttMon tree. BUGS
The probe does unnecessary DNS queries, i.e. more than configured in the "pings" variable, because the RTTMon MIB only allows to set a total time for all queries in one measurement run (one "life"). Currently the probe sets the life duration to "pings"*5+3 seconds (5 secs is the timeout value hardcoded into this probe). SEE ALSO
<http://oss.oetiker.ch/smokeping/> <http://www.switch.ch/misc/leinen/snmp/perl/> The best source for background info on SAA is Cisco's documentation on <http://www.cisco.com> and the CISCO-RTTMON-MIB documentation, which is available at: ftp://ftp.cisco.com/pub/mibs/v2/CISCO-RTTMON-MIB.my <ftp://ftp.cisco.com/pub/mibs/v2/CISCO-RTTMON-MIB.my> 2.6.8 2013-03-17 Smokeping_probes_CiscoRTTMonDNS(3)
All times are GMT -4. The time now is 11:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy