Conference netcad::hub_mgnt

Oh, I forgot to mention that LIGOs (I forget the marketing name for the
thingies that let you switch ports back-to-front) are not supported in
the X1.0.10 field test version of clearVISN Resilience, but will be in
the real version 1 product (and in a near-future ft release).

Tom

    
    RE .-1
    
    ...That is *MODULE* ligos are not saved/restored - (ligo settings used
    by a module resident in a docking station).  
    
    *CHASIS* / *MAM* ligos ARE saved restored by the "DEChub 900 Manager" 
    backup/restore scripts.
    
    (chasis ligos are the ones you see/set in the HUBwatch LAN interconnect
    screen, and typically the ones you care about.  Module ligos only 
    matter for modules in a docking station).
    
    Bottom line is that the "DEChub 900 Manager" scripts should
    successfully backup & restore your hub backplane configuration;
    (keep in mind that you must save/restore "port groupings" for 
    PORTswitch repeaters separately).
                                                              Carl.
    

Field test version X1.0.11 of clearVISN Resilience is now available.
This kit is darned close to what will be shipping.  It is a Windows
kit that can also be installed on and works with Windows NT.

	> ftp slink.dechub.lkg.dec.com
	Username: anonymous
	Password: <your name here, please>
	ftp> binary   <this toggles between ASCII/binary.>
	ftp> prompt   <this disables annoying "Do you want this file" prompts>
	ftp> cd [.resilx11]
	ftp> mget *.*
	ftp> quit

	Directory DKB0:[ANONYMOUS.RESILX11]

	DATA.Z;1          1262/1263    25-OCT-1995 11:34:28.53
	README.TXT;1        61/63      25-OCT-1995 11:34:19.83
	SETUP.EXE;1         91/93      25-OCT-1995 11:33:54.00
	SETUP.INS;1          8/9       25-OCT-1995 11:33:52.13
	SETUP.PKG;1          1/3       25-OCT-1995 11:34:25.35
	_INST16.EX_;1      521/522     25-OCT-1995 11:34:01.59
	_ISDEL.EXE;1        15/15      25-OCT-1995 11:33:59.77
	_SETUP.DLL;1        19/21      25-OCT-1995 11:33:57.74
	_SETUP.LIB;1       178/180     25-OCT-1995 11:35:22.34

	Total of 9 files, 2156/2169 blocks.

Sometime in the next day or so, I'll add the users guide manual in that 
same directory.  It contains important configuration and restriction 
information for using the product.

If you copy it, please let me know.

Tom Hood

Field test version X1.0.12 of clearVISN Resilience is now available.
This kit was going to be the final one, but in honor of Halloween, there
will be an X1.0.13 in the next few days.  

This is a Windows kit that can also be installed on and works with Windows NT.

	> ftp slink.dechub.lkg.dec.com
	Username: anonymous
	Password: <your name here, please>
	ftp> binary   <this toggles between ASCII/binary.>
	ftp> prompt   <this disables annoying "Do you want this file" prompts>
	ftp> cd [.resilx12]
	ftp> mget *.*
   <then do the following if you want to get the users guide...>
	ftp> ascii
	ftp> cd [-.resildoc]
	ftp> get RESIL_INSTALL_USE_V1.PS
	ftp> quit

What you'll get are the following files (sizes in OpenVMS blocks, where
one block is 512 bytes)...

	Directory DKB0:[ANONYMOUS.RESILX12]
	  DATA.Z;1             718/720     31-OCT-1995 10:05:41.37
	  README.TXT;1          63/63      31-OCT-1995 10:05:38.88
	  SETUP.EXE;1           91/93      31-OCT-1995 10:05:10.52
	  SETUP.INS;1            8/9       31-OCT-1995 10:05:08.96
	  SETUP.PKG;1            1/3       31-OCT-1995 10:06:07.53
	  _INST16.EX_;1        521/522     31-OCT-1995 10:05:21.13
	  _ISDEL.EXE;1          15/15      31-OCT-1995 10:05:15.07
	  _SETUP.DLL;1          19/21      31-OCT-1995 10:05:13.47
	  _SETUP.LIB;1         178/180     31-OCT-1995 10:05:16.66
	Total of 9 files, 1614/1626 blocks.

	Directory DKB0:[ANONYMOUS.RESILDOC]
	  RESIL_INSTALL_USE_V1.PS;1    5979/5979  26-OCT-1995 10:56:14.78

There are important configuration restrictions when doing a restore on a 
hub in order to maintain connectivity between the workstation and the hub.
Read the Installation & Use manual for more details.

Again, if you copy it, please let me know.

If you find bugs, PLEASE LET ME KNOW IMMEDIATELY!

Tom Hood

when trying to copy RESIL_INSTALL_USE_V1.PS;1
i end up with 

%FTP-E-OUTPROCF, Error processing output file AP000_TOOPCS:[USERS.SELLES]RESIL_I
NSTALL_USE_V1.PS;1
-RMS-W-RTB, 34001 byte record too large for user's buffer

i am copying for vms to vms thru UCX ftp 
any idea ? i use ascii mode as it is a Postscript file 

PJ

>-RMS-W-RTB, 34001 byte record too large for user's buffer
>
>i am copying for vms to vms thru UCX ftp 
>any idea ? 

Just copy in "image" mode.
-Chuck

Oh, I forgot to mention here...

For 8-1/2 x 11 (US), copy [anonymous.resildocs]RESIL_8_X_11.PS;1
For A4 (elsewhere),  copy [anonymous.resildocs]RESIL_A4.PS;1

Tom

Hi Folks,

which is the status of clearVISN for UNIX ?

Who could tell the release date of the UNIX version  ?

Arturo Lopez
Cologne Germany

> Who could tell the release date of the UNIX version  ?

	Check with Jack NAC::Forrest.

    Hello,
    
    I.m triyng theclearVISN Resilience..it is great !!
    
    2 suggestion:
    
    1. The Status window is not so clear to read (small characters, small
    window...) Have you planned to improve the quality?
    One way should be to change the color of the characaters: white instead 
    of black
    Another way should be to change the background to white
    
    2. You said that the Hubwatch is not a prerequisite but, if it is
    installed, the clearVISN Resilience Backup will use the HW_AGENT.DAT
    file.
    I think it should be useful (for who that doesn't have HUBwatch) to 
    save in that file the list of the agents (like we do with HUBwatch)
    
    Many thanks for your attention
    
    Francesco

    Hello,
    
    any plan to support the DECpacketprobe?
    
    As you know the major configuration problem of a DECPacketprobe is the
    Watchdog alarm table than can be very big (lots of domains with many
    alarm each)
    The only way that we have today is to save one alarm at a time using the
    Watchdog window's commands.
    
    Hoping...
    Francesco

Anything *can* be done, but the shipping version acts and looks like the
x15 version. Work has already started for the V2.0 version which will 
include GIGAswitch support.  I'll forward your note about the packetprobe
to the project leader for consideration.

    
    Can we assume that when the files are write-protected, you don't want
    us using that version anymore?
    
    In addition, it seems like x22 is the latest. However, previous notes
    alluded to x12 being close to the shipping version. So, the question
    is, is there a located for the version to be shipped so we can use this
    and then also field test the latest?

The answer is...

The final Resilience V1.0 kit may have been made. 
Unfortunetly, there have been a string of "final" V1.0 kits, and we have
not put them in the ftp area because they all report themselves as V1.0.
I can promise you there will not be another X version.

If it is the final kit this time, you can expect to see it in the ftp
area on slink soon.

And yup, if there's no read access, don't read 'em.

	Tom;

	Will the new clearVISN products, that were announced today, be 
	available on the net? Will StoneyBrook allow us to use it internally
	to become familiar with use of these new products or will there
	be licensing issues?

	-Larry

>	Will the new clearVISN products, that were announced today, be 
>	available on the net? Will StoneyBrook allow us to use it internally
>	to become familiar with use of these new products or will there
>	be licensing issues?

Stuff we develop usually gets put on the net.  But let us finish making
it first, OK? ;-{)}

Joint development stuff involves licensing, which means real money, about
which I happily refer you to Jack NAC::Forrest, clearVISN Product Manager.

tom

	What's this..... announce a product and not have the software finished!
	What are we....Microsoft.... 

	Biggest complaint I get about HUBwatch is customer misunderstanding
	of the word "management". ie... Use HUBwatch to manage your DEChub.
	They think manage will do everything. I have to explain the difference
	between the words "manage" and "monitor". The price of NETview, or
	having to use OpenView, usually eliminates the "monitor" portion of 
	the network. I assume that with clearVISN, I can use the word 
	"manage" as an all encompassing word for control of the DECHub, and 
	customers will not have problem with the word "managing" of the hub.
	I hope I can get my hands on these products soon, as I would love to
	show customers a full network management product, with support for
	other vendors products (Bay & Cisco & 3Com) (what about the Proteon
	product...or will that be a given as the RouteAbout is based on this
	code?).

	I was hoping Digital would work out a similar agreement as with
	the ProbeWatch software and licensing with Frontier.

	-Larry	

>	I was hoping Digital would work out a similar agreement as with
>	the ProbeWatch software and licensing with Frontier.
Larry, 
I don't know anything [some people think I should stop this sentence
right here, but I'll continue anyway] about how the licensing has been
worked.  Alls I knows is about code.  Check with Jack for the licensing info.

>	What are we....Microsoft.... 
You comparing me to Microsquat?  Hrumph!  That's it... No more answers!

>	Biggest complaint I get about HUBwatch is customer misunderstanding
>	of the word "management". ie... Use HUBwatch to manage your DEChub.
So the new name "MultiChassis Manager" (and "Stack Manager") still don't
cut it, eh? Seriously, what features do your customers need?  It's just a
simple matter of software...

Anxiously awaiting your reply,
Tom Hood

	Sorry about that reference to the big "M". Keep those answer's rollin.

	Chassis Manager is a better name, but we must make it very clear to 
	customers, that event alarming is not the job of Chassis Manager or 
	"HUBwatch". Alot of customer I dealt with expected more from the 
	product, but that was purely a misunderstanding of the word "manage".
	(network manager vs. hub manager)

	Reviewing the product annoucement, I still do not see any reference to
	event monitoring. Will that be another clearVISN Core product? What 
	is clearVISN Core?

	My wish list:
	
		1. If it's got a MIB, it should have a GUI. The MIB has
		    data to be displayed. This would require a common API
		    so re-usable code could be used. The MIBs tree structure
		    should be easy to browse or display.

		2. If it can send SNMP Traps, we should have a routine to catch
		   them and display them thru the GUI. But, the Trap must
		   be in the MIB.

	Geez... I'm starting to ramble.

	-Larry

Larry,

Sometime this year there will be a clearVISN product called clearVISN Alarm
Configurator, which, when used with the clearVISN core, will do all the right
stuff.  V1 is pretty basic. V2 is pretty spiffy.

And, expect a MIB browser in the clearVISN core, also sometime this year.
I don't think it's in this first wave, but I could be wrong.

Tom

And before people ask here for schedules and ship dates, please don't.

	Thanks for the info.

	And great to see the alarms and MIB browser are being looked at.

	I just read the final press release, in this mornings VOGON, and I
	see that the CD will not be available till June. Is there any field
	test programs we can test? How close is [.anonymous.resil] to the
	product that will be shipping in June? Or is this just a subset?

	I just pulled the programs from slink.dechub and will be testing
	later.

	-Larry

The Resilience kit on slink is SSB V1.0.

    The Installation Guide mentioned support for Windows NT V3.51, but not
    the architecutre.  I'm assuming it works on Intel, but does it work on
    Alpha?
    
    Thanks!
    tl

    Alpha is planned, but the current NT stuff is intel.
    
    Tom Hood
    clearVISN

    
    Tom:
    
    Any plans to support GIGAswitches (specially, have a customer 
    asking for GS/FDDI)?
    
    Carlos Silva
    NIS Mexico

I think V2 of the Recovery Manager (aka Resilience) supports GIGAswitch.

Tom Hood
clearVISN