[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

3902.0. "Probelms with CHIPCOM hub management" by ARRODS::HAWESJ (John Hawes ) Wed Oct 14 1992 14:29

I am trying to manage a Chipcom hub using DECmcc.

The SNMP traps generated by the HUB are being sent to the DECmcc
system, and I get the following TRAP received if an interface goes
down.

=====================================================================
Domain:         LOCAL_NS:.map_chipw
Entity:         SNMP CHIPW interface
Event Source:   SNMP LOCAL_NS:.chipw
Severity:       Critical
Timestamp:      14-oct-1992
Text :          linkDown
Details:

Successfully received event(s)

LinkDown
A LinkDown trap was received:

        Enterprise      1.3.6.1.4.49.1.3.1.0
        agent-addr      16.182.32.5
        generic-trap    linkDown
        specific-trap   0
        time-stamp      1270490821
        ifindex         147
=====================================================================

When the trap is received the CHIPW icon changes to RED but the
interface entity below does not change. I would have thought the trap
would change SNMP entity CHIPW interface 147 to RED. I found note
3868.1 said

  "In V1.3, enterprise specific traps will be delivered under the
   child entity for the enterprise, (while generic traps are delivered
   under the global entity SNMP). You should be able to use
   Notification services to change icon colours for child entity
   events."
 
So I assume this will not work until DECmcc V1.3.

I then decided to try using alarms, and wrote the following alarm.

create domain map_chipw rule interface_change_stat -
expression = (change_of (SNMP chipw interface 147 ifLastChange, *,*),-
at every 00:05:00),-
severity = critical, -
description = " ip interface has changed state"


It fired when the interface changed state from up to down, or down to
up, the "CHIPW" icon changed colour to red and the "interface" entity
below that also changed to red, however "interface 147" does not ???

Help anyone know why ??


Thanks

John


PS: The CHIPCOM MIB is full of useful ENTITIES such as
      "" online51nnMMGTModTable""

How do I find out what these entities are for, most of them say
"attribute not gettable" when I try to use them.

T.R	Title	User	Personal Name	Date	Lines
3902.1	About online51nnMMGTModTable subtree...	ZTOIS1::VISTA	Renato VISTA, SIS Strasbourg, France	`Thu Oct 15 1992 14:01`	31
	Hi John, About your PostsScriptum, these subtrees are used to get variables by module technology, ie online51nnMMGTModTable for 5100M-MGT module (Ethernet Management Module) Please note the semantic sequence : online for ONline CHIPCOM products 50 for CONTROL modules 51 for ETHERNET modules 52 for TOKEN RING modules 53 for FDDI modules nn number of external ports MMGT suffix of module name (5100M-MGT) ModTable List of 51nnMMGT modules really installed in the hub (the instance index is the slot number). If NO INSTANCE NUMBER IS GIVEN, it means that there is NO MODULE of that subtree/technology installed on the HUB (it explains your "attribute non gettable/available"). Renato
3902.2	its a hard slog	ARRODS::HAWESJ	John Hawes	`Wed Oct 21 1992 06:02`	21
	Thanks Renato for your reply. I have been out at the customer site for the last few days setting the system up. I resolved one problem, create domain map_chipw rule interface_change_stat - expression = (change_of (SNMP chipw interface 147 ifLastChange, ,),- at every 00:05:00),- severity = critical, - description = " ip interface has changed state" I used the name chipw as the SNMP entity, however it was registered as CHIPW. This caused the icon to change colour but not the interface. When I changed the rule to CHIPW both the icon and interface changed colour. I am still working on the other problems. Regards John
3902.3	Internet HOST alias to be defined ??	ZTOIS1::VISTA	Renato VISTA, SIS Strasbourg, France	`Fri Oct 23 1992 07:34`	16
	John, Have you defined an alias name for CHIPW, ie : 1) If VMS/UCX, UCX>set host CHIPW/alias="chipw" 2) if ULTRIX/Internet, edit /etc/hosts, and define as following xxx.xxx.xxx.xxx CHIPW chipw May be it would solve your problem... Renato
3902.4	Check rev level of Eflash prom	PARVAX::STORM		`Fri Oct 23 1992 10:45`	6
	One other thing you might want to check... Make sure the EFLASH PROM on the Chipcom hub is up to rev 3. The latest Chipcom MIB requires this. Karen
3902.5	Getting there	ARRODS::HAWESJ	John Hawes	`Tue Nov 10 1992 06:39`	24
	Karen, Renato, Thanks for the information. I also found that CHIPCOM_HUB3_BRG_10BT_MIBDEF.TXT;2 Is the MIBII for use with Chipcom HUB software version 3.0, and it will not work with the old V2.1 software. The CHIPCOM_HUB21_MIBDEF.TXT;2 is a MIBI which works with the V2.1 hub software. I wrote some alarm rules to check the power supplies and also hub temperature,the customer was very happy because it picked up three power supplies which had gone off line. I am picking up the SNMP traps from the hubs , I only wish it was possible to target the linkdown/linkup traps. Regards John