Sponsored Content
Full Discussion: Routing problem
Operating Systems Solaris Routing problem Post 302658303 by sri243 on Tuesday 19th of June 2012 06:29:24 AM
Old 06-19-2012
Question Routing problem

Hi,

I have two physical interfaces on a servers.
We have connected them to differerent subnets.
1) First interface:
10.158.49.87 to newtwork 10.158.49.0, its gateway is 10.158.49.1
(It is added as default gateway)
It is existing set up. It works well
2) Second interface:
We have connected this another network 10.158.31.0.
And assigned IP 10.158.31.87.
I am able to ping this server from servers having series IP address 10.158.31.*
Gateway of 10.158.31 network is 10.158.31.1.
I tried to add route using below.
#route add 10.158.31.0/24 10.158.31.1 -ifp eth2

But still I am unable to ping the server from outside of 10.158.31 series IPs Smilie.

Please explain, how to resolve this.

Regards/Sri
 

10 More Discussions You Might Find Interesting

1. IP Networking

Routing problem

Hi I know this problem is more likely some windows problem but it has also something to do with unix. We have a windows nt environment wich uses AIX (unix) machines as file servers (samba). In our windows network environment we nicely see al the unix file servers via the 10 MB network. Last... (2 Replies)
Discussion started by: Mark Detrez
2 Replies

2. IP Networking

routing problem

following Problem. I configured my SuSE Linux 8.0 as a router. I4l, named, ip_forward, iptables (NAT/MASQUERADING) are running or are aktivatet. I just can get a internet connection about the proxy server squid, but if i want to use other protocols i need functional routing. (I had this... (1 Reply)
Discussion started by: razor
1 Replies

3. IP Networking

Routing Problem

I have a question concerning networking. Could any forum members explain to me why I might be getting "no route to host" messages when I try to connect through ftp and http protocols? I have went to my etc/hosts file and everything seems to be configured properly. I can connect within my... (1 Reply)
Discussion started by: cstovall
1 Replies

4. IP Networking

routing problem in solaris

hi, below is the situation: my server is in 128.10.200.xxx network. i have a solaris computer running in a subnet. this computer got 2 nic card. 1 is 172.18.198.xxx , another 1 is 10.100.xxx.11 there is a machine stick with this computer, ip is 10.100.xxx.12 so, 10.100.xxx.11 and... (3 Replies)
Discussion started by: kyhah
3 Replies

5. IP Networking

Specific routing problem help needed

Hi, I am trying to set up the following : - One linux box connected to the net, static address, eth0 - No other eth interface on the box I want to set up this box in a way it can accept remote connections, like pptp tunnels (which seems the easier to set up unless you have other idea)... (2 Replies)
Discussion started by: aerostar700
2 Replies

6. Solaris

Routing problem of Solaris

Hi, I got problem of Sun Solaris 8 routing. IP of SunA is 10.16.64.164, and have routing table: 10.16.64.0 10.16.64.164 U 1 19236 bge1 10.6.0.0 10.6.0.3 U 1 16534 bge0 224.0.0.0 10.6.0.3 U 1 ... (4 Replies)
Discussion started by: milo
4 Replies

7. Red Hat

routing problem...im missing something

hi, having an issue on a class C network with trying to get a redhat diskless setup going. I am using oracle enterprise 5, which is RHEL 5.3 i believe. here is the scenario: sun sparc m4k that i am planning on making the red hat boxes boot off after i get the network issue fixed. ... (3 Replies)
Discussion started by: caddyjoe77
3 Replies

8. AIX

Aix Routing Problem

I need the following solution , please help me... Current situation ip: 192.168.0.12 persistent and 192.168.254.12 service ip gateway: 192.168.0.254 subnet: 255.255.255.0 i have added a new ip on a new nic ip: 10.10.255.40 gateway: 10.10.255.62 subnet: 255.255.255.224 ... (1 Reply)
Discussion started by: rajibimran
1 Replies

9. IP Networking

routing problem/question

Internet Gateway 192.168.0.201 Server 1 192.168.0.101 192.168.1.101 192.168.2.101 gateway: 192.168.0.201 VIP: 192.168.1.100 VIP: 192.168.2.100 Server 2 192.168.0.102 192.168.1.102 192.168.2.102 gateway: 192.168.0.201 Client 1 192.168.2.201 gateway: 192.168.2.100 (1 Reply)
Discussion started by: hopfensp
1 Replies

10. IP Networking

Routing problem : two interfaces one gateway

hi folks, i have a horstbox-router with the following configuration. it has 4 ethernet ports from wich one (wan0) is configured as an external modem via dhcp. at this port/interface(wan0) it is connected with my home network (other switch). this configuration results in the following... (14 Replies)
Discussion started by: gencaslan
14 Replies
SNMPDELTA(1)                                                         Net-SNMP                                                         SNMPDELTA(1)

NAME
snmpdelta - Monitor delta differences in SNMP Counter values SYNOPSIS
snmpdelta [ common options ] [-Cf] [ -Ct ] [ -Cs ] [ -CS ] [ -Cm ] [ -CF configfile ] [ -Cl ] [ -Cp period ] [ -CP Peaks ] [ -Ck ] [ -CT ] AGENT OID [ OID ... ] DESCRIPTION
snmpdelta will monitor the specified integer valued OIDs, and report changes over time. AGENT identifies a target SNMP agent, which is instrumented to monitor the given objects. At its simplest, the AGENT specification will consist of a hostname or an IPv4 address. In this situation, the command will attempt communication with the agent, using UDP/IPv4 to port 161 of the given target host. See snmpcmd(1) for a full list of the possible formats for AGENT. OID is an object identifier which uniquely identifies the object type within a MIB. Multiple OIDs can be specified on a single snmpdelta command. OPTIONS
COMMON OPTIONS Please see snmpcmd(1) for a list of possible values for COMMON OPTIONS as well as their descriptions. -Cf Don't fix errors and retry the request. Without this option, if multiple oids have been specified for a single request and if the request for one or more of the oids fails, snmpdelta will retry the request so that data for oids apart from the ones that failed will still be returned. Specifying -Cf tells snmpdelta not to retry a request, even if there are multiple oids specified. -Ct Flag will determine time interval from the monitored entity. -Cs Flag will display a timestamp. -CS Generates a "sum count" in addition to the individual instance counts. The "sum count" is the total of all the individual deltas for each time period. -Cm Prints the max value ever attained. -CF configfile Tells snmpdelta to read it's configuration from the specified file. This options allows the input to be set up in advance rather than having to be specified on the command line. -Cl Tells snmpdelta to write it's configuration to files whose names correspond to the MIB instances monitored. For example, snmpdelta -Cl localhost ifInOctets.1 will create a file "localhost-ifInOctets.1". -Cp Specifies the number of seconds between polling periods. Polling constitutes sending a request to the agent. The default polling period is one second. -CP peaks Specifies the reporting period in number of polling periods. If this option is specified, snmpdelta polls the agent peaks number of times before reporting the results. The result reported includes the average value over the reporting period. In addition, the highest polled value within the reporting period is shown. -Ck When the polling period (-Cp) is an increment of 60 seconds and the timestamp is displayed in the output (-Cs), then the default display shows the timestamp in the format hh:mm mm/dd. This option causes the timestamp format to be hh:mm:ss mm/dd. -CT Makes snmpdelta print its output in tabular form. -Cv vars/pkt Specifies the maximum number of oids allowed to be packaged in a single PDU. Multiple PDUs can be created in a single request. The default value of variables per packet is 60. This option is useful if a request response results in an error becaues the packet is too big. EXAMPLES
$ snmpdelta -c public -v 1 -Cs localhost IF-MIB::ifInUcastPkts.3 IF-MIB::ifOutUcastPkts.3 [20:15:43 6/14] ifInUcastPkts.3 /1 sec: 158 [20:15:43 6/14] ifOutUcastPkts.3 /1 sec: 158 [20:15:44 6/14] ifInUcastPkts.3 /1 sec: 184 [20:15:44 6/14] ifOutUcastPkts.3 /1 sec: 184 [20:15:45 6/14] ifInUcastPkts.3 /1 sec: 184 [20:15:45 6/14] ifOutUcastPkts.3 /1 sec: 184 [20:15:46 6/14] ifInUcastPkts.3 /1 sec: 158 [20:15:46 6/14] ifOutUcastPkts.3 /1 sec: 158 [20:15:47 6/14] ifInUcastPkts.3 /1 sec: 184 [20:15:47 6/14] ifOutUcastPkts.3 /1 sec: 184 [20:15:48 6/14] ifInUcastPkts.3 /1 sec: 184 [20:15:48 6/14] ifOutUcastPkts.3 /1 sec: 184 [20:15:49 6/14] ifInUcastPkts.3 /1 sec: 158 [20:15:49 6/14] ifOutUcastPkts.3 /1 sec: 158 ^C $ snmpdelta -c public -v 1 -Cs -CT localhost IF-MIB:ifInUcastPkts.3 IF-MIB:ifOutcastPkts.3 localhost ifInUcastPkts.3 ifOutUcastPkts.3 [20:15:59 6/14] 184.00 184.00 [20:16:00 6/14] 158.00 158.00 [20:16:01 6/14] 184.00 184.00 [20:16:02 6/14] 184.00 184.00 [20:16:03 6/14] 158.00 158.00 [20:16:04 6/14] 184.00 184.00 [20:16:05 6/14] 184.00 184.00 [20:16:06 6/14] 158.00 158.00 ^C The following example uses a number of options. Since the Cl option is specified, the output is sent to a file and not to the screen. $ snmpdelta -c public -v 1 -Ct -Cs -CS -Cm -Cl -Cp 60 -CP 60 interlink.sw.net.cmu.edu .1.3.6.1.2.1.2.2.1.16.3 .1.3.6.1.2.1.2.2.1.16.4 fi SEE ALSO
snmpcmd(1), variables(5). 4th Berkeley Distribution 25 Jul 2003 SNMPDELTA(1)
All times are GMT -4. The time now is 07:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy