[j-nsp] How to load a lot of prefixes
BRIANT Alain
alain.briant at c-s.fr
Wed Feb 20 16:48:13 EST 2008
Hi dong bei
If your main problem is in loading the configuration inside the router
be sure to do it with a "load merge terminal" with several routes like
this:
static {
route 1.2.3.4/24 discard;
}
Instead of loading the set commands like this:
set routing-options static route 1.2.3.4/24 discard
- You should prefer to load the config via a telnet or ssh session
instead of using the console port.
- If the speed is too fast when you send the config and have some
errors try to put some line pacing (timer of about 10 to 50ms) at the
end of each line (see in your terminal or telnet application)
Hop this will help you
Regards
Alain
Quoting wang dong bei <wang.dong.bei at gmail.com>:
> Hi talented minds,
>
> I want to do some testing with BGP and I need to inject a lots of routes,
> preferably the entire Internet routing table, into some of the routers of an
> isolated lab. My initial approach is to capture the "show route bgp" output
> from one of my routers and massage the data into the "set routing-options
> static prefix....." and load everything into my testing routers. However,
> the script is more difficult to write, the result is full of errors, and
> when I load the config, it somehow hang my terminal sessions.
>
> So are there anyways to quickly populate the routing table of my testing
> routers by administrative configuration means?
>
> thanks for your help.
>
> regards,
>
> dong bei
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
----------------------------------------------------------------
Ce message electronique et tous les fichiers joints qu'il contient
(ci-apres "le message") sont confidentiels et destines exclusivement a
l'usage des destinataires indiques ou des personnes dument habilitees
a les recevoir a leur place.
Si vous recevez ce message par erreur, merci de bien vouloir le
detruire et d'en avertir l'emetteur.
Toute utilisation de ce message non conforme a sa destination, toute
diffusion ou toute publication totale ou partielle est interdite sauf
autorisation expresse de l'emetteur.
Les idees et opinions exprimees dans ce message sont celles de son
auteur et ne representent pas necessairement celles de CS
Communication & Systemes ou de ses filiales.
Malgre toutes les dispositions prises par CS Communication & Systemes
et ses filiales pour minimiser les risques de virus, les fichiers
joints a ce message peuvent contenir des virus qui pourraient
endommager votre systeme informatique. Il vous appartient d'effectuer
vos propres controles anti-virus avant d'ouvrir les fichiers joints.
CS Communication & Systemes et ses filiales declinent toute
responsabilite pour toute perte ou dommage resultant de l'utilisation
de ce message et/ou des fichiers joints.
This e-mail and any file attached hereto (hereinafter 'the e-mail')
are confidential and intended solely for the use of the adressees
indicated below or the persons duly entitled to receive them in their
place.
If you receive this e-mail in error, please delete it and notify the sender.
Any use of this e-mail not in accordance with its purpose, any
dissemination or disclosure, either whole or partial, is prohibited,
unless formally approved by the sender.
The ideas or opinions expressed in this e-mail are solely those of its
author and do not necessarily represent those of CS Communication &
Systeme or its affiliates.
Despite all the measures taken by CS Communication & Systeme and its
affiliates in order to minimize the risks of virus, the files attached
to this e-mail may contain virus which could damage your information
system. You are responsible for processing your own anti-virus
checking before opening any file attached hereto. Neither CS
Communication & Systemes, nor its affiliates, shall be held liable for
any loss or damage due to the use of this e-mail or any file attached
hereto.
More information about the juniper-nsp
mailing list