03-05-2012
Lack of IP Connectivity
Hi
Can any one please help identify the issue in scenario 2:
Connectivity Diagram:
1) Distribution Switch----Int_Switch----LabSwitch(Fa1/0)----Terminal Ser
2) Distribution Swtich----Int_Swtich----LabSwitch(Fa2/0)----3640 Router
---all links are access links
Distribution Switch (int vlan 10 = 10.1.96.251/26)
Int_Switch (int vlan 10 = 10.1.96.196/26)
LabSwitch (int vlan 10 = 10.1.96.234/26)
Termial Ser (Int Eth0 = 10.1.96.254/26)
3640 Router (int Fa1/0 = 10.1.96.245/26)
Scenario1: I could able to successfully ping/telent Termianal server from my pc.
Scenario2: Can able to ping Distribution switch ip from 3640 router and vice versa. But cannot able to ping/telnet from my pc. I have also confiured a default router on router as 0.0.0.0 0.0.0.0 10.1.96.251 but still cannot able to ping. i have a default-gate 10.1.96.251 configured.
Can any one please help in scenario2, if I am missing some thing.
Thanks in advance.
5 More Discussions You Might Find Interesting
1. Linux
postfix configuration issues...specifically masquerading (lack of )
Mail sent to our intranet arrives correctly (me@domain.com).
Mail sent to our intranet arrives correctly (me@domain.com).
Anything going outside does not, so my tests get rejected (me@hostname.com) :(
any assistance... (5 Replies)
Discussion started by: mr_manny
5 Replies
2. Solaris
Are more and more companies moving away from Solaris? I am currently helping a company search for a Sr. Solaris Engineer near Philadelphia and it seems as if more candidates are in other UNIX flavors. Is this correct? Where is the best place to search for Solaris Engineers?
Thank you for... (2 Replies)
Discussion started by: nickcrocemisi
2 Replies
3. What is on Your Mind?
Are more and more companies moving away from Solaris? I am currently helping a company search for a Sr. Solaris Engineer near Philadelphia and it seems as if more candidates are in other UNIX flavors. Is this correct? Where is the best place to search for Solaris Engineers?
Thank you for your... (1 Reply)
Discussion started by: nickcrocemisi
1 Replies
4. Shell Programming and Scripting
I'm working on a script I wrote called backup.sh
when I run it like this:
. ./backup.sh
I get this error:
ksh: ./backup.sh: no closing quote
when I run it this way:
backup.shI get this error:
backup.sh: 28: Syntax error: end of file unexpected (expecting "fi")I looked through the code over... (21 Replies)
Discussion started by: jzacsh
21 Replies
5. UNIX for Dummies Questions & Answers
So I have a Networking class at my university that involves learning the basic commands of unix (i.e. Chmod, cat, cp, ls, mv, rm, mkdir, rmdir, pwd, etc) and my professor had us download and install Solaris and PuTTY as a means of...I suppose practicing using/executing commands. However due to... (7 Replies)
Discussion started by: bo74
7 Replies
LEARN ABOUT DEBIAN
mrtg-ping-probe
MRTG-PING-PROBE(1) General Commands Manual MRTG-PING-PROBE(1)
NAME
mrtg-ping-probe - ping probe module for Multi Router Traffic Grapher
DESCRIPTION
mrtg-ping-probe is a ping probe module for MRTG 2.x. It is used to monitor the round trip time and packet loss to networked devices. MRTG
uses the output of mrtg-ping-probe to generate graphs visualizing minimum and maximum round trip times or packet loss.
mrtg-ping-probe is not run directly, but is called by MRTG as a helper when it needs to determine ping time to a host.
Act responsibly: do not use mrtg-ping-probe to ping devices without the owner's permission. Just imagine if 10,000 people decided to ping
your hosts! mrtg-ping-probe is meant to be used within your network to get round trip time performance figures for your network.
OPTIONS
To use mrtg-ping-probe you need to configure MRTG to call it from within the definition of a target host. This is done in the MRTG config
file, which is usually /etc/mrtg.conf.
Here's an example snippet: change the target name and IP address to suit your needs.
Target[your.target.ping]: `/usr/bin/mrtg-ping-probe 123.456.789.123`
SetEnv[your.target.ping]: MRTG_INT_IP="123.456.789.123" MRTG_INT_DESCR="ping"
MaxBytes[your.target.ping]: 100
AbsMax[your.target.ping]: 200
Options[your.target.ping]: gauge, growright
YLegend[your.target.ping]: ping time (ms)
ShortLegend[your.target.ping]: ms
Legend1[your.target.ping]: Maximum Round Trip Time in ms
Legend2[your.target.ping]: Minimum Round Trip Time in ms
Legend3[your.target.ping]: Maximal 5 Minute Maximum Round Trip Time in ms
Legend4[your.target.ping]: Maximal 5 Minute Minimum Round Trip Time in ms
LegendI[your.target.ping]: Max:
LegendO[your.target.ping]: Min:
Pay close attention to the backticks in the first line which tell MRTG to execute the nominated external program. Note also that you need
to use the "gauge" option, since the results of subsequent ping probes are independant values and not an incrementing counter.
SEE ALSO
mrtg(1).
The latest release of mrtg-ping-probe can be found on the web at http://pwo.de/projects/mrtg/
AUTHOR
This manual page was written by Jonathan Oxer <jon@debian.org>, for the Debian project (but may be used by others).
April 14, 2003 MRTG-PING-PROBE(1)