_______________________________________________________________________________________________________
_______________________________________________________________________________________________________
© Virtual Access 2017
GW7304 Series User Manual
Issue: 1.9
Page 9 of 336
Some configuration sections can be defined more than once. An example of this is the
routing table where multiple routes can exist and all are named ‘route’. For these
sections, the UCI command will have a code value [0] or [x] (where x is the section
number) to identify the section.
Web Field/UCI/Package Option
Description
Web: Metric
UCI: network.@route[0].metric
Opt: metric
Specifies the route metric to use.
Note: these sections can be given a label for identification when using UCI or package
options.
network.@route[0]=route
network.@route[0].metric=0
can be witten as:
network.routename=route
network.routename.metric=0
However the documentation usually assumes that a section label is not configured.
The table below shows fields from a variety of chapters to illustrate the explanations
above.
Web Field/UCI/Package Option
Description
Web: Enable
UCI: cesop.main.enable
Opt: enable
Enables CESoPSN services.
0
Disabled.
1
Enabled.
Web: Syslog Severity
UCI: cesop.main.severity
Opt: log_severity
Selects the severity used for logging events CESoPSN in syslog.
The following levels are available.
0
Emergency
1
Alert
2
Critical
3
Error
4
Warning
5
Notice
6
Informational
7
Debug
Web: Agent Address
UCI: snmpd.agent[0].agentaddress
Opt: agentaddress
Specifies the address(es) and port(s) on which the agent should
listen.
[(udp|tcp):]port[@address][,…]
Table 1: Example of an information table
1.2.2
Definitions
Throughout the document, we use the host name ‘VA_router’ to cover all router models.
UCI commands and package option examples are shown in the following format:
root@VA_router:~# vacmd show current config