| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
I have been playing with DECmcc on VMS and think it is a wonderful piece of software. I do have a couple of questions regarding multi-site management. I cannot see that I can manage ethernet stations on remote sites if I have multiple sites linked by routers. The problem is really terminal servers. If I have 20 remote sites, all centrally managed and routed (not bridged), then can I manage at level 2 on the remote site without having DECmcc running there ?? Can I even register the devices ?? I have a customer who centrally manages 140 sites, each with 2 VAXes and 3-5 terminal servers. Will he be able to manage the terminal servers ??
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 255.1 | set host | MKNME::DANIELE | Tue Aug 14 1990 17:59 | 17 | |
Any device whose management protocol is LAN-based ( like Ethernet or LAT ) requires "the manager" to be local to that LAN. "The manager" means part of the management software. In DECmcc's case, this means you need a director on a system on the LAN. When DECmcc is distributed ( not in V1.0 or V1.1 ), you'll be able to issue management requests from a central director, but there will still have to be "part of a director" running local to the LAN. The director part will contain an AM that now can handle the particular protocol. Registration entails asking an AM to show the entity's identifiers, so all of the statements above apply. Hope this helps, Mike | |||||