COMTREND GCA-7000 Ethernet Over Coax Adapter User Manual

: June 6, 2024
: COMTREND

COMTREND GCA-7000 Ethernet Over Coax Adapter

Product Information

Front Panel LED Indicators

LED	COLOR	MODE	Description
Power	Green	On	The G.hn Coaxial Adapter is powered on
Off	Off	The G.hn Coaxial Adapter is powered off or faulty
Connection	Green	On	The current connection (line rate) is more than

Front Panel Buttons

Security| Press for more than 2 seconds for enabling data encryption in GCA-7000’s. Please refer to GCA-7000_QIG.pdf for details.
---|---
Reset| Press for less than 10 seconds to reset the device.
Press for more than 10 seconds to restore factory defaults.

G.hn/Coax Setup

Logging In

Perform the following steps to login to the web user interface.
STEP 1: Start the Internet browser and input the default IP address for the device in the Web address field. For example, if the default IP address is 192.168.0.5, type http://192.168.0.5
STEP 2: A dialog box will appear, such as the one shown below. Input the default Authentication Password.
Authentication Password: admin

Logging In

Click the OK button to continue.
Note:
The Factory Reset password is: betera

G.hn Interface

Basic Configuration

MAC Address Displays the MAC address of the device.
Device ID Device ID of this node.
Domain Name string of all nodes in the network.
Force node Type force the modem to have a particular role (END POINT or DOMAIN MASTER or AUTOMATIC)
Node Type Shows the current status of the device.
G.hn profile of all nodes in the network: select which G.hn profile that must be applied to the network (COAX 100MHz and COAX 200MHz).

NDIM Configuration

NDIM mode set to Automatic for enabling automatic DOD selection functionality and set to Manual for manual configuration of DOD.
Domain ID (DOD) manually set the DOD number from 1 to 15 to use a different preamble seed than the default 0.

Encryption Configuration via WEB UI

Pairing Password used for authentication. Write a custom password to manually create a secure domain.

Available Connections

In this tab table, all the available G.hn connections are presented. Remote node DID and MAC address; transmission and reception physical speeds.

IP Interface

IP Config

In the IP configuration tab of one G.hn node, the IPv4 and IPv6 settings can be read and changed.
IPv4 subsection:

DHCPv4 enabled: in the case of choosing ”NO” IP configuration in the following parameters, the IPv4 Address, Subnet Mask, Default Gateway and DNS should be configured; fill these fields in. In the case of choosing “YES” they will be filled automatically when the configuration is received from the DHCPv4 server.
IPv4 address/netmask: IPv4 address / netmask of this device.
Default Gateway: IPv4 gateway to connect the device to other LAN segments.
DNS: Domain Name Server IP (IPV4).
Additional address #1/2: additional fixed IPv4 addresses that will always be configured at boot time.

IPv6 subsection:

DCHPv6 enabled: in the case of choosing ”NO” IP configuration in the following parameters, the IPv6 Address, prefix, Default Gateway and DNS should be configured; fill these fields in. In the case of choosing “YES” they will be filled automatically when the configuration is received from the DHCPv6 server.
IPv6 Address / prefix: IPv6 address / prefix of the device to read the node’s DHCPv6 address in case the DHCPv6 is enabled.
Default Gateway: IPv6 gateway to connect the node to other LAN segments.
DNS: Domain Name Server IP (IPV6).
Additional address #1/2/3/4: additional fixed IPv6 addresses that will always be configured at boot time.
IPv6 Link-Local Address: to read the node’s Link Local address.
IPv6 SLAAC address: IPv6 address, automatically obtained by means of the SLAAC mechanism.

NTPv4/v6 subsection:

NTPv4/v6 client enabled: Enable/disable NTP client.
Resynchronization time: Configure re-synchronization interval time in minutes.
NTP IPv4/v6 address: Hostname or IP (IPv4 or IPv6) of NTP server.

Ethernet Interface

The Ethernet table shows the status & Info of the Ethernet interface; including Interface, Speed, Duplex, Interface Type, Mode, and Internal PHY & Link.

Power Saving
Ethernet power saving can be disabled, enabled by Ethernet link or enabled by Ethernet activity; idle timer can be configured as well.

Device Interface

Hardware Information

In this tab, basic information such as MAC Address and Serial Number of the selected node is shown.

Software Information

Shows the FW version and system uptime.

Security

The nodes in the network: to change the configuration password string from the default (“admin”) to another; decided by the user.

SW Update

Current loaded firmware version is shown. Any flash section can be upgraded; the first flash section should be selected and after clicking on the “OK” button the corresponding file should be chosen. Usually, a reboot should be performed afterwards to make sure the changes are effective.
The protocol is by FTP client or TFTP client. L2 is proprietary and is reserved for future use.

HTTP SW Update

STEP 1: Enter the path and filename of the firmware image file in the Software File Name field or click the Browse button to locate the image file.
STEP 2: Click the OK button once to upload and install the file.

NOTE 1: The update process will take about 2 minutes to complete. The device will reboot and the browser window will refresh to the default screen upon successful installation. It is recommended that you compare the Software Version on the Device Interface screen with the firmware version installed, to confirm the installation was successful.
NOTE 2: The Power LED indicates the status of firmware update progress. Please DO NOT power off the device when Power LED is flashing or the device will be damaged.

Multicast Interface

MCAST Configuration

In the MCAST Configuration tab of “My Network”, IGMP snooping and MLD features can be enabled or disabled. Also, IGMP multicast IP addresses ranges which the G.hn PLC network will sniff; can be configured.

IGMP Snooping: Enable or Disable.
MLD Snooping: Enable or Disable.
IGMP/MLD broadcast report (allowed): set to NO for enabling reports dropping until the video source is detected, this is a recommended setting when IGMP/MLD is enabled. Set to YES for broadcasting reports until the video source is detected; this implies the multicast video stream is sent as broadcast and it is the recommended state when IGMP/MLD is disabled.
IGMP/MLD broadcast report mode: Report broadcast forwarding behavior when the MCAST.GENERAL.REPORT_BROADCAST_ALLOWED is enabled.
- If 0 then broadcast reports only when the video source is unknown.
- If 1 then broadcast reports always.
- If 2 then broadcast reports always if IGMPv3 and only when video source is unknown in others.
  The term ‘video source’ refers to the node whose Ethernet port is connected directly to the Home Gateway.
Filter unknown multicast traffic: Enables the Multicast Filtering feature.
If enabled, all the unsolicited multicast traffic will be blocked.
In IPv4 multicast traffic, only the traffic between the IP ranges defined in the
MCAST.GENERAL.IGMP_IP_RANGES_DEF and the packets are unsolicited, these packets will be dropped.
Warning: This feature implies a higher CPU load, so it is advisable to enable it only in the Video Source. Only 100 Kbps of broadcast traffic could be managed in this mode.

IGMP Multicast Ranges Configuration: 4 multicast IP address ranges can be configured defining the minimum and maximum IP addresses of each range. Only multicast traffic within these ranges will be processed.
Broadcast Suppression: Maximum throughput allowed without suppressing broadcast traffic. The accuracy of this parameter depends on size of packets (big packets -> more accuracy). Value 0 deactivates this functionality.

QoS Configuration

In the QoS configuration tab, the packet classifier can be managed to define a QoS rule for incoming Ethernet traffic, and assign a priority to be used in the G.hn network. Press the “Ok” button to load the newly configured settings:

QoS CRITERION: a general criterion can be chosen among “None” (no QoS), “Custom” and “802.1p”.
Type of Frame: with this parameter the type of Ethernet traffic being transmitted by the G.hn network should be selected. Based on this parameter, the internal offsets in the system are adjusted. In the QoS tab, Ethernet frame offsets should set a counting number as they appear in the sniffer SW (for instance, the same field will be in a different position if normal Ethernet frames or 802.1Q tagged frames exist).
Packet detection 1: first packet detection rule can be configured (offset, bitmask and pattern). Packets which accomplish it will be sent to the classification module.
Packet detection 2: if second packet detection is also enabled, both, first and second detection criteria must be accomplished to pass packets to the classification module.
Packet classification: up to 8 classification rules can be defined in this section for packets which have previously been correctly detected. For 802.1p only priorities can be managed, offset, bitmask and pattern are predefined to sniff the PCP field.
Default priority: select default priority; which will be applied to non classified incoming packets. Priority 7 is the highest. Priority 0 is the lowest.
TCP Ack Class in IPv4: Mapping TCP ACK (IPv4) to a Class Value.
TCP Ack Class in IPv6: Mapping TCP ACK (IPv6) to a Class Value.
ARP Class: Mapping ARP to a Class Value.
DSCP Class: Mapping of each DSCP value to a Class Value.

As shown above, if QoS criterion: DSCP, all other options are grayed out, and follow the QoS rules below. According to G.9960 specs, the priority mapping recommended by [IEEE 802.1D] sub clause 7.7.3 is presented in Table III.1. for four priority queues.

PCP	Priority	Acronym	Traffic Types
1	0 (Third)	BK	Background
0	1 (lowest)	BE	Best Effort
2	2 (lowest)	EE	Excellent Effort
3	3 (Third)	CA	Critical Applications
4	4 (second)	VI	Video, < 100 ms latency and jitter
5	5 (second)	VO	Voice, < 10 ms latency and jitter
6	6 (highest)	IC	Internetwork Control
7	7 (highest)	NC	Network Control

In summary, the sequence of priority queue, (7,6) > (5,4) > (3,0) > (2,1)

G.hn spectrum Interface

Notches

In this tab a table with all configured Notches of selected node will be shown. The table is composed of next columns for every notch: Notch Number, Type of notch, Start Frequency (KHz), Stop Frequency (KHz), Depth (in dB).
The first 13 notches (Regulation) are Read Only, RO, in the system and they can be neither removed nor modified. The next 40 notches (Vendor) are defined by the vendor using SDK and they are also RO. The last 10 notches (User) are R/W and they can be added/removed by user using this tool.

To add new notches the user should fill the “Add a new User Notch” fields, setting Start and Stop frequencies in KHz and depth in dB of notch and then press the “Ok” button. They will be added in first User free position from number 0 to 9. (If successful, you can see a record in the Type column).
To remove a User Notch, the “Remove a User Notch” section should be used, setting notch number to be removed from 0 to 9 and pressing the “Ok” button.

Log File Interface

Log file Interface

Log File

In the Log File configuration the following settings can be read, and changed by clicking on the corresponding “OK” button for the selected node:

Enable Log File: set to YES for enabling Log File functionality in the node and set to NO for disabling it.
Data Capture: Interval sets the interval of time in seconds to capture data.
FTP Server URL: configures the URL for the remote FTP server where the files will be uploaded.
FTP Server Login: configures the user for the FTP server.
FTP Server Password: configures the password for the FTP server.
Upload to Server Interval: sets the interval of time in minutes to send the captured file to the remote server.

TR069

TR069 Configuration

ACS URL: URL for the CPE to connect to the ACS using the CPE WAN Management Protocol. This parameter MUST be in the form of a valid HTTP or HTTPS URL. An HTTPS URL indicates that the ACS supports SSL. The “host” portion of this URL is used by the CPE for validating the certificate from the ACS when using certificate-based authentication.
Username: Username used to authenticate the CPE when making a connection to the ACS using the CPE WAN Management Protocol. This username is used only for HTTP-based authentication of the CPE.
Password: Password used to authenticate the CPE when making a connection to the ACS using the CPE WAN Management Protocol. This password is used only for HTTP-based authentication of the CPE.
PeriodicInformEnable: When set to YES, the modem should periodically send information to the ACS using the Inform method call.
PeriodicInformInterval: The duration in seconds of the interval in which the CPE MUST attempt to connect with the ACS and call the Inform method.
Conn Req Username: Username used to authenticate an ACS making a Connection Request to the modem.
Conn Req Password: Password used to authenticate an ACS making a Connection Request to the modem.

STUN Configuration

STUNEnable: Enables(YES) or disables(NO) the use of STUN. This applies only to the use of STUN in association with the ACS to allow UDP Connection Requests.
STUNServerAddress: Host name or IP address of the STUN server to send Binding Requests if STUN is enabled via the STUN_ENABLE parameter. If it is an empty string and STUN_ENABLE is YES, the modem should use the address of the ACS extracted from the host portion of the ACS URL.
STUNServerPort: Port number of the STUN server to send Binding Requests if STUN is enabled via STUN_ENABLE. By default, this should be equal to the default STUN port, 3478.
STUNUsername: If it is not an empty string, the value of the STUN USERNAME attribute to be used in Binding Requests (only if message integrity has been requested by the STUN server).If it is an empty string, the modem will not send STUN Binding Requests with message integrity.
STUNPassword: The value of the STUN Password to be used in computing the MESSAGE-INTEGRITY attributes to be used in Binding Requests (only if message integrity has been requested by the STUN server).
STUNMaxKeepAlivePeriod: If STUN is enabled, the maximum period, in seconds, that STUN Binding Requests must be sent for the purpose of maintaining the binding in the Gateway. This applies specifically to Binding Requests sent from the UDP Connection Request address and port. A value of -1 indicates that no maximum period is specified.
STUNMinKeepAlivePeriod: If STUN is enabled, the minimum period, in seconds, that STUN Binding Requests can be sent for the purpose of maintaining the binding in the Gateway. This limit applies only to Binding Requests sent from the UDP Connection Request address and port, and only those that do not contain the BINDING-CHANGE attribute. This limit does not apply to retransmissions following the procedures defined in [RFC3489].

Advanced Interface

Hardware Reset: Click on this button to perform a reboot in the node.
Factory Reset: Input the password: betera and click the OK button to perform a factory reset. The current configuration will be lost.