RE: QNTC file system (mostly) empty

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

I hear you, Charles, but I don't think it is a CPU issue. It is a matter of 
the response from the Windows machines in the domain. It might matter that 
you specify a WINS server, don't know. This is done in the NetServer 
configuration - as the presentation says, there is no "setup" for QNTC.

The presentation has a section on improving performance - I did not look at 
it yet.

Too much fun, man!
Vern

At 08:33 AM 8/4/2004, you wrote:
> Vern,
>
> I'll take a look at the info.
>
> The problem with your idea is that the secondary partition, which was
> obviously down while the primary was down, had all the servers listed
> yesterday morning.
>
> Which doesn't fit into your idea especially when you consider that the CPU
> allocated to the secondary is much smaller than what is on the primary, even
> taking other activity into account.
>
>
> Charles
>
>
> > -----Original Message-----
> > From: Vern Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx]
> > Sent: Wednesday, August 04, 2004 9:21 AM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: QNTC file system (mostly) empty
> >
> >
> > Charles
> >
> > I think it might be a matter of the time it takes for the discovery
> > process. It can take a long time, and it is done at each
> > IPL.
> > ftp://ftp.software.ibm.com/eserver/iseries/web/netserver/commo
> > n/v5r2smb/QNTC_F03.pdf
> > is a presentation on QNTC.Take a look at
> > www.iseries.ibm.com/netserver for
> > more info.
> >
> > HTH
> > Vern
> >
> > At 07:41 AM 8/4/2004, you wrote:
> > >Just an update,
> > >
> > >I came in this morning, did the WRKLNK and all my severs were there.
> > >
> > >It's not possible that somebody did something to the box to
> > fix it.  So I
> > >don't know what's going on.  I may still open a call with
> > IBM to see if they
> > >have any thoughts.
> > >
> > >Charles
> > >
> > >
> > >--
> > >This is the Midrange Systems Technical Discussion
> > (MIDRANGE-L) mailing list
> > >To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > >To subscribe, unsubscribe, or change list options,
> > >visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > >or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > >Before posting, please take a moment to review the archives
> > >at http://archive.midrange.com/midrange-l.
> >
> >
> > --
> > This is the Midrange Systems Technical Discussion
> > (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.