There might be a connection loss or integration issue with the third-party monitoring tool. Try disabling the Traffic Monitoring tool to discard this could be the reason and test it one more time.

Copper SFP 10/100/1000 supports a maximum distance of 100 meters.

The traffic monitoring function is enabled when your switch ports are flooding with broadcast, multicast, and unknown unicast (also referred to as Destination Look-up Failure or DLF) packets and want to block the ports. Third-party monitoring tools may be considered as threats and present connection loss or integration issues. 

No. Only one feature can be enabled at a time.

The Loop Detection feature in Volktek switches detects a loop in the network, blocks the port causing the loop and avoids degradation of network performance.

A Switching Loop occurs in a network when there are more than one Layer 2 (OSI model) paths between two endpoints.  For example, multiple connections between two network switches or two ports on the same switch connected to each other will create a loop and result in a down network situation.

1.  Install a larger network cabinet for proper airflow and heat dissipation.
2.  Avoid installing cables in front of switch and network cabinet air vents.
3.  In case of a fully-enclosed cabinet, use exhaust fans and perforated walls or doors to facilitate air flow.

Username: admin
Password: admin 

1. Managed Switches
    - GUI
    - Console and
    - Telnet
2. Lite-Managed Switches
    - GUI
3. Un-managed switches
    - No​

192.168.0.254

Role 1:  Bind Deny Profile (The port only denies the specific multi-cast address traffic, it can receive other traffic)
Role 2:  Bind Permit Profile (The port is only permitted to receive the specific multi-cast address traffic, it cannot recieve other traffic)
Role 3: No Bind Any Profile (The port is a general port to receive the all multi-cast address traffic when the client sends out the associated IGMP report packets).
Answer:  You can bind deny and permit profile at a time for any specific port
The example below shows the rules to drop or allow any multi-cast IP

Eg: You create 2 profiles and bind under port 1
      - Profile 1 with group 227.1.1.1 ~ 227.1.1.100 => Type “Deny”
      - Profile 2 with group 227.1.1.200 ~ 227.1.1.250 =>type “Permit”

The switch will check Profile 1 first then turn to Profile 2
The results on port 1 are shown below
+  Multicast IP: 227.1.1.1~227.1.1.100 => drop
+  Multicast IP: 227.1.1.200~227.1.1.250 => pass
+  Other Multicast IP pass under profile 1, but drop under profile 2
If you initially commanded to add profile 2 to port 1 then Profile 1, the switch will check the rule on Profile 2 first, then turn to Profile 1.
The results on port 1 are shown below
Multicast IP: 227.1.1.200~227.1.1.250 => pass, as it initially check profile 2
Other Multicast IP => drop, in this case profile 1 has no meaning

For VLAN priority, you can configure by

• Port-based
• QinQ
• MAC-Based
• ALC

Role 1: Bind Deny profile(The port only deny the specific multicast address traffic, others can receive)
Role 2: Bind Permit profile (The port only permit to receive the specific multicast address traffic, others cannot receive)
Role 3: No bind any profile (The port is like a general port to receive the all multicast address traffic when client send out the associated the IGMP report packets).
Answer: You can bind deny and permit profile at a time for any specific port
And the example rule to drop or allow any multicast IP as below

Eg: You create 2 profile and bind under port 1
- Profile 1 with group 227.1.1.1 ~ 227.1.1.100 => Type “Deny”
- Profile 2 with group 227.1.1.200 ~ 227.1.1.250 =>type “Permit”

The SW will check Profile 1 first then turn to Profile 2
So results on port 1 as below
+  Multicast IP: 227.1.1.1~227.1.1.100 => drop
+  Multicast IP: 227.1.1.200~227.1.1.250 => pass
+  Other Multicast IP pass under profile 1, but drop under profile 2

If you have command initially add profile 2 to port 1 then Profile 1, the SW will check the rule on Profile 2 first then turn to profile 1
So results on port 1 as below
n  Multicast IP: 227.1.1.200~227.1.1.250 => pass, as it initially check profile 2
n  Other Multicast IP => drop, in this case profile 1 has no meaning

Question:
 I have one question about the IGMP Filtering permit behavior.
I can understand the “deny” behavior is “NOT to allow the port to receive the specific multicast address.
But what is the “permit” behavior? Can the port only receive the specific multicast address?
When the IGMP filtering enable, does it mean all ports follow the filtering table? What is the port IGMP Snooping behavior if it is not bind to the profile?

Answer: 
For IGMP filtering, you can config Maximum 10 profiles, each Profile you can config Maximum 10 multicast groups
The type rule
“Deny” means drop
“Permit” means allow

When you filter on specific port, it will check the Filtering table and only allow multicast in range “Permit”. Thus, you should filter for downlink ports only
When IGMP filtering enabled, it will activate the global config on SW
Once you add specific profile to interface, the filtering process will start
And from now on, IGMP Snooping will depend on IGMP filtering rule for multicast traffic allow or drop.

For IGMP snooping and MVR, user can set the multicast IP address, then SW will translate to MAC address. For static multicast MAC address, this is L2 function and use in special case when user understand and want to fix this MAC to specific ports.

(Web GUI is enabled by default setting)
- To Enable Web GUI through CLI:
   L2SWITCH(config)#http server port 80
- Disable Web GUI through CLI:
   L2SWITCH(config)#no web server
- Disable Web GUI through GUI: 
   Go to Maintenance >> choose Server and Disable​

This is a firmware related issue.  Please contact our Technical Support at support@volktek.com for the latest firmware.

This is a firmware related issue.  Please contact our Technical Support at support@volktek.com for the latest firmware.

This is a firmware related issue.  Please contact our Technical Support at support@volktek.com for the latest firmware.

The reset button on the switch is designed to restart the switch.  When it is pressed for over 5 seconds, the switch will load to factory default settings.

Security settings of public domain mail servers such as gmail or yahoo may cause this issue.  You need to enable those mail servers to allow less secured apps to work.  Email alarm features work best with private domains.

Commands to configure port isolation:

- MEN-3410(config)#interface fa1/0/1
- MEN-3410(config-if)#port-isolation ports 1,9-10,0
- 1 → Interface Id
- 9-10 → Uplink ports
- 0 → CPU

Through Web GUI:
Under VLAN menu, select port isolation.  Downlink ports should be isolated.
Select port ID & Egress Port (uplink ports) and click on 'Apply' to configure port isolation.
Port status ‘V’ indicates that port packet can be sent to that port.
Port status ‘-’ indicates that port packet cannot be sent to that port.

Commands to configure management VLAN

- MEN-3410(config)#interface eth0
- MEN-3410(config-if)#management vlan

Configure management VLAN through Web GUI
Under "General setting", you can change hostname, DHCP client enable/disable, configure static IP address, subnet mask, default gateway, and management VLAN.

Commands to change management IP:

  - MEN-3410(config)#interface eth0
  - MEN-3410(config-if)#ip address ABCD/M
  - MEN-3410(config-if)#ip address default-gateway ABCD

To enable DHCP client:

  - MEN-3410(config)#interface eth0
  - MEN-3410(config-if)#ip dhcp client enable

Change management IP through GUI:
Under "General Setting", you can change hostname, DHCP client enable/disable, configure static IP address, subnet mask, default gateway, and management VLAN.

This is a firmware related issue. Please contact our Technical Support at support@volktek.com for the latest firmware.

This is a firmware related issue. Please contact our Technical Support at support@volktek.com for the latest firmware.

Access Switches only support STP/RSTP

Access Switches do not support L3 functions as they are L2+ switches

14W

Users can downgrade or upgrade to Device-Lock firmware.  However, for security reasons, we don’t allow users to downgrade from Device-Lock firmware to a normal version.  If you require a downgrade, please contact our technical support team at support@volktek.com.

Device Lock is a customized feature designed to lock the switch to a particular network.  By enabling the Device Lock feature, the switch will function only in the configured domain and will not function in any other network, thereby reducing device thefts at the last mile.

Master, Slave, and Master-slave.

Enable the Device Lock feature to restrict unauthorized authentication.

One time.

No.

No.

No.

Contact Volktek at support@volktek.com with the following details:
  - Contact Person
  - Company Name
  - Switch Model
  - MAC
  - Serial No.
  - Distributor

Device Lock is a customized feature designed to lock the switch to a particular network. By enabling the device lock feature, the switch is locked to function only on the configured network. This feature significantly reduces device thefts at the last-mile.

It is necessary to have consistent links and authentications between SLAVE and MASTER in different deployment scenarios.  Please contact our technical support team if you encounter such problem at support@volktek.com.

Roles of the Device-Lock feature:
- Master:  Master is the authenticator which processes authentication request from SLAVE devices so that all ports are ready for port forwarding.
- Master-Slave:  This is a hybrid role. It sends authentication requests to the master device through uplink ports. Once it is authenticated, it will open downlink ports for the SLAVE device to become authenticated.
- Slave:  Slave is supplicant which gets authenticated together with the master device through specified uplink ports. Before a successful authentication, all downlinks are blocked, and no services are possible.

Benefits:
- Lock the switch to a specific network
- Switch will not function in any networks other than its configured network
- Reduces device thefts at the last mile