Lookout 6 Hypertrends - Symlinks- Static URL problems

[erblock]

ISSUE:

This problem has been verified to affect any client process hypertrend data/display link(s) through symlink(s) to server process(s) on same machine with Citadel 5 database also residing on same machine.  Also verified to be an issue from client machines on the same subnet (with simple machine_name DNS valid) to server-machine-process/server-machine-Citadel 5.

DETAIL:

Client symlink's Static URLs must have the form \\machine_name\process_name to properly display hypertrend data in a client process.

Alternate forms of URL's such as \\ip_address\process_name and \\FQDN\process_name, no longer function under Lookout 6.

All three forms worked fine under all older versions of Lookout that supported Symlinks.

NOT GOOD:

This Issue renders all remote (off subnet) client access (including web client)  via hypertrends to Lookout 6 databases USELESS.

another BIG Bug in Lk6....

Side Note:

During testing, I also noticed that if a web client under IE 6 (WinXP SP2+) will crash if a process called by the browser is stopped on the remote server machine. Even if the process on the server is restarted, IE never recovers and must be killed.

Ed Block

MIT, Cambridge, MA

[erblock]

OK, It's been almost a week with no acknowlegement or repy from NI (also submitted via email support).

???

[erblock]

Come on Lookout developers....NIWeek is over!  Accept the failure and move on... Back to work!

Any word on this Hypertrend/Nicitdl5.exe issue??

Cheers,

Ed

[nickf]

erblock,

Thank you for identifying this issue.  Our developers are currently working on a fix for this.  The fact that hypertrends will not update using IP addresses in symbolic links is partially related to the Citadel performance issues that have been identified by you and Mike@DTSI.

I have posted a fix for the case where IP addresses are used with symbolic links within a single sub-net.  Unfortunately, the current fix will not resolve the issue of being able to access trends from different subnets. 

Please check ni.com/downloads for the patch.

We are working on resolving both the performance issue and the cross subnet trending issue and will release a patch when one is available.  Do you have an open support ticket regarding this issue?


Regards,

Nick Folse
Product Support Engineer - Lookout
National Instruments R&D

[erblock]

Thank You Nick!

I this the support ticket # your asking about? ---Re: (Reference#7086854) Lookout 6 Hypertrends - Symlinks- Static URL

I never sent an official support request for the performance issues with nicitdl5.exe on Citadel servers because it looked like the general issue of performance was previously identified.  I just added some specific data to the issue.   I could put one in if that is appropriate.

I'm happy seeing your response and forthcoming fixes will be quite welcome because I really can't proceed with further testing of Lookout 6 in my environment until the Hypertrend issues are workable since we rely on them quite heavily.

Regards,

Ed

[erblock]

Nick or anyone else at Lookout support....

Any idea an when either or both of these issues will be fixed or significantly improved?  Please?

Ed

[erblock]

How about a progress report on LK 6.0 and Citadel 5.0  repair progress someone....

Your loyal users deserve that.....

[nickf]

Ed,

  We are making progress toward resolving this issue.  We at National Instruments understand your concern regarding this matter and are working hard to provide a resolution fast as possible.  Unfortunately, I can not provide an estimate of when this issue will be resolved.  We will keep you informed of the latest news when it is available.

Sincerely,

Nick Folse
Product Support Engineer
National Instruments R&D

[erblock]

Progress update(s) please??

Thanks,

Ed

[.avi file]

Greetings! 
 Thanks for your patience! As Nick mentioned in our earlier posting, our customer concerns are the highest priority. As of this time please be aware that we have fixed the issue concerning hypertrends and the CPU usage it consumes in lookout 6.0. The announcement of the next update of lookout will be releasing shortly that addresses the issue. We cannot give you the exact date, but you can be rest assured that we are working hard to release it as soon as possible. The link to the update will be posted on this thread as well.

Thanks and we truly appreciate your patience
Best regards
Avi Harjani