Re: [c-nsp] Best Practices to make one BGP link prefer for egrees and ingress traffic of one subnet
Gert Doering via cisco-nsp <[email protected]> Mon, 23 Feb 2026 16:12:25 +0100
| Newsgroups | gmane.network.nsp.cisco |
|---|---|
| Message-ID | <[email protected]> |
--===============5923399719605740476==
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="CNwM89hi4A3mt8+f"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
--CNwM89hi4A3mt8+f
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi,
On Mon, Feb 23, 2026 at 06:02:47PM +0300, Muhammad Atif Jauhar via cisco-ns=
p wrote:
> Thank you both for your feedback.
>=20
> Basically, one subnet is for backup environment and other link is for
> normal user traffic toward Data center.
>=20
> If we use one link most of the bandwidth captured by backup to avoid any
> bandwidth issue and slowness faced by users, we acquired one link for only
> backup and replication.
>=20
> Now want to segregate traffic on both link to avoid any bandwidth issue.
Quite often this can be done by destination (like, "backup server is
in the remote location, on a well-known IP address, so *this* prefix
goes to the left, and will take most of the traffic"). Sometimes not.
B&R traffic tends to be highly asymmetric by nature ("much higher needs
toward the backup storage than vice versa") so getting this direction
sorted out can help a lot with the scenario "backup left, link can be
saturized, rest goes right, sufficient capacity remains".
gert
--=20
"If was one thing all people took for granted, was conviction that if you=
=20
feed honest figures into a computer, honest figures come out. Never doubte=
d=20
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistre=
ss
Gert Doering - Munich, Germany [email protected]=
=2Ede
--CNwM89hi4A3mt8+f
Content-Type: application/pgp-signature; name=signature.asc
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
iQGzBAEBCAAdFiEEti5qK05WVwt73GvgHYKe/spWKBIFAmmcblcACgkQHYKe/spW
KBJHfgv/cvlqdJ+ajXpy5ykmd9EwDxEqXiQt5FOk/a/1mEV22xtBO2UbqeqwN6Z5
5zNxON1Dtaw2xOUJhalQ5lk7e+SpCeLCE9mlUw2aQo+KV9AFwqE8/vqU+wIxGFmO
WQRy0WQBEsbB/2pGTX1PQbbd1/vqYS8SKrIzxWZ8CfWHtt6rppy+JTTM15BPT5GY
jdKuDF5WR/ai+OsVxSA1M1QbTRB4pg67XxhpOGXQxa8GzvReOkPVqVoWpF/atTqT
CtYsFoUB1iaquy2mksXWoUpDOLz2hxh+p8bYij7F3jF4cyoMNMDnB23Hc1pk7X8J
ahTAhEHGU1yT76OPKR3PqbfvquEmxvUjMczl9xu83prJX2cMDPXJ50rw/ZZ+SXT0
f0c92A7zB6ehx0Qhj12q3+4h4Qby4jcHl61U0RQgoTh8CQdahsC3Lj+Uo8raGXa3
XsiqOJQWtZ7fFe7HaBQIe3ZaTdgy6gUxSSsrX5lJ8EkBcI4JQlRfcW18rcHxPEcF
gC18TNhw
=8YHy
-----END PGP SIGNATURE-----
--CNwM89hi4A3mt8+f--
--===============5923399719605740476==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KY2lzY28tbnNw
IG1haWxpbmcgbGlzdCAgY2lzY28tbnNwQHB1Y2submV0aGVyLm5ldApodHRwczovL3B1Y2submV0
aGVyLm5ldC9tYWlsbWFuL2xpc3RpbmZvL2Npc2NvLW5zcAphcmNoaXZlIGF0IGh0dHA6Ly9wdWNr
Lm5ldGhlci5uZXQvcGlwZXJtYWlsL2Npc2NvLW5zcC8K
--===============5923399719605740476==--