Interconnection fabric 6248

Similar Questions

• Why we need spend version of catalogue of interconnection fabric

  Please let me know why and when do we need to upgrade the version of catalogue of interconnection fabric? What is the difference between the version or the version firmware update catalog.

  Fabric catalog version upgrade will be all risk on IFS, what will be the back plane of roll.

  Do you mean the ability catalog?

  If so, Cisco publishes upgrade version (/ revisions) of the components all the time. Catalogue of compatibility is a way to have these new subsystems without a new upgrade features Basic (NXOS, UCSM etc) systems.

  The catalog update is transparent and doesn't require any charging. It should not be necessary to restore an upgrade to the catalogue of ability, it's a nice little XML file that contains components known/support UCS.

• VNX 5300 file shared storage - connect to Cisco UCS 6200 interconnection fabric

  Hello

  I'm designing a calculation and Shared Storage solution to help

  • EMC VNX 5300 shared storage
    • Block
    • File - sharing two Data Mover with i/o 10GE ports
  • Cisco UCS Blade Server Platform
    • Interconnection of Cisco UCS 6248 fabric
    • Chassis Cisco UCS 5108

  I have a question about where the connection Data movers with i/o 10GE ports. I connected to the 6248 UCS Cisco fabric interconnections or connect them to the switch IP network?

  kind is ok.

• How to recover from a failure of a software on the interconnection fabric 6120

  Hi all

  Has been a software failure, while the upgrade of the fabric of interconnections. Does anyone know the process to recover from a failure of a software.

  Ive copied the boot images and system, the quick charger ive started the image of kickstart and then loaded the system image, but the fabric of interconnection always recharges to the command prompt "switch (boot).

  Thanks in advance

  Darren

  You will need the bin UCSM so file. You can download this EAC.

  "ucs-Manager - k9.1.3.1c.bin.

  / * Style definitions * / table. MsoNormalTable {mso-style-name : « Table Normal » ; mso-tstyle-rowband-taille : 0 ; mso-tstyle-colband-taille : 0 ; mso-style-noshow:yes ; mso-style-priorité : 99 ; mso-style-qformat:yes ; mso-style-parent : » « ;" mso-rembourrage-alt : 0 cm 5.4pt cm 0 5.4pt ; mso-para-margin : 0 cm ; mso-para-marge-bottom : .0001pt ; mso-pagination : widow-orphelin ; police-taille : 11.0pt ; famille de police : « Calibri », « sans-serif » ; mso-ascii-font-family : Calibri ; mso-ascii-theme-font : minor-latin ; mso-fareast-font-family : « Times New Roman » ; mso-fareast-theme-font : minor-fareast ; mso-hansi-font-family : Calibri ; mso-hansi-theme-font : minor-latin ; mso-bidi-font-family : « Times New Roman » ; mso-bidi-theme-font : minor-bidi ;} 1. Once booted to the 'switch (boot)' prompt, copy all the files in /bootflash

  / * Style definitions * / table. MsoNormalTable {mso-style-name : « Table Normal » ; mso-tstyle-rowband-taille : 0 ; mso-tstyle-colband-taille : 0 ; mso-style-noshow:yes ; mso-style-priorité : 99 ; mso-style-qformat:yes ; mso-style-parent : » « ;" mso-rembourrage-alt : 0 cm 5.4pt cm 0 5.4pt ; mso-para-margin : 0 cm ; mso-para-marge-bottom : .0001pt ; mso-pagination : widow-orphelin ; police-taille : 11.0pt ; famille de police : « Calibri », « sans-serif » ; mso-ascii-font-family : Calibri ; mso-ascii-theme-font : minor-latin ; mso-fareast-font-family : « Times New Roman » ; mso-fareast-theme-font : minor-fareast ; mso-hansi-font-family : Calibri ; mso-hansi-theme-font : minor-latin ; mso-bidi-font-family : « Times New Roman » ; mso-bidi-theme-font : minor-bidi ;}

  Switch (Boot) # conf t

  Switch (Boot) (config) # interface mgmt 0

  Switch (Boot)(Config-if) # address ip [IP address] [mask]

  Switch (Boot)(Config-if) # No tap

  output Switch (Boot)(Config-if) #.

  Switch (Boot) (config) # ip default-gateway [IP of the gateway]

  output Switch (Boot) (config) #.

  Switch (Boot) # copy scp:[email protected]/ * *//images/kickstart-image-version.bin bootflash:

  Switch (Boot) # copy scp:[email protected]/ * *//images/system-image-version.bin bootflash:

  Switch (Boot) # copy scp:[email protected]/ * *//images/ucs-manager-version.bin bootflash:

  2. rename file ucs-Manager-version the name that the system for image name "nuova-sim-mgmt - nsg.0.1.0.001.bin.

  Switch (Boot) # copy bootflash:ucs - Manager - verison.bin bootflash:nuova - sim-mgmt - nsg.0.1.0.001.bin

  3 reset

      switch(boot)# exit
  
  

  4 CTRL-L to enter the charger and start kickstart and system image at the same time, the space between

      loader> boot kickstart-image-version.bin system-image-version.bin
  
  

  5. When you get the system up, re - join your cluster (or restore your configuration), then make sure that you set the initialization as previusly mentioned variables.

  Let me know how you go with the foregoing.

  Robert

• Conversion of Standalone put in Cluster Mode of interconnection fabric UCS

  Dear all,

  I have an environment, where the configuration is done on the stand-alone version FI. Now the customer has purchased another FI.

  Ask that let me know the best practice to convert the stand-alone version FI in cluster mode.

  If someone can share the document that would be great...

  Looking forward to hear as soon as POSSIBLE.

  Kind regards

  Gopi G

  Very simple. Connect to your existing fabric of interconnection of the field running. Type 'local-mgmt connection '.  In this next command, the IP address is the virtual IP address of the cluster. You will use this from now on to use UCSM. Type 'cluster enable IPAddress '. Answer Yes to the prompt. Cable now your second interconnect with the ports of L1 and L2 as a normal cluster configuration.

  You will need to rework your service profiles since you now have a side B available.

  http://www.Cisco.com/c/en/us/TD/docs/unified_computing/UCS/SW/GUI/config...

• Fabric 6248 with MDS

  Hi all

  We are at the stage of inter-connecting simple IBM V3700 SAN box with double FI 6248 (redundant) via unique Cisco MDS 9000 SAN Switch with single UCS 5108 chasis.

  We have four blades B200 M3 in UCS 5108. The blades have no local hard disks. Our requirement is to install hyperV/Windows on IBM storage.

  I did the physical connections between IBM and MDS & MDS FI 6248 and FI 6248 dual Core 6509 VSS enabled.

  I don't have issues with part FI 6248 and LAN, I have doubts about FI 6248 with SAN kindly advise.

  6248 FI are default mode (Host End). I need to change FI on switch mode?
  I change ports Uplink FC, unified FI ports connected to the MDS are configured as storage CF?
  How vNIC, vSAN (vSAN how do I need), vHBA & Service profile works to each other? can any advise please?
  What steps do we need to set up in FI & MDS so that we can use SAN storage for hyperV/Windows installation?

  It's my first deployment of the UCS 5108, to apologize to ask fundamental questions.

  Kind regards

  1. what would be the impact of multiple VSANS vs default vSAN, I plan to use default vSan in the two FI-6248 & I can't find any problem with this, please advise.

  Please do not use default vsan (vsan nr or 1); best practices: create different VSAN fabric A and B; e.g. vsan 10A, vsan 20 b

  2 - pool WWPN, should I create two different WWPN pool 1 for FI-6248-A & others for FI-6248-B? I have only a UCS 5108 chasis, we cannot set an unique WWPN for the two FI-6248 Pool? What is the best practice? I can't find any problem with single WWPN pool. Please advise.

  Best practices: use pools of different pwwn to fabric A and B; useful for troubleshooting; in General: all pools must also encode a field id UCS (your starting with 1). just in case in the future, you have another! See attachment.

  3 - incase, if I will configure 1 WWPN pool would I face any problem in mapping the area in MDS? According to my understanding there will be no problem because the area is just the initiator (Server Blade) mapping & target (IBM Storage). Keep in mind, I only Cisco MDS SAN Switch NOT redundant. Please advise.

  Even with an SDM, you create a virtual double fabric with 10 and 20 VSANs. zoning is done by VSANs, zones and activation as well!

  what adapter policy 4 - Creating Service profile should I choose in the menu Dynamics vNIC? I want to install Windows on Hyper V environment, but I'm not hyper V option. It has linux, VMWare, VMWare passthrough, window, default & some HyperV more but not?

  You do not create dynamic vNIC! This only applies to the VM - FEX, resp. SR - IOV. Hyper-V means political adapter = window

  Good luck

  Walter.

• UNI-DIRECTIONAL press UCS 6248 interconnections of fabric?

  Hello

  If possible, I'd like to see a UNI-DIRECTIONAL between my 5548 neighbor was cheating Nexus and my 6248 interconnection fabric.

  UNI-DIRECTIONAL feature is supported by the 5548 s and easily activated.

  However, I can't find any information on how to activate on the UCS FI ports uplink ethernet. Is this possible?

  Thank you.

  Hello

  UNI-DIRECTIONAL UCS FINANCIAL support will be available in the next version major i.e UCSM 2.2

  UNI-DIRECTIONAL feature is currently not available on the FI.

  HTH

  Padma

• 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

• 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

• 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

• two or more frame with fabric in cluster interconnect

  Hi experts

  I just want to confirm the proper way to connect two or more UCS 5108 chassis with a pair of interconnect fabric 6120xp clustered.

  I though that they should connect like this: the tissue Extender first of all chassis must connect on interconnection fabric A and second all chassis tissue Expander connects to the fabric interconnect b. as on the diagram here: https://supportforums.cisco.com/docs/DOC-5949

  However, I saw someone did: 1 chassis connects as I went through although above but for the 2 chassis, fabric Extender 1 connect to the B interconnection fabric and fabric fabric Extender 2 interconnect a. -

  can someone tell me which is appropriate/best practices? no reason the second chassis enjambment?

  Thank you

  Ming

  Ming, you must fix this implementation.  It's like ghostbusters: do not exceed the streams!

  Always systematically cable chassis fex to interconnection fabric.  Most common installation:

  Interconnection of fabric (primary) is connected to the hand (looking for the rear of the chassis) left FEX

  Fabric interconnect (subordinate) B is hand-bound straight FEX.

  Why?  You will get errors (can't be bothered them up!) and if you move a Service profile to a chassis to another chassis that is wired differently, it will not work (CNAs wired to different financial institutions, where the living are active / inactive = bad).

  PS - to change this, if I were you, I would like to turn off the entire system - fabric interconnects, chassis, everything.  then re-cable.  then turn on the fabric of the interconnections and chassis and check configurations are ok.

• 6248 FI console Configuration, incorrect subnet mask

  After clear console FI 6248 configuration and Setup...

  I didn't enter the subnet mask... No idea what went wrong?

  Enter the configuration method. (console/gui)? Console
  Usage: grep [OPTION]... MODEL [FILE]...
  Try "grep - help ' for more information.
  Usage: grep [OPTION]... MODEL [FILE]...
  Try "grep - help ' for more information.

  Enter the installation mode; the program installation newly or restore from a backup. (configuration/restoration)? Setup

  You have chosen to install a new interconnection fabric. Continue? (y/n): y

  Apply the password? (y/n) [y]: n

  Enter the password "admin":
  Confirm the password "admin":

  Is - this fabric of doing interconnection in a group (select 'no' for autonomous)? (yes/no) [n] :

  Enter the name of the system: FI

  Address IP Mgmt0 physical switch: 192.168.0.1

  Physical switch Mgmt0 IPv4 subnet mask: 255.255.255.0
  Incorrect subnet mask. IPv4 Mgmt0 physical switch subnet mask: form invalid IPv4. Must be of the form 'X.X.X.X', where each
  Letter match a decimal number between 0 and 255.
  IPv4 Mgmt0 physical switch subnet mask:
  IPv4 Mgmt0 physical switch subnet mask: 255.0.0.0
  Incorrect subnet mask. IPv4 Mgmt0 physical switch subnet mask: form invalid IPv4. Must be of the form 'X.X.X.X', where each
  Letter match a decimal number between 0 and 255.
  Physical switch Mgmt0 IPv4 subnet mask: 255.255.255.0
  Incorrect subnet mask. IPv4 Mgmt0 physical switch subnet mask: form invalid IPv4. Must be of the form 'X.X.X.X', where each
  Letter match a decimal number between 0 and 255.
  IPv4 Mgmt0 physical switch subnet mask:
  IPv4 Mgmt0 physical switch subnet mask: 255.255.0.0
  Incorrect subnet mask. IPv4 Mgmt0 physical switch subnet mask: form invalid IPv4. Must be of the form 'X.X.X.X', where each
  Letter match a decimal number between 0 and 255.

  http://jeffsaidso.com/2013/01/when-disaster-strikes/

  might be useful as well; just for next time :-)

• FC Port-Channel does not

  Hello

  I need help, I'm setup CF port-channel between 9148 MDS and Cisco fabric Interconnect 6248 and the port-channel does not work. He said no operational members.

  For the MDS, see configuration below:

  NPIV #feature SW (config)

  SW (config) #feature fport-channel-trunk

  SW (config) #interface fc1/17-18

  SW(config-f) force Group-channel mode # 63

  SW(Config-if) F #switchport mode

  SW(Config-if) #switchport trunk-allowed vsan 1-2 (I have only vsan 1 and 2)

  SW (config) #no close

  SW (config) #interface 63 port channel

  SW(Config-if) F #switchport mode

  SW(config-f) #switchport trunk-allowed vsan 1-2

  SW (config) - #no close

  Note: the ports are assigned to vsan 2

  See the attached screenshots for interconnection fabric config

  On the fabric of interconnections switchport mode are defined E. What I have to change to F. If yes where can I change since the option is not there in the UCS Manager?

  have you added the VSANS on the UCSM as well?

  What Code are you runnig on the San Norhbound selector?

  You can be hitting

  https://Tools.Cisco.com/bugsearch/bug/ CSCty04686

• Chassis

  Hello guys

  Nicely, the 6248 UCS can be installed on the chassis of UCS 5108 Blade Server?, or should be off chassis

  Thank you

  The 6248 is an interconnection of autonomous UCS fabric, which connects to 5108 chassis (max. 20).

  Mini UCS configuration part of the interconnect fabric 6324 5108 chassis (see http://www.cisco.com/c/en/us/products/servers-unified-computing/ucs-mini/index.html)