I have the same problem, but it has something to do with QoS. When you disable "mls qos" on the switch, the port-channel will function normal again.
It doesn't help when you configure "mls qos trust dscp" on the port-channel!!!!!

Similar Messages

Port-channel Problem between Fabric Interconnect and N7K vPC

Dear all,
I have a problem with Port-channel Uplink between Fabric Interconnect with N7K using vPC
This is my network topology for UCS Deployment
In N7K I has configured vPC for red link and green link, at Fabric Interconnect A I has configured Port-Channel with member is Port 1 and Port 2, uplink is red link. At Fabric Interconnect B, I has configured Port-Channel with member is Port 1 and Port 2, uplink is green link.
The show interface port-channel on N7K is good, every port-channel is up and have all member. But At Fabric Interconnnect, when I see on UCS Manager, the status of Port-Channel on Fabic A and Fabric B is fault with Additional Info: No operational member. Although all link is link up and I has status of Port-Channel is enable on UCS Manager. When I see the Properties of Port 1, Port 2 on Port-channel, I see the membership status is : individual. This mean port-channel is not up and no membership in this configuration. I want to using port-channel for load balance and plus more bandwidth for uplink to 20Gig. I don't understand why ?
Please help me resolve this problem, I has send the capture screen of UCS Manager when I show status of Port-channel and Port-member in port-channel in attach items.
Anyone can help me to resolve this, thanks you very much. Please reference attach items for more detail about fault.
Thanks,
Trung.

Thanks Matthew very much,
I has resolved this problem. The reason of problem is miss match protocol of port-channel between N7K and Fabric Interconnect. The Fabric Interconnect always use LACP protocol, but N7K using Port-channel mode on, that why the port-channel failed. I has configured LACP for port-channel in N7K, it has resolved the problems.
Thanks,
Trung.

MDS9513 Add ISL to Port Channel problem.

Hi Experts,
I have a problem when add a new ISL to an existing Port Channel config.
The ISL port is up state and correctly configured like another ports in port channel.
Looks bellow the error:
MDS1300M6A# show port-channel summary
Interface                 Total Ports        Oper Ports        First Oper Port
port-channel 1                 4                 4                  fc12/48
port-channel 2                 2                 2                  fc6/47
MDS1300M6A# show port-channel database
port-channel 1
    Administrative channel mode is active
    Operational channel mode is active
    Last membership update failed: port not compatible [Resources Unavailable]
    First operational port is fc12/48
    4 ports in total, 4 ports up
    Ports:   fc12/48 [up] *
             fc10/48 [up]
             fc11/48 [up]
             fc9/48   [up]
Anyone seen this?
Tks
Wellington

That did the trick - specifically setting the port channel to rate-mode shared. Certainly solved the problem as far as getting all the deisred ports up in the channel, but where I still have a knowledge gap is the operational difference between dedicated and shared. Are there any Cisco docs (beyond the command reference guide to toggle the feature) that explains why you'd choose one versus the other, and what it means from a design perspective?
On a different note, while I'm no expert, here's some background to consider for others who may encounter the same issue (whether on UCS or a Nexus 5K). I (and our network team) come from an IOS background, so while the IOS "parts" of NX-OS are pretty familiar, the SAN "parts" of NX-OS are a little new. We're also more CLI oriented, and while not impossible to configure via CLI, in our environment, the GUI for UCS seems to be more popular across the board - and we're still learning that piece as well.
Our storage team is very familiar with SAN-OS, so they're very comfortable with the SAN "parts" of NX-OS. But, they're very used to configuring the MDS switches via the GUI, which is what got us off track a bit. In our scenario, creating a SAN port channel on the MDS via the GUI didn't give us the option for setting "switchport rate-mode shared" Not saying it's not there in the GUI, but we certainly couldn't find it.
Long story short, if the configuration of the SAN port channel on the MDS is in question, check it via the CLI and make any necessary changes there as a quick workaroud.

FI 6248 Nexus 5548 Port-channel problem

                   Hi all
I have a strange behavior between 2 FI and 2 nexus 5k configured as VPC , From a remote location and from my desktop I can ping odd ip and not even , from an other desktop in the same LAN the reverse, for both the tracert are good.
The only solution is to shutdown ports 1/1-2 on nexus A or FI A and in that case both desktops can ping both IP.
All seems OK, no log error , no error on interface , I give below some commands
What thing to know is that the nexus b has a L3 card , not the Nexus A , In fact I am waiting for a spare L3 daughter card.
On both NexusI have such configuration and status
interface port-channel201
description ucs-Fab-a
switchport mode trunk
switchport trunk native vlan 999
spanning-tree port type edge trunk
vpc 201
UCSM-PARIS-A(SSI153000ST)
                       Eth1/1        129    S I s     UCS-FI-6248UP Eth1/11
UCSM-PARIS-A(SSI153000ST)
                       Eth1/2        174    S I s     UCS-FI-6248UP Eth1/12
sh port-channel summary
201   Po201(SU)   Eth      LACP      Eth1/1(P)    Eth1/2(P)
sh mac address-table dynamic | i 1010
* 1010     0025.b5c9.481e    dynamic   0          F    F Po201
* 1010     0025.b5c9.481f    dynamic   10         F    F Po201
sh ip arp
10.203.136.21   00:01:05 0025.b5c9.481f Vlan1010
10.203.136.22   00:12:43 0025.b5c9.481e Vlan1010
On both FI A have such configuration and status
terface port-channel201
description U: Uplink
switchport mode trunk
pinning border
switchport trunk native vlan 999
switchport trunk allowed vlan 1,104,999,1010-1013,1020-1021,1500-1502,1510-151
2,1550-1552,1560-1561,1600-1602,1610-1619
speed 10000
sh port-channel summary
201   Po201(SU)   Eth      LACP      Eth1/9(P)    Eth1/10(P)   Eth1/11(P)
                                     Eth1/12(P)
sh mac address-table dynamic
* 1010     0025.b5c9.481e    dynamic   0          F    F Po201
* 1010     0025.b5c9.481f    dynamic   0          F    F Po201
sh cdp nei
E2RTR001(SSI1608085E) Eth1/9          120     S I s       N5K-C5548UP   Eth1/1
E2RTR001(SSI1608085E) Eth1/10         120     S I s       N5K-C5548UP   Eth1/2
E2RTR002(SSI16080F17) Eth1/11         151     R S I s     N5K-C5548UP   Eth1/1
E2RTR002(SSI16080F17) Eth1/12         136     R S I s     N5K-C5548UP   Eth1/2
Any ideas, A configuration I forgot on FI ?
Regards .

In fact in the probem I described the path is Esx -> FAB A - > N5K-A (for layer 2) -> N5K-B (for L3) -> routing to the LAN
And what you told me is that such configuration is not supported with VPC configuration , so I need to wait to receive the L3 card for the N5k-A. and check later if I have the same problem.
thanks

Alpha channel problem with Pixel Bender blendShaders

I'm using Pixel Blender to try and create a blend shader for a Flex 4.0 app.
It looks like this:
<languageVersion : 1.0;>
kernel PixelReverse
<   namespace : "com.abc.def.filters";
    vendor : "EdAlive";
    version : 1;
>
    input image4 foreground;
    input image4 background;
    output pixel4 dst;
    void
    evaluatePixel()
        pixel4 fgPixel = sampleNearest(foreground, outCoord());
        pixel4 bgPixel = sampleNearest(background, outCoord());
        if((bgPixel.r == 0.0) && (bgPixel.g == 0.0) && (bgPixel.b == 0.0) && (bgPixel.a == 0.0)){
            bgPixel.r = bgPixel.g = bgPixel.b = 1.0;
        dst.r = 1.0 - abs(fgPixel.r - bgPixel.r);
        dst.g = 1.0 - abs(fgPixel.g - bgPixel.g);
        dst.b = 1.0 - abs(fgPixel.b - bgPixel.b);
        dst.a = fgPixel.a;
It looks correct in the Pixel Bender preview window.
When I use it in a Flex project with proper 32 bit png images, the filter seems to work correctly, except it sets any partial alpha value on the images to fully opaque (like a 1 bit alpha channel).
Because the image preview looks correct in Pixel Bender, I'm assuming it's a problem with the bitmap data that Flex is passing to the blend shader filter.
I tried changing the filter to simply output a copy of the foreground firstly, and the background second, to test.
When returning a copy of the foreground, the imags weren't visible on stage, either because the pixels were transparent or because it was really returning the background pixels, camouflaging the images.
When returning a copy of the background, the images were just black rectangles.
The images are being place on stage programmatically inside an mx Module, and having their depth property set.
They also have draggable behaviour, where the current drag object is layered above all else during the drag.
I'm actually using a subclass of mx.controls.Image, but am simply setting the source property with preloaded bitmap data, so I'm am fairly sure the subclass is not a factor.
I hope this is enough information for someone to be able to provide some help.
Thanks

Please make sure you have installed the latest graphics drivers, from http://www.nvidia.com/Download/index.aspx?lang=en-us, for your graphics card.

Port Mapping Problem with AEX

I have a new Airport Extreme and a problem that did not exist with the Airport. I connect a Toshiba network camera to an Airport Express, set as a WDS remote, with the netcam connected to the wired ethernet port of the Express. I can see the netcam, which also functions as a web server, on the internal 10.x.x.x address, and have reserved a discrete 10.x.x.x address via the MAC/DHCP reservation function of the Extreme. Just like the older Airport which did this without a hiccup, I should be able to map a port (e.g. 1200) on the public IP to port 80 of the internal 10.x.x.x address, then access the netcam on the internal network from any browser (http://67.x.x.x:1200). My cable modem is just that: no router involved other than the Airport Extreme. I'm using the latest Extreme and Express firmware, and am either missing something with the new Leopard firewall, overlooking something else, or dealing with a product flaw. Any help is appreciated and Happy Holidays.

I have forwarded the port (have tried several different ports actually) in what I think it the correct way: using the Airport Utility, connected to the Airport Extreme, and, under advanced options, selected port mapping, entered the public TCP port of 1200, then the private 10.x.x.x IP address of the netcam (which I can access from the internal network with no problem), coupled with the private TCP port of 80. I then attempt to access the netcam from the Internet by entering http://my cable modem IP address:1200 (or another port to which I've attempted to map). This method worked for two years with the Airport, but, with the Extreme and Leopard (simultaneous transition), I'm stumped. After reading other about other port mapping problems, I reserved an IP address for the netcam based on its MAC with no positive results. I also set the firewall through the Security icon in System Preferences to allow all incoming connections. Thanks for taking the time to respond.

ThinkPad USB 3.0 dock network port has problems with our Cisco 6509 switch

We purchased a ThinkPad USB 3.0 dock for and X1 carbon and the main issue we are having is the network port does not seem to work with our Cisco 6509 switch. I tried updating the firmware on the dock but it still hasn't fixed the issue. I was wondering if anyone else had run into this problem with any other networks out there.

I'm seeing the same issue with a ThinkPad W520. When I connect my ethernet cable directly to the laptop, my internet speeds are on par with my service provider of 18 Mbps. When I move that cable to the dock, I will only see 1.5 Mbps. I have two displays attached to the dock and I'm running Windows 7. I've updated the dock firmware and have installed the latest system drivers. Is there anything else to try?

Poweredge (Win 2003) port teaming problem with Cat 6509s

Hi
One of our server guys has reported a problem with port teaming his Win 2003 Dell servers (running MS Exchange). He has set them up with an active port attached to 6509-A and a standby port attached to 6509-B. The servers have Broadcom NICs. At times the server is completely unavailable - unable to RDP or telnet and users have complained of poor performance.
Does anyone hae any experience - any info gratefully received.
Regards,
Paul

I'm not so sure CSCsj55739 is the issue. I have a few questions:
1) Can you post a text dump of the Broadcom team config (usually available from the teaming GUI).
2) Are both NICs connected to the same VLAN?
3) Is this same VLAN carried between 6509-A and 6509-B?
4) Have you tried removing the team and putting the team address on one physical NIC at a time, to see if simply one NIC or the other has a connection issue?

12K Port-channel Problem

Hello Everyong,
I'm trying to create a port-channel on my cisco 12K router and getting this error message.
Could some explain to me why this isn't working?
12Kconfig)#interface GigabitEthernet5/1/0
12K(config-if)#channel-group 2
Error: not supported on GigabitEthernet5/1/0.
Please and Thank you

Hi,
i found one previous issue with the same error and it was found that LinkBundling on Engine 5
interfaces is supported from 33S release only.
More info:-
http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/lnkbndl.html#wp1279546
So this feature is supported in 33S.
thanks,
Vinay

Port channel configuration with VMware

Hi everyone, I have dual 6120 interconnects, each of which have two uplink ports. I also have two Catalyst 4900M switches to uplink to. So I plan to configure both 802.1q and 802.3ad on each of the 6120 uplink pairs. My question relates to the physical cabling, bearing in mind ESX will be running on the blades.
Would you cable both the uplink ports on interconnect 1 to switch 1? Or would you cross-connect them to both switch 1 and switch 2?
As per this article I see ESX does not support splitting a port channel across two switches, but I am unsure how the presence of the 6120s affects this. Can anyone suggest the best way of doing the cabling based on the kit I have? Thanks.
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1001938&sliceId=1&docTypeID=DT_KB_1_1&dialogID=14912551&stateId=1%200%2014916516

Hey Simon, let's address this is two parts because there are two layers: server-bound (ESX-6120) and north-bound (6120-Cat4900).
At the ESX end, use the default srcPort in the vSwitch / port group with both 10GbE uplink ports (vmnic0 and vmnic1) set to active (not active/passive). There are no loops in this configuration. On the VNIC (in UCSM) you select trunk port and allow all the VLANs that your vSwitch port groups needs. If you don't use a VLAN for the Service Console/ESXi Management, then make sure you set Native to the correct VLAN in the VNIC to allow untagged traffic down the right path.
At the 6120 you can't explicitly configure a trunk for border ports, they are already set so and when you add VLANs they are added to every border port trunk configuration. You, of course, need to make sure the Cat4900 ports at the other end of the cable have the same trunkport VLAN configuration.
So in summary - set VLANs in vSwitch port groups, VNIC in UCSM and northbound switch.
Now when it comes to port channels, you can only configure two or more border ports as a port channel if they are cabled to the same Cat4900. If you had Nexus 5k/7k northbound then you could use vPC on them to allow "mesh" cabling (ie. one 6120 connects to both Nexus switches). But as you aren't using Nexus you will end up with a configuration as Jeremy explained:
ESX --> vSwitch0 --> srcPort load balancing --> 2 active uplinks --> many port groups
6120-a --> Cat4900-a
6120-b --> Cat4900-b
However, I would still recommend using a couple of border ports in a port channel on each fabric to each Cat4900 because, if you pull out a cable/lose a port, then when that port is re-enabled the existing live traffic is redistributed whereas without the port channel only new traffic will be spread across both links.
Cheers
Steve
Cisco UCS Team

Port-channel issue with FI-N7k using rate-mode share

Hi Dears,
I'm trying to using port-channel between Fabric Interconnect (FI) and N7K. in N7K use rate-mode share and LACP but the port-channel in N7K was suspended.
I was trying :
1. I using non dedicated port in Nexus 7010.
      - rate-mode share
      - channel-group 1 mode active
      - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was suspended
2. I using non dedicated port in Nexus 7010
     - rate-mode share
     - channel group 1 mode on
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was came up, but in Fabric interconnect was failed.
3. I using dedicated port in Nexus 7010
     - rate-mode share
     - channel group 1 mode active
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was suspended
4. I using dedicated port in Nexus 7010
     - rate-mode dedicated
     - channel group 1 mode active
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was came up and running well.
is any other way to configure port-channel in N7K with rate-mode share and LACP ?
or it's some of limitation in port-channel when using rate-mode share at N7K ?
nb: fabric interconnect only support LACP and cannot be configurable.
regards,
Berwin H

HI Mark,
1. Can you please check your ethernet card ...where this port channel connected..on the server.
    may be there are 2 different card.
2. from cisco websites:
Error Message
Explanation
This port has different port attributes than other ports within the port channel.
Recommended Action
Match the port attributes to that of the port channel.
Regards
Please rate if it helps.
Match the port attributes to that of the port channel.This port has different port attributes than other ports within the port channel.
EC-5-CANNOT_BUNDLE_LACP: [char] is not compatible with aggregators in
channel [dec] and cannot attach to them ([char])

Port Channel 5548 with 6509

My company just purchased a Nexus 5548. I've been fooling around with the configurations and just getting familiar with this equipment. I've already configured a port channel using 2 10gig ports on our 3850 and its working fine.
Now, I'm trying to configure a second port channel with our 6509 1gig ports. Ports comes up. But I cannot communicate between these 2 devices.
Show CDP Neigh shows the other devices. Show Etherchannel summary is blank
This is the config on the 6509
interface Port-channel22
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface GigabitEthernet9/7
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 22 mode on (I also tried using Active and desirable)
Config on 5548
Inteface Port-Channel 2
switchport
switchport mode trunk
speed 1000
interface ethernet1/32
switchport mode trunk
speed 1000
channel-group 22 mode on
I also have feature Lacp , interface vlan and vlan dot1q tag native enabled
Any ideas why I cannot communicate between these devices?

This is what is showing on the 5548
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-SPEED: Interface Ethernet1/32, operat
ional speed changed to 1 Gbps
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/32, op
erational duplex mode changed to Full
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Etherne
t1/32, operational Receive Flow Control state changed to off
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Etherne
t1/32, operational Transmit Flow Control state changed to off
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-SPEED: Interface port-channel2, opera
tional speed changed to 1 Gbps
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_DUPLEX: Interface port-channel2, o
perational duplex mode changed to Full
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface port-ch
annel2, operational Receive Flow Control state changed to off
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface port-ch
annel2, operational Transmit Flow Control state changed to off
2015 Mar 18 08:18:09 DC-5548-01 %ETH_PORT_CHANNEL-5-PORT_UP: port-channel2: Ethe
rnet1/32 is up
2015 Mar 18 08:18:09 DC-5548-01 %ETH_PORT_CHANNEL-5-FOP_CHANGED: port-channel2:
first operational port changed from none to Ethernet1/32
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_UP: Interface Ethernet1/32 is up i
n mode trunk
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_UP: Interface port-channel2 is up
in mode trunk
My 6509 does not show anything. Now when I do a show etherchannel summary on the 6509, the protocol is lacp.

Centre channel problem with DDTS-100

I have a set of Gigaworks s750 speakers connected to my PC, PS3 and Xbox 360 via the DDTS-100 decoder; up until yesterday this was all working fine. Having moved some of the gear around to accomodate my new desk, I plugged everything back in and found that the sound from the front centre channel is muffled and/or quieter than the other channels.
The speakers themselves don't seem to be the problem as the PC (which is connected via the switch box included with the decoder) sounds fine but the problem persists with both the PS3 and X360.
My first thought was that I'd pulled one of the cables loose while rearranging the furniture but I've re-plugged everything in several times since with no joy. I've also tried changing the spdif cables and switching the sockets around, as well as removing the switch box and plugging the speakers directly into the decoder but nothing made any difference.
Has anyone ever encountered anything like this before and/or could offer any suggestions?
Any advice would be much appreceated.

I finnaly found out my problem
The buzz came out from my coax cable from my DVD. My DVD player was probably inducing 60Hz on the coax output.
I switched to the optical output and no more buzz.
I'll need to buy a new toslink cable to plug my x-box on the optical input #2
Also I pluged my TV audio out in my st analog input, it also induced a 60 Hz on my DDTS-100. The decoder does not seem to filter out electric noises.
I'm pretty happy to have found out my problem but I'm very dispointed that the DDTS-100 does not filter any electric noises.
Mat

Sound channel problem with Personal Cinema FX500

WinXP SP1
MBoard : ASUS P4S533
(CMI8738 on-board Audio)
MSI Personal Cinema FX5200 MS-8918
The problem is that in the setup of WinDVD, the only audio source i can choose in WAVE,
but the sound output of the video tuner is on Line-In, of course.
Because of this problem, the remote affects the volume of WAVE, and has no effect on the Line-In channel. And, of course, when recording, the sound on the wave channel is recorded,
so, no sound !
Any one encountered this problem ? I installed the drivers on the original CD.

After nearly 3 months, I came up with the answer myself:
I installed a new driver (639) for the CMI8738 on-board sound and now the "Line In" option appears in the WinDVR setup.

Port forwarding problems with WRT610N v2 + WAG54GS v1.0

Background:
I have a WAG54GS v1.0 (Annex A) which I was using to handle my home network and my ADSL connection. I bought a WRT610N v2 (which I'll refer to as the router) with the intention that it would replace the networking duties of the WAG54GS (which I'll call the modem), which would be relegated to just handling the Internet connection. Both are running their latest firmware.
I've gotten this configuration to work, but with one problem: I've lost a lot of flexibility in regard to port forwarding. The problem is that the only way I've managed to get the Internet to work is by having the router on 192.168.0.1, and the modem on 192.168.1.1. If I try and have both on 192.168.0.x or 192.168.1.x then connecting to the Internet no longer works under any configuration of options I've tried.
What this means is that when I go to setup port forwarding in the modem, I can only forwards to clients on 192.168.1.x, but the router can only forward to 192.168.0.x. The only things I can get to work are situations where port range triggering can be applied, so only when a connection is made on the relevant port to an external IP, and then that external IP also communicates back on that port. As you may guess this doesn't nearly cover all cases.
Question:
Should it be be possible to have both router and modem on either 192.168.0.x or 192.168.1.x, which would allow port forwarding to work as expected. That should have in theory been possible with the modem's bridge mode except that it's then impossible to configure the PPPoA settings necessary to connect to my ISP.
Or am I going to have to rethink the network layout (i.e. buy a dedicated ADSL modem and fully retire my WAG54GS?)
Solved!
Go to Solution.

Actually in the end what I figured out was that as far as my WRT610N was concerned my WAG54GS was my ISP, and that was all it needed to know about the Internet connection. So I set it to connect to the WAG54GS with a static IP, stuck that IP into the WAG54GS's DMZ, and left the WRT610N to handle port forwarding as all devices that connect will do so through that. (Yes, I've disabled the wireless features of the WAG54GS)
I'm reasonably sure I tried the combination of settings you've suggested (including moving the WAG54GS off the Internet port of the WRT610N, which I would have wanted to avoid anyway as I have four permanently connected devices anyway) and found it still wouldn't work. And I wasn't trying to set both to 192.168.1.1 at any point, my self-obscured point was that changing only the last block of the IP address failed to work for accessing the Internet.

Port-channel problem with WiSM

Similar Messages

Maybe you are looking for