Zhone-GPON-MIB Table View

Configuration parameters that apply to one OLT. This profile is
auto-created.

Configuration parameters applying to a single onu stacked on an olt.
This profile is auto-created.

The gpon port is similiar to VCLs in ATM.  Data is transferred between
OLT and ONU via ports. This profile is dynamically created during
CLI bridge-add, host-add, interface-add commands but must be 
explicitly created during SNMP operation.
          
GEM ports can be created using a supplied I/F index value or
using the next available I/F index value.   Since the GEM Port
is a virtual device, ZMS prefers to supply the I/F index value
because ZMS cannot lookup the newly created GEM port using
shelf/slot/olt/port indexing ( virual devices do not support
these values).
          
How to create a GEM port using next available I/F Index value, 
using a single SNMP packet with multiple var-binds:
          
   1. Do an SNMP-Next of the object ifIndexNext to determine
      the I/F index value of the new GEM port.  The SNMP-Next
      will not result in the auto-increment of ifIndexNext.
          		
   2. Issue single SNMP set command containing the following:
         zhoneGponPortConfigRowStatus.1 = create
         zhoneGponPortConfigRowShelf.1 = 1
         zhoneGponPortConfigRowSlot.1 = GEM port slot
         zhoneGponPortConfigRowOlt.1 = GEM port OLT
         zhoneGponPortConfigRowPort.1 = GEM Port ID value
         zhoneGponPortConfigRowTrafficProfile.1 = traffic profile
          
   The GEM port will be created using the next available ifIndex.
          	  
How to create a GEM port with a specified I/F index value, 
using a single SNMP packet with multiple var-binds:
          
   1. Do an SNMP-Get of the object ifIndexNext to determine
      the next available I/F index value.  The SNMP-Get
      will result in the auto-increment of ifIndexNext.
          
   2. Issue single SNMP set command containing the following:
         zhoneGponPortConfigRowStatus.aaa = create
         zhoneGponPortConfigRowShelf.aaa = 1
         zhoneGponPortConfigRowSlot.aaa = GEM port slot
         zhoneGponPortConfigRowOlt.aaa = GEM port OLT
         zhoneGponPortConfigRowPort.aaa = GEM Port ID value
         zhoneGponPortConfigRowTrafficProfile.aaa = traffic profile
          
      where aaa is the I/F index value collected in step 1.
          
   A GEM Port cannot be created if an I/F translate record
   already exists using the supplied I/F index value.
          
How to delete a GEM port using a single SNMP packet:
          
   1. Determine I/F index of GEM port config profile (aaa)
          
   2. Issue single SNMP set command containing the following:
         zhoneGponPortConfigRowStatus.aaa = destroy
          
Special Notes:
           
   1. The deletion of a GEM port will be prevented if the GEM    
      port supports bridges, interfaces, etc.
          
   2. The GEM port ID value determines the GEM port ONU.

Table for management of upstream bandwidth

Table of discovered serial numbers available
for assignment to onus.

Current status of onu as reported from Gpon driver.

Table containing the OMCI commands for the Managed Entities (ME) on an ONU.
          
The following 'how to' examples demonstrate access of the object
zhoneOnuOmciMEOmciCommands.
          
How to create ME profile:
   1. Determine ME profile instance <aaa>
   2. Place file <filename> into uplink file system
   3. Issue single SNMP set command containing the following:
         zhoneOnuOmciMEProfileRowStatus.aaa = create
         zhoneOnuOmciMEProfileName.aaa = ME profile name
         zhoneOnuOmciMEProfileFilename.aaa = <filename>
          
How to update existing ME profile from a file:
   1. Determine ME profile instance <aaa>
   2. Place file <filename> into uplink file system
   3. Issue single SNMP set command containing the following:
         zhoneOnuOmciMEProfileRowStatus.aaa = import
         zhoneOnuOmciMEProfileName.aaa = ME profile name
         zhoneOnuOmciMEProfileFilename.aaa = <filename>
          
How to extract ME profile into a file:
   1. Determine ME profile instance <aaa>
   2. Issue single SNMP set command containing the following:
         zhoneOnuOmciMEProfileRowStatus.aaa = export
         zhoneOnuOmciMEProfileFilename.aaa = <filename>     
   3. The file <filename> now exists on uplink file system
          
How to delete ME profile:
   1. Determine ME profile instance <aaa>
   2. Issue single SNMP set command containing the following: 
         zhoneOnuOmciMEProfileRowStatus.aaa = destroy

Table containing Generic OMCI commands for an ONU.
          
The Generic profile is 'created' from an existing ME profile.  During this
operation, the 'variable' defintions from the ME profile are extracted
from the ME profile and placed into the Generic profile.   
          
The Generic profile is 'updated' from a file placed into the uplink's file system.
          
The following 'how to' examples demonstrate access of the object
zhoneOnuOmciGenericOmciCommands.
          
How to create Generic profile from ME profile:
   1. Determine Generic profile instance <aaa>
   2. Issue single SNMP set command containing the following:
         zhoneOnuOmciGenericProfileRowStatus.aaa = create
         zhoneOnuOmciGenericProfileName.aaa = profile name
         zhoneOnuOmciGenericProfileMESrcProfileName = ME profile source
   3. Profile is now created and the profile will not contain
      any variables and values.
          
How to update existing Generic profile from a file:
   1. Determine Generic profile instance <aaa>
   2. Place file <filename> into uplink file system
   3. Issue single SNMP set command containing the following:
         zhoneOnuOmciGenericProfileRowStatus.aaa = import
         zhoneOnuOmciGenericProfileFileName.aaa = <filename>
          
How to extract Generic profile into a file:
   1. Determine ME profile instance <aaa>
   2. Issue single SNMP set command containing the following:
         zhoneOnuOmciGenericProfileRowStatus.aaa = export
         zhoneOnuOmciGenericProfileFilename.aaa = <filename>  
   3. The file <filename> now exists on uplink file system
          
How to delete Generic profile:
   1. Determine Generic profile instance <aaa>
   2. Issue single SNMP set command containing the following: 
         zhoneOnuOmciGenericProfileRowStatus.aaa = destroy

Table containing Specific OMCI commands for an ONU.
          
The Specific profile is 'created' from existing ME and Generic profiles.  
During this operation, the 'variable' defintions from the ME and Generic 
profile are extracted from the profiles and placed into the Specific profile.
The ME and Generic profile names are extracted from the ONU's Olt/Onu config
profile.   
          
The Specific profile is 'updated' from a file placed into the uplink's file system.
          
The following 'how to' examples demonstrate access of the object
zhoneOnuOmciSpecificOmciCommands.
          
How to create Specific profile from ME and Generic profiles:
   1. Determine Specific profile instance <aaa> (from ONU's ifIndex)
   2. Issue single SNMP set command containing the following:
         zhoneOnuOmciSpecificProfileRowStatus.aaa = create
         zhoneOnuOmciSpecificProfileFileName = <filename>
   3. The profile is now created and the omciCommands contents have
      been placed into <filename>.  The name of the ME profile 
      used to create the Speofic profile is installed
      into zhoneOnuOmciSpecificProfileMESrcProfile.
          
How to update existing Specific profile from a file:
   1. Determine Specific profile instance <aaa> (from ONU's ifIndex)
   2. Place file <filename> into uplink file system
   3. Issue single SNMP set command containing the following:
         zhoneOnuOmciGenericProfileRowStatus.aaa = import
         zhoneOnuOmciGenericProfileFileName.aaa = <filename>
          
How to extract Specific profile into a file:
   1. Determine Specific profile instance <aaa> (from ONU's ifIndex)
   2. Issue single SNMP set command containing the following:
         zhoneOnuOmciGenericProfileRowStatus.aaa = export
         zhoneOnuOmciGenericProfileFilename.aaa = <filename>  
   3. The file <filename> now exists on uplink file system
          
How to delete Specific profile:
   1. Determine Specific profile instance <aaa> (from ONU's ifIndex)
   2. Issue single SNMP set command containing the following: 
         zhoneOnuOmciGenericProfileRowStatus.aaa = destroy

A table of all GPON OMCI ONU alarms.

A table of the GPON GEM Port Traffic profiles.

Current status of GEM port as reported from Gpon driver.

Table of current-interval statistics gathered via 
OMCI from ONT's as specified in the ME profiles used 
by that ONT.

Table of previous-interval statistics gathered via 
OMCI from ONT's as specified in the ME profiles used 
by that ONT.

Table of current-interval statistics gathered via 
OMCI from ONT's as specified in the ME profiles used 
by that ONT.

Table of objects used to reboot an ONU via the OMCI.

Table of objects used to configure the admin state
of a physical port on an ONU.

This table is used to perform ONU software upgrades.
There is one table entry for each ONU.
Each ONU is addressed by it's ifIndex.

Current Status of OLT as reported from the Gpon Driver.

Current status of OLT DBA as reported from CAC.

Information about onu upgrade.

Per OLT statistics gathered from Broadlight device.

Per ONT Upstream Statistics provided by Broadlight.