Like I said earlier, CISCO will soon have to capitulate and agree to integrate NDS along side of Active Directory (when it ever shows its face).
This article was on the front page of todays PCWeek...
Cisco takes heat for shunning NDS
By Scott Berinato, PC Week Online October 9, 1998 5:09 PM ET
Networking leader Cisco Systems Inc. is being called on the carpet by many customers for ignoring their calls to integrate Novell Inc.'s Novell Directory Services with its networking hardware.
Though Cisco and Microsoft Corp. inked just such an agreement this spring for work with Microsoft's as-yet-unreleased Active Directory, Novell and Cisco will not commit to a such a partnership, or even a definitive statement of direction, for NDS.
"They're alienating a huge installed base," said a network administrator at a major Washington financial institution running both NDS and hundreds of Cisco switches and routers. "Basically, if I see competing offers in 1999, I'll start to look elsewhere for infrastructure."
By tying the directory to the networking hardware, administrators are able to do such things as configure routers on the fly and manage policies by user instead of IP address.
The difficulty for Cisco started earlier this year when it licensed Microsoft's Active Directory technology -- due with Windows NT 5.0 next year -- to support its forthcoming CNS (Cisco Networking Services) software. The resulting CNS/Active Directory, which will run on both Windows NT and Solaris, will provide directory-based management of Cisco hardware.
Though no agreement was made at that time, users of Cisco hardware and NDS expected a similar licensing deal that would yield a CNS for NDS.
However, this never happened. In fact, in a recent memo to its sales force, Cisco reiterated its support for Active Directory and offered no plan to support NDS.
Those who have made the investment in NDS feel that Cisco is in essence choosing the directory for them. "I want to call a meeting between Cisco and Novell and say, 'That's enough 'marketecture.' What are you going to do about this?'" said Jim Price, manager of enterprise network services for the Arizona Telecommunications System, in Phoenix, which has Cisco equipment and 1,000 clients managed by NDS.
In users' minds, Cisco's relationship with Microsoft, of Redmond, Wash., is deepening the freeze between Cisco and Novell.
"I feel like [Cisco is] making contradictory statements; it sounds like they've tied their wagon to Active Directory," said the network administrator at the major Washington financial institution. "I might get some interoperability from standards, but I'll have to go with Active Directory for the value-add."
While Cisco officials defend their Microsoft alliance, Kurt Dahm, senior product manager at Cisco, said: "We have every intention of working with all of our directory friends through the standards process. In no way are we trying to limit or segment the directory market."
Novell officials in Provo, Utah, said that's not enough. "We are committed to the standards process, but we believe that specific vendors working together can realize greater use of the directory sooner," said Ron Palmeri, vice president of strategic relations at Novell.
The decision to go with Microsoft, according to Cisco officials in San Jose, Calif., was predicated on the belief that Active Directory will provide technological advantages, specifically in replication schemes.
That optimization is a primary source of contention for enterprise managers such as Juan Mata of Excell Agent Services Inc., a call center in Phoenix. "It doesn't leave me with a good feeling," Mata said. "Our key application runs on NetWare, but we also have some running on NT. It was a nightmare to maintain both."
Mata said that until the companies join CNS and NDS, he will manage Cisco hardware separately. If, in the long run, Cisco and Novell choose not to work together to link CNS and NDS, management of Cisco hardware and policy allocation on that hardware via NDS will be, at best, complicated.
The long-term ray of hope for users is a nascent body of standards. Both DEN (Directory Enabled Networking) and LDAP (Lightweight Directory Access Protocol) Version 3 will provide baseline interoperability between directories.
But even though DEN and LDAPv3 will eventually bring base interoperability, vendor-specific extensions for differentiation will negate the management simplicity promised by directories. |