blob: 129eb49314dc6e55b1c038defa5e83c40412388d [file] [log] [blame]
Shad Ansari2f7f9be2017-06-07 13:34:53 -07001# ========================================================================
2#
3# This is a sample bal_autostart.ini file. If used, it must reside in
4# the same directory as the bcm_sdn_agent executable.
5#
6# Examples for EPON ,GPON, XGPON1, and XGSPON systems are given below. You cannot mix
7# EPON / GPON / XGPON1 / XGSPON entries in this file. Systems are assumed to be either
8# EPON or GPON or XGPON1 or XGSPON (as determined by the entry for topology.pon_mode in
9# the bal_config.ini file). NGPON2 systems are not supported by the autostart feature
10# or BAL code at this time.
11#
12# ========================================================================
13# This is a sample autostart script for a MAPLE EPON system,
14# where ONUs are identified by their MAC address
15#
16# NOTE: This script is only useable on an SDN version
17# of BAL, that is, with the bcm_sdn_agent.
18#
19# On startup, the bcm_sdn_agent code reads this autostart file,
20# then:
21# - brings up the access-terminal
22# - brings up each interface specified in the entry list
23# - brings up a subscriber-terminal for each ONU entry
24#
25# ONU IDs can overlap on different PON interfaces
26#
27# Entry format for an EPON system is:
28# onu=ONU ID, int=PON INTERFACE ID, mac=MAC ADDRESS OF THE ONU
29# e.g.
30# onu=3, int=2, mac=00:33:23:33:33:98
31# ========================================================================
32#
33# Uncomment-out entries below and modify them for your EPON system
34#
35#onu=1, int=0, mac=00:10:18:ad:69:d0
36#onu=6, int=0, mac=00:10:18:ad:63:38
37#onu=3, int=2, mac=00:10:18:ad:66:74
38#onu=12, int=0, mac=00:10:18:ad:29:32
39#onu=3, int=1, mac=00:10:18:ad:59:22
40#onu=3, int=0, mac=00:10:18:ad:68:44
41
42
43
44# ========================================================================
45# This is a sample autostart script for a MAPLE GPON system,
46# where ONUs are identified by their password and serial number
47#
48# NOTE: This script is only useable on an SDN version
49# of BAL, that is, with the bcm_sdn_agent
50#
51# On startup, the bcm_sdn_agent code reads this autostart file,
52# then:
53# - brings up the access-terminal
54# - brings up each interface specified in the entry list
55# - brings up a subscriber-terminal for each ONU entry
56#
57# ONU IDs can overlap on different PON interfaces
58#
59# Entry format for an GPON system is:
60# onu=ONU ID, int=PON INTERFACE ID, vend=VENDOR ID, pass=PASSWORD
61# e.g.
62# onu=3, int=2, vend=VENDOR ID FROM ONU LABEL, pass=ONU PASSWORD
63#
64# NOTE: If bcm_sdn_agent is started in autonoumous ONU activation mode (-O or --auto_activate command line option),
65# vend and pass parameters should be set as 0. In this case, the system does not bring the
66# subscriber terminal up. The subscriber terminal will be activated automatically when discovered.
67# Note that ONU entries with with vend & pass equal and not-equal 0 can be mixed. In this case,
68# some subscriber terminals will be pre-configured, before they are discovered
69# ===================================================================
70#
71# Uncomment-out entries below and modify them for your GPON system
72#
73#onu=1, int=0, vend=4252434d01946121, pass=31323334353637383930
74#onu=6, int=0, vend=4252434d01946132, pass=31323334353637383930
75#
76# Uncomment the entry below if bcm_sdn_agent is started in autonomous ONU
77# activation mode (-O or --auto_activate). The entry below will cause PON
78# interface 2 to be enabled. ONUs will be activated automatically when discovered
79#
80#onu=1, int=2, vend=00, pass=00
81
82
83# ========================================================================
84# This is a sample autostart script for a MAPLE XGPON1 or XGSPON system,
85# where ONUs are identified by their password and registration ID
86#
87# NOTE: This script is only useable on an SDN version
88# of BAL, that is, with the bcm_sdn_agent
89#
90# On startup, the bcm_sdn_agent code reads this autostart file,
91# then:
92# - brings up the access-terminal
93# - brings up each interface specified in the entry list
94# - brings up a subscriber-terminal for each ONU entry
95#
96# ONU IDs can overlap on different PON interfaces
97#
98# Entry format for an XGPON1 or XGSPON system is:
99# onu=ONU ID, int=PON INTERFACE ID, vend=VENDOR ID, registration_id=REGISTRATION_ID
100# e.g.
101# onu=3, int=2, vend=VENDOR ID FROM ONU LABEL, registration_id=REGISTRATION_ID
102#
103# As in case with GPON, bcm_sdn_agent controlling XGPON1 or XGSPON system can be started in autonomous
104# ONU activation mode. In this case vend and registration_id should be set 0.
105# The ONU will be activated automatically when discovered
106# ===================================================================
107#
108# Uncomment-out entries below and modify them for your XGPON1 or XGSPON system
109#
110#onu=1, int=0, vend=4252434d01946121, registration_id=202020202020202020202020202020202020202020202020202020202020202020202020
111#onu=6, int=0, vend=4252434d01946132, registration_id=202020202020202020202020202020202020202020202020202020202020202020202020
112#
113# Uncomment the entry below if bcm_sdn_agent is started in autonomous ONU
114# activation mode (-O or --auto_activate). The entry below will cause PON
115# interface 2 to be enabled. ONUs will be activated automatically when discovered
116#
117#onu=1, int=2, vend=00, registration_id=00