6248 fabric interconnects FC interfaces and MDS ports license

Similar Questions

• Connection of fabric interconnect with the Cisco MDS switch

  I'm new to the unified fabric and try to understand it.

  There are clients who connect fabric connects directly to switch MDS without any Nexus 5 K between the two.  If the fabric of interconnections are able to provide connectivity to the LAN and SAN Islands then why you install Nexus 5 K between two switches to add an extra jump.

  Thank you

  Hello

  Most of the clients do the following:

  -connect FI upstream for example N5k with vPC for Ethernet (IP)

  -connect FI upstream for example MDS for the classic FC

  This implies that between the blade into the chassis and FI you run FCoE, integrating CF and Ethernet on the same means of transport; then, on the FI, FC and Ethernet is disintegrated.

  The other choice would be Multihop FCoE, linking FCoE also FI and N5k and make the disagregation it.

  However, if your storage subsystem is FC and FCoE, I wouldn't recommend Multihop FCoE (I see only a minority of clients to do).

  Walter.

• Noisy fan UCS 6248 fabric Interconnect noise RPM

  Hello

  Our pair of interconnection fabric installed 6248 produce a FAN noise.

  Is it possible to reduce their RPM? So can be more silent? The server room have good air conditioning.

  Some newspapers like below:

  Fabric - Has (nxos) # show the fan environment details

  Fan:
  ---------------------------------------------------
  Module fan air Speed (%)  Speed
  Direction
  ---------------------------------------------------
  1 1 front-to-Back 60 15428
  1 front-to-Back 2 60 11065
  1 front-to-Back 3 60 14835
  1 front-to-Back 4 60 10997
  2 1 front-to-Back 60-15000
  2 front-to-Back 2 60 11134
  2 3 front-to-Back 14835 60
  2 front-to-Back 4 60 11065

  Power supply:
  -----------------------------------
  Configured module air flow
  Direction speed (%)
  -----------------------------------
  Front-to-1 Back 60
  2 front-to-Back 60
  Fabric-A (nxos) #.

  Fabric-A (nxos) #.
  Fabric - A (nxos) # show environment

  Fan:
  ------------------------------------------------------
  Fan model Hw status
  ------------------------------------------------------
  Chassis-1 UCS-FAN-6248UP - ok
  Chassis-2 UCS-FAN-6248UP - ok
  PS - 1 UCS-PSU-6248UP-AC - ok
  PS - 2 UCS-PSU-6248UP-AC - ok

  Temperature
  -----------------------------------------------------------------
  MajorThresh MinorThres CurTemp sensor module status
  (Celsius)     (Celsius)    (Celsius)
  -----------------------------------------------------------------
  1 ok taken 67 58 35

  Power supply:
  Voltage: 12 Volts
  -----------------------------------------------------------
  PS model power input power state
  Type (Watts) (Amp)
  -----------------------------------------------------------
  UCS-PSU-6248UP-AC AC 780,00 65.00 1 ok
  2 UCS-PSU-6248UP-AC AC 780,00 65.00 ok

  Model power power power power status mod
  Asked asked allocated allocated
  (Watts)   (Amp)       (Watts)   (Amp)
  --- ----------------------  -------   ----------  --------- ----------  ----------
  UCS-FI-6248UP-SUP 492,00 41,00 41,00 492,00 1 power
  UCS-FI-DL2 24.00 3 2.00 24.00 2.00 under tension

  Summary of the use of power:
  --------------------
  Power supply redundancy mode: redundant
  Operational mode of power supply redundancy: redundant

  Total power 1560.00 W

  Reserved for directors of research 492,00 W of power
  Power currently used by Modules 24.00 W

  -------------
  Available power 1044.00 total W
  -------------
  Fabric-A (nxos) #.

  Felipe,

  Please open a TAC case to see if the problem is in the hardware level (a show of UCSM tech will be necessary) an engineering failure analysis may be needed to determine what is happening.

  -Kenny

• 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

• RDP Web Interface and connection broker proxies on the same port on 8 MR1

  Hello

  By reading the whats new document for version 8 MR1, I saw this:

  vWorkspace Secure Gateway role Consolidation

  All roles in Secure Gateway (RDP encryption, encryption of Internet access and Connection Broker encryption) can now be combined on the same server using the same IP address, port number and certificate server.

  .. which made me think that I might have RDP, web and broker any proxy if a gateway using port 443. This would be useful.

  However, in the secure gateway proxy configuration tool it has always down:

  NOTE: Either the Web Interface can be configured to the same address and the port that RDP proxy proxy or Broker for proxy connections.

  Am I misunderstand the information contained in the new document what, or if the text on the gateway configuration tool has not been updated? I share all of the 3 proxies on the same port?

  Scott.

  Scott, my apologies for the confusion. The text in the dialog box should be removed when the new feature has been added. It was an oversight that has not taken until after the product has been released. We intend to publish a fix that removes the misleading text when we release our next server important side fix.

  Marc

• Setting port channel between UCS - FI and MDS 9124 (Mode F)

  Dear team,

  We tried to create the channel of port between UCS FI and MDS 9124

  But the port channel do not take action in mode F on MDS 9124

  FI is in host FC end Mode

  We have allowed FC uplink on FI trunking

  We have activated NPIV on MDS

  We have activated the MDS trunk

  FI and MDS in default VSAN

  To check that we have changed the way FI FC channels mode and switch port became active, but in E mode

  When we enabled CF trunking of uplink on the port mode FI channels and FC Switching became active in mode TE

  but in both cases above, showflogi database shows WWPN of SAN alone does not have the any fi.

  How to achieve this?

  Have read that no need to change the mode switching mode of CF swicthing and keep FC Endhost way

  SO how to channel ports with mode F MDS and FI (Display Mode as NProxy)

  What is it has nothing to do with the MDS NX - OS version? (https://supportforums.cisco.com/thread/2179129)

  If yes how to put as license for ports came with the camera and we don't have any CAP/PAK or license file as she came

  with license

  Also, we saw 2 files available for download (m9100-s2ek9-kickstart - mz.5.2.8 .bin and m9100-s2ek9 - mz.5.2.8 .bin b b) to use

  Thanks and greetings

  Jose

  Hi Jo Bo.

  What version of the software if your MDS race?

  On your UCS do connect nxos and show ficelleStringString ficelleT inteface and find the mac address.

  It is possible that you could be hitting the bug below. If this is the case, you may need to update the firmware on your MDS.

  Add MAC YES '002a6a', '8c604f', '00defb' for 5 k/UCS-FI

  http://Tools.Cisco.com/support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId= CSCty04686

  Symptom:

  Link change cannot connect any other Nexus or other Cisco Switch in mode VAN with a port channel F.   Question can be viewed in older versions of 5.1

  5.1.3.N1.1a

  but not later

  5.1.3.N2.1c

  Release. Question is also found in

  5.2 (1) N1 (1)

  and

  6.0 (2) N1 (1)

  and later versions.

  Conditions:

  Nexus configured for the link SAN PortChannels or NPIV Nexus mode connected to the UCS via regular F port channel where UCS VAN VAN edge mode switch: YES switch manufactured FI or another Cisco UCS Port WWN: xx:xx:00:2 has: 6a: xx:xx:xx or xx:xx:8 c: 60:4f:xx:xx:xx

  Workaround solution:

  Turn-off on Nexus 5 k TF-port question link mode does not happen with standard F-PORT SAN to remove Portchannel config

  Other Description of the problem:

  To check question collect please see the flogi-event history internal errors whenever the port is attempted OLS, AMENDMENTS, PBA counters will increment. This can be determined via the following output, view port internal info to see all the internal-historic port of error events

• Fabric interconnecting Cisco high availability

  Hi Experts,

  I would like to know,

  (1) what does fabric adapter interconnection cluster (L1, L2) ports are using high availability?

  (2) can form us able to interconnect fabric and fabric interconnection interconnection 6100 6200 to a cluster? If ok means how they exchange of history since the two are completely different material. ?

  Thanks in advance,

  Jako Raj

  Hello

  (1) L1 and L2 ports are used for the purpose of managing only basically to synchronize data management, triggering a possible failover.

  (2) different hardware platforms are supported in the same cluster only in a process of upgrading equipment. Actually what really happens in this meanwhile is the copy of the configuration and the new FI is promoted as primary. Although he works as a group, he is an active-standby cluster, where a single FI acts as principal.

  Kind regards

• Reference Dell powerconnect 5524 cannot ping between coelio and trunk port

  Hello...

  We set up a new switch of 5524 I untagged on vlan 20 and access ports where vlan 20 I allowed. I created a computer on the access port on the same trunk port ip net... cant ping beween them. I'm no expert of switch, so I wonder what I missed. I did the same thing on a dell old 3524 and it works directly...

  Here's the port config I tried to do a ping beween is 6 and 10 ports

  (Another thing, how how to remove):

  switchport mode trunk
  switchport access vlan none)

  Any help would be greatly appreciated!

  interface vlan 1
  IP 88.131.90.252 255.255.255.240
  !
  interface vlan 5
  the name 'SCE CJA'
  !
  interface vlan 6
  the name "out of Tele2.
  !
  interface vlan 7
  name "Outside Telenor"
  !
  interface vlan 8
  name "TDC Multivrf"
  !
  interface vlan 20
  TDC-CISCO-LAN name
  !
  [0mMore: , quit: q or CTRL + Z, one line: interface vlan 21]
  the name "FW inside."
  !
  interface vlan 99
  name «FW sync»
  !
  gigabitethernet1/0/1 interface
  Description CPE1
  switchport access vlan 5
  !
  interface gigabitethernet1/0/2
  Description CPE2
  switchport access vlan 5
  !
  interface gigabitethernet1/0/3
  Df description
  spanning tree portfast
  switchport mode trunk
  switchport access vlan no
  !
  interface gigabitethernet1/0/4
  Description Oupps-cb2
  [0mMore: , quit: q or CTRL + Z, a single line: spanning tree portfast]
  switchport mode trunk
  switchport access vlan no
  !
  interface gigabitethernet1/0/5
  Upp-ccm1 description
  spanning tree portfast
  switchport access vlan 20
  !
  interface gigabitethernet1/0/6
  Oupps-ccm2 description
  spanning tree portfast
  switchport access vlan 20
  !
  interface gigabitethernet1/0/7
  Tdc-multivrf1 description
  switchport access vlan 8
  !
  interface gigabitethernet1/0/8
  TDC-multivrf2 description
  switchport access vlan 8
  !
  [0mMore: , quit: q or CTRL + Z, one line: interface gigabitethernet1/0/9]
  Description Oupps-cb-tq03
  spanning tree portfast
  switchport mode trunk
  !
  interface gigabitethernet1/0/10
  Description Oupps-cb-tq04
  spanning tree portfast
  switchport mode trunk
  !
  interface gigabitethernet1/0/11
  Tele2-outside description
  switchport access vlan 6
  !
  interface gigabitethernet1/0/12
  Tele2-outside description
  switchport access vlan 6
  !
  interface gigabitethernet1/0/13
  Telenor-outside description
  switchport access vlan 7
  !
  [0mMore: , quit: q or CTRL + Z, one line: interface gigabitethernet1/0/14]
  Telenor-outside description
  switchport access vlan 7
  !
  interface gigabitethernet1/0/15
  Description Word-Oupps-fw-tq01-inside
  switchport mode trunk
  !
  interface gigabitethernet1/0/16
  Description Word-Oupps-fw-tq02-inside
  switchport mode trunk
  !
  interface gigabitethernet1/0/17
  FW-sync description
  switchport access vlan 99
  !
  interface gigabitethernet1/0/18
  FW-sync description
  switchport access vlan 99
  !
  interface gigabitethernet1/0/19
  Description Word-Oupps-fw-tq01-outside
  [0mMore: , quit: q or CTRL + Z, a single line: switchport mode trunk]
  !
  interface gigabitethernet1/0/20
  Description Word-Oupps-fw-tq02-outside
  switchport mode trunk
  !
  interface gigabitethernet1/0/22
  FW-Sync description
  switchport access vlan 99
  !
  interface gigabitethernet1/0/23
  Description Word-Oupps-FW-tq01-outside
  192.168.11.1 IP address 255.255.255.0
  switchport mode trunk
  !
  interface gigabitethernet1/0/24
  Description Word-AIN-LAN-SW
  switchport access vlan 20
  !
  IP route 0.0.0.0 0.0.0.0 88.131.90.241

  [0mMore: , quit: q or CTRL + Z, a single line:]

  Information of VLAN

  The name of the VLAN Tag Ports Ports unmarked Type permission
  ---- ------------ ------------------ ------------------ --------- -------------
  1 1 article gi1/0/3-4, default required
  Article gi1/0/9-10
  item in gi1/0/15-16,
  item in gi1/0/19-21,
  item in gi1/0/23,
  item in gi1/0/25-48,
  TE1/0/1-2.
  GI2/0/1-48.
  TE2/0/1-2.
  IG3/0/1-48.
  TE3/0/1-2.
  IG4/0/1-48.
  TE4/0/1-2.
  IG5/0/1-48.
  TE5/0/1-2.
  GI6/0/1-48.
  TE6/0/1-2.
  gi7/0/1-48.
  TE7/0/1-2.
  gi8/0/1-48.
  TE8/0/1-2, m 1-32
  5 CPE TDC article gi1/0/3-4, item in gi1/0/1-2 permanent required
  [0mMore: , quit: q or CTRL + Z, one line: article gi1/0/9-10]
  item in gi1/0/15-16,
  item in gi1/0/19-20,
  item in gi1/0/23
  6 outside section gi1/0/3-4, item in gi1/0/11-12 permanent required
  Tele2 item in gi1/0/9-10,
  item in gi1/0/15-16,
  item in gi1/0/19-20,
  item in gi1/0/23
  7 outside article gi1/0/3-4, item in gi1/0/13-14 required permanent
  Telenor item in gi1/0/9-10,
  item in gi1/0/15-16,
  item in gi1/0/19-20,
  item in gi1/0/23
  8 TDC Multivrf item in gi1/0/3-4, item in gi1/0/7-8 permanent required
  Article gi1/0/9-10
  item in gi1/0/15-16,
  item in gi1/0/19-20,
  item in gi1/0/23
  TDC-CISCO-LA 20, article gi1/0/3-4, item in gi1/0/5-6, item in gi1/0/24 required permanent
  N item in gi1/0/9-10,
  item in gi1/0/15-16,
  [0mMore: , quit: q or CTRL + Z, one line: item in gi1/0/19-20,]
  item in gi1/0/23

  In safe mode the PVID is 1 VLAN by default. You can do this by entering the command #switchport trunk vlan native {number of vlan}. If Cisco is configured to accept and send the marked packets and has an IP address in the subnet of VLAN 20, it should be able to communicate with other devices in VLAN 20.

• How to distinguish the physical interface and logic (subinterface) interface to the Cisco router/Switch?

  Hi Expert,

  How to distinguish the physical interface and logic (subinterface) interface to the Cisco router/Switch? Can you please clarify a formal way for this so have?

  A physical interface is numbered with the same name of the interface when printing on the physical port. For example "GigabitEthernet 0/1" corresponds to port 1 of the 0 module (or the base unit).

  A logical interface can be a subinterface on a routed port and will have a point ("". "") preceding the number sous-interface (ex. GigabitEthernet 0/1.1). It can also be a loop or a virtual interface (on a router this could also include interfaces like the tunnel and virtual tunnel or VTI types). A switch may also have a VLAN logical interfaces (e.g. interface vlan 1) which are used as layer 3 virtual interfaces of type.

• Fabric interconnection B, management services do not respond

  Hello

  We have configured the option Call Home at UCSM and we get error below the option Call Home since last Saturday. We opened with Cisco to resolve this error, but according to the TAC TAC "error is a temporary error that connects the fabric can automatically recover."

  Here are the error messages that we get

  E mail-1:

  Object:

  Notification of the system-A system - diagnosis: GOLD-major-2011-12-27 17:54:09 GMT - 12:00 fabric Interconnect B, management services do not respond

  Message body:

  Name: System-A

  Time of the event: 2011-12-27 17:54:09 GMT - 00:00

  Description: fabric B event interconnection, management services do not respond

  Severity level: 6

  E mail-2:

  Object:

  Notification of the system-A system - diagnosis: GOLD-major-2011-12-27 17:54:09 GMT - 12:00 fabric Interconnect B, management services do not respond

  Message body:

  http://www.w3.org/2003/05/soap-envelope">

  http://www.Cisco.com/2004/01/AML-session' SOAP - env:mustUnderstand = 'true' SOAP - env:role ='http://www.w3.org/2003/05/soap-envelope/role/next' > '.

  http://Tools.Cisco.com/neddce/services/DDCEService>

  http://www.Cisco.com/appliance/URI>

  http://www.Cisco.com/appliance/URI>

  1058:SSI1442BFRC:4EFA0641

  http://www.Cisco.com/2004/01/AML-block">

  http://www.Cisco.com/2005/05/CALLHOME/diagnostic>

  2011-12-27 17:54:09 GMT - 00:00

  Interconnection UCS 6100 series fabric

  4.2 (1) N1 (1.43 q)

  1059:serial number: 4EFA0641

  0

  true

  true

  fake

  6

  http://www.Cisco.com/2005/05/CALLHOME"version ="1.0">

  2011-12-27 17:54:09 GMT - 00:00

  Fabric interconnection B, management services do not respond

  diagnosis

  GOLD-major

  Cisco

  Interconnection UCS 6100 series fabric

  [email protected] / * />

  [email protected] / * />

  ContractID

  [email protected]/ * */@SSI1442BFRC

  System-A

  Name

  [email protected] / * />

  + 00-0000000000

  Address of the Office

  http://www.Cisco.com/RME/4.0">

  N10-S6100

  0.0

  SerialNumber

  sam_content_file

  <>

  ACK = "no".

  cause = "management-services-refractory.

  changeSet =""

  Code = "F0452".

  created = "" 2011-12 - 27 T 23: 24:09.681 ""

  descr = 'interconnection fabric B, management services do not.

  DN = "sys/mgmt-entity-B/error-F0452".

  highestSeverity = "critical".

  ID = "2036245".

  lastTransition = "' 2011-12 - 27 T 23: 24:09.681" "

  LC =""

  happen = '1 '.

  origSeverity = "critical".

  prevSeverity = "critical".

  rule = "mgmt-entity-management-services-refractory.

  severity = "critical".

  status = 'created '.

  Tags =""

  [[type = 'management' / >]] >

  We want to understand what is the impact of this error and is there something we can do to avoid this error? I also want to know what that might be the cause get this error?

  Let me know if anything else is needed from my side

  See the downloaded file technology.

  Amit,

  I have reached out to the TAC engineer and will get back to you. In addition, please download tech to see the last UCSM to SR.

  "display the State of the extended cluster" would show the State of the cluster.

  For core dumps unannounced, you check in the Admin of UCSM tab

  Padma

• 6120 fabric Interconnect - 8 pre-installed licenses?

  The specifications for the 6120 reports interconnection sheet 8 pre-installed licenses are included: (http://www.cisco.com/en/US/prod/collateral/ps10265/ps10276/spec_sheet_c17-665945.pdf)

  «There are eight ports previously authorized (out of 20) included with the Cisco UCS 6120XP.» Sixteen ports previously authorized (over 40) are included in the 6140XP UCS. All additional ports require a license.

  We are currently using twelve ports on each of our four 6120 interconnets. If the wages of the licenses are deleted it shows only six ports with no grace period and the rest have expired.

  Ports in use are not sequential (as shown below), and it seems to have 1,2,3,4,17 and 18 as licenses pre-installed with two apparently missing.

  I recorded a request for TAC, but suck after several emails back.

  Can someone advise please?

  1 period of grace (license-ok) 0

  2 period of grace (license-ok) 0

  period of grace (license-ok) 3 0

  period of grace (license-ok) 4 0

  11 (license expired)

  12 (license expired)

  13 (license expired)

  14 (license expired)

  15 (license expired)

  16 (license expired)

  period of grace (license-ok) 17 0

  period of grace (license-ok) 18 0

  Hello

  You can check on the following doc for more information on port licenses:

  http://www.Cisco.com/en/us/docs/unified_computing/UCS/SW/GUI/config/Guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_01101.PDF

  David

• Fabric Interconnect inventory is not complete

  Hello

  I recently started to see this message in our environment of UCS.

  XXXXXX00 - A # shows fault
  Gravity last Transition time Code ID Description
  --------- -------- ------------------------ -------- -----------
  Major F0885 2015 - 11-01 T 20: 48:03.980 2489810 fabric Interconnect B inventory is not complete card-inventory,eth-pc-inventory,eth-port-inventory,fc-pc-inventory,fc-port-inventory,mgmt-port-inventory,remote-eth-port-inventory,switch-fru,switch-inventory

  I was wondering if anyone has any ideas on how to clear this error or where to start to look for clues as to its origin? Google search didn't donnГ anything fruitful. I see no problem in operations I can say as it may sound, everything works fine on the two FI. Is there maybe a way to force a further verification of the inventory or something like that?

  Thanks for any information.

  Kind regards

  Brandon

  Brandon,

  It looks like CSCuw36128.

  https://Tools.Cisco.com/bugsearch/bug/CSCuw36128/?reffering_site=dumpcr

• Partition to opt on fabric interconnect an includes file system errors

  After a downgrade from painful recovery (failed upgrade from 2.2.3d to 2.2.6d) everything works again, but I see

  Partition to opt on fabric interconnect an includes file system errors (see attachment)
  

  To remedy this unpleasant error advice are appreciated.

  Hello Walter.

  The bug that you run is;

  https://Tools.Cisco.com/bugsearch/bug/CSCus79160/?reffering_site=dumpcr

  I stumbled upon this problem in the past, the TAC will load the debugging plugin and just check a few blocks. Anika, a system launch is another fix but it is a longer process, if you open a TAC case don't forget to mention the bug above and they can try this work around first.

  I would like to know if you have any other questions or need help.

  Qiese Sa'di

• Interface of Cisco - Port heartbeat

  Our switch displays the following lighting terminal monitor (it's just a few of the incriminated ports)

  46w3d: % C4K_EBM-4-HOSTFLAPPING: 00:50:56:98:48:86 host in vlan 10 is flapping between port IG3/8 and Gi2/26

  46w3d: % C4K_EBM-4-HOSTFLAPPING: 00:50:56:AB:46:C4 host in vlan 10 is flapping between port Gi2/26 and Gi2/27

  46w3d: % C4K_EBM-4-HOSTFLAPPING: 00:50:56:98:59:0 B host in vlan 10 is flapping between port Gi2/23 and the port IG3/34

  46w3d: % C4K_EBM-4-HOSTFLAPPING: 00:50:56:B6:48:C3 host in vlan 10 is flapping between port IG3/9 and IG3/41

  46w3d: % C4K_EBM-4-HOSTFLAPPING: 00:50:56:B6:2 C host: 06 in vlan 10 is flapping between port IG3/24 and Gi2/34

  46w3d: % C4K_EBM-4-HOSTFLAPPING: 00:50:56:98:7 A: 22 host in vlan 10 is flapping between port IG3/7 and IG3/41

  Ports are configured as below and refer all to our VMware NIC host.

  interface GigabitEthernet3/7

  VSH02 - Nic description 9

  switchport trunk encapsulation dot1q

  switchport trunk allowed vlan 10-13 30, 50

  switchport mode trunk

  end

  Our vSwitch is configured with the Staus binding only for failover detection and LB use route based on the hash of the IP.

  What I understand, it is causing latency on our network and possibly questions PLEASE? Someone at - it a resolution to this?

  Thank you

  Brendan

  Hello

  First - beat addresses have nothing to do with the STP or latency.

  You can however activate "portfast" on the relevant port, for various reasons it is an improvement of the service.

  Heartbeat is normal, it's part of vmware, the sending of two network cards. You can advise the switch it is normal by creating an etherchannel. Note ESXi does not support LACP, so you can run ' mode channel-group 1.

• Problem of COM and Modem Ports

  Dear Sirs, although I have all the updated drivers, all Bluetooth ports, Modem and my PC series are kept with questions (marked with the "!" sign), so I can't use this devices.

  I went to the Toshiba web site and updated all the drivers.

  I deleted the deviced and clik "find the hardware changes" and the Ports are installed with questions.
  This medication was working a few weeks ago, so I guess that the problem is a few OS update?

  So I use W7 64 if one users pass trought this problem please help me.
  Thank you
  Nuno Rafael

  + The message was edited: changed topic +.

  Can you please tell us which model of laptop you have and that you use the original pre-installed OS that you got with your laptop?