TRONTEQ 006-130-117 ROQSTAR Gigabit Managed Ethernet Switches User Manual

• DHCP Option 82 Leases may be used to assign the same IP configuration to any network host attached to a specific ROQSTAR port (port based).
• Host Based MAC Leases may be used to assign the same IP configuration to a specific network host as identified by it’s MAC address.

The ROQSTAR device supports a separate DHCP server for each VLAN / IP subnet (also called DHCP subnet). Each DHCP subnet can be configured independently. A DHCP-subnet is represented by valid VLAN / IP Interfaces combinations configured in the ROQSTAR device. Changes to either VLAN or IP interfaces configuration will directly impact the DHCP configuration as follows:

• changing the IP Address of an IP Interface will reset the existing DHCP configuration belonging to the respective subnet
• deleting the IP Address of an IP Interface will reset the existing DHCP configuration belonging to the respective subnet. DHCP Service will not function on subnet in which the ROQSTAR has no configured IP address (the IP address is 0.0.0.0).
• adding an IP Address to an IP Interface will automatically create a corresponding DHCP subnet.
• changing Port VLAN Membership will reset the existing DHCP Option 82 Lease DHCP configuration of any affected ROQSTAR ports.
• deleted VLAN Ids or VLANs without any Port Members will have their corresponding DHCP configuration deleted.

Notes:

• Create stable VLAN and IP Interfaces configuration before creating a DHCP configuration
• Extending the VLAN or IP Interfaces configuration will have no impact on the existing DHCP configuration.

Name
A fixed identifier stating the VLAN from which this DHCP Subnet was created.
Note: Local subnets are automatically created/deleted/reseted based on the local VLAN / IP Interfaces configuration.
IP Interface
The corresponding IP Interface configuration for this DHCP Subnet.
Needs to be non 0.0.0.0.
Note: DHCP subnets with no IP Address are unusable for DHCP server
Network
The network address of the current subnet derived from the IP Interface configuration.
Needs to be non 0.0.0.0.
Netmask
The netmask address of the current subnet derived from the IP Interface configuration.
Needs to be non 0.0.0.0.
DHCP Role
server: The ROQSTAR device operates as a DHCP Server for all enabled subnets.
relay: The ROQSTAR device operates as a DHCP Relay for all enabled subnets.
DHCP Active Check mark to enable or disable the DHCP operation for this subnet.
Enabling the DHCP operation on this subnet will reroute all DHCP packets entering the ROQSTAR device to the local DHCP service.
Description A descriptive text can be saved here.
DELETE
Remote DHCP subnets may be removed with this operation.
Note: This button is disabled for automatically created DHCP subnets based on the local VLAN / IP Interfaces configuration.
APPLY
This button becomes available only when a configuration setting has been changed. Using this button will validate and apply the DHCP configuration for this subnet.
Notes:

• Using the APPLY operation for a DHCP Subnet, it will discard any unsaved changes which may have been made in other DHCP subnets.
• Unsaved DHCP configuration for a subnet is indicated by a light yellow background color of the subnet table.

Other Server This setting configure the DHCP service on this Subnet to use a remote DHCP Server located in another device. When configured this will set the DHCP Role to “relay”.
Note: The IP Address 127.0.0.1 configured here points to the local DHCP Server.
This Switch This setting configure the DHCP service on this Subnet to use the local DHCP Server. When configured this will set the DHCP Role to “server”.
Note: The Parameters settings will be visible only when this setting is selected.
Parameters
Lease Time: the time in seconds after which an IP Address configuration leased to a DHCP Client expires. After expiration the lease will be marked as free and reused for future leases. The default value is 86400 seconds (24 hours) with the minimum value being 300 seconds (5 minutes) and the maximum 604800 seconds (7 days).
Default Pool: An IP Address range valid within this subnet’s range of valid network hosts and non-conflicting with any static leases configuration. The range start IP Address needs to be smaller or same as the range end IP Address in order to be able to define a valid range. The default range 0.0.0.0 to 0.0.0.0 means that no dynamic leases are configured which effectively disables dynamic clients IP Address configuration.
Edit DHCP Parameters: A drop-down list of additional DHCP configuration parameters which may be offered to DHCP Clients together with an IP Address lease. The parameters are grouped in this list when their default configuration remains unchanged. Select any parameter from the dropdown list to configure it. Delete the value of any configured parameter to restore it to its default state.
Netmask: The DHCP Option 1 – Subnet Mask information to be offered to clients. The default value is the same value as the local subnet’s network mask. A valid value here needs to be a subset of the local subnet’s network mask.
Gateway: The DHCP Option 3 – Router information to be offered to clients.
The default value is 0.0.0.0 which means that no Router information is offered. A valid value here needs to be an IP Address non-conflicting with the Network and Netmask addresses, with the Default Pool range or with any static lease IP Address configuration. The Gateway’s IP Address is also required to be included in the range of valid IP Hosts for this Subnet.
Primary DNS and Secondary DNS: The DHCP Option 6 – Domain Name Server information to be offered to clients. The default value is 0.0.0.0 which means that no DNS Server information is offered to clients. The Secondary DNS may be used only in conjunction with a valid Primary DNS.
Domain: The DHCP Option 15 – Domain Name information to be offered to clients. The default value is an empty text string. Domain names up to 255 characters may be configured here. Type
O82: short name for static Port Based O82 Leases.
MAC: short name for static Host Based MAC Leases.
DYN: short name for dynamic leases.
Note: O82 and MAC leases are added through the Click to configure new static lease drop-down list.
Identifier
for O82 leases this is the Port Name where a fixed static IP Configuration is offered to any attached device.
for MAC leases this is the MAC Address of a client being offered static IP Configuration. A value of 00:00:00:00:00:00 means that the lease is not yet configured.
for DYN leases this is the MAC Address of the client using this dynamic lease.
IP Address
For all lease types this is the IP Address associated with this lease.
State
N/A: the lease is unconfigured.
free: the lease is not in use by a client.
leased: the lease is used by a client.
Expiry
Time in HH:MM:SS until this lease expires.
If the lease is inactive then 00:00:00 is displayed.
Operation
DELETE: this button will delete the selected lease and its configuration.
Note: after using DELETE the whole DHCP Subnet configuration needs to be saved in order to effectively deactivate the lease.
Click to configurenew static lease
By default the Lease Settings table has no lease configuration. Only through this drop-down list new static leases may be configured.
This drop-down list offers the list of unconfigured Port Based O82 leases ( DHCP Option 82 Leases) and a Host Based MAC lease which may be multiple times selected for individual static MAC leases configuration.
The presence of Port Based O82 leases is directly influenced by the Port VLAN Membership. Adding and/or removing port members in a VLAN will add and/or remove Port Based O82 leases in the Lease Settings configuration.
Once a Port Based O82 lease is selected it will be directly shown in the Lease Settings table.
A Port Based O82 lease is returned to this drop-down list after a DELETE operation.
4.4 Rapid Spanning Tree
Spanning Tree is a protocol and algorithm used to prevent packets from circling in loops. This is crucial when the physical network topology consists of one or more rings. Rings are often used to get redundant physical communication paths.
If there are no loops (rings) in your network topology, we recommend disabling Spanning Tree.
In such a setup Spanning Tree is needed for correct network operation. Otherwise switching loops are created which will inhibit the correct and stable operation of the whole network, because traffic will quickly reach 100% utilization.
Spanning Tree is able to detect such loops in the physical topology and break them up logically. For proper operation a Root Bridge is needed, towards which all other Ethernet Switches in the network will maintain open communication. The placement of this Root Bridge may be critical to the performance of the whole network in cases where frequent link failures occur.
Best practices indicate that the Root Bridge should be the Ethernet Switch with the most central physical position in the network, which has the most available bandwidth. It makes sense to also designate a second best Ethernet Switch as “backup” Root Bridge.
To decide which Ethernet Switch will be the Root Bridge the configurable Bridge Priority parameter is used. A lower value specifies a higher priority. In case of equal Bridge Priority values the Management MAC Addresses will be used as a tie breaker to determine the Root Bridge.
To ensure proper Spanning Tree operation in a network all Ethernet Switches must either forward or process the RSTP packets. Therefore all devices that support RSTP should have that feature enabled.
RSTP works on the physical connection and is not affected by VLANs. If RSTP is enabled, RSTP packets are sent on all ports, irrespective of VLANs. If VLANs are used, care must be taken to ensure that rings present in the topology carry the same VLANs for the complete ring (respectively).
The source MAC address of the sent RSTP packets is that port’s individual MAC address.
Spanning Tree Protocol
RSTP: Spanning Tree operation according to IEEE 802.1Q2005 RSTP standard.
none: Spanning Tree operation is disabled.
Bridge Priority
Values starting from 0 to 61440 based on which a “root” bridge can be elected. A value of 0 is the highest priority.

Enhanced Features

5.1 Power Over Ethernet (PoE)
Power over Ethernet (PoE) is a standard to deliver power through Ethernet cable. The ROQSTAR device acts as Power Sourcing Equipment (PSE), while the connected device, that consumes the power, is called Powered Device (PD).
As soon as PoE enabled on a port, the PoE function will automatically monitors the port for a PD detection and classification. If a valid PD is detected, it will be classified according to IEEE802.3at and powered according port settings.
ROQSTAR device utilizes port based power management settings to budget power per port.
This is necessary to avoid overallocation of power. Practically, most of the PDs are low power devices. There are two options to set budget power per port, based on:

• PoE Class: Power allocation values per port are 4W, 7W, 15.4W, 30W
• Current Limit: Power allocation values per port are 2W, 4W, 6W, 8W, 10W, 12W, 15W, 20W

Port
The name of the specific port being configured.
Powered Name
Device Descriptive name which may be used for the PD.
Enable PoE
Check box for enabling/disabling PoE on the selected port.
Limit Class
Setting for Class Limit according to PoE Classes. PD with classification matches set Limit Class or lower will be powered.
PoE Class overview:

• Class 0 (15.4W)
• Class 1 (4W)
• Class 2 (7W)
• Class 3 (15.4W)
• Class 4 (30W)

Note: Class 0 is handled as Class 3
Nominal Power Limit
Setting for port based power budget according to current limit values. PD equal or lower to set current limit will be powered. In case a PD exceeds the port power budget, it will be immediately dropped.
Possible values:

• Class based (current limit set according to Class Wattage)
• 2W (current limit set to 56.25mA)
• 4W (current limit set to 93.75mA)
• 6W (current limit set to 131.25mA)
• 8W (current limit set to 168.75mA)
• 10W (current limit set to 206.25mA)
• 12W (current limit set to 243.75mA)
• 15W (current limit set to 318.75mA)
• 20W (current limit set to 412.50mA)

Priority
Port based priorities for dropping PD in case of exceeding power budget.

• low: PD on this ports will be dropped first
• high: PD on this ports will be dropped, after all low priority ports are being dropped
• critical: PD on this ports will be dropped at last

ITxPT xstatus
Enable PoE port power off reporting via xstatus on this port
Note: All limits are measured at the port of ROQSTAR device. The available power reaching the PD also depends on the length and quality of the cable connection.
5.2 Network Address Translation (NAT)
This feature allows communication between selected hosts in different IP segments.
The 1:1 NAT is an IP address translation between the External IP Address and the Device IP Address. The External IP Address is a “virtual” IP address inside ROQSTAR device. All incoming packets for the External IP Address will be sent to local Device IP Address by replacing the original External IP Address with the Device IP Address.If Masquerade is enabled this will also replace the source address with the ROQSTAR device’s IP address. For both parties it looks like they are communicating with a device in the local subnet. This has the advantage that no routing tables and gateway are needed.
If Masquerade is disabled, extra settings are needed in the local device:

• default gateway should be set to IP address of ROQSTAR device, or
• a routing table entry to the device should be configured

Masquerading makes the configuration much easier, because the participating device doesn’t need default route (or gateway) configuration.
Note: Changing the NAT settings will interrupt existing connections. NAT enabled
Enable / Disable NAT function.
Set NAT Status
enable NAT: This operation will activate the NAT function disable NAT: This operation will deactivate the NAT function. All existing NAT rules will be removed. Device IP Address
The Device IP Address of the device that should be reachable form the other network
External IP Address The IP Address that should represent the device in the other network
Masquerade
enable Masquerade: If Masquerade is selected this will also replace the source address with the ROQSTAR device IP address.
disable Masquerade: No masking of the sender.
Note: Masquerade will not need extra routing table entries.
Notes:

• IP Forwarding will allow IP packets to be routed between different VLANs if they match a NAT rule. This is necessary to applying NAT rules for IP packets entering or exiting this IP Interface.
• Proxy ARP will allow the ROQSTAR device to answer ARP requests regardless of VLAN.

5.3 Port Forwarding
This feature will redirect a single TCP or UDP port to a different device. The Incoming IP Address must be one of the ROQSTAR device’s IP addresses. Incoming IP Address The IP Address where connections are expected. This must be a ROQSTAR device’s IP Address to work
Incoming Port
The port where connections are expected.
Note: If a port is used where a service is running (e.g. the web server) this service will no longer be reachable.
Protocol
The Protocol

• TCP
• UDP

Destination IP Address The IP Address where packages are sent to.
Destination Port The Port where packages are sent to.
Masquerade enable Masquerade: This will mask the original sender of the message with the ROQSTAR device’s IP Address disable Masquerade: No masking of the sender.
Note: Masquerade makes routing table entries unnecessary.
5.4 Quality of Service (QoS)
QoS feature allows setting priority to outgoing packets. Priority is mapped to output queues.
Each port contains eight independent output queues with different options for priority.
Depending on the queue’s properties an algorithm selects which of the queues gets to send the next packet.
There are two different types of queues:

• Strict queues have a ranking. First, all packets of the highest-ranking queue are sent, then all packets of the next-highest ranking queue etc.
• Weighted queues have a fixed ratio between them. For example one queue is allowed to send two times as many packets as a particular other weighted queue. A round robin scheduling is utilized. Weighted queues are ranked lower than strict queues.

The priority ranking is: Q7 > Q6 > Q5 > [round robin between Q4/Q3/Q2/Q1/Q0].
Assigning packets to a queue is possible through values in the packet itself (the PCP value of a VLAN tag or the DSCP value of an IP header) or by assigning fixed priority to the port the packet was received on.

port, regardless of their PCP or DSCP values.
PCP

default queue| Packets are assigned by their PCP value (if a VLAN tag is present), else to the configured “Default Queue”.
DSCP
default queue| Packets are assigned by their DSCP value (if a IP header is present), else to the configured “Default Queue”.
PCP
DSCP
default queue| Packets are assigned by their PCP value (if a VLAN tag is present), else by their DSCP value (if a IP header is present), else to the configured “Default Queue”.

The assignment of PCP / DSCP values to the queues is defined in corresponding tables:

• mapping of PCP value (0..7) to queue (Q0..Q7)
• mapping of DSCP value (0..63) to queue (Q0..Q7)

Notes:

• If ROQSTAR device adds VLAN tag to packet the PCP value in this tag will be determined by DSCP to PCP mapping. There is an additional mapping for this case: mapping of DSCP value (0..63) to PCP value (0..7).
• In all other cases the configured “Default PCP” value of the packet’s ingress port is used.
• Typically there are no usable PCP/DSCP values in the packets coming from the peripheral devices, so the ROQSTAR device could be configured to use the “Default Queue” criterion. A port whose connected device should always be allowed to send, is assigned the Default Queue Q7 (strict, highest rank), while two less important devices are assigned Q2 and Q4. Q4 is favored by a factor of 12/3=4 compared to Q2. When the packets coming from these devices have the same destination port, the packet scheduling is as follows: As long as there are packets in Q7 they are sent exclusively. When Q7 is empty, both Q2 and Q4 are allowed to send. As long as both contain packets, Q4 sends four times as many packets as Q2.

5.5 Bypass Relay
The bypass relay function provides connection between two ports even if ROQSTAR device is power down or failed to boot the software image.
The bypass relay is build in between two ports. If ROQSTAR device is in power down or in boot process, the relays are closed and hard-wire the bypass relay ports. In this state the data traffic may pass through these ports. As soon as the ROQSTAR device is in operation, the bypass relay is switched off, and data traffic flows through ROQSTAR Ethernet Switch and will be processed according settings in ROQSTAR device. Notes:

• If the bypass is active the port LED of bypass relay ports are off.
• If the bypass is active ROQSTAR Ethernet Switch has no impact on data traffic flows on the bypass relay ports.

Diagnostic Features

6.1 Identifying the ROQSTAR Device
ROQSTAR devices have several identifiers that are either immutable and unique or can be changed by the user.

LLDP message
SNMP sysDescr
DNS-SD inventory
host name| roqstar-fcf8b7080286| unique| LLDP message
SNMP sysName
Management
MAC address| FC:F8:B7:08:02:86| unique| type label on enclosure
web interface
LLDP message
IP communication
Port MAC addresses| FC:F8:B7:08:02:87 one for each Ethernet port| unique| web interface
LLDP message
SNMP ifPhysAddress
Description| CCTV Switch_123| parameter| web interface
Contact, Location| Vehicle_123, Door_1| parameter| web interface
SNMP sysContact, sysLocation

6.2 Port Monitoring
This monitoring function shows the current state and settings of the Ethernet ports:Port
The name of the port as seen on the device’s casing
Name
A descriptive name assigned by the user
Link Status
down: the port has no link partner or link negotiation failed up: the port has successfully established a link with another device
Speed Status
“-”: no speed can be reported because there is no link
10: 10 Mbit Ethernet
100: 100 Mbit Fast Ethernet
1000: 1000 Mbit Gigabit Ethernet
Duplex Status
full: Ethernet Full Duplex operation is active.
half: Ethernet Half Duplex operation is active. If this mode hasn’t been explicitly configured then it may be an indicator of cable problems or link configuration incompatibilities.
Link Configuration Current configured setting
Auto Negotiation Configuration
Current configured setting
Speed Configuration Current configured setting
Duplex Configuration Current configured duplex setting
MAC
The MAC Address associated to this port
6.3 Packet Counters
The ROQSTAR device continuously counts the packets traffic. These counters are shown in the web interface and may be used when troubleshooting.
Note: All counters are 64 bit counters which on overflow will reset the value to 0
Port
The name of the port as seen on the device’s label.
Incoming Octets
The total number of bytes received on this port since ROQSTAR device has been powered on.
Incoming Unicast Packets
The total number of unicast packets received on this port since ROQSTAR device has been powered on.
Incoming Non-Unicast Packets
The total number of non-unicast packets (multicast and broadcast packets) received on this port since ROQSTAR device has been powered on.
Incoming Discards
The total number of packets which could not be received on this port since ROQSTAR device has been powered on.
Note: Due to bandwidth the packets need to be discarded because not enough resources are available to correctly process them.
Incoming Errors
The total number of malformed packets received on this port since ROQSTAR device has been powered on.
Note: Malformed packets may be generated by cable issues or incorrect port settings.
Outgoing Octets
The total number of bytes sent on this port since the ROQSTAR device has been powered on.
Outgoing Unicast Packets
The total number of unicast packets sent on this port since the ROQSTAR device has been powered on.
Outgoing Non-Unicast Packets
The total number of non-unicast packets (multicast and broadcastpackets) sent on this port since the ROQSTAR device has beenpowered on.
Outgoing Discards
The total number of packets which could not be sent on this port since the ROQSTAR device has been powered on.
Note: Due to bandwidth constraints, the packets need to be discarded because not enough resources are available for correct processing.
Outgoing Errors
The total number of malformed packets sent on this port since the ROQSTAR device has been powered on.
6.4 PoE Monitoring
This monitoring function shows the PoE port state, allocated total power, detected PD classes, power consumption, voltage and current values per port.
Power budget
The Power Budget shows total power value available and that may be allocated by all PoE devices in sum
Power allocated
The Power Allocated shows how much power is currently
Port
The name of the port as seen on the device’s casing
PD Name
This is a descriptive name which may be used for the powered device
PoE Mode
PoE operation on the selected port
Priority
Set port priority
PoE Status
PoE state of the port
PD Class
This shows the class of the connected PoE device
PD Limit Class
The upper limit for the maximum accepted PoE class on this port
Power Limit
This shows the current Nominal Power Limit for this port
Power allocated
This shows how much power is allocated for this port
Power Usage (W)
This shows the present power delivered
Voltage (V)
This shows the present voltage on the port
Current (mA)
This shows the present current delivered by the ROQSTAR device in mA
6.5 Event Logging
6.5.1 Internal Event Logging
The ROQSTAR device can store up to 8000 log entries in its internal memory. By exceeding 8000 entries a corresponding event with message “Log entries limit 8000 exceeded.” is generated and oldest entries will be replaced if new event entries occur.
Following interaction are supported:
Reload Log
This operation will refresh the log entries being displayed.
Download Log
This operation will offer for download a CSV formatted file containing all log entries.
Clear Log
This operation will delete all current log entries.
The log entries information is organized as follows:
Total Runtime
The total run time of the device since the first boot.
Synchronized Time (UTC)
The synchronized time in UTC format.
Note: This is available only when NTP synchronization is active.
Impact
The impact describes the importance or the severity of the log message:
CRITICAL: Function is disrupted.
ERROR: Function error is detected.
WARNING: Function may not behave as expected.
NOTICE: Informational message, no function impact.
Service
The service that triggered the message. May be one of:
POE: Power Over Ethernet function.
NTP: Network Time synchronization function.
POWER: Power supply monitoring function.
PORT: Switch port management function.
STP: Spanning Tree function.
IP: IP Interfaces management function.
SYSTEM: System management function.
USB: USB management function.
DHCP: Dynamic IP Address configuration function.
Message
The message body.
6.5.2 Remote Event Logging
This feature allows to send log messages to a remote server for collection and storage in addition to the local event logging. In case no network connection is available an effort to try sending the log messages later is made. The feature utilizes the syslog protocol via UDP and TCP.
Apart from the event-driven log messages sending of periodic messages can be enabled, also known as MARK or heartbeat messages. On the receiver side their presence indicate that the ROQSTAR device is running and the network connection is alive.
Enable
Activate or deactivate the remote logging functionality.
Destination
The IPv4 address or hostname of the computer the log messages shall be sent to.
Protocol, Port
The protocol (either UDP or TCP) used to send the log messages, along with the protocol’s destination port (1 – 65535).
Periodic heartbeat messages
Whether periodic messages (also known as “MARK”) shall be sent to signify that the ROQSTAR device is still “alive”.
Interval of heartbeat messages
Interval of the heartbeat messages from 10 seconds to 3600 seconds.
6.5.3 NTP Client
The ROQSTAR device is able to synchronize its internal time with a remote source. The NTP Client queries the time from a NTP server, whose address must be configured. Either an IPv4 address or a hostname. The interval in which the time is queried is configurable from 8 seconds to 1092 minutes.
Once the NTP Client has synchronized its clock it will generate a log entry. This can be used to calculate the time of earlier log entries. The time synchronization status will be directly visible in the log entry.Enable
Activate or deactivate the time synchronization service.
Server IP
The IP Address or hostname of an NTP time source server.
Query Interval
This interval determines how often the client should sent time requests to the server.
6.6 DNS-SD Inventory Service
The DNS-SD Inventory service can be used for discovering and monitoring devices. It utilizes mDNS multicasts, so devices can be discovered even if it is not known which or how many devices are expected. This inventory service is specified by ITxPT and implemented according to specification version 2.1.1.
The information is provided by a TXT record. It is automatically transmitted at startup and can also be queried via the address _itxpt_socket._tcp.local

FCFFFFFFFFFFFF

6.7 ITxPT xstatus
The xStatus is information provided in the ITxPT inventory service TXT record. It is used to publish the device status in a generic way. Up to 60 device status are supported. Each device status can have one of the following states:

6.7.1 Device Status No. 1
The Device Status No. 1 will have the value of the most urgent values of the other device status fields that are supported. In that sense it reports whether there are any alerts.
6.7.2 Device Status No. 20
The Device Status No. 20 reports ROQSTAR device’s power supply

supply voltage of V2 is valid
10 (Warning)| supply voltage of V1 is valid
supply voltage of V2 is not valid
---|---

6.7.3 Device Status No. 31
The Device Status No. 31 reports link status, if enabled

6.7.4 Device Status No. 32
The Device Status No. 32 reports global status of PoE function

6.7.5 Device Status No. 33
The Device Status No. 33 reports status of PoE ports, if enabled

6.8 SNMP
The SNMP function allows for remote monitoring of certain ROQSTAR device functions. The information is defined in MIBs and referred to by their OID numbers. The MIBs supported by ROQSTAR devices are

• MIB-2 > system (OID 1.3.6.1.2.1.1)
• MIB-2 > ifTable (OID 1.3.6.1.2.1.2.2)
• MIB-2 > powerEthernetMIB (OID 1.3.6.1.2.1.105)
• LLDP-MIB (OID 1.0.8802.1.1.2)

SNMP versions 1, 2c and 3 are supported. SNMP version 1 and 2c implement access based on a community name. ROQSTAR device supports one community with read only access (read community) and one community with read and write access (write community). In these SNMP versions the authentication mechanism transmits the communities in an insecure manner over the network.
In SNMP version 3 a stronger authentication mechanism is used to prevent eavesdropping.
The supported cryptography standards are SHA as authentication protocol and AES-128 as privacy protocol. Together with the user settings these are the credentials required when requesting information via SNMPv3.
Note: It is possible to forego authentication by omitting the passwords.
Server settings: Version 1
Check mark to enable or disable SNMP version 1.
Version 2c
Check mark to enable / disable SNMP version 2c.
Version 3
Check mark to enable / disable SNMP version 3.
Read Community
The community name consisting of a size between 4 to 32 characters.
Write Community
The community name consisting of a size between 4 to 32 characters.
User settings Username
SNMPv3 user name to be added. A valid user name must have a size between 1 to 32 printable ASCII characters.
Note: An SNMP version 3 user has always read and write access.
Authpass
SNMP Authentication password for the new user. A valid password must have a size between 8 – 255 printable ASCII characters.
Privpass
User’s private password consisting of a size between 8 to 255 printable ASCII characters.
Add User
This operation configures the given user.
6.8.1 SNMP Traps
SNMP Traps are messages sent by the ROQSTAR device to give notification on certain events to a remote server for monitoring purposes.
Note: SNMP traps are always sent using SNMP version 1.
SNMP Traps are configured with the following parameters:
Enable
Check mark to enable or disable the SNMP trap function.
Receiver
The IP address or hostname of the SNMP trap receiver.
Trap Community
The name of the SNMP Trap community used for authentication.
Supported SNMP Trap events:

bindings: value: 3
Powered device is removed| A port identifier in the form of pethPsePortIndex from powerEthernetMiB.| 1.3.6.1.2.1.105.0.1| Variable bindings: value: 4
PoE power supply disabled/stopped on aport due to power limit| A port identifier in the form of pethPsePortIndex from powerEthernetMiB| 1.3.6.1.2.1.105.0.1| Variable bindings: value: 1

6.9 LLDP
LLDP is a protocol used for topology mapping and discovery by having neighboring devices regularly exchange information on the interconnection links. The messages contain general information about the sender like MAC Address or Names.
LLDP message content sent by ROQSTAR device:

524F531B05000009
Chassis ID Type and Value| Locally assigned, FC:F8:B7:00:00:00
Port ID Type and Value| MAC address, FC:F8:B7:00:00:03
Port Description| P3
Time To Live| 40 seconds

Note: The source MAC address in the LLDP packets sent by ROQSTAR device is specific per port.
LLDP settings: Port
The name of the ROQSTAR device port being affected by the LLDP configuration.
receive only
Incoming LLDP frames are processed only.
receive & transmit
Incoming LLDP frames are processed and local LLDP frames are periodically transmitted using a 10 seconds interval.
Local Port
The local Port Name on which this neighbor device has been detected.
System Name
The name of the neighbour.
System Description The system description of the neighbour.
Chassis ID Type
The chassis id advertised by the neighbour.
Chassis ID Value
The chassis id advertised by the neighbour.
Port ID Type
The port ID type on the neighbour device the frame was sent from.
Port ID Value
The port ID value on the neighbour device the frame was sent from.
Port Description
The port description on the neighbour device the frame was sent from.
Age
The time in seconds since this neighbour has been detected.
6.10 Port Mirroring
Port Mirroring allows the duplication of network traffic seen on specific ports. The duplicated packets are sent out on another port. These “mirrored” packets reflect the actual traffic and can be captured using packet sniffer tools for debugging purposes.
For multiple ports either the incoming traffic, outgoing traffic or both can individually configured to be mirrored to a single destination port.
Port
The ROQSTAR device port to be mirrored or used as a destination port.
Traffic to mirror
Incoming: RX frames entering this port.
Outgoing: TX frames leaving this port.
Destination
The port where mirrored packets are copied to. Only one port may be configured as destination port.
Note:

• The destination port can not be used as a mirrored port.
• Do not attach another ROQSTAR device to the destination port.

Factory Default Settings

System identification| • description: “description”
• contact: “contact”
• location: “location”
---|---
DNS Client| • disabled
Files| • no files present
Ethernet Ports| • All ports are enabled, Auto Negotiation
• Monitoring via ITxPT xstatus is disabled
VLAN| • disabled
IP Interfaces, DHCP
Client| • IP address 192.168.1.1, subnet mask 255.255.255.0
• IP Forwarding, Proxy ARP disabled
• DHCP Client disabled
QoS| • disabled
• default PCP: 0
Port Mirroring| • disabled
LLDP| • enabled
Spanning Tree| • RSTP is enabled
• Bridge Priority 32768
DHCP Servers| • disabled
PoE| • enable PoE: true on all ports
• limit class: class 4
• nominal power limit: Class based
• priority: low
• ITxPT xstatus: disabled
NTP| • disabled
Remote Logging| • disabled
SNMP| • SNMP v1, v2c and v3 are enabled
• no SNMPv3 user accounts
• read community: public
• write community: private
SNMP Traps| • disabled
NAT| • disabled
User accounts| • user name: admin
• password: password

Software User Manual – ROQSTAR Gigabit
Managed Ethernet Switches
2022-08-16

References

• TRONTEQ - Ethernet Switches für ÖPNV
• TRONTEQ • Ethernet Switches for Public Transport

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>