From: Dennis J. Hartmann (dhartma5@optonline.net)
Date: Fri May 20 2005 - 23:16:44 GMT-3
On a side note, anyone looking at their CCIE SP shoud be paying
close attention to the wide-style metrics conversation because you'll need
it for doing accurate MPLS Traffic Engineering if your core is running ISIS
(only OSPF and ISIS are supported as P routing protocols in MPLS Traffic
Engineering).
I hope this wasn't too off topic. It's not like I'm talking about
Juniper or the Pix. ;-)
-Dennis
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Mark
Lasarko
Sent: Friday, May 20, 2005 7:27 PM
To: ccielab@groupstudy.com
Subject: Re: RE: isis metric-style transition
Greetings Gladston,
Interesting - Are you also running IPv4?
Here's why I ask:
Rack1R1(config)#router isis
Rack1R1(config-router)#address-family ipv6
Rack1R1(config-router-af)#multi-topology
%Must enable wide metrics first
(on a 3620 @ 12.2(15)T14)
I interpret the above as meaning I cannot have both
IPv4 and IPv6 without wide (or transition) metrics.
Also, you're configuring this locally - I think what I was looking at was
between devices
Please let me know what you find.
Thanx!
~M
>>> <gladston@br.ibm.com> 05/20/05 7:13 PM >>>
Hi,
From what I remember on the ISIS examples I saw, it is not necessary to use
wide metric.
For example:
router(config)# router isis cisco
router(config-router)# net 49.aaaa.bbbb.cccc.dddd.0000.2222.2222.2222.00
router(config-router)# exit
router(config)# interface ethernet 0
router(config-if)# ipv6 address 2000:1:2::1/64 router(config-if)# ipv6
router isis cisco router(config-if)# interface serial 0 router(config-if)#
ipv6 address 2000:1:1::1/64 router(config-if)# ipv6 router isis cisco
Would be enough to get ipv6 routing with ISIS.
I will lab it soon, just to double check it.
Did you read this requirement on any doc?
This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:11:59 GMT-3