Conference csc32::consolemanager

Delio,

  Exactly what do you want, your question is not clear to me?

  Do you want to -

	1) Run Console Manager on a VAXft system, or
	2) Manage a VAXft system from another system running
	   Console manager.

  If Number 2 then yes they can do that if the VAXft has a Console
  Port which adheres to the rules specified in the SPD (RS232,
  XOn/XOfF etc.)

  If Number 1, then we dont know, we have never tried it as we dont
  have access to a VAXft. This is also the reason why it doesnt appear
  in the SPD or SSA.


Cheers,
Phil

    
    Phil,
    
    	thanks for the quick answer, I tray to be more clear about VCS and
    
    VAXft.
    
    We have a Workstation 4000/60 and we control a few VAXs' and some VAXft
    
    via a decserver 200. When we connect a VAXft we need connect both the
    
    consolles and 2 consolles "eats" 2 license, but we connect ONLY 1 CPU.
    
    Connecting 2 consolle we need give them 2 NAMES but is 1 machine.
    
    Onto the VCS doesn' t exist predefined profile for VAXft 610 neither
    
    VAXft 810.
    
    Events generated from the VAXft and displayed by the VCS are sended to
    
    SNS and there are not recognised because the name of VAXft into the VCS
    
    coud not be the one in the decnet database, for the problem of the 2
    
    consolles.
    
    What I meen for VAXft control is have a predefined profile that allows
    
    me to define the 2 consolles as ZONE A and ZONE B of the same machine
    
    with 1 name.
    
    		Have a nice Easter
    				    see you 
    				Delio.

Delio.


  With PCM, you still need two licences. PCM does not know how many
  systems are on the end of the serial lines, how can it!

  The action routine you are using to send events to SNS should
  be modified in order to "change" the name of the system when
  the event has come from your second VAXft console.

Cheers,
Phil

    
    	Phil,
    		thats really kind of you answer to me so quick.
    
    Coming to VAXft what I can answer to customer is that in this 
    
    version on PCM (1.1) FT is seen as 2 CPU and not like 1 machine.
    
    Am I right?
    
    			Regards,
    						Delio.

Yes, you are right.

    I would suggest that the best way of doing things anyway, is to send
    SNS messages into CM. There will be a service kit available to do this
    (contact Guy Balaguer@VBO) in June/July. You will then, not have the
    problem you mention.
    
    Phil,
    
    Just wondering, when CM puts messages out, does it use the real node
    name, or does it/can it use the alias? If not, it would be good for a
    next release to be able to force the alias for ENS and 'SET HOST'
    options.
    
    Martin

Martin,
    
>>    Just wondering, when CM puts messages out, does it use the real node
>>    name, or does it/can it use the alias? If not, it would be good for a
>>    next release to be able to force the alias for ENS and 'SET HOST'
>>    options.

  The "real" node name of what? If you mean the serviced system, how exactly
  are we supposed to know what it is? We can only use the information we
  have in our database!

Cheers,
Phil

    Sorry Phil, could've put that better. What I meant is that each console
    line is associated with a particular 'node name'. This means that an FT
    machine will have two console lines, with different names. Therefore,
    it would be good to be able to use an 'alias' when ever using CM. (This
    could also be useful for anything where you don't care which 'system' you
    connect to)
    
    When defining the serviced node, you would have the option of saying
    that you can use the alias instead of the serviced node name. This
    would mean that if you had two serviced nodes with the same alias it
    would connect to either one. At the moment, VCS does this with the 'Set
    Host' option on the C3, but not the console.
    
    The advantage here is that you can use any FT console, you don't care
    which, but you can also connect to a specific one, if you so desire.
    
    To sum up :-
    
    Serviced node would have an alias, and an option to force use of alias.
    If alias is used and forced, it can connect, monitor, or set host to any 
    serviced node that has that alias. If you use the serviced node name,
    then you connect to that console directly.
    
    Handling ENS is going to be more difficult, but one step at a time.
    
    Martin

  Ahh OK, I see what you are getting at now, we could almost do this with 
  the "group" concept we have today. It still means however, that there
  would have to be two licences (one for each VAXft console).

  I'll add this to our wishlist.

Cheers,
Phil

    
    Phil,
    
    	I have an other item for your CM wishlist: insert event list and 
    scan profile about FT machine.
    
    		Regards, 
    					Delio.

>>    	I have an other item for your CM wishlist: insert event list and 
>>    scan profile about FT machine.

  Sigh, unfortunately, we dont have the manpower, equipment or time to do 
  this, or update any of the other events and profiles that were previously 
  shipped with VCS and CM V1.0. For this reason we are trying to get this
  stuff done by the product groups responsible for the various
  software/hardware. 

  Thanks for the suggestion anyway

Cheers,
Phil