Sponsored Content
Full Discussion: Dual NIC problem
Operating Systems Solaris Dual NIC problem Post 55982 by RTM on Thursday 23rd of September 2004 10:08:07 AM
Old 09-23-2004
Is this a script or software shutting down the interface just because a ping doesn't get answered?

If so, fix the script - get different software - change the router to respond to pings.

Please explain your problem in more detail including what is shutting down the interface.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

problem in dual boot

i want to know how do i make my system a dual boot system for Linux 7.1 and Windows Nt 4.0 :( :confused: :confused: (2 Replies)
Discussion started by: mad2life
2 Replies

2. UNIX for Dummies Questions & Answers

Dual Boot problem,help!!!!

I had Win98 and Win Xp on a dual boot on my system, I formatted my C: drive to get rid of Win98 and installed Linux Madrake in its Place, it all installed ok but when I boot up I can no longer dual boot and it goes straight into Mandrake Linux. How can I get either a dual boot so I can get to XP... (10 Replies)
Discussion started by: Merv
10 Replies

3. UNIX for Dummies Questions & Answers

SuSE 8.1 NIC problem

i have just installed suse 8.1 on a third computer which has an Asus p4s8x with onboard NIC and sound. now, on install suse detected everything automatically with no probelm, however upon reboot the sound failed to load as well as the network card. /dev/eth* doesnt exist. i looked in the bios and... (2 Replies)
Discussion started by: norsk hedensk
2 Replies

4. UNIX for Advanced & Expert Users

Dual boot problem

Hi All, I have a pc loaded with windows 2000 professional. Recently added new disk of size 80GB and installed redhat linux to second disk. Now system is booting to linux but not to windows 2000. How to configure for dual boot. Thanks in advance - Bache Gowda (3 Replies)
Discussion started by: bache_gowda
3 Replies

5. UNIX for Dummies Questions & Answers

nic problem

hello friends i am using x86 pc i can install solaris o/s but nic card is not deceting. i am not able see in file called /etc/path_to_inst. i did /touch reconfigu and devfsadm also. i used external nic card also realtech 8169d am using gigabyte mother board 775. (0 Replies)
Discussion started by: manoj123
0 Replies

6. AIX

Dual port NIC, cfgmgr

OS: AIX 6.1 The host has a dual port NIC installed and when I went to run `cfgmgr -v` to configure it I got an error showing device packages are missing from the install: `cfgmgr -v` on 10.15.xx.xxx cfgmgr: 0514-621 WARNING: The following device packages are required for device support but... (3 Replies)
Discussion started by: b1f30
3 Replies

7. Solaris

IPMP. Is this a NIC problem!!?

-- IPMP Groups -- Node Name Group Status Adapter Status --------- ----- ------ ------- ------ IPMP Group: hostname1.xx-xxxx.xxxi sc_ipmp1 Online ce5 Online IPMP Group: hostname1.xx-xxxx.xxxi ipmpgrp01... (2 Replies)
Discussion started by: FeNiCrC_Neil
2 Replies

8. Solaris

NIC problem

can anyone help me fix this? what command should I use to bring them back to "TRUE"? Interface Speed Duplex Autoneg --------- ----- ------ ------- ce0 100 Mbit/s FULL FALSE ce5 100 Mbit/s FULL ... (3 Replies)
Discussion started by: uuontario
3 Replies

9. Solaris

Mulitple Zones on Dual NIC host

Greetings Forumers! I am running into an issue with multiple zones on an M5000 with 2 NICs. The NICs are on separate VLANs. These zones are using the 2 NICs to communicate with other systems but when they need to communicate with a zone on the same system, but different NIC, the application... (9 Replies)
Discussion started by: bluescreen
9 Replies

10. AIX

LPAR NIC Problem

On all our lpars we have our main interface set up and a backup network interface. On a number of our lpars those connections go to a down state for no apparent reason. They are still attached but they show up as "*en1" in netstat. Has anyone else come across this issue or know why an... (4 Replies)
Discussion started by: bsewen
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 10:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy