Hi Guys,
how to count number of files successfully copied while coping files from source to destination path
ex:10 files from source to target location copying
if 8 files copied successfully then
echo successfully copied=8
failure=2 files
if two files get error to coping files from... (23 Replies)
hi All,
i have 2 server setup now for Rsync, i configured Rsync on both of the server and it worked well when i did run from source to destination. and while running back from destination to source it produced this error:
bash-3.2$ ksh rsync_bravo_db.ksh usa0300uz1247.apps.mc.xerox.com... (0 Replies)
Hi Everyone,
I am using solaris 10.I am facing a different problem here with tlsftp.I have intalled all steps for tlsftp and able to connect to the destination server from the source server.It worked for some days.But recently when i am connectin it is giving below error.I am... (0 Replies)
I'd like to specify a different build and deployment path for files, by default the same path is used for both build and install, I wasn't able to find a way to make these different. With Solaris pkgadd, one can specify different paths in prototype, so I would assume something like that is possible... (0 Replies)
Move all files starting with a specific name to different directory.
This shell script program should have three parameters
File Name
Source Directory
Destination Directory
User should be able to enter ‘AB_CD*' in file name parameter. In this case all the files starting with AB_CD will... (1 Reply)
Hi all,
I have some doubts in selecting the interface to transfer packets and receive the packets.
--> Multiple interfaces :
--------------------
1) 0.0.0.0 --------> wild card address.
2) x.x.x.x --------> valid address.(192.168.1.156)
3) ff.ff.ff.ff -------->... (0 Replies)
Hi, need help how to count unique destination for the source ip. The file is contains 4 number of fields. Example of the file is here
src ip dest ip #of flows total bytes
192.168.6.0 88.0.33.2 12 128
192.168.6.0 88.0.33.2 1 168
192.168.6.0 ... (5 Replies)
IBDIAGPATH(1) IB DIAGNOSTIC PACKAGE IBDIAGPATH(1)NAME
ibdiagpath - IB diagnostic path
SYNOPSYS
ibdiagpath
{-n <[src-name,]dst-name>|-l <[src-lid,]dst-lid>|-d <p1,p2,p3,...>}
[-c <count>] [-v] [-t <topo-file>] [-s <sys-name>] [-i <dev-index>]
[-p <port-num>] [-o <out-dir>] [-lw <1x|4x|12x>] [-ls <2.5|5|10>] [-pm]
[-pc] [-P <<PM counter>=<Trash Limit>>]
DESCRIPTION
ibdiagpath traces a path between two end-points and provides information regarding the nodes and ports traversed along the path. It
utilizes device specific health queries for the different devices along the traversed path. The way ibdiagpath operates depends on the
addressing mode used on the command line. If directed route adressing is used, the local node is the source node and the route to the
destination port is known apriori. On the other hand, if LID route (or by-name) addressing is imployed, then the source and destination
ports of a route are specified by their LIDs (or by the names defined in the topology file). In this case, the actual path from the local
port to the source port, and from the source port to the destination port, is defined by means of Subnet Management Linear Forwarding Table
queries of the switch nodes along those paths. Therefore, the path cannot be predicted as it may change. The tool allows omitting the
source node, in which case the local port on the machine running the tool is assumed to be the source. Note: When ibdiagpath queries for
the performance counters along the path between the source and destination ports, it always traverses the LID route, even if a directed
route is specified. If along the LID route one or more links are not in the ACTIVE state, ibdiagpath reports an error. Checks for path
validity from partitions, IPoIB and QoS perspectives are also provided.
ibdiagpath.log -
A dump of all the application reports generate according to the provided flags
ibdiagnet.pm -
A dump of the pm Counters values, of the fabric links
OPTIONS -n <[src-name,]dst-name> :
Names of the source and destination ports (as defined in the topology file; source may be omitted -> local port is assumed to be the
source)
-l <[src-lid,]dst-lid> :
Source and destination LIDs (source may be omitted -> local port is assumed to be the source)
-d <p1,p2,p3,...> :
directed route from the local node (which is the source) and the destination node
-c <count> :
The minimal number of packets to be sent across each link (default = 100)
-v :
Enable verbose mode
-t <topo-file> :
Specifies the topology file name
-s <sys-name> :
Specifies the local system name. Meaningful only if a topology file is specified
-i <dev-index> :
Specifies the index of the device of the port used to connect to the IB fabric (in case of multiple devices on the local system)
-p <port-num> :
Specifies the local device's port number used to connect to the IB fabric
-o <out-dir> :
Specifies the directory where the output files will be placed (default = /var/cache/ibutils)
-lw <1x|4x|12x> :
Specifies the expected link width
-ls <2.5|5|10> :
Specifies the expected link speed
-pm :
Dump all the fabric links, pm Counters into ibdiagnet.pm
-pc :
Reset all the fabric links pmCounters
-P <PM=<Trash>> :
If any of the provided pm is greater then its provided value, print it to screen
-h|--help :
Prints the help page information
-V|--version :
Prints the version of the tool
--vars :
Prints the tool's environment variables and their values
ERROR CODES
1 - The path traced is un-healthy
2 - Failed to parse command line options
3 - More then 64 hops are required for traversing the local port to the "Source" port and then to the "Destination" port.
4 - Unable to traverse the LFT data from source to destination
5 - Failed to use Topology File
6 - Failed to load required Package
IBDIAG 1.0 2014-06-09 IBDIAGPATH(1)