[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | POLYCENTER Console Manager |
| Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
| Moderator: | CSC32::BUTTERWORTH |
|
| Created: | Thu Aug 06 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1541 |
| Total number of notes: | 6564 |
Hi,
This has got me beat. I have about 20 HP-UX boxes connected up to console
manager using telnet, not LAT. Until recently these were connected via
DECserver 90TLs. They then got swapped over to DECserver 900TMs in a DEChub
900.
When connected to the 90TL no problem. Now, connected to the 900TM if the
HP-UX box is shutdown and power cycled it will not reboot properly. It hangs
at prompts where before it just waited for the timeout and continued.
A HP-UX box has two stages of booting, the fisrt stage where it is reading
startup code for PROM, setting boot path etc, and the second where it has
actually accesses the disk load HP-UX etc. It hangs in the first phase.
Why?
DPDPCM2 port 2 is a 90TL port that works, DPDPCM6 is a 900TM port that does
not.
I am using NAS 1.5 on the 900TM.
TSM_SVR_DPDPCM2> sho server
DECserver 90TL V1.1A BL45-11 LAT V5.1 ROM 2.0.0 Uptime: 1 04:27:05
Address: 08-00-2B-A1-8A-69 Name: DPDPCM2 Number: 0
Identification:
Circuit Timer: 80 Password Limit: 3
Console Port: 1 Prompt: dpdpcm2>
Inactivity Timer: 30 Queue Limit: 100
Keepalive Timer: 20 Retransmit Limit: 8
Multicast Timer: 30 Session Limit: 64
Node Limit: 200 Software: MNENG1
Service Groups: 0, 4
Enabled Characteristics:
Announcements, Broadcast, Dump, Lock
TSM_SVR_DPDPCM2> sho port 2 char
Port 2: Server: DPDPCM2
Character Size: 8 Input Speed: 9600
Flow Control: XON Output Speed: 9600
Parity: None Signal Control: Disabled
Stop Bits: Dynamic
Access: Remote Local Switch: None
Backwards Switch: None Name: PORT_2
Break: Local Session Limit: 4
Forwards Switch: None Type: Ansi
Default Protocol: Telnet
Preferred Service: None
Authorized Groups: 0, 4
(Current) Groups: 0, 4
Enabled Characteristics:
Failover, Input Flow Control, Loss Notification, Message Codes,
Output Flow Control, Verification
TSM_SVR_DPDPCM2> sho port 2 telnet char
Port 2
Profile: Character
Echo: Remote Newline From Term: <CR>
Toggle Echo: ^E Newline From Host: <CRLF>
Binary: Disabled Newline To Term: <CRLF>
Xmit Char Size: 8 Newline To Host: <CRLF>
Rcv Char Size: 8 Input Flow Control: Enabled
Signal Req: Enabled Output Flow Control: Enabled
IP: +s +f ^Y Local Msg Verify: Enabled
SYNCH: +s -f ^X Local Switch Recog: Enabled
AYT: -s -f ^T Quote: None
AO: -s +f ^O
EOR: -s -f None
BRK: -s -f None
TSM_SVR_DPDPCM2> sho port 2 telnet server char
Port 2
Xmit Char Size: 8 Newline From Term: <CRLF>
Rcv Char Size: 8 Newline From Host: <CRLF>
IP: None Newline To Term: <CRLF>
AYT: None Newline To Host: <CR>
AO: None EC: None
EOR: None EL: None
NOP: None
BRK: None
----------------------- and 900TM ---------------------------------
TSM_SVR_DPDPCM6> sho port 9 char
Port 9: (Remote) Server: DPDPCM6
Character Size: 8 Input Speed: 9600
Flow Control: XON Output Speed: 9600
Parity: None Signal Control: Disabled
Stop Bits: Dynamic Signal Select: CTS-DSR-RTS-DTR
Access: Remote Local Switch: None
Backwards Switch: None Name: PORT_9
Break: Local Session Limit: 4
Forwards Switch: None Type: Ansi
Default Protocol: Telnet Default Menu: None
Preferred Service: None
Authorized Groups: 0
(Current) Groups: 0
Enabled Characteristics:
Failover, Input Flow Control, Loss Notification, Message Codes,
Output Flow Control, Verification
TSM_SVR_DPDPCM6> sho port 9 telnet char
Port 9
Profile: Character
Echo: Remote Newline From Term: <CR>
Toggle Echo: ^E Newline From Host: <CRLF>
Binary: Disabled Newline To Term: <CRLF>
Xmit Char Size: 8 Newline To Host: <CRLF>
Rcv Char Size: 8 Input Flow Control: Enabled
Signal Req: Enabled Output Flow Control: Enabled
IP: +s +f ^Y Verification: Enabled
SYNCH: +s -f ^X Switch Character: Enabled
AYT: -s -f ^T Quote: None
AO: -s +f ^O
EOR: -s -f None
BRK: -s -f None
TSM_SVR_DPDPCM6> sho port 9 telnet server char
Port 9
Xmit Char Size: 8 Newline From Term: <CRLF>
Rcv Char Size: 8 Newline From Host: <CRLF>
IP: None Newline To Term: <CRLF>
AYT: None Newline To Host: <CR>
AO: None EC: None
EOR: None EL: None
NOP: None BRK: None
Echo Negotiation: Noinitiate
David McKenzie
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1311.1 | VAX and 900TM does not work either | CMGOP2::meod22dgp4.gen.meo.dec.com::mckenzie | --> dangling pointer | Tue Jun 11 1996 22:01 | 11 |
| Hi,
I also have a VAX OpenVMS box connected to the 900TM. Irebooted and power cycled it as well.
Guess what? it does not come up properly either. The lines are smeared accross the screen.
It looks like <cr> is not acted on
Has anybody succesfully used a 900TM as a DECserver for PCM?
David McKenzie
|
| 1311.2 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Wed Jun 12 1996 11:51 | 25 |
| RE -1.
This may be due to the fact that the HP sends LF and
not CRLF pair. Change the telnet server characteristics
for the port in question via
Local> change port x telnet server newline from host <LF>
It's best to do the above with PCM down. And BTW,
when manipulating the telnet server chars,
the "host" is the device connected to the physical
terminal server port and the "terminal" is actually
the system that has a telnet conection to the port.
In this case it's the PCM engine.
RE -2. What happens if you shutdown PCM and then
telnet to the server port one of the systems is
connected to, .i.e., do
TELNET server-name listener-number
Do you see the same phenomena?
REgards,
Dan
|