How we can achieve First level of troubleshooting from Ionix Notification COnsole

This post was done in 2011, there is no one to answer this question, is there any sound emc engineer to answer this, or the community is started just for the sake of having because other companies are having the same?

Thanks Paul for such a instant reply, now thats what called community

Anyways, yesterday itself, we have resolve these issues, and have adjusted the parameters based on our environment, however if you can assist further and tell us if you have any ready script for trace route, as it doesnt come along with the installation, i searched as well as tried to apply based on the script, however it seems i am making a mistake

Hi Navid,

It appears from the error that this server tool is not present on the SAM server:

CI-ESPEC-While attempting to locate file with search path

    "E:\InCharge8_PSS\SAM\smarts\local\;E:\InCharge8_PSS\SAM\smarts\",

    intermediate path "actions\server\" and final component "ics-ping-all.sh"

-ENOENT-No such file or directory

Do you see any scripts located at E:\InCharge8_PSS\SAM\smarts\local\actions\server\ or E:\InCharge8_PSS\SAM\smarts\actions\server\?

A server tool must be located in the BASEDIR/smarts/local/actions/server directory on the host where the Global Manager (SAM) is running. The Global Manager must be able to execute the script.

Server tools are invoked under the username that the Global Manager (SAM) is running under. Sserver tools are invoked on the same host as the Global Manager.

Kind Regards,

Paul O'Rourke

Hello Navid,

Unfortunately EMC does not offer a stock file for doing a trace route of a device between the SAM server and the device that has an alert associated with it.  If you would like this functionality to be added to the capabilities of your deployment then you would have to add it yourself.  Unfortunately based on the error you have provided us, it looks like you are installed on a Windows environment looking at the directory structure of the error, but the script it is looking for is a *.sh script, which don't get installed with our Windows software.

If you are on Windows you should be able to easily modify the ping script by replacing the "ping" command on line 224 of ICS-Ping-IP.cmd with the "tracert" command and your script should do a trace route instead of a ping.  This simple change may work as well with the shell command if the OS is configured to use the linux tracert but may possibly need to update the command to include command line options (such as -4 or -6 for IPv6).  You just need to find where the ping command is in the file with the trace route command and its appropriate options.

The file I have attached is an example of the changes I am talking about.  If you take a look at lines 91 through 111 you will see that this is actually  the ics-ping-IP.sh file with the ping command replaced by a tracert command that uses IPv4 (-4) and sends a packet that is 64 byte long.  This is just an example of what you can do to make the changes, not an actual script for use so I have not tested it.

Please let us know if this is helpful to you.

Cheers,

Sean

Sean Mackinnon | EMC ASD - Smarts |  Monday - Friday 8:30 - 16:30 EST/EDT | Hopkinton, MA, USA

Yes you are right, we were doing it wrong, however we have both linux and windows environment ip and sam domain, and hence we will need both, however we tried doing what you mentioned on our windows server, however it did not work, though the script output said it was successful, please check the attached

Hi Navid,

I do not see any file attached. Looks like you make have forgotten.

Can you please attach the file?

Thanks,

Paul