01-26-2012 07:11 PM - edited 03-07-2019 04:34 AM
Hi All,
I am sure that F1 linecards on Nexus weren’t able to support L3 functionality, so my query is does the F2 linecard (N7k-F248XP-25) on Nexus 7010 support Layer 3?
Regards,
Mayank
Solved! Go to Solution.
01-26-2012 07:42 PM
Hello,
Yes F2 does support both L2 and L3 (plus some other additional functions).
You may check specifications here:
http://www.cisco.com/en/US/partner/prod/collateral/switches/ps9441/ps9402/data_sheet_c78-685394.html
and here:
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/at_a_glance_c45-689339.pdf
One restriction - F2 can't work with M1 or F1 line cards in same VDC, so F2 line cards should be set in separate VDC.
Hope this helps,
Nik
01-26-2012 07:42 PM
Hello,
Yes F2 does support both L2 and L3 (plus some other additional functions).
You may check specifications here:
http://www.cisco.com/en/US/partner/prod/collateral/switches/ps9441/ps9402/data_sheet_c78-685394.html
and here:
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/at_a_glance_c45-689339.pdf
One restriction - F2 can't work with M1 or F1 line cards in same VDC, so F2 line cards should be set in separate VDC.
Hope this helps,
Nik
01-26-2012 07:47 PM
Hi Nikolay,
Thanks for the confirmation.
Cheers!
09-06-2013 08:50 AM
Hi, Im know that this is resolved but i have a f2e Card
Model: N7K-F248XP-25E
Type (SFP capable): 1000base-SX
and i can not configure an interface as l3
NX7K-1-VDC-3T-S1-L3FP(config)# interface ethernet 7/2
NX7K-1-VDC-3T-S1-L3FP(config-if)# no switchport
ERROR: Ethernet7/2: requested config change not allowed
whats the problem??
Software
BIOS: version 2.12.0
kickstart: version 6.2(2)
system: version 6.2(2)
BIOS compile time: 05/29/2013
kickstart image file is: bootflash:///n7000-s2-kickstart-npe.6.2.2.bin
kickstart compile time: 7/9/2013 20:00:00 [08/22/2013 04:51:27]
system image file is: bootflash:///n7000-s2-dk9.6.2.2.bin
system compile time: 7/9/2013 20:00:00 [08/22/2013 08:07:03]
Hardware
cisco Nexus7000 C7010 (10 Slot) Chassis ("Supervisor Module-2")
Intel(R) Xeon(R) CPU with 12224956 kB of memory.
09-25-2013 02:14 AM
Salvador,
I had the same issue. It seems to be how the card is configured in the admin VDC. By default I believe it's in L2 only mode.
The most likely cause is that the default VDC type is M1/F2E and you need to convert that to F2E only VDC(vdc limit-resource module-type ) if you want to operate your F2E line card in Layer 3 mode.
to confirm: sh vdc
and if this is the case:
(All from within the admin VDC).
conf t
vdc xyz <<< (Note, not 'switchto' vdc)
limit-resource module-type f2e
Then follow the instructions regarding 'rebind interface'. All physical interfaces need to be re-initialised in order to pickup their new role. Some of the physical interface commands will change slighlty too. 'Rebind Interface' is also run from the admin VDC, not the production VDC.
After this, all physical interfaces will be L3 by default, not L2 as before. You can switch them back to L2 with the 'switchport' interface command. Much like a L3 6500 from here on out. L3 routed inerfaces and SVI's configured in the traditional way.
Dave.
01-24-2014 09:23 AM
I was having an issue configuring interface VLANs (SVI). I could create the SVI, but when I did a "no shutdown" then a "show interface" it was "down (Non-routable VDC mode)." I have the appropriate licenses installed. I then tried to change one of my switchports to a routed port, just like Salvador, but that did not work. I found this post and limited the module type to f2e (previously was allowing m1 m1xl m2xl f2e), recreated the interface VLAN, did a "no shut," it came "up/up," and I was able to ping across my trunk.
Thanks a bunch Dave!
02-04-2014 05:51 AM
Glad it helped you, David!
Slightly obscure, and specific to Nexus, so though it was worth sharing.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: