This read-write field enables or disables usage billing specifically for this logical port, but its actual effect depends on the node-wide nodeBilling setting: when nodeBilling is enabled, this per-port setting takes precedence, but when nodeBilling is disabled, billing is forced off regardless of this object's value; the default here is disabled. An admin needs to understand this precedence relationship before assuming a port is billed just because lportBilling reads enabled, since if the node-level switch is off, no billing happens no matter what this says. For example, an admin who sets lportBilling to enabled(2) on a customer's DXI port but forgets that nodeBilling is still disabled at the node level would be surprised that no usage records are actually generated for that customer.