Nexus 2232 - 10gig only

Looking for a quick answer here. Someone is telling me they are able to purchase a 1gig Copper SFP tranciever and use that in a Nexus 2232. As in, connecting a 1gig connection into a Nexus 2232. I was under the impression that a N2232 was 10gig only
Am I wrong?
Thanks
Jeremy

Hey Jeremy,
Yes, the Nexus 2232PP can operate also as 1Gbps and the GLC-T transceiver is listed as compatible in the Cisco Nexus 2232PP matrix.
http://www.cisco.com/c/en/us/td/docs/interfaces_modules/transceiver_modules/compatibility/matrix/OL_6981.html
Regards.
Richard

Similar Messages

Nexus 2232 - sfpInvalid

I get sfpInvalid when inserting a FET-10G in a Nexus 2232. I've inserted several FET's in several ports, same error on all ports. Output;
nx-d12-01# sh int eth115/1/5 transceiver details
Ethernet115/1/5
    transceiver is present
    type is Fabric Extender Transceiver
    name is CISCO-JDSU
    part number is PLRXPL-VC-S43-CG
    revision is B
    serial number is JUS1708B94M
    nominal bitrate is 10300 MBit/sec
    Link length supported for 50/125um OM3 fiber is 100 m
    Link length supported for 62.5/125um fiber is 10 m
    cisco id is --
    cisco extended id number is 4
           SFP Detail Diagnostics Information (internal calibration)
                Current              Alarms                  Warnings
                Measurement     High        Low         High          Low
Temperature   31.91 C        75.00 C      5.00 C     70.00 C       10.00 C
Voltage        3.30 V         3.63 V      2.97 V      3.46 V        3.13 V
Current        0.00 mA       10.00 mA     2.59 mA     8.50 mA       3.00 mA
Tx Power        N/A           2.69 dBm -11.30 dBm   -1.30 dBm     -7.30 dBm
Rx Power        N/A     --    2.99 dBm -13.97 dBm   -1.00 dBm     -9.91 dBm
Note: ++ high-alarm; + high-warning; -- low-alarm; - low-warning
The port is configured default (no config on port);
Port          Name               Status    Vlan      Duplex Speed   Type
Eth115/1/5    --                 sfpInvali 1         full    10G     --

Hi Leo,
Apologies in advance if I'm teaching you to suck eggs in this explanation.
I guess technically and logically this is an interface on the parent Nexus switch, but in this case we can deduce it to be a physical interface on a FEX. Here we know the parent switch is a Nexus 5K as we can see the NX-OS version 5.2(1)N1(4) from the sh run int eth115/1/1 command output that was included. The N designation in the NX-OS version number is that given to the Nexus 5K platform.
nx..(config-if)# do sh run int eth115/1/1
!Command: show running-config interface Ethernet115/1/1
!Time: Thu Jul 4 11:22:47 2013
version 5.2(1)N1(4)
interface Ethernet115/1/1
The Nexus 5K built in ports are numbered Eth1/1-32 and eth2/1-16 (N5548) or Eth1/1-48, eth2/1-16, eth3/1-16 and eth4/1-16 (N5596) so it's not one of those.
For the host interfaces on the FEX, the number is in the form eth X/Y/Z where X is the number assigned to the FEX in the parent switch configuration, Y is always 1, and Z is the number of the physical interface on the FEX. In the case of the Nexus 2232 this would obviously be in the range 1-32.
So what we can see from the output the OP has included is that the FET has been inserted in host interface 1 and 5 of the FEX that is assigned the number 115 in the parent switch.
Regards

Nexus 2232 TM uplink ports are they only for uplink use?

We have upgraded our N5K to support the new 2232TM, but now we face the issue that the 8 SFP+ ports are not visible in our config:
Nexus5010_1# sh fex 103 det
FEX: 103 Description: 2KSRV02   state: Online
FEX version: 5.0(3)N2(2a) [Switch version: 5.0(3)N2(2a)]
FEX Interim version: 5.0(3)N2(2a)
Switch Interim version: 5.0(3)N2(2a)
Extender Model: N2K-C2232TM-10GE, Extender Serial: FOC15262P7Q
Part No: 73-13626-03
Card Id: 164, Mac Addr: 30:e4:db:66:12:02, Num Macs: 64
Module Sw Gen: 21 [Switch Sw Gen: 21]
post level: complete
pinning-mode: static    Max-links: 1
Fabric port for control traffic: Eth1/9
Fabric interface state:
    Po103 - Interface Up. State: Active
    Eth1/9 - Interface Up. State: Active
    Eth1/10 - Interface Up. State: Active
Fex Port        State Fabric Port
       Eth103/1/1 Down       Po103
       Eth103/1/2 Down       Po103
       Eth103/1/3 Down       Po103
       Eth103/1/4 Down       Po103
       Eth103/1/5 Down       Po103
       Eth103/1/6 Down       Po103
       Eth103/1/7 Down       Po103
       Eth103/1/8 Down       Po103
       Eth103/1/9 Down       Po103
      Eth103/1/10 Down       Po103
      Eth103/1/11 Down       Po103
      Eth103/1/12 Down       Po103
      Eth103/1/13 Down       Po103
      Eth103/1/14 Down       Po103
      Eth103/1/15 Down       Po103
      Eth103/1/16 Down       Po103
      Eth103/1/17 Down       Po103
      Eth103/1/18 Down       Po103
      Eth103/1/19 Down       Po103
      Eth103/1/20 Down       Po103
      Eth103/1/21 Down       Po103
      Eth103/1/22 Down       Po103
      Eth103/1/23 Down       Po103
      Eth103/1/24 Down       Po103
      Eth103/1/25 Down       Po103
      Eth103/1/26 Down       Po103
      Eth103/1/27 Down       Po103
      Eth103/1/28 Down       Po103
      Eth103/1/29 Down       Po103
      Eth103/1/30 Down       Po103
      Eth103/1/31 Down       Po103
      Eth103/1/32 Down       Po103
They are not visible: neither with the "show fex" neither with the "show int status", we cannot configure them....?
Do you think it's possible to access these ports by another way and configure them to allow some hosts to connect on it or is their purpose exclusively UPLINK?
best regards,
Eric Gillis

Do you mean the Fabric interfaces? If yes, you cannot use those for any host connectivities.
HTH,
jerry

Jumbo MTU on Nexus 2232 FEX

Hi,
This is related to bug CSCum09831 - jumbo MTU does not work on 2232 FEXes unless it is configured globally. Currently we have several qos groups with jumbo MTU enabled on only one of them and this setup works fine on 2148 FEXes but not on the 2232.
Now I want to enable Jumbo MTU on all qos groups but I'm not sure that this will solve the problem, any suggestions would be highly appreciated.
Thanks,
Adrian

Hi Adrian,
I checked the BUG and for 22XX Fex the Jumbo Frame configuration has to be done globally. This is part of the design for these series of Fex.
So i would suggest to enable Jumbo frames globally and see if the issue gets resolved. Else you can reach out to me i will be more than happy to assist.
Regards,
Seemab

Nexus 2232 and IBM 10 Gig CNA compatability

Has anyone got a good doc on software/hardware compatability for Nexus, specifically 2232, and IBM 10 Gig CNAs? Im struggling with some Unix guys, I can use this particular pair of 2232s all day, but when I link a new 770 VIO....nada. We bypass the 2232 and link to the 5596 and it links up immediately. I suspect the IBM CNA and compatability but need the proof. Stumbling google I didn't see anything but I don't speak Unix very well either. We're running 2232PPs on 5596s at 5.1(3)N2(1b). Any help is appreciated.

hi Robert,
thanks a lot for your reply.
here is the uplink port profile config:
port-profile type ethernet HostUplink
vmware port-group
switchport mode trunk
switchport trunk native vlan 1
switchport trunk allowed vlan 1-3967,4048-4093
channel-group auto mode on mac-pinning
no shutdown
system vlan 803,832,900-901
state enabled
803 is mgmt for both esx and vsm, 900 is control, 901 is packet.
my NC553i driver version is different from what you suggested, it is 2.102.518.0, any reason why you suggest to use the version you specified?
I have been trying to contact HP support, to be honest, not saying overall, but from my experience, they are much less helpful then Cisco support, I will keep trying.
thanks
ming

Nexus 9396PX support only with VTP transparent mode

Why Nexus 9396PX not support vtp server and client mode ?
We are using with 6.1(2)I3(2) version.
Thanks.

Is any expert out there who can answer my query ?. Much appreciated.

Servers connected to Nexus 5548 only getting 200 Mbps of throughput

Servers connected to NExus 5k were only getting 100 Mbps of throughput. So I disabled Flow control recieve on all the ports. After this we are getting 200 Mbps of speed. The servers are connected throuh 10 gig port. Could you guys please suggest why the throguhput is still low? Atleast we should get 1Gbps of thrpoughput.

Hi Adam,
I think we probably need a little more information to go on. Can you answer the following?
What type of servers and NICs?
What OS are you running on the servers?
What cables do you have from the servers to the switch?
Are the two servers in the same subnet or is the traffic between them routed?
If routed, is that in the Nexus 5548 or some other router?
How are you testing throughput?
Presumably you're not seeing any errors on the switch ports that the servers are connected to?
Regards

Le GLC-T et le nexus 2000

FR:
J'aimerai savoir si le GLC-T ( connecté à un des ports Hosts du Cisco Nexus 2232PP) supporte 10/100/1000 Mbps ou 1000 Mbps seulement ?
EN:
I want to knew if a GLC-T connected to a host port of Nexus 2000 (2232PP) is considerated as a 10/100/1000 Base T or only 1000 Mbps Base T ?
Merci

Think you Jeye
I had hoped for an answer with more technical document than the datasheet because some times we find in the datasheet writed 1G for GLC-T and it appears by the table of the compatibility matrix it can support 10/100/1000 Mbps ; BY EXAMPLE in the datasheet of Switch 3560 (
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps5528/product_data_sheet09186a00801f3d7d.html) nothing said that the GLC-T can support 10/100/1000 Mbps , you can see only 1000 Base -T But in reality this switch support 10/100/1000 Base T when you looked in the Matrix table :
http://www.cisco.com/en/US/docs/interfaces_modules/transceiver_modules/compatibility/matrix/OL_6981.html#wp142660
and you can notice in the matrix nothing special was said about GLC-T with the Nexus 2232
BUT I THINK YOU ! For your answer ( for me now the nexus 2232PP support only 1000 Mbps with GLC-T)
Best regards
Zammit Ikbel

Adapter-fex Supported VICs and Nexus Switches

HI,
I am thinking of using C220M4 in standalone mode. I have been reading about adapter-fex and I am wondering which Cisco VIC supports adapter-fex and which Nexus Switch will support adapter-fex.
I am thinking of using a VIC1225 and Nexus 3000.
Thanks.

I believe that adaptor fex is supported only with Nexus 5k and N2k:
Network Adapter Virtualization Design (Adapter-FEX) with Cisco Nexus 5500 Switches and Cisco Nexus 2232 Fabric Extenders
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/guide_c07-690080.html
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/data_sheet_c78-657397.html

Nexus 5548 L3 daughter card flapping

Hi guys,
Anyone of you here that experienced the logs below on their Nexus box:
2011 Dec 12 06:24:45 GDCNXS5K01 %BTCM-2-BTCM_LOG_ROUTER_ERR: router card in slot 3 has internal link(s) flapped: router ports down: 0x1a108000 0x1a109000 0x1a10a000 0x1a10b000 0x1a10c000 0x1a10d000 0x1a10e000 0x1a10f000
I am getting this log at least once a day. Seems like it is shutting down the SVI of the box after the said log occured. Good thing I have enable vPC and I am able to access the NXS5K through the vCP keepalive link (mgmt).
I have two Nexus 5548, but only one is experiencing the said error.
Any inputs, suggestions would be greatly appreciated.
Thanks,
Edzel

We had this same problem this past weekend, only in module 2 on a 5596.
In our case, we had rebooted our primary Nexus and found the following message immediately preceeded the BTCM error you noted:
%$ VDC-1 %$ %NOHMS-2-NOHMS_DIAG_ERROR: Module 2: Bootup diag detected major event: Forwarding ASIC failure: Ethernet2/9 Ethernet2/10 Ethernet2/11 Ethernet2/12 Ethernet2/13 Ethernet2/14 Ethernet2/15 Ethernet2/16
We replaced the module. A "show diag results module 3" would probably show you the same thing. However, I don't think the error message will show up until you reboot.
If your flapping Nexus is secondary, you probably won't notice anything major, but if it is your primary, it would probably affect your routing.

Nexus 1010 boot failed

Hi all,
I tried to boot nexus 1010, but only cimc can login. The serial console did not show any information, and still no response. So I tried to connect keyboard and monitor, both are no response. In addition, the nic port is down too.
Have any idea? Or who to troubleshooting it?
Sent from Cisco Technical Support iPhone App

Hello Padma,
Has this server worked before ?
-> Yes.
Are you able to access the N1010 host CLI interface by doing SSH to CIMC IP address ?
-> Yes.
ssh admin@ "connect host" did not show any response, and console can not return to CIMC.
Sent from Cisco Technical Support iPhone App

Strange nexus behavior

I'll try to explain this best i can . We have 2 6509's running port channels down to 2 Nexus 7000' where the 7000's are running vpc . All the routing is still being done on the 6509's . The nexus 7000's only have routing running via separate ospf links back to the 6509's . The plan is to eventually have the routing on the nexus so we have all the layer 3 SVI's that are on the 6509's defined on the 7000's with hsrp but all are admin down on the 7000's for now. On the 7000's all the routing looks correct with all the ip routes being learned on the separate ospf links. This is the strange thing from the 7000's if try to ping the svi addresses both the primary and secondary addresses on the 6509's they ping fine but if you try to ping any hsrp virtual address none of those ping . The really strange thing we see in the routing table on the 7000's is that hsrp virtual is put into the ospf table as a /32 with a source of the vlan that it is on on the 7000's which is admin'd down so obviously that traffic is not going to go anywhere if it's trying to send it down a admin down SVI . The actual subnet that the SVI is in is a /24 . So what we tried is we removed the downed svi on both 7000's and then cleared that /32 virtual address and it works correctly and the route for that address looks correct being the ospf uplinks to the 6509's . I'm not sure what to make of it . Is there some inherent difference in the way the Nexus handles hsrp even if it's admin'd down? Or can anyone explain this behavior . I will add this if you stick a device in that vlan on either the 7000's or a nexus 5000 which is below the 7000's configured with an address and the virtual address as the gateway it rides the vpc's as it should up from the 5000's to the 7000's and up to the 6509s . You can also ping the hsrp virtual from this device . The problem just seems to be with the nexus 7000 and ospf and the hsrp virtual address being in the table as a /32 pointing to a vlan which is admi'd down on the 7000's . Strange. Any speculation welcome...

Well there seems to be at least 2 or 3 bugs that are fairly close to this so my guess is it is a bug . Seems like there is more hsrp bugs than there should be on the Nexus platform. The only problem with this is a "clear ip route *" does not fix what we are seeing so we really don't have a fix for this issue.
STP vPC: route still installed after no hsrp
CSCuh07613
Description
Symptom:
hsrp vip is down by "shutdown" or "no hsrp", but route still installed
Conditions:
- On a N7k running 6.2(2)/6.2(2a) when a new SVI is created and HSRP is configured.
- disable hsrp by "no hsrp " or shutdown interface.
Workaround:
clear ip route *
Further Problem Description:
Customer Visible
Was the description about this Bug Helpful?
(0)
Last Modified:
Jan 2,2014
Status:
Fixed
Severity:
3 Moderate
Product:
Cisco Nexus 7000 Series Switches
Support Cases:
5
Known Affected Releases:
(2)
6.2(1.111)S5
6.2(2a)

Nexus 5548 - %ARP-3-DUP_SRCIP_PROBE: Duplicate address Detected

Hello.
Looking for some assistance on the following please, I'll try to include a lot of detail:
I noticed we're receiving repeating messages on a pair of Nexus 5548UP switches, regarding duplicate IP's, and the IP's in question are the mgmt0 of each respective Nexus switch; which are connected to each other and uplinked to two 3750X switches which are also linked to each other (not as a stack, with optics).
Here is a sample of the syslog message: %ARP-3-DUP_SRCIP_PROBE: arp [####] Duplicate address Detected. Probe packet received from zzzz.zzzz.zzzz on mgmt0 with destination set to our local ip, xxx.xxx.xxx.xxx
And in ascii art, here is a diagram: SW1&2 are 3750X (running 15.x code) and NX1&2 are Nexus 5548UP (running 6.x code)
SW1---SW2
| |
NX1---NX2
Pretty basic box/"ring", just in case the diagram doesn't format well, with rapid spanning-tree in effect. The Nexus are Layer2 only, and the 3750X's are Layer 2 & 3 /w HSRP on a few SVI's in them. All vlans can pass over the connecting trunks. And on the Nexus, the management interface (mgmt0) is connected to 3750X (NX1 to SW1 and NX2 to SW2); e.g. management is done over this vrf interface, versus it flowing through a trunk interface to a SVI on the Nexus.
I know these messages to be erroneous as far an being actual duplicate IP's on the network, and have seen a few posts that indicate a command ("no ip arp gratuitous hsrp duplicate") typically referencing a Nexus 7000 setup has helped, but obviously as described that's not involved here. Note: Placing that command on the mgmt0 interface of the two nexus had no positive effect. The messages didn't start showing until after HSRP was enabled on the applicable 3750X SVI's - so seems a likely correlation.
Essentially looking to clear this up (ideally) or suppress the messages since they're false. Any ideas?
Thanks!

For those encountering this same issue, here is some information that may lead you to a resolve.
I decided to open a TAC case to get some direct assistance, and I was directed to the 3750X's and a new feature in the 15.x code, "ip device tracking". I was directed to remove that without specific details / steps on how to best do it (e.g. "no ip device tracking" does not remove it from the global config, as of 15.2(1)E anyway and is the most current at the time of this posting), and that didn't take, giving the message: % IP device tracking is disabled at the interface level by removing the relevant configs. However, after doing some research on the command, I can across some similar posts on 15.x code and duplicate IP messages.... Here's two posts I referenced:
https://supportforums.cisco.com/thread/2244042
https://supportforums.cisco.com/thread/2239656
I opted for the "no macro auto monitor" command in the 3750X's in global config, as mentioned in the above post(s) - This did stop the messages from occurring in the Nexus switches. IMPORTANT NOTE: I noticed that it did appear to bounce all the switch ports however, which could impact production - Be advised!
I cannot speak to if the interface level command 'nmsp attach suppress' is a better route to go, which is also referenced in the posts (first one primarily) - I went the other route to not have all the extra config line entries. I have asked Cisco what the true impact of the "no macro auto monitor" command is, and am waiting a response - Ideally there's little to none, probably depending on if you want to make use of device tracking or not... in my case, I suspect I don't have a need for this and thus there's no impact - I shall see.
It would be ideal if code is released to disable this service / feature in the future more gracefully and/or code changes are done to remedy this issue so you can have the feature enabled (or not). I akin this much like the "vstack" service that was introduced around 12.2(55/58)SE IOS that couldn't be disabled & left an open TCP port (not good for security scans), then with 12.2(58)SE2 they allowed it to be disabled (e.g. "no vstack" in global config).
Hopefully these details prove of value.
Regards.
NOTE: Since it doesn't seem you can"answer" your own posts, which seems silly; please note I consider this item resolved / answered.

Nexus 5K

Dears,
I have a situation now where most of my servers are not supporting FCOE so basically each server will have 4 Links , 2 Links will be Ethernet for users reach-ability and 2 links for pure FC storage. Now since im getting Nexus 2k that only supports 1 GiG ethernet connection i'll connect those 2 Ethernet server legs to the N2k and from the N2k there will UPLINK to two different Nexus5K (VPC) now i'll be left with the 2 FC server Links can i connect it direct to the Nexus5K and connect my Storage Pool which is pure FC also ???.
Thanks in advance

Hi Inayat..
Thanks agian, actually i need to configure track via tracking ip sla. If ip sla does not in nexus 5k, could you suggest any other option.
Using IPSLA i was trying to monitor icmp for a ip.
pls help.

There will be no 64gb Nexus 6 ??!!?

I have an upgrade coming up and was so happy to see that Verizon announced it was going to carry the Nexus 6.
When I look on the smartphones page at the Nexus 6 they only show it in 32gb. Is it possible that they'd only carry the smallest size? I was just talking to some co-workers about it and they agree that this is surprising. It's not something I'd even consider as you loose a big chunk of that to the OS. I watch tv and movies from google play at the gym with unreliable wifi and HAVE GOT TO HAVE more memory for downloads. I also keep gigs of personal music and pictures on my phone. Also I use it for work and have keep work some work documents too.
I hear Tmobile has it in 64gb. Maybe I'll consider this when my contract is up.

The fact that it is a Nexus is why we want it. The fact that when one day we have had enough of Verizon's ** we can take the phone to any carrier we want. There will come a point in time where your better network will not outweigh the rudeness and brashness and runaround we get from you.
Why Nexus 6?
Fastest updates of any Android phone. No touchwhiz or sense skin over android. Oh and that beautiful screen.
Everything with you is a fight. Keep my off contract discount fight, activate my Nexus 6 on Verizon fight. Then the funny part is if you look up Nexus 6 on Verizon website. It says all sizes and colors supported!

Nexus 2232 - 10gig only

Similar Messages

Maybe you are looking for