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.

Similar Messages

  • 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)

  • 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)

  • How to download MIB for NXOS or platform Nexus 7010 and Nexus 7004

    Hello,
    I need to monitor my Nexus 7004 and 7010 by my SNMP Agent, but I can't find the way to donload the required MIBs.
    For information I'm running the folling images:
    bootflash:///n7000-s2-dk9.6.2.6b.bin
    bootflash:///n7000-s1-dk9.6.1.5.bin
    By advance thanks for the support
    Gildas

    The module you are running requires a minimum software version of 5.1.
    You are currently running 5.0.3 which is why the module is not
    recognized.
    Below is a link that explains this:
    http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/data_s
    heet_c78-605482.html
    Product Specification
    Table 3 lists the specifications for the Cisco Nexus 7000 32-Port 10 Gigabit Ethernet
    Module with XL Option.
    Table 3. Product Specifications
    Item
    Specifications
    System
    Product compatibility
    Supported in all Cisco Nexus 7000 Series chassis
    Software compatibility
    Cisco NX-OS Software Release 5.1 or later (minimum requirement)
    You would need to upgrade you software.
    Hope this helps.
    Regards
    Muhammed M

  • 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.

  • 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

  • How to re-route source & gate for Buffered Period in DAmx

    I am trying to write a DAQmx program that does the follow :
    (1) creates 1 PulseTrain task; this task routes is output to a requested pin with will be used as a SOURCE for a Buffered Period task.
    (2) if requested creates a second PulseTrain who's output will be used as the Buffered Period GATE.
    (3) the Buffered period task needs to assign ANY SOURCE,GATE and run till its stopped by the user.
    Note that this task needs to "sample/read" its data and show it to the user.
    My questions are :
    (a) is the PulseTrain "output" re-route done OK ?
    (b) how to re-route the Period source/gate - I used DAQmxSetChanAttribute, but I an not sure it is right
    ©) how to make the Period task write the data into "my program buffer" so I do not have to read it when "stop" is pressed.
    I try to run with simulated devices on a P4 3.2GHZ running XP :
    First TrainPulse - ctr0, out->RSTI0
    Second TrainPulse - ctr1, out->RSTI1
    Period - ctr2, source=RSTI1, gate=RSTI0
    Running this program with a SIMULATED device - OK (data = 0). with the real device - I get error -200141
    I included my code.
    Attachments:
    DaQmx test.zip ‏147 KB

    I have a new question
    I need to create an event buffered task when the source=80mhz internal card timebase, gate=source of other counter (e.q for counter 1 use 0, for 3 use 2)
    I know that with Traditional-DAQ it will look like )see attch file):
    Now the convertion to DAQmx :
    ++++++++++++++++++++++++++++++
    void SetupEvent(void)
    if ( Internal.P6602_ID == -1 ) return;
    sprintf(Chan,"Dev%d/ctr1",Internal.P6602_ID); // channel 1
    DAQmxErrChk (DAQmxCreateTask("EventChan1",&DaqmxTasks.PCI_6602[1]));
    DAQmxErrChk (DAQmxCreateCICountEdgesChan(DaqmxTasks.PCI_6602[1],Chan,"EventChan1",DAQmx_Val_Rising,0,
    DAQmx_Val_CountUp));
    DAQmxErrChk (DAQmxSetTimingAttribute (DaqmxTasks.PCI_6602[1], DAQmx_SampTimingType, DAQmx_Val_SampClk) );
    DAQmxErrChk (DAQmxSetTimingAttribute (DaqmxTasks.PCI_6602[1], DAQmx_SampQuant_SampMode,DAQmx_Val_ContSamps) );
    DAQmxErrChk(DAQmxSetTimingAttribute (DaqmxTasks.PCI_6602[1],DAQmx_SampQuant_SampPerChan, BUF_MAX));
    // set source
    DAQmxErrChk (DAQmxSetTimingAttribute (DaqmxTasks.PCI_6602[1], DAQmx_SampClk_Src, "/Dev1/80MHzTimebase"));
    // and gate
    sprintf(msg,"/Dev%d/ctr0Source",Internal.P6602_ID);
    DAQmxErrChk(DAQmxSetChanAttribute (DaqmxTasks.PCI_6602[1], Chan, DAQmx_CI_CountEdges_Term, msg,0));
    sprintf(Chan,"Dev%d/ctr3",Internal.P6602_ID); // channel 3
    DAQmxErrChk (DAQmxCreateTask("EventChan3",&DaqmxTasks.PCI_6602[3]));
    DAQmxErrChk (DAQmxCreateCICountEdgesChan(DaqmxTasks.PCI_6602[3],Chan,"EventChan3",DAQmx_Val_Rising,0,
    DAQmx_Val_CountUp));
    DAQmxErrChk (DAQmxSetTimingAttribute (DaqmxTasks.PCI_6602[3], DAQmx_SampTimingType, DAQmx_Val_SampClk) );
    DAQmxErrChk (DAQmxSetTimingAttribute (DaqmxTasks.PCI_6602[3], DAQmx_SampQuant_SampMode,DAQmx_Val_ContSamps) );
    DAQmxErrChk(DAQmxSetTimingAttribute (DaqmxTasks.PCI_6602[3],DAQmx_SampQuant_SampPerChan, BUF_MAX));
    DAQmxErrChk (DAQmxSetTimingAttribute (DaqmxTasks.PCI_6602[1], DAQmx_SampClk_Src, "/Dev1/80MHzTimebase"));
    sprintf(msg,"/Dev%d/ctr2Source",Internal.P6602_ID);
    DAQmxErrChk(DAQmxSetChanAttribute (DaqmxTasks.PCI_6602[3], Chan, DAQmx_CI_CountEdges_Term, msg,0));
    return;
    Error:
    Internal.StartStop = OFF;
    if ( DAQmxFailed(error) ) DAQmxGetExtendedErrorInfo(errBuff,1024);
    StopCallBack();
    MessagePopup ("SetupEvent Error", errBuff);
    return;
    I am not sure this is the way to do it .
    Can samebody help ?
    Thanks, Galia
    Attachments:
    AutoScannerDAQCards.c ‏20 KB

  • How BOM and routing is selected for Planned order and Production order?

    Hi,
    Can any1 plz tell me how BOM and routing is selected for a planned order and production order. ?

    Hello Mathisuthan,
    BOM and Routing selection for the planned order and production order through production version, If u have more than one BOM and more than one Routing then u can maintain this information as Production Version in the system.
    Production version you maintained
    MM01/MM02 -- MRP4--- Production version
    Or you can create Production Versions in Mass also with Transaction Code "C223"
    In the case no production version maintained/created  for the material, then system by default  will pick the first BOM and routing.
    I hope this information helpful to you.
    Regards
    Umesh Mali

  • 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

  • How Clean ip Route Table and configuration

    How Clean ip Route Table and configuration?
    Cisco have any best practice?

    Hey Juan,
    your question is not very clear but i believe you want to know how to clean ip route table and configuration. So:
    1. Cleaning IP routing table - clear ip route * - This will refersh the routing table.
    2. Cleaning configuration - It depends on the device however in most of Cisco devices you may clear the startup configurtion and its done :)
    HTH.
    regards,
    RS.

  • How do I route audio from a YouTube video to AU Lab using SoundFlower so that I can capture the YouTube video's sound stream?

    How do I route audio from a YouTube video to AU Lab using SoundFlower so that I can capture the YouTube video's sound stream?

    Attach camera via USB or put card in card reader.
    Go to FCP, and go to the Log and TRANSFER window.
    If FCP recognizes the card, you will see your clips listed on the left.
    You can view them, set Ins and Outs, and import just what you want.
    Once you choose a section of video and import it, FCP converts (transcodes) from its original camera format to Apple ProRes422 - a more edit friendly video file.

  • How can i route smtp client in multiple messaging store servers environment

    In multiple messaging store servers environment, how can i route smtp client to the host which was specified in user's ldap "mailhost" attribute,just likes route pop client through mmp.
    does mmp can do it? or any other idea?
    thx a lot~!

    So, you want to add a text line to some messages, but not all?
    That's going to be pretty complex, actually.
    First, if all your mail is text, adding a text footer isn't all that difficult, it's done through the conversion channel.
    But filtering that, so you only do it for some users, isn't going to be easy at all.
    If you can get your users to point their clients to a particular MTA, then you can add the tag on that mta, only.
    Please note, that a text tag on a text mail is possible. Adding to an HTML mail is FAR more complex, and not a job for somebody not extremely familiar with MIME and building such.

  • 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

  • How to configure router to use ip pool on the aaa server for vpn clients

    how to configure router to use ip pool on the aaa server for vpn clients . i want to use vpn clients to connect to the router. authenticate using the aaa server username databse and also use the ip pool cretaed on the aaa server. i am not able to find the command on the router pointing to use the pool created on the aaa server. can u some one help me with this command.
    sebastan

    Hello Sebastan,
    what do you use as AAA server (e.g. ACS with TACACS+ or RADIUS) ?
    Regards,
    GNT

Maybe you are looking for