Sponsored Content
Top Forums Shell Programming and Scripting Network connectivity Pre checks Post 303001699 by looney on Wednesday 9th of August 2017 01:20:30 PM
Old 08-09-2017
Network connectivity Pre checks

Hello All,
We are running multiple codes in prod all having different sources of databases in other servers. Many times due to network issue connectivity and DB issue the jobs got failed and to recover them become very brainstorming . I planning to create one script that can pre check if all the networks are up and running also if DB is good to connect with existing user name and password only then the dependent jobs should run.
I don't have any knowledge on network side. Please suggest me if anyone have done the same thing ever. What are the details i need.

For eg is it good to check network by ping command.I will introduce all such steps in script.



Moderator's Comments:
Mod Comment
Please do not try to bump posts up the list by posting again.
You agreed to follow the rules (mostly for polite behaviour) when you joined.

Last edited by rbatte1; 08-11-2017 at 07:41 AM.. Reason: Bumping-up message
 

10 More Discussions You Might Find Interesting

1. IP Networking

ip network connectivity with novell

Hi, I would like to know how i can setup my unix computer to connect to novell. Anybody any idea? (5 Replies)
Discussion started by: edw1ns
5 Replies

2. Solaris

Network Connectivity lost after reboot

I have 4 V440 servers running Solaris 9. I have their interfaces configured (ce0) and have connectivity to our network. However, after reboot,...the connectivity is lost although the interface shows that its still up after an ifconfig -a. Only after I reconfigure the interface do I restore... (19 Replies)
Discussion started by: StorageGuy
19 Replies

3. AIX

Pre-checks

AIX Guys!!! What pre-checks would you do on a 5.3 server before TL/SP/APAR installation? Bala (2 Replies)
Discussion started by: balaji_prk
2 Replies

4. Solaris

pcn0 intermittent network connectivity issue

I have a solaris 10 x86 installed on a VMware server. It has been runing well for a couple weeks, but started to have network connectivity issue since last week. The network card seems to be up and down every one minute. So I got connection closed after I sshed to it for about one minute. #... (2 Replies)
Discussion started by: fredao
2 Replies

5. UNIX for Advanced & Expert Users

network connectivity issue between vista and fedora

Hi guys, I had two computer which is one with vista and other one with fedora and they are connected via one router. from vista to fedora is fine.. I can ping or connect via putty using Ip address but I couldn't connect putty using hostname/domain. If I typed in fedora the hostname,... (0 Replies)
Discussion started by: peac3
0 Replies

6. UNIX for Dummies Questions & Answers

xend kills network connectivity on boot

red hat 5 update 4 64bit. linux newby. on an interactive boot i can ping -t my vm linux server from my physical MS XP workstation and a vm W2000 64 bit server until xend is started, after that i get destination unreachable. if i choose not to start xend on the interactive boot i retain... (1 Reply)
Discussion started by: slartibartfast9
1 Replies

7. HP-UX

Network Connectivity Issues

Newbie with UNIX here. Currently troubleshooting a UNIX terminal we have. I determined it to be bad and swapped it out with a known good terminal. I went in and changed the IP address and host name to reflect the old terminal. Although now there is no connectivity. I swapped out the NIC... (1 Reply)
Discussion started by: kevinlord190
1 Replies

8. AIX

IBM Pureflex network connectivity issue

Hello Everyone We have purchased IBM Pureflex chassis with 5 P460 blades. We have configured each blade with dual vios and 4 vio clients. VIOS installation and vio client installation and configuration was completed successfully. When we tried to connect the network cables from Pureflex... (2 Replies)
Discussion started by: yuvarakasil
2 Replies

9. Red Hat

Server health Checks pre & post Rebooting

Hi, Earlier we used to reboot servers based on adhoc request, never checked anything on it pre-reboot., But now i need to reboot regularly but most of the info is not available, I need to know want to make sure that server to be rebooted without any issues, so I want to do few prechecks which will... (5 Replies)
Discussion started by: nanz143
5 Replies

10. UNIX for Dummies Questions & Answers

Configure network connectivity as guest O.S under vmware

Hi! I am not sure if this is the right place to post this question. What I did was to download vmware onto my laptop, them install a linux distro as a guest O.S., on VM network configuration I have used "bridge", them I used Virtual Network Editor to chose the network interface, but as I write... (4 Replies)
Discussion started by: fretagi
4 Replies
queuedefs(4)							   File Formats 						      queuedefs(4)

NAME
queuedefs - queue description file for at, batch, and cron SYNOPSIS
/etc/cron.d/queuedefs DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue. The format of the lines are as follows: q.[njobj][nicen][nwaitw] The fields in this line are: q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see at(1)); c is the default queue for jobs run from a crontab(1) file. njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100. nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2. nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's queue, or because the system-wide limit of jobs executing has been reached. The default value is 60. Lines beginning with # are comments, and are ignored. EXAMPLES
Example 1: A sample file. # # a.4j1n b.2j2n90w This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron. SEE ALSO
at(1), crontab(1), nice(1), cron(1M) SunOS 5.10 1 Mar 1994 queuedefs(4)
All times are GMT -4. The time now is 09:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy