Sponsored Content
Top Forums Shell Programming and Scripting Collect information from switches Post 302303892 by chinni-script on Friday 3rd of April 2009 07:42:13 PM
Old 04-03-2009
Collect information from switches

Hi All ,

In my environment we have 12 SAN switches .Culd u pls help me for below queries .

[1] would like to telnet to all switches and collect information in daily basis with "switchstatus" command and store the output under /tmp/ folder on systemA .

[2]To keep passwords of 12switches in a text file on unix host ,is there any best way to maintain in non-readable format just to protect the view from others .

Chinni.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Tar switches!!!

Hi, If i want to write my data on several tapes, (more than one tape), what switch(s) i need to use with tar. In other word if my data needs the sapce more than one tape & i don't wanna to compress or ... my data. so is it possible to write up to the end of the tape & it asks to put another... (1 Reply)
Discussion started by: nikk
1 Replies

2. Solaris

Planning for DR, I have to collect information

Dear All, We are going for Disaster Recovery project, the vendor asked for more details about how much is the daily data changes only. using sar / iostat can any one help me to collect this ?! Note: only I need the changed data size not the daily increasing data. this is to know how much... (1 Reply)
Discussion started by: adel8483
1 Replies

3. Shell Programming and Scripting

script to collect all db information

hi all I am looking for shell script ,by which i need to gather all the DB information in Sybase server . Thanks in advance :) (3 Replies)
Discussion started by: mvsramarao
3 Replies

4. Infrastructure Monitoring

Nagios monitoring for switches.

Hi, I have configured check_snmp plugin and using the plugin i am able to monitor the uptime of the switch. But the following fails # /usr/local/nagios/libexec/check_snmp -H 10.10.10.1 -C ready -o ifOperStatus.1 -r 1 -m RFC1213-MIB SNMP CRITICAL - *down(2)* | # Any suggestions ? (1 Reply)
Discussion started by: uxadmin007
1 Replies

5. Shell Programming and Scripting

Multiple commandline switches

I have a script that has commandline switches that work no problem. But i don't know how to enable it to have multiple switches at one time. So I'd want myscript -h -o or even myscript -ho but i'm having no luck incorporating this. I tried shifting but i'm not getting it. Thanks ----------... (0 Replies)
Discussion started by: DC Slick
0 Replies

6. Shell Programming and Scripting

echo switches

Hello All, I am writing an shell script but abruptly its not able to recognize switches in echo statement. #!/bin/bash top -n 1 -b>ankit host=`hostname` time=`cat ankit|grep load|tr -s " "|cut -d " " -f3` load=`cat ankit|grep load|tr -s " "|cut -d "," -f4|cut -d ":" -f2` ... (3 Replies)
Discussion started by: ajaincv
3 Replies

7. Shell Programming and Scripting

shell script to collect information from current and remote unix boxes

I am using AIX 5.3.0.0 ; I need a script to find out each remote AIX boxes Hostname, Model name and Serial number in following format Hostname Modelname SerialID AIXMC01 IBM,7026-B80 IBM,0110BBA1F AIXMC02 IBM,7026-H50 IBM,0110BBA56 AIXMC03 IBM,7026-H50 IBM,0110BBARR... (12 Replies)
Discussion started by: amir07
12 Replies

8. AIX

LACP between AIX 7.1 and HP procurve switches

Hi. On a standalone AIX server, 7.1 version, I have 3 connected gigabit ethernet ports. I made an etherchannel like this : # lsattr -El ent4 adapter_names ent1,ent2 | EtherChannel Adapters True alt_addr 0x000000000000 | Alternate EtherChannel Address True auto_recovery yes | Enable... (1 Reply)
Discussion started by: stephnane
1 Replies

9. Shell Programming and Scripting

Read Strings in as options to switches

I have a script using getops with -a -t -l as potential switches, based on the switches used, it will set the respective variable value which will cause the routine/function to run. I need to also pass a string with the switch that will get parsed by the function. example ./myscript -a... (8 Replies)
Discussion started by: glev2005
8 Replies

10. SuSE

How to filter SYSLOG data to collect meaningful information only?

Dear users, SUSE 10 sp3 and SUSE 11. I made configuration changes in '/etc/syslog-ng/syslog-ng.conf' to move SYSLOG content to LogRhythm. This is what I changed in the file. Un-comment out the following lines #Enable this and admop IP to send log messages to... (10 Replies)
Discussion started by: JDBA
10 Replies
MARK(1)                                                              [nmh-1.5]                                                             MARK(1)

NAME
mark - manipulate message sequences SYNOPSIS
mark [+folder] [msgs] [-sequence name ...] [-add | -delete] [-list] [-public | -nopublic] [-zero | -nozero] [-version] [-help] DESCRIPTION
The mark command manipulates message sequences by adding or deleting message numbers from folder-specific message sequences, or by listing those sequences and messages. A message sequence is a keyword, just like one of the "reserved" message names, such as "first" or "next". Unlike the "reserved" message names, which have a fixed semantics on a per-folder basis, the semantics of a message sequence may be defined, modified, and removed by the user. Message sequences are folder-specific, e.g., the sequence name "seen" in the context of folder "+inbox" need not have any relation whatsoever to the sequence of the same name in a folder of a different name. Three action switches direct the operation of mark. These switches are mutually exclusive: the last occurrence of any of them overrides any previous occurrence of the other two. The -add switch tells mark to add messages to sequences or to create a new sequence. For each sequence named via the -sequence name argu- ment (which must occur at least once) the messages named via msgs (which defaults to "cur" if no msgs are given), are added to the sequence. The messages to be added need not be absent from the sequence. If the -zero switch is specified, the sequence will be emptied prior to adding the messages. Hence, -add -zero means that each sequence should be initialized to the indicated messages, while -add -nozero means that each sequence should be appended to by the indicated messages. The -delete switch tells mark to delete messages from sequences, and is the dual of -add. For each of the named sequences, the named mes- sages are removed from the sequence. These messages need not be already present in the sequence. If the -zero switch is specified, then all messages in the folder are added to the sequence (first creating the sequence, if necessary) before removing the messages. Hence, -delete -zero means that each sequence should contain all messages except those indicated, while -delete -nozero means that only the indi- cated messages should be removed from each sequence. As expected, the command "mark -sequence foo -delete all" deletes the sequence "foo" from the current folder. When creating or modifying sequences, you can specify the switches -public or -nopublic to force the new or modified sequences to be "pub- lic" or "private". The switch -public indicates that the sequences should be made "public". These sequences will then be readable by all nmh users with permission to read the relevant folders. In contrast, the -nopublic switch indicates that the sequences should be made "private", and will only be accessible by you. If neither of these switches is specified, then existing sequences will maintain their cur- rent status, and new sequences will default to "public" if you have write permission for the relevant folder. Check the mh-sequence(5) man page for more details about the difference between "public" and "private" sequences. The -list switch tells mark to list both the sequences defined for the folder and the messages associated with those sequences. Mark will list the name of each sequence given by -sequence name and the messages associated with that sequence. If the sequence is private, this will also be indicated. If no sequence is specified by the -sequence switch, then all sequences for this folder will be listed. The -zero switch does not affect the operation of -list. The current restrictions on sequences are: o The name used to denote a message sequence must consist of an alphabetic character followed by zero or more alphanumeric characters, and cannot be one of the (reserved) message names "new", "first", "last", "all", "next", or "prev". o Only a certain number of sequences may be defined for a given folder. This number is usually limited to 27 (11 on small systems). (The internal implementation relies on bitmasks, with some bits set aside for internal use.) o Message ranges with user-defined sequence names are restricted to the form "name:n", "name:+n", or "name:-n", and refer to the first or last `n' messages of the sequence `name', respectively. Constructs of the form "name1-name2" are forbidden for user defined sequences. FILES
$HOME/.mh_profile The user profile PROFILE COMPONENTS
Path: To determine the user's nmh directory Current-Folder: To find the default current folder SEE ALSO
flist(1), pick(1), mh-sequence(5) DEFAULTS
`+folder' defaults to the current folder `-add' if -sequence is specified, -list otherwise `msgs' defaults to cur (or all if -list is specified) `-nozero' CONTEXT
If a folder is given, it will become the current folder. HELPFUL HINTS
Use flist to find folders with a given sequence, and "pick sequence -list" to enumerate those messages in the sequence (such as for use by a shell script). MH.6.8 11 June 2012 MARK(1)
All times are GMT -4. The time now is 09:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy