Hashing per Vport

Hashing traffic per Vport ensures that the traffic on the same PON (or DSLAM) traverse the same Vport, and therefore, it is the same member link that this Vport is associated with. The Vport instances of the same Vport on another member links are irrelevant for QoS treatment.

The Vport for Nokia routers is referenced via inter-dest-string, which can be returned via RADIUS. For this reason, the terms hashing per inter-dest-string or hashing per Vport can be interchangeably used.

If the subscriber is associated with a Vport, hashing is automatically performed per inter-dest-string. In case that no such association exists, hashing defaults to per-subscriber hashing.

In specific cases, S-vlan tag can represent Vport. In such a case, per S-vlan hashing is needed. This can be implicitly achieved by the following configuration:

configure
  subscr-mgmt
    msap-policy <name>
      sub-sla-mgmt
  def-inter-dest-id use-top-queue 

configure
  port <port-id>
    ethernet
      access
        egress
    vport <name> 
      host-match dest <s-tag>   

Through this CLI hierarchy, S-tag is implicitly associated with the inter-dest-string and consequently with the Vport.

Note: LAG hashing parameters that are configured under config>lag, for example, per-link-hash, take precedence and are incompatible with the vport-hashing command.