| >A customer I am working with is running PCM 1.5 on OSF 2.0. When I disconnect
>the
>cable from a Telnet server, CM does not recognise that the system has gone away
>and no connection can be made. I have tested this using a DECserver 200 and if
>I
>disconnect the cable from the server, CM does not produce an event. I have
>installed the Patch kit.
Hmm,
The method we use to detect a line breaking is different between TELNET and LAT
connections:
On LAT the driver reports the virtual circuit timing out and we do the stuff.
TELNET is not so simple as it tends to sit around expecting the connection to
come back. We have a timer which if the line has not seen data for a specific
time sends a TELNET GET STATUS protocol message. and waits for response. If
there is not response within a timeout period we specify then the TELNET session
is declared dead and we attempt a reconnect. At this point you get the Lost
message. Try this yourself by Telneting to a port on a terminal server i.e.
telnet server list_num
Then pull out the connection to the server. The TELNET application does not
detect the circuit failing.
I don't think you tried this on a DECserver 200 as that DECserver does not
support TELNET. If you really meant a DS300 the one under my desk ( which I use
for testing) acts as above.
Now another gotcha is that not all vendors terminal servers support all the
TELNET options. Some do not support the GET STATUS message ( e.g. Xyplex). In
this case we check for this on the first open of the port and disable checking
(you should also get an event saying that this happened).
>Can you tell me the difference between the Eventlist window and the multi shot
>window. I have some events which use the multi-shot window but some of these
>also go to the Eventlist window.
The eventlist image puts up a window and puts the data for many events into
that window as a list.
The default action name supplied with PCM for this image is: Multi-Line Window.
The eventsingle image puts up a window with info about a single event.
The default action name supplied with PCM for this image is: Single-Shot Window.
>Finally, the customer finds it hard to believe that we do not supply a list of
>OSF events and how is he supposed to define events if we don't even know them.
>I have gone through all the syslog files but as this is a test system, there
>are very few messages output.
No harder to beleive than the PCM engineering team. We have spent a long time
trying to ask, persuade, coerce other groups to provide PCM scan profiles, but
the sort of reply we get is:
"We are not funded to help make YOUR product a success" I think they forget we
work for the same company.
Remember we are in the same position as your customer ( or even worse off) when
trying to get OSF/1 (or any engineering group) to do this.
As a course of action I suggest that you get the customer to raise an IPMT case
against OSF/1 or any other product whom they feel ought to provide this kind of
information.
Cheers Simon...
P.S. as far as the question about the action routines is concerned they are
documented in the User Guide. If the information there is insufficient please
let us know as we will pass this on to the documentation writer for the next
version.
|
| When I disconnect the cable from a DECserver 200 using the LAT protocol, PCM does
not recognise that the link is lost. After 24 hrs, I still have the option
Connect to Console. Can PCM indicate when it has lost a link. This customer will
be managing 200 nodes on the PCM system and it is vital to know if PCM has
lost one of its links. The customer will be using TELNET.
In relation to the eventlist routine and the actions I have defined to use
Multi-shot window, I dont understand why some events go to both windows while
other events only go to the multi-shot window. When I start up the C3 window, I
start the eventlist. At first I thought all events that went to the C3 window
went to eventlist including CM messages. However,some filters I have defined
to use Multi-shot, send events to both eventlist and the multi-shot window. Is
this expected behaviour. As I will be using several displays which call up the C3
window with eventlist, should I only use filters if I want action routines other
than multi-shot window. Also I do not want the CM events appearing on all
eventlist windows
I think the documentation is good and the bookreader on-line help is brilliant.
I have been used to VCS for some time and old habits die hard.
Do you know who I can mail in the OSF engineering group with my
requests/complaints.
Thanks,
Dave.
|
| Dave,
>>When I disconnect the cable from a DECserver 200 using the LAT protocol, PCM does
>>not recognise that the link is lost. After 24 hrs, I still have the option
>>Connect to Console. Can PCM indicate when it has lost a link. This customer will
>>be managing 200 nodes on the PCM system and it is vital to know if PCM has
>>lost one of its links. The customer will be using TELNET.
Which cable did you pull out? If it was the RS232 one then I wouldnt expect
the connection to go away as we still have a virtual circuit and connection
to the port on the DECserver, if you pulled the ethernet cable, then PCM
should see your LAT session to the DS200 go away almost immediately, it does
on our test systems and I dont know why yours isnt, maybe there is someone
who knows more about LAT reading this that could tell us.
What happens if after the long period (24 hours in your case) you try and
perform the connect?
>>In relation to the eventlist routine and the actions I have defined to use
>>Multi-shot window, I dont understand why some events go to both windows while
>>other events only go to the multi-shot window. When I start up the C3 window, I
>>start the eventlist. At first I thought all events that went to the C3 window
>>went to eventlist including CM messages. However,some filters I have defined
>>to use Multi-shot, send events to both eventlist and the multi-shot window. Is
>>this expected behaviour. As I will be using several displays which call up the C3
>>window with eventlist, should I only use filters if I want action routines other
>>than multi-shot window. Also I do not want the CM events appearing on all
>>eventlist windows
OK, we dont have a "Multi-show window" but we do have a "Multi-Line window"
I assume you are referring to the Multi-Line window which from now on I
will refer to as eventlist. Eventlist has 3 different modes of operation...
1) As an action routine, in this mode the events delivered to the window
are determined by what you set up in your FILTER records. Customizations
are saved in the CONSOLE$APP_DEFAULTS: directory, and the
customize->filter option is disabled on the basis that you have been
given this window for a reason and you should not be allowed to ignore
what you have been given by filtering the events out!!
2) Interactively (Started via a $CONSOLE EVENTLIST/blah/blah/blah command),
in this mode, the window will get ALL events that occur for systems YOU
are allowed access to. Customization made in this mode, such as filters
(from the customize->filter menu option) are saved in your login
directory (or CONSOLE$USER_DEFAULTS if defined)
3) As a "child" of the C3. This mode acts exactly like the interactive one
except that customizations are saved in CONSOLE$APP_DEFAULTS: with a file
name which includes C3 and your USERNAME.
Now, ENS has no way of knowing that if you have 3 eventlists started and
that they all point to your workstation, so it will send the appropriate
events to each eventlist (in fact in the case of the 2 and 3 above, they
get ALL the events which happen, but filter out the ones for systems you
have not been given access, the filtering does not happen within ENS).
So, if you run the C3 all the time on your workstation, you probably do not
want to set up a Filter to display an eventlist (unless you disable the
eventlist child of the C3). The same applies if you run the eventlist
interactively. UNLESS of course you want to get told about events for
systems that you have not been given access to in the database, in which
case setting up a filter to display the eventlist as an action is the way
to go.
So, to sum up, this is all really simple stuff if you wrote it, a little
mind-bending if you didnt, and just think, I left a load of stuff out of
the documentation for this release which I havnt tested enough yet and am
not prepared to support until I have, so it will get more complicated,
trust me ;-)
>>I think the documentation is good and the bookreader on-line help is brilliant.
>>I have been used to VCS for some time and old habits die hard.
Thanks for the compliment, its probably your "old habits" that are screwing
you up ;-)
>>Do you know who I can mail in the OSF engineering group with my
>>requests/complaints.
I dont have a name, Simon may have I will ask him for you, alternatively,
you could try looking in the OSF notes conference although I think OSF/1
like a lot of the large engineering groups are in the fortunate position of
having several product managers, I just hope you get the right one.
Cheers,
Phil
|
| >When I disconnect the cable from a DECserver 200 using the LAT
>protocol, PCM do
>not recognise that the link is lost. After 24 hrs, I still have the
>option
Some clarification is needed here. When you say you "disconnect the
cable" are you disconnecting the the server from the Ethernet or
are you disconnecting the async cable that connects the server port
to the managed system? If you are doing the latter, PCM will never
know that this has happened. If you are disconnecting the ethernet
cable, the daemons should detect this almost immediately as the read
posted to the LTA device should terminate with SS$_HANGUP status and
will then attempt to reconnect every 15 seconds if I remember right.
>In relation to the eventlist routine and the actions I have defined to
>use Multi-shot window, I dont understand why some events go to both
>windows
What do you mean "Multi-Shot WIndow"? As Simon said, the actions
defined in the database are:
PCM Edit> sho action
Full or Brief listing? [f=full, b=brief] (b):
Output file (SYS$OUTPUT):
Archive Clean-up Clean up the Archive area
Broadcast Broadcast an event to a User or Terminal
Mail Mail an event to a User
Multi-Line Window One Event per line in a window
Single-Shot Window One event in one window
So when you say Multi-shot are you really talking about "Multi-Line
Window" which by the way is also referred to as "Eventlist"? In
actuality "Eventlist" is the name of the application. The action
called "Multi-Line Window" in effect runs the "Eventlist" application.
>Also I do not want the CM events appearing on all eventlist windows.
Then you will have to define different filters *AND* action routines
to do what you want. This is becuase the action name is used to
name the mailbox that is used to pass information to the process running
the action. You then define filters to run these two different actions
using whatever filter criteria you want.
Regs,
Dan
|