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

Conference noted::decnis

Title:	DEC Network Integration Server (DECNIS)
Notice:	Please read note 1 to use this conference effectively
Moderator:	MARVIN::WELCH

Created:	Wed Sep 18 1991
Last Modified:	Thu Jun 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3660
Total number of notes:	15082

3604.0. "AppleTalk to only be supported on MPC-II/III..." by MARVIN::WELCH () Fri Apr 11 1997 12:07

This is a 'test the water' note. 

We are having problems getting all the DECNIS functionality into the MPC-I 
flash chips (2M). Since V3.1 we have been confining newer functionality to 
just MPC-II/III. Recently we have developed functionality to compress profile 
files in the combined image. However, we are slowly running out of options 
and the code-base continues to get bigger. 

My next step would be to remove AppleTalk support from MPC-I. This code, for
perverse reasons takes up almost 0.5M of code space, before compression. I 
don't know of many customers who use AppleTalk and I would like your
help to determine the impact of this decision. 

I can't promise an upgrade program, but I'm happy to work with customers
and support people to provide what help I can.

Thanks for your feedback...

Steve.

T.R Title User Personal
Name Date Lines

3604.1 Input HTKING::M_SHELDON Mon Apr 14 1997 00:12 44

T.R	Title	User	Personal Name	Date	Lines
3604.1	Input	HTKING::M_SHELDON		`Mon Apr 14 1997 00:12`	44
	Hi Steve: I have almost daily contact with U.S and Canadian support customers using DECNIS's and have yet to run across one using the Appletalk Routing capabilities. I know must be some out there, but they are in the small minority. My estimate of the DECNIS's most used functions would be in order: 1) DECnet PhaseIV and DECnet/OSI Routing 2) Transparent Bridging 3) IP (mostly using RIP, Integrated IS-IS and Static Routing in that order, with a few using or considering OSPF) 4) X.25 Connector and Relay capabilities 5) Novell Netware (and that's not a lot) Since you are asking for input, let me say that the DTF trace utility is absolutely great. I have worked several DECNIS and RouteAbout problems where this tool was invaluable. As you are probably aware we cannot directly view the DECNIS's IP routing control protocol tables from NCL, only the forwarding database. DTF allows me to see the routing updates as they are sent and received and that's only a very small part of what it can trace. My compliments to John Rigby, Tony Hart, and whoever else was involved. Two things I would like to see are: 1) A way to see events even though the DECNIS was loaded and managed from a PC. Loading from a PC used to cripple troubleshooting in two ways, no tracing and no events. You have solved the trace issue but events are still very powerfull facility and I have lost them using PC management. Would it be possible to at least include event logging from the console (MPC II/III or from a TELNET session) ? 2) An IP traceroute command would be helpfull. Thanks for the good work... Mike Sheldon CSC/CS Network Support

Hi Steve:

I have almost daily contact with U.S and Canadian support customers using
DECNIS's and have yet to run across one using the Appletalk Routing
capabilities. I know must be some out there, but they are in the 
small minority. My estimate of the DECNIS's most used functions
would be in order:

1) DECnet PhaseIV and DECnet/OSI Routing

2) Transparent Bridging

3) IP (mostly using RIP, Integrated IS-IS and Static Routing in that order,
   with a few using or considering OSPF)

4) X.25 Connector and Relay capabilities

5) Novell Netware  (and that's not a lot)

Since you are asking for input, let me say that the DTF trace utility
is absolutely great. I have worked several DECNIS and RouteAbout problems 
where this tool was invaluable. As you are probably aware we cannot directly 
view the DECNIS's IP routing control protocol tables from NCL, only the 
forwarding database. DTF allows me to see the routing updates as they are 
sent and received and that's only a very small part of what it can trace. 

My compliments to John Rigby, Tony Hart, and whoever else was involved.

Two things I would like to see are:

1) A way to see events even though the DECNIS was loaded and managed
   from a PC. Loading from a PC used to cripple troubleshooting in two
   ways, no tracing and no events. You have solved the trace issue but
   events are still very powerfull facility and I have lost them using PC 
   management. Would it be possible to at least include event logging 
   from the console (MPC II/III or from a TELNET session) ?

2) An IP traceroute command would be helpfull.

Thanks for the good work...


						Mike Sheldon
						CSC/CS Network Support