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
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)