Jump to content

Banyan VINES: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
No edit summary
Line 36: Line 36:


==Continuing influence of Banyan and VINES in IT - user groups==
==Continuing influence of Banyan and VINES in IT - user groups==
Forme Banyan customers, employees and technicians still communicate with each other via Internet [[user groups]], [[blog]]s and [[chat room]]s. As the earliest implementors of directory services, former Banyan people had a ten year jump on both Novell and Microsoft in understanding both the business advantages as well as the architecture and implementation aspects of directory services. Former Banyan consultants now work in many areas of IT and still form a cadre with unique experience and unrivaled skills in the directory services industry. Consulting companies that once specialized in VINES now specialize in Active Directory and Unix, Linux and other OSX implementations support for directory services.
Former Banyan customers, employees and technicians still communicate with each other via Internet [[user groups]], [[blog]]s and [[chat room]]s. As the earliest implementors of directory services, former Banyan people had a ten year jump on both Novell and Microsoft in understanding both the business advantages as well as the architecture and implementation aspects of directory services. Former Banyan consultants now work in many areas of IT and still form a cadre with unique experience and unrivaled skills in the directory services industry. Consulting companies that once specialized in VINES now specialize in Active Directory and Unix, Linux and other OSX implementations support for directory services.


[[Category:Operating systems]]
[[Category:Operating systems]]

Revision as of 17:57, 5 February 2008

Banyan VINES (for Virtual Integrated NEtwork Service) was a computer network operating system and the set of computer network protocols it used to talk to client machines on the network. The Banyan company based the VINES operating system on Unix, and the network protocols on the archetypical Xerox XNS stack. VINES formed one of a group of XNS-based systems which also included Novell NetWare and ARCNET; like most of these earlier products it has since disappeared from the market, Banyan along with it.

James Allchin, who has since worked as Group Vice President for Platforms at Microsoft Corporation until his retirement at January 30th 2007, worked as the chief architect of Banyan VINES.

VINES technology

VINES ran on a low-level protocol known as VIP, the VINES Internetwork Protocol: essentially identical to the lower layers of XNS. Addresses consisted of a 32-bit address and a 16-bit subnet which mapped onto the 48-bit Ethernet address in order to route to machines. This meant that, like other XNS-based systems, VINES could only support a two-level internet.

A set of routing algorithms, however, set VINES apart from other XNS systems at this level. The key differentiator, ARP (Address Resolution Protocol), allowed VINES clients to automatically set up their own network addresses. When a client first booted up it broadcast a request on the subnet asking for servers, which would respond with suggested addresses. The client would use the first to respond, although the servers could hand off "better" routing instructions to the client if the network changed. The overall concept very much resembled AppleTalk's AARP system, with the exception that VINES required at least one server, whereas AARP functioned completely "headlessly". Like AARP, VINES required an inherently "chatty" network, sending updates about the status of clients to other servers on the internetwork.

Rounding out its lower-level system, VINES used RTP (the Routing Table Protocol), a low-overhead message system for passing around information about changes to the routing, and ARP to determine the address of other nodes on the system. These closely resembled the similar systems used in other XNS-based protocols. VINES also included ICP (the Internet Control Protocol), which it used to pass error-messages and metrics.

At the middle layer level, VINES used fairly standard software. The unreliable datagram service and data-stream service operated essentially identically to UDP and TCP on top of IP. However VINES also added a reliable message service as well, a sort of hybrid of the two that offered guaranteed delivery of a single packet.

At the topmost layer, VINES provided the standard file and print services, as well as the unique StreetTalk, likely the first truly practical globally-consistent name-service for an entire internetwork. Using a globally distributed, partially replicated database, StreetTalk could meld multiple widely-separated networks into a single network that allowed seamless resource-sharing. It accomplished this through its rigidly hierarchical naming-scheme; entries in the directory always had the form item@group@organization. This applied to user accounts as well as to resources like printers and file servers.

VINES client software

VINES client-software ran on most PC-based operating systems, including MS-DOS and earlier versions of Microsoft Windows. It was fairly light-weight on the client, and hence remained in use during the later half of the 1990s, when many machines not up to the task of running other networking stacks then in widespread use. This occurred on the server side as well, as VINES generally offered good performance even from mediocre hardware.

Initial market success - world-wide companies and government entities

With the low bandwidth requirements inherent in the efficient StreetTalk model, global companies and governments that grasped the inherent advantages of world-wide directory services seamlessly spanning multiple time zones caught on to the techological edge that VINES brought to the IT table. Gas and oil companies, power companies, public utilities, the US Government including the State Department, Treasury Department, and the US department of Defense implemented VINES in world-wide operations. The US State Department, for example, was an early adopter of the VINES technology. Able to take advantage of the then high-speed 56k modems for telephonic connectivity of the developed world to the limited telephone modem speeds of 300 baud over bad analog telephone systems in the Third World, VINES was able to link embassies around the world. VINES also came with built-in point-to-point and group chat capability that was useful for basic communication over secure lines.

Defense Department Adoption and the US Marine Corps

By the late 1980s the US Marine Corps was in search of simple off-the-shelf worldwide network connectivity with rich built-in email, file, and print features. By 1988 the Marine Corps had standardized on VINES as both its garrison (base) and forward-deployed ground-based battlefield email-centric network operating system. Using both ground-based secure radio channels and satellite and military tactical phone switches the Marine Corps was ready for its first big test of VINES, the 1990-1991 Gulf War. Units were able to seamlessly coordinate ground, naval, and air strikes across military boundaries by using the chat function to pass target lists and adjust naval gun fire on the fly. Ground fire support coordination agencies used VINES up and down command channels from Battalion-to-Regiment through Division-to-Corps and Squadron-to-Group to Aircraft Wing-to-Corps, as well as in peer-to-peer unit communication.

VINES competitors - Seizing the directory services "thunder'

For fully one decade Banyan's OS competitors, Novell and Microsoft, dismissed the utility of directory services. Thus VINES virtually dominated what would come to be called the "directory services" space from 1985 to 1995. While seeming to ignore VINES, Novell and eventually Microsoft, companies with a flat server- or domain-based network model, came to realize the strategic value of the directory services model. With little warning Novell went from playing down the value of directory services to announcing its own flavor, Netware Directory Services, or NDS (eventually Novell would change their term NDS to mean Novell Directory Services). Microsoft, originally a 100% desktop operating system company, which had gone through its own round of operating system development, first with IBM by initially partnering with them to develop an Intel-based disk operating system PCDOS and its Microsoft twin, MS-DOS, and eventually by sharing true network operating system development with IBM LAN Manager and its Microsoft twin, Microsoft LAN Manager. had parted company with IBM and continued its development of LAN Manager into what would become known as Windows NT, essentially its OS 4.0. NT was an originally a flat server or domain-based operating system with none of the advantages of either VINES or NDS. When Banyan was able to port the StreetTalk services to run on Microsoft NT this was not lost on their larger OS rival. By the typical and, many insiders would argue, often fatal "Black Widow spider" technology sharing, Banyan was sharing their technological advantages with a much larger competitor. Using that information, Microsoft soon began work on its own implementation of a directory services model to be called Active Directory and rolled out with its OS 5.0, Windows 2000. Even while hiring away James Allchin, known as the "Father of StreetTalk," Microsoft ran into technical difficulties, particularly in world-wide synchronization of Active Directory across time zones. Not afraid to use outside expertise, Microsoft actually partnered with Banyan in one of Banyan's last strategic and, many would argue, ultimately fatal partnerships, as Banyan sent a team of its most experienced StreetTalk engineers to Redmond to "fix Active Directory." With that "fix" purported to be highly successful, to many, both internally as well as in the Industry, Banyan had written its own death warrant. Active Directory was as robust as and, in several key ways, superior to VINES. While VINES was limited to a three-part name, user.company.org, like Novell's NDS structure, Active Directory was not bound at all to such a limiting naming convention. And, unlike either NDS or VINES, Active Directory had developed and additional capability, both lacked, its "forest and trees" organizational model. The combination of a better architecture and a marketing company the size of Microsoft signaled doom for StreetTalk, VINES as an OS, and finally Banyan itself.

The end of the company that pioneered portable directory services

By the late 1990s, VINES' once-touted StreetTalk Services' non-flat, non-domain model with its built in messaging, efficiency and onetime performance edge had become irrelevant

Banyan, always a technology-driven company and not a sales-driven company was unable to market its product far beyond its initial base of multi-national and government entities. Unable to quickly develop an OS to take advantage of newer hardware, and not realizing that it was the Streetalk directory services itself, rather than the shrink-wrapped OS, that was the prime value added, VINES sales rapidly dried up, both due to these problems as well as the rapid rise of Windows NT. Banyan increasingly turned to StreetTalk as a differentiator, eventually porting it to NT as a stand-alone product and offering it as an interface to LDAP systems.

Dropping their Banyan brand, a name known worldwide for the invisible and useless name, ePresence, in 1999, as a general Internet services company. Banyan soon became an internet NON-presence and after a series of equally incompetent and ultimately failed ventures it sold its services division to Unisys in late 2003 and liquidated its remaining holdings in its Switchboard.com subsidiary which had been based in the StreetTalk technology. It was a sad end for a company that had been unique in its technology product offering only 15 years earlier and which had enjoyed more than a decade of unrivaled success in the directory services space.

Continuing influence of Banyan and VINES in IT - user groups

Former Banyan customers, employees and technicians still communicate with each other via Internet user groups, blogs and chat rooms. As the earliest implementors of directory services, former Banyan people had a ten year jump on both Novell and Microsoft in understanding both the business advantages as well as the architecture and implementation aspects of directory services. Former Banyan consultants now work in many areas of IT and still form a cadre with unique experience and unrivaled skills in the directory services industry. Consulting companies that once specialized in VINES now specialize in Active Directory and Unix, Linux and other OSX implementations support for directory services.