Conference csc32::consolemanager

I see your customer has set the remote server to use TELNET as the default 
protocol, But have they set up the listener information and enabled it for 
the server ports in question?

What happens if the customer does the command:

$ TELNET server listener_num

  Where server and listener_num are the same as they have entered in the
  PCM database?

Cheers,
Phil

Things to do:


Please note I am making some assumptuins here so you may need to change the
commands slightly as I dont know the exact config.


At Server:

  Define telnet listener 2007 port 7
  define telnet listener 2007 connection enable
  Define telnet listener 2008 port 8
  define telnet listener 2008 connection enable


These map the physical port to the listeners.

 Set up IP on server

  Define internet address vvv.xxx.yyy.zzz
  define internet subnet  vvv.xxx.yyy.zzz

As the server is on a different network to the PCM machine  

 define internet gateway vvv.xxx.yyy.zzz network aaa.bbb 

As they are All defines you will need to reboot the server to make them active
or do the same commands with a SET verb.

Aty this point check you can ping the server from the PCM host and try the
TELNET Test Phil suggested.

If you get a connection with TELNET host 2007 you sholud be able to connect via
PCM

At PCM the system entry should look like:


Protocol TELNET


Server Name Internet name of Terminal Server ( or you can put the
vvv.xxx.yyy.zzz form address in)..

Listener Number 2007

System Enabled

Logging Enabled

Scan (Whatever you want).


Hope this helps.

Cheers Simon....

Good day,

I'm running PCM V1.5 (ECO 1) on OSF/1 V3.0. I'm trying to connect a
GIGAswitch console to PCM using telnet.

I can do a:

# telnet 16.155.16.6 2032

and I get the GIGAswitch console OK. But, I can't seem to get PCM to connect...

# console -c gigaswitch
System gigaswitch is disabled or unavailable

Yet, the gigaswitch seems to be configured properly in the editor:

System Name         = gigaswitch
    Information     =
    Connection      = TELNET (terminal server)
    Terminal Server = 16.155.16.6
    Listener Number = 2032
    Scan Profile    =
    Icon filename   = GigaSwitch.xbm
    Console line    = Enabled
    Logging is enabled, directory = /var/opt/console/logs
PCM Edit>

Any ideas what to look for?

Thanks,

Ed

    Ed,
    
        Did you issue a reconfigure command or alternately, restart PCM?
    You can also check to see if the PCM daemon knows about your new
    connection by issuing a console -d -S system_name.
    
    Dave

Hi Dave,

Yes, I'd reconfigured PCM but no luck. Here's some more info:

# console -r
Do You Really want to Reconfigure Console Manager? (N) :y
Console Manager reconfiguration started ...
Console Manager reconfiguration complete
# console -d -S gigaswitch
System gigaswitch not found
# console -d -a
    ------SYSTEM------ ---PID--- STATE -BYTES- -LINES- EVENTS ------USER------
1   gigaswitch         763        TYF        0       0   3.0K
#

Any idea why console -d -S gigaswitch doesn't work?

Thanks, 

Ed

>># console -d -S gigaswitch
>>System gigaswitch not found
>># console -d -a
>>    ------SYSTEM------ ---PID--- STATE -BYTES- -LINES- EVENTS ------USER------
>>1   gigaswitch         763        TYF        0       0   3.0K
>>#

>>Any idea why console -d -S gigaswitch doesn't work?

    It's one of those situations where it works on my system but not yours.
    (I'm running on Ultrix but it shouldn't make a difference.)
    
    Alternately, you can issue the following command:
    
    # console -d -c
    
    This puts you in continuous mode. Press shift-s (i.e. capital S) and
    you should be prompted for the system name.
    
    I'm perplexed as to why you can't connect to the gigaswitch.
    You can define the environment variable CONSOLE_DEBUG to ALL,
    but watch out, you'll be bombarded with information, al lot of 
    which probabily won't make any sense.
    
    You could also try restarting PCM. Make sure all the processes have
    died before restarting by doing a 'ps aux' command.
    
    Dave
    
    

    Do you have enough licenses installed? PCM will configure nodes in the
    order they are present inthe database. If for example, you had 12
    licenses installed and gigaswitch was the 13th system, PCM would 
    not configure the node and mark it disabled.
    
    Regs,
      Dan

Good day,

I've tried the console -d -c then hit shift-S gigagswitch... that works:

                                                 POLYCENTER Console
Manager Summary
                                                           System Details
Host: kaoosc.kao.dec.com                                               
                                   Thu Dec 15 08:20:00 1994

System ............: gigaswitch
Enabled ...........: Yes
Line status .......: Open Failure

In use by .........:

Parent pid ........: 752
Connection type....: TCP/IP

Logging device ....: 61% Full
Last Archive ......: None Performed

Lines of data .....: 0  Bytes: 0
Event total .......: 7

   Crit: 7  Maj: 0  Min: 0  Warn: 0  Clr: 0  Ind: 0


I've also re-booted the alpha... still no go.

I've set the CONSOLE_DEBUG variable to ALL and did a console connect
gigaswitch. It core dumps after about 30 seconds...

-rw-------   1 root     users     720896 Dec 15 08:13 core
# console conn gigaswitch
CMShm: Returning HEADER record
CMShm: Searching for system : gigaswitch
CMShm: Get system archive flag
CMShm: Searching for system : gigaswitch
CMShm: Get system archive flag
CMShm: Searching for system : gigaswitch
CMShm: Get system status
CMShm: Searching for system : gigaswitch
CMShm: Get system archive flag
CMShm: Searching for system : gigaswitch
CMShm: Get system status
CMShm: Searching for system : gigaswitch
CMShm: Get system status
CMShm: Searching for system : gigaswitch
CMShm: Get system status
CMShm: Searching for system : gigaswitch
CMShm: Get system archive flag
CMShm: Searching for system : gigaswitch
CMShm: Get system status

*gigaswitch -                                                          
                                   |  | Console Inactive
Copyright (c) 1994 Digital Equipment Corporation. All Rights Reserved
System gigaswitch is disabled or unavailable
Command: sh: 2263 Memory fault - core dumped
#

Since this is my first attempt at configuring/using PCM on OSF (we're
coming from VAX/VMS and VCS), I'll re-install DCR151 to see if anything
changes...

Thanks,

Ed

Ed,

  Turn off the debug flag, it will not provide you with any
  useful information.

  Do you have, as Dan asked, enough licence units?

  You should not experience a core dump when trying to connect,
  so, something is amiss.

  Can you export your database and mail it to elbrig::sdj then Simon
  can try and reproduce the core dump.

Cheers,
Phil

OK,

So, I'm *almost* convinced that it's not me. I've re-installed
DCROSF151 (using setld -d and setld -l). Here are the steps I took:

1. setld -d DCROSF151
2. setld -l .
3. console -e (to ensure the telnet parts are OK)
4. console -C3 (to startup PCM and try to connect to gigaswitch)
5. Tried command line console connect gigaswitch...

This *should* work, no?

I did check the license as pointed out in .7:

# lmf list full for POLY-CONSOLEMGR
           Product Name: POLY-CONSOLEMGR
               Producer: DEC
                 Issuer: DIGITAL-IM&T
   Authorization Number: BIX-AK-94257-1-KAO-KAOOSC-542
        Number of units: 0
                Version:
   Product Release Date: 14-SEP-1995
   Key Termination Date:
Availability Table Code:
    Activity Table Code: CONSTANT=100
            Key Options: MOD_UNITS
          Product Token: *FOR_DIGITAL_INTERNAL_USE_ONLY*
            Hardware-Id:
         License status: active
      Cancellation Date:
        Revision Number: 0
                Comment:
      Cache Total Units: 100
        Activity Charge: 0

Any other hints/help are appreciated...

Thanks,

Ed

Good day,

I've sent the exported database to elbrig::sdj... thanks Phil.

I've also noticed that the console connect gigagswitch command core
dumps after about 30 seconds (anywhere from 30 - 60 seconds).

Thanks,

Ed

Ed,

  It would appear from our testing that if your host isnt defined in
  either your /etc/hosts file or DNS then we cant resolve it, attempting
  to look up the ip address of your server indicates that this is the case.

  So, try adding your terminal server to /etc/hosts and see if that works.

  It worked for us, your system gives a nice CLK> prompt ;-)

  We shouldnt really need to do a lookup if you give us an address, as we
  are, there is clearly a problem in our code. However, its too risky to
  change it for this release, I have added it to the list of things we
  have to fix for V2.0

Cheers,
Phil
 

Thanks Phil,

Adding the DECserver to /etc/hosts solved the mystery... Thanks

I guess now's a good time to enable the password on the gigaswitch
console... ;^)

Ed

    
    Hi,
    
    I am unable to get PCM to make a connection to a DECSERVER 700 using
    TELNET. I have setup the server exactly the same as another working
    configuration, and defined the port and internet addresses etc.
    
    I can do a $ TELNET ip-address listener-no and I connect straight to
    the console no problem.
    
    I have just discovered the following error in the CONTROLLER_02.LOG,
    
    Socket error on TELNET console for system PMAV11
    Failed to create TCP socket port number 2001
    %SYSTEM-F-TIMEOUT, device timeout
    
    Also, the events screen is reporting an error,
    
    Console link for system PMAV11 lost - %SYSTEM-F-TIMEOUT, device timeout
    
    Any ideas anyone ?
    
    Regards,
    
    Bruce
    

    We have a customer site that is seeing similar problems to .14. The
    reason for why the customer cannot connect is begin investigated but a
    side effect of the problem is that the 'Console Ctrl nn' process
    hangs in an LEF state. Any attempt to connect to any of the other
    consoles using this process hang. 
    
    Also when starting PCM it can takes the controller process 10
    minutes to fail a connection. Are the timeout values when initiating
    the connection specified in the code or are they using the defaults
    supplied by UCX.
    
    Thanks,
    
    Geoff Judd.

    
    re:  .14 
    
    since going home last night my error messages have changed slightly,
    its now;
    
    Socket error on TELNET console for system PMAV19
    Failed to create TCP socket port number 2004
    %SYSTEM-F-UNREACHABLE, remote node is not currently reachable
    
    Also,
    
    On the DECserver, my port had a username which was clearly console text
    but it dosent seem to want to connect ...
    
    
    My telnet command still works though ...
    
    Any ideas ?
    
    Bruce
    

    
    re:- .14
    
    UCX needed the name of the terminal server defined.
    
    ie.
    
    $ UCX
      DEFINE/SET HOST "pmat01"/address=93.49.16.31/alias="PMAT01"
    
    Note the case sensitivity. It still seems strange to me that the TELNET 
    access worked but PCM needed the remote terminal server name defined
    (even though this name is only used as reference by TSM ?).
    
    Thank to Geoff Judd for his help on this one.
    
    Regards,
    
    Bruce
    
    
    
    

  Ahaa, the light goes on! Yes, this is a known problem, it would appear
  that we dont do a name resolve in quite the correct way, I will attempt
  to fix this for the next release.

Cheers,
Phil

    >Note the case sensitivity. It still seems strange to me that the TELNET
    >access worked but PCM needed the remote terminal server name
    >defined (even though this name is only used as reference by TSM ?).
    
    According to your previous notes you entered the ip-address when you did
    the TELNET command. If you entered the ip host-name of the decserver in
    the PCM database and UCX did not know about this host-name then PCM
    will fail. Telnet would have failed if you had done
    
    TELNET host-name listener-number
    
    Regs,
      Dan

    
    re:- .19
    
    The only info PCM had about the terminal server was the ip address and
    the listener number not the terminal server name. The name of the
    terminal server only appears in the TSM database on the local software
    load host. Am I missing something here ?
    
    Regards,
    
    Bruce

    I thought that you had placed the ip *host-name* of the decserver in
    the PCM database. If the UCX SET HOST command has not been done then
    PCM wouldn't have been able to connect hence my comment in -2. No big
    deal!
    
    Regs,
      Dan