Access routes for link configuration.

Fig. 5.9: Menu Link settings / Service access / Services

Service channel	There are two modes of accessing the internal management system of the microwave link: standard and direct
	standard: Both units are configured with the separate IP addresses, Netmasks, Gateways and Management VLANs. IP addresses of both units does not have to belong in to the same sub-net. The “Internal VLAN” is required to encapsulate the internal service traffic between both units of the microwave link. There are additional internal service addresses used for this internal service traffic (see “IPv4 address – Local” section for further details).
	direct: Both units are configured with the separate IP addresses but with the same Netmask, Gateway and the Management VLAN. IP addresses of both units must belong in to the same sub-net. There is no need for “Internal VLAN” to handle the internal service traffic between both units of the microwave link. No additional internal service addresses exist. NOTE: It is strongly recommended to use “Management VLAN” to encapsulate and prioritize the management traffic when the direct mode is selected. If the “Management VLAN” is not used (while in direct mode), the internal service traffic is NOT prioritized.
IPv4 address – Local	Service IP address, by default 192.168.169.169 for L unit and 192.168.169.170 for U unit. Four addresses 169.254.173.236/30 are used for internal communication. Must not be used as service IP address. Those four addresses are not used while “Service channel” is set to “direct” mode. Note Unknown IP address If you forget the Service IPv4 address, it can be found by reading data broadcast through LLDP protocol. Data is transmitted every 60 seconds and contains the following information: Management address: IP address System Description: Serial number Chassis Subtype: Type (e.g. RAY2-17-L) IEEE 802.1 – Port and Protocol VLAN ID: Port and Protocol VLAN Identifier: (e.g. 300 (0x012C)) but only if Management VLAN is enabled The message can be recorded and converted into a readable form using an LLDP client. A suitable tool for this purpose is Wireshark IP traffic analyzing tool, with free licenses available for both Windows and Linux. To locate the message easily, use the Capture filter “ether proto 0x88cc” in Wireshark.
IPv4 address – Peer	Management address of the Peer station. This address has to be set up when the “Service channel” is set to “direct” mode.
Netmask	Mask for service access, 24 by default.
Gateway	Default gateway for service access; empty by default.
Management VLAN	Enables access via VLAN management. Blocks access for https, ssh and telnet configuration via untagged packets (without VLAN) making only VLAN access possible. VLAN management is off by default. WARNING: By enabling VLAN management, ALL accesses are blocked for configuration using normal (untagged) LAN! During tests, you may enable VLAN management on one unit only (if the “Service channel = standard”). Then it is possible to access the link via LAN and VLAN either directly or via radio link.
VID	VLAN management ID, by default 1. This field must have a value entered even when VLAN management is not active.
Protocol	Protocol 802.1q or 802.1ad
Internal VLAN	Valid only for “Service channel = standard”: The RAy uses one VLAN id for internal service communication between both units. There are two situations when it might be necessary to change the Internal VLAN id: – Conflict within user data flow when the same VLAN id is already present within a data flow. – Conflict with the internal management address of another RAy unit located at the same site and connected in the same LAN segment. NOTE: The Ethernet frames within this service channel are marked with IEEE 802.1p priority class “7”. Default parameters for QoS and Egress queue control are pre-set to prioritize this service communication channel.
Web server	Allows access via web server (for HTTP and HTTPS protocol). WARNING: after disabling access via web server, you will not be able to access the unit using a web browser!
CLI (telnet)	Enables access via telnet protocol. Provides access to CLI (Command Line Interface) for simple telnet clients. Disabled by default.
CLI (SSH)	Enables access via SSH protocol. Provides secure access to CLI. If preventing unauthorized access to the unit is the number one priority, leave only this server on.
SNMP	Enabling SNMP server. Off by default.
SNMP community string	SNMP community string. Can contain both lower and uppercase letters, numbers, four characters . : _ – and can be up to 256 characters long.
SNMP trap IP	Address for sending SNMP traps. It is possible to record up to 3 addresses separated by commas.
LED indicators	Enable LED status indicators on the body of the unit. You can turn off all LEDs with this option.
LLDP (Service IP info)	Data transmitted through the LLDP protocol can be accessed in two ways:   On Transmissions every 60 seconds   Single Transmitted once only when unit is rebooted See “IPv4 address – Local … Unknown IP address” for description of the data transmitted through the LLDP protocol.

The USB connector is used for management access (not for user data) to the local unit using Ethernet or WiFi adapter. Only RACOM recommended adapters are supported.

Default WiFi IP address of the unit is 172.17.17.17 with DHCP enabled by default allocating IP address automatically to connected device.

Fig. 5.10: Menu Link settings / Service access / USB accessories

	Note
	When upgrading from FW older than 2.1.28.0 it is necessary to click “Show Defaults” followed by “Apply” to enable smooth WiFi functionality.

List and setup of users. Example menu of the cli_super level user.

Fig. 5.11: Menu Link settings / Service access / Users

Within the default Factory Settings one user is defined in the system. This user has username admin and password admin and is assigned the highest level of permissions cli_super. This user then assigns other users to the system along with their level of permissions.

Service access has three groups of users with different levels of permissions.

Numbers of users that can be defined in the system:

   * The system prevents the user from deleting both cli_super accounts.

The logged on user is shown in the top right of the screen. There can be different users on either end of the link.

	Important
	It is strongly recommended that the default password admin is changed. Similarly all other users should change their password. Using the CLI, it is appropriate to supplement the SSH key.

Note

More users concurrently If two or more users work concurrently on the unit any change of configuration settings should be applied by all users. This applies to the menu Link settings which works with both, Local and Peer parameters. Notification to other users: If one user sends the Apply command, other users will receive a message: “Configuration changed, please go to Link settings and click Refresh”. Other users can only use the Apply command after refreshing Link Settings.

Edit use

Clicking “Edit” next to a username opens a screen with configuration of the given account.

Fig. 5.12: Menu Link settings / Service access / Users / edit

Backup user

Delete user

Add user

Mirror users

Fig. 5.13: Menu Link settings / Alarms / Status

Fig. 5.14: Alarm severity

Overview of alarms

All system alarms are listed on this screen. Inactive alarms are colored white with an “OK” text label. Active alarms are colored according to the severity of the alarm with a text message describing the measured value status.

For a detailed description of each Alarm click on the Alarm name.

Fig. 5.15: Menu Link settings / Alarms / Acknowledge

Alarm acknowledgement allows the operator to confirm the system is set in alarm state. Only an active alarm can be acknowledged. Multiple selections of active alarms (to acknowledge groups of alarms) can be performed using Shift or Ctrl keys.

Fig. 5.16: Menu Link settings / Alarms / Config

The diagnostics system of the link monitors the operation of the unit.

It generates various event outputs – system warnings and alarms. The event is always written to the system log and indicated in the status bar and Alarms/Status screen. Some events have adjustable thresholds. Events with no adjustable thresholds may or may not be Enabled. If they are not Enabled, the system event is not activated even if the system status is changed.

If the event goes above or below the set parameter limits or a link goes down or up, you can choose to send an SNMP trap. All SNMP traps are OFF in defaults.

The unit internal Ethernet switch port status

Fig. 5.17: Menu Switch settings / Port status

The unit internal Ethernet switch RMON counters

Fig. 5.18: Menu Switch settings / RMON counters

The Remote Network MONitoring (RMON) MIB was developed by the IETF to support monitoring and protocol analysis of LANs.

The Internal switch port RMON counters

These counters provide a set of Ethernet statistics for frames received on ingress and transmitted on egress.

Fig. 5.20: Menu Switch settings / Register dump

The exact contents of the internal switch configuration and diagnostic registers can be listed for diagnostic purposes. All registers are separated into several groups.

Fig. 5.21: Menu Switch settings / RSTP

RSTP service status

Port settings

Fig. 5.22: Menu Switch settings / Port

Phyter is responsible for Ethernet signal conversion between wire (e.g. CAT7 cable) and internal switch bus.

The unit internal Ethernet switch Port settings

Fig. 5.23: Menu Switch settings / Port advanced

PIRL (Port based Ingress Rate Limiting) has the task of arranging the transfer of frames; ensuring as few frames as possible are discarded and that ports are not blocked.

Diagram of framework processing options are available within the QoS, PIRL and Egress queue control menus:

Fig. 5.24: PIRL and queues

Frame

The frame comes via port, has a certain length and MAC addresses SA and DA. The IP header carries the DSCP priority and may also carry the 802.1p VLAN priority.

QoS

The Queue priority (QPri) is created based on preferences within the DSCP or 802.1p priority. This priority takes values from 0 to 3, and controls the processing of frames inside the switch.

The Frame priority (FPri) is processed in a similar manner. Frame coming from the network and frame being sent to the network is marked by this priority.

PIRL

Between the port and the common switch there may be between 1 and 5 “flow restrictors” working in parallel according to the schedule “leaky bucket”. These are called “Resource”. This is analogous to the container which is intermittently replenished by tokens according to incoming frames and is continuously emptied. Regulatory measures are implemented at a certain height to ensure the bucket does not overflow.

PIRL – Edit section of this menu is made up of several groups of parameters:

The above mentioned parameters are used to allocate part of a frame to each Resource. Their passage is regulated thus avoiding network congestion. If there is a framework that does not match the filter of any Resource, this then passes to the switch without restrictions.

Switching block

In this block (L2-switch) each frame is routed to a designated port according to the Advanced menu.

Egress queue

Block output queues. Each port receives frames from the L2 switch through 4 queues (No. 3-0). The highest priority has a queue No. 3. The frames are organized into queues according to their priorities QPri.

The Method to empty queues is selected by the parameter Scheduling Mode. The emptying rate is governed by the Rate limit parameter.

A Frame sent from the port to the network can be identified by priority FPri, although it is also possible to change its tag: see menu VLAN/Egress mode.

Port based ingress rate limiting, see also the Functional diagram

Fig. 5.25: Menu Switch settings / PIRL

The device supports per port TCP/IP ingress rate limiting along with independent Storm prevention. Port based ingress rate limiting accommodates information rates from 64 Kbps to 1 Mbps in increments of 64 Kbps, from 1 Mbps to 100 Mbps in increments of 1 Mbps and from 100 Mbps to 1000 Mbps in increments of 10 Mbps.

In addition to this, the device supports Priority based ingress rate limiting. A given ingress rate resource can be configured to track any of the four priority traffic types. One of the popular schemes for implementing rate limiting is a leaky bucket. The way a leaky bucket scheme works is that the bucket drains tokens constantly at a rate called Committed Information Rate (CIR) and the bucket gets replenished with tokens whenever a frame is allowed to go through the bucket. All calculations for this bucket are done in tokens. Therefore, both bucket decrementing and incrementing is performed using tokens (i.e., frame bytes are converted into bucket tokens for calculation purposes).

The device supports a color blind leaky bucket scheme.

The traffic below Committed Burst Size limit (CBS Limit) is passed without any further actions. If the traffic burst were to continue and the bucket token depth approaches closer to the Excess Burst Size limit (EBS Limit) by less than the CBS Limit, then a set of actions are specified. Note that if the frame gets discarded then the equivalent number of tokens for that frame will not get added to the bucket.

There are the two default ingress limiting rules already configured in the switch default configuration. They limit the maximum allowed ARP traffic coming to the CPU port to 10Mbps from Eth1 and 10Mbps from Eth2 ports.

Fig. 5.26: Leaky bucket

Fig. 5.27: Menu Switch settings / PIRL Resource

Each port can be assigned up to five different ingress rate resources.

Each resource defines a rule (filter) for the incoming frame. If the rule is met, the frame is affected (as set by the EBS limit action parameter). If the incoming frame does not meet any rule, it is not affected by PIRL. The frame is accepted and forwarded further to the switch engine.

See also Output queue diagram.

Fig. 5.28: Menu Switch settings / Egress queue

Fig. 5.29: Menu Switch settings/QoS/802.1p

The IEEE 802.1p QoS technique also known as class of service (CoS), is a 3-bit field called the Priority Code Point (PCP) within an Ethernet frame header when using VLAN tagged frames as defined by IEEE 802.1Q. It specifies a priority value of between 0 and 7 inclusive that can be used by QoS disciplines to differentiate traffic. The value 0 is generally taken as the lowest priority and 7 as the highest priority.

Fig. 5.30: Menu Switch settings /QoS/DSCP

The DSCP stands for Differentiated services Code Point which is a 6-bit value stored within the IP header. The QoS techniques using those bits are called DiffServ or Differentiated services.

Fig. 5.32: Menu Switch settings / Advanced / VLAN

Setup of VLAN related and global parameters.

Fig. 5.33: Menu Switch settings / Advanced / STU

The per VLAN Spanning Tree Unit (STU) in the device supports user commands to access and modify the contents of the Port State database.

Primary key	The icon indicates which parameter field is taken as the unique identifier in the database. This field entry ensures each record is unique and must not be duplicated.
SID	VTU 802.1s (MSTP) Port State Information Database number. This parameter indicates the SID number that is associated with the 802.1s “Port state” parameter. It is essential to define the SID to be able to create records in the VTU (VLAN Table).
Label	A custom string label for a STU entry.
Port state	This parameter is used to support 802.1s per VLAN spanning tree. Port states (bellow) are valid for frames with a VID that is associated to this SID:   disabled Use non-VLAN Port States (i.e., the port’s default Port State) for this port.   blocking /listening     learning     forwarding aaaa This “Port state” takes precedence over the port’s Port State bits unless the port’s Port State (driven by STP) is Disabled (which prevents all frames from flowing).
Add entry	Add a new STU database entry.
Edit	Press the Edit button to open the configuration dialog of the selected STU database record. NOTE: Should the Primary key value be modified, the “other” record – identified by the entered Primary key – is added (if it does not exist yet) or modified (if it exists already).
Delete	Delete the selected STU database record.

Fig. 5.34: Menu Switch settings / Advanced / STU / edit

Fig. 5.35: Menu Switch settings / Advanced / VTU

The VTU (VLAN Table Unit) records form the VLAN Table.

Primary key	The icon indicates which parameter field is taken as the unique identifier in the database. This field entry ensures each record is unique and must not be duplicated.
VID	VLAN ID. This parameter indicates the VID number that is associated with the Member tag, VTU Priority, VTU policy and the FID (Forwarding Information Database number).
Label	A custom string label for a VTU entry.
FID	Forwarding Information Database number. If separate address databases are used, this parameter indicates the address database number to use for all frames assigned with this VID. All MAC DA look-ups and SA learning will refer to the address database number defined by the FID associated with the frame’s VID. Multiple VID’s can use the same FID. If separate address databases are not used, the FID must be zero. The ATU database records are joined with the VTU database records via this number.
SID	802.1s Information Database Number. If 802.1s per VLAN spanning tree is being used, this parameter indicate the spanning tree instance number to use for all frames assigned with this VID. Multiple VID’s can use the same SID. The STU database records are joined with the VTU database records via this number.
Use VID priority	VID Priority Override. This parameter is used to indicate that frames assigned with this VID can have their priority overridden with the “VID priority” value (see below) if the port’s “VTU priority override” parameters is enabled to do so. See VTU priority override for more details.
VID priority	VID Priority override value when enabled by the “Use VID priority” parameter (see above). Used for priority override on ingressing frames. Enabling a priority on a VID will override the frame’s priority only if the port’s VTU priority override parameter is enabled to do so.
VID policy	This parameter is used to indicate that frames assigned with this VID can have Layer 2 Policy actions applied to it if the port’s “Policy VTU” (menu Advanced/Monitoring,Policy/Policy) is enabled to do so.
Member tag	This parameters is used to indicate which ports are members of the VLAN (i.e, with the given VID) and if these VLANs frames should be tagged or untagged, or unmodified when exiting the port as follows:   egress unmodified Port is a member of this VLAN and frames are to egress unmodified.   egress untagged Port is a member of this VLAN and frames are to egress Untagged.   egress tagged Port is a member of this VLAN and frames are to egress Tagged.   not member Port is not a member of this VLAN. The result is that frames assigned with this VID can not egress this port. This parameter takes effect only if the “802.1q mode” parameter (see menu Advanced/VLAN) is set to “secure” mode.
Add entry	Add a new VTU database entry.
Edit	Press the Edit button to open the configuration dialog of selected VTU database record. NOTE: Should the Primary key value be modified, the “other” record – identified by the entered Primary key – is added (if it does not exist yet) or modified (if it exists already).
Delete	Delete the selected VTU database record.
Flush all	Delete the whole VTU database.

Fig. 5.36: Menu Switch settings / Advanced / VTU / edit

Fig. 5.37: Menu Switch settings / Advanced / ATU settings

Setup of ATU (Address Translation Unit) table related parameters.

Fig. 5.38: Menu Switch settings / Advanced / ATU

The Address Translation Unit (ATU) in the device supports user commands to access the contents of the MAC address database.

There is one static record which can not be deleted. This is the management CPU record. The unicast frames directed to management are allowed to access the CPU port. The VLAN tunnel parameter is also used to enable the AP frames to access the CPU port.

Primary key	The icon indicates which parameter field is taken as the unique identifier in the database. This field entry ensures each record is unique and must not be duplicated.
FID	Forwarding Information Database number. If multiple address databases are not being used, this parameter must remain zero. If multiple address databases are being used, this parameter is used to set the desired address database number that is to be associated with this ATU Entry’s MAC Address. When frames ingress the switch, the VID assigned to the frame is used to access the VTU. The VTU returns the FID associated with that VID for MAC address lookups in to the ATU.
MAC	MAC address associated with this ATU entry in the database number defined by the FID.
Label	A custom string label for an ATU entry.
Entry state	The Entry state parameter is used to determine the entry’s age or its type as follows:   static Use for ordinary static entry.   static policy Use for “Policy DA” and/or Policy SA (menu Switch settings/Advanced/Monitoring/Policy).   static non rate limiting Use for “SA non rate limit” and/or “DA non rate limit” (menu Switch settings/Interface/PIRL).   static management This value is used for the mapping of the DA even if the “DA mapping” parameter is disabled (menu Switch settings/Advanced/ATU settings).   dynamic Ordinary dynamic entry.
Use MAC priority	Use this parameter to enable the MAC priority (see “MAC priority” description).
MAC priority	Use the MAC priority to override value, when it is enabled by the “Use MAC priority” parameter. It is used for priority override on ingressing frames. Enabling a priority on a MGMT MAC address will override all priorities for these MGMT frames. Enabling a priority on a static, non-MGMT MAC address, will only override the frame’s priority if the port’s DA priority override or SA priority override parameters are enabled.
Trunk member	When this parameter is enabled, the MAC address is a member of a trunk – according to the “Trunk Id” parameter. When this parameter is disabled, the MAC address is associated with port(s) – according to the Port association parameter.
Trunk Id	The Trunk ID associated with this MAC address. The port or ports that this DA MAC address is associated with is determined by the Port association parameter. Use this parameter to ensure the proper unit management CPU is accessed when two units are connected in trunk.
Trunk port association vector	Mask of ports associated with this MAC address.
Add entry	Add a new ATU database entry.
Edit/Copy	Press the Edit/Copy button to open the configuration dialog of the selected ATU database record. NOTE: Should the Primary key value be modified, the ‘other’ record – identified by the entered Primary key – is added (if it does not exist yet) or modified (if it exists already).
Delete	Delete the selected ATU database record.
Flush all and use default	Delete the whole ATU database and create default record(s).
Flush non-static	Delete all except static ATU database records.

Fig. 5.39: Menu Switch settings / Advanced / ATU / edit

Fig. 5.40: Menu Switch settings / Advanced / Monitoring, Policy

Setup of Monitoring and Policy functions.

The Policy functions allow a special handling of specific types of ingress frames.

Fig. 5.41: Menu Switch settings / Advanced / RSTP

The Rapid Spanning Tree Protocol (RSTP) is a network protocol that ensures a loop-free topology for any bridged Ethernet local area network. The basic function of RSTP is to prevent bridge loops and the broadcast radiation that results from them. Spanning Tree Protocol also allows network design to include spare (redundant) links to provide automatic backup paths if an active link fails, without the danger of bridge loops, or the need for manual enabling/disabling of these backup links.

Fig. 5.42: Menu Switch settings / Advanced / Trunk

Port trunking is supported by the device using any combinations of ports. The ports that are to be associated with the trunk need to have all the port members’ defined with the same “Trunk Id” and the “Enabled” parameter has to be enabled.

When a frame enters a Trunk Port its Source Address (SA) is learned with its association to the ingress port’s TrunkID number. In this way the contents of the address database contain the same association with the frame’s SA regardless of the link of the trunk the frame entered the switch.

When frames are routed back toward a trunk the frame will have its Destination Address (DA) found from the address database. If the frame’s DA is unknown the frame will try to flood out all ports of the trunk (this is OK in so far as this will be fixed with load balancing). If the frame’s DA is found, the entry will indicate mapping to a trunk and the entry’s DPV bits will contain the TrunkID associated with this frame’s DA. This TrunkID needs to be converted into a DPV (Destination Port Vector) that the rest of the switch can use. This is accomplished by accessing the Trunk Mapping table using the TrunkID that was in the ATU’s entry.

Fig. 5.44: Menu Tools / Maintenance / Feature keys

The sub-set of RAy parameters is affected by use of SW Feature keys.

The SW Feature keys limiting data transfer speed [Mbps] are available. Speed of the transferred data is determined by a combination of the radio channel bandwidth (parameter Bandwidth [MHz]) and modulation order (parameter TX modulation). The key limiting the data transfer speed enables only certain combinations of the channel bandwidth and modulation order to get the data transfer speed according to the key. The data transfer speed is typically slightly higher than declared.

When installed, the key is activated after the unit restart. The unit can be restarted using the Tools – Maintenance – Restart. Choose the Restart mode – warm.

Fig. 5.45: Menu Tools / Firmware

If a new firmware version is released for the given microwave link type, you can upload it to your RAy units.

Info
Firmware version	Information about the current firmware package version on the Local and Peer units.
Radio firmware version	Information about the radio board current firmware version on Local and Peer unit.
Radio configuration version	Radio board calibration data format version.
Hardware version	Information about the HW version of the modem board.
Radio hardware version	Information about the HW version of the radio board.
Firmware upgrade
Firmware upload	Open file upload – opens a dialog for uploading firmware package to the unit buffer. Only after firmware has been prepared in the buffer, can you perform the actual upgrade. NOTE: Use the file as it is (do not unpack).
File name	Name of the uploaded firmware file.
File size [B]	Size of the uploaded firmware file.
Version in buffer	Information about firmware version prepared in the buffer for installation into the unit (Local, Peer). This firmware must first be prepared in the Firmware upload section (see above).
Clean buffer	You can use the Clean buffer button to delete prepared firmware package in the buffer.
Force upgrade	Force mode blocks all safety and compatibility checks and probably bricks your unit. You should not use force mode until instructed to do so by the technical support.
Upgrade	Use the Upgrade button to perform the firmware installation.
	Warning Installing the firmware takes several minutes (about 3 minutes). During this time, transmission of user data is interrupted. Do not interrupt the power supply during firmware installation!

Fig. 5.48: Menu Tools / Bar indicators

Graphical indication of BER, SNR and RSS.

The Antenna Alignment Tool supports interactive antenna alignment. RSS and SNR are displayed for both local and peer unit. A selected value can be indicated in large font and acoustically. Values are refreshed 10x per second.

When performing antenna alignment, both ATPC and ACM functions should be disabled; their automatic behaviour interferes with the alignment process which is based on finding the maximum signal strength.

The tool is accessed via e.g. http://192.168.169.169/tk for standard Ethernet ports, and via http://172.17.17.17/tk for connections using USB/WiFi or USB/Eth. The Antenna Alignment Tool does not require user authentication.

Fig. 5.49: Ray Tools

Fig. 5.50: Menu Tools / RX constellation

Constellation diagram shows the quality of received signal.

Fig. 5.51: Menu Tools / Frequency analyzer

A very useful tool for identifying in-band interference and locating a free channel. It is not a full-blown spectrum analyzer as it scans the spectrum with 7MHz channel resolution. The accuracy of measured results is given by the accuracy of measuring RSS.

	Warning
	Running spectrum measurement causes interruption of user data flow between stations!

After using the analyzer visit any of the Link menu settings and select Refresh. This restores the configuration connection (message Peer: n/a ).

Preview all values for the last 24 hours. Click on a thumbnail to open the viewer with a chart.

Fig. 5.52: Menu Tools / History / Thumbnails

Detailed graphical view of one or two selected values for the given interval. You can choose to view data from Local or Peer or both.

Fig. 5.53: Menu Tools / History / Viewer

Numerical view of all values

Fig. 5.54: Menu Tools / History / Data

The Ping tool allows sending ICMP pings to a selected address

Fig. 5.56: Menu Tools / Programs / Ping

Start the test by clicking on Send. The result is displayed in the text window.

Web interface for executing non-interactive scripts and programs.

Fig. 5.57: Menu Tools / Programs / CLI

#!/bin/sh
#script checkes if service with the same name or vid already exists
#if not creates a new entry in VTU with given VID
#
#  input parameters:
#      service_name - name of the new service
#      VID - vid of the new service
#
#  return values:
#      0 - ok
#      3 - bad parameter
#      5 - service already exists
#      6 - there already exists an entry with given VID
#     42 - other error

D42_NAME="$1"
D42_VID="$2"

D42N="service_data42"

error()
{
        echo "$D42N: Error: $*" >&2
}

info()
{
        echo "$D42N: $*" >&2
}

die()
{
        error "$*"
        exit 42 #error
}

# basic check if not empty
if [ -z "$D42_NAME" ]; then
        error "Bad service name"
        exit 3
fi
if [ -z "$D42_VID" ]; then
        error "Bad service VID"
        exit 3
fi

D42_FOUND=$(cli_nw_get --vtu all | grep "$D42_NAME")
if [ -n "$D42_FOUND" ]; then
        error "Service(s) with name $D42_NAME found"
        echo $D42_FOUND
        exit 5
fi

D42_VALID=$(cli_nw_get --vtu "$D42_VID" | sed -n 's/^valid=\(.\+\)$/\1/p')
if [ "pre_$D42_VALID" = "pre_true" ]; then
        error "VID $D42_VID is used"
        cli_nw_get --vtu "$D42_VID"
        exit 6
fi

D42_VALID=$(cli_nw_get --stu 1 | sed -n 's/^valid=\(.\+\)$/\1/p')
if [ "pre_$D42_VALID" = "pre_false" ]; then
        info "Creating STU entry with SID=1"
        cli_nw_set --stu 1 'label="D42_auto", port_state=["disabled", "disabled", "forwarding", "disabled", "disabled", "forwarding", "forwarding"]'
        if [ $? -ne 0 ]; then
                die "Failed to create STU entry"
        fi
fi

info "Creating service \"$D42_NAME\" with VID=$D42_VID"
cli_nw_set --vtu "$D42_VID" label="$D42_NAME" 'fid=0, sid=1, pri_override=true, priority=5, policy=false, member_tag=["unmodify", "unmodify", "tag", "unmodify", "not_member", "not_member", "unmodify"]'
if [ $? -ne 0 ]; then
        die "Failed to create service \"$D42_NAME\" with VID=$D42_VID"
fi