mpls_forwarding - bstoll/featureprofiles GitHub Wiki
Ensure that gRIBI programmed operations result in the correct traffic forwarding behaviour on the DUT.
- Configure DUT
port-1
to be connected to ATEport-1
, and DUTport-2
to be connected to ATEport-2
. ATEport-2
is configured to have an assigned address of198.18.2.2
, and the interface is enabled. - For label stack depths beginning at
baseLabel
, withnumLabels
addition labels:- Program a
LabelEntry
matching outer label 100 pointing to a NHG containing a single NH. - Program a
NextHopEntry
which points to192.18.2.2
pushing[baseLabel, ..., baseLabel+numLabels]
onto the MPLS label stack.
- Program a
- Run an MPLS flow matching label 100's forwarding entry and validate that is received at the destination port.
- Configure DUT
port-1
to be connected to ATEport-1
, and DUTport-2
to be connected to ATEport-2
. ATEport-2
is configured to have an assigned address of198.18.2.2
, and the interface is enabled. - For label stack depth beginning at
baseLabel
, withnumLabels
addition labels:- Program a IPv4Entry matcing IP Prefix
192.168.0.0/24
pointing to a NHG containing a single NH. - Program a
NextHopEntry
which points to192.18.2.2
pushing[baseLabel, ..., baseLabel+numLabels]
onto the MPLS label stack.
- Program a IPv4Entry matcing IP Prefix
- Run an IP flow matching IP Prefix
192.168.0.0/24
and validate that it is received at the destination port.
- gRIBI:
Modify()
-
ModifyRequest
AFTOperation
id
network_instance
-
op
:ADD
-
ip
*next_hop_group
-
mpls
*next_hop_group
-
next_hop_group
*id
*next_hop
-
next_hop
*id
*ip_address
*pushed_label_stack
ModifyResponse
-
AFTResult
id
status