UCS fabric Interconnect after Failover (primary, subordinate)

Dear team,

After the changeover of FI - A has FI - B when we check show state his FI - B as primary and FI - A cluster as subordinates

The FI - A is now back online and HA shows as ready, but when we check to see the cluster status his shows still FI-B as primary and FI-A as subordinates

FI - A return himself will support as primary or do we need to give the force control of FI - B head to FI - A as primary again?

Thanks and greetings

Jose

Hi Jose,

FI has returned to the primary course again. The primary/sub-sub-coordinate is purely in a management perspective and nothing else (the two FIs before traffic etc.). Therefore, there is no problem to have FI B as primary or vice versa.

On a side note, if you want to trigger a failover manually, you can do the CLI from the context of local-mgmt of the primary focus:

UCS-B# connect local-mgmt b
UCS-B(local-mgmt)# cluster lead a




Thanks,


Shankar

Tags: Cisco DataCenter

Similar Questions

  • NSX design with cisco UCS/fabric interconnects and Nexus switches

    Hi Experts

    I am new to NSX design and deployment and working on a project. We deploy NSX for applications of level 4 (web, app, db, DC). I use logic, DLR, ESG and DFW switches. I next we intend to use roads static confusion..

    1. do we cover all the VLAN from the virtual to the physical environment? for example mgmt VLAN, level vlans(web,app,db), vxlan transport vlan or it should be only a VLAN specific?  which means would be I have set all the VLANS in environment NSX in my physical switching environment?

    2 vds? don't we create not only 1 vds initially during the deployment of vcenter or more? Should we take any special consideration while deploying to the deployment of the NSX?

    3 static routes - we configure static routes on the DLR and the GSS? Should I use the default routes upstream? on the physical router should we be routing all subnets from virtual environment to the GSS.

    4. where and who should create virtual machines? Via vCenter or before the deployment of the nsx NSX?

    5. we have a level of domain controller. Should it be part of 3 or separate applications with allow any any rule on DFW?

    Thank you

    Sam

    (1) the VLANs which exist for physical Machines span the logical switch VXLAN NSX in the following cases:

    • If the current deployment there are physical Machines in the same Vlan and subnet IP with Virtual Machines. If this common Port Vlan group is migrated to a switch logic VXLAN Backed port group and not possible to change the IP addresses of the virtual machines, and then a bridge DLR (Distributed logical router) works as the conversion between Vlan physical and virtual VXLAN
    • If Conversion of P-to-V of the physical Machines continue on this Vlan

    VLAN which cover only the virtual machines or virtual local networks which cover only physical Machines must not be delayed.

    (2) for the deployment of the NSX, there may be more than 1 dVS or only 1 vDS according to the design. There may be another type of traffic other VXLAN base of virtual machines such as backup, storage, VMotion and the overall design, management, best practices apply here as well.  A requirement of the NSX is a common VDS that spans the entire Cluster. For each Cluster, this "common VDS' may be different. Yet once this VDS maybe a separate VDS dedicated VTEP or VTEP features functionality can be added to the existing VDS. It may be best to separate the VTEP vDS.

    (3) for the DLR, a default gateway is usually sufficient. If static routes are used, the GSS must then drive by default upstream and the static routes with the next hop of the DLR downstream for the subnets in the subnets IP VM logical switch. On the physical router static route to the VM, but also DLR - ESG logical subnets Subnet switch is required. Management of static routes is easier if route summarization is possible, or if necessary, close to the IP subnets, so it may be a good idea to use the dynamic routing such as Ospf or BGP protocol. There are also features of IP address management in Vrealize and other IPAM solutions if Automation is necessary for large and dynamic environments.

    (4) NSX has no functionality in the creation of the VM, it only creates Services network such as switches, routers, Firewalls, Load Balancing. The creation of the part VM continiues the same way as before. A point to note is maybe the logic is created appear as VXLAN named port groups on the VDS. NSX Manager creates groups of ports on the VDS, the only difference is that the name includes VXLAN. The virtual machine is like before added to this group of VXLAN Backed Port settings, or added to the logical switch from NSX Manager interface that appears again as a Plugin for VCenter. VCENTER is so point to create virtual machines and add these VMs to the logic is.

    (5) level of domain controller can be a separate layer, or other third party, may be preferable to upgrade separated except 3 applications. Usually, it's the same design without NSX. dFW rules can help protect the domain controller with allowing only ports of the virtual machine or physical Machines being admitted. dFW rules can apply to VXLAN based logical switches NSX so that VLAN based DVS Port groups because it's the kernel module.

  • 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.

  • Use of external ports on the fabric of the UCS of interconnections

    Hello everyone

    We have a new UCS with 2 fabric interconnects and I want to uplink the ISCSI NICS to an external server not cisco.   What I read, it looks like using a port of the device is the way to go.  However I have noticed on the port configuration of the server, he does not see the VLAN already defined.  The server communicates only with a SAN upstream on our main switch;  If you define a VLAN separately on external does this mean if my server had to communicate with a blade of Cisco low flow to send traffic to the base and then back down even though he was on the same VLAN?  Just try to understand it.  Would it not be better to configure the mode switch?   I know that you will lose some functionality with mode switch.

    Thank you

    Jason,

    I don't ' know if you've already read, but here's the doc of a connectivity device port.

    http://www.Cisco.com/c/en/us/support/docs/servers-unified-computing/UCS-...

    Thank you

    Saurabh

  • 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

  • 6248 fabric interconnects FC interfaces and MDS ports license

    Hello

    I need help. I need to configure port-channel of CF between 2 x 9148 MDS and 2 x Cisco fabric interconnects. My main problem here is interfaces CF appear not on the fabric of interconnections (UCS Manager). I don't see ethernet ports. I have to turn on the unified ports or do I license for CF?

    I also connected the ds-sfp-fc8g-sw FPS but I get the error "operation status failed, reason: SFP Validation failed.

    Another thing, all 48 FC ports on switches DMS 9148 acquire the license. Aren't they supposed to come with 16 ports enabled by default?

    Any ideas?

    Hi Selby

    6248 FI unified ports, by default, all are Ethernet; so as a first step, you must configure the FC ports.

    You just need Ethernet port licenses, which are also universal.

    See, for example.

    https://supportforums.Cisco.com/message/3763853#3763853

    For SDM 9148 licenses take a look on

    http://www.Cisco.com/c/en/us/products/collateral/storage-networking/MDS-9148-multilayer-fabric-switch/data_sheet_c78-571411.html

    There are packages with

    Cisco MDS 9148 48 - Port Multilayer Fabric Switch with 16, 32 or 48 active ports of 8 Gbps

    Good luck

  • 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 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

  • Add a temporary file after failover

    Hello
    We have a configuration of Guard (10g 2 node windows 2003 RAC ASM, r2 server) data. After failover to the backup system and run some queries, I discovered the following messages in the alert log:
    ATTENTION: The following temporary tablespaces do not contain any file.
    This condition can occur when a backup controlfile
    been restored. It may be necessary to add files to these
    storage spaces. This can be done using the SQL statement:

    ALTER TABLESPACE < nom_tablespace > ADD TEMPFILE

    Then I issue the following command
    alter tablespace temp_ts add tempfile '+ DATA' size 100M;

    I have a few questions about this behavior:
    (1) in my old primary school, it has the temporary file. Why there is no temporary file after failover?
    (2) passage to the require also add tempfile? As we use ASM, we add a temporary file for each passage?

    Thank you very much in advance.

    (1) in my old primary school, it has the temporary file. Why there is no temporary file after failover?

    TempFiles must always be added whenever the controlfile is recreated. That's why they are temporary, they can be dropped and re-created at any time. Consistency of databases has no dependencies on temp. When the configuration of data protection has been initially implemented, he need to instantiating a standby and had to be done through backup. I clone data bases often and I often forget to add the tempfiles after creating a clone. This happened during the day before was originally instantiated, any tempfiles have been added. You switched to the night before and realized that there is no tempfiles.

    (2) passage to the require also add tempfile? As we use ASM, we add a temporary file for each passage?

    Passage to the should not require to add tempfiles, because the controlfiles are not re-created. Check the data dictionary by selecting the name from v$ tempfile, if she comes back with no line, the database currently has no temporary file.

  • I installed VMware ESXi on my Cisco's UCS server but after that I don't get from CIMC.

    I installed VMware ESXi on my Cisco's UCS server but after that I don't get from CIMC. also, I am unable to ping the address IP of CIMC. Any help?

    I think that MMIC does nothing with your ESXi installation... it is OoB management for servers of the UCS.

    Check your config MMIC inside the BIOS again.

    BR,

    Dragan

  • DataGuard passage failed: impossible to failover, primary database is always "PRIM".

    Hi all


    DataGuard digital switchover is Getting failed with the below error:

    DGMGRL > passage to the "dry";

    Continue to pass, please wait...

    Error: ORA-16664: impossible to receive the result of a database

    Failed.

    Impossible to failover, primary database is always "PRIM".

    Note:it comes to node unique database with physical styandby.

    =====================================================

    In alert log file provides, I am getting below the error during the failover operation:

    Fatal OR connect 12514 error, connect to:

    (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=rac1.localdomain)(PORT=1524)))(CONNECT_DATA=(SERVICE_NAME=PRIM_DGB)(INSTANCE_NAME=PRIM)(CID=(PROGRAM=oracle)(HOST=rac2.localdomain)(USER=oracle)))

    Please suggest to solve this problem.

    Thank you.

    Problem is fixed - value StaticConnectIdentifier checked to a database of primary and standby in dgmgrl ==> primary port and standby was wrong wrt to the listening port value.

    Step 1 > error ORA-16664 and ora-12514

    ==> check StaticConnectIdentifier value for a primary database and a standby in dgmgrl ==> primary port and standby had value default IE 1521

    Primary:

    SEE THE VERBOSE "PRIM" DATABASE

    StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rac1.localdomain) (PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = PRIM_DGMGRL) (INSTANCE_NAME = PRIM)(SERVER=DEDICATED)))'

    Standby time:

    SEE THE DETAILED "DRY" DATABASE

    StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rac2.localdomain) (PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = SEC_DGMGRL)(INSTANCE_NAME=SEC) (SERVER = DEDICATED)

    Step 2 > listening port for the primary and standby is 1524 and 1525, so change these manually.

    Primary:

    SQL > show parameter local_listener

    VALUE OF TYPE NAME

    ------------------------------------ ----------- ------------------------------

    LOCAL_LISTENER chain

    SQL > alter system set local_listener ='(ADRESSE = (PROTOCOL = TCP) (HOST = rac1.localdomain) (PORT = 1524))

    Standby time:

    ALTER system set local_listener = '(ADDRESS = (PROTOCOL = TCP) (HOST = rac2.localdomain) (PORT = 1525))';

    #edit database 'PRIM' set the property StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rac1.localdomain) (PORT = 1524)) (CONNECT_DATA = (SERVICE_NAME = PRIM_DGMGRL) (INSTANCE_NAME = PRIM)(SERVER=DEDICATED)))'

    #edit database 'DRY' set the property StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rac2.localdomain) (PORT = 1525)) (CONNECT_DATA = (SERVICE_NAME = SEC_DGMGRL)(INSTANCE_NAME=SEC) (SERVER = DEDICATED)))'

  • The physical connectivity of fabric interconnect with MDS and failover please suggest

    Dear team

    We have 2 FI and 2 MDS 1 SAN

    Currenlty connectivity is

    2 physical connections of FI - has direct MDS1

    2 direct physical links to FI - B MDS2

    SDM 1 connection to the main controller of SAN

    SDM 1 connection to the secondary controller SAN

    Connection of 2 MDS to the PDC of SAN

    2 MDS to the secondary controller SAN connection

    Hope the above connectivity is good?

    We had watched

    http://www.Cisco.com/en/US/prod/Collateral/ps4159/ps6409/ps5990/white_paper_c11_586100.html (as a team always preferred to go through the standards of cisco)

    We could consolidate the FI and the primary and subordinate, even here for MDS in we need FI. or it will be through FIS?

    If not these 2 MDs they work as independent but share the configs that happens between them?

    Now this never changes (creation area) we do on MDS1 hope that will get relpicated in MDS2 through FIS?

    If MDS1 fails will be all the configuration is available on MDS2 and yet infra smooth it won't work? and vice versa?

    All the additional steps to be performed to achieve this?

    Which is the best way to do this please suggest

    Thanks and greetings

    Jose

    Hi Jose.

    Physically, your connection is good.

    On the side of the UCS, the role of "Primary" and "Subordinate" refer only to the management of the system and the device that actually performs UCS Manager.

    Each MDS device will have a separate configuration (zoning).  It's different between the 2 devices.

    The blade itself will be a connection on each side, or the "fabric SAN.

    for example

    +----+

    +---+    +-----+

    |   |    |     |

    |   |    |     |

    |   | SAN |     |

    | +->----<--+ >

    | |         |  |

    | |         |  |

    +---+-+-+    +--+--+--+

    |       |    |        |

    | MDS - A |    | MDS - B |

    +--^-^--+    +---^-^--+

    | |           | |

    +--+-+--+    +---+-+--+

    |       |    |        |

    | UCS - A |    | UCS - B |

    +--+----+    +-----+--+

    |               |

    |               |

    VSAN100 +-+ | VSAN200

    |    |     |    |

    +----><>

    | Blade |

    +-----+

    The blade will have a HBA on FabricA (VSAN100) and FabricB (VSAN200)

    Each HBA has a different WWPN, and on the Bay of SAN, each controller will have a WWPN

    So on MDS - A, the zoning will be:

    Blade WWPN

    WWPN primary storage has

    WWPN secondary storage has

    MDS - B, the zoning will be:

    Blade WWPN B

    Storage WWPN primary B

    Storage WWPN secondary B

    So the configuration is * not * synchronized between both MDS devices, but each of them have visibility to the device of vHBA of blades.  At the level of the blade, the software of multiple paths on the operating system will handle any failover.

    On the UCS, we would usually use a channel from Port to the MDS.

  • 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

Maybe you are looking for