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

Conference npss::gigaswitch

Title:GIGAswitch
Notice:GIGAswitch/FDDI Jan 97 BL3.1 914.0 documentation 412.1ion 412.1
Moderator:NPSS::MDLYONS
Created:Wed Jul 29 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:995
Total number of notes:4519

927.0. "mib variables to automatically monitor hunt group?" by RDMCS3::STUART (Scott Stuart - NPB SE - 410.315.9954) Thu Feb 13 1997 09:03

    I am following up on notes 870 and 740.  My customer wants to set up
    automatic montoring of hunt groups.  I want to check my reasoning and
    see if anyone else has implemented this yet.  They have the tools to
    set up automatic montioring and will write the script to get the
    correct MIB variables.
    
    1. If anyone has set this up to do automatic performance, error
    monitoring of hunt group ports, please post an answer here or send me
    mail at [email protected].
    
    2. What needs to be gathered is
    	i. On each GS - what hunt groups exits
    	ii. What physical ports are active members of that hunt group
    	iii. The UNA of each hunt group member which GS that represents
    	iv. Aggregate and individual if statistics (input, output, errors,
    etc.)
    
    For i and ii
    Use  portGroupStatusTable    
    	            portGroupStatusBridgePort       INTEGER,
                    portGroupStatusPortNumber       INTEGER,
                    portGroupStatusPortType         INTEGER,
                    portGroupStatusOperStatus       INTEGER
            
    If the PortType is - hunt group and the OperStatus is bridging, then
    the BridgePort is the physical port I want to monitor and 
    the PortNumber is the Hunt Group number? 
    
    
    For iii:  What mib variable for this one?
    
    For iv: look at the if statisitics.
    
    What am I missing?
    
    Thanks
    -- scott
    [email protected]
T.RTitleUserPersonal
Name		DateLines
927.1NPSS::MDLYONSMichael D. Lyons DTN 226-6943Mon Feb 24 1997 15:15115
>>    1. If anyone has set this up to do automatic performance, error
>>    monitoring of hunt group ports, please post an answer here or send me
>>    mail at [email protected].
>>    

        To the best of my knowledge, those customers which have installed
    hunt groups and which are monitoring those hunt groups are using the
    standard interface group MIB objects to do it.  I have no special
    information about how they are doing any monitoring.  There have been
    no specialized MIB objects added for hunt group performance monitoring.

>>    2. What needs to be gathered is
>>    	i. On each GS - what hunt groups exits
>>    	ii. What physical ports are active members of that hunt group
>>    	iii. The UNA of each hunt group member which GS that represents
>>    	iv. Aggregate and individual if statistics (input, output, errors,
>>    etc.)
>>    

        for i/ii (from the MIB):

    portGroupMembershipTable	OBJECT-TYPE
        SYNTAX  SEQUENCE OF PortGroupMembershipEntry
        ACCESS  not-accessible
        STATUS  mandatory
        DESCRIPTION
		"The table for storing the port group membership."
        ::= { gigaSets 1 }

    portGroupMembershipEntry 	OBJECT-TYPE
        SYNTAX  PortGroupMembershipEntry
        ACCESS  not-accessible
        STATUS  mandatory
        DESCRIPTION
		"An entry stores information about a single port
		group."
        INDEX { portGroupBridgePort }
        ::= { portGroupMembershipTable 1 }

    PortGroupMembershipEntry ::=
        SEQUENCE {
		portGroupBridgePort		INTEGER,
		portGroupMembership		DisplayString,
		portGroupMembershipWorkBuf	DisplayString,
		portGroupPortType		INTEGER,
		portGroupPortTypeWorkBuf	INTEGER,
		portGroupPortOperStatus		INTEGER
        }

    portGroupBridgePort		OBJECT-TYPE
        SYNTAX  INTEGER
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
		"The port group port number.  It is unique within this table
		and must be between 37 and 64.  Without 
		management settings, the port group has no members in it.
		"
	::= { portGroupMembershipEntry 1 }

    portGroupMembership		OBJECT-TYPE
        SYNTAX  DisplayString
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
		"
		This object displays the current state of the port group
		membership.  Managers specify a new port group membership
		using portGroupMembershipWorkBuf.  The new membership
		becomes effective and remains unchanged after a system crash
		when portGroupAction is set to doUpdate and the updating 
		process succeeds.
		"
        ::= { portGroupMembershipEntry 2 }



>>    
>>    For iii:  What mib variable for this one?
>>    

        The Upstream Neighbor Address is one of the standard FDDI MIB (RFC
    1285 for the GIGAswitch/FDDI system BL3.1) objects:

          snmpFddiMACUpstreamNbr OBJECT-TYPE
              SYNTAX  FddiMACLongAddressType -- OCTET STRING (SIZE (6))
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The MAC's upstream neighbor's long individual MAC
                      address.  It may be determined by the Neighbor
                      Information Frame protocol (refer to ANSI SMT
                      7.2.1).  The value shall be reported as '00 00 00
                      00 00 00' if it is unknown."
              REFERENCE
                      "ANSI { fddiMAC 24 }"
              ::= { snmpFddiMACEntry 8 }



>>    For iv: look at the if statisitics.
>>    

        There are no aggregate counters, if that is what you are asking. 
    Aggregate counters are actually somewhat less interesting than the
    individual counters on each port, although the total is somewhat
    useful.

>>    What am I missing?
>>    

        See note 926.4 for a list of some MIB objects which may be
    considered worth monitoring.
    
    MDL