BGP bug in eNSP

Hello there,

I found a problem, or a bug, when used the eNSP to simulate the BGP.

Please refer to the topology below

When R3 and R5 didn’t establish the EBGP peer relationship, and aggregate the routes on R3 manually with as-set attribute set, in this situation, the BGP routing table on R4 displays as below:

<R4>dis bgp ro

 BGP Local router ID is 4.4.4.4

 Status codes: * - valid, > - best, d - damped,

               h - history,  i - internal, s - suppressed, S - Stale

               Origin : i - IGP, e - EGP, ? - incomplete

 Total Number of Routes: 2

      Network            NextHop    MED    LocPrf    PrefVal Path/Ogn

 *>   172.16.200.1/32    10.34.34.1               0      300 200?

 *>   192.168.0.0/16     10.34.34.1               0      300 200 {100}?

As you can see, AS numebr 200 is out of the bracket, but when the R3 and R5 establish the EBGP peer relationship, the BGP routing table on R4 is normal. Please check output below:

<R4>dis bgp ro

 BGP Local router ID is 4.4.4.4

 Status codes: * - valid, > - best, d - damped,

               h - history,  i - internal, s - suppressed, S - Stale

               Origin : i - IGP, e - EGP, ? - incomplete

Total Number of Routes: 2

      Network            NextHop    MED   LocPrf    PrefVal Path/Ogn

*>   172.16.200.1/32    10.34.34.1              0      300 200?

*>   192.168.0.0/16     10.34.34.1              0      300 {200 100 500}?

I’ll attach the eNSP project, kindly help to confirm if there is a bug, or just I have some miss configuration.

Thanks.