Mailing List Archive

I can configure VEs with both "ipv6 address" and "ipv6 enable" on my FCX.
What version of code are you running?


On Thu, Nov 7, 2013 at 11:13 AM, Mark Price <mprice@tqhosting.com> wrote:

>
> Hi all,
>
> Is anyone using layer3 IPv6 features on FCX?
>
> I enabled system-wide ipv6 with:
>
> ipv6 unicast-routing
>
> I can successfully configure IPv6 addresses on ethernet interfaces, and
> ping ipv6 across them.
>
> However, when I configure IPv6 on a VE interface (and "ipv6 enable" on the
> VE), the system doesn't seem to recognize it. I cannot ping the local ipv6
> address, and it doesn't show up in "show ipv6 route"
>
>
> Mark
>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>

Hi Matt,

On Thu, Nov 7, 2013 at 4:08 PM, Matt Kassawara <mkassawara@gmail.com> wrote:

> I can configure VEs with both "ipv6 address" and "ipv6 enable" on my FCX.
> What version of code are you running?
>

The config was accepted for me, and is now installed in 'sho ipv6 route'
when removing follow-ve from the VE that I was configuring.

However, I'm still unable to communicate with ipv6 hosts on a vlan from VE
interface. tcpdump from connected host shows no traffic when trying to
ipv6 ping from FCX to a host on ipv6 subnet on VE.

SW: Version 08.0.00aT7f3


Have you been able to successfully pass ipv6 traffic via VE?


thanks,

Mark

I'm running 7.3.00a in production and 8.0.01 in the lab... both with IPv6
working on VEs. Can you provide the rest of your configuration?

P.S. - For unrelated reasons, I recommend upgrading to at least 8.0.01.


On Fri, Nov 8, 2013 at 12:14 AM, Mark Price <mprice@tqhosting.com> wrote:

>
> Hi Matt,
>
> On Thu, Nov 7, 2013 at 4:08 PM, Matt Kassawara <mkassawara@gmail.com>wrote:
>
>> I can configure VEs with both "ipv6 address" and "ipv6 enable" on my FCX.
>> What version of code are you running?
>>
>
> The config was accepted for me, and is now installed in 'sho ipv6 route'
> when removing follow-ve from the VE that I was configuring.
>
> However, I'm still unable to communicate with ipv6 hosts on a vlan from VE
> interface. tcpdump from connected host shows no traffic when trying to
> ipv6 ping from FCX to a host on ipv6 subnet on VE.
>
> SW: Version 08.0.00aT7f3
>
>
> Have you been able to successfully pass ipv6 traffic via VE?
>
>
> thanks,
>
> Mark
>
>

Hi Mark

We have a number of ICX switches in the lab, due to go into production in a
few weeks we hope.

Our vendor advises against 8.0.01 for the moment as "bleeding edge"

Do you have any further comment on your recommendation of 8.0.01 "for
unrelated reasons" please? :-)

Thanks!



*Justin Keery, Director*
Venus Business Communications Ltd
*FAST FIBRE INTERNET AND ETHERNET PRIVATE NETWORKS*
24 Denmark St, London WC2H 8NJ

VENUS
020 7240 5858
07976 153 984
www.venus.co.uk




On 8 November 2013 14:13, Matt Kassawara <mkassawara@gmail.com> wrote:

> I'm running 7.3.00a in production and 8.0.01 in the lab... both with IPv6
> working on VEs. Can you provide the rest of your configuration?
>
> P.S. - For unrelated reasons, I recommend upgrading to at least 8.0.01.
>
>
> On Fri, Nov 8, 2013 at 12:14 AM, Mark Price <mprice@tqhosting.com> wrote:
>
>>
>> Hi Matt,
>>
>> On Thu, Nov 7, 2013 at 4:08 PM, Matt Kassawara <mkassawara@gmail.com>wrote:
>>
>>> I can configure VEs with both "ipv6 address" and "ipv6 enable" on my
>>> FCX. What version of code are you running?
>>>
>>
>> The config was accepted for me, and is now installed in 'sho ipv6 route'
>> when removing follow-ve from the VE that I was configuring.
>>
>> However, I'm still unable to communicate with ipv6 hosts on a vlan from
>> VE interface. tcpdump from connected host shows no traffic when trying to
>> ipv6 ping from FCX to a host on ipv6 subnet on VE.
>>
>> SW: Version 08.0.00aT7f3
>>
>>
>> Have you been able to successfully pass ipv6 traffic via VE?
>>
>>
>> thanks,
>>
>> Mark
>>
>>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>

I ran 8.0.00a in the lab and lost any form of CLI access (including serial
console) on all of my ICX/FCX switches after a couple of weeks. I'm using
BNA and a couple of other utilities that connect to each switch via SSH
about once per minute which apparently exacerbates a memory leak in the
component managing CLI sessions. Upgrading to 8.0.01 resolved this issue
for me. However, I'm still running 7.x in my production environment.


On Fri, Nov 8, 2013 at 7:29 AM, Justin Keery <justin.keery@venus.co.uk>wrote:

>
> Hi Mark
>
> We have a number of ICX switches in the lab, due to go into production in
> a few weeks we hope.
>
> Our vendor advises against 8.0.01 for the moment as "bleeding edge"
>
> Do you have any further comment on your recommendation of 8.0.01 "for
> unrelated reasons" please? :-)
>
> Thanks!
>
>
>
> *Justin Keery, Director*
> Venus Business Communications Ltd
> *FAST FIBRE INTERNET AND ETHERNET PRIVATE NETWORKS*
> 24 Denmark St, London WC2H 8NJ
>
> VENUS
> 020 7240 5858
> 07976 153 984
> www.venus.co.uk
>
>
>
>
> On 8 November 2013 14:13, Matt Kassawara <mkassawara@gmail.com> wrote:
>
>> I'm running 7.3.00a in production and 8.0.01 in the lab... both with IPv6
>> working on VEs. Can you provide the rest of your configuration?
>>
>> P.S. - For unrelated reasons, I recommend upgrading to at least 8.0.01.
>>
>>
>> On Fri, Nov 8, 2013 at 12:14 AM, Mark Price <mprice@tqhosting.com> wrote:
>>
>>>
>>> Hi Matt,
>>>
>>> On Thu, Nov 7, 2013 at 4:08 PM, Matt Kassawara <mkassawara@gmail.com>wrote:
>>>
>>>> I can configure VEs with both "ipv6 address" and "ipv6 enable" on my
>>>> FCX. What version of code are you running?
>>>>
>>>
>>> The config was accepted for me, and is now installed in 'sho ipv6 route'
>>> when removing follow-ve from the VE that I was configuring.
>>>
>>> However, I'm still unable to communicate with ipv6 hosts on a vlan from
>>> VE interface. tcpdump from connected host shows no traffic when trying to
>>> ipv6 ping from FCX to a host on ipv6 subnet on VE.
>>>
>>> SW: Version 08.0.00aT7f3
>>>
>>>
>>> Have you been able to successfully pass ipv6 traffic via VE?
>>>
>>>
>>> thanks,
>>>
>>> Mark
>>>
>>>
>>
>> _______________________________________________
>> foundry-nsp mailing list
>> foundry-nsp@puck.nether.net
>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>>
>
>

I doubt your issue is this simple, but with Brocade/Foundry at least one physical interface assigned to the VLAN must be ‘up’ in order for the ve to be ‘up’ and therefore in the routing table. This is different from other vendors where the virtual interface can be ‘up’ by itself.

/Ryan

Ryan Harden
Senior Network Engineer
University of Chicago - ASN160
P: 773.834.5441

On Nov 7, 2013, at 12:13 PM, Mark Price <mprice@tqhosting.com> wrote:

>
> Hi all,
>
> Is anyone using layer3 IPv6 features on FCX?
>
> I enabled system-wide ipv6 with:
>
> ipv6 unicast-routing
>
> I can successfully configure IPv6 addresses on ethernet interfaces, and ping ipv6 across them.
>
> However, when I configure IPv6 on a VE interface (and "ipv6 enable" on the VE), the system doesn't seem to recognize it. I cannot ping the local ipv6 address, and it doesn't show up in "show ipv6 route"
>
>
> Mark
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp


_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

C6500's work the same way. Vlan (e.g. VE) has to be part of an 'UP'
interface (tagged or not) for the vlan itself to go 'UP'.

~Randy

On 11/08/2013 10:46 am, Ryan Harden wrote:
> I doubt your issue is this simple, but with Brocade/Foundry at least
> one physical interface assigned to the VLAN must be ‘up’ in order for
> the ve to be ‘up’ and therefore in the routing table. This is
> different from other vendors where the virtual interface can be ‘up’
> by itself.

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Vlans on a catalyst 6500 are up/up once you remove the shutdown command.

I just tested it.



-----Original Message-----
From: foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net] On Behalf Of Randy McAnally
Sent: Friday, November 08, 2013 12:41 PM
To: foundry-nsp@puck.nether.net
Subject: Re: [f-nsp] IPv6 on FCX

C6500's work the same way. Vlan (e.g. VE) has to be part of an 'UP'
interface (tagged or not) for the vlan itself to go 'UP'.

~Randy

On 11/08/2013 10:46 am, Ryan Harden wrote:
> I doubt your issue is this simple, but with Brocade/Foundry at least
> one physical interface assigned to the VLAN must be ‘up’ in order for
> the ve to be ‘up’ and therefore in the routing table. This is
> different from other vendors where the virtual interface can be ‘up’
> by itself.

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Not on SXI11, at least:

(config)#vlan 250
(config-vlan)#exit
(config)#int vlan 250
(config-if)#no sh
(config-if)#exit
(config)#do sh int vlan 250 | i proto
Vlan250 is down, line protocol is down
(config)#int t2/4
(config-if)#switchport trunk allowed vlan add 250
(config-if)#exit
(config)#do sh int vlan 250 | i proto
Vlan250 is up, line protocol is up

I ran into this a few months ago during initial setup as I honestly
wasn't expecting it. :)


~Randy

On 11/08/2013 2:48 pm, Joseph Jackson wrote:
> Vlans on a catalyst 6500 are up/up once you remove the shutdown
> command.
>
> I just tested it.
>
>
>
> -----Original Message-----
> From: foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net] On
> Behalf Of Randy McAnally
> Sent: Friday, November 08, 2013 12:41 PM
> To: foundry-nsp@puck.nether.net
> Subject: Re: [f-nsp] IPv6 on FCX
>
> C6500's work the same way. Vlan (e.g. VE) has to be part of an 'UP'
> interface (tagged or not) for the vlan itself to go 'UP'.
>
> ~Randy
>
> On 11/08/2013 10:46 am, Ryan Harden wrote:
>> I doubt your issue is this simple, but with Brocade/Foundry at least
>> one physical interface assigned to the VLAN must be ‘up’ in order for
>> the ve to be ‘up’ and therefore in the routing table. This is
>> different from other vendors where the virtual interface can be ‘up’
>> by itself.
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp

--
Randy McAnally
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Well then.. Color me shocked. I wonder when that changed - off to cisco.com



-----Original Message-----
From: Randy McAnally [mailto:rsm@fast-serv.com]
Sent: Friday, November 08, 2013 3:19 PM
To: Joseph Jackson
Cc: foundry-nsp@puck.nether.net
Subject: RE: [f-nsp] IPv6 on FCX

Not on SXI11, at least:

(config)#vlan 250
(config-vlan)#exit
(config)#int vlan 250
(config-if)#no sh
(config-if)#exit
(config)#do sh int vlan 250 | i proto
Vlan250 is down, line protocol is down
(config)#int t2/4
(config-if)#switchport trunk allowed vlan add 250 (config-if)#exit (config)#do sh int vlan 250 | i proto
Vlan250 is up, line protocol is up

I ran into this a few months ago during initial setup as I honestly wasn't expecting it. :)


~Randy

On 11/08/2013 2:48 pm, Joseph Jackson wrote:
> Vlans on a catalyst 6500 are up/up once you remove the shutdown
> command.
>
> I just tested it.
>
>
>
> -----Original Message-----
> From: foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net] On
> Behalf Of Randy McAnally
> Sent: Friday, November 08, 2013 12:41 PM
> To: foundry-nsp@puck.nether.net
> Subject: Re: [f-nsp] IPv6 on FCX
>
> C6500's work the same way. Vlan (e.g. VE) has to be part of an 'UP'
> interface (tagged or not) for the vlan itself to go 'UP'.
>
> ~Randy
>
> On 11/08/2013 10:46 am, Ryan Harden wrote:
>> I doubt your issue is this simple, but with Brocade/Foundry at least
>> one physical interface assigned to the VLAN must be ‘up’ in order for
>> the ve to be ‘up’ and therefore in the routing table. This is
>> different from other vendors where the virtual interface can be ‘up’
>> by itself.
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp

--
Randy McAnally

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Honestly I never really checked on previous releases. Would be curious
to know if/when this changed!

Kind-of makes sense to work this way though, I wouldn't want black-holes
going into OSPF, ect.

~Randy

On 11/08/2013 4:21 pm, Joseph Jackson wrote:
> Well then.. Color me shocked. I wonder when that changed - off to
> cisco.com
>
>
>
> -----Original Message-----
> From: Randy McAnally [mailto:rsm@fast-serv.com]
> Sent: Friday, November 08, 2013 3:19 PM
> To: Joseph Jackson
> Cc: foundry-nsp@puck.nether.net
> Subject: RE: [f-nsp] IPv6 on FCX
>
> Not on SXI11, at least:
>
> (config)#vlan 250
> (config-vlan)#exit
> (config)#int vlan 250
> (config-if)#no sh
> (config-if)#exit
> (config)#do sh int vlan 250 | i proto
> Vlan250 is down, line protocol is down
> (config)#int t2/4
> (config-if)#switchport trunk allowed vlan add 250 (config-if)#exit
> (config)#do sh int vlan 250 | i proto
> Vlan250 is up, line protocol is up
>
> I ran into this a few months ago during initial setup as I honestly
> wasn't expecting it. :)
>
>
> ~Randy
>
> On 11/08/2013 2:48 pm, Joseph Jackson wrote:
>> Vlans on a catalyst 6500 are up/up once you remove the shutdown
>> command.
>>
>> I just tested it.
>>
>>
>>
>> -----Original Message-----
>> From: foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net] On
>> Behalf Of Randy McAnally
>> Sent: Friday, November 08, 2013 12:41 PM
>> To: foundry-nsp@puck.nether.net
>> Subject: Re: [f-nsp] IPv6 on FCX
>>
>> C6500's work the same way. Vlan (e.g. VE) has to be part of an 'UP'
>> interface (tagged or not) for the vlan itself to go 'UP'.
>>
>> ~Randy
>>
>> On 11/08/2013 10:46 am, Ryan Harden wrote:
>>> I doubt your issue is this simple, but with Brocade/Foundry at least
>>> one physical interface assigned to the VLAN must be ‘up’ in order for
>>> the ve to be ‘up’ and therefore in the routing table. This is
>>> different from other vendors where the virtual interface can be ‘up’
>>> by itself.
>>
>> _______________________________________________
>> foundry-nsp mailing list
>> foundry-nsp@puck.nether.net
>> http://puck.nether.net/mailman/listinfo/foundry-nsp

--
Randy McAnally
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

>On 11/08/2013 4:21 pm, Joseph Jackson wrote:
>>Well then.. Color me shocked. I wonder when that changed - off to
>>cisco.com

* rsm@fast-serv.com (Randy McAnally) [Fri 08 Nov 2013, 22:27 CET]:
>Honestly I never really checked on previous releases. Would be
>curious to know if/when this changed!
>
>Kind-of makes sense to work this way though, I wouldn't want
>black-holes going into OSPF, ect.

It's been like that forever. The search keyword to use is 'autostate'.


-- Niels.

--
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

I was doing similar stuff on a C4900 very recently

If there's an interface up *which is allowed to pass the VLAN* (does not
have to be explicitly assinged), the VIF/VE will be up.

But if there are no interfaces which are allowed to pass the VLAN (ie
VLANSs are blocked by default, or need to be added explicitly etc) the
VIF/VE was down.




*Justin Keery, Director*
Venus Business Communications Ltd
*FAST FIBRE INTERNET AND ETHERNET PRIVATE NETWORKS*
24 Denmark St, London WC2H 8NJ

VENUS
020 7240 5858
07976 153 984
www.venus.co.uk




On 8 November 2013 19:48, Joseph Jackson <jjackson@aninetworks.net> wrote:

> Vlans on a catalyst 6500 are up/up once you remove the shutdown command.
>
> I just tested it.
>
>
>
> -----Original Message-----
> From: foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net] On Behalf
> Of Randy McAnally
> Sent: Friday, November 08, 2013 12:41 PM
> To: foundry-nsp@puck.nether.net
> Subject: Re: [f-nsp] IPv6 on FCX
>
> C6500's work the same way. Vlan (e.g. VE) has to be part of an 'UP'
> interface (tagged or not) for the vlan itself to go 'UP'.
>
> ~Randy
>
> On 11/08/2013 10:46 am, Ryan Harden wrote:
> > I doubt your issue is this simple, but with Brocade/Foundry at least
> > one physical interface assigned to the VLAN must be ‘up’ in order for
> > the ve to be ‘up’ and therefore in the routing table. This is
> > different from other vendors where the virtual interface can be ‘up’
> > by itself.
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp

Hi all, thanks for the responses regarding IPv6 routing on FCX.

I did get this working. One problem I encountered was due to "ip follow"
on my VEs. In order to activate IPv6 on the VE after adding IPv6 address,
I had to remove "ip follow ve #" and then re-apply "ip follow ve #"

I *think* this may have been caused by configuring ipv6 addresses on the
VEs before "ipv6 unicast-routing" global config was added.


Thanks,

Mark


On Fri, Nov 8, 2013 at 9:13 AM, Matt Kassawara <mkassawara@gmail.com> wrote:

> I'm running 7.3.00a in production and 8.0.01 in the lab... both with IPv6
> working on VEs. Can you provide the rest of your configuration?
>
> P.S. - For unrelated reasons, I recommend upgrading to at least 8.0.01.
>
>
>