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 !

Similar Messages

Nexus 1000v port-channels questions

Hi,
I’m running vCenter 4.1 and Nexus 1000v and about 30 ESX Hosts.
I’m using one system uplink port profile for all 30 ESX Host; On each of the ESX host I have 2 NICs going to a Catalyst 3750 switch stack (Switch A), and another 2 NICs going to another Catalyst 3750 switch stack (Switch B).
The Nexus is configured with the “sub-group CDP” command on the system uplink port profile like the following:
port-profile type ethernet uplink
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 1,800,802,900,988-991,996-997,999
switchport trunk native vlan 500
mtu 1500
channel-group auto mode on sub-group cdp
no shutdown
system vlan 988-989
description System-Uplink
state enabled
And the port channel on the Catalyst 3750 are configured like the following:
interface Port-channel11
description ESX-10(Virtual Machine)
switchport trunk encapsulation dot1q
switchport trunk native vlan 500
switchport trunk allowed vlan 800,802,900,988-991
switchport mode trunk
switchport nonegotiate
spanning-tree portfast trunk
end
interface GigabitEthernet1/0/18
description ESX-10(Virtual Machine)
switchport trunk encapsulation dot1q
switchport trunk native vlan 500
switchport trunk allowed vlan 800,802,900,988-991
switchport mode trunk
switchport nonegotiate
channel-group 11 mode on
spanning-tree portfast trunk
spanning-tree guard root
end
interface GigabitEthernet1/0/1
description ESX-10(Virtual Machine)
switchport trunk encapsulation dot1q
switchport trunk native vlan 500
switchport trunk allowed vlan 800,802,900,988-991
switchport mode trunk
switchport nonegotiate
channel-group 11 mode on
spanning-tree portfast trunk
spanning-tree guard root
end
Now Cisco is telling me that I should be using MAC pinning when doing a trunk to two different stacks , and that each interface on 3750 should not be configured in a port-channel like above, but should be configured as individual trunks.
First question: Is the above statement correct, are my uplinks configured wrong? Should they be configured individually in trunks instead of a port-channel?
Second questions: If I need to add the MAC pinning configuration on my system uplink port-profile can I create a new system uplink port profile with the MAC pinning configuration and then move one ESX host (with no VM on them) one at a time to that new system uplink port profile? This way, I could migrate one ESX host at a time without outages to my VMs. Or is there an easier way to move 30 ESX hosts to a new system uplink profile with the MAC Pinning configuration.
Thanks.

Hello,
From what I understood, you have the following setup:
     - Each ESX host has 4 NICS
     - 2 of them go to a 3750 stack and the other 2 go to a different 3750 stack
     - all 4 vmnics on the ESX host use the same Ethernet port-profile
          - this has 'channel-group auto mode on sub-group cdp'
     - The 2 interfaces on each 3750 stack are in a port-channel (just 'mode on')
If yes, then this sort of a setup is correct. The only problem with this is the dependance on CDP. With CDP loss, the port-channels would go down.
'mac-pinning' is the recommended option for this sort of a setup. You don't have to bundle the interfaces on the 3750 for this and these can be just regular trunk ports. If all your ports are on the same stack, then you can look at LACP. The CDP option would not be supported in the future releases. In fact, it is supposed to be removed from 4.2(1)SV1(2.1) but I still see the command available (ignore 4.2(1)SV1(4) next to it) - I'll follow up on this internally:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_2_1_1/interface/configuration/guide/b_Cisco_Nexus_1000V_Interface_Configuration_Guide_Release_4_2_1_SV_2_1_1_chapter_01.html
For migrating, the best option would be as you suggested. Create a new port-profile with mac-pinning and move one host at a time. You can migrate VMs off the host before you change the port-profile and can remove the upstream port-channel config as well.
Thanks,
Shankar

2960 Stack Port Channel Question

I have a 2960 stack with 2 WS-C2960S-48FPD-L distribution switches running c2960s-universalk9-mz.150-2.SE2.bin.
I then have three stand alone 2960S-48 access switches running the same code.
I will have two ten Gig uplinks in a port-channel back to a 6500. I have this config. however
I would like to have port-channel between each of the distribution switches in the stack and each of the stand alone access switches.
So as an example:
distribution switches: port 1/0/48 and 2/0/48 in port channel 1
access switches: 1/0/51 and 1/0/52 in channel-group 1 active
Am I right in thinking that because these port channels come off of two different switches in a 2960 stack that they need to be LACP and the ports on the access switches need to be in "channel-group X active". And does it need to be in active mode on both sides?
Thank You in advance

Yes, both sides must have identical channel mode.

Port-Channel Question

I need help on a cisco config and was wondering if anyone could help me. I currently have 4 Cisco 3750 which are stacked in our server room and now I have 4 more Cisco 3750 which are stacked also in a wiring closet. I just up-linked both 3750 stacks using 4 Fiber SFP SX modules. I wanted to config a port-channel on each stack however after 5 minutes or so the switch disables the port-channel interface as a config error on the port channel.
This is my current config
interface Port-channel1
description "Uplink to 3750 Stack 2"
switchport trunk encapsulation dot1q
switchport trunk native vlan 7
switchport mode trunk
interface GigabitEthernet1/0/25
switchport trunk encapsulation dot1q
switchport trunk native vlan 7
switchport mode trunk
channel-group 1 mode on
**Update** Just as FYI we have a VoIP network in which I'm trying to do is load balance/agrigate the network traffic a cross each switch in the stack (Cross Stack EtherChannel).
Thanks for the help.

Hello Oscar,
sorry for the delay.
But presidio's post gives you the answer.
You can check this configuration on the following link:
http://www.cisco.com/en/US/products/hw/switches/ps5023/products_configuration_guide_chapter09186a00801cdea1.html#1033981
Switch# configure terminal
Switch(config)# interface range gigabitethernet1/0/25 - 26
Switch(config-if-range)# switchport mode access
Switch(config-if-range)# switchport access vlan 7
Switch(config-if-range)# channel-group 1 mode on
Switch(config-if-range)# end
do the same for all physical interfaces configured in the channel-group
Lets us know if it helped.
Vlad

Fabric Interconnect To MDS 9148 FC Port Channel/Trunks

Is it possible to create both a Port Channel and Trunk on a Cisco MDS 9148? Yes correct?
Or can I only trunk between the 2 MDS switches and not the MDS to Fabric Interconnect?
These FC links would be connected to a 2248XP Fabric Interconnect carrying multiple VSANs from the MDS to the Fabric Interconnect.
Thanks

Hello,
Yes, you can have trunk links grouped into port channel ( F port-channel trunking ) between FI and MDS.
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_0101.html
Padma

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

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

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

SAN Switch 9148 UPG procedure when using Port Channel

Hi,
I am kind of new to the UPG procedure of Cisco Switch, and the customer i am working with is using Port Channel.
Do i have to shutdown the port channel before executing the switch UPG or if everything can stay up? Will i lose connection when the UPG will proceed ?
If anyone has some documentation that describe the process, it would be much appreciated.
Thank you
Christian

Hi,
I am kind of new to the UPG procedure of Cisco Switch, and the customer i am working with is using Port Channel.
Do i have to shutdown the port channel before executing the switch UPG or if everything can stay up? Will i lose connection when the UPG will proceed ?
If anyone has some documentation that describe the process, it would be much appreciated.
Thank you
Christian

N7K Port Channel Layer 3 VLAN Question

I have 2 N7K switches and would like to connect them via port channel and put the channel in VLAN 101. I have the following config, does it make sense? Thanks in advance!
interface eth 3/1
switchport
channel-group 101 mode active
interface eth 3/2
switchport
channel-group 101 mode active
interface port-channel 101
switchport
switchport mode access
switchport access vlan 10
spanning-tree network type edge
interface vlan 10
ip address 10.1.1.1/24

Could be something like this in the both sides (if the port numbers match):
conf t
feature lacp
feature interface-vlan
interface eth 3/1
switchport
channel-group 101 mode active
interface eth 3/2
switchport
channel-group 101 mode active
interface port-channel 101
switchport
switchport mode access
switchport access vlan 101
spanning-tree port type network
interface vlan 101
ip address 10.1.1.1/24
no shut
end
vlan 101
end
*(This ip address will be available in only one box, you can use a FHRP as well, to increase the level of reachability)

SGE2010 port-channel and trunking config question

I have port-channels configured and working for the native VLAN on multiple SGE2010s. I now want to add multiple VLANs and enable trunking for the port-channel. I am not clear on the appropriate way to enable trunking as it can be enabled on the port and on the port-channel. The ports and port-channel are currently in access mode. If anyone can provide the correct configuration, I would appreciate the guidance. I also need to get the port-channels and trunking working with 3Com 4500 & 4200s. If you know of any configuration issues, again any guidance would be appreciated

Hi Jacqueline,
Sorry Juans answer needs some correction, but I am grateful for Juans participation.
The SGE2010 does not support a CLI.
There is a unsupported CLI, that someone plastered somehwere on this community, but i must admit i still like to use the GUI.
The software on the SGE2XXX was recently updated so you can find that on the cisco.com website.
I have created a link below to a recording i just made, regarding Link aggregation on the SGE2XXXX, i thnk if you see the 11 minute recording a couple of times, maybe pause it, play with your switch, it will start to make sense.
you can't breat the switch by configuring it
click here to see a recording of me creating a Link aggregation between two switches
regards Dave

Port Channel Best Practice

Hi All,
I have a MDS9509 with port channels going to my Cisco blade switches on my HP Proliant blade enclosure.
I have NO ports left on my MDS9509, but DO have some remaining on the blade enclosure.
The question is, can i port channel from the blade enclosure to another edge switch (MDS9148)?
Is that a supported configuration/Best Practice and what are the ramifications if I do that?
So I'm going from Core, to edge and then to edge switch with port channel.
Thanks,
Matt

Hi Matthew,
Sorry for the misunderstanding, your to-be diagram cleared up a lot for me :-)
First off, yes, it will work. There's no reason it shouldn't and if you have the external ports free on your 9124e, you can hook up a new switch.
It's far from a conventional design, because blade switches are supposed to go in the Edge. It's not a best practice.
What I would recommend is that you move some of the storage from your edge to the 9148, and treat it as a collapsed core, sharing an edge switch (the blade switch). You can then ISL the 9148 and the 9509 together into a somewhat sensible topology.
So for one fabric this would be
(disk)---9148 --- 9509 -- (disks) (some moved to the left to free up space for ISLs)
9124e
Or you can contact your sales team and look to swap some Linecards with higher port density ones.
Lastly I would like to note that, however you link up the switches, most combinations available to you will 'work'. So as a temp solution you can go ahead with the (core - blade - edge) scenario. Just know that you'll be introducing bottlenecks and potential weak points into your network.

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

Disappointed: ASA 8.4 Redundant using Port-channels

So I finally got all our ASAs upgrade to version 8.4 and was all sorts of excited to configure port-channels to our 6500 + SUP7203B switches. I was severally disappointed to discover that I cannot configure two port-channels and have them be members of a redundant interface pair. It would seem like a logical topology.
Port-channel1 = Gig0/0 & Gig0/1
Port-channel2 = Gig0/2 & Gig0/3
Redundant1 = Port-channel1 & Port-channel2
Port-channel1 would connect to the primary 6500
Port-channel2 would connect to the backup 6500
What would it take to make this work? Am I going to have to wait for 8.5? Will we finally get BGP then too? (Had to get that in there)
http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/interface_start.html#wp1329357
EtherChannel Guidelines
•You can configure up to 48 EtherChannels.
•Each channel group can have eight active interfaces. Note that you can assign up to 16 interfaces to a channel group. While only eight interfaces can be active, the remaining interfaces can act as standby links in case of interface failure.
•All interfaces in the channel group must be the same type and speed. The first interface added to the channel group determines the correct type and speed.
•The device to which you connect the ASA 5500 EtherChannel must also support 802.3ad EtherChannels; for example, you can connect to the Catalyst 6500 switch.
•All ASA configuration refers to the logical EtherChannel interface instead of the member physical interfaces.
•You cannot use a redundant interface as part of an EtherChannel, nor can you use an EtherChannel as part of a redundant interface. You cannot use the same physical interfaces in a redundant interface and an EtherChannel interface. You can, however, configure both types on the ASA if they do not use the same physical interfaces.

Hello Yaplej,
Agree with you but unfortunetly this is not supported yet,
We migh need to wait some time before this desing can be accomplish,
Regards,
If you do not have any other question please mark the question as answered

MDS switch: DCNM: Is there a way to monitor the traffic on every port within a port channel using DCNM?

I am trying to monitor the load on an 8 port ISL between 2 MDS FC switches, on DCNM.
Since it is a plain trunk link, I am able to monitor the stats of every ISL port individually.
My question is, since port channel shows up as a single interface on DCNM, is there a way to monitor the per port utilization in that port channel?

Thanks for the update! If anyone else has the same question, the answer is that in order to extract the bus log information in the TDMS file, you should use the DIAdem Bus Log Converter tool. It is expected (though confusing) that the file looks mostly empty in the Data Portal until you use this tool to extract the information.
Also, this is a fantastic tutorial from a very bright engineer on how to correlate data from multiple sources, such as raw frame files, in DIAdem. Highly recommended reading. It also has some data on the bus log converter.
Jarrod S.
National Instruments

About n1000v with port channel

there is a n1000v connected to multiple upstream switches in the customer's production environment.
the following is from the Cisco Nexus 1000V Interface Configuration Guide, Release4.2(1)SV2(2.1).
You use vPC-HM mode to create a port channel when the switch is connected to multiple upstream switches
that are not clustered.
my question is,
can I use LACP with multiple upstream switches that are not clustered?
can I use LACP with multiple upstream switches that are stacked?
if I stack multiple upstream switches,does it mean clustered?
thanks.

Hi,
See some of the guidelines:
Guidelines and Limitations
Port channeling has the following guidelines and restrictions:
•All ports in the port channel must be in the same Cisco Nexus 1000V module; you cannot configure port channels across Cisco Nexus 1000V modules.
•Port channels can be formed with multiple upstream links only when they satisfy the compatibility requirements and under the following conditions:
–The uplinks from the host are going to the same upstream switch.
–The uplinks from the host going to multiple upstream switches are configured with vPC-HM.
•You can configure multiple port channels on a device.
•After you configure a port channel, the configuration that you apply to the port channel interface affects the port channel member ports. The configuration that you apply to the member ports affects only the member port where you apply the configuration.
•You must remove the port security information from a port before you can add that port to a port channel. Similarly, you cannot apply the port security configuration to a port that is a member of a channel group.
•You can configure ports that belong to a port channel group as PVLAN ports.
•Any configuration changes that you apply to the port channel is applied to every member interface of that port channel.
•Channel member ports cannot be a source or destination SPAN port.
That said LACP should work on switches that are not clustered and meet the conditions above.
A stack is treated as one unit which means that would be like you have just one big chassis.
Stacking does not the same as clustering it works different. so if you stack them that would be a stack not a cluster
http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4/interface/configuration/guide/n1000v_if_5portchannel.html#wp1270746
Hope this helps.

One or two LAG port-channel for 5508 v7.4 in HA setup?

Hi group
I have a question regarding LAG in HA setup; do you configure two port-channel, one for each controller or, only one port-channel for both?
I have a stack of 3 x 3750x, and 2 x 5508 with each two Gigabit uplink in use.
Active controler (5508-1) is connected to stack switch 1 and stack switch 2.
Standby controller (5508-2) is connected to stack switch 2 and stack switch 3.
I cannot find any documentation or guidelines for configurations of LAG in HA setup.
P.S. my question is not how to configure LAG or LACP, it only if you use one port-channel consist of 4 gigabit ports, or you have two with each 2 gigabit port to each controller.
TIA,
Peter

Thanks Stephen for your reply.
The switch doesn’t see which of the two port-channel that is on the active controller right?
If WLC01 is the active one in PO1 and standby is WLC02 in PO2, the MAC of the active controller (WLC01) will be sending on PO1.
When failover to standby, the MAC of WLC02 will be sending on PO2. As I see it, it is same IP address (management IP address of WLC01) but different MAC address – from WLC02.
So why could it not be one Port-channel, both controller will use one and same config when it become active?
TIA
Peter

Port-channel question on 9148

Similar Messages

Maybe you are looking for