Release Notes for BPX SES Release 3.0
=====================================

Applicable for Following Products:
	
	BPX SES

Release Notes for the BPXSES 3.00
==================================

Following information is common to multiple releases of BPX SES.

- Refer "SUPPORTED MIBs" section for information on MIBs supported

- Refer "MIB LOAD ORDER" section for information on Loading MIBs.

- Refer "LOADING TRAP MIBs" section for information on MIBs 
  having trap definitions

- Refer "RFC MIBs" section for the MIBs that are from RFC.
  Some NMS software packages load some of these Standard MIBs 
  and corresponding applications load them automatically when started.
 
  Loading errors will be reported if the MIBs conflict with the
  allready loaded standard MIBs.

- Refer "AGENT-CAPABILITIES MIB" for AGENT CAPABILITIES information

1. SUPPORTED MIBs

1.1 Standard MIBs

    RFC1213-MIB.my        ( RFC 1213 )
    IANAifType-MIB.my     ( RFC 1573 )
    IF-MIB.my             ( RFC 2233 )
    RS-232-MIB.my         ( RFC 1659 )
    SNMPv2-MIB.my         ( RFC 1907 )
    SNMPv2-SMI.my         ( RFC 1902/RFC 2578 )
    SNMPv2-TC.my          ( RFC 1903/RFC 2579 )
    SNMPv2-CONF.my        ( RFC 1904/RFC 2580 )
    SNMP-FRAMEWORK-MIB.my ( RFC 2571 )
    PerfHist-TC-MIB.my    ( RFC 2493 )
    ATM-MIB.my            ( RFC 2515 )
    ATM-TC-MIB.my         ( RFC 2514 )
    ENTITY-MIB.my         ( RFC 2737 )
    PNNI-MIB.my           ( From ATM Forum )
    PNNI-MIB-NO-U32.my    ( Same as PNNI-MIB without the Unsigned32 definition )

1.2 Cisco Enterprise MIBs

    CISCO-SMI.my
    CISCO-TC.my
    CISCO-TC-NO-U32.my ( SAME as CISCO-TC without the Unsigned32 definition )

    CISCO-PRODUCTS-MIB.my               : For sysObjectID Values
    CISCO-ENTITY-VENDORTYPE-OID-MIB.my  : For entPhysicalVendorType values

    CISCO-SYSTEM-MIB.my
    CISCO-ENTITY-FRU-CONTROL-MIB.my
    CISCO-ENTITY-SENSOR-MIB.my

1.3 Stratacom Enterprise MIBs(Cisco MIBs Under stratacom enterprise)

    CISCOWAN-SMI.my
    CISCO-WAN-ATM-CONN-MIB.my
    CISCO-WAN-SVC-MIB.my
    CISCO-WAN-SCM-MIB.my
    CISCO-WAN-TRAP-VARS-MIB.my
    CISCO-BPXSES-TRAPS-MIB.my
    CISCO-WAN-COMMON-TRAPS-MIB.my

    BASIS-MIB.my
    BASIS-SHELF-MIB.my
    BASIS-GENERIC-MIB.my 
    GENERICOBJECT-MIB.my
    RTM-MIB.my        
    ERR-STATUS-MIB.my 

NOTE:

1. Following MIBs are part of MGX R1.1.30 release.
   -----------------------------------------------
(In MGX8850 Release 1.x, the MIB file name is finalMib.AXIPOP.my)
(Following MIBs are part of finalMib.AXIPOP.my). These MIB files need
to be loaded only if finalMib.AXIPOP.my file is not loaded.

BASIS-MIB.my
BASIS-SHELF-MIB.my
BASIS-GENERIC-MIB.my 
GENERICOBJECT-MIB.my

2. Following MIBs are released seperately. These MIBs are common
   between multiple products(MGX8850, MGX8220 etc)

RTM-MIB.my        : Replaces rtm.my
ERR-STATUS-MIB.my : Replaces ERR-STATUS-MIB.my


"MIB LOAD ORDER"
-----------------
This section has information on 

 -  MIB Compiler Issues 

 -  MIB Load Ordering 


MIB Compiler Issue(More of Unsigned32 Problem)
---------------------------------------------

   To Know more about Unsigned32 problem while loading MIBs refer item 1.

1)  RFC 14xx based compilers vs RFC 19xx based compilers
    =====================================================

   RFCs 1442-52 define the "party-based SNMPv2".  These RFCs are
   obsoleted by the newer Draft Standard RFCs 1902-08.
   MIB-syntax-wise there are very few differences between these two
   versions of SNMPv2.  However, there are some differences.

   Cisco's MIBs are currently using the RFC 14xx rules.  It is
   expected that the move to RFC 19xx will be made in the
   not-too-distant future.

   If your MIB compiler supports SNMPv2-style MIBs, it probably
   supports one of these two versions of SNMPv2.  You should not have
   any problems if your compiler is RFC 14xx based, however there is a
   known problem with CISCO-TC.my if your compiler is RFC 19xx based.

   If you don't know which version of SNMPv2 your compiler is based
   on, try to load the CISCO-TC.my MIB.  If it loads successfully,
   then you're fine.  If your compiler is RFC 19xx based it might
   complain about the following line:

        Unsigned32 ::= TEXTUAL-CONVENTION

   Unsigned32 is a predefined datatype in RFC 19xx.  For this reason,
   we provide an alternate version of CISCO-TC.my - namely
   CISCO-TC-NO-U32.my, which, as the name implies, does not include a
   definition for Unsigned32 (since the compiler already knows about
   this datatype).  Load this MIB instead of CISCO-TC.my.

   We now also have a PNNI-MIB-NO-U32.my. This is the same as
   PNNI-MIB.my except that it does not include a definition for
   Unsigned32. If you need the PNNI-MIB and are using an RFC 19xx
   based compiler, load the NO-U32 version of this MIB.

NOTE:
   If CISCO-TC.my can not be loaded successfully, load CISCO-TC-NO-U32.my file
   If PNNI-MIB.my can not be loaded successfully, load PNNI-MIB-NO-U32.my file.

2) MIB Load ordering

   Many MIBs use definitions that are defined in other MIBs.  These
   definitions are listed in the IMPORTS clause near the top of the
   MIB.

   If MIB mumble imports a definition from MIB bumble, some MIB
   compilers require you to load MIB bumble prior to loading MIB
   mumble.  If you get the load order wrong, the compiler will
   probably complain about the things that were imported - claiming
   that they are "undefined".

   The following is a list of MIBs that many other MIBs import from,
   and the order that these MIBs should be loaded.  This will probably
   take care of 95% of your load order issues (i.e. most of the other
   MIBs can be loaded in any order).
   If you attempt to load some other MIB and get complaints about
   "undefined" items, look at what MIBs this MIB is importing from.
   make sure that you have loaded all of these other MIBs first.



        SNMPv2-SMI.my
        SNMPv2-TC.my
        SNMPv2-CONF.my
        SNMPv2-MIB.my
        RFC1213-MIB.my
	IANAifType-MIB.my
        IF-MIB.my
        CISCO-SMI.my
        CISCO-PRODUCTS-MIB.my
        CISCO-TC.my (or CISCO-TC-NO-U32.my if CISCO-TC.my can not be loaded)
	CISCOWAN-SMI.my
	SNMP-FRAMEWORK-MIB.my
 	PerfHist-TC-MIB.my
	ATM-FORUM-TC-MIB.my
	ATM-TC-MIB.my
	ATM-MIB.my
	CISCO-ENTITY-VENDORTYPE-OID-MIB.my
        BASIS-MIB.my

Following MIBs can be loaded after the above MIBs are loaded.However follow the
sequence (load order sequence) for the MIBs specified in groups.

ENTITY-MIB.my
CISCO-ENTITY-FRU-CONTROL-MIB.my
CISCO-ENTITY-SENSOR-MIB.my


PNNI-MIB.my(or PNNI-MIB-NO-U32.my if PNNI-MIB.my can not be loaded)
CISCO-WAN-SVC-MIB.my

RS-232-MIB.my

CISCO-SYSTEM-MIB.my

CISCO-WAN-ATM-CONN-MIB.my

BASIS-SHELF-MIB.my

BASIS-GENERIC-MIB.my

GENERICOBJECT-MIB.my

ERR-STATUS-MIB.my

RTM-MIB.my


"LOADING TRAP MIBs"
------------------

Step 1: Load following files only if AXIPOP-MIB(MGX8850 Release 1.x.x File )
        is not loaded.

    BASIS-MIB.my
    BASIS-SHELF-MIB.my
    BASIS-GENERIC-MIB.my
    GENERICOBJECT-MIB.my

Step 2: Load CISCO-WAN-TRAP-VARS-MIB.my

Step 3: Load the following files independent of each other

	CISCO-WAN-COMMON-TRAPS-MIB.my ( Common for MGX8850 + BPX SES )

	CISCO-BPXSES-TRAPS-MIB.my    ( Specific to BPX SES )

"RFC MIBs"
----------


        RFC1213 MIB is same as RFC1213-MIB
	RFC2011 MIB is same as IP-MIB
	RFC2012 MIB is same as TCP-MIB
	RFC2013 MIB is same as UDP-MIB
	RFC2233 MIB is same as IF-MIB
	RFC2558 MIB is same as SONET-MIB
	RFC2496 MIB is same as DS3-MIB
	RFC2515 MIB is same as ATM-MIB
	RFC1907 MIB is same as SNMPv2-MIB
	RFC1902/RFC2578 MIB is same as SNMPv2-SMI
	RFC1903/RFC2579 MIB is same as SNMPv2-TC
	RFC1904/RFC2580 MIB is same as SNMPv2-CONF
	RFC1906 MIB is same as SNMPv2-TM
	RFC2571 MIB is same as SNMP-FRAMEWORK-MIB


- AGENT-CAPABILITIES MIBs: These MIBs contains information about the
  set of capabilities present in the agent for a particular mib. 
  
  These MIBs contain information on the set of values supported for
  objects, access level restrictions, whether object is implemented or not.
  
  For More information, refer RFC 2580.

   The AGENT-CAPABILITIES macro in agent capabilities mibs
   specifies refinements or variations with respect to
   OBJECT-TYPE and NOTIFICATION-TYPE macros
   in MIB modules, NOT with respect to MODULE-COMPLIANCE macros in
   compliance statements.

  
  This might contain information on the following:
     * The access level support restriction on some of the objects

       i.e an object is defined read-write in the MIB. However agent
       supports only read-only access.

     * The restricted SYNTAX level.
       i.e an object is defined with range of 1..100. However agent
       supports only range from  1..10.

     * The Default value used for an object.
    
      i.e an object contain DEFVAL clause and has value 1.
      However the default value support for that object is 2.


    CISCO-SNMPv2-CAPABILITY.my             : For SNMPv2-MIB
    CISCO-SYSTEM-CAPABILITY.my             : For CISCO-SYSTEM-MIB
    CISCO-IF-CAPABILITY.my                 : For IF-MIB in PXM
    CISCO-RS-232-CAPABILITY.my             : For RS-232-MIB
    CISCO-BULK-FILE-CAPABILITY.my          : For CISCO-BULK-FILE-MIB
    CISCO-ENTITY-CAPABILITY.my             : For ENTITY-MIB
    CISCO-ENTITY-FRU-CONTROL-CAPABILITY.my : For CISCO-ENTITY-FRU-CONTROL-MIB
    CISCO-WAN-TOPOLOGY-CAPABILITY.my       : For CISCO-WAN-TOPOLOGY-MIB
    CISCO-ATM-CAPABILITY.my                : For ATM-MIB
    CISCO-PNNI-CAPABILITY.my               : For PNNI-MIB

    CISCO-BPXSES-COMMON-TRAPS-CAPABILITY.my: For CISCO-WAN-COMMON-TRAPS-MIB
    CISCO-WAN-ATM-CONN-CAPABILITY.my       : For CISCO-WAN-ATM-CONN-MIB
    CISCO-WAN-SVC-CAPABILITY.my            : For CISCO-WAN-SVC-MIB
    CISCO-WAN-BASIS-SHELF-CAPABILITY.my    : For BASIS-SHELF-MIB
    CISCO-WAN-BASIS-GENERIC-CAPABILITY.my  : For BASIS-GENERIC-MIB
