Port Mapping 6120 to 6248 FI Upgrade

I am planning the upgrade for our 6120XP FIs to be replaced with 6248s.  I have the read the upgrade guide and need a little clarification.  In our 6120s we are utilizing the N10-E0060 FC expansion slot for storage connectivity.   We are not utilizing an expansion module with our 6248s as the 32 fixed universal ports provide sufficient port capacity for our environment.
The upgrade guide refers to mapping slot 2 ports on the 6120 to slot 2 on the 6248.  How do I proceed with the upgrade process without slot 2?  Will the 6248 automatically detect the FC SFPs in the higher order fixed ports and divide the slot 1 ports into Ethernet and FC pools automatically?  Or do I need to manually specify the division between Ethernet and FC?    I am also assuming that manual remapping will be necessary as I will be changing from 2/X ports to 1/X ports?
Thanks!

In line with what Chris stated about the unified port wizard. The FC port/Ethernet ports must be contiguous, what I mean by this is that you can't make ports 1/12-13 FC and then make ports 1/14-5 Ethernet. Best practice is to start at the right and work to the left for the FC ports. I usually make at least ports 1/29-32 FC, this will give you 4 FC ports, for larger environments I would do 6. You must do this on each Fabric Interconnect but only do 1 at at time. As soon as you hit finish on the unified port tool the FI will reboot.
If you had the optional expansion module and you changed some of those ports to be FC then only the expansion module would get reset instead of a switch reboot.
I did a blog post on this subject last year - http://jeremywaldrop.wordpress.com/2011/11/08/cisco-ucs-6248-unified-port-configuration/

Similar Messages

  • AEBS Gigabit 802.11n FW 7.2.1 - OS X 10.5.1 Port Mapping HELP!!!!

    Hi
    I have a AEBS with Gigabit Ethernet upgraded to Firmware 7.2.1. I am running OS X Leopard 10.5.1 and I am unable to successfully forward ports. Every time I query a port that I believe to have mapped successfully it appears closed using canyouseeme.org.
    I have followed numerous instructions, but they all seem to be instructions for Tiger, I'm wondering if a setting has been missed. I have successfully assigned a static IP address to my machine but still the port appears to be closed. I do run the Leopard firewall using specific applications option (the third one), but I have also tried it with the firewall off and it still hasn't changed anything, the ports are always closed.
    So now I'm pretty much stumped. Has any one actually managed to get a setup similar to mine working, with the ports being open? All advice appreciated.
    Thanks
    Message was edited by: dalyboy

    Hello dalyboy. Welcome to the Apple Discussions!
    Try the following to see if it will help ...
    To setup port mapping on an 802.11n AirPort Extreme Base Station (AEBSn), either connect to the AEBSn's wireless network or temporarily connect directly, using an Ethernet cable, to one of the LAN port of the AEBSn, and then use the AirPort Utility, in Manual Setup, to make these settings:
    1. Reserve a DHCP-provided IP address for the host device.
    Internet > DHCP tab
    o On the DHCP tab, click the "+" (Add) button to enter DHCP Reservations.
    o Description: <enter the desired description of the host device>
    o Reserve address by: MAC Address
    o Click Continue.
    o MAC Address: <enter the MAC (what Apple calls Ethernet ID if you are using wired or AirPort ID if wireless) hardware address of the host computer>
    o IPv4 Address: <enter the desired IP address>
    o Click Done.
    2. Setup Port Mapping on the AEBSn.
    Advanced > Port Mapping tab
    o Click the "+" (Add) button
    o Service: <choose the appropriate service from the Service pop-up menu>
    o Public UDP Port(s): <enter the appropriate UDP port values>
    o Public TCP Port(s): <enter the appropriate TCP port values>
    o Private IP Address: <enter the IP address of the host server>
    o Private UDP Port(s): <enter the same as Public UDP Ports or your choice>
    o Private TCP Port(s): <enter the same as Public TCP Ports or your choice>
    o Click "Continue"
    (ref: "Well Known" TCP and UDP ports used by Apple software products)

  • Port mapping stopped working using Mavericks

    Hi,
    on Snow Leopard, I had iVPN using port mapping up-and-running.
    Basically using this explanation (https://discussions.apple.com/docs/DOC-3415).
    On Mavericks it stopped working.
    I'm running AE 7.7.2, and Mavericks 10.9.1.
    Tools I tried are iVPN together with a DynDNS setup (also the Personal Website).
    I don't get non of these working anymore...
    Any ideas?
    Regards.

    OK solved, or at least the problem was not with the modem or router.
    Oddly, enough the app I was using to test the port forwarding did not recognize that the ports were open. Nor did the internet via canyouseeme.org. However, when I tried a previous version of the same app, it worked fine.
    I am still using 7.6.1, but I will upgrade the firmware and see if things are still ok.
    Sorry to clog up the boards with what turned out to be a non-issue. I'd erase this post if I knew how.

  • Port Mapping Question

    Well, I thought I had this all figured out...
    About a year ago I set up an older AirPort Extreme Base Station (Version 5.7) successfully to port to an iMac running OS X Tiger Server. As Leopard came out I decided that I wanted to do a little upgrading around the house and purchased the new AEBS along with a Mac Mini to run the new server software.
    I have no problems getting the AEBS set up, but the port mapping just doesn't seem to work correct.
    Right now I reverted back to the old system and seem to be serving just fine on the Mac Mini with OS X Leopard Server... But I'd really like to leverage the new AEBS.
    So, anyone out there can offer some advice on one of the settings I seem to be missing that seems to make this not work?
    Thanks

    It might also be a DCHS/NAT problem...
    Here's a post I added this morning...
    http://discussions.apple.com/thread.jspa?threadID=1320615&tstart=0

  • Port mapping converting gui to cli

    Hi,
    I am having an issue with a new office LAN implementation and I was wondering if anyone can help.
    The current setup has a Linksys router and there are port mappings for the servers for a inside and outside port. This has been input via GUI. I am upgrading to a 3845 router and have converted the GUI input to Cisco CLI. This however does not work and the LAN does not behave as it did before.
    The Linksys GUI input is attached.

    Hi @samdilloway,
    A few questions for you:
    Did you check if those servers can go to the internet?
    Is the NAT functioning properly when they go outside?
    Here is a link of a page with the step-by-step process of the port mapping configuration. Make sure you're doing it exactly like that:
    http://kb.linksys.com/Linksys/ukp.aspx?pid=80&vw=1&articleid=21470
    Also, a link of a TSHOOT page for the same problem:
    http://kb.linksys.com/Linksys/ukp.aspx?pid=80&vw=1&articleid=22385
    To be sure, the problem that you have is that users from outside cannot access to the services your mapping, right?
    Let me know your answers.
    HTH.
    Don't forget to rate.
    Rgrds,
    Martin, IT Specialist

  • Port Mapping control page missing under firmware 7.3.2

    The reference to "port mapping" on page 55 of the manual "Designing AirPort Networks Using AirPort Utility Mac OS X v10.5 + Windows" is now missing following upgrading my Time Capsule to firmware 7.3.2 - see:
    http://manuals.info.apple.com/en/DesigningAirPort_Networks10.5-Windows.pdf
    Could anyone out there shed some light on where this functionality has gone?
    Further to this can anyone advise where I might access firmware v 7.3.1 so that I can regain this functionality?

    This query can be disregarded.
    It appears the v7.3.2 firmware upgrade reset the 'Connection Sharing' to 'Off (Bridge mode)'.

  • New Airport Extreme (802.11n): :  Port Mapping... ***???

    There are two different programs I was formerly using, whereby (after following instructions) I was able to create a static IP address for every machine on my network, plus open ports 8000 and 9990-9998 respectively. But ever since upgrading to the new Airport Extreme (802.11n), it completely stopped working. To boot, I've upgraded to Leopard on one of two of the machines (the other is still using 10.3.9).
    I haven't been able to figure out for the life of me, how to configure it. It's no longer as obvious where and what information to put in. All guides that would remotely help are designed for the older Airport unit, which has completely different menus in the Airport Utility.
    Is there anyone out there who has experience with Dot-Tunes and/or Nicecast or similar port mapping, who has the patience to describe, in layman's terms, what steps to take to get this set up correctly again, starting with how to reassign static IPs for my machines. I will not ask a lot of questions and take up too much more of your time. I'm just frustrated after a whole day of trying to figure this out and fruitless Google and forum searches.
    Thank you so much.

    I'm not familiar with either Dot-Tunes or Nicecast, but the following would be the general port mapping procedure with the 802.11n AirPort Extreme Base Station (AEBSn) using the AirPort Utility. Note in this procedure you will not need to assign a static IP address for each of your host devices. Instead you will be taking advantage of the AEBSn's DHCP reservations feature.
    To setup port mapping on an AEBSn, either connect to the AEBSn's wireless network or temporarily connect directly, using an Ethernet cable, to one of the LAN port of the AEBSn, and then use the AirPort Utility, in Manual Setup, to make these settings:
    1. Reserve a DHCP-provided IP address for the host device.
    Internet > DHCP tab
    o On the DHCP tab, click the "+" (Add) button to enter DHCP Reservations.
    o Description: <enter the desired description of the host device>
    o Reserve address by: MAC Address
    o Click Continue.
    o MAC Address: <enter the MAC (what Apple calls Ethernet ID if you are using wired or AirPort ID if wireless) hardware address of the host computer>
    o IPv4 Address: <enter the desired IP address>
    o Click Done.
    2. Setup Port Mapping on the AEBSn.
    Advanced > Port Mapping tab
    o Click the "+" (Add) button
    o Service: <choose the appropriate service from the Service pop-up menu>
    o Public UDP Port(s): <enter the appropriate UDP port values>
    o Public TCP Port(s): <enter the appropriate TCP port values>
    o Private IP Address: <enter the IP address of the host server>
    o Private UDP Port(s): <enter the same as Public UDP Ports or your choice>
    o Private TCP Port(s): <enter the same as Public TCP Ports or your choice>
    o Click "Continue"
    (ref: "Well Known" TCP and UDP ports used by Apple software products)

  • DPC3941t Gateway - Port Mapping

    After swapping out my TC8305 gateway for the DPC3941t yesterday, I changed the local IP configuration from 10.0.0.1 to 192.168.1.1, as my home network is configured that way.  My NAS and security cameras did not reconnect, and I did a hard reset on them and reinstalled with their setup files.  After the first one was installed and working properly, and I was able to access it, I tried to access the gateway home page and it was blocked.  I restarted it and was then able to log in.  I installed the second camera and the same thing happened.  The event log showed 88 entries of port mapping and port deletion.  I was told by tech support last night to hard reset the gateway and start all over.  I did the reset and am back at 10.0.0.1, with my NAS and cameras unreachable.  The NAS and cameras worked fine on the TC8305, and the TC8305 worked fine until the last upgrade.   They scheduled a technician to come back tomorrow but they don't do router configuration, only swap one out for another.  Is there any fix for this other than my going out and buying a separate modem and router?  Thank you for any enlightenment out there.  Kat.

    JayInAlg wrote:
    My personal recomendation is to your your own high end router so you are in complete control of your network settings and port forwarding.  If you don't have Comcast digital voice phone service, then you certainly can purchase your own modem also.  If you do have CDV, then get the gateway place in bridge mode and connect your own router to LAN port 1. You will always be fighting this situation if you keep Comcast's gateway, which is deigned for basic internet funtions.I tried to work with the Comcast equipment due to my history of buying modems and routers that quit working shortly after their 1 year warranty expired.  For the last 7 years, when a modem quit working, I called Comcast and they brought me a new one.  I upgraded routers several times, never spending too much on one.  I had the TC8305c gateway for the past 2 years and never had a problem with it until last month.  However, now it is time to go back to the two box system.  You are absolutely right. I bought an Arris/Motorola SB6183 modem and a Netgear WNDR4500 router yesterday.  Due to Murphy's Law, I did the setup backwards.  First, I put the gateway in bridge mode.  Then set up the router.  Then I disconnected the gateway and connected the modem to the coax, and ethernet to my computer.  Did the activation through the browser, shut down the modem, connected the router and powered up both boxes.  Everything is working fine.  The NAS and the security cameras came back online without any reconfiguring.  The guest network is on. Everyone is happy.  Took less than an hour. Thank you for pointing this out to me.  I hope the modem and router last longer than the 90 day warranty.  I bought the protection plan, although they won't bring me a new one like Comcast did.  Wish me luck.   Kathy 

  • Setup Port Mapping

    For the life of me, I cannot see anywhere on Airport Utility a place to set port mapping for an airport extreme. I need to setup port 80 and there is no documentation ANYWHERE online to do that. I see one site which shows a tab on airport utility that says port mapping, but I guess that was killed in an upgrade cuz it ain't on mine!!!! Any help would be great

    Try the following basic procedure to configure port mapping on the 802.11b/g AirPort Extreme Base Station (AEBS):
    Port mapping, under Leopard with the 802.11g version of the AEBS, will require at least two steps:
    1) Assign a static IP address for the host computer that will be accessed from the Internet.
    2) Configuring port mapping on the AEBS.
    1. Assign a static IP to the host device
    System Preferences > Network > Show > AirPort > TCP/IP
    o Configure IPv4: Manually
    o IP Address: <choose an IP address outside of the AEBS's DHCP range: 10.0.1.2 - 10.0.1.200>
    o Subnet Mask: 255.255.255.0
    o Router: 10.0.1.1
    o DNS Servers <your ISP DNS server IPs>
    To setup port mapping on an AEBS, either connect to the AEBS's wireless network or temporarily connect directly, using an Ethernet cable, to the LAN port of the AEBS, and then use the AirPort Utility, in Manual Setup, to make these settings:
    2. Setup Port Mapping on the AEBS.
    Advanced > Port Mapping tab
    o Click the "+" (Add) button
    o Service: <choose the appropriate service from the Service pop-up menu>
    o Public UDP Port(s): <enter the appropriate UDP port values>
    o Public TCP Port(s): <enter the appropriate TCP port values>
    o Private IP Address: <enter the IP address of the host server>
    o Private UDP Port(s): <enter the same as Public UDP Ports or your choice>
    o Private TCP Port(s): <enter the same as Public TCP Ports or your choice>
    o Click "Continue"

  • Port mapping reverts to blocking

    I'm using an airport extreme to connect an Imac to a slimserver to play bbc radio via alienbbc.
    This requires port mapping 554 which can be arranged via the advanced menus, my problem
    is that when rebooting after software upgrades, airport seems to forget about this. More
    explicitly, trying to initiate a bbc stream produces a console message indicating that the
    connection on port 554 was "refused" and the connection is aborted. Getting
    into the airport assistant, verifying that that this port is still mapped and then rebooting the
    airport seems to bring it back, but this is quite a nuisance. If anyone has any advice on this
    I would be most grateful.
    This question was posed earlier in early October, but received no response.
    Since then I've observed that the
    reversion happens not only after upgrades, but occurs quite spontaneously. Since it takes
    several minutes to restore the setting, I really hope that someone has some explanation that
    will help to resolve the problem.

    Hi Michael,
    do you remeber how you solved this problem? We have exactly the same behaviour:
    After a release change from BW 3.x to BW 7.0 we call an ABAP-based web template with http://<host>:8000... The browser automatically changes this URL to http://<host>:50000. How can we switch this off?
    Thanks in advance and kind regards
    Joerg

  • AEBS no longer forwards port 80 after 7.3.1 upgrade?

    After upgrading to firmware version 7.3.1, AEBS no longer forwards public port 80 to private port 80 of my LAN Linux server running Apache. The port mapping configuration hasn't changed from the time before the upgrade. I've seen a lot of reports regarding problems with DMZ, but this is using just a straight port mapping.
    When I try accessing my public IP via port 80, the connection is simply refused. nmap -P0 -p 80 shows port 80 as filtered, when it should be open like it was previously with the exact same configuration. (Naturally I've checked that Apache is running properly and is accessible from within the LAN.)
    Deleting the port mapping and recreating it didn't help.
    Curiously, the problem seems specific to a port mapping of public 80 -> private 80. All other port mappings (all of which also existed before the firmware update) still work. These include pub 22 -> priv 22 (for SSH) and pub 113 -> priv 113 (for identd). The internal IP address for the server where the forwardings point to is a MAC address-based permanent DHCP lease in the 192.168.1.x scope, and it has remained unchanged throughout the firmware upgrading and port mapping process.
    There's a workaround, but I think it's ugly. If I forward another public port, say 8080, to the private port 80, the mapping works. This means I can successfully connect from the outside world using http://my.public.ip:8080. Not pretty, and it's obviously a bug, so I don't consider this a solution.
    Has anyone else encountered the same problem? I've reported it to Apple some time ago, but haven't received a reply yet. It'd be great if there was a fix that didn't involve waiting for another firmware upgrade and hoping for the best, or downgrading.

    I'm not sure about port 80, but i know (at least before the upgrade) port 53 (DNS) was being freaking intercepted by the AEBS for some reason, instead of forwarding to the DMZ like it should. I haven't checked this behaviour yet with 7.3.1. Easily the stupidest $#%@ thing i've ever seen a router do.

  • How do I use Port Mapping?

    b How do I use Port Mapping?
    (This document will assume that you are using and ABS/AEBS/AX as an internet router and have DHCP & NAT turned on.)
    Sometime you may want to offer access to a computer on your AirPort network to users on the internet, whether it be a web site, or for file sharing, or just remote access for yourself when traveling. If any of these sound like something you want to do, then you need to understand how Port Mapping works.
    b AirPort as Firewall
    Most of the time your AirPort base station will not let any traffic into your network which did not originate from your network. It will let everything out and replies to your traffic back in, but it will not let sessions initiated on the internet side of the base station in to your network. This is what is referred to as the "NAT firewall" capability of the base station and it provides effective protection for your network from the internet. What Port Mapping does is poke a hole in this wall to allow certain type(s) of traffic into the network and direct this traffic to a specific computer on the network. In the firewall world this is commonly referred to as an "inbound proxy" or "inbound translation" rule or "PAT" (Port Address Translation) in the router world.
    b The Need for Manual Addressing
    Since a Port Mapping entry in the base station configuration requires an inside private IP address to be specified, the computer to which to mapping entry applies should always have the IP address specified in the mapping entry. Thus, DHCP should not be used for a computer offering services on the internet as the Port Mapping entry will no longer work if the target computer's IP address changes. In general, an Apple base station's DHCP server will try to assign IP addresses in the 10.0.1.2 to 10.0.1.200 range. IP addresses above 10.0.1.200 can be Manually assigned to computers and other devices on the network up to 10.0.1.254. 10.0.1.255 is reserved (it is the broadcast address for the 10.0.1 subnet). To Manually set up the TCP/IP information for a Macintosh running Mac OS X, go to System Preferences -> Network and "Show" the appropriate interface (Ethernet or AirPort) and click on the TCP/IP tab. Select "Configure Manually" and enter the following information:
    IP address : 10.0.1.201 (or whatever address you decide to use)
    Subnet mask : 255.255.255.0
    Router IP : 10.0.1.1 (the AirPort base station LAN IP)
    DNS server : 10.0.1.1, or whatever DNS server IP your ISP uses
    After making these changes verify that your computer can still access the internet and local resources on the LAN before continuing.
    b Port Mapping a service
    In our example we will be hosting a web site on a computer which we have given an IP address of 10.0.1.201. Basic web sites are accessed using the HyperText Transport Protocol (HTTP) and this protocol typically uses port 80 to communicate. In order for others to see the web site, we must configure a Port Mapping entry in the base station configuration to not only allow the web browsers in, but to tell the base station what IP address the web server is using. The Port Mapping entry has three parts: Public Port, Private IP, and Private Port. In this case you would use the following values:
    Public Port : 80
    Private IP : 10.0.1.201 (this is the computer hosting the web site)
    Private Port : 80
    In order to access the web site from the internet, users must reference the base station's WAN port public IP (determined by looking at the base station configuration summary page in the AirPort Admin Utility). Since this address may change over time, you might want to use a Dynamic DNS service to simplify connecting for your users.
    Sometimes the port you wish to use may be blocked by the ISP. In this case, use a different non-standard Public Port number for the service, but keep the Private Port standard. In the above example, if the ISP was blocking port 80, you could potentially use 8080 instead, so:
    Public Port :

    Public Port : 8080
    Private IP : 10.0.1.201
    Private Port : 80
    Your users would then have to enter "http://<publicIP>:8080/" (where <publicIP> is the public IP address of the AirPort base station) to access the web site.
    b Internal Access
    It should be noted that when accessing these services from within the network you cannot reference the Public IP/Public Port, but rather you must use the Private IP/Private Port. Thus, "http://10.0.1.201:80/" in the above example.
    b Limits and Options
    There is a maximum of 20 Port Mapping entries that can be made in an Apple base station configuration. If you use an AirPort Extreme or AirPort Express base station there is an option which can be helpful in the case where you need many ports opened to a single computer. This is the "Default Host" option. When using this it is not necessary to use Port Mapping at all as all ports will be opened to the specified "Default Host". This is found in "Base Station Options". The default IP address for the "Default Host" is 10.0.1.253. You may change this IP address. The target computer must be Manually configured as specified above with the same IP address. Since all ports are now open to this computer, you should enable and configure the Mac OS X firewall on the default host computer to protect it from intruders.
    b Useful Related Links
    <a href="http://docs.info.apple.com/article.html?artnum=52002>"Designing AirPort Extreme Networks: Manuals</a>
    "Well Known" TCP and UDP Ports Used By Apple Software Products
    IANA Port Number Assignments

  • Cisco ASA 5505 - Port Mapping

    Hi, I'm new into IT and I was wondering if somebody could help me set up Port Mapping. Here's my scenario - 
    We have set up an Asterisk VoIP server that uses UDP port 5060 and another port range, and we want any public incoming connections destined for our Asterisk server on Port 5099 to be translated at the firewall to go to our Asterisk server on port 5060. I have been using ASDM 6.4 but theres no easy way to do this (as far as I know, and why I've came here looking for an answer).
    We have currently just left port 5060 open to the public (so our home workers can use our phone system) but really want to get this sorted ASAP due to SIP Bots that look for ports like 5060 that are open!!
    Any help would be greatly appreciated and if anybody needs anymore information just ask!!

    Hi,
    You need to have a NAT rule set for port-forwarding to make as per your requirement..... I will give you cli based configuration example....
    If your ASA is running with pre-8.3 version:
    static (inside,outside) tcp interface 5099 192.168.1.10 5060 netmask 255.255.255.255
    If your ASA is running with post-8.3 version:
    object network SERVER-01
    host 192.168.1.10
    object network SERVER-01
    nat (Inside,Outside) static interface service tcp 5099 5060
    Regards
    Karthik

  • How do I configure my airport utility for port mapping?

    I am trying to view my FOSCAM cameras over the internet while away from home. They work fine in my house using Wi-Fi. Instructions say to do port forwarding. I have cameras set up, but can't get my router to port forward. I found "Port Forwarding" in Airport Utlility then NETWORK. 'Router mode: DHCP and NAT';on 'Port Settings I click on the "+" at the bottom. 'Private IP Address: populates to 10.0.1.201'. What goes in the other blocks?

    Please check out the following AirPort User Tip for details on how to configure Port Mapping on the AirPort routers. I would suggest that you check your FOSCAM documentation as to what TCP and/or UDP ports are required to access their IP cameras from a remote location.

  • Port Mapping is not working ?

    First of all, sorry for my bad english as it is not my primary language.
    So my problem is that I play Warcraft 3 and that I would like to host some games. To be able to host, I have to do port mapping for the ports : 6112-6119, which I did in the Airport Utility --> Advanced --> Port Mapping. I did it for every port 6112, 6113, etc. But the thing is that when I go on this website: http://www.whatsmyip.org/ports/games/ (Which is a website that tells me what ports are open on my computer), only port 6112 is open. Ports 6113-6119 are closed. Before my Airport Extreme, I had a Linksys and I had no problems with hosting and port mapping, which means it is not my ISP that is blocking the ports.
    Also this is the setup of my internet if it can help. I have an AirPort Extreme wich is connected to the modem in my basement (I did the port mapping on this one) . From this Airport Extreme, I have another Airport Extreme connected to it. I am connected to the second Airport Extreme in bridge mode with ethernet.
    I don't know if this was clear or not lol. Anyway I would appreciate any help. Thank You !

    This is just a guess, but if you still have that AirPort Extreme, you might plug it in long enough to have AirPort Utility do a File >Export Configuration File, then reconnect the Time Capsule and do a File > Import Configuration File.  Once that's done you may have to do a little adjustment to account for the disk drive.

Maybe you are looking for