The gen_config file for these suites are contained in dpa_syntax_peer.cfg. The following notes only indicate additional facts about the tests
Peer line Configuration:
group type internal/external peeras 201
aspath-opt {
dpa 20 as 3552
}
Route Set: default routes for environmenet
PCs: 223.1
223.2
223.3
192.168.10.1
Suns: 223.1
223.2
223.3
198.108.60.1
import statement: none
export statement: none
Results:
default routes
Comments: clear routing table before begining
group type internal/external peeras 201
aspath-opt {
as 3552 dpa 30
}
Route Set: default routes for environmenet
route-set 1
import statement:
import proto bgp autonomoussystem 201
aspath-opt {
as 3552 dpa 30
}
{
all;
}
export statement:
export proto bgp as 201
{
proto bgp as 201 {
all;
};
proto static {
all;
};
};
Results: default
union of machines route-set 1
Comments: clear routing table before begining
group type internal/external peeras 201
aspath-opt {
as 3552 dpa 30
}
Route Set: default routes for environmenet
route-set 2
import statement:
import proto bgp autonomoussystem as1
aspath-opt {
as 3552 dpa 30
}
{
all;
}
export statement:
export proto bgp as as2
{
proto bgp as as2 {
all;
};
...
proto static {
all;
};
};
Results: default
union of machines route-set 2
Comments:
group type internal/external peeras 201
aspath-opt {
as 3552 dpa 30
}
Route Set: default routes for environmenet
import statement:
import proto bgp autonomoussystem as1
aspath-opt {
as 3552 dpa 30
}
{
all;
}
export statement:
export proto bgp as as2
{
proto bgp as as2 {
all;
};
...
proto static {
all;
};
};
Results: default routes
comments: none
group type internal/external peeras 201
aspath-opt {
as 3552 dpa 30
}
Route Set: default routes for environmenet
route_set 1
import statement:
import proto bgp autonomoussystem as1
aspath-opt {
dpa 30 autonomous-system 20
}
{
all;
}
export statement:
export proto bgp as as2
{
proto bgp as as2 {
all;
};
...
proto static {
all;
};
};
Results: default routes
comments: none
group type internal/external peeras 201
aspath-opt {
}
Route Set: default routes for environmenet
route_set 1
import statement:
import proto bgp autonomoussystem as1
aspath-opt {
}
{
all;
}
export statement:
export proto bgp as as2
{
proto bgp as as2 {
all;
};
...
proto static {
all;
};
};
Results: default routes
For external peers, the when the route generated changes its as-path from having a DPA to not having a DPA - route is also not withdrawn on external peers.. (1 4 4 to 1 4 5)
group type internal/external peeras 201
aspath-opt {
dpa 20 as 3552
comm-split 3552 20
}
Route Set: default routes for environmenet
import statement: none
export statement: none
Is this the right response? I think so.
group type internal/external peeras 201
aspath-opt {
dpa 20 as 3552
comm-split 3552 20
comm-split 3552 21
}
Route Set: default routes for environmenet
route_set 1
import statement:
import proto bgp autonomoussystem as1
aspath-opt {
}
{
all;
}
export statement:
export proto bgp as as2
{
proto bgp as as2 {
all;
};
...
proto static {
all;
};
};
Results: default routes
When the previous route received or generated by an internal peer has different DPA on re-configuration. The internal peer considers this an aspath change and does not re-advertise the route.
External peers re-advertise this route.
group type internal/external peeras 201
aspath-opt {
as 3552 dpa 30
comm-split 3552 20
comm-split 3552 21
comm-split 3552 22
comm-split 3552 23
comm-split 3552 24
comm-split 3552 25
comm-split 3552 26
comm-split 3552 27
comm-split 3552 28
comm-split 3552 29
}
Route Set: default routes for environmenet
route_set 2
import statement:
import proto bgp autonomoussystem as1
aspath-opt {
as 3552 dpa 30
comm-split 3552 20
comm-split 3552 21
comm-split 3552 22
comm-split 3552 23
comm-split 3552 24
comm-split 3552 25
comm-split 3552 26
comm-split 3552 27
comm-split 3552 28
}
{
all;
}
export statement:
export proto bgp as as2
{
proto bgp as as2 {
all;
};
...
proto static {
all;
};
};
Results: default routes
Earlier routes (223.30/223.40) are removed as unreachable because they have been tagged with the static tag of earlier aspath. but they are not re-announced. This is a problem.
group type internal/external peeras 201
aspath-opt {
autonomous-system 3552 dpa 30
}
Route Set: default routes for environmenet
route_set null
import statement:
import proto bgp autonomoussystem as1
aspath-opt {
autonomous-system 3552 dpa 30
}
{
all;
}
export statement:
export proto bgp as as2
{
proto bgp as as2 {
all;
};
...
proto static {
all;
};
};
Results: default routes
all routes are removed because of change in static route. It works, but we still haven't conquered the first problem.
group type internal/external peeras 201
aspath-opt {
dpa 30 autonomous-system 20
community no-export
}
Route Set: default routes for environmenet
route_set 1
import statement:
import proto bgp autonomoussystem as1
aspath-opt {
dpa 30 autonomous-system 20
community no-export
}
{
all;
}
export statement:
export proto bgp as as2
{
proto bgp as as2 {
all;
};
...
proto static {
all;
};
...
proto static {
all;
};
};
Results: default routes
No export function works. Unreachable prefix sent. Yeah!
group type internal/external peeras 201
aspath-opt {
dpa 30 autonomous-system 20
community no-advertise
}
Route Set: default routes for environmenet
route_set 1
import statement:
import proto bgp autonomoussystem as1
aspath-opt {
dpa 30 autonomous-system 20
community no-advertise
}
{
all;
}
export statement:
export proto bgp as as2
{
proto bgp as as2 {
all;
};
...
proto static {
all;
};
...
proto static {
all;
};
};
Results: default routes
No installation of routes in remote site. Need to change the expected routes file. Why do we not install in the route table?? Why do we not