ITEM: DR5065L

TCPCOM | telnet failing



Question:

os lv 4.2.1
model 7025

COMMO///getting 1831-119 nfs error on reboot of production box

Response:

Customer Contact

Response:

Response:


FOR INITIAL ITEMS, COMPLETE ALL FIELDS 
FOR UPDATES/ELECTRONIC ITEMS, COMPLETE THE FIELDS MARKED WITH *

 ENV:os lv 4.2.1
     model 7025

*CUSTOMER REP:

 PROBLEM: ugraded to 4.2.1. Customer did a licensing change from
 2 to 8.  
 Getting 1831-119 nfs error on reboot of production box.
 Cannot telnet into the box.
*ACTION TAKEN: \#errpt -> e18e984f 
  Conferenced in Robert M. for assistance.  Looks like this is a
 defect. 
 \#lslpp -l bos.net.nfs.client -> version 4.2.1.0
 \#lslpp -l bos.net.tcp.client -> version 4.2.1.0

  Customer will go check this and let us know

Per item DH0136.  Had customer uncomment the following lines in 
/etc/pse.conf:
m       timod                           \# TLI module
m       tirdwr                          \# TLI read/write interface
The timod and tirdwr appear to be drivers that are required for the
streams environment.

Also had the customer do: 
 stopsrc -g nfs      -----> ok
 stopsrc -g tcpip    -----> ok
 stopsrc -g portmap  -----> ok
 rm -rf /etc/state /etc/sm /etc/sm.bak /etc/rmtab /etc/xtab
 startsrc -g portmap ------> ok
 startsrc -g tcpip ----> ok
 startsrc -g nfs -> ok

 still getting cannot telnet in and still getting the errors from
 earlier.

 Had customer reboot since the pse.conf will have to be reloaded
 from boot.

 After reboot problems still persist.  Having customer download
 the lastest ptfs for 
 \# bos.net.nfs.client -> U451507
 \# bos.net.tcp.client -> U451567

 Customer will call back  when this is completed.
 *ACTION PLAN: WOCB

 TEST CASE: n/a


Response:

Customer Contact

Response:

Response:


FOR INITIAL ITEMS, COMPLETE ALL FIELDS 
FOR UPDATES/ELECTRONIC ITEMS, COMPLETE THE FIELDS MARKED WITH *

 ENV:os lv 4.2.1
     model 7025

*CUSTOMER REP: Doug Peterson

 PROBLEM: Customer installed the newest filesets but he for
 bos.net.nfs.client and bos.net.tcp.client.  

*ACTION TAKEN:  Customer is still getting the rpc errors 1831-119.
 unable to register.

 df -> space on files are ok.

 Customer also mentions that nfsd does not start.
 biod does.

 Customer has no exports this is why nfsd does not start
  \#vi /etc/services  telnet is in and shows for *.23
 \#vi /etc/inetd.conf telnet line is in and uncommented.
   :set list -> shows there is spaces instead of tabs
    between his telnet fields.  Mentioned this could cause problems.

    Customer says he has the same thing for all the others, but,
    processes like ftp are working.

   Customer can telnet, but it hangs after the escape character.

   Also had customer increase licensing from 8 to 64.

   Customer is going to reboot and call back.  He wants to work
   on telnet problem first.

*ACTION PLAN:  requeue item to tcpcom to WOCB.

 TEST CASE: n/a


Response:

Response:

ENV:4.2
CUSTOMER REP:Doug Peterson
PROBLEM:Customer cannot telnet into his system.
ACTION TAKEN:I had him do a
lssrc -t telnet hangs
ps -ef|grep inetd it was running
stopsrc -s inetd
startsrc -s inetd
lssrc -t telnet still hangs
pg /etc/inetd.conf  looks ok
stopsrc -s inetd
cd /usr/lpp/bos.net/inst_root/etc
cp inetd.conf /etc/inetd.conf
startsrc -s inetd
now he can telnet ok
he getting error 1831-119 rpc.statd
also
e18e984f  failing module lockd in error log
ok to lower priority
customer change order in which he mount files 
ACTION PLAN:wocb
TEST CASE: NONE

Response:

Customer Contact

Response:

*CUSTOMER REP: Doug Peterson

 PROBLEM: has applied PTFs, rebooted, and same problem..

*ACTION TAKEN:
checking his /etc/pse.conf against a working 4.2.1 production 
system we have here, I had him uncomment the following:
\# PSE communication protocols

d+      xtiso   unixdg  /dev/xti/unixdg \# unix domain datagrams \# nfsv3
d+      xtiso   unixst  /dev/xti/unixst \# unix domain byte-stream       \# nfsv3
d+      xtiso   udp     /dev/xti/udp    \# UDP/IP        \# nfsv3
d+      xtiso   tcp     /dev/xti/tcp    \# TCP/IP        \# nfsv3

*ACTION PLAN:
CWCA- Customer WCB if needed.
 TEST CASE:


Response:

Response:

Customer called back to say that this last set of lines we uncommented have
fixed the problem completely.
So to recap - there seems to be a problem with
migrations of 4.2.0 to 4.2.1 that leaves some critical lines in 
/etc/pse.conf commented out. -These affect operation of the entire nfs
group.
To correct, ensure that all of the following are uncommented:
\# PSE communication protocols

d+      xtiso   unixdg  /dev/xti/unixdg \# unix domain datagrams \# nfsv3
d+      xtiso   unixst  /dev/xti/unixst \# unix domain byte-stream       \# nfsv3
d+      xtiso   udp     /dev/xti/udp    \# UDP/IP        \# nfsv3
d+      xtiso   tcp     /dev/xti/tcp    \# TCP/IP        \# nfsv3

\# PSE modules

m       timod                           \# TLI module    \# nfsv3
m       tirdwr                          \# TLI read/write interface      \# nfsv3



Support Line: TCPCOM | telnet failing ITEM: DR5065L
Dated: September 1997 Category: N/A
This HTML file was generated 99/06/24~13:30:15
Comments or suggestions? Contact us