Label | Description |
---|---|
Switch ports | Select to view the detailed information and connection status of the Nebula Device port in the past two hours, day, week or month. |
Click this button to reload the data-related frames on this page. | |
Edit | Select the ports you want to configure and click this button to configure Nebula Device settings on the ports, such as link aggregation, PoE schedule, LLDP and STP. |
Aggregate | Select more than one port and click this button to group the physical ports into one logical higher-capacity link. |
Split | Select a trunk group and click this button to delete the trunk group. The ports in this group then are not aggregated. A trunk group is one logical link containing multiple ports. |
Tag | Click this button to create a new tag or delete an existing tag. |
Reset | Click this button to reboot the PD (powered device) connected to the PoE port. Follow the prompt and click Confirm to reboot the PD connected to this port. This button is not available for an uplink port. |
Search | Specify your desired filter criteria to filter the list of Nebula Device ports. You can filter the search by selecting one or more Nebula Devices. Under Ports, you can search for multiple ports separated by a comma, or a range separated by a hyphen. For example: 1,2,4–6. |
Switch ports | This shows the number of ports on the Nebula Device. |
Export | Click this button to save the Nebula Device port list as a CSV or XML file to your computer. |
CRC alert icon | This prompt appears if CRC errors are detected in the port(s). Go to Switch > Monitor > Switches: Switch Details: Port Details for the details. See Switch Port Details for more information. |
Switch / Port | This shows the Nebula Device name and port number. If the port is added to a trunk group, this also shows whether it is configured as a static member of the trunk group (Static) or configured to join the trunk group through LACP (LACP). If the port is connected to an uplink gateway, it shows Uplink. Click details to display the port details screen. See Switch Port Details. |
Port name | This shows the descriptive name of the port. |
#Port | This shows the port number. |
LLDP | This shows whether Link Layer Discovery Protocol (LLDP) is supported on the port. |
Received broadcast packets | This shows the number of good broadcast packets received. |
Received bytes | This shows the number of bytes received on this port. |
Received packets | This shows the number of received frames on this port. |
Sent broadcast packets | This shows the number of good broadcast packets transmitted. |
Sent bytes | This shows the number of bytes transmitted on this port. |
Sent multicast packets | This shows the number of good multicast packets transmitted. |
Received multicast packets | This shows the number of good multicast packets received. |
Sent packets | This shows the number of transmitted frames on this port. |
Total bytes | This shows the total number of bytes transmitted or received on this port. |
Enabled | This shows whether the port is enabled or disabled. |
Link | This shows the speed of the Ethernet connection on this port. Auto (auto-negotiation) allows one port to negotiate with a peer port automatically to obtain the connection speed and duplex mode that both ends support. |
Connection | This shows the connection status of the port. • Gray (#888888): The port is disconnected. • Orange (#FF8900): The port is connected and is transmitting data at 10 or 100 Mbps. • Green (#64BE00): The port is connected and is transmitting data at 1000 Mbps (1 Gbps). • Azure (#0079FF): The port is connected and is transmitting data at 2.5 Gbps. • Violet (#8800FF): The port is connected and is transmitting data at 5 Gbps. • Blue (#004FEE): The port is connected and is transmitting data at 10000 Mbps (10 Gbps). When the port is in the STP blocking state, failed LACP negotiation state, or failed port authentication state, a blocked icon displays. Move the cursor over a time slot to see the actual date and time when a port is connected or disconnected. |
Auth. policy | This shows the name of authentication policy applied to the port. |
Allowed VLAN | This shows the VLANs from which the traffic comes is allowed to be transmitted or received on the port. |
PoE | This shows whether PoE is enabled on the port. |
RSTP | This shows whether RSTP is enabled on the port. |
Status | If STP/RSTP is enabled, this field displays the STP state of the port. If STP/RSTP is disabled, this field displays FORWARDING if the link is up, otherwise, it displays Disabled. |
Schedule | This shows the name of the PoE schedule applied to the port. |
Type | This shows the port type (Trunk or Access). |
PVID | This shows the port VLAN ID. It is a tag that adds to incoming untagged frames received on the port so that the frames are forwarded to the VLAN group that the tag defines. |
Tag | This shows the user-specified tag that the Nebula Device adds to the outbound traffic on this port. |
Storm Control | This shows whether traffic storm control is enabled or disabled on the port. |
Broadcast Limit (pps) | This shows the maximum number of broadcast packets the Nebula Device accepts per second on this port. |
Multicast Limit (pps) | This shows the maximum number of multicast packets the Nebula Device accepts per second on this port. |
DLF Limit (pps) | This shows the maximum number of Destination Lookup Failure (DLF) packets the Nebula Device accepts per second on this port. |
Loop Guard | This shows whether loop guard is enabled or disabled on the port. |
Network Analytic Alert | An amber alert icon displays if the NCC generates alerts when an error or something abnormal is detected on the port for the IPTV network. Move the cursor over the alert icon to view the alert details. |
IPSG protected | This shows whether IP source guard protection is enabled on this port. |
Received CRC packets | This shows the number of CRC (Cyclic Redundancy Check) errors received on the port. |
Number of IGMP Group | This shows the number of IGMP groups the port has joined. |
Management control | This shows if management control is enabled on this port. See Switch > Configure > Switch ports: Edit for more information. |
Click this icon to display a greater or lesser number of configuration fields. |
Label | Description |
---|---|
Switch ports | This shows the Nebula Device name and port number for the ports you are configuring in this screen. |
Name | Enter a descriptive name for the ports. |
Tags | Select or create a new tag for outgoing traffic on the ports. |
Port enabled | Select to enable or disable the ports. A port must be enabled for data transmission to occur. |
RSTP | Select to enable or disable RSTP on the ports. |
STP guard | This field is available only when RSTP is enabled on the ports. Select Root guard to prevent the Nebula Devices attached to the ports from becoming the root bridge. Select BPDU guard to have the Nebula Device shut down the ports if there is any BPDU received on the ports. Otherwise, select None. |
LLDP | Select to enable or disable LLDP on the ports. |
Link | Select the speed and the duplex mode of the Ethernet connection on the ports. Choices are 10M/Half Duplex, 10M/Full Duplex, 100M/Half Duplex, 100M/Full Duplex, 1000M/Full Duplex, Auto, 10M/AN, and 100M/AN (Gigabit connections only). |
Extended range | Select to enable or disable extended range. Extended range allows the port to transmit power and data at a distance of 250 meters. When enabled, the port’s PoE Power up mode is locked to 802.3at, and the port’s link speed is limited to 10M/Full Duplex. |
Media type | You can insert either an SFP+ transceiver or an SFP+ Direct Attach Copper (DAC) cable into the 10 Gigabit interface of the Nebula Device. Select the media type (SFP+or DAC 10G) of the SFP+ module that is attached to the 10 Gigabit interface. |
Port Isolation | Select to enable or disable port isolation on the ports. The ports with port isolation enabled cannot communicate with each other. They can communicate only with the CPU management port of the same Nebula Device and the Nebula Device’s other ports on which the isolation feature is not enabled. |
IPSG protected | Select to enable or disable IP source guard protection on the port. |
Auth. policy | This field is available only when you select Access in the Type field. Select the authentication policy type and name of the pre-configured authentication policy that you want to apply to the ports. See Switch > Configure > Authentication for more information on authentication policy type. See Authentication for more information on configuring authentication policy. Select Open if you do NOT want to enable port authentication on the ports. |
Bandwidth Control | Select to enable or disable bandwidth control on the port. |
Ingress | Specify the maximum bandwidth allowed in kilobits per second (Kbps) for the incoming traffic flow on the ports. |
Egress | Specify the maximum bandwidth allowed in kilobits per second (Kbps) for the out-going traffic flow on the ports. |
Loop guard | Select to enable or disable loop guard on the ports. The loop guard feature cannot be enabled on the ports that have Spanning Tree Protocol (RSTP, MRSTP or MSTP) enabled. |
Storm Control | Select to enable or disable broadcast storm control on the ports. |
Broadcast Limit (pps) | Specifies the maximum number of broadcast packets the Nebula Device accepts per second on the ports. |
Multicast Limit (pps) | Specifies the maximum number of multicast packets the Nebula Device accepts per second on the ports. |
DLF Limit (pps) | Specifies the maximum number of DLF packets the Nebula Device accepts per second on the ports. |
Type | Set the type of the port. Select Access to configure the port as an access port which can carry traffic for just one VLAN. Frames received on the port are tagged with the port VLAN ID. Select Trunk to configure the port as a trunk port which can carry traffic for multiple VLANs over a link. A trunk port is always connected to a Nebula Device or router. |
Management control | Select Enabled to configure the port as a management port. The default is Enabled. This allows the administrator to set the Nebula Device ports through which the device management VLAN traffic is allowed. Make sure to enable this for an uplink port to maintain connection with Nebula. |
VLAN type | This field is available only when you select Access in the Type field. None: This port is a regular access port and follows the device’s access port rules. Vendor ID based VLAN: Apply the Vendor ID based VLAN settings from Switch > Configure > Switch settings to this port. Voice VLAN: Apply the Voice VLAN settings from Switch > Configure > Switch settings to this port. For details on configuring Vendor ID based VLAN and Voice VLAN settings, see Switch Settings. |
PVID | A PVID (Port VLAN ID or native VLAN) is a tag that adds to incoming untagged frames received on a port so that the frames are forwarded to the VLAN group that the tag defines. Enter a number between 1and 4094 as the port VLAN ID. |
Allowed VLANs | This field is available only when you select Trunk in the Type field. Specify the VLANs from which the traffic comes. You can then transmit or receive traffic on the ports. See Set Up Dynamic VLAN With RADIUS (for Nebula Switches only) for the steps in setting up dynamic VLAN with RADIUS. See Monitor Dynamic VLAN Using Event Logs (for Nebula Switches only) for more information on monitoring dynamic VLANs using event logs. |
PoE Settings | |
PoE | Select Enabled to provide power to a PD connected to the ports. |
PoE schedule | This field is available only when you enable PoE. Select a pre-defined schedule (created using the Switch > Configure > PoE schedule screen) to control when the Nebula Device enables PoE to provide power on the ports. You must select Unschedule in the PoE schedule field before you can disable PoE on the ports. If you enable PoE and select Unschedule, PoE is always enabled on the ports. The Nebula Device will follow the PoE schedule even when the Nebula Device is not connected to NCC. Click Edit to go to Switch > Configure > PoE schedule screen to create a new PoE schedule. |
PoE priority | When the total power requested by the PDs exceeds the total PoE power budget on the Nebula Device, you can set the PD priority to allow the Nebula Device to provide power to ports with higher priority. Select Low to set the Nebula Device to assign the remaining power to the port after all critical and medium priority ports are served. Select Medium to set the Nebula Device to assign the remaining power to the port after all critical priority ports are served. Select Critical to give the highest PD priority on the port. |
Power up mode | Set how the Nebula Device provides power to a connected PD at power-up. 802.3at – the Nebula Device supports the IEEE 802.3at High Power over Ethernet standard and can supply power of up to 30W per Ethernet port. IEEE 802.3at is also known as PoE+ or PoE Plus. An IEEE 802.3at compatible device is referred to as Type 2. Power Class 4 (High Power) can only be used by Type 2 devices. If the connected PD requires a Class 4 current when it is turned on, it will be powered up in this mode. 802.3af – the Nebula Device follows the IEEE 802.3af Power over Ethernet standard to supply power to the connected PDs during power-up. Legacy – the Nebula Device can provide power to the connected PDs that require high inrush currents at power-up. Inrush current is the maximum, instantaneous input current drawn by the PD when first turned on. Pre-802.3at – the Nebula Device initially offers power on the port according to the IEEE 802.3af standard, and then switches to support the IEEE 802.3at standard within 75 milliseconds after a PD is connected to the port. Select this option if the Nebula Device is performing 2-event Layer-1 classification (PoE+ hardware classification) or the connected PD is NOT performing Layer 2 power classification using Link Layer Discovery Protocol (LLDP). Force 802.3at – the Nebula Device provides PD Wide Range Detection (WRD) with power of up to 33 W on the port without performing PoE classification. Select this if the connected PD does not comply with any PoE standard. 802.3bt – the Nebula Device follows the IEEE 802.3bt standard to supply power of up to 60 W per Ethernet port to the connected PDs at power-up. Pre-802.3bt – the Nebula Device offers power on the port according to the IEEE 802.3bt standard. Select this if the connected PD was manufactured before the IEEE 802.3bt standard was implemented on September 2018, but requires power between 33 W and 60 W. IEEE 802.3bt is also known as PoE++ or PoE Plus Plus. |
Auto PD recovery | Select to enable or disable automatic PD recovery on the port. Automatic PD recovery allows the Nebula Device to restart a Powered Device (PD) connected to the port by turning the device on and off again. |
Detecting mode | Select LLDP to have the Nebula Device passively monitor current status of the connected Powered Device (PD) by reading LLDP packets from the PD on the port. Select Ping to have the Nebula Device ping the IP address of the connected Powered Device (PD) through the designated port to test whether the PD is reachable or not. |
Action | Set the action to take when the connected Powered Device (PD) has stopped responding. Select Reboot-Alarm to have the Nebula Device send an SNMP trap and generate a log message, and then turn off the power of the connected PD and turn it back on again to restart the PD. Select Alarm to have the Nebula Device send an SNMP trap and generate a log message. |
Neighbor IP | Set the IPv4 address of the Powered Device (PD) connected to this port. If Detecting Mode is set to Ping and the PD supports LLDP, the connected PD’s IPv4 address to which the Nebula Device sends ping requests is displayed automatically. |
Polling Interval | Specify the number of seconds the Nebula Device waits for a response before sending another ping request. For example, the Nebula Device will try to detect the PD status by performing ping requests every 20 seconds. |
Polling Count | Specify how many times the Nebula Device resends a ping request before considering the PD unreachable. |
Resume Polling interval (sec) | Specify the number of seconds the Nebula Device waits before monitoring the PD status again after it restarts the PD on the port. |
PD Reboot Count | Specify how many times the Nebula Device attempts to restart the PD on the port. The PD Reboot Count resets if any of the following conditions are true: • The Nebula Device successfully pings the PD. • You modify any Auto PD Recovery settings and apply them. • The Nebula Device restarts. |
Resume Power Interval (sec) | Specify the number of seconds the Nebula Device waits before supplying power to the connected PD again after it restarts the PD on the port. |
IPTV Setting | |
Overwrite advanced IGMP setting | Select ON to overwrite the port’s advanced IGMP settings (configured in the Configure > Advanced IGMP screen) with the settings you configure in the fields below. Otherwise, select OFF. |
Leave Mode | Select Immediate Leave to remove this port from the multicast tree immediately when an IGMP leave message is received on this port. Select this option if there is only one host connected to this port. Select Normal Leave or Fast Leave and enter an IGMP normal/fast leave timeout value to have the Nebula Device wait for an IGMP report before the leave timeout when an IGMP leave message is received on this port. You need to specify how many milliseconds the Nebula Device waits for an IGMP report before removing an IGMP snooping membership entry when an IGMP leave message is received on this port from a host. In Normal Leave mode, when the Nebula Device receives an IGMP leave message from a host on a port, it forwards the message to the multicast router. The multicast router then sends out an IGMP Group-Specific Query (GSQ) message to determine whether other hosts connected to the port should remain in the specific multicast group. The Nebula Device forwards the query message to all hosts connected to the port and waits for IGMP reports from hosts to update the forwarding table. In Fast Leave mode, right after receiving an IGMP leave message from a host on a port, the Nebula Device itself sends out an IGMP Group-Specific Query (GSQ) message to determine whether other hosts connected to the port should remain in the specific multicast group. This helps speed up the leave process. |
Maximum Group | Select Enable and enter the maximum number of multicast groups this port is allowed to join. Once a port is registered in the specified number of multicast groups, any new IGMP join report received on this port will replace the earliest group entry in the multicast forwarding table. Otherwise, select Disable to turn off multicast group limits. |
IGMP filtering profile | An IGMP filtering profile specifies a range of multicast groups that clients connected to the Nebula Device are able to join. Select the name of the IGMP filtering profile to use for this port. Otherwise, select No Select to remove restrictions and allow the port to join any multicast group. |
Fixed router port | Select Auto to have the Nebula Device use the port as an IGMP query port if the port receives IGMP query packets. The Nebula Device forwards IGMP join or leave packets to an IGMP query port. Select Fixed to have the Nebula Device always use the port as an IGMP query port. This helps prevent IGMP network topology changes when query packet losses occur in the network. |