[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

6449.0. "how to get nodename changed successfully" by CSC32::J_RYER (MCI Mission Critical Support Team) Tue May 14 1996 01:32

    MCI has changed names on some of their DECnis's from just .router
    to .usa.loc.router.  They have been using "occurs" alarm rules in
    which the nodename on the global entity instance is wildcarded (*).
    
    Now, if the router is registered with its correct full name 
    (.usa.loc.router) then they never get notification from DECmcc 
    that the alarm has fired.  If they de-register and then re-register
    the router with its old short name (.router), then they do get
    notification, but the icon for that node doesn't change color on
    the iconic map.
    
    If they explicitly specify the fullname of the router in an
    "occurs" alarm rule, then everything works as it should - they
    do get notification, and the icon does change color appropriately.
    
    Where could MCC be storing the old form of the nodename?  We
    thought that de-registering it and then re-registered it to match
    the name that is set in the router and in the LOCAL namespace 
    should have worked.
    
    Thanks in advance for any help.  If you need more details, let me know;
    I'm new to DECmcc, so I may not be always using the right terms for
    things!
    
    Jane Ryer
    MCI Mission Critical Support Team

T.R Title User Personal
Name Date Lines

6449.1 try delete and create of * rule again? GADWAL::W_MCGAW Wed May 15 1996 20:47 10

T.R	Title	User	Personal Name	Date	Lines
6449.1	try delete and create of * rule again?	GADWAL::W_MCGAW		`Wed May 15 1996 20:47`	10
	Hi, It might be worth while to delete and recreate the occurs alarm rule for the wildcarded entity again. This is a long shot, but may straighten out the alarm rules since the wildcard rule was created when the DECnis's were registered as .router.name. Walt McGaw Digital Network Services Unit CSC/CS

    Hi,
    
    It might be worth while to delete and recreate the occurs alarm rule
    for the wildcarded entity again.  This is a long shot, but may
    straighten out the alarm rules since the wildcard rule was created when
    the DECnis's were registered as .router.name.
    
    Walt McGaw
    Digital Network Services Unit
    CSC/CS