| Re .0
>using brs$config I ran into a couple of bugs. First, when I configure a DECNIS
>with OSI access the brs$config program generates wrong syntax for the MCC
>register command. It writes the line like this:
>
>REGISTER NODE xxxxx SYNONYM xxxx , -
>CREATE DOMAIN yyyyy MEMBER xxxxx
>
>Obviously the BRS$CONFIG_MCC_DOMAIN.COM fails on the CREATE directive.
>
>Second, on the BRS$CONFIG menu the SETUP SERVER options fails with the folowing
>in the log file:
>
>-f-exists, file GET_CIRC.TMP already exists, non superseded...
>
>I'm using BRS 1.4 with OVMS VAX 6.2 and DECOSI 6.3 eco level 6.
What's the date of your BRS V1.4 kit?
There was a V4.1-1 kit produced.
I can't find it in the release notes, but I reviewed the CMS entries for
BRS V1.4 ECO 1 and there are several references to fixing DECNIS problems.
The kit is at:
BULOVA::BRS$KITS:[BRS014]
BRS$CONSOLE_CFG.DAT;1 264/264 22-NOV-1995 11:45:46.00
BRS.DECW$BOOKSHELF;1 1/3 9-NOV-1995 17:58:49.00
BRSINSTAL.COM;1 322/324 4-JUN-1996 11:57:47.00
BRSOMS014.RELEASE_NOTES;2 73/75 21-JUN-1996 14:34:46.00
BRSOMS014.RELEASE_NOTES_PS;1 183/183 21-JUN-1996 14:34:25.00
BRSOMS014_RELEASE_NOTES.DECW$BOOKSHELF;1
1/3 21-JUN-1996 14:36:18.00
BRSOMS14_CONFIG_GUIDE.DECW$BOOK;1 1888/1890 8-NOV-1995 18:19:44.00
BRSOMS14_INSTALL_GUIDE.DECW$BOOK;1 859/861 9-NOV-1995 17:02:59.00
BRSOMS14_MANAGER_GUIDE.DECW$BOOK;1 3217/3219 8-NOV-1995 18:11:36.00
BRSOMS14_RELEASE_NOTES.DECW$BOOK;1 77/78 9-NOV-1995 16:49:55.00
BRSOMSR014.A;2 4158/4158 21-JUN-1996 18:34:31.00
BRSOMSR014.B;2 2592/2592 21-JUN-1996 18:35:01.00
BRSOMSR014.C;2 162/162 21-JUN-1996 18:35:22.00
Total of 13 files, 13797/13812 blocks.
>Second issue: PCM receives MCC alarms from the first site only once, as soon as
>I start up BRS or when I DISABLE/ENABLE Framework alarms from OMS management.
>Then PCM receives only MCC alarms from second site. The alarms are correctly
>displayed in the Framework Notification window for both sites.
>
>Any clue?
I'm not sure what you mean here.
Only the Primary OMS is running the Framework alarms.
Look for a batch job BRS$MCCRULES.
Then the BRS$ENS_MCC process places all messages to the ENS window. The Primary
OMS is also running PCM, and displays the ENS window to all OMS users.
Regards
James :-)
|
| OK, I've got the November 1995 CDROM distribution, BRSCDV14, so I suppose
the save sets are earlier dated than 21-JUN-1996. Hope the new kit fixes the
first problem.
To explain better the second, I configured one OMS station and two sites (so a
cluster with four members). The sites are connected thru FDDI
and two GIGASWITCH with latest firmware (3.11). When I start the OMS interface
and therefore the PCM ENS window I get messages from both sites. But I noticed
that I receive power cabinet, fan, interface messages from one GIGASWITHC only
when I start the PCM interface or when I disable/enable at once the FRAMEWORK
alarms. Instead in the Framework Notification window every five minutes I get
INDETERMINATE messages about cabinet, power, fans from one GIGASWITH. Shouldn't
these messages be displayed also in the ENS window? Again I receive
INDETERMINATE messages in the Framework window about DS200 terminal servers
that do not appear in ENS. By the way the TSAM module is not considered in the
BRS$INSTAL menu, neither a license, and also it doesn't work under DECnet /OSI.
I also installed the latest patch (fix04) of TSAM but when I issue a show
command to a terminal server I get a "Termserver_AM is disabled", and the
MCC_TS_AM_SRV process is up and runnig.
Any help would be appreciated. Thanks
Tano
|