Hi,
Now that we have rolled out MPLS, doing a trace from other ISP's to Internet
addresses on the other side of our MPLS core results in one of 2 things:
1. If the trace from the originating ISP filters out RFC1918 addresses you
will get a few blank hops as the ttl expires are filtered out.
2. If they do not filter the 1918 addresses you will see the Private
addresses in your traceroute.
Even though you can see the addresses you can't route to it so it only
becomes a visual problem, Oh and it will slow your trace down a little as it
tries to do name resolution.
In my opinion I would rather see the hops in the middle than time outs.
I believe there is a software tweak in later IOS's to allow the MPLS hops to
become transparent, this should resolve this aesthetic problem.
Perhaps someone could shed some light on which IOS version has this option.
-----Original Message-----
From: Edward S. Desouza [mailto:edward_desouza@yahoo.com]
Sent: Thursday February 2001 04:19
To: cisco-nsp@puck.nether.net
Subject: [nsp] BCP for Address space for ISP environment
Hi Guys,
In an ISP environment, it is recommended ( at ISP
workshops held by CISCO as a BCP ( Best Common
Practise ) to use only VALID Internet IP addresses for
the ISP backbone. Are there any specific disadvantages
if a mix of Valid and Private address space is used in
an ISP backbone if proper filtering of private address
spaces is possible ???? I would appreciate it if I
could get specific examples of disadvantages with a
mix and match of valid and invalid address spaces.
Rgds,
Edward
=====
Edward S. Desouza
23/24 Manali 5,
Evershine Nagar,
Malad (W),
Bombay 400064.
Tel:9122-8886362
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices!
http://auctions.yahoo.com/
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:30 EDT