Conference azur::mcc

2873.0. "Why not do Autoregistration followup on Applications?" by FOUR62::LICAUSE (Al Licause (338-5661)) Tue Apr 28 1992 12:29

In working with the new Bridge Autoregistration....a nice utility!...I tried it
on our local Easynet segment and found many bridges.

Quite a few came up unreachable for what ever reason, but as per V1.2 these
entities were partially registered.

I've writen a brief command procedure to simply check for such entities and
loop until all have been fully registered.

This is specific to bridge modules, but I would image could be modified for
any type of entity.

Partial registration is only part of the answer....to really be effective
for customers...(i.e. value added..)...we need to do a little more and
automatically register everything or as much as is possible.

Any comments appreciated and also comments on the code.

================================================================================
$! This command procedure will repeated get a list of known bridge entities
$! from DECmcc and search for those that have been partially registered.
$! It will then attempt to register those entities.
$! If all bridges have been successfully registered, no action is taken.
$!
$top:
$ mcc show bridge * all ident, to file bridges_all.txt
$ set noon
$ search/window=(4,0) bridges_all.txt insuff/output=partial_br.txt
$!
$! Check for empty file
$!
$ open/read input partial_br.txt
$ set noon
$ read input check
$ close input
$ if "''check'".eqs."" then goto no_partial_regs
$!
$ search partial_br.txt local_ns/output=partial_bridges.tmp
$ open/read input partial_bridges.tmp
$ open/write output partial_bridges2.tmp
$ write output "$ manage/enterprise"     !enter the first line of procedure
$next:
$   read/end=no_more input line
$   new_line = "Register " + "''line'"
$ write output new_line
$ goto next
$!
$no_more:
$ close input
$ close output
$ delete/noconfirm partial_br.txt.*
$ delete/noconfirm partial_bridges.tmp.*
$ @partial_bridges2.tmp
$ delete/noconf partial_bridges2.tmp.*
$!
$ goto top   !Repeat the entire process
$!
$no_partial_regs:
$ delete/noconfirm partial_br.txt.*
$ delete/noconfirm bridges_all.txt.*
$ write sys$output " "
$ write sys$output "All Bridges have been successfully registered"
$ write sys$output " "

Hi Al,

Thanks for you suggestion.  

The latest version of the STM FM (t1.2.7) will 
only register bridges that can be reached.  This is to prevent the
spanning tree map from becoming a mess.   However,  you can accomplish
what you desire by running the autoregister directive peroidically.
This is because the latest version will only attempt to register new
bridges that aren't already fully registered.   Therefore, each autoregister
iteration will only pick thoese bridges that could not be reached by an 
earlier attempt and autoregistration.

Bob

Bob,

thanks for the explaination....this is good to know.

Al

> The latest version of the STM FM (t1.2.7) will 
> only register bridges that can be reached.  

I only  have  a  hazy  understanding  of  what is being talked about here so
forgive  me  if this is not really an issue.  In particular I don't know how
the  information  about  adjacent bridges and the reachability of bridges is
determined.   I  assume  it  uses  RBMS  to  ask each bridge about neighbour
bridges and also uses RBMS to determine if the bridge is reachable.

Does that mean that if you have a non-DEC (or non-RBMS) bridge then it won't
appear  on  the  map even if it is adjacent to an RBMS bridge which reported
it?

Do you try multiple protocols (RBMS, SNMP, CMIP)?

Will this cause a problem for the DECNIS, which implements SNMP and CMIP but
not RBMS?  And third-party bridges?

Graham