[c-nsp] 6vpe - me3600x

[Aaron]

That's exactly what I was asking!  Thanks Jason

*** not shown here , I reverted my vrf one definition back to the legacy
mode so I could see this process run through.... very nice...one thing I see
is that it added an additional helper under my svi's ... why ?

ip helper-address global 192.168.254.136
ip helper-address 192.168.254.136

does "global" mean global vrf?  If so, that's NOT where that dhcp server
lives...so I would seem that I wouldn't want that there.



Aaron

noc-3600(config)#vrf ?
  definition   VRF definition mode
  selection    selection criteria
  upgrade-cli  upgrade cli

noc-3600(config)#vrf up
noc-3600(config)#vrf upgrade-cli ?
  multi-af-mode  Upgrade to multi address family VRF support

noc-3600(config)#vrf upgrade-cli multi-af-mode ?
  common-policies      IPv4 VRF policies are moved to common VRF policies
  non-common-policies  IPv4 VRF policies are not moved to common VRF
policies,but kept as ipv4 only VRF policies.

noc-3600(config)#vrf upgrade-cli multi-af-mode no
noc-3600(config)#vrf upgrade-cli multi-af-mode non-common-policies ?
  force  Do not prompt for confirmation
  vrf    Specify a particular VRF
  <cr>

noc-3600(config)#vrf upgrade-cli multi-af-mode non-common-policies
You are about to upgrade to the multi-AF VRF syntax commands.
You will lose any IPv6 address configured on interfaces
belonging to upgraded VRFs.

Are you sure ? [yes]:
Number of VRFs upgraded: 2
noc-3600(config)#
noc-3600(config)#^Z
noc-3600#sh run vrf one
Building configuration...

Current configuration : 725 bytes
vrf definition one
 rd 10.101.12.253:1
 !
 address-family ipv4
  route-target export 1:1
  route-target import 1:1
 exit-address-family
!
!
interface Vlan10
 vrf forwarding one
 ip address 10.40.4.1 255.255.255.0 secondary
 ip address 1.2.3.4 255.255.255.240
 ip access-group coming-from-dhcp-customers in
 ip access-group going-to-dhcp-customers out
 ip helper-address global 192.168.254.136
 ip helper-address 192.168.254.136
!
interface Vlan11
 vrf forwarding one
 ip address 10.40.5.1 255.255.255.0
 ip helper-address global 192.168.254.136
 ip helper-address 192.168.254.136
!
router bgp 64512
 !
 address-family ipv4 vrf one
  redistribute connected
  maximum-paths ibgp unequal-cost 3
 exit-address-family
!
end

-----Original Message-----
From: Jason Lixfeld [mailto:jason at lixfeld.ca] 
Sent: Wednesday, September 26, 2012 3:11 PM
To: Aaron
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] 6vpe - me3600x

Not sure I quite understand what you're asking, but I'll share some
ME3600/6VPE related foo from a similar exercise I went through last week.

I found that I had to use 'vrf upgrade-cli multi-af-mode
non-common-policies' to get the v6 address-family configurable within a VRF
instance.

Not sure if that helps you at all..

On 2012-09-26, at 4:03 PM, "Aaron" <aaron1 at gvtc.com> wrote:

> I have 15.2(4)S on my me3600x so I'm ready to test 6vpe.
> 
> 
> 
> I'm seeing that there isn't really a way to enable ipv6 under the 
> regular vrf definition "ip vrf one" syntax..  But I do see that "vrf
definition one"
> has address-family v4 and v6 under it..
> 
> 
> 
> I didn't know how to migrate vrf structures of "ip vrf one" to "vrf 
> definition one" so I just went at it to see how smoothly I could make 
> this happen.  someone please tell me if there was a better way or if 
> anything I mentioned is misunderstood on my part.
> 
> 
> 
> *** again, the premise here was a wanted to do 6vpe on this me3600x 
> PE..so I was under the impression that I had to use "vrf definition 
> one" in order to make vrf "one" ipv6 aware... so I proceeded to remove 
> "ip vrf one" and recreate it under the "vrf def one" syntax.
> 
> *** WAIT FOR VRF TO DELETE....do sh vrf one "being deleted"...wait...
> 
> *** interface vrf command changed
> 
> ------ old - "ip vrf forwarding one"
> 
> ------ new - "vrf forwarding one"
> 
> *** you gotta add mp-ibgp vrf-specific structure back in
> 
> 
> 
> Conf t
> 
> no ip vrf one
> 
> 
> 
> vrf d one
> 
> rd 10.101.12.253:1
> 
> address-family ipv4
> 
> route-target export 1:1
> 
> route-target import 1:1
> 
> 
> 
> interface Vlan10
> 
> vrf forwarding one
> 
> ip address 10.40.4.1 255.255.255.0 secondary
> 
> ip address 1.2.3.4 255.255.255.240
> 
> ip access-group coming-from-dhcp-customers in
> 
> ip access-group going-to-dhcp-customers out
> 
> ip helper-address 192.168.254.136
> 
> 
> 
> interface Vlan11
> 
> vrf forwarding one
> 
> ip address 10.40.5.1 255.255.255.0
> 
> ip helper-address 192.168.254.136
> 
> 
> 
> 
> 
> router bgp 64512
> 
> address-family ipv4 vrf one
> 
>  redistribute connected
> 
>  maximum-paths ibgp unequal-cost 3
> 
> 
> 
> do wr
> 
> 
> 
> 
> 
> 
> 
> Aaron
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/