Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Ascend Communications (ASND) -- Ignore unavailable to you. Want to Upgrade?

To: Glenn D. Rudolph who wrote (19046)	10/26/1997 12:09:00 PM
From: Pullin-GS	Read Replies (1) \| Respond to of 61433

*Edited* Lets just say that having to muscle their equipment into a working network model is a total pain in the ass at times! It can be done, for they support everything under the sun(this is good), but it is like trying to squeez blood from a turnip! Implementation/Deployment issues abound! Early routers (Wellfleet days): Whenever you made a change to the router configuration, you had to reboot the router, thus creating a network outage for about 10 minutes in some cases! Do you have any idea how often changes are made to a large networ? Every day. This is unacceptable. CISCO routers have ALWAYS been dynamic, in that if you make a change, it takes place immediatly without a network interruption. At one point in time BAY management decided that their routers would no longer support TELNET! You had to use the buggy SNMP SiteManager (Site Mangler<G>) software (pre7.4 releases would not work 50% of the time) just to configure it! If your SNMP agent failed on your router, your SOL. You had to power reset the router. Needless to say, that did'nt last long and was corrected in about a year. But after they corrected the TELNET issue, once you tellneted to the router, the codes to configure it where not nice menue driven utilities, but memory alteration commands and SNMP literals (1.2.51.441.31313.4.343.343.33.33.1212 is an example of one) and they where unpublished for the administrators to have, unless you where an engineer at BAY. And if you had access to the read-only SNMP community string (which is usually set to PUBLIC by most systems by default), you could view the Write SNMP string! Kind of sucks for configuration management of the routers...any dweeb-hack could get in and shut down your network! 802.3 Spanning tree (required for bridged WANS, such as Digital's LAT protocol) plum did'nt work (it's been fixed). Frame relay Direct Mode configuration (Equivalent to Cisco's Point-to-Point subinterfaces) where not available until 2 years AFTER Cisco did it....and BAY never did suport Frame Relay Gang-of-Four signalling (CISCO ALWAYS supported that, and currently defaults to it). If you did not know this, you could not make a BAY talk to a CISCO because of the default configurations. I could go on until I'm blue in the face!