Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
# comment, ignored. columns: nodename,interface index,interface description,type name
"some node","1","FastEthernet0/0","categoryA"
"not_the_greatest_name","10","Dialer1","catB"
"pleasefindme",,"Dialer1194","categoryA"
"iknowtheindex",12,,"catB"


Burst Billing Customer List

...

This is implemented again using a list file, but  with a very specific format.

In the GUI you'd select "from Burst Billing Customer List file must contain one node plus one interface plus one client number/service number plus contracted upstream plus contracted downstream in this order.
Interface can be listed by index or by interface description.

...

File (Upload)" and upload the file of choice.
For opreports-cli you use burst_billing_customer_list=<path to listfile>,
and for a scheduled report you would set the property burst_billing_customer_list with the value being the path to the list file.

The Burst Billing Customer List can only be in csv format:

  • Each entry must start with the node name, folllowed by an interface, a client number, contracted upstream (mbps) and contracted downstream (mbps):

    Code Block
    titleBurst Billing Customer List in csv format

...

  • ASGARD,FastEthernet0/0,809-101-6782,

...

  • 5,

...

  • 45
    ASGARD,2,809-101-

...

  • 6782,

...

  • 60,

...

  • 5
    Huawei_AR2240,5,12345678,

...

  • 20,

...

  • 200
    Huawei_AR2240,GigabitEthernet0/0/1.243,12345679,100,

...

  • 10
    Teldat_ATLAS60,ethernet0/0.3839,12345670,20,20
    TeldatM1

...

  • ,10,

...

  • 12345671,10,10


    Interfaces can be identified by the numeric SNMP interface index, or by the SNMP ifDescr property
    .


Nodes and Interfaces that are part of an opCharts Business Service

...