Nexus 6004 vs 6509 for Cores?

My organization is in the process of implementing two projects:
*Replacing our cores
*Upgrading our server access switches
Our current cores are dual WS-C6509's running in HSRP mode. We are upgrading them to new 6509's so we can implement VSS. They have not been installed yet, but we do have the equipment in our posession and mostly configured.
We are also in talks to purchase two Nexus 6004 chassis along with sixty 2232TM-E FEX's. It looks like this is going to happen soon. We use 4506's for our server access layer and are looking for the 6004/2000 Nexus platform to replace all of these 4506's.
What are the pro's and con's of skipping the 6509's and instead using the 6004/2232TM-E setup as our Core and Access layer?

You can just use the 6000 and eliminate the 6500 altogether. I am deploying 6004 as layer-3 and also for FEXs and server connectivity. One thing to remember is that with the current Nexus-OS if you are using the 6ks as layer-3, you can only connect 24 FEXa to a pair of 6ks. If you are using them as layer-2 only then the number is 48.
The other thing you should know is that the 6ks are 40Gig only. So, in order to connect for example a FEX or another device to it using 10Gig, you need to purchase the special 40Gig to 10Gig cable. This cable has a 40gig interface and one side and 4 10gig on the other side. We get ours from Panduat and they work really well. These cables are not cheap. They cost is about $500 per cable.
If you need part number for the cable and you need more info let me know.
http://www.panduit.com/wcs/Satellite?c=Page&childpagename=Panduit_Global%2FPG_Layout&cid=1345564328975&packedargs=locale%3Den_us%26prod_cat_id%3D3%26prod_id%3D3&pagename=PG_Wrapper
HTH

Similar Messages

Maximum Distance for FCOE on Nexus 6004

Hi,
We have a fabric composed by 2 Nexus 6004. The links between the 2 Nx 6004 are configured with vE_ports.
What is the maximum length for the links between the 2 Nexus 6004 ?
Many thanks in advance.
Nicolas.

I found the following, which is most likely not up to date
Q. Is the Nexus 6004 capable of long distance FCoE and will this functionality work at FCS?
The Nexus 6004 hardware allows FCoE distances up to 100km with 10GbE interface, 30km with 40GbE interface between two Nexus 6004 devices. However at FCS, the FCoE distance will be limited to 300m. Future software release will provide CLI tuning options to support longer distance.
•300m FCoE at FCS (optical transceiver distance limitation)
10-km FCoE for 10 GE and 40 GE ports with global QoS policy (roadmap)

FCoE and multiple Nexus 5000s and a 7000 core

Hi
I have a customer who is looking at four Nexus 5020s to start with and more in the future uplinked to a Nexus 7000 core.
Am I right in thinking that whilst data traffic will be able to reach hosts ocnnected to a different Nexus 5002 via the 7000 core FCoE traffic will not ?
If so what is teh recommended way of rolling out pods of 5020s for VMware servers with converged network adaptors so that they can all access the SAN ?
Regards
Pat

Don't use corecenter for fan speed control. Instead, use the BIOS:
1) Open Corecenter from the administrator account or a user account that has admin privileges. Click on the top center logo which should open the fan speed control window. There should be two items, CoolnQuiet and User/Manual or something like. Put it in manual and move the slider all the way to the right. Ignore the CoolnQuiet, it's misnamed here - MSI's corecenter does not control CoolnQuiet. What MSI is calling CoolnQuiet is just fan speed control. Anyway, put it in manual. Close Corecenter and you should never have to open it again unless you want to monitor fan RPM's.
2) Next, reboot and enter the BIOS. Go to the H/W Monitor settings. Turn on Smart CPU Fan Speed. Set to 40 C +/- 1. This will allow the motherboard to control the fan speed. On the other hand, if you want your fan always at maximum, then disable Smart Fan Speen control. Don't worry about the Smart NB Fan speed, leave it disabled.
Also, keep in mind that when you first open Corecenter, the immediate fan RPM's reported are not correct. It takes it a few seconds to get the readings. So wait until Corecenter minimizes itself to the system tray, then open it from there, and you will see the correct fan RPM's.

Nexus 6004 EIGRP Relationship between the two switches

Hi All,
I will try to explain this as best as I can. In our current TEST LAB we have a Pair of Cisco ASA5585x running in Active/Passive mode. We use a VRF transit to connect the 10 GB interface to a Pair of Cisco Nexus 6004 (L3) switches running vPC between them. Downstream we also have a pair of Cisco 9372 switches (L2) also running vPC between the two.
As of right now we have EIGRP neighbor relationship formed between the two N6K's and the ASA.
ASA
ciscoasa# sh eigrp neighbors
EIGRP-IPv4 neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
1 172.16.230.9 Te0/8.451 12 01:30:25 1 200 0 52
0 172.16.230.10 Te0/8.451 12 01:30:25 1 200 0 48
The ASA formed relationship with both N6K's
SWITCH1
Nexus6-1# sh ip eigrp neighbors vrf inside
IP-EIGRP neighbors for process 100 VRF Inside
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 172.16.8.3 Vlan680 11 01:28:28 1 50 0 45
1 172.16.230.10 Vlan451 13 01:28:28 1 50 0 46
2 172.16.230.11 Vlan451 10 01:28:00 4 50 0 13
Nexus6-1#
SWITCH2
Nexus6-2# sh ip eigrp neighbors vrf Inside
IP-EIGRP neighbors for process 100 VRF Inside
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
2 172.16.8.2 Vlan680 14 01:30:11 23 138 0 48
0 172.16.230.9 Vlan451 13 01:30:11 480 2880 0 50
1 172.16.230.11 Vlan451 13 01:29:48 1598 5000 0 13
Nexus6-2#
Both Nexus Switches formed EIGRP neighbors using the vPC Peer-Link. There is enough documentation out there that strongly suggest not to use vPC Peer-Links for EIGRP anything.
We do have additional interfaces available on the 6K's that we can use as a cross connect for EIGRP. What we are having trouble understanding how we can force EIGRP traffic over those ports?
Here is a complete Switch config:
Switch1
Nexus6-1# sh run
feature telnet
cfs eth distribute
feature eigrp
feature interface-vlan
feature lacp
feature vpc
feature lldp
vlan 1
vlan 451
name P2P_VRF_SVI
vlan 652
name Management
vlan 680
name Inside
vrf context Inside
vrf context management
ip route 0.0.0.0/0 172.16.52.1
vrf context peer-keepalive
vpc domain 99
role priority 1
peer-keepalive destination 10.200.50.2 source 10.200.50.1 vrf peer-keepalive
delay restore 120
interface Vlan1
interface Vlan451
description Inside p2p to ASA
no shutdown
vrf member Inside
ip address 172.16.230.9/29
ip router eigrp 100
no ip passive-interface eigrp 100
interface Vlan651
interface Vlan680
description Inside Network
no shutdown
vrf member Inside
ip address 172.16.8.2/22
ip router eigrp 100
interface port-channel99
switchport mode trunk
spanning-tree port type network
vpc peer-link
interface port-channel102
switchport mode trunk
vpc 102
interface Ethernet1/1
description vPC Peer Link 1.1
switchport mode trunk
speed auto
channel-group 99
interface Ethernet1/6
interface Ethernet1/7
description vPC Peer Link 1.7 to Nexus 9372 PRI
switchport mode trunk
speed auto
channel-group 102 mode active
interface Ethernet1/8
interface Ethernet1/9
interface Ethernet2/1
description vPC Peer Link 2.1
switchport mode trunk
speed auto
channel-group 99
interface Ethernet2/2
interface Ethernet2/7
description vPC Peer Link 2.1 to Nexus SEC
switchport mode trunk
speed auto
channel-group 102 mode active
interface Ethernet2/8
interface Ethernet8/1
description keep-alive peer-link to ALNSWI02
no switchport
vrf member peer-keepalive
ip address 10.200.50.1/30
interface Ethernet8/2
description Uplink to ASA
switchport mode trunk
interface Ethernet8/3
interface mgmt0
vrf member management
ip address 172.16.52.3/23
line console
line vty
boot kickstart bootflash:/n6000-uk9-kickstart.7.0.1.N1.1.bin
boot system bootflash:/n6000-uk9.7.0.1.N1.1.bin
router eigrp 100
passive-interface default
default-information originate
vrf Inside
autonomous-system 100
default-information originate
poap transit
Nexus6-1#
Nexus6-1# sh ip eigrp neighbors vrf inside
IP-EIGRP neighbors for process 100 VRF Inside
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 172.16.8.3 Vlan680 11 01:28:28 1 50 0 45
1 172.16.230.10 Vlan451 13 01:28:28 1 50 0 46
2 172.16.230.11 Vlan451 10 01:28:00 4 50 0 13
Nexus6-1#
Nexus6-1# sh ip eigrp topology vrf Inside
IP-EIGRP Topology Table for AS(100)/ID(172.16.8.2) VRF Inside
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 172.16.8.0/22, 1 successors, FD is 2816
via Connected, Vlan680
P 172.16.230.8/29, 1 successors, FD is 2816
via Connected, Vlan451
Nexus6-1# sh vpc
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 99
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
vPC role : primary
Number of vPCs configured : 1
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Disabled
vPC Peer-link status
id Port Status Active vlans
1 Po99 up 1,451,652,680
vPC status
id Port Status Consistency Reason Active vlans
102 Po102 up success success 1,451,652,6
80
Nexus6-1# sh spanning-tree
VLAN0001
Spanning tree enabled protocol rstp
Root ID Priority 32769
Address 1005.caf5.88ff
Cost 2
Port 4197 (port-channel102)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
Address 8c60.4f2d.2ffc
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
Po102 Root FWD 1 128.4197 (vPC) P2p
Eth8/2 Desg FWD 2 128.1026 P2p
Eth8/3 Desg FWD 2 128.1027 P2p
VLAN0451
Spanning tree enabled protocol rstp
Root ID Priority 33219
Address 8c60.4f2d.2ffc
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33219 (priority 32768 sys-id-ext 451)
Address 8c60.4f2d.2ffc
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
Po102 Desg FWD 1 128.4197 (vPC) P2p
Eth8/2 Desg FWD 2 128.1026 P2p
VLAN0652
Spanning tree enabled protocol rstp
Root ID Priority 33420
Address 1005.caf5.88ff
Cost 2
Port 4197 (port-channel102)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33420 (priority 32768 sys-id-ext 652)
Address 8c60.4f2d.2ffc
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
Po102 Root FWD 1 128.4197 (vPC) P2p
Eth8/2 Desg FWD 2 128.1026 P2p
VLAN0680
Spanning tree enabled protocol rstp
Root ID Priority 33448
Address 1005.caf5.88ff
Cost 2
Port 4197 (port-channel102)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33448 (priority 32768 sys-id-ext 680)
Address 8c60.4f2d.2ffc
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
Po102 Root FWD 1 128.4197 (vPC) P2p
Eth8/2 Desg FWD 2 128.1026 P2p
Nexus6-1#
Switch2
Nexus6-2# sh run
!Command: show running-config
!Time: Sat Feb 12 19:02:44 2011
version 7.0(1)N1(1)
hostname Nexus6-2
feature telnet
cfs eth distribute
feature eigrp
feature interface-vlan
feature lacp
feature vpc
feature lldp
vlan 1
vlan 451
name P2P_VRF_SVI
vlan 652
name Management
vlan 680
name Inside
vrf context Inside
vrf context P2P_Inside_VRF
vrf context management
ip route 0.0.0.0/0 172.16.52.1
vrf context peer-keepalive
vpc domain 99
role priority 2
peer-keepalive destination 10.200.50.1 source 10.200.50.2 vrf peer-keepalive
delay restore 120
interface Vlan1
interface Vlan451
description Inside p2p to ASA
no shutdown
vrf member Inside
ip address 172.16.230.10/29
ip router eigrp 100
no ip passive-interface eigrp 100
interface Vlan680
description Inside Network
no shutdown
vrf member Inside
ip address 172.16.8.3/22
ip router eigrp 100
interface port-channel99
switchport mode trunk
spanning-tree port type network
vpc peer-link
interface port-channel102
switchport mode trunk
vpc 102
interface Ethernet1/1
description vPC Peer Link 1.1
switchport mode trunk
speed auto
channel-group 99
interface Ethernet1/2
interface Ethernet1/6
interface Ethernet1/7
description vPC Link 1.7 to Nexus 9372 SEC
switchport mode trunk
speed auto
channel-group 102 mode active
interface Ethernet1/8
interface Ethernet1/12
interface Ethernet2/1
description vPC Peer Link 2.1
switchport mode trunk
speed auto
channel-group 99
interface Ethernet2/2
interface Ethernet2/6
interface Ethernet2/7
description vPC Link 2.1 to Nexus PRI
switchport mode trunk
speed auto
channel-group 102 mode active
interface Ethernet2/8
interface Ethernet2/12
interface Ethernet8/1
description keep-alive peer-link to ALNSWI01
no switchport
vrf member peer-keepalive
ip address 10.200.50.2/30
interface Ethernet8/2
description Uplink to ASA
switchport mode trunk
switchport trunk allowed vlan 1,451,652,680
interface Ethernet8/3
interface Ethernet8/20
interface mgmt0
vrf member management
ip address 172.16.52.4/23
line console
line vty
boot kickstart bootflash:/n6000-uk9-kickstart.7.0.1.N1.1.bin
boot system bootflash:/n6000-uk9.7.0.1.N1.1.bin
router eigrp 100
vrf Inside
autonomous-system 100
default-information originate
poap transit
logging logfile messages 6
Nexus6-2#
Nexus6-2#
Nexus6-2# sh ip eigrp neighbors vrf Inside
IP-EIGRP neighbors for process 100 VRF Inside
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
2 172.16.8.2 Vlan680 14 01:30:11 23 138 0 48
0 172.16.230.9 Vlan451 13 01:30:11 480 2880 0 50
1 172.16.230.11 Vlan451 13 01:29:48 1598 5000 0 13
Nexus6-2#
Nexus6-2# sh ip eigrp topology vrf Inside
IP-EIGRP Topology Table for AS(100)/ID(172.16.8.3) VRF Inside
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 172.16.8.0/22, 1 successors, FD is 2816
via Connected, Vlan680
P 172.16.230.8/29, 1 successors, FD is 2816
via Connected, Vlan451
Nexus6-2#
Nexus6-2#
Nexus6-2# sh vpc
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 99
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
vPC role : secondary
Number of vPCs configured : 1
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Disabled
vPC Peer-link status
id Port Status Active vlans
1 Po99 up 1,451,652,680
vPC status
id Port Status Consistency Reason Active vlans
102 Po102 up success success 1,451,652,6
80
Nexus6-2#
Nexus6-2#
Nexus6-2# sh spanning-tree
VLAN0001
Spanning tree enabled protocol rstp
Root ID Priority 32769
Address 1005.caf5.88ff
Cost 3
Port 4194 (port-channel99)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
Address 8c60.4f2d.777c
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po99 Root FWD 1 128.4194 (vPC peer-link) Network P2p
Po102 Root FWD 1 128.4197 (vPC) P2p
Eth8/2 Desg FWD 2 128.1026 P2p
Eth8/3 Desg FWD 2 128.1027 P2p
VLAN0451
Spanning tree enabled protocol rstp
Root ID Priority 33219
Address 8c

Jon,
Are you ready for the mass confusion?
when Looking at the ASA EIGRP neighbors output here is what I see.
ASA# sh eigrp neighbors
EIGRP-IPv4 neighbors for process 100
H   Address                 Interface       Hold Uptime   SRTT   RTO Q Seq
                                            (sec)         (ms)       Cnt Num
3   172.16.230.1            Te0/8.450        13 16:45:14 1    200   0   64
2   172.16.230.2            Te0/8.450        11 16:45:14 1    200   0   84
1   172.16.230.10           Te0/8.451        11 16:45:20 1    200   0   178
0   172.16.230.9            Te0/8.451        13 16:45:20 1    200   0   148
For simplicity sake lets just concetrate on Interface TenGigabit0/8.451 which is the SVI on the Nexus switch that is VLAN451
From the Nexus Switch 6004 that is directly connected to the ASA here is what I see
SWI01# sh ip eigrp neighbors vrf Inside
IP-EIGRP neighbors for process 100 VRF Inside
H   Address                 Interface       Hold Uptime SRTT   RTO Q Seq
                                            (sec)         (ms)       Cnt Num
0   172.16.8.3              Vlan680         10   17:04:30 54   324   0   177
1   172.16.230.10           Vlan451         11   16:59:10 819 4914 0   178
2   172.16.230.11           Vlan451         14   16:53:48 24   144   0   20
The Inside VRF that is tied to both SVI's on the Switch vlans 451 and 680 is in EIGRP 100 on the switch
SWI01# sh run int vlan 451
interface Vlan451
description Inside p2p to ASA
no shutdown
vrf member Inside
ip address 172.16.230.9/29
ip router eigrp 100
no ip passive-interface eigrp 100
SWI01# sh run int vlan 680
interface Vlan680
description Inside Network
no shutdown
vrf member Inside
ip address 172.16.8.2/22
ip router eigrp 100
hsrp 1
    authentication text test
    preempt
    priority 250
    ip 172.16.8.1
so you with me so far?
If you are you have noticed that on the ASA neighbors the ASA sees 172.16.230.11 as a neighbor which is the Secondary Nexus SW. That is becauise they all share the same subnet.
172.16.230.8/29
Brakedown:
PRI Nexus 6004 - 172.16.230.9
SEC NEXUS 6004 - 172.16.230.10
PRI ASA 5585x - 172.16.230.11
SEC ASA 5585x - 172.16.230.12
Because the ASA EIGRP network is a /29 it learns the Secondary Nexus via the Primary Nexus.
I am not sure that the link we created between the two Nexus Switches is doing anything but consuming ports right now.
SWI01# sh run int ethernet 8/9
interface Ethernet8/9
description EIGRP PORT to Secondary Nexus
switchport mode trunk
switchport trunk allowed vlan 450-451
SWI02# sh run int ethernet 8/9
interface Ethernet8/9
description EIGRP PORT to Primary Nexus
switchport mode trunk
switchport trunk allowed vlan 450-451
So the SVI's that go up to the ASA for inspection are 450 and 451. The network SVI's are 600 and 680 all of them live on the switch, and 680, and 600 are extended over the peer links down to the 9372's.
I think that we are breaking the golden rule of vPC BUT.. I am not 100% sure. Some of the documents read that we should not be allowing network vlans over peer links, but then how do you extend the vlans down to the leaf switch?
This is giving me nightmares at the moment…
does this make sense?

4500-X vs 6880-X for Core/Distribution

Hi,
    We are in the process of looking at upgrading our eight year old Cisco network to something newer.
    Currently we have a 6500 for core/distribution with about 40+ 1 gig fibre links running out to access layer switches. (3560 and 3560X)
    The whole design is routed with the links from core/distribtion to access all being layer 3. The intent was to dual attach access layer switches to 6500s in two buildings but this was never actually implemented.
     The new design uses 3650 switches at the access layer, and a recommendation to use the 6880-X for core/distribution. This time around key buildings will be dual attached and I expect we will keep the routed design. 9396PX will be introduced at the datacenter layer.
     It looks to be like the 6880-X is a pretty limited unit. No real path to 40 or 100 gig, no redundant supervisors, just a big box of 10 Gig ports.
     I am assuming the cost on a 6807 chassis is just going to be too high, although 40 G and 100G are either available today or on the roadmap.
     I am trying to figure out why two 4500-X with Enterprise software in VSS mode isn't a better fit. The port count is good at 80 (between the two), it has more bandwidth, features like MACSEC and SGT are on the develpment radar (if not already implemented), and two of these in VSS means I can perform a firmware update with minimal down time.
     I plan to implement ISE in 2015 so having a platform that is going to work with ISE is really important to me.
Thanks
Murray

Wow, amazing that noone answered such a real world question. I had like 2 similar cases within the last 2 months!!!
I normaly really like 4500X, it´s a powefull 1U 10G unit, and I myself am a fan of VSS, so - I agree with you, that should be a first choice! (btw - 6880 also supports VSS)
When to use 6880X? Well, I had a case recently with 45 3750X stacks in the core, so 80 ports in total wouldnt even cover a port-channel per stack, so - I used 6880X. How do I see this switch? As a moderatly priced almost-Nexus alternative for Campus with 10G with a VSS support.
To sum it up - yeah, I´d use 4500X if I were you...
Cheers!

Nexus 6004 FC NPIV

I am looking at replacing my MDS 9506 (2) with 4 nexus 6004.
FC will connect to the new 20 port UP cards on the nexus 6004
some info req.
Configurations simiilar to that of mDS
support for zoning
npiv support
what lic is required NPIV - FC
vsan
dcns
optics from MDS 9506 will work on nexus 6004
fcoe support - lic req

Please look at
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-6000-series-switches/datasheet-c78-732277.html
which contains the hardware features as well as the licenses.
It is easy to migrate a configuration from MDS to Nexus 6004.
Be aware, that there might be features, which are not available on Nexus, e.g. IVR.
Also, the native FC speed limitation is 8 Gbps !
Cisco SFP's from MDS should work ok in Nexus 6004
http://www.cisco.com/c/en/us/products/collateral/storage-networking/mds-9000-series-multilayer-switches/product_data_sheet09186a00801bc698.html

Nexus 6004 TOR connectivity to Brocade DCX

Hi Experts,
I am facing an issues in our new data centre. We want to install Nexus 6004 in the TOR and connect the FC links back to the existing DCX?
I see from the datasheets that the 6004 now has native FC capability. Is it supported to set the 6004 to NPIV mode and connect as an Access gateway to the edge for the Brocade SAN?
Any advise appreciated as I really want to push CISCO at the TOR.
digduggo

See Figure 6-2 Converged Multi-hop FCoE Network Design Using FCoE NPV
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/fcoe/513_n1_1/ops_fcoe/ops_fcoe_npv.html
You have to use NPV on N5k, there is no FC interop support on N5k, to connect to Brocade.

Cisco Nexus 6004 | Fibre Tx and Rx Levels

Hi All,
On the Nexus 6004 series, does anybody know how to see the light levels for the optics.
I am using the command: show interface ethernet 2/5/4 transceiver details which outputs:
Ethernet2/5/4
    transceiver is present
    type is QSFP-40G-CSR4
    name is CISCO
    part number is AFBR-79EEPZ-CS2
    revision is 02
    serial number is XXXXXXXX
    nominal bitrate is 10300 MBit/sec
    Link length supported for 50/125um OM3 fiber is 300 m
    Link length supported for 50/125um OM2 fiber is 82 m
    cisco id is --
    cisco extended id number is 16
           SFP Detail Diagnostics Information (internal calibration)
                Current              Alarms                  Warnings
                Measurement     High        Low         High          Low
Temperature   47.63 C        75.00 C     -5.00 C     70.00 C        0.00 C
Voltage        3.32 V         3.63 V      2.97 V      3.46 V        3.09 V
Current        0.00 mA        0.00 mA     0.00 mA     0.00 mA       0.00 mA
Tx Power        N/A            N/A         N/A         N/A           N/A
Rx Power        N/A            N/A         N/A         N/A           N/A
Note: ++ high-alarm; + high-warning; -- low-alarm; - low-warning
Is it a case that the SFP's in this instance do not support the light level information? the controller, optics or wdm commands are not available on the Nexus.
Thanks all for your support.

Hi Marvin,
The System version: 6.0(2)N1(2)
Software
BIOS:      version 2.6.0
loader:    version N/A
kickstart: version 6.0(2)N2(2)
system:    version 6.0(2)N2(2)
Power Sequencer Firmware:
             Module 0: version v5.0
             Module 1: version v2.0
             Module 2: version v2.0
             Module 3: version v2.0
             Module 4: version v2.0
Fabric Power Sequencer Firmware: Module 0: version v3.0
Microcontroller Firmware:        version v1.1.0.3
QSFP Microcontroller Firmware:
             Module 1: v1.3.0.0
             Module 2: v1.3.0.0
             Module 3: v1.3.0.0
             Module 4: v1.3.0.0

Cisco Nexus 1000v Virtual Switch for Hyper-V Availability

Hi,
Does anyone have any information on the availability of the Cisco Nexus 1000v virtual switch for Hyper-V. Is it available to download from Cisco yet? If not when will it be released? Are there any Beta programs etc?
I can download the 1000v for VmWare but cannot find any downloads for the Hyper-V version.
Microsoft Partner

Any updates on the Cisco Nexus 1000v virtual switch for Hyper-V? Just checked on the Cisco site, however still only the download for VMware and no trace of any beta version. Also posted the same question at:
http://blogs.technet.com/b/schadinio/archive/2012/06/09/windows-server-2012-hyper-v-extensible-switch-cisco-nexus-1000v.aspx
"Hyper-V support isn't out yet. We are looking at a beta for Hyper-V starting at the end of February or the begining of March. "
-Ian @ Cisco Community
|| MCITP: EA, VA, EMA, Lync SA, makes a killer sandwich. ||

There is a UNIX line command for Core audio RAM size addressing?

Hi all
There is a Terminal line command that allow me to addressing more ram size in the Logic AUDIO preferences?
I greatly appreciate your help
Thanks in Advance!
G

fermusic wrote:
please stay focused to that picture
I don't look for magician..
I know that there is terminal command for change setting about song backup count...
since Logic 8 the Project Backup has been fixed to 10...
I mentioned defaults in my first post. 'defaults' is the command line utility to set the maximum number of backups, and the key/value is clearly visible in the file, where I see no clearly identified key for the preference setting you seek.
so you can type 'man defaults' into terminal to read the manual for defaults.
Also in Logic 6 32bit application... and in Logic 7.2.3 (32bit application)
there is a setting that allow me to addressing 384Mb to the system core audio... and it is not a 64 bit apps.
Memory addressing != Memory allocating
I'm looking for a Terminal command that can rewrite Logic preferences files... in the same way as made for change the Song Backups number...
Please stay focused I don't need theoretical explaination..
I'm a Musician... I'm not a Developer...
BUT I Know.. for sure...I can adress 384Mb for core audio...
I need to bypass the automatic ram adressing only and strictly focused to achieve 384MB just for CORE AUDIO!!!
Right right right. I addressed that by typing:
you'd have insider info to use that utility for the intentions that you have in mind
If that preference exists, it is not public knowledge (to my knowledge). You would need to know a few things about the preference key/value to set or remove it.
So, yeah - my original post covered it all, to the best of my knowledge.
J

Nexus 6004: Question about port-profile type port-channel

I'm setting up a new deployment of Nexus 6004 switches and want to utilize port-profiles as much as possible to simplify management down the road.
All uplinks to other switches, routers and firewalls will be connected using VPC:s. On the port-channels (vpc) the only thing that will change over time is the allowed vlans.
It seems that port-profiles of the type port-channel does not behave in the same way as those with type ethernet, at least not when adding vlans.
If I modify the port-profile using "switchport trunk allowed vlan add XXX" it will delete the previous config and only retain "switchport trunk allowed vlan add XXX", and not merge it with the previous config as is expected.
Question: Is this a bug or is it working as intended?
RH_N6K4_01(config-sync)# switch-profile rh
Switch-Profile started, Profile ID is 1
RH_N6K4_01(config-sync-sp)# port-profile type port-channel FIREWALL-UPLINK
RH_N6K4_01(config-sync-port-prof)# switchport trunk allowed vlan 3
RH_N6K4_01(config-sync-port-prof)# verify
Verification Successful
RH_N6K4_01(config-sync-sp)# commit
Verification successful...
Proceeding to apply configuration. This might take a while depending on amount of configuration in buffer.
Please avoid other configuration changes during this time.
Commit Successful
RH_N6K4_01(config-sync)# show port-profile
SHOW PORT_PROFILE
port-profile FIREWALL-UPLINK
type: Port-channel
description:
status: enabled
max-ports: 512
inherit:
config attributes:
switchport mode trunk
switchport trunk allowed vlan 3
evaluated config attributes:
switchport mode trunk
switchport trunk allowed vlan 3
assigned interfaces:
===================================
RH_N6K4_01(config-sync-sp)# port-profile type port-channel FIREWALL-UPLINK
RH_N6K4_01(config-sync-port-prof)# switchport trunk allowed vlan add 84
RH_N6K4_01(config-sync-port-prof)# verify
Verification Successful
RH_N6K4_01(config-sync-sp)# commit
Verification successful...
Proceeding to apply configuration. This might take a while depending on amount of configuration in buffer.
Please avoid other configuration changes during this time.
Commit Successful
RH_N6K4_01(config-sync)# show port-profile
SHOW PORT_PROFILE
port-profile FIREWALL-UPLINK
type: Port-channel
description:
status: enabled
max-ports: 512
inherit:
config attributes:
switchport mode trunk
switchport trunk allowed vlan add 84
evaluated config attributes:
switchport mode trunk
switchport trunk allowed vlan add 84
assigned interfaces:
Expected behavior here would be "switchport trunk allowed vlan 3,84". This only occurs when using "port-profile type port-channel" not when using "port-profile type ethernet"

<> is template syntax and is generally the type of object a container holds.. So it is defining that the MSGQUEUE type is a deque holding struct_buffer*'s.

[SOLVED]Support for cores revision 0x17 and 0x18 disabled...

Everything is perfect on my arch linux setup except the following message I get at boot
Support for cores revisions 0x17 and 0x18 disabled by module param allhwsupport=0. Try b43.allhwsupport=1
Help please
EDIT: After some googling I found a spanish website and did the following
Uncommented '#RuntimeWatchdogSec=0' in /etc/systemd/system.conf
And now it finally stfu. I've also added in the boot parameters after quiet splash loglevel=3
Last edited by sexyzero (2013-10-01 12:13:04)

I did, you linked to it already
I slightly modified modemmanager-git in the AUR and added some dependencies, the git version now works for me.

Prictical Guidelines for core java

Hi Friends,
I want a book like "explorering in c" for Core Java.
I am facing some problem, while executing the small tricky program of core Java.
I want a book which is related with practical oriented.
Means small junk of code and I have to calculate the out put or compilation error or run time error or which type of exception it will give.
Is there any book like this?
Or please give me this link
Please suggest me the book name or website name..........

"Thinking in Java" is quite good; the 3rd edition is a free e-book; downloadable from the author's web site http://www.mindviewinc.com/

Uplink Nexus 5010 to 6509 and management

I have looked around online on Cisco's site and scanned over the Nexus 5000 document and I cant seem to find the answers Im looking for. The document I am referring to can be found at http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli_rel_4_0_1a/CLIConfigurationGuide.html
I have two questions:
1) Are there any guides to connecting the 5000's to 6509's which would be serving as the core? If not can someone point me in the right direction.
2) I have configured the management port on the 5000. In order to access the CLI of the switch without a console cable do I need to have the management port connected to my infrastructure or can I ssh/telnet to the switch by just having it uplinked via Fiber back to the 6509's?
Thank you kindly

Mod Ports Card Type                              Model              Serial No.
1   48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX     SAL12330BKM
4    8 CEF720 8 port 10GE with DFC            WS-X6708-10GE      SAL123418MN
5    4 CEF720 4 port 10-Gigabit Ethernet      WS-X6704-10GE      SAL11370JSY
6    2 Supervisor Engine 720 (Active)         WS-SUP720-BASE     SAL1201BZUC
9   16 SFM-capable 16 port 1000mb GBIC        WS-X6516A-GBIC     SAL08196XHD
Mod MAC addresses                       Hw    Fw           Sw           Status
1 0022.55ec.69a8 to 0022.55ec.69d7   3.0   12.2(18r)S1 12.2(18)SXF1 Ok
4 0023.045e.fbe8 to 0023.045e.fbef   1.6   12.2(18r)S1 12.2(18)SXF1 Ok
5 001d.4542.17b0 to 001d.4542.17b3   2.6   12.2(14r)S5 12.2(18)SXF1 Ok
6 0019.e7d4.3e5c to 0019.e7d4.3e5f   4.0   8.4(2)       12.2(18)SXF1 Ok
9 000f.f780.d2bc to 000f.f780.d2cb   4.1   7.2(1)       8.5(0.46)RFW Ok
Mod Sub-Module                  Model              Serial       Hw     Status
1 Centralized Forwarding Card WS-F6700-CFC       SAL1230Y8RY 4.1    Ok
4 Distributed Forwarding Card WS-F6700-DFC3C     SAL123304FZ 1.0    Ok
5 Distributed Forwarding Card WS-F6700-DFC3B     SAL1115LPP0 4.6    Ok
6 Policy Feature Card 3       WS-F6K-PFC3A       SAL1201C3KH 2.6    Ok
6 MSFC3 Daughterboard         WS-SUP720          SAL1201C1TQ 3.1    Ok
Mod Online Diag Status
1 Pass
4 Pass
5 Pass
6 Pass
9 Pass
#sh ver
Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(18)SXF15a, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by cisco Systems, Inc.
Compiled Tue 21-Oct-08 00:04 by kellythw
Image text-base: 0x40101040, data-base: 0x42DDBE30
ROM: System Bootstrap, Version 12.2(17r)S4, RELEASE SOFTWARE (fc1)
BOOTLDR: s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(18)SXF15a, RELEASE SOFTWARE (fc1)
pa-core-6509 uptime is 1 year, 11 weeks, 2 days, 23 hours, 49 minutes
Time since pa-core-6509 switched to active is 1 year, 11 weeks, 2 days, 23 hours, 48 minutes
System returned to ROM by s/w reset at 08:16:27 UTC Tue Oct 28 2008 (SP by bus error at PC 0x401A4578, address 0x0)
System image file is "disk0:s72033-advipservicesk9_wan-mz.122-18.SXF15a.bin"

Best path for Core Data implementation

Hi all,
First post so pls go easy!
I'm a seasoned Windows/Web App developer who has recently (3-4m) discovered Mac, Cocoa and Obj-C. I've been buried in Apple docs, Hillegass and Dalrymple books for some time now trying to get to the point where I'm ready to build the Cocoa project that I have in mind, which looks to be well suited to a Core Data based Application driven by SQLite. The data model is reasonably complex with around 10 inter-related entities which must retain data integrity.
Anyway, onto the question... historically I would have built a class library to encapsulate the use of the data model and accessed that class library when events fired to do what needs to be done. The Cocoa solution appears to support this - presumably though creating my own framework that is then referenced by the Cocoa application. I can see though that there is another path where I skip the encapsulation and build a Core Data based Cocoa app directly.
At a high level - is there a preference between the two approaches?
The latter seems well documented/supported but I am synically thinking that is because it is more straightforward and clearly faster, are there other advantages such as performance.
For background the app when running will follow similar form to Mail.app in terms of multi-view with some data tables and custom views in play.
Thanks,
Chris

Hi K T - thanks.
Bottom line I think is that encapsulation is a safety blanket that I probably need to let go of. CD ticks boxes on a theory level, subject to implementation not being too heavy it seems like the logical step. The only consideration was to encapsulate a framework built on the known methods, then move the framework to CD under the covers when ready - that seems a bit gutless though and almost definitely inefficient time wise. I guess that there is little point in encapsulating CD from the outset - feel like it just adds unnecessary work in addition to some degree of performance overhead?
{quote}Are you looking for flexibility or performance, by the way?{quote}
Performance - the data model is unlikely to change once bedded in beyond addition of properties etc very infrequently. The app is likely to need to handle many tens of thousands of rows of data (albeit small in terms of data volume per row) for some users, and my conclusion from the documentation was that SQLite is the most appropriate route if committing to CD where data volume and/or relationships are plentiful. Is that a fair assessment?
{quote}Are you looking to mimic traditional application interfaces or to adopt trends that are currently unfolding?{quote}
The app I plan to build desperately needs to be brought up to date - possibly even beyond the advanced UI that AppKit seems to offer by default IMO. That said I don't want to overcommit on the extent of the build, but I do want to turn heads without just slapping coverflow or similar in for the sake of it. If you have any references or examples for doable leading edge UI design on OSX they would be gratefully received.
Thanks again for your help - really appreciate it.
Chris

Nexus 6004 vs 6509 for Cores?

Similar Messages

Maybe you are looking for