[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference irocz::terminal_servers

Title:Terminal Servers
Notice:See Note 2 for Directory of important notes. Please use keywords.
Moderator:LAVC::CAHILLON
Created:Tue May 14 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3547
Total number of notes:12300

3422.0. "NAS 2.0 SW-Status PC=0786D5F0,C=0004" by UTOPIE::FISCHER_J () Tue Jan 28 1997 03:38

Hi,

my customer asks what the following software-status means
and which there can be that the software-status is not "Normal".

Furthermore the command 'show server' shows the software-parameter
"<<STD>>" instead of "WWENG2" which he can see by committing
the command 'list server'.

Can anybody tell me any reasons why he gets this software-status
and why there are differences between the output of 'show/list server'?

Any help will be highly appreciated.

Thanks,
Johann

-----------------------------------------------------------------------------
Network Access SW V2.0 for DS700-16 BL10-40  ROM V4.0-0  Uptime:   1 04:25:50

Address:   08-00-2B-38-EB-BB   Name:   48B01              Number:     2

                     Cur  High  Max
Active Ports:          2     3   16     Minutes To Shutdown:        N/A
Active Users:          2     2   16     Discarded Nodes:              0
Queue Entries:         0     0  100     Resource Errors:              0

Available Services:   65    65  N/A     Port Framing Errors:          0
Local Services:        2     2    0     Port Parity Errors:           0
Reachable Nodes:      23    23  100     Port Overrun Errors:          0

                                        Boot Device:        Ethernet: 0
Active Circuits:       0     0   32     Primary Hosts:             G900
Connected Nodes:       0     0   32     Load Address: AA-00-04-00-84-07
Connected Sessions:    3     4   64     Dump Address: AA-00-04-00-84-07
% CPU Used:            2    85  100     Console User: AA-00-04-00-20-07
% Memory Used:        24    24  100     Boot Protocol:              MOP

Selftest Status: Normal
==>Software Status: PC=0786D5F0, SP=079C6160, SR=2504, ME=00000000, C=0004 <==
================ ------------------------------------------------------

T.RTitleUserPersonal
Name
DateLines
3422.1LAVC::CAHILLJim CahillTue Jan 28 1997 10:1517
> Network Access SW V2.0 for DS700-16 BL10-40  ROM V4.0-0  Uptime:   1 04:25:50
> ...
> Selftest Status: Normal
> ==>Software Status: PC=0786D5F0, SP=079C6160, SR=2504, ME=00000000, C=0004 <==

It looks like the server reloaded the day before this display was generated
due to an illegal instruction exception.

Was a crash dump captured?
 
> Furthermore the command 'show server' shows the software-parameter
> "<<STD>>" instead of "WWENG2" which he can see by committing
> the command 'list server'.

I don't know why "<<STD>>" is being displayed.

Jim
3422.2< RE .1 >UTOPIE::FISCHER_JWed Jan 29 1997 12:3767
Hi Jim,

thanks for the reply, my customer has provided a dump, but this dump
has been forced via the CRASH-command (not the same as the first one
that could not be captured). 
Hopefully it will contain some useful information for you. However,
the setup of the dump file on the dump host was always o.k. (and
worked in the second case of forced dump) --> could be some (physical ?)
network problem (or heavy load, broadcast storm,..) before or during
the first crash, thereby preventing the DECserver to even dump "successfully". 


The location for the dumpfile is:
UTOPIE::DISK$USER3:[FISCHER_J.PUBLIC]DS748B01.DMP;1

Thanks,
Johann

Local> show server
TSM_SVR_48B01> sh server


Network Access SW V2.0 for DS700-16 BL10-40  ROM V4.0-0  Uptime:   3 05:17:47

Address:   08-00-2B-38-EB-BB   Name:   48B01              Number:     2

Identification:

Circuit Timer:            80           Password Limit:            3
Console Port:              1           Prompt:              Telnet>
Inactivity Timer:         30           Queue Limit:             100
Keepalive Timer:          20           Retransmit Limit:         16
Multicast Timer:          30           Session Limit:            64
Node Limit:              100           Software:            <<STD>>
============================================================???????
Service Groups:   0

Enabled Characteristics:
Announcements,  Broadcast,  Dump,  Heartbeat,  Lock



Local> show server status

Network Access SW V2.0 for DS700-16 BL10-40  ROM V4.0-0  Uptime:   1 04:25:50

Address:   08-00-2B-38-EB-BB   Name:   48B01              Number:     2

                     Cur  High  Max
Active Ports:          2     3   16     Minutes To Shutdown:        N/A
Active Users:          2     2   16     Discarded Nodes:              0
Queue Entries:         0     0  100     Resource Errors:              0

Available Services:   65    65  N/A     Port Framing Errors:          0
Local Services:        2     2    0     Port Parity Errors:           0
Reachable Nodes:      23    23  100     Port Overrun Errors:          0

                                        Boot Device:        Ethernet: 0
Active Circuits:       0     0   32     Primary Hosts:             G900
Connected Nodes:       0     0   32     Load Address: AA-00-04-00-84-07
Connected Sessions:    3     4   64     Dump Address: AA-00-04-00-84-07
% CPU Used:            2    85  100     Console User: AA-00-04-00-20-07
% Memory Used:        24    24  100     Boot Protocol:              MOP

Selftest Status: Normal
Software Status: PC=0786D5F0, SP=079C6160, SR=2504, ME=00000000, C=0004
================ ??????????????????????????????????????????????????????
3422.3LAVC::CAHILLJim CahillWed Jan 29 1997 14:545
A dump generated using the CRASH command won't help answer the question
of why the server previously crashed.

Delete the dump file in [.PUBLIC] and wait for the server to crash again.

3422.4< again >UTOPIE::FISCHER_JMon Feb 03 1997 02:3914
Hi Jim,

I,m sorry, but I,ve to ask you again, what <<STD>> at the
software-parameter means and why it is displayed,
because my customer asked for it again.

I,ve tried to find it out myself, but I had no luck in getting any
answer about it. Perhaps you can help me getting any information
about this software-status, if not maybe you can give me a hint
who can help me or what I can do to get this information.

Thanks,
Johann

3422.5LAVC::CAHILLJim CahillMon Feb 03 1997 10:0621
> I,m sorry, but I,ve to ask you again, what <<STD>> at the
> software-parameter means and why it is displayed,
> because my customer asked for it again.

I have no idea...  I've searched the DNAS source code and can't find any
place where that string appears.

Has anyone else seen this before??

> Perhaps you can help me getting any information
> about this software-status

As I said in .1:

> It looks like the server reloaded the day before this display was generated
> due to an illegal instruction exception.

A crash dump is needed in order to get any more information about this
condition.

Jim
3422.6IROCZ::D_NELSONDave Nelson LKG1-3/A11 226-5358Mon Feb 03 1997 11:2119
RE: .5

>> I,m sorry, but I,ve to ask you again, what <<STD>> at the
>> software-parameter means and why it is displayed,
>> because my customer asked for it again.

> I have no idea...  I've searched the DNAS source code and can't find any
> place where that string appears.

That's because it's in the ROM Firmware.  One of the MOP options is to load
the "Standard" image for a particular host.  I think it's based on a 
registration in the NCP/NCL database.  I have seen this before, but I don't
know exactly how you get it to happen.  Maybe you define a NULL-string for
the software image name?

Regards,

Dave

3422.7The load host initiated the re-bootIROCZ::RRICHARDMon Feb 03 1997 16:3239

  Hi,

  I believe Dave is correct.  The Software name is  displayed as <<STD>> 
  because the dump/load host initiated a re-boot following the crash dump.  
  The server would normally re-boot on it's own, in which case it would request
  the load image specified in NVRAM, usually WWENG2. However, because the load 
  host requested the reboot and didn't specify an image name the server's 
  subsequent boot request will be targeted to the default image configured via
  MOP/NCP on the load host.  The server's BOOT/DIAGNOSTIC ROM code apparently 
  doesn't pass the image name to the operational firmware in this case. 

  You could probably correct the problem by changing the node characteristics
  for the server in the host's database.
 
  For example, changing :

    Node Volatile Characteristics as of  3-FEB-1997 16:22:47

    Remote node =   13.100 (TEST)

    Service circuit          = SVA-0
    Hardware address         = 08-00-2B-0D-B1-ED
    Load file                = MOM$LOAD:WWENG2.SYS
    Dump file                = MOM$LOAD:TEST.DMP

  to:

     Node Volatile Characteristics as of  3-FEB-1997 16:22:47

     Remote node =   13.100 (TEST)

     Service circuit          = SVA-0
     Hardware address         = 08-00-2B-0D-B1-ED
     Dump file                = MOM$LOAD:TEST.DMP


  bob r.
3422.8< thanks for all support >UTOPIE::FISCHER_JWed Feb 05 1997 12:181