SRW2024 + uplink SRW2048 problem

Similar Questions

• The NIC failover does not work in LBT mode

  Dear community,
  

  
  

  We met a strange behavior in our network environment while testing our new Cisco 4500 switches x 10g. If you have a TCP Session (example JJ | netcat) data transfer between two virtual machines on different host esx failover does not work on the VM receiver if a physical connection fails.

  The test configuration is as follows:

  |    | - 4 - switch 1 vmnic - vmnic 4-|    |

  VM1 | ESX1 |                  | VSS |                    | ESX2 |-VM2

  |    | - 5 - switch 2 vmnic - vmnic 5-|    |

  More details:

  • The switches are configured as a cluster VSS. New version of the software
  • ESX1/2 are running the latest version 5.5
  • The two vmnic is active on a DV-switch in LBT mode
  • Exchanges are configured with "Port based on the physical NIC load."
  • VM1 and VM2 are invited linux, NICS are vmxnet3

  Steps to reproduce:

  1. Beginning listening mode on VM2 (netcat-l Pei 12345 |) JJ = / dev/null)
  2. Start the transfer on VM1 (dd if = / dev/zero bs = 1 M | netcat VM2 12345)
  3. Check which link is used (in my example vmnic5 on ESX2)
  4. Unplug the ESX2 vmnic5

  What you observe:

  • DD-traffic dies immediately
  • If you kill the dd on machines (it does not end by itself) and start all over again, it works immediately
  • If you ping VM1 VM2 or another system, it works
  • If you plugged vmnic5 again once the virtual machine is switched to new vmnic5-> if you didn't kill dd will continue

  Now to test the reverse:

  1. Beginning listening mode on VM2 (netcat-l Pei 12345 |) JJ = / dev/null)
  2. Start the transfer on VM1 (dd if = / dev/zero bs = 1 M | netcat VM2 12345)
  3. Check which link is used (in my example vmnic4 on ESX1)
  4. Disconnect vmnic1 ESX1

  What you observe:

  • Failover works like a charm
  • Failback works like a charm

  Conclusion:

  • Only the virtual machine at the front desk has a problem
  • Only an already established TCP session behaves badly, work of new sessions very well (as does ping, no losses)
  • If you use LACP place LBT on uplink the problem disappeared
  • Same problem if you connect two links to Switch1
  • Same problem if you use a physical box with linux and LACP as system
  • I did the same test with two c3750x (no cluster VSS) and has not encountered the problem

  Any ideas? It's really a good one.

  Thank you!

  Sascha

  
  

  
  

  Update:

  To make it clear, it doesn't have the transmission of UDP.

  Post edited by: sewert1

  I did some further testing and also involved cisco. There is no problem with the switches and network in general.

  Turns out he works with Windows clients, but it does not work with Linux. But it works with Linux with adapters e1000 and e1000e but not with vmxnet3.

  So I did some tests and learned that the vmxnet3 kernel module must be at least version 1.3. Version 1.1 (SLES 11 default) or 1.2 (default SLES12) does not work.

  (./vmware-install.pl--clobber-noyau-modules = vmxnet3)

• Problems with SRW2048 and SRW2016

  We have sold dozens or even hundreds of SRW2016 16 port switches and a few SRW2048 units.  For the money, they seem like a lot of things, but from a reliability point of view, we are at our wit's end.

  We're constantly visits on-site to see that all network problems because these units are dead.

  We do not yet have one of these units in service which has not been replaced at this stage.

  It now lasts for a year or two, but as an example;  Monday, we made 2 visits on-site and found 2 dead switch SRW2016 separate clients to the point where only the ports 7,8,15 and 16 would be illuminated.

  Yesterday, we had another problem of frantic network with a SRW2048 to another customer where we could only transfer data at about 78 KB/sec on any network port.  Even if I prefer to use the latest firmware on these switches, the upgrade has not helped at all.  We were forced to replace the switch entirely.  It was our 4' th 48-port switch Linksys that failed last year.

  We have new SRW2048 and SRW2016 units and use them to replace these bad units, but it becomes uncontrollable.

  It's not like these switches are in difficult environments, the controlled environment rooms are more and still die.

  Just curious if it's just our bad luck or if it is a subscription issue too with all the world?

  Well, what I've seen before - on the SRW2048 specifically - your problem, it's that they are managed switches that have a default IP address assigned to them (192.168.1.254 I think). The problem arises when you have a managed switch on the network because they have the two 192.168.1.254 - and if you understand ARP, then you can see the problem. The two switches are trying to find the mac address of 192.168.1.254 and they respond together, add to this PLEASE, and you have one heck of a loop and a mess. A quick opening of Wireshark and you will see that almost all traffic is consumed with ARP queries for these IP addresses.

  To take care of this, simply reassign the IP addresses of switches so that they are not the same, and you should be all set.

• Problem of VM - FEX - uplinks in VmWare are blocked by admin

  Hello

  Im trying to configure the VM - FEX on our infrastructure of UCS. I've updated all the components of the UCS for version 2.1(3a). Our VmWare is verision 5.1.0 and we have Enterprise Plus feature set.

  I have studied several documentations on the VM - FEX configuration, but without success...

  I have a UCS VCenter integration upward. My DVS created in the UCSM can be seen in the vCenter, also when I create the port profile, I see in the vcenter, and attach the virtual machine with it.

  The only problem is, the uplinks to the VM - FEX DVS are in the State, "blocked by the admin" in the vCenter, and there is no possibility of silent them.

  Can someone help me?

  Thank you and best regards Jiri.

  Initially, we used to have the same file for the N1k and VM - FEX but this sometimes changed back. A good way to check this would be to see what VEM modules are loaded. For example:

  N1k:

  ~ # esxcfg-module -l | grep vem vem-v160-l2device        3    36 vem-v160-n1kv            13   220 vem-v160-vssnet          4    6820 vem-v160-stun            1    128

  VM - FEX:

  ~ # esxcfg-module -l | grep vem vem-v152-vmfex-svs-mux   11   32 vem-v152-vmfex-pts       1    148

  (V160, v152) version number could vary, but the modules PTS, svs - mux etc will not change.

  Thank you

  Shankar

• Implementation of VLAN through SRW2048 & SG300-20

  Hi all

  I have a Linksys SRW2048 who has connected workstations. This switch is connected to a CSB SG300-20 by fiber that has connected on servers.

  The problem I have is that the internet is involved in the building is nearby the Linksys SRW2048 and I need to get to the SG300-20 without allowing access to the workstation so that it can pass through the filter of our content and then access all the workstations to it.

  I have 2 SRW2048 at SG300-20 fiber connection, is in use and connected servers to the rest of the network that the other is not in use.

  I guess I need to put two ports on say VLAN 10, one for internet connection ADSL modem and one for the miniGBIC use spare on switch SRW2048 fiber. Then the SG300-20 again once I'll need two ports on VLAN 10 on miniGBIC inflow and the port connect with unfiltered internet content filter

  The content filter will be connected then after it has been filtered to a port on the default VLAN for the rest of the workstations to access.

  In theory, the above is correct? If so could someone please go through what I have to do on the two switches to allow them to speak on the same VLAN.

  Thank you very much

  Matt

  Hi Matt,

  I just did this on my SRW208MP and my SRW208P-K9-NA

  Save your settings before you make these changes, so you can correct if you had problems.

  If I remember I did the following., but the VLANs have been already marked on the fiber ports.

  Step 1. I removed VLANs marked my fiber ports and just left ports uplink untagged VLAN by default.

  Step 2. My fiber uplink ports added to the Group of LAG 1 on both switches

  Step 3 now, I added selected each vlan and tag them individually on the Group 1 GAL

  Step 4.  Yes, and as you say, added the hypothetical ADSL modem to a switch as VLAN10 not signposted in port

  seems easy, good luck

  Best regards, Dave

• Convert software SRW2048 SG300

  In my view, the SRW series is the same as basic material the SG300 series.

  Is there a way to update the firmware on the series SRW using firmware SG300?

  The SG300 firmware is much more usable. Also I'd rather have consistency we have the old SRW2024/48 and new switches SG300.

  Bob

  David,

  You are on point.

  the 300 series is an Update replacement and hardware and software of the oldest product SRW.

  If you have purchased order p/n SRW2008 the updated version here in the United States that's so order p/n SRW2008-K9-NA

  We made the change in order p/n for reasons of consistency so that if you ordered SRW2008 in the past you order now SRW2008-K9-xx

  where xx is a code region for regulatory requirements and power.

  SRW2008 was a linksys product while replacing, SRW2008-K9-NA, is for example a Cisco product that now takes care of switching L3, IPv6 and a bearable CLI and a whole bunch of new features.

  SRW2008-K9-NA has a cisco SG300-10 p/n internal.

  Refer to the following table a wide for some clarity on this subject.

  This table has been copied and pasted from the public announcement of the EOL, to October 2010 referenced in the URL that follows;

  http://www.Cisco.com/en/us/prod/collateral/switches/ps5718/ps9967/end_of_life_notice_c51-632243.html

  Part number of end of sale product	Product description	Replacement product reference number	Replacement product description	More information
  SRW2008-EU	8-port 10/100/1000 Gigabit Switch with WebView	SRW2008-K9-G5	Managed switch of SG 300 - 10 10 Gigabit ports	-
  SRW2008MP-EU	8-port 10/100/1000 Gigabit Switch WebView Maximum Power PoE	SRW2008MP-K9-EU	Switch managed, SG 300-10MP, 10-port Gigabit PoE Max	-
  SRW2008P-EU	8-port 10/100/1000 Gigabit Switch with WebView and PoE	SRW2008P-K9-EU	Switch managed SG 300 - 10 p 10-port Gigabit PoE	-
  SRW2008P-UK	8-port 10/100/1000 Gigabit Switch with WebView and PoE	SRW2008P-K9-UK	Switch managed SG 300 - 10 p 10-port Gigabit PoE	-
  SRW2016-EU	16-port 10/100/1000 Gigabit Switch with WebView	SRW2016-K9-EU	Managed switch of SG 300 - 20 20-port Gigabit	-
  SRW2024-CN	24-port 10/100/1000 Gigabit Switch with WebView	SRW2024-K9-CN	Managed switch of SG 300 - 28 28-port Gigabit	-
  SRW2024P - TO THE	24-port 10/100/1000 Gigabit Switch with WebView and PoE	SRW2024P-K9 - TO THE	Managed switch of SG 300 - 28 p 28-port Gigabit PoE	-
  SRW2024P-EU	24-port 10/100/1000 Gigabit Switch with WebView and PoE	SRW2024P-K9-EU	Managed switch of SG 300 - 28 p 28-port Gigabit PoE	-
  SRW2048	48-Port 10/100/1000 Gigabit Switch with WebView	SRW2048-K9-NA	Managed switch of SG 300 - 52 52-port Gigabit	-
  SRW2048-AR	48-Port 10/100/1000 Gigabit Switch with WebView	SRW2048-K9-AR	Managed switch of SG 300 - 52 52-port Gigabit	-
  SRW2048 - TO THE	48-Port 10/100/1000 Gigabit with 4 Combo SFP switch WebView	SRW2048-K9 - TO THE	Managed switch of SG 300 - 52 52-port Gigabit	-
  SRW2048-CN	48-Port 10/100/1000 Gigabit Switch with WebView	SRW2048-K9-CN	Managed switch of SG 300 - 52 52-port Gigabit	-
  SRW2048-EU	48-Port 10/100/1000 Gigabit Switch with WebView	SRW2048-K9-EU

  Managed switch of SG 300 - 52 52-port Gigabit

  -

  SRW2048-UK

  48-Port 10/100/1000 Gigabit Switch with WebView

  SRW2048-K9-UK

  Managed switch of SG 300 - 52 52-port Gigabit

  -

  SRW208 - TO THE

  8-port 10/100 Ethernet Switch with WebView

  SRW208-K9 - TO THE

  SF 300 - 08 8-port 10/100 managed switch

  -

  SRW208-CN

  8-port 10/100 Ethernet Switch with WebView

  SRW208-K9-CN

  SF 300 - 08 8-port 10/100 managed switch

  -

  SRW208G-EU

  8-port 10/100 Ethernet Switch with WebView, expansion Slots

  SRW208G-K9-G5

  SF 302-08 8-port 10/100 Switch managed with Gigabit Uplinks

  -

  SRW208MP

  8-port 10/100 Ethernet Switch WebView, Maximum power PoE

  SRW208MP-K9-NA

  SF 302-08MP 8-port 10/100 PoE Managed Switch w/Gig Links Max

  -

  SRW208MP-EU

  8-port 10/100 Ethernet Switch WebView, Maximum power PoE

  SRW208MP-K9-EU

  SF 302-08MP 8-port 10/100 PoE Managed Switch w/Gig Links Max

  -

  SRW208MP-UK

  8-port 10/100 Ethernet Switch WebView, Maximum power PoE

  SRW208MP-K9-UK

  SF 302-08MP 8-port 10/100 PoE Managed Switch w/Gig Links Max

  -

  SRW208P

  8-port 10/100 with WebView and PoE

  SRW208P-K9-NA

  SF 302 - 08 p 8-port 10/100 PoE Managed Switch w/Gig rising

  SRW208P - TO THE

  8-port 10/100 Ethernet Switch with WebView and PoE

  SRW208P-K9 - TO THE

  SF 302 - 08 p 8-port 10/100 PoE Managed Switch w/Gig rising

  -

  SRW208P-EU

  8-port 10/100 Ethernet Switch with WebView and PoE

  SRW208P-K9-EU

  SF 302 - 08 p 8-port 10/100 PoE Managed Switch w/Gig rising

  -

  SRW208P-UK

  8-port 10/100 Ethernet Switch with WebView and PoE

  SRW208P-K9-UK

  SF 302 - 08 p 8-port 10/100 PoE Managed Switch w/Gig rising

  -

  SRW224G4-CN

  24-port 10/100 + 4 Gigabit ports, 2 Combo SFP switch WebView

  SRW224G4-K9-CN

  SF 300-24 24-port 10/100 Switch managed with Gigabit Uplinks

  -

  SRW248G4 - TO THE

  48-Port 10/100 + 4 switch with WebView Gigabit ports

  SRW248G4-K9 - TO THE

  SF 300-48 48-port 10/100 Switch managed with Gigabit Uplinks

  -

  SRW248G4-EU

  48-Port 10/100 + 4-port Gigabit, 2 Combo SFP switch WebView

  SRW248G4-K9-EU

  SF 300-48 48-port 10/100 Switch managed with Gigabit Uplinks

  -

  SRW248G4-UK

  48-Port 10/100 + 4-port Gigabit, 2 Combo SFP switch WebView

  SRW248G4-K9-UK

  SF 300-48 48-port 10/100 Switch managed with Gigabit Uplinks

  -

  SRW248G4P

  48-Port 10/100 + 4 switch with WebView and PoE Gigabit ports

  SRW248G4P-K9-NA

  SF 300 - 48P 48-port 10/100 PoE Managed Switch w/Gig rising

  -

  SRW248G4P - TO THE

  48-Port 10/100 + 4 switch with WebView and PoE Gigabit ports

  SRW248G4P-K9 - TO THE

  SF 300 - 48P 48-port 10/100 PoE Managed Switch w/Gig rising

  -

  SRW248G4P-UK

  48-Port 10/100 + 4 switch with WebView and PoE Gigabit ports

  SRW248G4P-K9-UK

  SF 300 - 48P 48-port 10/100 PoE Managed Switch w/Gig rising

  -

  Order details on the 300 series check the following URL;

  http://www.Cisco.com/Cisco/Web/solutions/Small_Business/products/routers_switches/300_series_switches/index.HTML-tab-models

  Bob, please do not order the older SKU, but order the replacement SKU with a K9 in the p/n. These parts new or updated numbers also come with a substantial warranty, in order to check the datasheet for this information on the warranty.

  Best regards, Dave

• Uplink speed

  I know there are some discussions about the speed, namely about HSUPA and a bunch of people ranting about AT & T. I think a lot of DOWNLOAD problems are AT & T issues.

  BUT.

  If you look at all speeds, I've still seen NOBODY counts more than 400 kbit/s while on the cell of uplink data. That most is - if you look at the users outside of the USA (and not on AT & T), this trend continues. Since WiFi seems higher uplink report, I think that the phone itself is not the limitation of what either and the problem may reside in the chip Qualcomm itself, or a driver.

  So... @Mark... Motorola... what's up with uplink speeds? 300 kb/s is not yet HSPA.

  If you think that it is a note in duplicate please... I'm strictly ask questions about RISING abismal connection speeds, I think it's different than the ranting about AT & T speeds.

  HSDPA - its maximum theoretical rate is 14.4 megabits per second (Mbps). AT & T has designed its network so that most users experience typical 700 Kbps downlink rates per second (Kbps) to 1.7 Mbps, with bursts of more than 1 Mbps.

  HSUPA - uplink typical rates 500 Kbps to 1.2 Mbps.

  HSPA - when using on a UMTS (3 G) network that isn't compatible HSDPA, top speed is 384 Kbps with typical speeds of 220 to 320 Kbps.

• EA2700 problems installing QoS

  I have an EA2700, which has updated the firmware fo the 1.0.14 (not Cisco Cloud Connect), and the window of QoS parameters on the installation of Web does not seem to work. All fields are gray'ed out, and the installation link does not work.  The original on the configuration firmware 1.0.12 box seemed to work.  I tried to revert to the previous firmware without success.  I would take some uplink of my VOIP (VONAGE) interface priority but had no chance. Is there a problem with the new firmware?

  davidmeyer wrote:

  I have an EA2700, which has updated the firmware fo the 1.0.14 (not Cisco Cloud Connect), and the window of QoS parameters on the installation of Web does not seem to work. All fields are gray'ed out, and the installation link does not work.  The original on the configuration firmware 1.0.12 box seemed to work.  I tried to revert to the previous firmware without success.  I would take some uplink of my VOIP (VONAGE) interface priority but had no chance. Is there a problem with the new firmware?

  Why not upgrade to Cisco Connect cloud, it is easy for you to give priority to the VOIP interface since it just drag and drop! But if you're not really comfortable with it. You can powercycle the router for 10-30 seconds if not work still then reset and reconfigure the router

• Problem with internet connection and E2000

  I was trying to figure out why my laptop and desktop computer were not in the same homegroup, pretty sure it just happened recently, after trying everything I could think of with Windows and nothing relevant on Google, so I decided to reset my router. Now my E2000 has a cable connecting a Verizon FIOS router (provided by coax) to it, which it probably complicates unnecessarily. I went and reset the router Verizon as well, and it does not solve my problem.

  My E2000 is aware that there is a connection, but it cannot establish a connection to the internet. I tried to use Cisco Connect (the software from the CD) to fix the problem and that has not worked. Go in the settings of the router and restart it don't work, either.

  When I bought this router, I plugged the cable coming from the Verizon router to the uplink port and using the router Wi - Fi better in my basement, but also direct connections significantly faster on my Playstation 3, Xbox360, office, etc. I did not have in place somehow out of what either the Cisco Connect software could have done, nothing fancy, just plugged and made sure everything was on my specific network for I can share via homegroup and have the media streaming.

  Anyone have any ideas on what might have happened, or what I could do to get an internet connection?

  The concept is similar to this article

  Editing cascading (connecting) a Linksys router to another Linksys router

  Since you already have a router in the form of the FIOS router, you will use the source of your DHCP, you must change the IP address of the router, then disable the DHCP.

  For example:

  FIOS 192.168.1.1

  E2000 192.168.1.2

  Then, you must connect the cable to one of the ports of the FIOS on one of the ports numbered on the e2000. Let me know if you encounter any problems. But the article is pretty much step by step.

• Problems of redundancy PowerConnect 7048

  Hello! I recently put in place a network I have a problem with and need someone to go through my configs of switch and tell me if they see something that I did wrong.

  The network consists of a blade M1000 - filled completely, Equalogic 2, 2 Powerconnect 7048 and 2 Powerconnect 8024-K (inside of the blade). I have everything configured for redundancy. Each server blade has 4 NIC, two are for iSCSI traffic and the other 2 are for virtual machine network traffic.

  The 7048 are stacked. I got everything is configured so I can unplug all four NICS (one at a time) on a blade, and the server will remain connected to storage and the network of the VM. I can also 2 (one at a time) 8024 switch K to shoot, and servers will be connected for the storage and the network of the VM. However, when I unplug one of the 7048 s 2, or the other, I lose the storage and access to the VM network, these all the network goes down. There is a lag configured for the uplink of the 7048 to a Meraki switch, so I should be able to always pass traffic, but the network is down.

  Attached are the configs of switch and a Visio diagram, I hope that someone can choose the problem immediately. My goal is a total redundancy, so when I lose a 7048 network remains standing. Thanks in advance!

  I try to activate the transfer non-stop on the battery and test it again. Nonstop forwarding allows transfer of battery units plan to continue to transmit packets while the control and management of aircraft restart after a power failure, hardware failure or the software on the management of battery unit.

  Console (config) #nsf

• UCS mac address problem

  Hi all

  simple question...

  You may know if it is a bug of mac address learning with version 1.4.1?

  I have go a blade with a mix of palo and other cards, some vnic are pinned to link rising with trunk allowed vlan 501 on both sides. On the blades of the UCS, i've got ESX and ESXi. Service console is labelled VLAN 501 (depending on the configuration of the trunk switch UCS and uplink). Some blade had obtained these interface pinned on the UCS6100 A and another on B (with failover). The fact is that if I ping from outside UCS UCS (ESX) inside no learning of mac is performed on all infrastructure.

  I don't know problem is the UCS because if I erase the mac table UCS, nothing works... and all the works if I start doing a ping of the UCS. I also tried to put the switch uplink static mac (ESX service console) but was not helpful.

  I hope this isn't a 1.4.1 bug...

  TNX and tnx for help

  Dan

  Y at - it you using uplink groups pine or have a network of layer 2 disjoint by chance?

  Questions like these are ususally PIN-related groups / Disjoint L2 using the wrong link DR port for traffic entering.  When the traffic is generated from within the outgoing UCS, the MAC table is updated on the upstream switch which allows traffic to flow, until he gets older.

  If one of them is the case I suggest take you a look at the videos of Brad name video #6:

  http://bradhedlund.com/2010/06/22/Cisco-UCS-networking-best-practices/

  Kind regards

  Robert

• Problems with config Small Business switch

  Hi, I know that if I read the documentation I will come for answers, but I'd really like some input from someone with more knowledge than me. I have a problem with Cisco SF300, one of the Small Business switches. I have a single interface on my router and I need to separate my internal networks, I thought that one way would be to use VLANs. On my two internal networks a network has D-Link unmanaged switches, the other has the Cisco SF300 I did as follows.

  On the Cisco Switch, all of the default ports for ports of junction. I changed FE1-FE24 and GE1-2 to access ports.

  Created two VLAN and placed FE1-FE24 in VLAN10 (also my management VLAN), GE3 is a trunk Port for unidentified VLAN20, VLAN 20 uplinks to my DiLink switches. This way my unmanaged switches traffic arrives on a trunk on VLAN20 untagged port.

  GE4 is a trunk port and I assigned to VLAN1 untagged, tag VLAN10 VLAN20 tag and. 10 of VLANS and VLAN 20 then to my router.

  The plan was to connect GE4 to my router, but I had two things happen that I can't explain.

  All first as soon as I connected my D-Link to GE3 LAN on VLAN20 came down, I couldn't ping servers from computers etc, all devices are connected to the D-links unmanaged. Secondly, the responsibilities of VLAN changed on GE3 GE4, VLAN 10 and 20 disappeared and only the VLAN by default was assigned, also under settings VLAN my state of interface VLAN for VLAN20 shows people with reduced mobility. One of my FE12 continues also to change VLAN access ports.

  Can anyone offer any suggestions as to what might have crushed the LAN and why change my VLAN. I wrote my config running at startup configuration incidentally.

  I added two screenshots.

  Seriously, I'd appreciate the help.

  Thank you

  Bob

  Hi Bob,

  Could you please post a topology? I can help with this, but it would be much easier that I could see your network.

  Thanks in advance,

  Garrett

• Problem with MAC pinning and new VLAN

  [Cross Announces nexus 1000V and forums of the UCS]

  Hi all, I have a working of the UCS 1.4 configuration (3i) and the Nexus 1000V 1.4 and according to best practices guide uses "channel-group auto on mac - pinning mode" on the uplink of Nexus. I have a problem when you add a new VLAN in this environment, and it is a reproducible problem in two different facilities.

  I pass by the VLAN usual creation process on the Nexus, the network upstream and within the UCS himself. I create new port vethernet profile and set it as an access port in the new VIRTUAL LAN. However when I join a VM (existing or new) to this new port vethernet profile in vCentre virtual machine cannot communicate with anything. However, if I disable MAC pinning with 'no channel-group auto on mac - pinning mode', the virtual machine will start instantly talk to the outside world and the new VIRTUAL LAN is running. Can I turn MAC pinning back once again, and everything continues to work.

  So the question is, is this normal or is there a problem? MAC the Θtiquetage has a brief interruption of the uplink, so is not a viable long-term customer solution when they want to add new VLAN. Is it possible to add new VLANS in this scenario without any unavailability of the network, but brief?

  Thank you

  Close the loop on this.  You tap the CSCto00715bug.

  Symptom: New MAC address is not learn on vem in the l2 table even though the mac address table is not overflow yet. vemcmd show l2-emergency-aging-stats | grep "Number of entries that could not be inserted:" will show extreme large number. Conditions: Nexus1000v VEM running on SV1.4 release. There are two CPU cores on the host. This issue may happen at race condition. Workaround: Reboot the ESX/ESXi host. 

  This problem is corrected in the 1. 4A release.

  Kind regards

  Robert

• Port-channel problem between fabric Interconnect and vPC N7K

  Hi all

  I have a problem with the Port Uplink channel between fabric interconnect with N7K using vPC

  It's my network for the UCS deployment topology

  

  N7K I configured vPC for red link and green linkto the fabric Interconnect A I has configured the Port-Channel with Member is Port 1 and Port 2, uplink is red link. Interconnection fabric B, I have configured the Port-Channel with Member's Port 1 and Port 2, uplink's green link.

  The interface port-channel on N7K show is good, each port-channel upwards and have all members. But the fabric Interconnnect, when I see in the UCS Manager, the status of the Port-Channel on Fabic A and fabric B dysfunction not more info: no operational Member. Although all the link is a link to the top and I've got the status of the Port Channel is enabled in the UCS Manager. When I see the properties Port 1, Port to Port-Channel 2, I see the number of members status is: individual. This means channel port is not up and no member in this configuration. I want to using the port-channel load balance and more bandwidth for the uplink of 20Gig. I don't understand why?

  Please help me solve this problem, I have to send the screenshot of UCS Manager when I show the status of the Port-Channel and Port-member in port-channel to reach items.

  Can someone help me solve this problem, thanks a lot. References, please include elements for more details on the fault.

  Thank you

  Trung.

  Hello Nguyen,

  Since the two N7k please collect:

  SH cdp nei

  SH run membership in. X int

  SH sum port-chan

  Thank you

  Matthew

• MAC Flaping after I Uplink AP chest

  I have configured my APs to transmit the SSID on VLAN 204, with managing IP's in 98 VLAN. Customer are authicating but now I get messages stating syslog I have MAC beat betteewn the uplink of the AP and the uplink switch. I have not now what is cauing this. Here is the error.

  1187 xxx.xx.131.122 xxx.xx.131.122 December 1, 2008 12:17 SW_MATM 4 MACFLAP_NOTIF Host 0013.cea3.750f in vlan 204 is flapping between port Fa0/17 and port Fa0/5

  How does one solve?

  MIke

  the command spanning tree portfast on trunk links creates a problem, remove, and check on