[Mispa-management-l] MTL - NITEL - SKYBAND - route server config - RE: ROUTE OF 102.176.250.0 /24

[Dr P Nyirenda]

Rajab: MTL : I have updated the route server config as you requested, see attached.

T.Jumbe: NITEL: I have removed the MALSWITCH prefix as discussed at the MMC Meeting.
This leaves the prefix 41.79.88.0/22 on Simbanet as here attached

Clement: SKYBAND: It was observed at the Mispa Management Committee Meeting on 30
May 2019 that the prefix 105.234.0.0/16 that appears on the Skyband prefix-list also appears
on the Airtel prefix-list as shown in the attached config and a recommendation was hence
made to remove it from Skyband list. Please review the config and the recommendation and
give me your direction.

IPv6: ALL: You will all note on the attached config that I have now assigned an IPv6 address
2001:43F8:380::2/64 on the interface GigabitEthernet0/1 of the route server and you will see
the IPv6 interface config towards the bottom of the attached file that shows the route server
config, the BGP routes and the IPv6 interface.

It would be great if you can activate IPv6 on your routers and give your interface the IPv6
address on the 2001:43F8:380::/64 subnet which ends with the last quartet on your IPv4
peering interface address.  So for example if your IPv4 peering address is 196.223.27.40/24
then your IPv6 address is 2001:43F8:380::40/64

Once done then please check if you can ping the IPv6 interface on the route server and let
me know.

Regards,

Paulos
======================
Dr Paulos B Nyirenda
NIC.MW & .mw ccTLD
http://www.registrar.mw



On 31 May 2019 at 13:51, Rajab R. Hussein wrote:

> Dear Dr Paulos,
>
> Find attached how the config should be under MTL lines.
>
> Regards,
>
> Rajab
>
> -----Original Message-----
> From: Dr P Nyirenda [mailto:paulos at sdnp.org.mw]
> Sent: Friday, May 31, 2019 2:35 PM
> To: Rajab R. Hussein
> Cc: mispa-chair at mix.mw; Maloto Nyirenda
> Subject: Re: ROUTE OF 102.176.250.0 /24
>
> On 30 May 2019 at 11:31, Rajab R. Hussein wrote:
>
> >
> >     Dear Dr. Paulos,
> >      
> >     We request to have the ip address below advertised in the route server :
> >      
> >     102.176.250.0 /24
>
> As we have normally done on the MIX, please send the exact config lines that I should use to act on this request for you.
>
> We do this to have a common understanding of the config as the config evolves.
>
> To assist with this config, I have here attached the current cisco route server config where your lines will fit.
>
> I will take receipt of the config lines as confirmation from you for this to be done for your MTL peering configuration at the MIX.
>
> Regards,
>
> PC
> ======================================
> Dr Paulos B Nyirenda
> Malawi SDNP PC: http://www.sdnp.org.mw
> NIC.MW & .mw ccTLD http://www.registrar.mw
> Chair: MISPA http://www.mispa.org.mw
>
>
> >      
> >      
> >     Best regards,
> >      
> >      
> >     Rajab
> >      
> >      
> >      
> >
> > --
> > This message has been scanned for viruses and dangerous content by
> > MailScanner, and is believed to be clean.
>
>
>
>
> ---
> This email has been checked for viruses by AVG.
> https://www.avg.com
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------- next part --------------
The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.

   ---- File information -----------
     File:  route-server-config-2019-05-31.txt
     Date:  31 May 2019, 19:00
     Size:  30660 bytes.
     Type:  Text
-------------- next part --------------
A non-text attachment was scrubbed...
Name: route-server-config-2019-05-31.txt
Type: application/octet-stream
Size: 30660 bytes
Desc: not available
URL: <http://chambo3.sdnp.org.mw/pipermail/mispa-management-l/attachments/20190531/8e2b4ed3/attachment-0001.obj>