home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #16 / NN_1992_16.iso / spool / comp / dcom / lans / hypercha / 16 < prev    next >
Encoding:
Internet Message Format  |  1992-07-31  |  5.4 KB
  1. Path: sparky!uunet!pmafire!news.dell.com!swrinde!mips!sdd.hp.com!usc!sol.ctr.columbia.edu!The-Star.honeywell.com!umn.edu!noc.msc.net!ns!news
  2. From: goldfaa@nfms.network.com (Angus Goldfinch)
  3. Newsgroups: comp.dcom.lans.hyperchannel
  4. Subject: 6400/6800 CDA V3.0 enhancements
  5. Message-ID: <1992Jul31.145649.2666@ns.network.com>
  6. Date: 31 Jul 92 14:56:49 GMT
  7. Sender: news@ns.network.com
  8. Organization: Network Systems Corporation
  9. Lines: 38
  10. Originator: goldfaa@nfms.network.com
  11. Nntp-Posting-Host: nfms.network.com
  12.  
  13. Network Systems Corporation                                                            
  14. M E M O R A N D U M                                    July 16, 1992                                                                
  15. MEMO TO:      Arne Langmo RUNIT                                                                                                     
  16. FROM:         A S Goldfinch                                                                                                         
  17. SUBJECT:      New DX Version CDA 3.0                                                                                                
  18.                                                                                                                                     
  19. In your recent correspondence, you mentioned two issues with respect                                                                
  20. to the installation  of the latest release of microcode, CDA Version                                                                
  21. 3.0, for NSC 6400 & 6800 routers.                                                                                                   
  22.                                                                                                                                     
  23. 1.  The  replacement of the define route interface command by define                                                                
  24.     secondary interface.                                                                                                            
  25.                                                                                                                                     
  26.     When enhancements are made to software it is often necessary  to                                                                
  27.     make  changes  to  the user interface. In this case we were well                                                                
  28.     aware of the situation and documented it accordingly in our  re-                                                                
  29.     lease  notes.    Because  of your remote geographic location you                                                                
  30.     have elected to perform your own upgrades and first line mainte-                                                                
  31.     nance. Please be assured that had you been on one of our  stand-                                                                
  32.     ard support contracts this work would have been performed by our                                                                
  33.     Network Engineer as part of the upgrade.                                                                                        
  34.     This  enhancement  allows  multiple logical network support on a                                                                
  35.     physical network interface. You are quite correct saying that  a                                                                
  36.     new  ip address needs to be assigned to the router for each log-                                                                
  37.     ical network being used on the interface. This method is similar                                                                
  38.     to that used by other vendors in the industry today.                                                                            
  39.                                                                                                                                     
  40. 2.  The SNMP response to an SNMP request for  interface  type  being                                                                
  41.     invalid.                                                                                                                        
  42.                                                                                                                                     
  43.     This  issue  is  quite clearly something that was wrong with our                                                                
  44.     SNMP agent software, which was  corrected  and  shipped  to  you                                                                
  45.     shortly after you reported the problem.                                                                                         
  46.                                                                                                                                     
  47. I hope this explains the reasons behind our changes and the benefits                                                                
  48. in this new software far outweigh the inconvience you were caused.                                                                  
  49.                                                                                                                                     
  50. 92198VM10005                                                                                                                        
  51.