Configuration/Uplink Video Bridged Help

Add or modify the data displayed, then click the Apply button.

Port Displays all the Ethernet ports or link aggregated groups on the uplink card.

Logical Type

Uplink 802.1Q: An uplink bridge uses one bridge interface in a VLAN as a default, and traffic from all other interfaces exits the system from this interface. As the default interface, packets entering the system on this interface do not have their source MAC addresses learned and associated with this interface. Traffic coming into this uplink interface is sent to the interface where the address has been learned. If the frame is a broadcast, it is filtered, unless it is an ARP or DHCP message that meets some special criteria. Unicasts received on an uplink port are forwarded to the downlink where the MAC address was learned.

Uplink bridge interfaces require an additional bridge-path configuration to set a default path for either a specific VLAN or globally for the system onto the uplink bridge. If an uplink is missing this configuration, traffic will not flow across the asymmetric VLAN. If RSTP (Rapid Spanning Tree Protocol, IEEE 802.1W) option is selected on two uplink bridge interfaces, it builds two links between device and uplink router. These two links are redundant to each other, if an active link fails, the redundant link will provide backup paths.

MVR: MVR allows video subscribers to share one multicast VLAN in the network while remaining in their own unique subscriber VLAN. MVR can send packets received from the multicast headend device on one MVR VLAN to one or more than one subscriber VLAN IDs.

Remote Spanning Tree Protocol (RSTP)

Check to enable RSTP.

RSTP (802.1W) is an evolution of the Spanning Tree Protocol (STP, IEEE 802.1D). STP links network segments and eliminates one of the difficulties of configuring bridge topologies - bridge loops. There still can only be one active path. Once RSTP is configured for a bridged network the Spanning Tree Algorithm (STA) analyzes the network and determines which links should be active or not. The STA defines the links by configuring the ports.

In the bridged network the root bridge is selected. The STA sends out messages - Bridge Protocol Data Units (BPDU) - to determine the least cost path to the root bridge. From this analysis the port roles are determined.

Q-in-Q

Check to enable Q-in-Q. The IEEE 802.1 Q-in-Q VLAN tagging expands the VLAN space in the Ethernet frame to support the tagging of previously tagged packets. This second tag (SLAN) creates a "double-tagged" Ethernet frame.

QoS

Check to enable.

VLAN Tagging and Translation

Type

Untagged, single tagged, or double-tagged.

Tagged bridging: Tagged bridges forward traffic based on the logical VLAN ID number. This tagging allows the segregation of a single Ethernet network into multiple virtual network segments.

Untagged bridging: Untagged bridges forward traffic based on MAC addresses but do not further segregation traffic. Traffic is broadcast over the Ethernet port and is either accepted or rejected based on the destination MAC address. In other words, there is no VLAN tagging; all ports are learning and forwarding without restriction without broadcast suppression. Forwarding to a default port is not allowed.

Double-tagged: Double tagging expands the VLAN space in the Ethernet frame, so that you may further segregate traffic. The packet is differentiated by VLAN ID and SLAN ID. This second tag gives a whole other layer, so you can have VLAN 100 which may be a department in a global organization, and VLAN 100, SLAN 100 be one group within that department.

VLAN ID

The Virtual LAN Identifier for the IP Interface. If the VLAN ID specified is non-zero, all traffic destined to this interface should be configured with this VLAN ID.

Q-in-Q

S-TAG TPID

Identifies the type of VLAN ID used. Typically set to 8100.

S-TAG ID

Specifies the SLAN ID assigned to an Ethernet frame.

QoS

VLAN CoS

Specifies the value loaded into the COS field of the VLAN header when an untagged packet received on this interface is tagged (VLAN ID inserted) for bridging. Value range is 0 to 7. Default is 0.

S-Tag CoS

The s-tag COS to be used when doing s-tag insertion.

Default is 0

Outgoing CoS Option

Determines COS setting on packets bridged out this interface

disable - COS setting is untouched.

all - COS will be set to Outgoing CoS Value.

Default is disable

Outgoing CoS Value

The COS value loaded into outgoing tagged packets.

Applicable only if interface sends tagged packets and Outgoing CoS Option is set to all.

S-Tag Outgoing CoS Option

Determines s-tag COS settings on packets bridged out this interface:

disable - s-tag COS setting just passed as Rxed.

all - s-tag COS will be set with Outgoing CoS Value

Default is disable

S-Tag Outgoing CoS Value

The s-tag COS value loaded into outgoing tagged packets.

 Applicaple only if interface sends S-tagged packets and S-Tag Outgoing CoS Option is All.

Default is 0

Packet Rule Group

Ingress Group Index

The index number for packet-rule-record(s) when adding multiple filters for ingress interfaces.

Egress Group Index

The index number for packet-rule-record(s) when adding multiple filters for egress interfaces.

Static paths

Note: Static paths are supported on Uplink, TLS, Rlinks, and Intralinks.
 

Unicast Aging

Unicast aging period in tenths of seconds for the specified VLAN. After the specified aging period is met, the VLAN address is deleted from the routing table. A value of 0 indicates that aging is turned off. Maximum value is 2147483647 tenths of seconds, which equates to approximately 2485.51 days.

Multicast Aging

The period in tenths of seconds for the specified VLAN. After the specified aging period is met, the VLAN address is deleted from the routing table.

A value of 0 indicates that aging is turned off. Maximum value is 2147483647 tenths of seconds, which equates to approximately 2485.51 days.

IGMP Query Interval

This number indicates both the query interval (how often (in seconds) IGMP query values are injected in the video stream. Usually, this value is less than one half the multicast aging period. For example, if the Multicast Aging is 150 seconds, the IGMP Query Interval could be 60.

IGMP Custom Address

If your network checks for source IP addresses, the default proxy IP address can be configured to a custom IP address. If you enter an IP address here, the source IP address of the IGMP membership reports will be sent with this address. If you don't specify a custom address, the system will default to a source IP of 10.10.10.1

Flap Control

Enables or disables Flap Control in the Bridge Filter Table.

Values:

Disable: turns Flap Control mode off.

Enable applies a hold time of 60 seconds before allowing addr/IP to be moved to a new port.

Fast indicates that as a MAC address comes into the system from one source and then is seen from another source, the MAC address table is purged from the first source and replaced with the second source without delay or restriction. If this behavior is not desired, the Flap Mode can be configured to disabled or default.

Default: indicates 'Don't Care' and defaults to disabled or enable as set by another entry.

Loop Prevention

Bridge loop issue prevention can be configured on both asymmetrical and TLS bridges to resolve certain incorrect MAC address behaviors.

None: no loop prevention.

BlockAsym: blocks a learning bridge if flap is detected between it and an uplink bridge. Setting this on an an uplink bridge interface on the VLAN ID will block the downlink when incorrect MAC address behavior occurs in a uplink/downlink configuration. When incorrect MAC address behavior involves two downlinks, the bridge interface on the VLAN ID for both downlinks is blocked.

BlockAll: incorporates blockAsym but it also blocks a learning bridge if it flaps against another learning bridge.

Bridge Flags

This setting configures IGMP snooping with proxy reporting. This applies to bridged video. IGMP snooping with proxy reporting reduces traffic between the system and the upstream multicast headend device by changing the behavior of the system for more efficient tracking and grouping of JOIN and LEAVE requests.

None: IGMP Snooping with Proxy reporting is disabled. For IGMP snooping without proxy reporting enabled, join requests from downstream hosts are simply forwarded by the system to the multicast headend device.

ProcessJoinAndLeave: Enable or disable the system to send Join and Leave requests to the Multicast router. For IGMP snooping with proxy enabled, join requests from downstream hosts are not forwarded by the device to the multicast headend device in the network, but are tracked by the device in an information table where hosts are organized into a group. When a host sends a join request that is the first join request of the group, the system terminates the join request from the host, originates new join request and sends it to the multicast headend device in the network along with the default IP address of 10.10.10.1 and a MAC address.

When a host sends a leave request that is the last leave request of the group, the system terminates the leave request from the host and originates a new leave request and sends it to the multicast headend device in the network. All leave requests, regardless of whether they are the last leave request of the group, or any earlier leave requests, are terminated on the device.

In this way, the multicast headend device starts and stops video transmission by processing requests sent directly from the device and not from downstream hosts. Proxy is when the device sends join and leave requests to the network and snooping is when the system monitors the join and leave requests from hosts to the system.

RespondToQuery: Allow or not allow the system to send query reports to the Multicast router.

UseBridgeIpAddress: When IGMP snooping with proxy reporting is enabled on a static uplink bridge, the default source IP address in the Ethernet packet sent from the bridge is 10.10.10.0. In certain cases there may be a need to replace 10.10.10.1 with the bridge IP address. For example when a router in the network has implemented Reverse Path Forwarding and expects an IP address in the subnet of the router. Another example is when different IP addresses in the same subnet are inserted for different SLMS devices for the purposes of debugging.

To save the configuration, click the Apply button.

 

May 14, 2012