home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!caen!batcomputer!ghost.dsi.unimi.it!univ-lyon1.fr!chx400!decus!g_fierlbeck
- From: g_fierlbeck@decus.ch
- Newsgroups: vmsnet.networks.management.decmcc
- Subject: MCC wildcard syntax granularity
- Message-ID: <2379.2b0bef11@decus.ch>
- Date: 19 Nov 92 19:46:25 CET
- Organization: DECUS (Switzerland)
- Lines: 26
-
-
- Why is the granularity of the wildcarding in mcc NCL syntax so large?
- :-( i.e. when will it get better?
-
- If I want to perform certain operations (e.g. setting up polling rules,
- counter zeroing, or whatever) on particular subsets of nodes in any
- particular domain, it seems that you can either specificy ALL the nodes
- or ALL instances of a subentity, or only exactly one. If I need to set
- up a rule that checks for an attribute on a particular kind of circuit,
- I don't want MCC to try checking these attributes on another kind of
- circuit, for example. Or maybe I want to check an attribute on the
- ethernet circuits on all VAXen in a domain - but our 9000s have MNA
- controllers, microVAXen SVAs, routers simply 'ETHERNET' and
- so on. --No, I don't want to have to use cmd procs, or write extreme
- numbers of rules, or tolerate 'shotgun blasts' of misdirected queries,
- or even use complicated/unrealistic domain groupings.
-
- Certainly this is not a restriction of the language definition itself!
-
- =========================================================================
-
- G. Fierlbeck, Netmgt. SOFFEX Swiss Options and Financial Futures Exchange
- Neumattstr. 7, CH-8953 Dietikon/ZH, Switzerland.
-
- X.400: c=CH a=arCom o=SOFFEX p=SOFFEX s=Fierlbeck g=George
-
-