Management port on fabric interconnect question

I'm using the same pool of of IP addresses for my FI and KVM pool.
I need to make sure that my management port on each FI is connected to a switch that is also accessible in the same range\subnet, correct?
After setting everything up, I'm currently unable to get to my VIP.

Correct.  Ensure the subnet masks are correct, and the gateway is reachable.  If you can "ping" from outside to each FI's management IP, there's no reason you shouldn't be able to reach the VIP.  Obivously the VIP address must be in the same subnet & VLAN as the management IPs, and not be used elsewhere in your environment.
Regards,
Robert

Similar Messages

  • Port-channel L2 problem with Fabric Interconnect and Nexus 7010

    Hi,
    i using port-channel from both fabric interconnect to N7k with 3 cables per Fabric Interconnect.
    but, my problem is when i creating port-channel, Fabric Interconnect don't support mode ON dan rate-mode share in Interface 10G Nexus 7010.
    I was trying :
    1. I using non dedicated port in Nexus 7010.
          - rate-mode share
          - channel-group 1 mode active
          - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was suspended
    2. I using non dedicated port in Nexus 7010
         - rate-mode share
         - channel group 1 mode on
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was came up, but in Fabric interconnect was failed.
    3. I using dedicated port in Nexus 7010
         - rate-mode share
         - channel group 1 mode active
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was suspended
    4. I using dedicated port in Nexus 7010
         - rate-mode dedicated
         - channel group 1 mode active
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was came up and running well.
    but, the problem is my costumer do not want using a dedicated rate-mode. if i using dedicated mode the only available port is 8 interfaces instead of 32 ports. i want to using rate-mode share in nexus 7010.
    is there any way to configuring port-channel using mode on in fabric interconnect ? i was trying using CLI to create port-channel in Fabric interconect but i cannot configure the channel group protocol.
    i attach the topology of N7K with Fabric interconnect.
    regards,
    Berwin H

    Hi Manish,
    the issue was solved, i was fix it last week.
    the solution is:
    i enable the license grace-priode (since my license is Enterprise so cannot create VDC) then i create a VDC (ex: VDC 2)  so i allocate the interface on all module
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin-top:0cm;
    mso-para-margin-right:0cm;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0cm;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"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;}
    N7K-M132XP-12 to VDC 2. after that i delete VDC 2 then all interface back to VDC 1 (default vdc). then i enable the rate-mode share in dedicated port and bundle into port-channel and its working.
    i dont know why it must move to VDC first then it will working, maybe cisco can explain the reasons.
    So here the result of my port-channel :
    SVRN7KFARM-HO-01# show port-channel summary
    Flags:  D - Down        P - Up in port-channel (members)
            I - Individual  H - Hot-standby (LACP only)
            s - Suspended   r - Module-removed
            S - Switched    R - Routed
            U - Up (port-channel)
    Group Port-       Type     Protocol  Member Ports
          Channel
    1     Po1(SU)     Eth      LACP      Eth1/1(P)    Eth1/2(P)    Eth1/3(P)
                                         Eth1/4(P)    Eth1/25(P)  
    2     Po2(SU)     Eth      LACP      Eth1/9(P)    Eth1/10(P)   Eth1/11(P)
                                         Eth1/12(P)   Eth1/26(P)  
    3     Po3(SU)     Eth      LACP      Eth1/17(P)   Eth1/18(P)  
    4     Po4(SU)     Eth      NONE      Eth10/32(P)  Eth10/34(P)  Eth10/35(P)
                                         Eth10/36(P)
    Thanks.
    Berwin H

  • Port-channel Problem between Fabric Interconnect and N7K vPC

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

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

  • Use UCS Fabric Interconnect 6100 with Extension Module E0060 (6 FC Ports)

    Hi Everybody,
    I have problem in my Architecture !!!   I THINK
    I want to use Extension Module E0060 (6 FC Ports) for UCS Fabric Interconnect 6100 for interconnectiong my Storage Array ( 2 Controlers with 2 FC Ports by cont.)  instead of use Nexus 5000 between FI 6100 and my Storage Array
    I tried to find details or case study for this way but No thing find !!!!!!!!!!!!
    I just find that th e best practices is to use Nexus 5000 but I have enough FC Ports with this Module ......  I THINK   but I m not an Expert
    Thanks for your help.

    Thanks for your answer Michael,
    But I really don't understand why I can't use the Module E0060 (6 FC Ports) in the FI 61xx instead of NEXUS 500 (I hope that's not commercial goal ) ????
    As you now the hardware architecture of FI 61xx is the same that Nexus 5000, the difference is that 61xx have features added and UCS Manager embedded.
    Now, If they have a features limited in 61xx like NPV or other things, I wil understand But until this moment I don't find Real ANswer in Cisco site of forum ( Al cisco documents mentionned that the best practices and the perfect design is to use 61xx and Nexus 5000 and MDS Switch between UCS and Storage Array ???????
    I Hope that you understand my problem

  • Fabric Interconnect B, management services are unresponsive

    Hi,
    We have configured Call Home option in UCSM and we are getting below error from Call Home option since last Saturday. We have open TAC with Cisco to troubleshoot this error but as per TAC "The error is a transient error from which the fabric interconnects can automatically recover."
    Below is the error messages we are getting
    E-mail-1:
    Subject:
    System Notification from System-A - diagnostic:GOLD-major - 2011-12-27 17:54:09 GMT-00:00 Fabric Interconnect B, management services are unresponsive
    Body Message:
    System Name:System-A
    Time of Event:2011-12-27 17:54:09 GMT-00:00
    Event Description:Fabric Interconnect B, management services are unresponsive
    Severity Level:6
    E-mail-2:
    Subject:
    System Notification from System-A - diagnostic:GOLD-major - 2011-12-27 17:54:09 GMT-00:00 Fabric Interconnect B, management services are unresponsive
    Body Message:
    <?xml version="1.0" encoding="UTF-8" ?>
    <soap-env:Envelope xmlns:soap-env="http://www.w3.org/2003/05/soap-envelope">
    <soap-env:Header>
    <aml-session:Session xmlns:aml-session="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">
    <aml-session:To>http://tools.cisco.com/neddce/services/DDCEService</aml-session:To>
    <aml-session:Path>
    <aml-session:Via>http://www.cisco.com/appliance/uri</aml-session:Via>
    </aml-session:Path>
    <aml-session:From>http://www.cisco.com/appliance/uri</aml-session:From>
    <aml-session:MessageId>1058:SSI1442BFRC:4EFA0641</aml-session:MessageId>
    </aml-session:Session>
    </soap-env:Header>
    <soap-env:Body>
    <aml-block:Block xmlns:aml-block="http://www.cisco.com/2004/01/aml-block">
    <aml-block:Header>
    <aml-block:Type>http://www.cisco.com/2005/05/callhome/diagnostic</aml-block:Type>
    <aml-block:CreationDate>2011-12-27 17:54:09 GMT-00:00</aml-block:CreationDate>
    <aml-block:Builder>
    <aml-block:Name>UCS 6100 Series Fabric Interconnect</aml-block:Name>
    <aml-block:Version>4.2(1)N1(1.43q)</aml-block:Version>
    </aml-block:Builder>
    <aml-block:BlockGroup>
    <aml-block:GroupId>1059:Serial Number:4EFA0641</aml-block:GroupId>
    <aml-block:Number>0</aml-block:Number>
    <aml-block:IsLast>true</aml-block:IsLast>
    <aml-block:IsPrimary>true</aml-block:IsPrimary>
    <aml-block:WaitForPrimary>false</aml-block:WaitForPrimary>
    </aml-block:BlockGroup>
    <aml-block:Severity>6</aml-block:Severity>
    </aml-block:Header>
    <aml-block:Content>
    <ch:CallHome xmlns:ch="http://www.cisco.com/2005/05/callhome" version="1.0">
    <ch:EventTime>2011-12-27 17:54:09 GMT-00:00</ch:EventTime>
    <ch:MessageDescription>Fabric Interconnect B, management services are unresponsive</ch:MessageDescription>
    <ch:Event>
    <ch:Type>diagnostic</ch:Type>
    <ch:SubType>GOLD-major</ch:SubType>
    <ch:Brand>Cisco</ch:Brand>
    <ch:Series>UCS 6100 Series Fabric Interconnect</ch:Series>
    </ch:Event>
    <ch:CustomerData>
    <ch:UserData>
    <ch:Email>[email protected]</ch:Email>
    </ch:UserData>
    <ch:ContractData>
    <ch:CustomerId>[email protected]</ch:CustomerId>
    <ch:ContractId>ContractID</ch:ContractId>
    <ch:DeviceId>N10-S6100@C@SSI1442BFRC</ch:DeviceId>
    </ch:ContractData>
    <ch:SystemInfo>
    <ch:Name>System-A</ch:Name>
    <ch:Contact>Name</ch:Contact>
    <ch:ContactEmail>[email protected]</ch:ContactEmail>
    <ch:ContactPhoneNumber>+00-0000000000</ch:ContactPhoneNumber>
    <ch:StreetAddress>Office Address</ch:StreetAddress>
    </ch:SystemInfo>
    </ch:CustomerData>
    <ch:Device>
    <rme:Chassis xmlns:rme="http://www.cisco.com/rme/4.0">
    <rme:Model>N10-S6100</rme:Model>
    <rme:HardwareVersion>0.0</rme:HardwareVersion>
    <rme:SerialNumber>SerialNumber</rme:SerialNumber>
    </rme:Chassis>
    </ch:Device>
    </ch:CallHome>
    </aml-block:Content>
    <aml-block:Attachments>
    <aml-block:Attachment type="inline">
    <aml-block:Name>sam_content_file</aml-block:Name>
    <aml-block:Data encoding="plain">
    <![CDATA[
    <faultInst
    ack="no"
    cause="management-services-unresponsive"
    changeSet=""
    code="F0452"
    created="2011-12-27T23:24:09.681"
    descr="Fabric Interconnect B, management services are unresponsive"
    dn="sys/mgmt-entity-B/fault-F0452"
    highestSeverity="critical"
    id="2036245"
    lastTransition="2011-12-27T23:24:09.681"
    lc=""
    occur="1"
    origSeverity="critical"
    prevSeverity="critical"
    rule="mgmt-entity-management-services-unresponsive"
    severity="critical"
    status="created"
    tags=""
    type="management"/>]]>
    </aml-block:Data>
    </aml-block:Attachment>
    </aml-block:Attachments>
    </aml-block:Block>
    </soap-env:Body>
    </soap-env:Envelope>
    We want to understand that what is the impact of this error and is there anything that we can do to prevent this error? Also want to know what might be the cause get this error?
    Let me know if anything else is needed from my side
    show-tech file uploaded.

    Padma,
    TAC Engineer sent below mail
    Hi Amit,
    I’ve checked through the show tech you’ve uploaded and have not found any indicators of errors for the error message you are seeing.
    As I mentioned in the call, the error is a transient error from which the fabric interconnects can automatically recover from. The recommended action is to wait for a few (10-15min) to see if the error clears automatically. If the error does not clear then we will need to do further troubleshooting. This error on its own is not a cause for worry. As you have HA in your system the management services would have failed over the to the other fabric interconnect and would not affect your system performance.
    We can leave the system under observation for a few days to see if other errors occur concurrently with this error.
    I will upload show-tech logs here, find my reply below
    Is the alert generated only for FI B or both FIs ->> Amit: Alert generated for FI-B only
    Any change in cluster state corresponding to alert time stamp ->> Amit: Unfortunately when this error generating we are unable to see the cluster state because of timing. If you can guide / suggest from any other location I can find the state that will be helpful
    Cluster physical link status ->> Amit: Cluster link is OK
    Does FI have any core dumps ->> Amit: I don't have any idea about this. How can check this ?
    Regards,
    Amit Vyas

  • Appliance port on 6248 Fabric Interconnects

    Is it possible to setup a storage device with a CIFS share on the 6248's through a port defined as an appliance port?  The GUI guide says this:
    "Appliance ports are only used to connect fabric interconnects to directly attached NFS storage."
    But what would be the difference if it were a CIFS share rather than an NFS mount?
    I'm trying to setup a storage unit that does both NFS and CIFS, but the backup software that I want to point to it through the FI's needs to have it as a CIFS share due to being a Windows platform.
    Any and all comments welcome.
    Thanks,
    Chad

    iSCSI, CIFS and NFS targets are all valid uses for the appliance port. 
    All the appliance port does is allow MAC learning on the interface. 
    Regards,
    Robert

  • - No link between IOM port 3/2/2 and fabric interconnect B:1/18

    Specifically I'm trying to find out what the 3/2/2 means in - No link between IOM port 3/2/2 and fabric interconnect B:1/18

    This from the fault reference guide:
    "No link between IOM port [chassisId]/[slotId]/[portId] and fabric interconnect [switchId]:[peerSlotId]/[peerPortId]"
    http://www.cisco.com/en/US/docs/unified_computing/ucs/ts/faults/reference/UCS_SEMs.html#wp1306388

  • Fabric Interconnect Uplink port channeling...

    Hi,
    We setup port channel of two 10G uplink interfaces on each Fabric Interconnect. Everything is running as expected.
    However we noticed that under 'Port-Channel # (Fabric #)' setting on LAN tap, 'Admin Speed' was set to '10Gbps'.
    Should we leave this configuration as is or match to the maximum bandwidth of port Channel we set up (20Gbps)?
    I only see four options on each port channel configuration, 1 Gbps, 10Gbps, 20Gbps and 40Gbps so I'm not sure if we should change this setting.
    Thank you                   

    Hello,
    You do not need to change the speed ( admin ). 20 Gbps configuration is applicable for certain server models.
    --------  NXOS output -----------------
    FI-A(nxos)# sh run int port-channel 1
    interface port-channel1
      description U: Uplink
      switchport mode trunk
      speed 10000
    FI-A(nxos)# show int port-channel 1
    port-channel1 is up
      Hardware: Port-Channel, address: 547f.ee67.e0fb (bia 547f.ee67.e0fb)
      Description: U: Uplink
      MTU 1500 bytes, BW 20000000 Kbit, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA
      Port mode is trunk
      full-duplex, 10 Gb/s
    FI-A(nxos)# sh int bri
    Port-channel VLAN  Type Mode   Status  Reason                    Speed  Protocol
    Interface                                                               
    Po1          1     eth  trunk  up      none                       a-10G(D)  lacp
    There is cosmetic defect where we list the operational speed as 10 Gbps instead of 20Gbps
    FI-A /eth-uplink/fabric # show port-channel detail
    Port Channel:
        Port Channel Id: 1
        Name: FIA
        Admin State: Enabled
        Oper State: Up
       Speed: 10 Gbps
        Oper Speed: 10 Gbps
        State Reason:
        flow control policy: default
    HTH
    Padma

  • Fabric Interconnect To MDS 9148 FC Port Channel/Trunks

    Is it possible to create both a Port Channel and Trunk on a Cisco MDS 9148? Yes correct?
    Or can I only trunk between the 2 MDS switches and not the MDS to Fabric Interconnect?
    These FC links would be connected to a 2248XP Fabric Interconnect carrying multiple VSANs from the MDS to the Fabric Interconnect.
    Thanks

    Hello,
    Yes, you can have trunk links grouped into port channel ( F port-channel trunking ) between FI and MDS.
    http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_0101.html
    Padma

  • Fabric Interconnect 6120xp question

    I have two fabric interconnect 6120xp in cluster on one i find the ip in running config and on the partner i dont. It might be due to this i dont get the ipaddress of the fabric interconnect (shows as 0.0.0.0) on my san switch when querying fcns database. Any help is appreciated.
    lhr02-wxp00-fic01-B(nxos)# sh run |inc ip
    ip host lhr02-wxp00-fic01-B 10.255.96.78
      ip address 10.255.96.78/24
    lhr02-wxp00-fic01-A(nxos)# sh run |inc ip
    role name server-equipment
    lhr02-wxp00-fic01-A(nxos)#
    lhr02-wxif-san02#  show fcns database  npv
    VSAN 20:
    NPV NODE-NAME           NPV IP_ADDR     NPV IF  CORE SWITCH WWN         CORE IF
    20:14:54:7f:ee:04:c8:01 10.255.96.78    fc2/4   20:00:54:7f:ee:07:6e:80 fc1/6
    20:14:54:7f:ee:04:c8:01 10.255.96.78    fc2/2   20:00:54:7f:ee:07:6e:80 fc1/5
    lhr02-wxif-san01#  show fcns database  npv
    VSAN 10:
    NPV NODE-NAME           NPV IP_ADDR     NPV IF  CORE SWITCH WWN         CORE IF
    20:0a:54:7f:ee:03:ee:c1 0.0.0.0         fc2/1   20:00:54:7f:ee:17:eb:80 fc1/3
    20:0a:54:7f:ee:03:ee:c1 0.0.0.0         fc2/3   20:00:54:7f:ee:17:eb:80 fc1/4

    On the FI with the 0.0.0.0 ipaddress  run the sho npv inter info | inc IP.
    Next go into UCSM and select the equipment tab.Then pick the FI in question. On the right select General tab and then Access.
    What is the ipaddress? Does it also show 0.0.0.0 here as well?
    If it does, try changing it to the address you wanted and check it again.
    If that does not work then you can try to erase the config on that FI and reconfiguring it from the begining.
    Verify they it joins the cluster and HA is ready and the ipaddress is available.

  • Question about 4500X VSS management port

    I have two standalone 4500X switches that I'm planning to convert to VSS. If I cable the management port on both switches to a management cloud, which management port should I put the management IP address? Is it the port on the active switch? if the active switch failed, would the management port on the standby switch take over the management IP?
    The management port is in VRF mgmtVrf. Should I create a default route for the VRF such as "ip route vrf mgmtvrf 0.0.0.0 0.0.0.0 ....." to point to its default gateway IP?
    Thanks

    When you convert the chassis to VSS, only the management interfaces (FastEthernet1) for switch-1 (active) will be visible in the config.  So you want to cable both management interfaces to your management cloud, but you only apply the IP to the active switch.
    The management port is in VRF mgmtVrf. Should I create a default route for the VRF such as "ip route vrf mgmtvrf 0.0.0.0 0.0.0.0 ....." to point to its default gateway IP?
    Correct, you need a default route in that mgmt vrf pointing to the gateway.
    HTH

  • No link between IOM port 2/2/3 and fabric interconnect B

    Hello
    I am trying to remove an uplink from an IOM to the fabric interconnect as its not required.  I have tried to reset the I/O module and re-acknowledge the chassis with no luck, it is still shown in the GUI with the error message as in the subject.  We are currently running 2.0(1s).  The kit isn't in production yet.
    Thanks for any help

    Yes i agress thats a pretty heavy approach to clean it. No if you left it there as it is, there would have been no operational issues. It would have just left this fault in the UCSM.
    ./Abhinav

  • 7304 nse100 FE Management Port configuration question

    How can the F0/0 FE Management Port be used? Since the 7304 has a redundant NSE100 prossesor card I would like to use this port two ways as a remote router access port for management and as a standard FastEthernet interface. Is configuration and advertising of the interface IP address the same as standard FastEthernet interfaces?

    The FastEthernet port on the Cisco 7304 is for management purposes only. Any other use of the FastEthernet port is not supported. This statement is according to the configuration notes of 7304.So, it cannot be used as a standard GE port.

  • Question of telnet or SSH to 4500X management port

    I configured 4500X management port (Fa1) and I can ping the IP from the network. But when I tried telnet to the port, the switch showed "password required but not set".
    I didn't configure any password for VTY. Should it be equivalent to "no login"? If to set or change a password for the management port, where to configure it?
    Thanks a lot

    Hi,
    Yes, "password" and "login" for the management port should be configured under the "vty" lines.
    Best regards,
    Antonin

  • Why would Fabric Interconnects populate in fabric topology?

    If the Fabric Interconnects are configured in End-Host mode, why would it be sending management traffic through an F port link making it populate on our fabric topology.  We don’t have this on our existing Blades centers and would expect that we would be able to suppress this for these UCS interconnect devices.  These devices are not managed by the SAN teams and they would prefer them NOT to appear as though they are.
    Any advice?

    Release notes in 2.0(5a) showed 
    CSCua91672
    The fcoe_mgr hap reset will no longer cause FI reboot.
    http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/release/notes/OL_25363.html
    I am really never on the Fiber Interconnects to execute any CLI commands.  But a memory leak for some other reason would certainly be a possibility. The fact that its own High Availability process causes double reset in its own High Availability architecture is troubling. 

Maybe you are looking for