Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm setting up our A700, and need to figure out how to convert e4e 40g to the e4e-h 10g ports. I have the breakout cabled up between the A700 and the end network switches. Where is the magic setting to make this happen?
Solved! See The Solution
1 ACCEPTED SOLUTION
coreywanless has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey Corey,
You can convert the ports from 40 GbE to 10 GbE in maintenance mode. The command is
*> nicadmin convert –m [ 40G | 10G ] [ port ]
So if your 40g card is in slot 4, run
*> nicadmin convert -m 10G e4e
Converting e4e 40G port to four 10G ports
Halt the system, install/change the cable, and then reboot for conversion to take effect
I hope this helps! Let us know if this works for you.
Best regards,
Dirk
9 REPLIES 9
coreywanless has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey Corey,
You can convert the ports from 40 GbE to 10 GbE in maintenance mode. The command is
*> nicadmin convert –m [ 40G | 10G ] [ port ]
So if your 40g card is in slot 4, run
*> nicadmin convert -m 10G e4e
Converting e4e 40G port to four 10G ports
Halt the system, install/change the cable, and then reboot for conversion to take effect
I hope this helps! Let us know if this works for you.
Best regards,
Dirk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That was it. Thanks for the quick feedback.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you convert a single port to 4x10 10GBE and leave the other as a 40GBE ISL port?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If I understand you, yes, we have that configuration:
e4a Cluster Cluster up 9000 auto/40000 healthy false
e4e Default - up 9000 auto/10000 healthy false
e4f Default - up 9000 auto/10000 healthy false
e4g Default - down 1500 auto/10 - false
e4h Default - down 1500 auto/10 - false
e4a is the 40GB connection back to Cluster Switches
e4e and e4f (two of the 40g to 10g split are ran to our network switches)
e4g and e4h are just hanging there on the other end. (Messy, but it is what it is)
If you are talking about the configuration on the other end (Where the 10g splitter connects into) You will need to create a ifgrp on the Netapp side, and a port-channel side to bond them all together.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Yes, that was the question. I should have provided more info but your answer is perfect despite my incomplete question.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
to follow up this thread, if I have two 40GbE ports, one is in slot 4, and the other is on onboard. If I want to setup 4x10GbE, should I just use all 4 split 10GbE from a single 40GbE port, or 2 x 10GbE from each 40GbE port should one of 40GbE port get failed, then the other 2x10GbE from the other 40GbE port would be still alive? I don't know enough about 40GbE port, could entire port go down at all?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When we tried the
*> nicadmin convert –m [ 40G | 10G ] [ port ]
and we get the following error "Firmware needs to be updated to complete the change", this is on a FAS90000. We cant seem to find if anyone else had this error. Everything we checked all seems to up to date.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Follow up to our issues, we needed to update the OnTap version to 9.7P22, once we completed the upgrade the command worked. The version we were running (9.5P2) was on the doc as an approved version for that command but that was not the case.