zhoneGponPortConfigTable

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "zhoneGponPortConfigTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "ZhoneGponPortConfigEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"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.\"",
    "::=",
    "{",
    "zhoneGponObjectID",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "ZhoneGponPortConfigEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "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."
    ],
    null,
    null,
    null,
    null
  ]
}