N7K-F248XP-25E 32k Route limit

We have a nexus 7009 with N7K-F248XP-25E, the F2 is limited to 32k routes, how can this be bypass and use the 7k limit of 5.2mil routes? Does anyone know if it can.
Thanks.

No I dont see the way to increase it. Please find below details:
Nexus 7700 F3-Series 12-Port 100 Gigabit Ethernet Module
Layer 2 / Layer 3
12 x 100 Gbps (CPAK)
192 x wire-rate 100 Gigabit Ethernet ports are supported in a Nexus 7718 chassis
1.8 billion packets per second layer 2 and layer 3 IPv4 and IPv6 forwarding
1.2 Tbps of data throughput (2.4 Tbps full-duplex)
7710 and 7718 chassis
Supervisor Engine 2E
Fabric-2 Module (7010 and 7018 chassis)
4 ingress and 8 egress queues per port
Jumbo Frame Support
64K MAC addresses
4096 VLANs per VDC
64K IPv4 routes
32K IPv6 routes
Switch on Chip (SoC) ASIC
N77-F312CK-26
Nexus 7700 F3-Series 24-Port 40 Gigabit Ethernet Module
Layer 2 / Layer 3
24 x 40 Gbps (QSFP+)
384 x wire-rate 40 Gigabit Ethernet ports in a Nexus 7718 chassis
1.44 billion packets per second layer 2 and layer 3 IPv4 and IPv6 forwarding
960 Gbps data throughput (1.92 Tbps full-duplex)
7710 and 7718 chassis
Supervisor Engine 2E
Fabric-2 Module (7010 and 7018 chassis)
4 ingress and 8 egress queues per port
Jumbo Frame Support
64K MAC addresses
4096 VLANs per VDC
64K IPv4 routes
32K IPv6 routes
Switch on Chip (SoC) ASIC
N77-F324FQ-25
Nexus 7700 F3-Series 48-Port Fiber 1 and 10 Gigabit Ethernet Module
Layer 2 / Layer 3
48 x 1/10 Gbps (SFP and SFP+)
768 x wire-rate 10 Gigabit Ethernet ports in a single Nexus 7718 chassis
720 million packets per second layer 2 and layer 3 IPv4 and IPv6 forwarding
480 Gbps data throughput (960 Gbps full-duplex)
7706, 7710 and 7718 chassis
Supervisor Engine 2E
Fabric-2 Module (7010 and 7018 chassis)
4 ingress and 8 egress queues per port
Jumbo Frame Support
64K MAC addresses
4096 VLANs per VDC
64K IPv4 routes
32K IPv6 routes
Switch on Chip (SoC) ASIC
N77-F348XP-23
Nexus 7700 F2-Series Enhanced 48-Port Fiber 1 and 10 Gigabit Ethernet Module
Layer 2 / Layer 3
48 x 1/10 Gbps (SFP and SFP+)
768 x wire-rate 10 Gigabit Ethernet ports in a single Nexus 7718 chassis
720 million packets per second layer 2 and layer 3 IPv4 and IPv6 forwarding
480 Gbps data throughput (960 Gbps full-duplex)
7706, 7710 and 7718 chassis
Supervisor Engine 2E
Fabric-2 Module (7010 and 7018 chassis)
4 ingress and 4 egress queues per port
Jumbo Frame Support
16K MAC addresses
4096 VLANs per VDC
32K IPv4 routes
16K IPv6 routes
Switch on Chip (SoC) ASIC
N77-F248XP-23E
NX-OS 6.2.2+
Nexus 7000 F3-Series 6-Port 100 Gigabit Ethernet Module
Layer 2 / Layer 3
6 x 100 Gbps (CPAK)
96 x wire-rate 100 Gigabit Ethernet ports in a single Nexus 7018 chassis
900 million packets per second layer 2 and layer 3 IPv4 and IPv6 forwarding
600 Gbps data throughput (1.2 Tbps full-duplex)
7004, 7009, 7010 and 7018 chassis
Supervisor Engine 1, 2 and 2E
Fabric-1 Module (7010 and 7018 chassis), Fabric-2 Module (7009, 7010, 7018 chassis)
4 ingress and 4 egress queues per port
Jumbo Frame Support
64K MAC addresses
4096 VLANs per VDC
64K IPv4 routes
32K IPv6 routes
Switch on Chip (SoC) ASIC
N7K-F306CK-25
Nexus 7000 F3-Series 12-Port 40 Gigabit Ethernet Module
Layer 2 / Layer 3
12 x 40 Gbps (QSFP+)
192 x wire-rate 40 Gigabit Ethernet ports in a single Nexus 7018 chassis
720 million packets per second layer 2 and layer 3 IPv4 and IPv6 forwarding
480 Gbps data throughput (960 Gbps full-duplex)
7004, 7009, 7010 and 7018 chassis
Supervisor Engine 1, 2 and 2E
Fabric-1 Module (7010 and 7018 chassis), Fabric-2 Module (7009, 7010, 7018 chassis)
4 ingress and 4 egress queues per port
Jumbo Frame Support
64K MAC addresses
4096 VLANs per VDC
64K IPv4 routes
32K IPv6 routes
Switch on Chip (SoC) ASIC
N7K-F312FQ-25
Nexus 7000 F2-Series Enhanced 48-Port Fiber 1 and 10 Gigabit Ethernet Module
Layer 2 / Layer 3
48 x 1/10 Gbps (SFP and SFP+)
768 x wire-rate 10 Gigabit Ethernet ports in a single Nexus 7018 chassis
720 million packets per second layer 2 and layer 3 IPv4 and IPv6 forwarding
480 Gbps data throughput (960 Gbps full-duplex)
7004, 7009, 7010 and 7018 chassis
Supervisor Engine 1, 2 and 2E
Fabric-1 Module (7010 and 7018 chassis), Fabric-2 Module (7009, 7010, 7018 chassis)
4 ingress and 4 egress queues per port
Jumbo Frame Support
16K MAC addresses
4096 VLANs per VDC
32K IPv4 routes
16K IPv6 routes
Switch on Chip (SoC) ASIC
N7K-F248XP-25E
NX-OS 6.1.2+
Nexus 7000 F2-Series Enhanced 48-Port 1 and 10GBASE-T Ethernet Copper Module
Layer 2 / Layer 3
48 x 1/10 Gbps (RJ-45)
768 x wire-rate 10GBase-T Ethernet ports in a single Nexus 7018 chassis
720 million packets per second layer 2 and layer 3 IPv4 and IPv6 forwarding
480 Gbps data throughput (960 Gbps full-duplex)
7004, 7009, 7010 and 7018 chassis
Supervisor Engine 1, 2 and 2E
Fabric-1 Module (7010 and 7018 chassis), Fabric-2 Module (7009, 7010, 7018 chassis)
4 ingress and 4 egress queues per port
Jumbo Frame Support
16K MAC addresses
4096 VLANs per VDC
32K IPv4 routes
16K IPv6 routes
Switch on Chip (SoC) ASIC
N7K-F248XT-25E
NX-OS 6.1.2+
Nexus 7000 F2-Series 48-Port 1 and 10 Gigabit Ethernet Module
Layer 2 / Layer 3
48 x 1/10 Gbps (SFP and SFP+)
768 x wire-rate 10 Gigabit Ethernet ports in a single Nexus 7018 chassis
720 million packets per second layer 2 and layer 3 IPv4 and IPv6 forwarding
480 Gbps data throughput (960 Gbps full-duplex)
7004, 7009, 7010 and 7018 chassis
Supervisor Engine 1, 2 and 2E
Fabric-1 Module (7010 and 7018 chassis), Fabric-2 Module (7009, 7010, 7018 chassis)
4 ingress and 4 egress queues per port
Jumbo Frame Support
16K MAC addresses
4096 VLANs per VDC
32K IPv4 routes
16K IPv6 routes
Switch on Chip (SoC) ASIC
N7K-F248XP-25
NX-OS 6.0+
Nexus 7000 F1-Series 32-Port 1 and 10 Gigabit Ethernet Module
Layer 2
32 x 1/10 Gbps (SFP and SFP+)
512 x wire-rate 10 Gigabit Ethernet ports in a single Nexus 7018 chassis
480 million packets per second layer 2 forwarding
320 Gbps data throughput (640 Gbps full-duplex)
7009, 7010 and 7018 chassis
Supervisor Engine 1, 2 and 2E
Fabric-1 Module (7010 and 7018 chassis), Fabric-2 Module (7009, 7010, 7018 chassis)
4 ingress and 8 egress queues per port
Jumbo Frame Support
256K MAC addresses
16K VLANs per module
N7K-F132XP-15
NX-OS 5.1.1
Nexus 7000 M2-Series 24-Port 10 Gigabit Ethernet Module with XL Option
Layer 2 / Layer 3
24 x 10 Gbps (SFP+)
384 x wire-rate 10 Gigabit Ethernet ports in a single Nexus 7018 chassis
120 million packets per second layer 2 and layer 3 IPv4 forwarding and 60 mpps IPv6
550 Gbps data throughput (1.1 Tbps full-duplex)
7004, 7009, 7010 and 7018 chassis
Supervisor Engine 1, 2 and 2E
Fabric-1 Module (7010 and 7018 chassis), Fabric-2 Module (7009, 7010, 7018 chassis)
8 ingress and 8 egress queues per port
Jumbo Frame Support
128K MAC addresses
4096 VLANs per VDC
1M IPv4 routes
350K IPv6 routes
N7K-M224XP-23L
NX-OS 6.1+
Nexus 7000 M2-Series 6-Port 40 Gigabit Ethernet Module with XL Option
Layer 2 / Layer 3
6 x 40 Gbps (QSFP+)
96 x wire-rate 40 Gigabit Ethernet and 10 Gbps ports in a Nexus 7018 chassis
120 million packets per second layer 2 and layer 3 IPv4 forwarding and 60 mpps IPv6
550 Gbps data throughput (1.1 Tbps full-duplex)
7004, 7009, 7010 and 7018 chassis
Supervisor Engine 1, 2 and 2E
Fabric-1 Module (7010 and 7018 chassis), Fabric-2 Module (7009, 7010, 7018 chassis)
8 ingress and 8 egress queues per port
Jumbo Frame Support
128K MAC addresses
4096 VLANs per VDC
1M IPv4 routes
350K IPv6 routes
N7K-M206FQ-23L
NX-OS 6.1+
Nexus 7000 M2-Series 2-Port 100 Gigabit Ethernet Module with XL Option
Layer 2 / Layer 3
2 x 100 Gbps (CFP)
32 x wire-rate 100 Gigabit Ethernet ports in a single Nexus 7018 chassis
120 million packets per second layer 2 and layer 3 IPv4 forwarding and 60 mpps IPv6
550 Gbps of data throughput (1.1 Tbps full-duplex)
7004, 7009, 7010 and 7018 chassis
Supervisor Engine 1, 2 and 2E
Fabric-1 Module (7010 and 7018 chassis), Fabric-2 Module (7009, 7010, 7018 chassis)
8 ingress and 8 egress queues per port
Jumbo Frame Support
128K MAC addresses
4096 VLANs per VDC
1M IPv4 routes
350K IPv6 routes
N7K-M202CF-22L
NX-OS 6.1+
Nexus 7000 M1-Series 8-Port 10 Gigabit Ethernet Module with XL Option
Layer 2 / Layer 3
8 x 10 Gbps (X2)
128 x wire-rate 10 Gigabit Ethernet ports in a single Nexus 7018 chassis
120 million packets per second layer 2 and layer 3 IPv4 forwarding and 60 mpps IPv6
80 Gbps of data throughput (160 Gbps full-duplex)
7004, 7009, 7010 and 7018 chassis
Supervisor Engine 1, 2 and 2E
Fabric-1 Module (7010 and 7018 chassis), Fabric-2 Module (7009, 7010, 7018 chassis)
8 ingress and 8 egress queues per port
Jumbo Frame Support
128K MAC addresses
4096 VLANs per VDC
1M IPv4 routes
350K IPv6 routes
N7K-M108X2-12L
NX-OS 5.0+
Nexus 7000 M1-Series 32-Port 10 Gigabit Ethernet Module with XL Option
Layer 2 / Layer 3
32 x 10 Gbps (SFP+)
512 x 10 Gigabit Ethernet ports in a single Nexus 7018 chassis
60 million packets per second layer 2 and layer 3 IPv4 forwarding and 30 mpps IPv6
80 Gbps of data throughput (160 Gbps full-duplex)
7004, 7009, 7010 and 7018 chassis
Supervisor Engine 1, 2 and 2E
Fabric-1 Module (7010 and 7018 chassis), Fabric-2 Module (7009, 7010, 7018 chassis)
8 ingress and 8 egress queues per port
Jumbo Frame Support
128K MAC addresses
4096 VLANs per VDC
1M IPv4 routes
350K IPv6 routes
4:1 oversubscription
N7K-M132XP-12L
NX-OS 5.1+
Nexus 7000 M1-Series 48-Port Gigabit Ethernet Modules with XL Option
Layer 2 / Layer 3
48 x 1 Gbps (SFP/RJ45)
768 x Gigabit Ethernet (SFP) or 10/100/1000 (RJ45) ports in Nexus 7018 chassis
60 million packets per second layer 2 and layer 3 IPv4 forwarding and 30 mpps IPv6
46 Gbps of data throughput (92 Gbps full-duplex)
7004, 7009, 7010 and 7018 chassis
Supervisor Engine 1, 2 and 2E
Fabric-1 Module (7010 and 7018 chassis), Fabric-2 Module (7009, 7010, 7018 chassis)
2 ingress and 4 egress queues per port
Jumbo Frame Support
128K MAC addresses
4096 VLANs per VDC
1M IPv4 routes
350K IPv6 routes
Some oversubscription
N7K-M148GS-11L
NX-OS 5.0 (SFP) / 5.1+ (RJ45)
Nexus 7000 M1-Series 32-Port 10 Gigabit Ethernet Module
Layer 2 / Layer 3
32 x 10 Gbps (SFP+)
512 x 10 Gigabit Ethernet ports in a single Nexus 7018 chassis
60 million packets per second layer 2 and layer 3 IPv4 forwarding and 30 mpps IPv6
80 Gbps of data throughput (160 Gbps full-duplex)
7009, 7010 and 7018 chassis
Supervisor Engine 1, 2 and 2E
Fabric-1 Module (7010 and 7018 chassis), Fabric-2 Module (7009, 7010, 7018 chassis)
8 ingress and 8 egress queues per port
Jumbo Frame Support
128K MAC addresses
4096 VLANs per VDC
128K FIB routes
4:1 oversubscription
N7K-M132XP-12
NX-OS 4.0+
Nexus 7000 M1-Series 48-Port Gigabit Ethernet Modules
Layer 2 / Layer 3
48 x 1 Gbps (SFP/RJ45)
768 x 10/100/1000 RJ45 or Gigabit Ethernet (SFP) ports in Nexus 7018 chassis
60 million packets per second layer 2 and layer 3 IPv4 forwarding and 30 mpps IPv6
46 Gbps of data throughput (92 Gbps full-duplex)
7009, 7010 and 7018 chassis
Supervisor Engine 1, 2 and 2E
Fabric-1 Module (7010 and 7018 chassis), Fabric-2 Module (7009, 7010, 7018 chassis)
2 ingress and 4 egress queues per port
Jumbo Frame Support
128K MAC addresses
4096 VLANs per VDC
128K FIB routes
Some oversubscription
N7K-M148GT-11
NX-OS 4.1+ (SFP) / 4.0+ (RJ45)

Similar Messages

How to do routing on N7K-F248XP-25E (Nexus 7010) ?

Hi all,
Please educate me the following scenario : I have Nexus 7010 with 2 L3 modules, N7K-M132XP-12L and N7K-M148GT-11L. Now to increase more ports for end devices, I add in the module N7K-F248XP-25E and believe it's for Layer 2 switching only. Is there a way to do routing on these L2 modules without having to go to the L3 modules ? Thanks for all help.

Is there a way to do routing on these L2 modules without having to go to the L3 modules ?
No. If you have an M1/M2 card and routing is enabled, the F2E card will "step down" and do Layer 2 work. All Layer 3 work will be done by the M1/M2 card.

10Gig Copper SFP for Nexus F Series module (N7K-F248XP-25E)

Does Cisco have 10Gig Copper SFP which can be supported on Nexus platform in the F Series module (N7K-F248XP-25E)

Leo,
Thank you for the answer, you mentioned 10Gig Copper module in your reply (Part# N7K-F248XT-25E) but I already have Fiber Module (Part# N7K-F248XP-25E), I just need 2 10Gig copper ports for my storage and cant afford to buy a whole new Copper module. My question was if there is any 10Gig Copper SFP supported on F Series Fiber Module (Part# N7K-F248XP-25E), (not a twinax/DAC cable since my distance is longer and Twinax wont work)

Does the F2 linecard (N7k-F248XP-25) on Nexus 7010 support Layer 3?

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

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.

Nexus 7009 does not show the N7K-F248XP-25 modules ethernet ports n sh run

Hi everyone,
I have a question...
I going to install two Nexus 7009 with three N7K-F248XP-25 modules on each one, I am planning to create 3 VDC, but at the initial configuration the system does not show the Ethernet ports of these modules, even with the show inventory and show module I can see that the modules are recognized and its status is OK. There is something that I have to do before start to configure these modules...? enable some feature or license in order to see the ports with show running CLI...?

You can enable F1, F2, M1, M1XL and M2XL Series modules. There are no restrictions on the type of mix allowed for the system module-type command. The system module-type command allows a mix of F1, F2, M1, M1XL, and M2XL Series modules in the VDC.
Note The limit-resource module-type command controls the restrictions on the module-types that can be mixed in the VDC.
Note Use the system module-type f2 command to allow F2E Series modules into a VDC. The ports from F2 and F2E Series modules can be allocated like any other ports.
Note The modules that you do not enable must not be powered on after you configure this feature and enter yes. An error message will force you to manually disable these modules before proceeding. This prevents major disruption and service issues within a VDC.
The no form of this command resets the configuration mode to allow all modules.
hope this helps

N7K-F248XP-25 VDC licensing

Hi All
My clients want 2
N7K-F248XP-25
and 1 N7K-M148GS-11
So how many N7K-ADV1K9 license i must take?
1 for M1 and 2 for F2
or
1 for M1 and 1 for F2..
My chassis is;
N7K-C7010-BUN2-R

Hi Robert,
The F2 module is L2 and L3 capable. It is quite a step up from F1 as it has no L3 capabilites, plus adding FEX to the F2 is a great improvement. As far as F2 vs M1, the M1 still has larger L3 tables and can hold more routes in hardware as well as run OTV. So the two types of modules are for different locations in your data center. M1 is a great fit for your routing edge due to this.
Lucinao,
For fabric 2 on 7010 and 7018 you must have NX-OS 6.
As far as the new VDC requirement for F2. Since the Nexus 7000s modules all have their own forwarding engines they must all run in a compatible mode. Think of it like mixing a 6500 with sup2 and a module with a DFC3...you can't do it.
So instead of just saying your chassis can only contain F2 or F1/M1 we are able to seperate the "generations" up by VDCs within the same chassis.
Chad

New N7K-F248XP-25

Ciao,
in my previous post I understand that this linecard will be officially released on 18th ... and today I discovered something new in the DS published.
"This extremely comprehensive set of Layer 2 and Layer 3 functions makes this module ideal for data center networks, where density, performance, and continuous system operation are critical."
Performance
• 720-mpps Layer 2 and Layer 3 forwarding capacity for both IPv4 and IPv6 packets
The DS is here:
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/data_sheet_c78-685394.html
is this new linecard N7K-F248XP-25 a L2/L3 like the M series???
And, according to the Dynamic Configuration Tool it's stated:
"A separate VDC is needed when deploying the N7K-F248XP-25 modules in a chassis that also contains other families of modules (i.e. N7K-M1xxx and N7K-F1xxx).The VDC feature is enabled by the N7K-ADV1K9 license. A separate VDC is NOT required when the chassis contains only N7K-F248XP-25 modules."
And also NX-OS Version 6 required ...
Any ideas??
Ciao e grazie!
Luciano

Hi Robert,
The F2 module is L2 and L3 capable. It is quite a step up from F1 as it has no L3 capabilites, plus adding FEX to the F2 is a great improvement. As far as F2 vs M1, the M1 still has larger L3 tables and can hold more routes in hardware as well as run OTV. So the two types of modules are for different locations in your data center. M1 is a great fit for your routing edge due to this.
Lucinao,
For fabric 2 on 7010 and 7018 you must have NX-OS 6.
As far as the new VDC requirement for F2. Since the Nexus 7000s modules all have their own forwarding engines they must all run in a compatible mode. Think of it like mixing a 6500 with sup2 and a module with a DFC3...you can't do it.
So instead of just saying your chassis can only contain F2 or F1/M1 we are able to seperate the "generations" up by VDCs within the same chassis.
Chad

Input pattern or replacement parameters exceed 32K size limit

Hi,
Following is my code
declare
v_clob1 clob := empty_clob;
v_clob2 clob := empty_clob;
begin
select result into v_clob2 from evex_output_copy where evex_output_uid = 1;
v_clob1 := 'a';
v_clob1 := replace(v_clob1, 'a', v_clob2);
end;
the length of v_clob2 is greater than 32K.
It shows the following error.
input pattern or replacement parameters exceed 32K size limit
How can I solve this ?
Ivan

Try the DBMS_LOB.copy procedure.

Hitting the 32k size limit with Keyword Expansion in packages

Hi!
I am hitting the 32k size limit with Keyword Expansion (KE). It is hardcoded in the procedure jr_keyword.analyze_mlt.
Are there any plans to get rid of this limit, so package bodies with size > 32000 bytes can be expanded?

Well, I am making progress. With a combination if utl_tcp.get_line() - to trap the header and utl_tcp.get_text - to get the data at 32K chunks - which I then put into a CLOB or VARRAY of VARCHAR2; I can get as much data as is sent.
The problem now is speed.
It takes over 60 seconds to get 160K (5 32K chunks) of data when I put it into the VARRAY of VARCHAR2, and it takes even longer if I use dbms_lob.write() and dbms_lob.writeappend() to store the data.
Am I doing something wrong? Is there another way?
Thank You for any Help.
Shannon

What is the difference between N7K-F248XT-25E-P1 and N7K-F248XT-25E?

I can see that there are 2 part number for Cisco Nexus 7000 Enhanced F2-Series 48-Port 1 and 10GBASE-T Ethernet Copper Module. One is
N7K-F248XT-25E-P1 and the other is N7K-F248XT-25E. What is the difference between them?

Hi Arshad,
It was from a presentation posted to the Partners section of the Cisco communities site. If you have access to the Partner Data Centre section of the site you can get the document at Nexus 7K F2e 1/10GbaseT Promotion.
If you personally don't have access to the document, then someone from your Cisco sales team should be able to get provide you with the details.
Regards

32k Rowsize Limit (ORA-006502) for Report Query Shared Objects in Apex 4.1

We're trying to move legacy reports off of PlanetPress into Apex. One of the report queries has over 20 tables and attempting to run with the "Test Report" button in the Edit Report Query screen gets the error message:
Error ORA-06502: PL/SQL: numeric or value error: character string buffer too small
This problem appears to have been characterized previously here:
Listener Error - character string buffer too small (ORA-06502)
If I comment out 13 lines/items in my SELECT clause, the Test Report runs okay. If I add back in an innocuous literal sellect of a 100-character string, it goes back to the 6502 error.
I was trying to add more literal strings to force APEX to shift internally from a 32k-limit to a CLOB for the row, however, with a 32k literal string in my SQL statement, APEX crashes. I can't strip out columns from my SQL as all are needed for the report.
I would very much appreciate a work-around or a patch to Apex 4.1 to address this limitation. Thank you.

Try moving some of your select logic into a view, thus you can select from the views and reduce your code... (Move the joining between tables and such to the view..)
Thank you,
Tony Miller
Webster, TX

Help to overcome 32K XML limit for Anychart Map

Hello,
Apex version 4.2.0.00.27
I am creating a heat map using the Anychart maps and have chosen to use the "Use custom XML" option in the Map Attributes to control the map being generated. However, I have hit a 32K limit for 'Custom XML' that is being passed to the Map.
A sample of the XML is:
<?xml version="1.0" encoding="UTF-8"?>
<anychart>
<charts>
<chart plot_type="Map">
<b>&P_MAPXML.</b>
<palettes>
</palettes>
</chart>
</charts>
</anychart>
I am using a procedure to generate the required XML and have created an Application Item (P_MAPXML) to hold the data. When P_MAPXML along with the enclosing XML is less than 32K then map dispalys correctly. If the XML generated is more than 32K then an error occurs as it truncates P_MAPXML and the Custom XML is no longer well formed.
There is a workaound via an old thread AnyChart gantt with custom xml and more then 32k but I was wondering is there a more upto date solution.
Edited by: user11899724 on 15-Apr-2013 04:45

Thanks Hiliary,
I soldiered on before I saw your reply.
I basically wanted an example of the minimum necessary to display an Anychart Map via the javascript method as there seemed to be issues with the examples that were on the forums not least assuming that every step was understood.
Anyway below I have put steps together just to display an Anychart Map and then along with your example above or the others from the Forum it can be customized to display dynamic data.
1. Create a new page within Apex
i) Under Application choose Create Page -> Blank Page -> Page Alias - (type: WorldMap) -> Name (type: World Map) -> ->Finish
2) Click Edit Page
3) Right Click on Region , Choose Create -> Click PL/Sql Dynamic Content ->Title (type: World Map) ->
Under Pl/SQL Source cut and paste the following:
<pre>
htp.prn('<textarea cols="500" rows="100" id="rowData" style="display:none">');
htp.prn('<anychart>
<charts>
<chart plot_type="Map">
<chart_settings>
<title enabled="true"><text>World Map</text></title>
<chart_background enabled="false"/>
<data_plot_background enabled="false"/>
</chart_settings>
<data_plot_settings>
<map_series source="world/world.amap">
<projection type="Mercator" centroid_x="10.4515266418457" centroid_y="51.1656913757324"/>
<undefined_map_region>
     <tooltip_settings enabled="true">
               <format>{%REGION_NAME}</format>
          </tooltip_settings>
          <label_settings enabled="true">
               <format>{%REGION_NAME}</format>
          </label_settings>
     </undefined_map_region>
     </map_series>
</data_plot_settings>
<data>
</data>
</chart>
</charts>
</anychart>');
htp.prn('</textarea>');
-- Line below seems to be coming out blank, should be:"
htp.prn('<div id="chartMap"></div>');
htp.prn('<script type="text/javascript" language="javascript" src="/i/flashchart/js/AnyChart.js"></script>
<script type="text/javascript" language="javascript">
AnyChart.swfFile = ''/i/flashchart/swf/AnyChart.swf'';
var chart = new AnyChart();
chart.width = "800";
chart.height = "400";
var data = document.getElementById("rowData").value.toString();
chart.setData(data);
chart.write("chartMap");
// alert(data);
</script>');
</pre>
Click Create Region
4) Run the Page.
If all is well it shoulld display the World Map, just be careful with the div tag line as that will need to added manually.
As said previously, there's lots of help on the forums about creating the dynamic content but this should be a good place to start, having a map that will display using that method.

32K ActionScript Limit

Regarding the following FAQ:
http://www.adobe.com/devnet/flex/articles/flexfaq.html#itemA-24
I need a little clarification.
I want to implement the suggested fix of putting in extra
code to force the compiler to break at a different place. However,
I wanted to know, if anyone has experience with it, whether this
hack will be a long-term solution, or will we be constantly needing
to change the amount of extra code as the number of options on the
form in question grows.
This is an Intranet application built in ColdFusion Flash
Forms.

Tracy,
Thanks for the response. I was afraid that was going to be
the answer.
We are still on Flex 1.5 in this particular situation because
we are using ColdFusion's "Flash Forms" feature to generate the
code. Unfortunately, Adobe used Flex 1.5 within ColdFusion to
create this feature; and it has not been upgraded. As far as I
know, there are no plans to ever upgrade this feature in
ColdFusion. That probably isn't a bad thing, since the feature is
very limited on a number of levels.
We do our real Flex work in 2.0, soon to be 3.0. This was a
"quick and dirty" project with "simple" use cases and requirements
that grew into something that is now kinda stretching the linits of
what can be done without using real Flex.

Change VDC type on n7k sup1

Hi.
I have a pair of Nexus 7010 with sup1 running 6.2(8)
There is default VDC only:
# sh vdc detail
Switchwide mode is m1 f1 m1xl f2 m2xl f2e f3
vdc id: 1
vdc name: nex7010-12
vdc state: active
vdc mac address: 40:55:39:23:1e:c1
vdc ha policy: RELOAD
vdc dual-sup ha policy: SWITCHOVER
vdc boot Order: 1
vdc create time: Tue Dec 20 11:23:37 2011
vdc reload count: 0
vdc uptime: 989 day(s), 22 hour(s), 10 minute(s), 34 second(s)
vdc restart count: 0
vdc type: Ethernet
vdc supported linecards: m1 f1 m1xl m2xl
I want to add N7K-F248XP-25E line card. So as I understand I should enter
(config)# vdc nex7010-11 id 1
(config-vdc)# limit-resource module-type m1 f1 m1xl m2xl f2e
And then insert line card. Is this right?
So my questions. Is this operation disruptive to traffic forwarding? Do I lost allocated interface and/or limit-resources after change VDC type and need to retype them again?

Hi insharie,
thanks for fast answer :)
My config:
Model
N7K-M148GT-11
N7K-M148GT-11
N7K-M148GT-11
N7K-M148GT-11
N7K-SUP1
N7K-SUP1
N7K-M108X2-12L
N7K-M108X2-12L
N7K-F132XP-15
So there is no F2 line cards.
I want to add F2e - N7K-F248XP-25E line card.
In "Cisco Nexus 7000 Series NX-OS VDC Configuration Guide":
"Beginning with Cisco NX-OS Release 6.2(2), F2e module type can exist with M1, M1XL, and M2XL module types in the same VDC."
And as I understand F2e will be working in Proxy Mode
"When you enter the limit-resource module-type command and it changes the F2e mode between the old VDC type and the new VDC type, you are prompted to enter the rebind interface command"
From the table "Table 7 VDC Types Impacted By F2e Proxy Mode" I do not see my case
Old VDC: M1,F1 --> New VDC: M1,F1,F2e
And can not figure out the impact.

OTV Connecting M1 ports to F2 ports

HI Guyz,
I am Designing a OTV Topology, where i have M1 series card (N7K-M108X2-12L) in OTV VDC & F2 Series card (N7K-F248XP-25E) in Aggregation VDC.
I need to connect M1 interface as its OTV INTERNAL interface to F2 interface in Aggregation VDC to learns local mac-addr.
i will dual hommed M1 interfaces from OTV VDC to 2 different 7K aggregation VDC using VPC.
as shown in fig Link-3 & 4 will be vpc member ports for 7K-A , 7K-B.
Are there any Limitations for connecting M1 interface direcltly to F2 interface , as shown above OTV VDC M1 port connects to Aggn VDC F2 port.???
thanks,
Mazhar

The only requirement to deploy OTV is the join interface must be in the M-module or F3 module (not avaliable for Nexus 7000 platform yet, only Nexus 7700).
The OTV internal interface, can be a M1 or even F-card in the lastest release.
About mix F2e with M1 modules, when you do that, the F2e routing capability is disabled, so all routing decision will be proxied to the M-module. This routing capacity is limited by the quatity of ports M that you have in your VDC.
http://www.cisco.com/en/US/docs/switches/datacenter/sw/nx-os/virtual_device_context/configuration/guide/vdc_mgmt.html#wp1263392

N7K-F248XP-25E 32k Route limit

Similar Messages

Maybe you are looking for