| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 320.1 | Are PRIVs ok? | NSSG::R_SPENCE | Nets don't fail me now... | Tue Sep 11 1990 16:28 | 5 |
| Do you have the LOG_IO priv enabled for your process? The BRIDGE AM
seems to need it.
s/rob
|
| 320.2 | We will need more information. | TOOK::A_MOORE | | Tue Sep 11 1990 17:40 | 21 |
| Thank you for taking the time to report an MCC problem.
We are unable to duplicate the problem you reported. The next step is to
try and get more information until we can reproduce or identify the problem.
We can take this offline as it may go multiple iterations.
Al
What version of MCC and its components are you using?
Was the domain created before the populate command was issued?
(It is required.)
Were there existing members in the domain that was populated?
Did you use FCL or the Iconic Map interface?
Can you do a DIRECTORY STATION * command?
Can you do a CREATE DOMAIN foo MEMBER (STATION stationthatfails)?
|
| 320.3 | logfile available | CLARID::HOFSTEE | Take a RISC, buy a VAX | Wed Sep 12 1990 11:45 | 3 |
| I've send tha complete log to Al moore.
Timo
|
| 320.4 | repeat:how to register bridge | CLARID::HOFSTEE | Take a RISC, buy a VAX | Fri Sep 14 1990 07:45 | 36 |
|
Since I haven't been able yet to get one bridge into my config I'll ask
again: is there anybody out there that can explain how to register a
bridge , other then clicking on the bridge icon and placing it on the
map or doing from FCL
MCC> REGISTER BRIDGE BRIDGE_NAME ADDRESS 08-00-2B-0A-15-3F
since both terminate with the error
The requested operation cannot be completed
MCC Service Error = The requested operation cannot be
completed.
MCC>TEST MCC 0 BRIDGE_AM
Test succesfull
MCC>SHOW MCC 0 BRIDGE_AM ALL CHAR
MCC 0 BRIDGE_AM
Characteristics
AT 14-SEP-1990 o9:35:22
Examination of attributes shows:
Component Identification = "DECmcc Bridge AM"
Component Version = T1.0.1
I am running with all privs, local DNS with access on everything etc.
Any info on what migt be wrong?
Thanks
Timo
|
| 320.5 | TRY using SHOW to determone the existence | TOOK::JESURAJ | | Fri Sep 14 1990 15:20 | 16 |
| Ref .4:
Looks like your bridge is not responding to the SHOW commands
issued by the bridge AM.
Try using the SHOW commands whether the bridge physically exists there.
A command like
MCC> SHOW BRIDGE ADDR = <Address>
will be useful in determining the existence.
... Jesuraj
|
| 320.6 | clarification | GOSTE::CALLANDER | | Fri Sep 14 1990 15:26 | 11 |
|
RE: MCC> SHOW BRIDGE ADDR = <Address>
What Jesuraj means is try entering the command:
MCC> SHOW BRIDGE <bridges address> ALL IDENTIFIERS
See if this works, to help isolate where the problem is (potentially
in the registration services OR the bridge AM).
|
| 320.7 | Explainations of Populate and Bridge registration problems | TOOK::A_MOORE | | Mon Sep 17 1990 21:41 | 36 |
| The explaination for Timo's problems for 320.0 follows:
Populate
--------------
The populate command over ran the domain capacity. Populate will load all
the members its is asked to until completion or an error. The domain limit
described in release notes was reached and populate stooped.
A soon to be available release should be able to hold all of Timo's current
stations. Bridges and stations or any other global entity can be stored
in a domain.
For now, manager's will have to split thier configuration into smaller
(more manageable) domains. I think the best way to do it would be to use a
FCL command file. For now plan on small domains.
Bridge Registration
-------------------
To register any entity DECmcc does a SHOW class instance-name ALL IDENT
This means the entity must be available in order to register it.
In Timo's case the SHOW BRIDGE 08-00-2B-xx-xx-xx ALL IDENT command returned an
error. The PROTOCOLINUSE error is caused by conflict with RBMS(A bridge
management software). A RBMS detached process BML (Bridge Management Listener)
has the protocol locked. It can be stopped by the VMS command $ STOP/ID=xxxxx
This is described in the release notes in more detail. DECelms can do more than
all RBMS can do and, being a good citzen, it does conflict with DECmcc.
In general most Registration problems can be tracked by doing the show command
and rechecking that DNS is set up correctly.
Al
|
| 320.8 | Slight correction... | WLYWLD::BRIENEN | DECmcc Bridge|Station Management. | Tue Sep 18 1990 12:54 | 13 |
|
> DECelms can do more than
> all RBMS can do and, being a good citzen, it does conflict with DECmcc.
What he meant to say was...
DECelms is a superset of RBMS, offering support for LAN Bridges and
the DECbridge 500 and DECconcentrator 500 (plus nifty stuff like
utilization statistics and an fddi ring map).
DECelms, being a good citizen (two kids, drives a Volvo, etc), does
not grab the bridge protocol for exclusive use (as RBMS does) and thus
does not conflict with DECmcc.
|
| 320.9 | should everything be reachable to make map? | CLARID::HOFSTEE | Take a RISC, buy a VAX | Tue Sep 18 1990 13:12 | 17 |
|
After having (re)read the release notes and having stopped RBMS, I am
indeed able now to register my bridges.
But related to this problem I have another question:
It appears now that one can only register bridges, stations and node4's
when they are reachable. Now what about the network manager that wants
to construct a complete map of his network, without worrying at the
moment if a device is reachable or not? In other words, is my
assumption right that you can only construct a complete map of your
LAN, with all bridges stations etc. when everything is powered up and
reachable, or am I missing something?
Thanks
Timo
|
| 320.10 | Use the shutdown procedure provided for RBMS | ALLZS::MORRISON | The Network IS the System | Tue Sep 18 1990 14:33 | 13 |
| RE: .7
> A RBMS detached process BML (Bridge Management Listener)
> has the protocol locked. It can be stopped by the VMS command $ STOP/ID=xxxxx
The proper way to shut RBMS down is to invoke the RBMS shutdown procedure:
$ @sys$manager:nms_rbms$shutdown
This will ensure that everything is closed down gracefully. Using STOP/ID
is an extreme way to stop a process, and should be used only when necessary.
Wayne
|
| 320.11 | Yes, Entity must be reachable. | WLYWLD::BRIENEN | DECmcc Bridge|Station Management. | Tue Sep 18 1990 14:54 | 13 |
| RE: 320.9 by CLARID::HOFSTEE
> It appears now that one can only register bridges, stations and node4's
> when they are reachable...
> ...
> In other words, is my
> assumption right that you can only construct a complete map of your
> LAN, with all bridges stations etc. when everything is powered up and
> reachable, or am I missing something?
No, you are not missing anything.
It works just as you have described it...
|
| 320.12 | planning | GOSTE::CALLANDER | | Tue Sep 18 1990 17:07 | 6 |
|
and to add to Chris' comment
...and we don't expect you to love it. There is work going on to
provide the ability to "Plan" entities that are not currently in your
network (or reachable).
|
| 320.13 | How many entities in a domain? | CLARID::HOFSTEE | Take a RISC, buy a VAX | Wed Sep 19 1990 08:54 | 592 |
| re. 7:
>The populate command over ran the domain capacity. Populate will load all
>the members its is asked to until completion or an error. The domain limit
>described in release notes was reached and populate stooped.
In the X.1.1.0 release notes it is only mentioned that the space
reserved per domain depends on the length of names and the number of
attributes. I don't seem to be able to store more than ~30 entities
in a domain. So, what is the limit approximately?
I guess , a workable limit should allow at least for a couple of
hundred items, given the fact that a small LAN nowadays easily has
hundreds of devices hanging on it. And no, I don't think that a network
manager wants to split his LAN in 25 domain's, one for each segment.
Since you HAVE to use a domain when creating a map, this upperlimit is
really to restrictive . Hope it will be changed soon.
Keep up the good work
Timo
Follows a log of a domain and its members, in which I seem to be unable
to add anymore global entities
Welcome to VAX/VMS V5.3-1
Username: SYSTEM
Password:
Welcome to VAX/VMS version V5.3-1 on node GIBBY
Last interactive login on Wednesday, 19-SEP-1990 10:21
Last non-interactive login on Wednesday, 19-SEP-1990 10:32
Z
[c
[62"p F
>
GIBBY::>mccl
DECmcc (T1.0.1)
)0[4l
=
>
)0[4l
=
>
MCC> show domain ethernim all att
Domain GIBBY_NS:.ethernim
ALL ATTRIBUTES
AT 19-SEP-1990 10:35:46
DomainName =
GIBBY_NS:.ethernim
Member Event Counter =
29
Directory =
SYS$SYSROOT:[SYSMGR]
Owner ID =
"SYSTEM"
Implementation Desc =
""
Location =
""
MAIL Account =
""
Phone Number =
""
Remarks =
""
Responsible Person =
""
Text File =
""
MCC> show domain ethernim member *
Using default ALL IDENTIFIERS
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.FENRES
Identifiers
AT 19-SEP-1990 10:36:15
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.FENRES
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.LPSAFS
Identifiers
AT 19-SEP-1990 10:36:16
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.LPSAFS
Domain GIBBY_NS:.ethernim Member Domain GIBBY_NS:.LNI_791
Identifiers
AT 19-SEP-1990 10:36:17
Examination of attributes shows
MemberName =
Domain GIBBY_NS:.LNI_791
Domain GIBBY_NS:.ethernim Member Domain GIBBY_NS:.MPR_792
Identifiers
AT 19-SEP-1990 10:36:17
Examination of attributes shows
MemberName =
Domain GIBBY_NS:.MPR_792
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.NETSYS
Identifiers
AT 19-SEP-1990 10:36:18
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.NETSYS
Domain GIBBY_NS:.ethernim Member BRIDGE GIBBY_NS:.BET_640
Identifiers
AT 19-SEP-1990 10:36:18
Examination of attributes shows
MemberName =
BRIDGE GIBBY_NS:.BET_640
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.MUGSY
Identifiers
AT 19-SEP-1990 10:36:19
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.MUGSY
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_200
Identifiers
AT 19-SEP-1990 10:36:20
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_200
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.BASTA
Identifiers
AT 19-SEP-1990 10:36:20
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.BASTA
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_249
Identifiers
AT 19-SEP-1990 10:36:21
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_249
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_260
Identifiers
AT 19-SEP-1990 10:36:22
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_260
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_678
Identifiers
AT 19-SEP-1990 10:36:22
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_678
Domain GIBBY_NS:.ethernim Member BRIDGE GIBBY_NS:.BET_743
Identifiers
AT 19-SEP-1990 10:36:23
Examination of attributes shows
MemberName =
BRIDGE GIBBY_NS:.BET_743
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_141
Identifiers
AT 19-SEP-1990 10:36:24
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_141
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_170
Identifiers
AT 19-SEP-1990 10:36:24
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_170
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_172
Identifiers
AT 19-SEP-1990 10:36:25
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_172
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_301
Identifiers
AT 19-SEP-1990 10:36:26
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_301
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_319
Identifiers
AT 19-SEP-1990 10:36:26
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_319
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.TERVA
Identifiers
AT 19-SEP-1990 10:36:27
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.TERVA
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_126
Identifiers
AT 19-SEP-1990 10:36:28
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_126
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_585
Identifiers
AT 19-SEP-1990 10:36:28
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_585
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_573
Identifiers
AT 19-SEP-1990 10:36:29
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_573
Domain GIBBY_NS:.ethernim Member BRIDGE GIBBY_NS:.BET_614
Identifiers
AT 19-SEP-1990 10:36:29
Examination of attributes shows
MemberName =
BRIDGE GIBBY_NS:.BET_614
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_543
Identifiers
AT 19-SEP-1990 10:36:30
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_543
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_584
Identifiers
AT 19-SEP-1990 10:36:31
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_584
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.WANDA
Identifiers
AT 19-SEP-1990 10:36:31
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.WANDA
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_746
Identifiers
AT 19-SEP-1990 10:36:32
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_746
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.station_220
Identifiers
AT 19-SEP-1990 10:36:33
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.station_220
Domain GIBBY_NS:.ethernim Member STATION GIBBY_NS:.PAMPAM
Identifiers
AT 19-SEP-1990 10:36:33
Examination of attributes shows
MemberName =
STATION GIBBY_NS:.PAMPAM
MCC> show station station_220 all att
STATION GIBBY_NS:.station_220
ALL ATTRIBUTES
AT 19-SEP-1990 10:36:50
Address =
08-00-2B-04-7D-EF
Name =
GIBBY_NS:.station_220
Boot Supported =
False
Console Carrier Reserved =
False
Console Carrier Supported =
False
Data Link Counters Supported =
True
Dump Supported =
False
Loop Supported =
True
Multiblock Loader Supported =
False
Primary Loader Supported =
False
Receive Block Check Error Failure =
False
Receive Frame Too Long Failure =
False
Receive Framing Error Failure =
False
Responding Address =
AA-00-04-00-82-CC
Send Carrier Check Failed Failure =
False
Send Excessive Collisions Failure =
False
Send Frame Too Long Failure =
False
Send Open Circuit Failure =
False
Send Remote Failure To Defer Failure =
False
Send Short Circuit Failure =
False
Bytes Received =
246079126
Bytes Sent =
56889404
Counter Creation Time =
18-SEP-1990 16:24:38.21
Data Overruns =
0
Frames Received =
2029279
Frames Sent =
510831
Frames Sent Initially Deferred =
18504
Frames Sent Multiple Collisions =
1952
Frames Sent Single Collisions =
1522
Multicast Bytes Received =
161838332
Multicast Frames Received =
1738897
Seconds Since Last Zeroed =
65535 Seconds
System Buffers Unavailable =
2
Unrecognized Frame Destination =
0
User Buffers Unavailable =
0
Alternate Address =
AA-00-04-00-82-CC
Functions Supported =
DEC_ENETV2
Implementation =
DESVA Microvax-2000 CSMA/CD controller
Maintenance Version =
V3.0.0
Implementation Desc =
""
Location =
""
MAIL Account =
""
Phone Number =
""
Remarks =
""
Responsible Person =
""
Text File =
""
MCC> exi
>
>
GIBBY::>lo
SYSTEM logged out at 19-SEP-1990 10:37:07.42
|
| 320.14 | limit is around 80 | TOOK::JESURAJ | | Wed Sep 19 1990 14:19 | 6 |
| The limit we have observed at present (with 25 char domain names) is
around 80. We are looking at the possibility of extending it.
/ Jesuraj
|
| 320.15 | old limit was 28 | GOSTE::CALLANDER | | Wed Sep 19 1990 15:12 | 7 |
| RE .13
The version Jesuraj is running, is the one released on monday. Prior
to that the limit was, I believe, 28. There is a message around
here somewhere from Al Moore stating the old and new limits.
|