-
Notifications
You must be signed in to change notification settings - Fork 207
aigp_test
Github Action edited this page Apr 1, 2026
·
1 revision
This test validates the support for AIGP ensuring the following use-cases
- The attribute can be transmitted and received between two bgp peers
- The propagation of the attribute can be controlled both per bgp neighbor and peer-group
- The attribute can be modified as needed with a policy on both import and export direction on a BGP peer
+---------+ Lag1[eBGP] +---------+ LAG2 [iBGP] +---------+
| ATE |=========================| DUT 1 |=========================| DUT 2 |
+---------+ +---------+ +---------+
| Device | vlan 10 | vlan 20 | vlan 30 | vlan 40 |
|---|---|---|---|---|
| DUT 1 | 198.51.100.1/30 | 198.51.100.5/30 | 198.51.100.9/30 | 198.51.100.13/30 |
| ATE | 198.51.100.2/30 | 198.51.100.6/30 | 198.51.100.10/30 | 198.51.100.14/30 |
| Device | vlan 10 | vlan 20 | vlan 30 | vlan 40 |
|---|---|---|---|---|
| DUT 1 | 2001:db8::1/126 | 2001:db8::5/126 | 2001:db8::9/126 | 2001:db8::13/126 |
| ATE | 2001:db8::2/126 | 2001:db8::6/126 | 2001:db8::10/126 | 2001:db8::14/126 |
| Device | vlan 10 IPV4 | vlan 10 ipv6 | vlan 20 IPV4 | vlan 20 ipv6 |
|---|---|---|---|---|
| DUT 1 | 198.51.100.17/30 | 2001:db8::17/126 | 198.51.100.21/30 | 2001:db8::21/126 |
| DUT 2 | 198.51.100.18/30 | 2001:db8::18/126 | 198.51.100.22/30 | 2001:db8::22/126 |
| Device | vlan 30 IPV4 | vlan 30 ipv6 | vlan 40 IPV4 | vlan 40 ipv6 |
|---|---|---|---|---|
| DUT 1 | 198.51.100.25/30 | 2001:db8::25/126 | 198.51.100.29/30 | 2001:db8::29/126 |
| DUT 2 | 198.51.100.26/30 | 2001:db8::26/126 | 198.51.100.30/30 | 2001:db8::30/126 |
| Device | ASN |
|---|---|
| ATE | 64496 |
| DUT 1 Default NI | 64497 |
| DUT 1 test-instance NI | 64498 |
| DUT 2 Default NI | 64497 |
| DUT 2 test-instance NI | 64498 |
| DUT 2 test-originate NI | 64499 |
| Network/ Network instance | Entity |
|---|---|
| DUT 1 Default NI | 49.0001.1980.5110.0025.00 |
| DUT 1 test-instance NI | 49.0001.1980.5110.0029.00 |
| DUT 2 Default NI | 49.0001.1980.5110.0026.00 |
| DUT 2 test-instance NI | 49.0001.1980.5110.0030.00 |
| DUT 2 test-originate NI | 49.0001.1980.5110.0100.00 |
| Flow name | Source | Destination | flow size | flow rate(percent) | flow vlan | Flow Src MAC | source interface | Destination interface |
|---|---|---|---|---|---|---|---|---|
| Flow 1 | 198.51.210.1 | 198.55.1.1 | 512 | 5 | 10 | 02:00:03:01:02:01 | eth1.10 | eth1.20 |
| Flow 2 | 198.51.210.1 | 198.55.2.1 | 512 | 5 | 30 | 02:00:03:01:04:03 | eth1.30 | eth1.40 |
| Flow 3 | 2001:db8:10::1 | 2001:db8:50::1 | 512 | 5 | 10 | 02:00:03:01:02:01 | eth1.10 | eth1.20 |
| Flow 4 | 2001:db8:10::1 | 2001:db8:60::1 | 512 | 5 | 30 | 02:00:03:01:04:03 | eth1.30 | eth1.40 |
| Interface | MAC Address |
|---|---|
| eth1.10 | 02:00:03:01:01:01 |
| eth1.20 | 02:00:03:01:02:02 |
| eth1.30 | 02:00:03:01:03:03 |
| eth1.40 | 02:00:03:01:04:04 |
RT-1.36.1 : AIGP modification with BGP policy, propagation control on BGP peers and next-hop self feature
- Create two lags named Lag1 and lag2 with both running LACP
- Configure both Lag1 and lag2 as the LACP active end
- Configure port 1 as a Lag1 member
- Configure port 2 as a Lag 2 member
- Create a non-default network instance and name it test-instance
- On Lag1, create subinterfaces in vlan 10 and 20
- Add these subinterfaces to the DEFAULT network instance
- Configure IPV4 on the subinterfaces as specified on table 1
- Configure IPV6 on the subinterfaces as specified on Table 2
- On Lag1, create subinterfaces in vlan 30 and 40
- Add these subinterfaces to test-instance network instance
- Configure IPV4 on the subinterfaces as specified on table 1
- Configure IPV6 on the subinterfaces as specified on Table 2
- On lag 2, create subinterface in vlan 10
- Add the subinterface to DEFAULT network instance
- Configure IPV4 and IPV6 addresses on the subinterfaces as specified on table 3
- On lag 2, create subinterface in vlan 20
- Add the subinterface to test-instance network instance
- Configure IPV4 and IPV6 addresses on the subinterfaces as specified on table 3
- Create a Loopback interface called Loopback10
- Configure IPV4 and IPV6 addresses on the Loopback interfaces as specified below
- IPV4 Address: 198.55.1.1/32
- IPV6 Address: 2001:db8:50::1/128
- Add the Loopback interface to the DEFAULT Network instance
- Configure IPV4 and IPV6 addresses on the Loopback interfaces as specified below
- Create a Loopback interface called Loopback20
- Configure IPV4 and IPV6 addresses on the Loopback interfaces as specified below
- IPV4 Address: 198.55.2.1/32
- IPV6 Address: 2001:db8:60::1/128
- Add the Loopback interface to the test-instance Network-instance
- Configure IPV4 and IPV6 addresses on the Loopback interfaces as specified below
- Create a route-policy named test-import-policy_aigp_20
- Create a statement named test-import-statement
- Set an action of aigp 20 and accept the route
- Create a route-policy named test-import-policy_aigp_150
- Create a statement named test-import-statement
- Set an action of aigp 150 and accept the route
- Create a route-policy named test-export-policy
- Create a statement named test-export-statement
- Create an action to set the aigp 200, next hop as self and finally accept the route
DUT 1 is going to run bgp in both of its DEFAULT and test-instance network instances. The DEFAULT network instance will run BGP on ASN 64497 and 64498 will be the ASN on the test-instance as specified on Table 5.
- Configure BGP with ASN 64497 as specified on Table 5
- Create four bgp peer-groups named uplink,uplink6 and downlink and downlink6
- Configure peer-as on these peer-groups as specified below
- peer-group: uplink; peer-as: 64496
- peer-group: uplink6; peer-as: 64496
- peer-group: downlink; peer-as: 64497
- peer-group: downlink6; peer-as: 64497
- Configure peers in peer-group downlink and downlink6 as route-reflector clients with cluster-id 1.1.1.1
- Create the following bgp peers with their peer-group, these BGP peers will be
established over vlan 10 and vlan 20 respectively on Lag1 towards the ATE
- Peer address: 198.51.100.2; peer-group: uplink
- Peer address: 198.51.100.6; peer-group: uplink
- Peer address: 2001:db8::2; peer-group: uplink6
- Peer address: 2001:db8::6; peer-group: uplink6
- Apply test-import-policy_aigp_150 in the import direction of both peer 198.51.100.2 and 2001:db8::2 respectively
- Apply test-import-policy_aigp_20 in the import direction of both peer 198.51.100.6 and 2001:db8::6 respectively
- Create the following BGP peers with their peer-group, These BGP peers will be established over vlan 10 on LAG 2 towards DUT 2 * Peer address: 198.51.100.18; peer-group: downlink * Peer address: 2001:db8::18; peer-group: downlink6
- Apply test-export-policy in the export direction on both 198.51.100.18 and 2001:db8::18
- Enable AIGP exchange on peers 198.51.100.2, 2001:db8::2, 198.51.100.18, 2001:db8::18,198.51.100.6 and 2001:db8::6
- Configure BGP with ASN 64498 as specified on Table 5
- Create four bgp peer-groups named uplink,uplink6 and downlink and downlink6
- Configure peer-as on these peer-groups as specified below
- peer-group: uplink; peer-as: 64496
- peer-group: uplink6; peer-as: 64496
- peer-group: downlink; peer-as: 64498
- peer-group: downlink6; peer-as: 64498
- Configure peers in peer-group downlink and downlink6 as route-reflector clients with cluster-id 1.1.1.1
- Create the following bgp peers with their respective peer-groups, these BGP
peers will be established over vlan 30 and vlan 40 respectively on Lag1
towards the ATE
- Peer address: 198.51.100.10; peer-group: uplink
- Peer address: 198.51.100.14; peer-group: uplink
- Peer address: 2001:db8::10; peer-group: uplink6
- Peer address: 2001:db8::14; peer-group: uplink6
- Apply test-import-policy_aigp_150 in the import direction of both peer 198.51.100.10 and 2001:db8::10 respectively
- Apply test-import-policy_aigp_20 in the import direction of both peer 198.51.100.14 and 2001:db8::14 respectively
- Create the following BGP peers with their respective peer-group, These BGP peer will be established over vlan 20 on LAG 2 towards DUT 2 * Peer address: 198.51.100.22; peer-group: downlink * Peer address: 2001:db8::22; peer-group: downlink6
- Apply test-export-policy in the export direction on both 198.51.100.22 and 2001:db8::22
- Enable AIGP exchange on 198.51.100.10, 2001:db8::10, 198.51.100.22,2001:db8::22, 198.51.100.14 and 2001:db8::14
- Create a lag named lag2 running LACP
- Configure lag2 as the LACP PASSIVE end
- Configure port 1 as a lag2 member
- Create a non-default network instance and name it test-instance
- On lag 2, create a subinterface in vlan 10
- Add the subinterfaces to the DEFAULT network instance
- Configure IPV4 on the subinterface as specified on table 3
- Configure IPV6 on the subinterface as specified on Table 3
- On lag 2, create another subinterface in vlan 20
- Add the subinterface to test-instance network instance
- Configure IPV4 on the subinterface as specified on table 3
- Configure IPV6 on the subinterface as specified on Table 3
DUT 2 is also going to run bgp in both of its DEFAULT and test-instance network instances. The DEFAULT network instance will run BGP on ASN 64497 and 64498 will be the ASN on the test-instance as specified on Table 5.
- Configure BGP with ASN 64497 as specified on Table 5
- Create 2 peer-groups named uplink and uplink6
- Configure peer-as on these peer-groups as specified below
- peer-group: uplink; peer-as: 64497
- peer-group: uplink6; peer-as: 64497
- Create the following bgp peers, these BGP peers will be established over
vlan 10 towards DUT 1
- Peer address: 198.51.100.17; peer-group: uplink
- Peer address: 2001:db8::17; peer-group: uplink6
- Enable AIGP exchange on both peers,that is 198.51.100.17 and 2001:db8::17
- Configure BGP with ASN 64498 as specified on Table 5
- Create 2 peer-groups named uplink and uplink6
- Configure peer-as on these peer-groups as specified below
- peer-group: uplink; peer-as: 64498
- peer-group: uplink6; peer-as: 64498
- Create the following bgp peers with their respective peer-groups, these BGP
peers will be established over vlan 20 towards DUT 1
- Peer address: 198.51.100.21; peer-group: uplink
- Peer address: 2001:db8::21; peer-group: uplink6
- Enable AIGP exchange on both peers,that is 198.51.100.21 and 2001:db8::21
- Create an aggregate interface with LACP named Lag1
- Add port 1 to Lag1
- Create emulated router
- Create 4 ethernet interfaces on the router, the ethernet interfaces named eth1.10, eth1.20, eth1.30, eth1.40 respectively
- Connect ethernet interfaces to the aggregate interface
- Configure Vlans 10,20,30 and 40 respectively on the ethernet interfaces
according to the following mapping
- eth1.10 - vlan 10
- eth1.20 - vlan 20
- eth1.30 - vlan 30
- eth1.40 - vlan 40
- Configure IPV4 addresses and gateway on the subinterfaces according to table 1
- Configure IPV6 addresses on the subinterfaces according to table 2
- Wait for lag interface to come up
- Create the following ipv4 and ipv6 BGP peers of type EBGP on the emulated Router
- Peer address: 198.51.100.1; remote AS: 64497
- Peer address: 198.51.100.5; remote AS: 64497
- Peer address: 198.51.100.9; remote AS: 64498
- Peer address: 198.51.100.13; remote AS: 64498
- Peer address: 2001:db8::1; remote AS: 64497
- Peer address: 2001:db8::5; remote AS: 64497
- Peer address: 2001:db8::9; remote AS: 64498
- Peer address: 2001:db8::13; remote AS: 64498
- Wait for the BGP peers to come up
- Create the following ipv4 and ipv6 Routes on the emulated router
- 198.51.210.0/24
- 198.51.220.0/24
- 2001:db8:10::/64
- 2001:db8:20::/64
- Create Traffic flow according the the specification on Table 7
- Push config on to the OTG
- Start Protocol on the OTG
- Validate that all physical interfaces on the ATE, DUT1 and DUT 2 are UP
- Validate that Aggregate interfaces on the ATE, DUT1 and DUT 2 are UP
- On DUT1, collect the out-packet counter information on interface Lag1 subinterfaces vlan 20 and 40
-
In the default NI:
- Fetch the BGP session-state of the peers 198.51.100.2, 2001:db8::2, 198.51.100.6 and 2001:db8::6
- Fetch the AIGP propagation status of the peers 198.51.100.2, 2001:db8::2, 198.51.100.6 and 2001:db8::6
- Fetch the BGP rib attributes of the routes received from the peers 198.51.100.6 and 2001:db8::6
-
In the test-instance NI:
- Fetch the BGP session-state of the peers 198.51.100.10, 2001:db8::10, 198.51.100.14 and 2001:db8::14
- Fetch the AIGP propagation status of the peers 198.51.100.10, 2001:db8::10, 198.51.100.14 and 2001:db8::14
- Fetch the BGP rib attributes of the routes received from the peers 198.51.100.14 and 2001:db8::14
-
In the default NI:
- Fetch the BGP session-state of the peers 198.51.100.17 and 2001:db8::17
- Fetch the AIGP propagation status of the peers 198.51.100.17 and 2001:db8::17
- Fetch the BGP attributes of of the routes received from peers 198.51.100.17 and 2001:db8::17
-
In the test-instance NI:
- Fetch the BGP session-state of the peers 198.51.100.21 and 2001:db8::21
- Fetch the AIGP propagation status of the peers 198.51.100.21 and 2001:db8::21
- Fetch the BGP attributes of the routes received from the peers 198.51.100.21 and 2001:db8::21
- Start Traffic on the OTG
- Wait for 60 second while the traffic is flowing
- Stop traffic on the OTG
- All physical interfaces must be UP
- All aggregate interfaces must be UP
- The out-packet counter information on interface Lag1 subinterfaces vlan 20 and 40 must be non-zero
- All BGP peers must be in Established state
- In the default NI, AIGP propagation must be true for the BGP peers 198.51.100.2,2001:db8::2, 198.51.100.6 and 2001:db8::6
- In the default NI, Routes(IPV4 and IPV6) received from the BGP peers 198.51.100.2 and 2001:db8::2 must have AIGP value of 150
- In the default NI, Routes(IPV4 and IPV6) received from the BGP peers 198.51.100.6 and 2001:db8::6 must have AIGP value of 20
- In the default NI, Routes(IPV4 and IPV6) received from BGP peers 198.51.100.6 and 2001:db8::6 must have the best-path state in adj-rib-in as true
- In test-instance NI, AIGP propagation must be true for the BGP peers 198.51.100.10,2001:db8::10, 198.51.100.14 and 2001:db8::14
- In test-instance NI, Routes(IPV4 and IPV6) received from the BGP peers 198.51.100.10 and 2001:db8::10 must have AIGP value of 150
- In test-instance NI, Routes(IPV4 and IPV6) received from the BGP peers 198.51.100.14 and 2001:db8::14 must have AIGP value of 20
- In test-instance NI, Routes(IPV4 and IPV6) received from the BGP peers 198.51.100.14 and 2001:db8::14 must have the best-path state in adj-rib-in as true
- All BGP peers must be in Established state
- In the default NI, routes received from the BGP peers 198.51.100.17 and 2001:db8::17 must have an AIGP value of 200
- In the default NI, IPV4 route received from the peer 198.51.100.17 must have a next-hop address of 198.51.100.17 while ipv6 routes received from 2001:db8::17 must have a next-hop address of 2001:db8::17
- In the default NI, AIGP propagation must be true for bgp peers 198.51.100.17 and 2001:db8::17
- In test-instance NI, routes received from the BGP peers 198.51.100.21 and 2001:db8::21 must have a AIGP value of 200
- In test-instance NI, IPV4 route received from the peer 198.51.100.21 must have a next-hop address of 198.51.100.21 while ipv6 routes received from 2001:db8::21 must have a next-hop address of 2001:db8::21
- In test-instance NI, AIGP propagation must be true for the peers 198.51.100.21 and 2001:db8::21
- The packet loss metric from each of the flows must be less than 2 percentage
{
"network-instances": {
"network-instance": [
{
"config": {
"name": "DEFAULT"
},
"interfaces": {
"interface": [
{
"config": {
"id": "Loopback10.0",
"interface": "Loopback10",
"subinterface": 0
}
}
]
},
"protocols": {
"protocol": [
{
"identifier": "BGP",
"config": {
"identifier": "BGP",
"name": "DEFAULT"
},
"bgp": {
"global": {
"config": {
"as": 64497
}
},
"peer-groups": {
"peer-group": [
{
"peer-group-name": "uplink",
"config": {
"peer-group-name": "uplink",
"peer-as": 64496
}
},
{
"peer-group-name": "uplink6",
"config": {
"peer-group-name": "uplink6",
"peer-as": 64496
}
},
{
"peer-group-name": "downlink",
"config": {
"peer-group-name": "downlink",
"peer-as": 64497
},
"route-reflector": {
"config": {
"route-reflector-client": true,
"route-reflector-cluster-id": "1.1.1.1"
}
}
},
{
"peer-group-name": "downlink6",
"config": {
"peer-group-name": "downlink6",
"peer-as": 64497
},
"route-reflector": {
"config": {
"route-reflector-client": true,
"route-reflector-cluster-id": "1.1.1.1"
}
}
}
]
},
"neighbors": {
"neighbor": [
{
"config": {
"neighbor-address": "198.51.100.2",
"peer-group": "uplink"
},
"apply-policy": {
"config": {
"import-policy": [
"test-import-policy_aigp_150"
]
}
}
},
{
"config": {
"neighbor-address": "198.51.100.6",
"peer-group": "uplink"
},
"apply-policy": {
"config": {
"import-policy": [
"test-import-policy_aigp_20"
]
}
}
},
{
"config": {
"neighbor-address": "2001:db8::2",
"peer-group": "uplink6"
},
"apply-policy": {
"config": {
"import-policy": [
"test-import-policy_aigp_150"
]
}
}
},
{
"config": {
"neighbor-address": "2001:db8::6",
"peer-group": "uplink6"
},
"apply-policy": {
"config": {
"import-policy": [
"test-import-policy_aigp_20"
]
}
}
},
{
"config": {
"neighbor-address": "198.51.100.18",
"peer-group": "downlink"
},
"apply-policy": {
"config": {
"export-policy": [
"test-export-policy"
]
}
}
},
{
"config": {
"neighbor-address": "2001:db8::18",
"peer-group": "downlink6"
},
"apply-policy": {
"config": {
"export-policy": [
"test-export-policy"
]
}
}
}
]
}
}
}
]
}
},
{
"config": {
"name": "test-instance"
},
"interfaces": {
"interface": [
{
"config": {
"id": "Loopback20.0",
"interface": "Loopback20",
"subinterface": 0
}
}
]
},
"protocols": {
"protocol": [
{
"identifier": "BGP",
"config": {
"identifier": "BGP",
"name": "DEFAULT"
},
"bgp": {
"global": {
"config": {
"as": 64498
}
},
"peer-groups": {
"peer-group": [
{
"peer-group-name": "uplink",
"config": {
"peer-group-name": "uplink",
"peer-as": 64496
}
},
{
"peer-group-name": "uplink6",
"config": {
"peer-group-name": "uplink6",
"peer-as": 64496
}
},
{
"peer-group-name": "downlink",
"config": {
"peer-group-name": "downlink",
"peer-as": 64498
}
},
{
"peer-group-name": "downlink6",
"config": {
"peer-group-name": "downlink6",
"peer-as": 64498
}
}
]
},
"neighbors": {
"neighbor": [
{
"config": {
"neighbor-address": "198.51.100.10",
"peer-group": "uplink"
},
"apply-policy": {
"config": {
"import-policy": [
"test-import-policy_aigp_150"
]
}
}
},
{
"config": {
"neighbor-address": "198.51.100.14",
"peer-group": "uplink"
},
"apply-policy": {
"config": {
"import-policy": [
"test-import-policy_aigp_20"
]
}
}
},
{
"config": {
"neighbor-address": "2001:db8::10",
"peer-group": "uplink6"
},
"apply-policy": {
"config": {
"import-policy": [
"test-import-policy_aigp_150"
]
}
}
},
{
"config": {
"neighbor-address": "2001:db8::14",
"peer-group": "uplink6"
},
"apply-policy": {
"config": {
"import-policy": [
"test-import-policy_aigp_20"
]
}
}
},
{
"config": {
"neighbor-address": "198.51.100.22",
"peer-group": "downlink"
},
"apply-policy": {
"config": {
"export-policy": [
"test-export-policy"
]
}
}
},
{
"config": {
"neighbor-address": "2001:db8::22",
"peer-group": "downlink6"
},
"apply-policy": {
"config": {
"export-policy": [
"test-export-policy"
]
}
}
}
]
}
}
}
]
}
}
]
},
"routing-policy": {
"policy-definitions": {
"policy-definition": [
{
"config": {
"name": "test-import-policy_aigp_150"
},
"statements": {
"statement": [
{
"config": {
"name": "test-import-statement"
},
"actions": {
"config": {
"policy-result": "ACCEPT_ROUTE"
}
}
}
]
}
},
{
"config": {
"name": "test-import-policy_aigp_20"
},
"statements": {
"statement": [
{
"config": {
"name": "test-import-statement"
},
"actions": {
"config": {
"policy-result": "ACCEPT_ROUTE"
}
}
}
]
}
},
{
"config": {
"name": "test-export-policy"
},
"statements": {
"statement": [
{
"config": {
"name": "test-export-statement"
},
"actions": {
"bgp-actions": {
"config": {
"set-next-hop": "SELF"
}
},
"config": {
"policy-result": "ACCEPT_ROUTE"
}
}
}
]
}
}
]
}
},
"interfaces": {
"interface": [
{
"name": "Loopback10",
"config": {
"name": "Loopback10",
"type": "iana-if-type:softwareLoopback",
"enabled": true
},
"subinterfaces": {
"subinterface": [
{
"index": 0,
"ipv4": {
"addresses": {
"address": [
{
"config": {
"ip": "198.55.1.1",
"prefix-length": 32
}
}
]
}
},
"ipv6": {
"addresses": {
"address": [
{
"config": {
"ip": "2001:db8:50::1",
"prefix-length": 128
}
}
]
}
}
}
]
}
},
{
"name": "Loopback20",
"config": {
"name": "Loopback20",
"type": "iana-if-type:softwareLoopback",
"enabled": true
},
"subinterfaces": {
"subinterface": [
{
"index": 0,
"ipv4": {
"addresses": {
"address": [
{
"config": {
"ip": "198.55.2.1",
"prefix-length": 32
}
}
]
}
},
"ipv6": {
"addresses": {
"address": [
{
"config": {
"ip": "2001:db8:60::1",
"prefix-length": 128
}
}
]
}
}
}
]
}
}
]
}
}The following configuration steps are additions to the configuration done on Test-case RT-1.36.1 above.
- On route-policy test-import-policy_aigp_20 statement test-import-statement, make the following modification
- re-set the AIGP metric from 20 to 150
- Add a new bgp action to prepend asn 64496 5 times
-
In the default NI:
- Fetch the BGP session-state of the peers 198.51.100.2, 2001:db8::2, 198.51.100.6 and 2001:db8::6
- Fetch the AIGP propagation status of the peers 198.51.100.2, 2001:db8::2, 198.51.100.6 and 2001:db8::6
- Fetch the BGP rib attributes of the routes received from the peers 198.51.100.6 and 2001:db8::6
-
In the test-instance NI:
- Fetch the BGP session-state of the peers 198.51.100.10, 2001:db8::10, 198.51.100.14 and 2001:db8::14
- Fetch the AIGP propagation status of the peers 198.51.100.10, 2001:db8::10, 198.51.100.14 and 2001:db8::14
- Fetch the BGP rib attributes of the routes received from the peers 198.51.100.14 and 2001:db8::14
- All BGP peers must be in Established state
- In the default NI, AIGP propagation must be true for the BGP peers 198.51.100.2,2001:db8::2, 198.51.100.6 and 2001:db8::6
- In the default NI, Routes(IPV4 and IPV6) received from the BGP peers 198.51.100.2 and 2001:db8::2 must have AIGP value of 150
- In the default NI, Routes(IPV4 and IPV6) received from the BGP peers 198.51.100.6 and 2001:db8::6 must have AIGP value of 150
- In the default NI, Routes(IPV4 and IPV6) received from BGP peers 198.51.100.2 and 2001:db8::2 must have the best-path state in adj-rib-in as true
- In test-instance NI, AIGP propagation must be true for the BGP peers 198.51.100.10,2001:db8::10, 198.51.100.14 and 2001:db8::14
- In test-instance NI, Routes(IPV4 and IPV6) received from the BGP peers 198.51.100.10 and 2001:db8::10 must have AIGP value of 150
- In test-instance NI, Routes(IPV4 and IPV6) received from the BGP peers 198.51.100.14 and 2001:db8::14 must have AIGP value of 150
- In test-instance NI, Routes(IPV4 and IPV6) received from the BGP peers 198.51.100.10 and 2001:db8::10 must have the best-path state in adj-rib-in as true
{
"routing-policy": {
"policy-definitions": {
"policy-definition": [
{
"config": {
"name": "test-import-policy_aigp_20"
},
"statements": {
"statement": [
{
"config": {
"name": "test-import-statement"
},
"actions": {
"bgp-actions": {
"set-as-path-prepend": {
"config": {
"repeat-n": 5,
"asn": 64496
}
}
},
"config": {
"policy-result": "ACCEPT_ROUTE"
}
}
}
]
}
}
]
}
}
}
RT-1.36.3 : Validate AIGP propagation, propagation enabled by default on IBGP peers and next-hop IP feature
The following configuration steps are additions to the configuration done on Test-case RT-1.36.2 above.
+-------------------------+ LAG2(vlan 30 and 40) [iBGP] +-------------+ LAG2 [iBGP] +---------+
| DUT2(test-originate NI)|===============================| DUT 1(RR) |===============================| DUT 2 |
+-------------------------+ ISIS +-------------+ ISIS +---------+
- On lag 2, create subinterface in vlan 30
- Add the subinterface to the DEFAULT Network instance
- Configure IPV4 and IPV6 addresses on the subinterfaces as specified on table 4
- On lag 2, create subinterface in vlan 40
- Add the subinterface to the test-instance Network-instance
- Configure IPV4 and IPV6 addresses on the subinterfaces as specified on table 4
-
Create a route-policy named default-export-v4
- Create a statement named test-statement
- Create the following actions
- set-next-hop 198.55.1.1
- accept the route
-
Create a route-policy named default-export-v6
- Create a statement named test-statement
- Create the following actions
- set-next-hop 2001:db8:50::1
- accept the route
-
Create a route-policy named non-default-export-v4
- Create a statement named test-statement
- Create the following actions
- set-next-hop 198.55.2.1
- accept the route
-
Create a route-policy named non-default-export-v6
- Create a statement named test-statement
- Create the following actions
- set-next-hop 2001:db8:60::1
- accept the route
- Create ISIS configuration instance named DEFAULT
- Configure the network entity as specified on Table 6
- Configure metric-style wide
- Add subinterfaces Lag 2 vlan 10 and lag 2 vlan 30 to the isis process and circuit type of point-to-point
- Add interface Loopback10 to the isis process
- Configure Lag 2 vlan 10 and lag 2 vlan 30 to only establish LEVEL 2 neighborship
- Configure a ISIS metric of 20 on Lag 2 vlan 10 and lag 2 vlan 30 for both IPV4 and IPV6 address-family
- Create ISIS configuration instance named DEFAULT
- Configure the network entity as specified on Table 6
- Configure metric-style wide
- Add subinterfaces Lag 2 vlan 20 and lag 2 vlan 40 to the isis process and circuit type of point-to-point
- Add interface Loopback20 to the isis process
- Configure Lag 2 vlan 20 and lag 2 vlan 40 to only establish LEVEL 2 neighborship
- Configure a ISIS metric of 20 on Lag 2 vlan 20 and lag 2 vlan 40 for both IPV4 and IPV6 address-family
- Remove test-export-policy in the export direction on both 198.51.100.18 and 2001:db8::18 which is in their export direction
- Configure the route-policy default-export-v4 in the export direction on 198.51.100.18
- Configure the route-policy default-export-v6 in the export direction on 2001:db8::18
- Create the following BGP peers with their peer-group (these BGP peering will be established towards DUT 2 on test-originate NI) * Peer address: 198.51.100.26; peer-group: downlink * Peer address: 2001:db8::26; peer-group: downlink6
- Undo the connect route to BGP redistribution that was done on test-case RT-1.36.1
- Remove test-export-policy in the export direction on both 198.51.100.22 and 2001:db8::22 which is in their export direction
- Configure the route-policy non-default-export-v4 in the export direction on 198.51.100.22
- Configure the route-policy non-default-export-v6 in the export direction on 2001:db8::22
- Create the following BGP peers with their peer-group (these BGP peering will be established towards DUT 2 on test-originate NI) * Peer address: 198.51.100.30; peer-group: downlink * Peer address: 2001:db8::30; peer-group: downlink6
The following configuration steps are additions to the configuration done on Test-case RT-1.36.1 above.
- Create a network instance and name it test-originate
- On lag2 create subinterfaces in vlan 30 and vlan 40 respectively
- Add these subinterfaces to test-originate network instance
- Configure IPV4 addresses on the subinterfaces as specified on table 4
- Configure IPV6 addresses on the subinterfaces as specified on table 4
- Create 2 Loopback interfaces and name them Loopback10 and Loopback20 respectively
- Add these Loopback interfaces (Loopback10 and Loopback20) to test-originate network instance
- Configure IPV4 and IPV6 addresses on these subinterfaces as specified below
- Loopback10: IPV4: 198.60.1.1/32; IPV6: 2001:db8:60::1/128
- Loopback20: IPV4: 198.70.1.1/32; IPV6: 2001:db8:70::1/128
- Create a prefix-set named Loopback-prefix-v4 and match the following prefixes
- ip-prefix: 198.60.1.1/32; masklength-range: exact
- ip-prefix: 198.70.1.1/32; masklength-range: exact
- Create a prefix-set named Loopback-prefix-v6 and match the following prefixes
- ip-prefix: 2001:db8:60::1/128; masklength-range: exact
- ip-prefix: 2001:db8:70::1/128; masklength-range: exact
- Create a route-policy named test-export-policy
- Create a statement named match-export-statement-v4
- Match the prefix-set Loopback-prefix-v4
- Create an action to set the aigp 200 and accept the route
- Create a statement named match-export-statement-v6
- Match the prefix-set Loopback-prefix-v6
- Create an action to set the aigp 200 and accept the route
- Create ISIS configuration instance named DEFAULT
- Configure the network entity as specified on Table 6
- Configure metric-style wide
- Add subinterfaces Lag 2 vlan 10 to the ISIS process with circuit type of point-to-point
- Configure Lag 2 vlan 10 to only establish LEVEL 2 neighborship
- Configure a ISIS metric of 20 on Lag 2 vlan 10 for both IPV4 and IPV6 address-family
- Create ISIS configuration instance named DEFAULT
- Configure the network entity as specified on Table 6
- Configure metric-style wide
- Add subinterfaces Lag 2 vlan 20 to the ISIS process with circuit type of point-to-point
- Configure Lag 2 vlan 20 to only establish LEVEL 2 neighborship
- Configure a ISIS metric of 20 on Lag 2 vlan 20 for both IPV4 and IPV6 address-family
- Create ISIS configuration instance named DEFAULT
- Configure the network entity as specified on Table 6
- Configure metric-style wide
- Add subinterfaces Lag 2 vlan 30 and lag 2 vlan 40 to the isis process and circuit type of point-to-point
- Configure Lag 2 vlan 30 and lag 2 vlan 40 to only establish LEVEL 2 neighborship
- Configure a ISIS metric of 20 on lag 2 vlan 30 and vlan 40 for both IPV4 and IPV6 address-family
- Create a BGP process with ASN 64499 as specified on Table 5
- Create BGP peer-group called default-peer-group and default-peer-group6
- Configure the peer-as,local-as and export-policy on these peer-groups as specified below * peer-group: default-peer-group; peer-as: 64497; local-as: 64497; export-policy: test-export-policy * peer-group: default-peer-group6; peer-as: 64497; local-as: 64497; export-policy: test-export-policy
- Create BGP peer-group called test-instance-peer-group and test-instance-peer-group6
- Configure the peer-as,local-as and export-policy on these peer-groups as specified below * peer-group: test-instance-peer-group; peer-as: 64498; local-as: 64498; export-policy: test-export-policy * peer-group: test-instance-peer-group6; peer-as: 64498; local-as: 64498; export-policy: test-export-policy
- Create the following BGP peers with their peer-group * Peer address: 198.51.100.25; peer-group: default-peer-group * Peer address: 2001:db8::25; peer-group: default-peer-group6 * Peer address: 198.51.100.29; peer-group: test-instance-peer-group * Peer address: 2001:db8::29; peer-group: test-instance-peer-group6
- Redistribute route from protocol DIRECTLY_CONNECTED to protocol BGP
- Stop Protocol on the OTG
- In the default network instance, collect the level 2 adjacency state for Lag 2 vlan 10 and lag 2 vlan 30
- In test-instance Network instance, collect the level 2 adjacency state for Lag 2 vlan 20 and lag 2 vlan 40
- In the default network instance, collect the level 2 adjacency state for Lag 2 vlan 10
- In test-instance Network instance, collect the level 2 adjacency state for Lag 2 vlan 20
- In test-originate Network instance, collect the level 2 adjacency state for Lag 2 vlan 30 and Lag 2 vlan 40
-
In the default NI:
- Fetch the BGP session-state of the peers 198.51.100.18, 2001:db8::18, 198.51.100.26 and 2001:db8::26
- Fetch the AIGP propagation status of the peers 198.51.100.18, 2001:db8::18, 198.51.100.26 and 2001:db8::26
- Fetch the BGP rib attributes of the routes received from the peers 198.51.100.26 and 2001:db8::26
- Fetch the route-reflector state of the peer-group downlink
- Fetch the route-reflector state of the peer-group downlink6
-
In the test-instance NI:
- Fetch the BGP session-state of the peers 198.51.100.22, 2001:db8::22, 198.51.100.30, 2001:db8::30
- Fetch the AIGP propagation status of the peers 198.51.100.22, 2001:db8::22, 198.51.100.30, 2001:db8::30
- Fetch the BGP rib attributes of the routes received from the peers 198.51.100.30, 2001:db8::30
- Fetch the route-reflector state of the peer-group downlink
- Fetch the route-reflector state of the peer-group downlink6
-
In the default NI:
- Fetch the BGP session-state of the peers 198.51.100.17 and 2001:db8::17
- Fetch the AIGP propagation status of the peers 198.51.100.17 and 2001:db8::17
- Fetch the BGP rib attributes of the routes received from peers 198.51.100.17 and 2001:db8::17
-
In the test-instance NI:
- Fetch the BGP session-state of the peers 198.51.100.21 and 2001:db8::21
- Fetch the AIGP propagation status of the peers 198.51.100.21 and 2001:db8::21
- Fetch the BGP rib attributes of the routes received from the peers 198.51.100.21 and 2001:db8::21
-
In the test-originate NI:
- Fetch the BGP session-state of the peers 198.51.100.25, 2001:db8::25, 198.51.100.29, 2001:db8::29
- Fetch the AIGP propagation status of the peers 198.51.100.25, 2001:db8::25, 198.51.100.29, 2001:db8::29
- Fetch the BGP state update sent metric for the peers 198.51.100.25, 2001:db8::25, 198.51.100.29, 2001:db8::29
-
All isis adjacency state must be up in all NI
-
In the default NI, the BGP session-state must be ESTABLISHED for the peers 198.51.100.18, 2001:db8::18, 198.51.100.26 and 2001:db8::26
-
In the default NI, AIGP propagation status must be true for the peers 198.51.100.18, 2001:db8::18, 198.51.100.26 and 2001:db8::26
-
In the default NI, the routes received from the peers 198.51.100.26 and 2001:db8::26 must have a AIGP metric of 200
-
In the default NI, the route-reflector-client state must be true for peer-group downlink and downlink6
-
In test-instance NI, the BGP session-state must be ESTABLISHED for the peers 198.51.100.22, 2001:db8::22, 198.51.100.30 and 2001:db8::30
-
In test-instance NI, AIGP propagation status must be true for the peers 198.51.100.22, 2001:db8::22, 198.51.100.30 and 2001:db8::30
-
In test-instance NI, the routes received from the peers 198.51.100.30, 2001:db8::30 must have a AIGP metric of 200
-
In test-instance NI, the route-reflector-client state must be true for peer-group downlink and downlink6
-
All isis adjacency state must be up in all NI
-
In the default NI, the BGP session-state must be ESTABLISHED for the peers 198.51.100.17 and 2001:db8::17
-
In the default NI, AIGP propagation status must be true for the peers 198.51.100.17 and 2001:db8::17
-
In the default NI, the routes received from the peers 198.51.100.17 and 2001:db8::17 must have a AIGP metric of 220
-
In the default NI, the routes received from the peer 198.51.100.17 must have a next-hop attribute of 198.55.1.1
-
In the default NI, the routes received from the peer 2001:db8::17 must have a next-hop attribute of 2001:db8:50::1
-
In test-instance NI, the BGP session-state must be ESTABLISHED for the peers 198.51.100.21 and 2001:db8::21
-
In test-instance NI, AIGP propagation status must be true for the peers 198.51.100.21 and 2001:db8::21
-
In test-instance NI, the routes received from the peers 198.51.100.21 and 2001:db8::21 must have a AIGP metric of 220
-
In test-instance NI, the routes received from the peer 198.51.100.21 must have a next-hop attribute of 198.55.2.1
-
In test-instance NI, the routes received from the peer 2001:db8::21 must have a next-hop attribute of 2001:db8:60::1
-
In test-originate NI, the BGP session-state must be ESTABLISHED for the peers 198.51.100.25, 2001:db8::25, 198.51.100.29, 2001:db8::29
-
In test-originate NI, AIGP propagation status must be true for the peers 198.51.100.25, 2001:db8::25, 198.51.100.29, 2001:db8::29
-
In test-originate NI, BGP state update sent metric for the peers 198.51.100.25, 2001:db8::25, 198.51.100.29, 2001:db8::29 must be non-zero
{
"routing-policy": {
"policy-definitions": {
"policy-definition": [
{
"config": {
"name": "default-export-v4"
},
"statements": {
"statement": [
{
"config": {
"name": "test-statement"
},
"actions": {
"bgp-actions": {
"config": {
"set-next-hop": "198.55.1.1"
}
},
"config": {
"policy-result": "ACCEPT_ROUTE"
}
}
}
]
}
},
{
"config": {
"name": "default-export-v6"
},
"statements": {
"statement": [
{
"config": {
"name": "test-statement"
},
"actions": {
"bgp-actions": {
"config": {
"set-next-hop": "2001:db8:50::1"
}
},
"config": {
"policy-result": "ACCEPT_ROUTE"
}
}
}
]
}
},
{
"config": {
"name": "non-default-export-v4"
},
"statements": {
"statement": [
{
"config": {
"name": "test-statement"
},
"actions": {
"bgp-actions": {
"config": {
"set-next-hop": "198.55.2.1"
}
},
"config": {
"policy-result": "ACCEPT_ROUTE"
}
}
}
]
}
},
{
"config": {
"name": "non-default-export-v6"
},
"statements": {
"statement": [
{
"config": {
"name": "test-statement"
},
"actions": {
"bgp-actions": {
"config": {
"set-next-hop": "2001:db8:60::1"
}
},
"config": {
"policy-result": "ACCEPT_ROUTE"
}
}
}
]
}
}
]
}
},
"network-instances": {
"network-instance": [
{
"config": {
"name": "DEFAULT"
},
"interfaces": {
"interface": [
{
"config": {
"id": "Loopback10.0",
"interface": "Loopback10",
"subinterface": 0
}
}
]
},
"protocols": {
"protocol": [
{
"identifier": "BGP",
"config": {
"identifier": "BGP",
"name": "DEFAULT"
},
"bgp": {
"peer-groups": {
"peer-group": [
{
"peer-group-name": "downlink",
"config": {
"peer-group-name": "downlink",
"peer-as": 64497
},
"route-reflector": {
"config": {
"route-reflector-client": true,
"route-reflector-cluster-id": "1.1.1.1"
}
}
},
{
"peer-group-name": "downlink6",
"config": {
"peer-group-name": "downlink6",
"peer-as": 64497
},
"route-reflector": {
"config": {
"route-reflector-client": true,
"route-reflector-cluster-id": "1.1.1.1"
}
}
}
]
},
"neighbors": {
"neighbor": [
{
"config": {
"neighbor-address": "198.51.100.18",
"peer-group": "downlink"
},
"apply-policy": {
"config": {
"export-policy": [
"default-export-v4"
]
}
}
},
{
"config": {
"neighbor-address": "2001:db8::18",
"peer-group": "downlink6"
},
"apply-policy": {
"config": {
"export-policy": [
"default-export-v6"
]
}
}
},
{
"config": {
"neighbor-address": "198.51.100.26",
"peer-group": "downlink"
}
},
{
"config": {
"neighbor-address": "2001:db8::26",
"peer-group": "downlink6"
}
}
]
}
}
},
{
"identifier": "DIRECTLY_CONNECTED",
"name": "DEFAULT",
"config": {
"identifier": "DIRECTLY_CONNECTED",
"name": "DEFAULT"
}
},
{
"identifier": "ISIS",
"config": {
"identifier": "ISIS",
"name": "DEFAULT"
},
"isis": {
"global": {
"config": {
"level-capability": "LEVEL_2",
"net": [
"49.0001.1980.5110.0025.00"
]
}
},
"interfaces": {
"interface": [
{
"config": {
"circuit-type": "POINT_TO_POINT",
"enabled": true,
"interface-id": "port-channel2.10"
},
"levels": {
"level": [
{
"config": {
"enabled": false,
"level-number": 1
},
"afi-safi": {
"af": [
{
"config": {
"afi-name": "openconfig-isis-types:IPV4",
"safi-name": "openconfig-isis-types:UNICAST",
"metric": 20
}
},
{
"config": {
"afi-name": "openconfig-isis-types:IPV6",
"safi-name": "openconfig-isis-types:UNICAST",
"metric": 20
}
}
]
}
}
]
}
},
{
"config": {
"circuit-type": "POINT_TO_POINT",
"enabled": true,
"interface-id": "port-channel2.30"
},
"levels": {
"level": [
{
"config": {
"enabled": false,
"level-number": 1
},
"afi-safi": {
"af": [
{
"config": {
"afi-name": "openconfig-isis-types:IPV4",
"safi-name": "openconfig-isis-types:UNICAST",
"metric": 20
}
},
{
"config": {
"afi-name": "openconfig-isis-types:IPV6",
"safi-name": "openconfig-isis-types:UNICAST",
"metric": 20
}
}
]
}
}
]
}
},
{
"config": {
"enabled": true,
"interface-id": "Loopback10"
}
}
]
}
}
}
]
}
},
{
"config": {
"name": "test-instance"
},
"interfaces": {
"interface": [
{
"config": {
"id": "Loopback20.0",
"interface": "Loopback20",
"subinterface": 0
}
}
]
},
"protocols": {
"protocol": [
{
"identifier": "BGP",
"config": {
"identifier": "BGP",
"name": "DEFAULT"
},
"bgp": {
"peer-groups": {
"peer-group": [
{
"peer-group-name": "downlink",
"config": {
"peer-group-name": "downlink",
"peer-as": 64497
},
"route-reflector": {
"config": {
"route-reflector-client": true,
"route-reflector-cluster-id": "1.1.1.1"
}
}
},
{
"peer-group-name": "downlink6",
"config": {
"peer-group-name": "downlink6",
"peer-as": 64497
},
"route-reflector": {
"config": {
"route-reflector-client": true,
"route-reflector-cluster-id": "1.1.1.1"
}
}
}
]
},
"neighbors": {
"neighbor": [
{
"config": {
"neighbor-address": "198.51.100.22",
"peer-group": "downlink"
},
"apply-policy": {
"config": {
"export-policy": [
"non-default-export-v4"
]
}
}
},
{
"config": {
"neighbor-address": "2001:db8::22",
"peer-group": "downlink6"
},
"apply-policy": {
"config": {
"export-policy": [
"non-default-export-v6"
]
}
}
},
{
"config": {
"neighbor-address": "198.51.100.30",
"peer-group": "downlink"
}
},
{
"config": {
"neighbor-address": "2001:db8::30",
"peer-group": "downlink6"
}
}
]
}
}
},
{
"identifier": "DIRECTLY_CONNECTED",
"name": "DEFAULT",
"config": {
"identifier": "DIRECTLY_CONNECTED",
"name": "DEFAULT"
}
},
{
"identifier": "ISIS",
"config": {
"identifier": "ISIS",
"name": "DEFAULT"
},
"isis": {
"global": {
"config": {
"level-capability": "LEVEL_2",
"net": [
"49.0001.1980.5110.0029.00"
]
}
},
"interfaces": {
"interface": [
{
"config": {
"circuit-type": "POINT_TO_POINT",
"enabled": true,
"interface-id": "port-channel2.20"
},
"levels": {
"level": [
{
"config": {
"enabled": false,
"level-number": 1
},
"afi-safi": {
"af": [
{
"config": {
"afi-name": "openconfig-isis-types:IPV4",
"safi-name": "openconfig-isis-types:UNICAST",
"metric": 20
}
},
{
"config": {
"afi-name": "openconfig-isis-types:IPV6",
"safi-name": "openconfig-isis-types:UNICAST",
"metric": 20
}
}
]
}
}
]
}
},
{
"config": {
"circuit-type": "POINT_TO_POINT",
"enabled": true,
"interface-id": "port-channel2.40"
},
"levels": {
"level": [
{
"config": {
"enabled": false,
"level-number": 1
},
"afi-safi": {
"af": [
{
"config": {
"afi-name": "openconfig-isis-types:IPV4",
"safi-name": "openconfig-isis-types:UNICAST",
"metric": 20
}
},
{
"config": {
"afi-name": "openconfig-isis-types:IPV6",
"safi-name": "openconfig-isis-types:UNICAST",
"metric": 20
}
}
]
}
}
]
}
},
{
"config": {
"enabled": true,
"interface-id": "Loopback20"
}
}
]
}
}
}
]
}
}
]
},
"interfaces": {
"interface": [
{
"name": "Loopback10",
"config": {
"name": "Loopback10",
"type": "iana-if-type:softwareLoopback",
"enabled": true
},
"subinterfaces": {
"subinterface": [
{
"index": 0,
"ipv4": {
"addresses": {
"address": [
{
"config": {
"ip": "198.55.1.1",
"prefix-length": 32
}
}
]
}
},
"ipv6": {
"addresses": {
"address": [
{
"config": {
"ip": "2001:db8:50::1",
"prefix-length": 128
}
}
]
}
}
}
]
}
},
{
"name": "Loopback20",
"config": {
"name": "Loopback20",
"type": "iana-if-type:softwareLoopback",
"enabled": true
},
"subinterfaces": {
"subinterface": [
{
"index": 0,
"ipv4": {
"addresses": {
"address": [
{
"config": {
"ip": "198.55.2.1",
"prefix-length": 32
}
}
]
}
},
"ipv6": {
"addresses": {
"address": [
{
"config": {
"ip": "2001:db8:60::1",
"prefix-length": 128
}
}
]
}
}
}
]
}
}
]
}
}RT-1.36.4 : Validate the Plus 1 incremental feature of AIGP when the IGP metric to original destination is zero
The following configuration steps are additions to the configuration done on Test-case RT-1.36.3 above.
- Configure a ISIS metric of Zero on Lag 2 vlan 10 and lag 2 vlan 30 for both IPV4 and IPV6 address-family
- Configure a ISIS metric of Zero on Lag 2 vlan 20 and lag 2 vlan 40 for both IPV4 and IPV6 address-family
- Configure a ISIS metric of Zero on Lag 2 vlan 10 for both IPV4 and IPV6 address-family
- Configure a ISIS metric of Zero on Lag 2 vlan 20 for both IPV4 and IPV6 address-family
- Configure a ISIS metric of Zero on lag 2 vlan 30 and vlan 40 for both IPV4 and IPV6 address-family
- In the DEFAULT network instance, fetch the ISIS metric on interfaces Lag 2 vlan 10 and lag 2 vlan 30
- In test-instance Network instance, fetch the ISIS metric on Lag 2 vlan 20 and lag 2 vlan 40
- In the DEFAULT network instance,fetch the ISIS metric on Lag 2 vlan 10
- In test-instance Network instance,fetch the ISIS metric on Lag 2 vlan 20
- In test-originate Network instance,fetch the ISIS metric on Lag 2 vlan 30 and vlan 40
- In default NI, Fetch the BGP rib attributes of the routes received from the peers 198.51.100.26 and 2001:db8::26
- In test-instance NI, Fetch the BGP rib attributes of the routes received from the peers 198.51.100.30 and 2001:db8::30
- In default NI,Fetch the BGP rib attributes of the routes received from peers 198.51.100.17 and 2001:db8::17
- In test-instance NI,Fetch the BGP rib attributes of the routes received from the peers 198.51.100.21 and 2001:db8::21
- All isis interface level metric must be zero
- In default NI,BGP routes received from 198.51.100.26 and 2001:db8::26 must have a AIGP metric of 200
- In test-instance NI,BGP routes received from 198.51.100.30 and 2001:db8::30 must have a AIGP metric of 200
- All isis interface level metric must be zero
- In default NI,BGP routes received from 198.51.100.17 and 2001:db8::17 must have a AIGP metric of 201
- In test-instance NI,BGP routes received from 198.51.100.21 and 2001:db8::21 must have a AIGP metric of 201
The following configuration steps are additions to the configuration done on Test-case RT-1.36.4 above.
- In Default NI, Disable AIGP propagation on the BGP peers 198.51.100.18 and 2001:db8::18
- In test-instance NI, Disable AIGP propagation on the BGP peers 198.51.100.22 and 2001:db8::22
-
In the default NI:
- Fetch the BGP session-state of the peers 198.51.100.18, 2001:db8::18, 198.51.100.26 and 2001:db8::26
- Fetch the AIGP propagation status of the peers 198.51.100.18, 2001:db8::18, 198.51.100.26 and 2001:db8::26
- Fetch the BGP rib attributes of the routes received from the peers 198.51.100.26 and 2001:db8::26
-
In the test-instance NI:
- Fetch the BGP session-state of the peers 198.51.100.22, 2001:db8::22, 198.51.100.30 and 2001:db8::30
- Fetch the AIGP propagation status of the peers 198.51.100.22, 2001:db8::22, 198.51.100.30 and 2001:db8::30
- Fetch the BGP rib attributes of the routes received from the peers 198.51.100.30 and 2001:db8::30
-
In the default NI:
- Fetch the BGP rib attributes of the routes received from peers 198.51.100.17 and 2001:db8::17
-
In the test-instance NI:
- Fetch the BGP rib attributes of the routes received from the peers 198.51.100.21 and 2001:db8::21
-
In the default NI:
- The BGP session-state on peers 198.51.100.18, 2001:db8::18, 198.51.100.26 and 2001:db8::26 must be in ESTABLISHED state
- AIGP propagation status must be False on the peers 198.51.100.18 and 2001:db8::18
- AIGP propagation must be True for the peers 198.51.100.26 and 2001:db8::26
- Routes received from peers 198.51.100.26 and 2001:db8::26 must have a AIGP metric of 200
-
In test-instance NI:
- The BGP session-state on peers 198.51.100.22, 2001:db8::22, 198.51.100.30 and 2001:db8::30 must be in ESTABLISHED state
- AIGP propagation status must be False on the peers 198.51.100.22 and 2001:db8::22
- AIGP propagation must be True for the peers 198.51.100.30 and 2001:db8::30
- Route received from peers 198.51.100.30 and 2001:db8::30 must have a AIGP metric of 200
- In the default NI, Routes received from peers 198.51.100.17 and 2001:db8::17 must not have AIGP attribute
- In the test-instance NI, Routes received from peers 198.51.100.21 and 2001:db8::21 must not have AIGP attribute
The following configuration steps are additions to the configuration done on Test-case RT-1.36.5 above( AIGP has been disabled on neighbor level and ISIS metric on link has been set to zero)
- In the default NI, Enable AIGP propagation for IPV4 address-family in the peer-group downlink
- In the default NI, Enable AIGP propagation for IPV6 address-family in the peer-group downlink6
- In test-instance NI, Enable AIGP propagation for IPV4 address-family in the peer-group downlink
- In test-instance NI, Enable AIGP propagation for IPV6 address-family in the peer-group downlink6
- In the default NI:
- Fetch the BGP session-state of the peers 198.51.100.18, 2001:db8::18, 198.51.100.26 and 2001:db8::26
- Fetch the AIGP propagation status of the peers 198.51.100.18, 2001:db8::18, 198.51.100.26 and 2001:db8::26
- Fetch the BGP rib attributes of the routes received from the peers 198.51.100.26 and 2001:db8::26
- In the test-instance NI:
- Fetch the BGP session-state of the peers 198.51.100.22, 2001:db8::22, 198.51.100.30 and 2001:db8::30
- Fetch the AIGP propagation status of the peers 198.51.100.22, 2001:db8::22, 198.51.100.30 and 2001:db8::30
- Fetch the BGP rib attributes of the routes received from the peers 198.51.100.30 and 2001:db8::30
- In the default NI:
- Fetch the BGP session-state of the peers 198.51.100.17 and 2001:db8::17
- Fetch the AIGP propagation status of the peers 198.51.100.17 and 2001:db8::17
- Fetch the BGP rib attributes of the routes received from peers 198.51.100.17 and 2001:db8::17
- In the test-originate NI:
- Fetch the BGP session-state of the peers 198.51.100.21 and 2001:db8::21
- Fetch the AIGP propagation status of the peers 198.51.100.21 and 2001:db8::21
- Fetch the BGP rib attributes of the routes received from peers the peers 198.51.100.21 and 2001:db8::21
- In the default NI,the BGP session-state of peers 198.51.100.18, 2001:db8::18, 198.51.100.26 and 2001:db8::26 must be ESTABLISHED
- In the default NI,the AIGP propagation status of the peers 198.51.100.18, 2001:db8::18, 198.51.100.26 and 2001:db8::26 must be true
- In the default NI, the routes received from the peers 198.51.100.26 and 2001:db8::26 must have a AIGP metric of 200
- In test-instance NI,the BGP session-state of peers 198.51.100.22, 2001:db8::22, 198.51.100.30 and 2001:db8::30 must be ESTABLISHED
- In test-instance NI,the AIGP propagation status of the peers 198.51.100.22, 2001:db8::22, 198.51.100.30 and 2001:db8::30 must be true
- In test-instance NI,the routes received from the peers 198.51.100.30 and 2001:db8::30 must have a AIGP metric of 200
- In the default NI,the BGP session-state of peers 198.51.100.17 and 2001:db8::17 must be ESTABLISHED
- In the default NI,the AIGP propagation status of the peers 198.51.100.17 and 2001:db8::17 must be true
- In the default NI, the routes received from the peers 198.51.100.17 and 2001:db8::17 must have a AIGP metric of 201
- In test-instance NI,the BGP session-state of peers 198.51.100.21 and 2001:db8::21 must be ESTABLISHED
- In test-instance NI,the AIGP propagation status of the peers 198.51.100.21 and 2001:db8::21 must be true
- In test-instance NI, the routes received from the peers 198.51.100.21 and 2001:db8::21 must have a AIGP metric of 201
paths:
# Configuration coverage
/network-instances/network-instance/tables/table/config/protocol:
/network-instances/network-instance/tables/table/config/address-family:
/routing-policy/defined-sets/prefix-sets/prefix-set/config/name:
/routing-policy/defined-sets/prefix-sets/prefix-set/config/mode:
/routing-policy/policy-definitions/policy-definition/statements/statement/actions/bgp-actions/set-as-path-prepend/config/repeat-n:
/routing-policy/policy-definitions/policy-definition/statements/statement/actions/bgp-actions/set-as-path-prepend/config/asn:
/routing-policy/defined-sets/prefix-sets/prefix-set/prefixes/prefix/config/ip-prefix:
/routing-policy/defined-sets/prefix-sets/prefix-set/prefixes/prefix/config/masklength-range:
/routing-policy/policy-definitions/policy-definition/statements/statement/config/name:
/routing-policy/policy-definitions/policy-definition/statements/statement/conditions/match-prefix-set/config/prefix-set:
/routing-policy/policy-definitions/policy-definition/statements/statement/actions/config/policy-result:
/routing-policy/policy-definitions/policy-definition/statements/statement/actions/bgp-actions/config/set-next-hop:
/network-instances/network-instance/protocols/protocol/config/identifier:
/network-instances/network-instance/protocols/protocol/config/name:
/network-instances/network-instance/protocols/protocol/bgp/global/config/as:
/network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/config/peer-group-name:
/network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/config/peer-as:
/network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/route-reflector/config/route-reflector-cluster-id:
/network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/route-reflector/config/route-reflector-client:
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/config/neighbor-address:
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/config/peer-group:
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/apply-policy/config/import-policy:
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/apply-policy/config/export-policy:
/network-instances/network-instance/protocols/protocol/isis/global/config/net:
/network-instances/network-instance/protocols/protocol/isis/global/config/level-capability:
/network-instances/network-instance/protocols/protocol/isis/levels/level/config/metric-style:
/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/config/interface-id:
/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/config/enabled:
/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/config/circuit-type:
/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/afi-safi/af/config/metric:
/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/afi-safi/af/config/afi-name:
/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/afi-safi/af/config/safi-name:
/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/config/level-number:
/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/config/enabled:
/network-instances/network-instance/table-connections/table-connection/config/address-family:
/network-instances/network-instance/table-connections/table-connection/config/src-protocol:
/network-instances/network-instance/table-connections/table-connection/config/dst-protocol:
# TODO: Create path for enabling AIGP on neighbor and peer-group basis an also bgp action for AIGP. see [PR/1451](https://github.com/openconfig/public/pull/1451)
# TODO: /network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/afi-safis/afi-safi/config/enable-aigp
# TODO: /routing-policy/policy-definitions/policy-definition/statements/statement/actions/bgp-actions/config/set-aigp
# TODO: /network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/config/enable-aigp
# Telemetry coverage
/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/adjacency-state:
/network-instances/network-instance/protocols/protocol/bgp/rib/afi-safis/afi-safi/ipv4-unicast/neighbors/neighbor/adj-rib-in-post/routes/route/state/best-path:
/network-instances/network-instance/protocols/protocol/bgp/rib/afi-safis/afi-safi/ipv6-unicast/neighbors/neighbor/adj-rib-in-post/routes/route/state/best-path:
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/state/messages/sent/UPDATE:
/network-instances/network-instance/protocols/protocol/bgp/rib/attr-sets/attr-set/state/aigp:
/network-instances/network-instance/protocols/protocol/bgp/rib/attr-sets/attr-set/state/next-hop:
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/state/session-state:
/interfaces/interface/state/counters/out-pkts:
/interfaces/interface/state/admin-status:
/interfaces/interface/state/oper-status:
rpcs:
gnmi:
gNMI.Set:
union_replace: true
gNMI.Subscribe:
on_change: true- FFF
-
Home
- Test Plans
- ACCTZ-1.1: Record Subscribe Full
- ACCTZ-2.1: Record Subscribe Partial
- ACCTZ-3.1: Record Subscribe Non-gRPC
- ACCTZ-4.1: Record History Truncation
- ACCTZ-4.2: Record Payload Truncation
- ACCTZ-5.1: gNSI.acctz.v1 (Accounting) Test RecordSubscribe Idle Timeout - client becomes silent
- ACCTZ-6.1: gNSI.acctz.v1 (Accounting) Test RecordSubscribe Idle Timeout - DoA client
- ACCTZ-7.1: gNSI.acctz.v1 (Accounting) Test Accounting Authentication Failure - Multi-transaction
- ACCTZ-8.1: gNSI.acctz.v1 (Accounting) Test Accounting Authentication Failure - Uni-transaction
- ACCTZ-9.1: gNSI.acctz.v1 (Accounting) Test Accounting Privilege Escalation
- ACCTZ-10.1: gNSI.acctz.v1 (Accounting) Test Accounting Authentication Error - Multi-transaction
- ACL-1.1: ACL match based on L3/L4 fields and DSCP value
- ACL-1.2: ACL Update (Make-before-break)
- ACL-1.3: Large Scale ACL with TCAM profile
- AFT-1.1: AFTs Base
- AFT-1.2: AFTs slow collector
- AFT-1.3: AFTs collector Flap
- AFT-2.1: AFTs Prefix Counters
- AFT-3.1: AFTs Atomic Flag Check
- AFT-5.1: AFTs DUT Reboot
- attestz-1: General enrollz and attestz tests
- Authz: General Authz (1-4) tests
- BMP-1.1: BMP Session Establishment and Telemetry Test
- BMP-2.7: BMP Pre Policy Test
- BMP-2.8: BMP Post Policy Test
- bootz: General bootz bootstrap tests
- Certz-1: gNSI Client Certificate Tests
- Certz-2: Server Certificate
- Certz-3: Server Certificate Rotation
- Certz-4: Trust Bundle
- Certz-5: Trust Bundle Rotation
- CFM-1.1: CFM over ETHoCWoMPLSoGRE
- CNTR-1: Basic container lifecycle via
gnoi.Containerz. - CNTR-2: Container network connectivity tests
- CNTR-3: Container Supervisor Failover
- CPT-1.1: Interface based ARP policer
- Credentialz-1: Password console login
- Credentialz-2: SSH Password Login Disallowed
- Credentialz-3: Host Certificates
- Credentialz-4: SSH Public Key Authentication
- Credentialz-5: Hiba Authentication
- DP-1.2: QoS policy feature config
- DP-1.3: QoS ECN feature config
- DP-1.4: QoS Interface Output Queue Counters
- DP-1.5: Egress Strict Priority scheduler with bursty traffic
- DP-1.7: One strict priority queue traffic test
- DP-1.8: Two strict priority queue traffic test
- DP-1.9: WRR traffic test
- DP-1.10: Mixed strict priority and WRR traffic test
- DP-1.11: Bursty traffic test
- DP-1.12: ECN enabled traffic test
- DP-1.13: DSCP and ECN bits are copied over during IPinIP encap and decap
- DP-1.14: QoS basic test
- DP-1.15: Egress Strict Priority scheduler
- DP-1.16: Ingress traffic classification and rewrite
- DP-1.17: DSCP Transparency with ECN
- DP-1.19: Egress traffic DSCP rewrite
- DP-2.2: QoS scheduler with 1 rate 2 color policer, classifying on next-hop group
- DP-2.4: Police traffic on input matching all packets using 1 rate, 2 color marker
- DP-2.5: Police traffic on input matching all packets using 2 rate, 3 color marker
- DP-2.6: Police traffic on input matching all packets using 2 rate, 3 color marker with classifier
- enrollz-1: enrollz test for TPM 2.0 HMAC-based Enrollment flow
- enrollz-2: enrollz test for TPM 1.2 Enrollment flow
- example-0.1: Topology Test
- FP-1.1: Power admin DOWN/UP Test
- FPGA-1.1: FPGA Status Test
- gNMI-1.1: cli Origin
- gNMI-1.2: Benchmarking: Full Configuration Replace
- gNMI-1.3: Benchmarking: Drained Configuration Convergence Time
- gNMI-1.4: Telemetry: Inventory
- gNMI-1.5: Telemetry: Port Speed Test
- gNMI-1.6: System gRPC Servers running in more than one network-instance
- gNMI-1.8: Configuration Metadata-only Retrieve and Replace
- gNMI-1.9: Get requests
- gNMI-1.10: Telemetry: Basic Check
- gNMI-1.11: Telemetry: Interface Packet Counters
- gNMI-1.12: Mixed OpenConfig/CLI Origin
- gNMI-1.13: Optics Telemetry, Instant, threshold, and miscellaneous static info
- gNMI-1.14: OpenConfig metadata consistency during large config push
- gNMI-1.15: Set Requests
- gNMI-1.16: Fabric redundnacy test
- gNMI-1.17: Controller card redundancy test
- gNMI-1.18: gNMI subscribe with sample mode for backplane capacity counters
- gNMI-1.19: ConfigPush and ConfigPull after Control Card switchover
- gNMI-1.20: Telemetry: Optics Thresholds
- gNMI-1.21: Integrated Circuit Hardware Resource Utilization Test
- gNMI-1.22: Controller card port attributes
- gNMI-1.23: Telemetry: Aggregate Interface Counters
- gNMI-1.24: gNMI Leaf-List Update Test
- gNMI-1.25: Telemetry: Interface Last Change Timestamp
- gNMI-1.26: Carrier Transitions Test
- gNMI-1.27: gNMI Sample Mode Test
- GNMI-2: gnmi_subscriptionlist_test
- gNMI-3: union_replace
- gNOI-2.1: Packet-based Link Qualification on 100G and 400G links
- gNOI-3.1: Complete Chassis Reboot
- gNOI-3.2: Per-Component Reboot
- gNOI-3.3: Supervisor Switchover
- gNOI-3.4: Chassis Reboot Status and Reboot Cancellation
- gNOI-4.1: Software Upgrade
- gNOI-5.1: Ping Test
- gNOI-5.2: Traceroute Test
- gNOI-5.3: Copying Debug Files
- gNOI-6.1: Factory Reset
- gNOI-7.1: BootConfig
- gNPSI-1: Sampling and Subscription Check
- HA-1.0: Telemetry: Firewall High Availability.
- Health-1.1: Generic Health Check
- Health-1.2: Healthz component status paths
- INT-1.1: Interface Performance
- IPSEC-1.1: IPSec with MACSec over aggregated links.
- IPSEC-1.2: IPSec Scaling with MACSec over aggregated links.
- IPSEC-1.3: IPSec Packet-Order with MACSec over aggregated links.
- MGT-1: Management HA solution test
- MPLS-1.1: MPLS label blocks using ISIS
- MPLS-1.2: MPLS Traffic Class Marking
- MPLS-2.2: MPLS forwarding via static LSP to BGP next-hop.
- MTU-1.3: Large IP Packet Transmission
- MTU-1.4: Large IP Packet through GRE/GUE tunnel Transmission
- MTU-1.5: Path MTU handing
- OC-1.2: Default Address Families
- OC-26.1: Network Time Protocol (NTP)
- P4RT-1.1: Base P4RT Functionality
- P4RT-1.2: P4RT Daemon Failure
- P4RT-1.3: P4RT behavior when a device/node is dowm
- P4RT-2.1: P4RT Election
- P4RT-2.2: P4RT Metadata Validation
- P4RT-3.1: Google Discovery Protocol: PacketIn
- P4RT-3.2: Google Discovery Protocol: PacketOut
- P4RT-3.21: Google Discovery Protocol: PacketOut with LAG
- P4RT-5.1: Traceroute: PacketIn
- P4RT-5.2: Traceroute Packetout
- P4RT-5.3: Traceroute: PacketIn With VRF Selection
- P4RT-6.1: Required Packet I/O rate: Performance
- P4RT-7.1: LLDP: PacketIn
- P4RT-7.2: LLDP: PacketOut
- PF-1.1: IPv4/IPv6 policy-forwarding to indirect NH matching DSCP/TC.
- PF-1.2: Policy-based traffic GRE Encapsulation to IPv4 GRE tunnel
- PF-1.3: Policy-based IPv4 GRE Decapsulation
- PF-1.4: GUEv1 Decapsulation rule using destination-address-prefix-set and TTL and DSCP behavior test
- PF-1.6: Policy based VRF selection for IPV4/IPV6
- PF-1.7: Decapsulate MPLS in GRE and UDP
- PF-1.8: Ingress handling of TTL
- PF-1.9: Egress handling of TTL
- PF-1.11: Rewrite the ingress innner packet TTL
- PF-1.12: MPLSoGRE IPV4 decapsulation of IPV4/IPV6 payload
- PF-1.13: MPLSoGRE IPV4 decapsulation of IPV4/IPV6 payload scale test
- PF-1.14: MPLSoGRE IPV4 encapsulation of IPV4/IPV6 payload
- PF-1.15: MPLSoGRE IPV4 encapsulation of IPV4/IPV6 payload scale test
- PF-1.16: MPLSoGRE IPV4 encapsulation IPV4/IPV6 local proxy test
- PF-1.17: MPLSoGRE and MPLSoGUE MACsec
- PF-1.18: MPLSoGRE and MPLSoGUE QoS
- PF-1.19: MPLSoGUE IPV4 decapsulation of IPV4/IPV6 payload
- PF-1.20: MPLSoGUE IPV4 decapsulation of IPV4/IPV6 payload scale test
- PF-1.21: Configurable IPv6 flow labels corresponding to IPV6 tunnels
- PF-1.22: GUEv1 Decapsulation and ECMP test for IPv4 and IPv6 payload
- PF-1.23: EthoCWoMPLSoGRE IPV4 forwarding of IPV4/IPV6 payload
- PF-1.24: Add and remove interface bound to PBF
- PF-1.25: Egress Static MPLS LSP Verification
- PF-2.3: Multiple VRFs and GUE DECAP in Default VRF
- PLT-1.1: Interface breakout Test
- PLT-1.2: Parent component validation test
- PLT-1.3: OnChange Subscription Test for Breakout Interfaces
- RELAY-1.1: DHCP Relay functionality
- Replay-1.0: Record/replay presession test
- Replay-1.1: Record/replay diff command trees test
- Replay-1.2: P4RT Replay Test
- RT-1.1: Base BGP Session Parameters
- RT-1.2: BGP Policy & Route Installation
- RT-1.3: BGP Route Propagation
- RT-1.4: BGP Graceful Restart
- RT-1.5: BGP Prefix Limit
- RT-1.7: Local BGP Test
- RT-1.8: BGP Route Reflector Test at scale
- RT-1.10: BGP Keepalive and HoldTimer Configuration Test
- RT-1.11: BGP remove private AS
- RT-1.12: BGP always compare MED
- RT-1.14: BGP Long-Lived Graceful Restart
- RT-1.15: BGP Addpath on scale with and without routing policy
- RT-1.19: BGP 2-Byte and 4-Byte ASN support
- RT-1.21: BGP TCP MSS and PMTUD
- RT-1.23: BGP AFI SAFI OC DEFAULTS
- RT-1.24: BGP 2-Byte and 4-Byte ASN support with policy
- RT-1.25: Management network-instance default static route
- RT-1.26: Basic static route support
- RT-1.27: Static route to BGP redistribution
- RT-1.28: BGP to IS-IS redistribution
- RT-1.29: BGP chained import/export policy attachment
- RT-1.30: BGP nested import/export policy attachment
- RT-1.31: BGP 3 levels of nested import/export policy with match-set-options
- RT-1.32: BGP policy actions - MED, LocPref, prepend, flow-control
- RT-1.33: BGP Policy with prefix-set matching
- RT-1.34: BGP route-distance configuration
- RT-1.35: BGP Graceful Restart Extended route retention (ExRR)
- RT-1.36: AIGP feature support test
- RT-1.51: BGP multipath ECMP
- RT-1.52: BGP multipath UCMP support with Link Bandwidth Community
- RT-1.53: prefix-list test
- RT-1.54: BGP Override AS-path split-horizon
- RT-1.55: BGP session mode (active/passive)
- RT-1.63: BGP Multihop
- RT-1.64: BGP Import/Export Policy (Control plane only) Functional Test Case
- RT-1.65: BGP scale test
- RT-1.66: IPv4 Static Route with IPv6 Next-Hop
- RT-1.67: IPv4 and IPv6 Static Route using Vlan Interface
- RT-1.71: BGP Disable Peer AS Filter (
disable-peer-as-filter) - RT-2.1: Base IS-IS Process and Adjacencies
- RT-2.2: IS-IS LSP Updates
- RT-2.6: IS-IS Hello-Padding enabled at interface level
- RT-2.7: IS-IS Passive is enabled at interface level
- RT-2.8: IS-IS metric style wide not enabled
- RT-2.9: IS-IS metric style wide enabled
- RT-2.10: IS-IS change LSP lifetime
- RT-2.11: IS-IS Passive is enabled at the area level
- RT-2.12: Static route to IS-IS redistribution
- RT-2.13: Weighted-ECMP for IS-IS
- RT-2.14: IS-IS Drain Test
- RT-2.15: IS-IS Extensions for Segment Routing
- RT-2.16: IS-IS Graceful Restart Helper
- RT-3.1: Policy based VRF selection
- RT-3.2: Multiple <Protocol, DSCP> Rules for VRF Selection
- RT-3.52: Multidimensional test for Static GUE Encap/Decap based on BGP path selection and selective DSCP marking
- RT-3.53: Static route based GUE Encapsulation to IPv6 tunnel
- RT-4.10: AFTs Route Summary
- RT-4.11: AFTs Route Summary
- RT-5.1: Singleton Interface
- RT-5.2: Aggregate Interfaces
- RT-5.3: Aggregate Balancing
- RT-5.4: Aggregate Forwarding Viable
- RT-5.5: Interface hold-time
- RT-5.6: Interface Loopback mode
- RT-5.7: Aggregate Not Viable All
- RT-5.8: IPv6 Link Local
- RT-5.9: Disable IPv6 ND Router Arvetisment
- RT-5.10: IPv6 Link Local generated by SLAAC
- RT-5.11: LACP Intervals
- RT-5.12: Suppress IPv6 ND Router Advertisement [Depreciated]
- RT-5.13: Flow control test
- RT-5.14: Aggregate Subinterface in Default and Non-default Network Instance
- RT-5.15: LACP Fallback Support
- RT-6.1: Core LLDP TLV Population
- RT-7.1: BGP default policies
- RT-7.2: BGP Policy Community Set
- RT-7.3: BGP Policy AS Path Set
- RT-7.4: BGP Policy AS Path Set and Community Set
- RT-7.5: BGP Policy - Match and Set Link Bandwidth Community
- RT-7.6: BGP Link Bandwidth Community - Cumulative
- RT-7.8: BGP Policy Match Standard Community and Add Community Import/Export Policy
- RT-7.9: BGP ECMP for iBGP with IS-IS protocol nexthop
- RT-7.10: Routing policy statement insertion and removal
- RT-7.11: BGP Policy - Import/Export Policy Action Using Multiple Criteria
- RT-7.51: BGP Auto-Generated Link-Bandwidth Community
- RT-8: Singleton with breakouts
- RT-10.1: Default Route Generation based on 192.0.0.0/8 Presence
- RT-10.2: Non-default Route Generation based on 192.168.2.2/32 Presence in ISIS
- RT-14.2: GRIBI Route Test
- SEC-3.1: Authentication
- SFLOW-1: sFlow Configuration and Sampling
- SR-1.1: Transit forwarding to Node-SID via ISIS
- SR-1.2: Egress Node Forwarding for MPLS traffic with Explicit Null label
- Storage-1.1: Storage File System Check
- SYS-1.1: Test default COPP policy thresholds for Arista
- SYS-2.1: Ingress control-plane ACL.
- SYS-3.1: AAA and TACACS+ Configuration Verification Test Suite
- SYS-4.1: System Mount Points State Verification
- System-1.1: System banner test
- System-1.2: System g protocol test
- System-1.3: System hostname test
- System-1.4: System time test
- System-1.5: System software-version test
- TE-1.1: Static ARP
- TE-1.2: My Station MAC
- TE-2.1: gRIBI IPv4 Entry
- TE-2.2: gRIBI IPv4 Entry With Aggregate Ports
- TE-3.1: Base Hierarchical Route Installation
- TE-3.2: Traffic Balancing According to Weights
- TE-3.3: Hierarchical weight resolution
- TE-3.5: Ordering: ACK Received
- TE-3.6: ACK in the Presence of Other Routes
- TE-3.7: Base Hierarchical NHG Update
- TE-3.31: Hierarchical weight resolution with PBF
- TE-4.1: Base Leader Election
- TE-4.2: Persistence Mode
- TE-5.1: gRIBI Get RPC
- TE-6.1: Route Removal via Flush
- TE-6.2: Route Removal In Non Default VRF
- TE-6.3: Route Leakage between Non Default VRF
- TE-8.1: DUT Daemon Failure
- TE-8.2: Supervisor Failure
- TE-9.1: gRIBI MPLS Compliance
- TE-9.3: FIB FAILURE DUE TO HARDWARE RESOURCE EXHAUST
- TE-10: gRIBI MPLS Forwarding
- TE-11.1: Backup NHG: Single NH
- TE-11.2: Backup NHG: Multiple NH
- TE-11.3: Backup NHG: Actions
- TE-11.21: Backup NHG: Multiple NH with PBF
- TE-11.31: Backup NHG: Actions with PBF
- TE-13.1: gRIBI route ADD during Failover
- TE-13.2: gRIBI route DELETE during Failover
- TE-14.1: gRIBI Scaling
- TE-14.2: encap and decap scale
- TE-14.3: gRIBI Scaling - full scale setup, target T1
- TE-14.4: gRIBI Scaling - full scale setup, target T2
- TE-15.1: gRIBI Compliance
- TE-16.1: basic encapsulation tests
- TE-16.2: encapsulation FRR scenarios
- TE-16.3: encapsulation FRR scenarios
- TE-17.1: VRF selection policy driven TE
- TE-18.1: gRIBI MPLS-in-UDP Encapsulation
- TE-18.3: MPLS in UDP Encapsulation Scale Test
- TE-18.4: ECMP hashing on outer and inner packets with MPLSoUDP encapsulation
- TestID-16.4: gRIBI to BGP Route Redistribution for IPv4
- TR-6.1: Remote Syslog feature config
- TR-6.2: Local logging destinations
- TRANSCEIVER-1.1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streaming
- TRANSCEIVER-1.2: Telemetry: 400ZR_PLUS Chromatic Dispersion(CD) telemetry values streaming
- TRANSCEIVER-3.1: Telemetry: 400ZR Optics firmware version streaming
- TRANSCEIVER-3.2: Telemetry: 400ZR_PLUS Optics firmware version streaming
- TRANSCEIVER-4.1: Telemetry: 400ZR RX input and TX output power telemetry values streaming.
- TRANSCEIVER-4.2: Telemetry: 400ZR_PLUS RX input and TX output power telemetry values streaming.
- TRANSCEIVER-5.1: Configuration: 400ZR channel frequency, output TX launch power and operational mode setting.
- TRANSCEIVER-5.2: Configuration: 400ZR_PLUS channel frequency, output TX launch power and operational mode setting.
- TRANSCEIVER-6.1: Telemetry: 400ZR Optics performance metrics (pm) streaming.
- TRANSCEIVER-6.2: Telemetry: 400ZR_PLUS Optics performance metrics (pm) streaming.
- TRANSCEIVER-7.1: Telemetry: 400ZR Optics inventory info streaming
- TRANSCEIVER-7.2: Telemetry: 400ZR_PLUS Optics inventory info streaming
- TRANSCEIVER-8.1: Telemetry: 400ZR Optics module temperature streaming.
- TRANSCEIVER-8.2: Telemetry: 400ZR_PLUS Optics module temperature streaming.
- TRANSCEIVER-9.1: Telemetry: 400ZR TX laser bias current telemetry values streaming.
- TRANSCEIVER-9.2: Telemetry: 400ZR_PLUS TX laser bias current telemetry values streaming.
- TRANSCEIVER-10.1: Telemetry: 400ZR Optics FEC(Forward Error Correction) Uncorrectable Frames Streaming.
- TRANSCEIVER-10.2: Telemetry: 400ZR_PLUS Optics FEC(Forward Error Correction) Uncorrectable Frames Streaming.
- TRANSCEIVER-11.1: Telemetry: 400ZR Optics logical channels provisioning and related telemetry.
- TRANSCEIVER-11.2: Telemetry: 400ZR_PLUS Optics logical channels provisioning and related telemetry.
- TRANSCEIVER-12.1: Telemetry: 400ZR Transceiver Supply Voltage streaming.
- TRANSCEIVER-12.2: Telemetry: 400ZR_PLUS Transceiver Supply Voltage streaming.
- TRANSCEIVER-13.1: Configuration: 400ZR Transceiver Low Power Mode Setting.
- TRANSCEIVER-13.2: Configuration: 400ZR_PLUS Transceiver Low Power Mode Setting.
- TRANSCEIVER-101: Telemetry: ZR platform OC paths streaming.
- TRANSCEIVER-102: Telemetry: ZR terminal-device OC paths streaming.
- TRANSCEIVER-103: Telemetry: ZR Plus platform OC paths streaming.
- TRANSCEIVER-104: Telemetry: ZR Plus terminal-device OC paths streaming.
- TRANSCEIVER-105: Telemetry: ZR platform OC paths streaming.
- TRANSCEIVER-106: Telemetry: ZR terminal-device OC paths streaming.
- TRANSCEIVER-107: Telemetry: ZR Plus platform OC paths streaming.
- TRANSCEIVER-108: Telemetry: ZR Plus terminal-device OC paths streaming.
- TUN-1.3: Interface based IPv4 GRE Encapsulation
- TUN-1.4: Interface based IPv6 GRE Encapsulation
- TUN-1.6: Tunnel End Point Resize for Ecapsulation - Interface Based GRE Tunnel
- TUN-1.9: GRE inner packet DSCP
- URPF-1.1: uRPF validation from non-default network-instance
- Test Plans