Port trunking on 9506

hi, would there be any advantage to do a port trunk to gain performance increase in speed/io through put?
scenario is as follows, I have 2 9506's, two seperate fabrics.
one netapp filer that has 8 ports, 4 for tape and 4 for disk luns.
would it make sense to create a port trunk for the 2 x 2 ports for tape or disk ?
I guess I am thinking like a bonded network for performance like in cisco switches, but does this apply to fc as well?
thank you

in FC world you create port-channel for switch to switch communication, not between target and initiator.
@dynamoxxx

Similar Messages

[svn:fx-3.x] 5820: Merged (back ported) trunk revisions 4460,4492,4516,4520 ,4585,4630,4692,4726,4964 - 3.x

Revision: 5820
Author: [email protected]
Date: 2009-03-31 13:40:12 -0700 (Tue, 31 Mar 2009)
Log Message:
Merged (back ported) trunk revisions 4460,4492,4516,4520,4585,4630,4692,4726,4964 -> 3.x
http://10.171.12.252/svn/opensource/flex/sdk/trunk
r4460 | [email protected] | 2009-01-08 20:53:33 -0500 (Thu, 08 Jan 2009) | 10 lines
Renamed UIComponentAccImpl to UIComponentAccProps because it extends AccessibilityProperties, not AccessibilityImplementation.
Added comments with the identifier for each magic role constant, so that it is easier to understand what roles our components are using.
Moved two static methods from UIComponentAccProperties to AccImpl because they make more sense there.
QE Notes: None
Doc Notes: None
Bugs: None
Reviewer: None (no functional changes)
r4492 | [email protected] | 2009-01-12 17:47:10 -0500 (Mon, 12 Jan 2009) | 8 lines
Simplified how an accessibility class gets hooked into its corresponding component class.
We now do the hooking in the static method enableAccessibility(), which is called by code that is autogenerated by the compiler. Previously this method did nothing and the hooking happened at static initialization time. This allows us to remove the static var accessibilityHooked and the static method hookAccessibility() in each accessibility class.
QE Notes: None
Doc Notes: None
Bugs: None
Reviewer: Deepa and Alex
r4516 | [email protected] | 2009-01-13 18:23:14 -0500 (Tue, 13 Jan 2009) | 16 lines
Accessibility changes to Panel and TitleWindow, as requested by Freedom Scientific.
These components now report their accessibility role as "grouping" rather than "window". Their accessibility name is now simply their title. They no longer report any child items. Their accessibility location is the bounding rect of the entire Panel or TitleWindow.
The AccessibilityImplementation continues to be attached to the titleBar, not to the Panel/TitleWindow, because the Flash Player ignores Sprites with an AccessibilityImplementation that are inside other Sprites with an AccessibilityImplementation. (The Flash accessibility model is flat, not hierarchical, and "child IDs" are only used for things like list items, not for controls in titled container.)
So although in the display hierarchy the Panel is a parent of its content controls, in the MSAA model it appears as their preceding sibling. JAWS will look at the "grouping" role and understand that because the bounding rect of the grouping includes some of its following siblings, they are "inside". (I don't know what this means in terms of what JAWS will actually speak.)
Also, the AccImpl class now implements getChildIDArray() to return an empty array, so that by default all components have 0 child items (rather than reporting an error).
Finally, subclasses with child items now compute how many they have and then call a new AccImpl utility method, createChildIDArray(), to create an Array that looks like [ 1, 2, 3, 4, 5 ].
QE Notes: None
Doc Notes: None
Bugs: SDK-12390, SDK-16340
Reviewer: Deepa
r4520 | [email protected] | 2009-01-13 20:07:53 -0500 (Tue, 13 Jan 2009) | 10 lines
Accessibility changes to List, DataGrid, Menu, and Tree, as requested by Freedom Scientific, to behave more like their corresponding standard Windows controls.
List, DataGrid, and Menu no longer report an accessibility value, either for the control itself or for its child items.
Tree no longer reports a value value for itself. For tree items the value is the indentation level as a String: "0", "1", "2", etc. Previously the top-level items had value "1" instead of "0".
QE Notes: None
Doc Notes: None
Bugs: SDK-17755
Reviewer: Deepa
r4585 | [email protected] | 2009-01-19 18:53:01 -0500 (Mon, 19 Jan 2009) | 6 lines
AccImpl now implements accSelect(). Although the implementation doesn't do anything, its existence is enough to avoid having the Player report an IAccessible "member not found" error when calling accSelect() on a child item.
QE Notes: None
Doc Notes: None
Bugs: SDK-16654
Reviewer: Jason
r4630 | [email protected] | 2009-01-22 19:54:13 -0500 (Thu, 22 Jan 2009) | 6 lines
Removed code in AccordionHeaderAccImpl and TabBarAccImpl where the child IDs were being adjusted up or down by 100000 for some unknown reason. Deneb (on Flash Player) and Nataliya and Jon (on JAWS) don't think this should be done.
QE Notes: None
Doc Notes: None
Bugs: None
Reviewer: Deepa
r4692 | [email protected] | 2009-01-27 17:13:03 -0500 (Tue, 27 Jan 2009) | 9 lines
Fixed missing or misplaced 'break' statements in the eventHandler() methods of the mx.accessibility classes. These have probably been causing some unintented MSAA events to be dispatched.
Also, each accessible component now dispatches OBJ_NAMECHANGE when its toolTip or errorString property changes, because the MSAA name includes the tooltip or error tip.
QE Notes: None
Doc Notes: None
Bugs: None
Reviewer: Deepa
r4726 | [email protected] | 2009-01-28 21:47:59 -0500 (Wed, 28 Jan 2009) | 16 lines
Accessibility changes to the MSAA name of several components, as requested by Freedom Scientific. These changes make Flex controls behave more like standard Windows controls.
In Accordion and TabBar, the name is now just what is displayed, without " Tab" or " Tab, Active" appended.
In ComboBox, List, and Tree, the name of each item is now just what it displays, without, for example, "2 of 7" appended.
Removed an artificial limit of 100000 items in List and Menu.
A Slider with an MXML id no longer returns that id as its name; no other component does this and id's are certainly no intended to be spoken.
Removed the getName() method of ComboBase, which isn't used.
QE Notes: None
Doc Notes: None
Bugs: None
Reviewer: Jason
r4964 | [email protected] | 2009-02-16 12:41:50 -0500 (Mon, 16 Feb 2009) | 7 lines
Modify AccImpl.as to add @private to _protected final function $eventHandler(event:Event):void_ to work around an ASdoc bug. i will remove it when the bug gets fixed.
QE Notes: None
Doc Notes: None
Bugs: -
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-12390
http://bugs.adobe.com/jira/browse/SDK-16340
http://bugs.adobe.com/jira/browse/SDK-17755
http://bugs.adobe.com/jira/browse/SDK-16654
Modified Paths:
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/AccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/AccordionHeaderA ccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/AlertAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/ButtonAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/CheckBoxAccImpl. as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/ColorPickerAccIm pl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/ComboBaseAccImpl .as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/ComboBoxAccImpl. as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/DataGridAccImpl. as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/DateChooserAccIm pl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/DateFieldAccImpl .as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/LinkButtonAccImp l.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/ListAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/ListBaseAccImpl. as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/MenuAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/MenuBarAccImpl.a s
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/PanelAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/RadioButtonAccIm pl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/SliderAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/TabBarAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/TitleWindowAccIm pl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/TreeAccImpl.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/containers/Panel.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/core/UIComponent.as
Added Paths:
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/UIComponentAccPr ops.as
Removed Paths:
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/UIComponentAccIm pl.as
Property Changed:
flex/sdk/branches/3.x/

UCS F port trunking and reserved VSAN confusion

We have an existing UCS infrastructre where all the FI's FC ports are connected to the MDS9513 as one to one connection ( no port channel or trunking) and the FI is working as "end host mode" . We are planning to move some crtical production application to the UCS infrastrcture and becuse of that we would like to use the FC port chanelling and F-port trunking. While reading some documents I found that there are some restriction on UCS for VSAN numbering while using the FI for F-port trunking . As per the following doc http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/cli/config/guide/2.0/b_UCSM_CLI_Configuration_Guide_2_0_chapter_010101.html#concept_5223F7F368524A39AB1A47B9F8BFEC8A
it says donot configure VSAN ID range from 3840 to 4079 . The MDS 9513 is running NX-OS 4.2(3) . Our existing MDS SAN infrstructure already have 2 VSANs with ID number 4000 and 4001 ( Both of these VSANS are usied for some storage replication unrelated to UCS). In the UCS we alreay have 2 VSANS' ( 200 and 201) and are planning to create 2 more ( 300 and 301). My question is if I configure the FI's for F-port truncking/FC port channeling then what will happen to my existing VSAN 4000 and 4001 on the MDS9513 SAN
Thanks
RK

If you are asking how long it will take to enable f-port trunk and how disruptive it will be? It's not lengthy, but, it will cause the link to stop passing traffic and cause SCSI retrys. Your server will know it happened. If your fc multipathing is operating properly there will be no outage.If there are any configuration issues, the link may be down for an extended period, further compounding this disruption in traffic.
You initially asked about two features, f-port trunk and f-port channel. These are seperate features and require different configuration changes. It's best to add one feature at a time, not both in the same configuration change. Each change will be disruptive.
Do one fabric at a time. Ensure the f-port trunk is fully functional before doing the f-port channel, making sure it is functional before starting work on the second fabric.If your multipathing is operating as it should, there will be no outage. If there is any doubt schedule an outage window.
Dave

Switch Port Trunk allowed Vlan

Hi Guys
Request your help on my query :
I have a distribution switch and access switch and port channel between them.
Dist switch is the VTP server
lets assum I have 25 vlan
when I do show vlan brief on the access switch I can see all 25 vlans listed now
no when I configure switch port trunk allowed vlan (ex : permitting 10 vlans )on the link connecting to access switch at Dist switch
Dist switch po1 -- connecting to - po Access switch
Dist switch #
int po1
switch port trunk alllowed vlan x,x,x,x,x,x,x,x,x,
After permitting 10 vlan through trunk allowed vlan and then when I do show vlan brief on the access switch , I should see only the 10 vlan whcih I have permiited right ?
Thanks in advance

Hi,
John is absolutely correct - even if you do not permit a VLAN on a trunk, it can still provide communication among local ports on a switch that are all assigned to the same VLAN.
I have a feeling that your original question was focused on a different aspect, though: You probably expected that if you exclude some VLANs from trunks, these VLANs will not be propagated via VTP to surrounding switches. Sadly, this is not the case. The switchport trunk allowed vlan command only affects data traffic in individual VLANs but it has no impact on the operation of VTP protocol. The VTP still advertises all VLANs, regardless of which VLANs are allowed on a trunk. To put it plainly, in a VTP domain, all server/client switches will know about all VLANs. THere is no legal possibility of having a single VTP domain consisting of server/client switch and yet have the switches differ in their VLAN database contents. It's as easy as that: one VTP domain = one big common VLAN database.
Best regards,
Peter

Server Port - Trunk Mode

Hi,
One of the Server ports (pointing towards a UCS Chassis) on my fabric interconnect is currently showing as down as it is Trunk mode not Fabric Mode as per all the other server ports.
For some reason when I look under the LAN tab this one interface is showing under "internal LAN". I have tried disabling and/or deleting the interface from under "internal LAN" however every time I re-configure the port as a Server Port it is showing back under and the mode remains in Trunk.
Does anyone have some advice how I can get this port out of Trunk Mode and into Fabric Mode?
Many Thanks, Paul

Hi Cristian,
As requested please see outputs below:
UCS1-A(nxos)# sh run int e1/22
interface Ethernet1/22
description S: Server
no pinning server sticky
switchport mode trunk
switchport trunk native vlan xxx4
switchport trunk allowed vlan xxx4,xxx7
no shutdown
UCS1-A(nxos)# show int fex-fabric
     Fabric      Fabric       Fex                FEX
Fex Port      Port State    Uplink    Model         Serial
1    Eth1/1        Active     1         N20-C6508 xx
1    Eth1/2        Active     2         N20-C6508 xx
2    Eth1/3        Active     1         N20-C6508 xx
2    Eth1/4        Active     2         N20-C6508 xx
3    Eth1/5        Active     1         N20-C6508 xx
3    Eth1/6        Active     2         N20-C6508 xx
4    Eth1/7        Active     1         N20-C6508 xx
4    Eth1/8        Active     2         N20-C6508 xx
5    Eth1/9        Active     1         N20-C6508 xx
5   Eth1/10        Active     2         N20-C6508 xx
6   Eth1/11        Active     1         N20-C6508 xx
6   Eth1/12        Active     2         N20-C6508 xx
7   Eth1/13        Active     1         N20-C6508 xx
7   Eth1/14        Active     2         N20-C6508 xx
8   Eth1/15        Active     1         N20-C6508 xx
8   Eth1/16        Active     2         N20-C6508 xx
9   Eth1/17        Active     1         N20-C6508 xx
9   Eth1/18        Active     2         N20-C6508 xx
10   Eth1/19        Active     1         N20-C6508 xx
10   Eth1/20        Active     2         N20-C6508 xx
11   Eth1/21        Active     1         N20-C6508 xx
12   Eth1/23        Active     1         N20-C6508 xx
12   Eth1/24        Active     2         N20-C6508 xx
13   Eth1/25        Active     1         N20-C6508 xx
13   Eth1/26        Active     2         N20-C6508 xx
14   Eth1/27        Active     1         N20-C6508 xx
14   Eth1/28        Active     2         N20-C6508 xx
UCS1-A(nxos)# show fex 1 detail
FEX: 1 Description: FEX0001   state: Online
FEX version: 5.0(3)N2(2.11.3a) [Switch version: 5.0(3)N2(2.11.3a)]
FEX Interim version: 5.0(3)N2(2.11.3a)
Switch Interim version: 5.0(3)N2(2.11.3a)
Chassis Model: N20-C6508, Chassis Serial: XXX
Extender Model: UCS-IOM-2204XP, Extender Serial: XXX
Part No: 73-14488-03
Card Id: 184, Mac Addr: c0:67:af:84:a6:5a, Num Macs: 38
Module Sw Gen: 21 [Switch Sw Gen: 21]
post level: complete
pinning-mode: static    Max-links: 1
Fabric port for control traffic: Eth1/1
Fabric interface state:
    Po1025 - Interface Up. State: Active
    Eth1/1 - Interface Up. State: Active
    Eth1/2 - Interface Up. State: Active
Fex Port        State Fabric Port
         Eth1/1/1 Down      Po1025
         Eth1/1/2 Down      Po1025
         Eth1/1/3 Down        None
         Eth1/1/4 Down        None
         Eth1/1/5 Down        None
                Eth1/1/6 Down        None
         Eth1/1/7 Down        None
         Eth1/1/8 Down        None
         Eth1/1/9 Down      Po1025
        Eth1/1/10 Down      Po1025
        Eth1/1/11 Down        None
        Eth1/1/12 Down        None
        Eth1/1/13 Down        None
        Eth1/1/14 Down        None
        Eth1/1/15 Down        None
        Eth1/1/16 Down        None
        Eth1/1/17    Up      Po1025
Logs:
01/03/2014 11:23:14.295257: Module register received
01/03/2014 11:23:14.296133: Registration response sent
01/03/2014 11:23:14.580311: Module Online Sequence
01/03/2014 11:23:17.47105: Module Online
If possible would you be free to discuss this on a WebEx?
Kind Regards, Paul

MDS Code Level for UCS FC Port Channel/Trunking

What is the required MDS code level needed to support FC Port-Channeling/Trunking on a 9222i, 9148, or 9509/9513 w/ Gen2 line cards to UCS 1.4(3)?
I know the fport-channel-trunk feature is needed and was released in MDS 4.2 code but I have seen documents that this level of code wont support these features when used to connect to Cisco UCS.
Can someone confirm? Is NXOS 5.0(4) or higher required?

Doug,
I wrote the doc almost a year ago and it doesn't have the latest interop matrix support information. The current MDS NX-OS support is located in this doc: http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/intmatrx.html
While, I wish this was also duplicated in UCS docs, they are more or less taking the stance that 3rd party (Cisco MDS is this case) interop is maintained by the 3rd party. EMC, Netapp, or even Cisco.
It would be a nightmare updating UCS docs with 3rd party qualifications and support.
The short answer to your question is:
UCS 1.4(1), 1.4(2), 1.4(3) Is supported by MDS9000: 3.3(4a), 3.3(5), 4.2(1a), 4.2(1b), 4.2(3a), 4.2(5), 5.0(1a), 5.0(4), 5.0(4c)
NPV was introduced in MDS 3.3. f port-channel/trunk was introduced in MDS 4.2.
As Ram mentioned above, 4.2(5) is what I would recommend if I wanted to implement f port-channel and/or f port-trunk. I have also had recent experience with 4.2(5) and it worked great with a large UCS f port-channel/trunk implementation
The specific switch limitations I mentioned in my doc still exist. Only certain models of MDS will support f port-trunk. Almost all models will support f port-channel.
Dave

10 Gig Trunk Port

I'm setting up two 3750E switches on a bench prior to installing them - with a ten Gig port trunk port between them. I am running PVST and have pretty standard switch configuration. Show span indicates that all my vlans are forwarding between the ports but the packet rate keeps increasing as if its in a loop. Must be something obvious but can't find it - is there anything special you have to do to those ten GIG Modules to get them to work.
# interface ten gig 1/0/2
# sw trunk enc dot1q
# sw mode trunk
# sw nonegotiate

pardon me. I thought you are saying that packets are dropping but you are talking about STP loop.
As mentioned in other post, check if this link creating STP loop because of UDLD ? Maybe one of your cable not working or some other reason.
Though in LR you dont need an attenuator but check the power levels at both sides.Are they within receiver sensitivity? as you must be connecting back to back just with patch cables.

Video feeds on trunked port

Here's my current setup:
Cisco 4948 switch connected to a Linksys SRW2008 switch to a AmiNET125 and laptops.
Basically, here's what I'm trying to accomplish... on my Cisco switch I have 3 VLANs: 10, 20, and 100. 10 is my Management/Data VLAN, 20 runs my video, and 100 is my external network. Previously I did not have my port trunked from the Cisco to Linksys switches. The ports on both the Cisco and Linksys were setup as as a VLAN access port to VLAN 10. I was also able to view my video feeds that were running on VLAN 20 on my AmiNET125 with this configuration. The multicast IP was 224.1.1.100 and I had no problems accessing it on the AmiNET or on the laptops connected to the Linksys.
Now we are trunking the port from the Cisco switch to the Linksys, and through software we are trunking the laptops. My Cisco switch port is setup trunked and allowing all 3 VLANs. I setup the Linksys (or hope I did correctly) to trunk and allow all 3 VLANs. My workstations only access VLAN 10 and 100. I can now no longer bring up the multicast IP 224.1.1.100 on the AmiNET or the laptops. Like I stated before, the video feed is running on VLAN 20. Is there some sort of additional configurations needed for my Linksys that I'm missing so that I can view the video on my AmiNET? Do I need to create a multicast group in the Linksys in order to view it?
I'm not as worried about the laptops, but need the feeds on the AmiNET.
Any help is extremely appreciated!

Right now, there is no way to inject a live wired video feed to the pad. Maybe next year.
But if you are in a goofy 'try this' mode....
1. Face time. If the bowling alley has a viable wifi network, do a face time connect, put an I phone on a stick and see the screen on your pad.
Or if there is no wifi,
2 an app called tango does video conference over 3G. Not real good, and totally dependant on signal quality, and eats away at your data cap, but would work in a pinch.

F-port-channel-trunk disruptive or not?

Hi,
We have a N5K with NPIV configured and and MDS9148 we're gonna setup a port channel and have come to the conclusion that we need the F-port-channel-trunk feature enabled on the MDS side.
Question: Is enabling the F-port-channel-trunk feature on the MDS disruptive or non-disruptive?
--M

It's too late; I would say it is disruptive; however, the disruption is so short, that you didn't notice it. Similar without non F-port trunking channeling: using a link: the lost sessions are simply redistributed over the remaining links; new flogi is necessary.

N2K port speed set

My N2K connected to N5K, why some ports can set the port speed, and some cann't set the port speed?
int eth102/1/25     ！！！No speed command
(config-if)# ?
beacon          Disable/enable the beacon for an interface
cdp             Configure CDP interface parameters
channel-group   Configure port channel parameters
description     Enter description of maximum 80 characters
inherit         Inherit a port-profile
ip              Configure IP features
ipv6            Configure IPv6 features
lacp            Configure LACP parameters
link            Configure link
lldp            Configure Interface LLDP parameters
logging         Configure logging for interface
mvr-group       MVR interface config
mvr-type        MVR interface config
mvr-vlan        Interface MVR Config
no              Negate a command or set its defaults
rate-limit      Set packet per second rate limit
service-policy Configure service policy for an interface
service-policy Policy Map
shutdown        Enable/disable an interface
snmp            Modify SNMP interface parameters
spanning-tree   Spanning Tree Subsystem
switchport      Configure switchport parameters
untagged        Default to use for untagged packets on interface
end             Go to exec mode
exit            Exit from command interpreter
pop             Pop mode from stack or restore from name
push            Push current mode to stack or save it under name
where           Shows the cli context you are in
(config-if)# int eth102/1/48       ！！！ include speed command
(config-if)# ?
bandwidth              Set bandwidth informational parameter
beacon                 Disable/enable the beacon for an interface
cdp                    Configure CDP interface parameters
channel-group          Configure port channel parameters
default                Set a command to its defaults
delay                  Specify interface throughput delay
description            Enter description of maximum 80 characters
duplex                 Enter the port duplex mode
fex                    Configure FEX fabric
flowcontrol            Configure interface flowcontrol
hardware               FEX Card type
inherit                Inherit a port-profile
ip                     Configure IP features
ipv6                   Configure IPv6 features
lacp                   Configure LACP parameters
link                   Configure link
lldp                   Configure Interface LLDP parameters
load-interval          Specify interval for load calculation for an interface
logging                Configure logging for interface
mac                    MAC
mac-address            Configure interface mac address
mvr-group              MVR interface config
mvr-type               MVR interface config
mvr-vlan               Interface MVR Config
negotiate              Configure link negotiation parameters
no                     Negate a command or set its defaults
priority-flow-control Enable/Disable PFC
rate-limit             Set packet per second rate limit
service-policy         Configure service policy for an interface
service-policy         Policy Map
shutdown               Enable/disable an interface
snmp                   Modify SNMP interface parameters
spanning-tree          Spanning Tree Subsystem
speed                  Enter the port speed
storm-control          Configure Interface storm control
switchport             Configure switchport parameters
untagged               Default to use for untagged packets on interface
vpc                    Virtual Port Channel configuration
vtp                    Enable VTP on this interface
end                    Go to exec mode
exit                   Exit from command interpreter
pop                    Pop mode from stack or restore from name
push                   Push current mode to stack or save it under name
where                  Shows the cli context you are in
1,N5K version:
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_home.html
Copyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
BIOS:      version 3.6.0
loader:    version N/A
kickstart: version 6.0(2)N1(2)
system:    version 6.0(2)N1(2)
Power Sequencer Firmware:
             Module 1: version v5.0
Microcontroller Firmware:        version v1.0.0.2
SFP uC:    Module 1: v1.1.0.0
QSFP uC:   Module not detected
BIOS compile time:       05/09/2012
kickstart image file is: bootflash:///n5000-uk9-kickstart.6.0.2.N1.2.bin
kickstart compile time: 3/14/2013 1:00:00 [03/14/2013 16:53:55]
system image file is:    bootflash:///n5000-uk9.6.0.2.N1.2.bin
system compile time:     3/14/2013 1:00:00 [03/14/2013 19:28:50]
Hardware
cisco Nexus 5596 Chassis ("O2 48X10GE/Modular Supervisor")
Intel(R) Xeon(R) CPU         with 8262944 kB of memory.
2,N5K port
Eth102/1/1    --                 connected 101       full    1000    --
Eth102/1/2    --                 connected 101       full    1000    --
Eth102/1/3    --                 connected 101       full    1000    --
Eth102/1/4    --                 connected 101       full    1000    --
Eth102/1/5    --                 connected 101       full    1000    --
Eth102/1/6    --                 connected 101       full    1000    --
Eth102/1/7    --                 connected 101       full    1000    --
Eth102/1/8    --                 connected 101       full    1000    --
Eth102/1/9    --                 connected 101       full    1000    --
Eth102/1/10   --                 connected 101       full    1000    --
Eth102/1/11   --                 connected 101       full    1000    --
Eth102/1/12   --                 connected 101       full    1000    --
Eth102/1/13   --                 connected 101       full    1000    --
Eth102/1/14   --                 connected 101       full    1000    --
Eth102/1/15   --                 connected 104       full    1000    --
Eth102/1/16   --                 connected 104       full    1000    --
Eth102/1/17   --                 connected 104       full    1000    --
Eth102/1/18   --                 connected 104       full    1000    --
Eth102/1/19   --                 connected 104       full    1000    --
Eth102/1/20   --                 connected 104       full    1000    --
Eth102/1/21   --                 connected 104       full    1000    --
Eth102/1/22   --                 connected 104       full    1000    --
Eth102/1/23   --                 connected 104       full    1000    --
Eth102/1/24   --                 connected 104       full    1000    --
Eth102/1/25   --                 notconnec 102       auto    auto    --
Eth102/1/26   --                 notconnec 102       auto    auto    --
Eth102/1/27   --                 connected 106       full    1000    --
Eth102/1/28   --                 connected 106       full    1000    --
Eth102/1/29   --                 connected 104       full    1000    --
Eth102/1/30   --                 connected 104       full    1000    --
Eth102/1/31   --                 connected 104       full    1000    --
Eth102/1/32   --                 connected 104       full    1000    --
Eth102/1/33   --                 connected 104       full    1000    --
Eth102/1/34   --                 connected 104       full    1000    --
Eth102/1/35   --                 connected 104       full    1000    --
Eth102/1/36   --                 connected 104       full    1000    --
Eth102/1/37   --                 connected 104       full    1000    --
Eth102/1/38   --                 connected 104       full    1000    --
Eth102/1/39   --                 notconnec 1         auto    auto    --
Eth102/1/40   --                 notconnec 1         auto    auto    --
Eth102/1/41   --                 notconnec 1         auto    auto    --
Eth102/1/42   --                 notconnec 1         auto    auto    --
Eth102/1/43   --                 notconnec 1         auto    auto    --
Eth102/1/44   --                 notconnec 1         auto    auto    --
Eth102/1/45   --                 notconnec 1         auto    auto    --
Eth102/1/46   --                 notconnec 1         auto    auto    --
Eth102/1/47   --                 notconnec 1         auto    auto    --
Eth102/1/48   ZTC-Switch-48      connected 105       full    100     --
3,Fex
show fex 102 det
FEX: 102 Description: AO4-N2K-FEX102   state: Online
FEX version: 6.0(2)N1(2) [Switch version: 6.0(2)N1(2)]
FEX Interim version: 6.0(2)N1(2)
Switch Interim version: 6.0(2)N1(2)
Extender Serial: FOX1742G09B
Extender Model: N2K-C2248TP-E-1GE, Part No: 73-13671-02
Card Id: 149, Mac Addr: 64:e9:50:16:08: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/3
FCoE Admin: false
FCoE Oper: true
FCoE FEX AA Configured: false
Fabric interface state:
    Po102 - Interface Up. State: Active
    Eth1/1 - Interface Up. State: Active
    Eth1/2 - Interface Up. State: Active
    Eth1/3 - Interface Up. State: Active
    Eth1/4 - Interface Up. State: Active
Fex Port        State Fabric Port
       Eth102/1/1    Up       Po102
       Eth102/1/2    Up       Po102
       Eth102/1/3    Up       Po102
       Eth102/1/4    Up       Po102
       Eth102/1/5    Up       Po102
       Eth102/1/6    Up       Po102
       Eth102/1/7    Up       Po102
       Eth102/1/8    Up       Po102
       Eth102/1/9    Up       Po102
      Eth102/1/10    Up       Po102
      Eth102/1/11    Up       Po102
      Eth102/1/12    Up       Po102
      Eth102/1/13    Up       Po102
      Eth102/1/14    Up       Po102
      Eth102/1/15    Up       Po102
      Eth102/1/16    Up       Po102

show run int eth102/1/25 all
!Command: show running-config interface Ethernet102/1/25 all
!Time: Tue Apr 14 14:33:38 2009
version 6.0(2)N1(2)
interface Ethernet102/1/25
no description
lacp port-priority 32768
lacp rate normal
priority-flow-control mode auto
lldp transmit
lldp receive
no switchport block unicast
no switchport block multicast
no hardware multicast hw-hash
no hardware vethernet mac filtering per-vlan
cdp enable
switchport
switchport mode access
no switchport dot1q ethertype
no switchport priority extend
switchport access vlan 102
spanning-tree port-priority 128
spanning-tree cost auto
spanning-tree link-type auto
spanning-tree port type edge
spanning-tree bpduguard enable
no spanning-tree bpdufilter
speed auto
duplex auto
flowcontrol receive off
flowcontrol send on
no link debounce
no beacon
delay 1
snmp trap link-status
logging event port link-status default
logging event port trunk-status default
mdix auto
storm-control broadcast level 100.00
storm-control multicast level 100.00
storm-control unicast level 100.00
no shutdown lan
load-interval counter 1 30
load-interval counter 2 300
no load-interval counter 3
medium broadcast
channel-group 2025 mode active
no shutdown
show run int eth102/1/48 all
!Command: show running-config interface Ethernet102/1/48 all
!Time: Tue Apr 14 14:35:08 2009
version 6.0(2)N1(2)
interface Ethernet102/1/48
description ZTC-Switch-48
lacp port-priority 32768
lacp rate normal
priority-flow-control mode auto
lldp transmit
lldp receive
no switchport block unicast
no switchport block multicast
no hardware multicast hw-hash
no hardware vethernet mac filtering per-vlan
cdp enable
switchport
switchport mode access
no switchport dot1q ethertype
no switchport priority extend
switchport access vlan 105
spanning-tree port-priority 128
spanning-tree cost auto
spanning-tree link-type auto
spanning-tree port type edge
spanning-tree bpduguard enable
no spanning-tree bpdufilter
speed auto
duplex auto
flowcontrol receive off
flowcontrol send on
no link debounce
no beacon
delay 1
snmp trap link-status
logging event port link-status default
logging event port trunk-status default
mdix auto
storm-control broadcast level 100.00
storm-control multicast level 100.00
storm-control unicast level 100.00
no shutdown lan
load-interval counter 1 30
load-interval counter 2 300
no load-interval counter 3
medium broadcast
no shutdown
Ports are connected, there is no relationship with the speed option, such as port 102/1/1 is connected, but no speed option, port 102/1/47 is notconnected, there speed options.
show int eth102/1/1
Ethernet102/1/1 is up
Belongs to Po2001
Hardware: 100/1000 Ethernet, address: 64e9.5016.0802 (bia 64e9.5016.0802)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
full-duplex, 1000 Mb/s
Beacon is turned off
Input flow-control is off, output flow-control is on
Switchport monitor is off
EtherType is 0x8100
Last link flapped 1d02h
int eth102/1/1
(config-if)# ?
beacon          Disable/enable the beacon for an interface
cdp             Configure CDP interface parameters
channel-group   Configure port channel parameters
description     Enter description of maximum 80 characters
inherit         Inherit a port-profile
ip              Configure IP features
ipv6            Configure IPv6 features
lacp            Configure LACP parameters
link            Configure link
lldp            Configure Interface LLDP parameters
logging         Configure logging for interface
mvr-group       MVR interface config
mvr-type        MVR interface config
mvr-vlan        Interface MVR Config
no              Negate a command or set its defaults
rate-limit      Set packet per second rate limit
service-policy Configure service policy for an interface
service-policy Policy Map
shutdown        Enable/disable an interface
snmp            Modify SNMP interface parameters
spanning-tree   Spanning Tree Subsystem
switchport      Configure switchport parameters
untagged        Default to use for untagged packets on interface
end             Go to exec mode
exit            Exit from command interpreter
pop             Pop mode from stack or restore from name
push            Push current mode to stack or save it under name
where           Shows the cli context you are in
show int eth102/1/47
Ethernet102/1/47 is down (Link not connected)
Hardware: 100/1000 Ethernet, address: 64e9.5016.0830 (bia 64e9.5016.0830)
MTU 1500 bytes, BW 0 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
auto-duplex, auto-speed
Beacon is turned off
Input flow-control is off, output flow-control is on
Switchport monitor is off
EtherType is 0x8100
int eth102/1/47
(config-if)# ?
bandwidth              Set bandwidth informational parameter
beacon                 Disable/enable the beacon for an interface
cdp                    Configure CDP interface parameters
channel-group          Configure port channel parameters
default                Set a command to its defaults
delay                  Specify interface throughput delay
description            Enter description of maximum 80 characters
duplex                 Enter the port duplex mode
fex                    Configure FEX fabric
flowcontrol            Configure interface flowcontrol
hardware               FEX Card type
inherit                Inherit a port-profile
ip                     Configure IP features
ipv6                   Configure IPv6 features
lacp                   Configure LACP parameters
link                   Configure link
lldp                   Configure Interface LLDP parameters
load-interval          Specify interval for load calculation for an interface
logging                Configure logging for interface
mac                    MAC
mac-address            Configure interface mac address
mvr-group              MVR interface config
mvr-type               MVR interface config
mvr-vlan               Interface MVR Config
negotiate              Configure link negotiation parameters
no                     Negate a command or set its defaults
priority-flow-control Enable/Disable PFC
rate-limit             Set packet per second rate limit
service-policy         Configure service policy for an interface
service-policy         Policy Map
shutdown               Enable/disable an interface
snmp                   Modify SNMP interface parameters
spanning-tree          Spanning Tree Subsystem
speed                  Enter the port speed
storm-control          Configure Interface storm control
switchport             Configure switchport parameters
untagged               Default to use for untagged packets on interface
vpc                    Virtual Port Channel configuration
vtp                    Enable VTP on this interface
end                    Go to exec mode
exit                   Exit from command interpreter
pop                    Pop mode from stack or restore from name
push                   Push current mode to stack or save it under name
where                  Shows the cli context you are in

How can I encrypt my data links between switch uplink ports ? I'm unable to use "cts Manual" command in C3560X switch.suggest me

How can I encrypt my data uplinks between switch trunk ports ? I'm unable to use "cts Manual" command in C3560X switch.suggest me as I want to encrypt my switch-to-switch link with Cisco TrustSec.

Hi
Login to switch & go to interface..
There you can give tags.. (ISL & DONT1Q)
Command switch-port mode trunk
Switch-port trunk encapsulation ssl or dot1Q

Port-channel question on 9148

hey I have a question about port-channel.
we have a port-channel 10 which contains 4 interfaces as below.
my question is how the port-channel associated with the servers? I mean the output "sh flogi database" as below........
do we need to add port-channel as a zone member ? I think the answer is no since I don;t see the port-channel as a zone member....
=================================================================
tormds01# sh interface port-channel 10
port-channel 10 is up
    Hardware is Fibre Channel
    Port WWN is 24:0a:54:7f:ee:a0:d5:48
    Admin port mode is auto, trunk mode is on
    snmp link state traps are enabled
    Port mode is F
    Port vsan is 510
    Speed is 32 Gbps
    5 minutes input rate 124316072 bits/sec, 15539509 bytes/sec, 9919 frames/sec
    5 minutes output rate 2205921104 bits/sec, 275740138 bytes/sec, 141424 frames/sec
      43540499847 frames input, 70772376296224 bytes
        0 discards, 0 errors
        0 CRC, 0 unknown class
        0 too long, 0 too short
      237450525827 frames output, 442040501099476 bytes
        0 discards, 0 errors
      0 input OLS, 0 LRR, 0 NOS, 0 loop inits
      0 output OLS, 0 LRR, 0 NOS, 0 loop inits
    Member[1] : fc1/1
    Member[2] : fc1/5
    Member[3] : fc1/9
    Member[4] : fc1/13
    Interface last changed at Tue Apr 8 22:16:49 2014
tormds01# sh flogi database
INTERFACE        VSAN    FCID           PORT NAME               NODE NAME
fc1/3            510   0x860000 50:06:01:64:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                           [torvnx01_spa0]
fc1/7            510   0x860100 50:06:01:6c:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                           [torvnx01_spb0]
fc1/11           510   0x860200 50:06:01:60:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                           [torvnx01_spa2]
fc1/15           510   0x860300 50:06:01:68:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                           [torvnx01_spb2]
port-channel 10 510   0x860400 24:0a:54:7f:ee:92:3e:80 21:fe:54:7f:ee:92:3e:81
port-channel 10 510   0x860401 20:01:04:25:b5:3a:00:8f 20:01:00:25:b5:30:00:8f
                           [mcvhes0101hba0]
port-channel 10 510   0x860402 20:01:04:25:b5:3a:00:9f 20:01:00:25:b5:30:00:9f
                           [mcvhes0102hba0]
port-channel 10 510   0x860404 20:01:04:25:b5:3a:00:6f 20:01:00:25:b5:30:00:6f
                           [mcvhes0103hba0]
port-channel 10 510   0x860408 20:01:04:25:b5:3a:00:7f 20:01:00:25:b5:30:00:7f
                           [mcvhes0104hba0]
port-channel 10 510   0x86040f 20:01:04:25:b5:3a:00:4f 20:01:00:25:b5:30:00:4f
                           [mcvhes0105hba0]
port-channel 10 510   0x860410 20:01:04:25:b5:3a:00:5f 20:01:00:25:b5:30:00:5f
                           [mcvhes0106hba0]
port-channel 10 510   0x860417 20:01:04:25:b5:3a:00:2f 20:01:00:25:b5:30:00:2f
                           [mcvhes0107hba0]
port-channel 10 510   0x860418 20:01:04:25:b5:3a:00:0f 20:01:00:25:b5:30:00:0f
                           [mcvhes0109hba0]
port-channel 10 510   0x86041b 20:01:04:25:b5:3a:00:bf 20:01:00:25:b5:30:01:bf
                           [mcvhes0110hba0]
port-channel 10 510   0x86041d 20:01:04:25:b5:3a:00:1f 20:01:00:25:b5:30:00:1f
                           [mcvhes0111hba0]
port-channel 10 510   0x86041e 20:01:04:25:b5:3a:00:3f 20:01:00:25:b5:30:00:3f
                           [mcvhes0108hba0]
port-channel 10 510   0x86041f 20:01:04:25:b5:3a:00:ff 20:01:00:25:b5:30:01:ff
                           [mcvhes0112hba0]
port-channel 10 510   0x860423 20:01:04:25:b5:3a:00:df 20:01:00:25:b5:30:01:df
                           [mcvhes0113hba0]
port-channel 10 510   0x860425 20:01:04:25:b5:3a:00:ef 20:01:00:25:b5:30:01:ef
                           [mcvhes0114hba0]
port-channel 10 510   0x860426 20:01:04:25:b5:3a:00:cf 20:01:00:25:b5:30:01:cf
                           [mcvhes0115hba0]
port-channel 10 510   0x860427 20:01:04:25:b5:3a:00:8e 20:01:00:25:b5:30:01:8f
                           [MCDBWS0200hba0]
port-channel 10 510   0x860429 20:01:04:25:b5:3a:00:9e 20:01:00:25:b5:30:01:9f
                           [MCDBWS0201hba0]
port-channel 10 510   0x86042a 20:01:04:25:b5:3a:00:7e 20:01:00:25:b5:30:01:7f
                           [mcvhes0118hba0]
port-channel 10 510   0x86042b 20:01:04:25:b5:3a:00:af 20:01:00:25:b5:30:01:af
                           [mcvhes0116hba0]
port-channel 10 510   0x86042c 20:01:04:25:b5:3a:00:6e 20:01:00:25:b5:30:01:6f
                           [mcvhes0117hba0]
port-channel 10 510   0x86042d 20:01:04:25:b5:3a:00:4e 20:01:00:25:b5:30:01:4f
                           [mcvhes0119hba0]
port-channel 10 510   0x86042e 20:01:04:25:b5:3a:00:5e 20:01:00:25:b5:30:01:5f
                           [mcvhes0120hba0]
port-channel 10 510   0x860431 20:01:04:25:b5:3a:00:2e 20:01:00:25:b5:30:01:2f
                           [awotorprodsql01hba0]
port-channel 10 510   0x860432 20:01:04:25:b5:3a:00:3e 20:01:00:25:b5:30:01:3f
                           [awotorprodsql02hba0]
port-channel 10 510   0x860435 20:01:04:25:b5:3a:00:fe 20:01:00:25:b5:30:00:ef
                           [dbcactv01n3hba0]
port-channel 10 510   0x860436 20:01:04:25:b5:3a:00:de 20:01:00:25:b5:30:00:bf
                           [dbcactv01n4hba0]
port-channel 10 510   0x860439 20:01:04:25:b5:3a:00:ce 20:01:00:25:b5:30:00:8e
                           [mcvhes0123hba0]
port-channel 10 510   0x86043a 20:01:04:25:b5:3a:00:be 20:01:00:25:b5:30:00:af
                           [mcvhes0122hba0]
port-channel 10 510   0x86043c 20:01:04:25:b5:3a:00:ae 20:01:00:25:b5:30:00:9e
                           [mcvhes0124hba0]
port-channel 10 510   0x860443 20:01:04:25:b5:3a:00:8d 20:01:00:25:b5:30:00:6e
                           [mcvhes0125hba0]
port-channel 10 510   0x860445 20:01:04:25:b5:3a:00:ee 20:01:00:25:b5:30:00:cf
                           [mcvhes0121hba0]
port-channel 10 510   0x860446 20:01:04:25:b5:3a:00:9d 20:01:00:25:b5:30:00:7e
                           [mcvhes0126hba0]
port-channel 10 510   0x860447 20:01:04:25:b5:3a:00:6d 20:01:00:25:b5:30:00:4e
                           [mcvhes0127hba0]
port-channel 10 510   0x860449 20:01:04:25:b5:3a:00:7d 20:01:00:25:b5:30:00:5e
                           [mcvhes0128hba0]

I think what you do is F-Port trunking channeling !
port-channel as a zone member ? I assume you will do pwwn based zoning; in which case the answer is NO !

Can't get switch ports to work

Okay so I have a basic home lab, 2600 router x2 and 2900 XL switch x 2. I've connected each router together (they "see" each other in cdp), and each router to one switch. My problem is that the interfaces that the router connects to the switch won't accept an ip address, (it says unrecognized command) and the switch lights are off). A "show status" says only the trunk port (22 on each switch) are connected. I've checked the cabling, it works, and the cables are out of the box. What am I missing/forgetting?
Sorry if i newb :\ I'm Looking forward to going over static routes xD
Thanks,
Devlin
(I looked throught the documentation, maybe I missed it? I did a config reset on the switches. I bought these used, I hope they aren't broken :\)

No, they don't work, POST is fine (The switches boot normally), CABLING IS FINE, they are NOT admin down
Switch1#sho run
Building configuration...
Current configuration:
version 12.0
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
hostname Switch1
ip subnet-zero
!!!!! Omitted fa ports 1-24
interface VLAN1
no ip directed-broadcast
no ip route-cache
line con 0
transport input none
stopbits 1
line vty 5 15
end
Switch1#sho int status
Says every port except the ports trunking between the two switches is "not connected"
!!!!!HERES AN EXAMPLE OF ON OF THE DOWN SWITCHPORTS!!!!!
Switch1#sho int fa0/1
FastEthernet0/1 is down, line protocol is down
Hardware is Fast Ethernet, address is 00b0.647f.6681 (bia 00b0.647f.6681)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive not set Auto-duplex , Auto Speed , 100BaseTX/FX ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 1d23h, output hang never Last clearing of "show interface" counters never Queueing strategy: fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 1 packets input, 64 bytes Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast 0 input packets with dribble condition detected
2 packets output, 424 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out
Switch1# sh version
Cisco Internetwork Operating System Software
IOS (tm) C2900XL Software (C2900XL-C3H2S-M), Version 12.0(5)WC8, RELEASE SOFTWAR
E (fc1)
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Thu 19-Jun-03 13:09 by antonino
Image text-base: 0x00003000, data-base: 0x0034E2F4
ROM: Bootstrap program is C2900XL boot loader
Switch1 uptime is 1 day, 23 hours, 31 minutes
System returned to ROM by power-on
System image file is "flash:c2900xl-c3h2s-mz.120-5.WC8.bin"
cisco WS-C2924M-XL (PowerPC403GA) processor (revision 0x11) with 8192K/1024K byt
es of memory.
Processor board ID FAA0402G17B, with hardware revision 0x03
Last reset from power-on
Processor is running Enterprise Edition Software
Cluster command switch capable
Cluster member switch capable
24 FastEthernet/IEEE 802.3 interface(s)
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 00:B0:64:7F:66:80
Motherboard assembly number: 73-3425-10
Power supply part number: 34-0920-01
Motherboard serial number: FAA04019FEM
Power supply serial number: NONE
Model revision number: A0
Model number: WS-C2924M-XL-EN
System serial number: FAA0402G17B
Configuration register is 0xF
I'm really desperate here I have no idea what the problem is, and I cannot prepare for the exam without being able to assign ip addresses to the switch ports. If anyone can help me I would be EXTREMELY grateful.
Thanks
Devlin

Multiple network ports.... options?

Our Xserve has 4 ethernet ports, but our switch doesn't support the right kind of link aggregation to make use of a fat trunked 4Gb connection to our network.
Is there any way I can I make use of these multiple ports to enhance or optimise network traffic to our server, and if so, how?
I guess I could activate and connect all 4 ports to our 2x 24 port switches, but each connection would need a different IP address – presumably that would affect DNS and accessing services on the server?
Advice appreciated!!

Really. At least, that was the case last December when we moved premises, bought the Xserve and a couple of these switches..... I think it's to do with that 'manual' bit in the Netgear specs – I have a feeling a little more intelligence on the part of the switch is required.
I had read the specs and assumed it would work. Frustratingly, I tried everything (last year), and no good. I'm not at work just now, so I can't log in to the control panel, but from memory, all you can do is specify groups of ports to 'trunk' together – it works fine between the two switches (I've set up a two-port trunk between the switches), just not Xserve to Switch A (or B!).
I really wanted this to work, as it would have balanced our network load to the server nicely, so if anyone thinks I've missed something........?

SRW2024 (Port Binding)

Hi all,
I've recently purchase an 24-port 10/100/1000 Gigabit Switch SRW2024. Any body please help me how to configure port binding with mac-address in SRW2024.
Regards,

Please elaborate your inquiry, I believe that there's no exact port binding features from this switch. Please correct me if I am wrong about this. But if you want Port Mirroring or Port Trunking you can just visit www.linksysbycisco.com/kb for more information about it.

Port trunking on 9506

Similar Messages

Maybe you are looking for