Pointer on getting CMIC to talk to the UCSE

Version 1
    This document was generated from CDN thread

    Created by: Ken Coley on 03-04-2012 08:45:03 PM
    The documentation in the Installation and Configuration guide is a little scant.  Not being familar with CMIC, I am a little lost of how all the connections work and how to get this up and running properly.  Is there a cheat sheet (20 pages or less) on how to get this configured and up and running?
     
    -Ken

    Subject: RE: Pointer on getting CMIC to talk to the UCSE
    Replied by: Brett Tiller on 03-04-2012 08:55:20 PM
    Hi Ken,

    We provide a GUI Management and Configuration Guide in the knowledge base that covers how to utilize the web interface.  Unfortunately, we don't have a quick start guide for that at the moment. 

    In terms of getting CIMC up and running, I've provided a sample router configuration below.  Based upon this configuration you can then type in the browser:  http://192.168.1.61  - IE seems to work best.    A few certificate acceptance screens should then appear, and you'll then log in with the default username/password provided in the release notes - admin/password.

    interface GigabitEthernet0/0
    ip address 192.168.1.60 255.255.255.0

    interface ucse2/0
    ip unnumbered GigabitEthernet0/0
    imc ip address 192.168.1.61 255.255.255.0 default-gateway 192.168.1.60
    imc access-port host console

    interface ucse2/1
    description Internal switch interface connected to Service Module
    no ip address

    ip route 192.168.1.61 255.255.255.255 ucse2/0


    -Brett

    Subject: RE: Pointer on getting CMIC to talk to the UCSE
    Replied by: Ken Coley on 04-04-2012 01:08:35 PM
    Brett,

    Tried these instructions, but they still don't work.  I am confused, is CMIC running on the UCSE or is it running on the second core of the router?  I never got it to work on 12.5(1)4.  So perhaps, I need to get CMIC running properly on the router?

    -Ken

    Subject: RE: Pointer on getting CMIC to talk to the UCSE
    Replied by: Brett Tiller on 04-04-2012 01:47:46 PM
    Ken,

    This CIMC is running on the UCSE, so the special configuration previously required with the CIMC-E that runs on the router second core is not required here.  Are you able to ping the service module from your windows box?  The interfaces are all up as well?

    Thanks,

    Brett

    Subject: RE: Pointer on getting CMIC to talk to the UCSE
    Replied by: Ken Coley on 04-04-2012 02:12:04 PM
    Brett,

    I now have it hooked up using external interface cabled to gig0/1 of the router.

    I have the router configured as 192.168.1.254 and the commands for UCSE set to:

    wsmtest#show run int ucse 2/0
    Building configuration...

    Current configuration : 130 bytes
    !
    interface ucse2/0
    ip unnumbered GigabitEthernet0/1
    imc ip address 192.168.1.253 255.255.255.0
    imc access-port dedicated
    end

    The router can now ping 192.168.1.253, but nothing outside the router can see that IP address.

    -Ken

    Subject: RE: Pointer on getting CMIC to talk to the UCSE
    Replied by: Ken Coley on 04-04-2012 02:17:27 PM
    Brett,

    Do you want to do a webex so I can show you whats going on here?

    -Ken

    Subject: RE: Pointer on getting CMIC to talk to the UCSE
    Replied by: Brett Tiller on 04-04-2012 02:48:53 PM
    Ken,

    Yes that sounds like a good idea.  I'd like to have a couple of our engineers to attend as well.  What times do you have available today?

    Brett

    Subject: RE: Pointer on getting CMIC to talk to the UCSE
    Replied by: Ken Coley on 04-04-2012 03:04:35 PM
    I can make myself available at whatever time is good for you.

    -Ken

    Subject: Re: New Message from Ken Coley in Unified Computing System E-Series Servers
    Replied by: Tuong Au on 04-04-2012 03:14:17 PM
    Hi Ken,

    There are several ways to access CIMC.  If you want to access CIMC using
    Œimc access-port dedicated¹ which is the dedicated management interface on
    the module then router configuration would be:

    -----[Management Interface UCS Module]

    Router#show run int ucse 4/0
    Building configuration...

    Current configuration : 139 bytes
    !
    interface ucse4/0
    imc ip address 192.168.1.253 255.255.255.0
    imc access-port dedicated
    end

    Have PC on same subnet as CIMC ip address and you should be able to access
    CIMC GUI.

    If you want access to CIMC using router¹s ucse interface then configuration
    would be:

    -----[G0/1 Router UCSE x/0]-----[UCSE Module]

    Router#show run int g0/1
    Building configuration...

    Current configuration : 119 bytes
    !
    interface GigabitEthernet0/1
    ip address 192.168.1.254 255.255.255.0
    end

    Router#show run int ucse 4/0
    Building configuration...

    Current configuration : 139 bytes
    !
    interface ucse4/0
    ip unnumbered GigabitEthernet0/1
    imc ip address 192.168.1.253 255.255.255.0
    imc access-port host console
    end

    Router#show run | i ip route
    ip route 192.168.1.253 255.255.255.255 ucse4/0
    Router#

    Thanks,
    Tom


    On 4/4/12 11:12 AM, "Cisco Developer Community Forums"
    <cdicuser@developer.cisco.com> wrote:

    > Ken Coley has created a new message in the forum "UCSE Beta Tester Questions":
    >
    > --------------------------------------------------------------
    > Brett,
    >
    > I now have it hooked up using external interface cabled to gig0/1 of the
    > router.
    >
    > I have the router configured as 192.168.1.254 and the commands for UCSE set
    > to:
    >
    > wsmtest#show run int ucse 2/0
    > Building configuration...
    >
    > Current configuration : 130 bytes
    > !
    > interface ucse2/0
    >  ip unnumbered GigabitEthernet0/1
    >  imc ip address 192.168.1.253 255.255.255.0
    >  imc access-port dedicated
    > end
    >
    > The router can now ping 192.168.1.253, but nothing outside the router can see
    > that IP address.
    >
    > -Ken
    > --
    > To respond to this post, please click the following link:
    >
    > <http://developer.cisco.com/group/ucse/forums/-/message_boards/view_message/54
    > 04886>
    >
    > or simply reply to this email.

    Subject: RE: Pointer on getting CMIC to talk to the UCSE
    Replied by: Ken Coley on 04-04-2012 03:26:22 PM
    Tuong,

    Using "imc access-port host console" burns up a router port, so you might as well do "imc access-port dedicated" and cable externally.  I dont see logically the difference.  Both require directing traffic to one of the unused gig interfaces.  BTW, using imc access-port host console requires that the gig interface its connected to be "UP", so where would you cable it.  This is why I suggest for each of the access methods a logical diagram, and use case be put into the user manual, so that an intelligent decision can be made.

    -Ken

    Subject: Re: New Message from Ken Coley in Unified Computing System E-Series Servers
    Replied by: Tuong Au on 04-04-2012 03:44:16 PM
    Hi Ken,

    Thanks for the feedback.  Difference is using dedicated mode does not
    require any router ports.  Traffic is directed to the dedicated management
    port on the module.

    You are correct about using &#140;imc access-port host console¹ requiring gig
    interface to be up.  You could have gig interface connect to switch so it
    will be &#140;UP¹.  Connection would be something like this for &#140;imc access-port
    host console¹:

    ----------[G0/1 Router UCSE x/0]------[UCSE Module]

    We will take your suggestion to improve our documentation with adding
    diagrams describing access methods.

    Thanks,
    Tom


    On 4/4/12 12:26 PM, "Cisco Developer Community Forums"
    <cdicuser@developer.cisco.com> wrote:

    > Ken Coley has created a new message in the forum "UCSE Beta Tester Questions":
    >
    > --------------------------------------------------------------
    > Tuong,
    >
    > Using "imc access-port host console" burns up a router port, so you might as
    > well do "imc access-port dedicated" and cable externally.  I dont see
    > logically the difference.  Both require directing traffic to one of the unused
    > gig interfaces.  BTW, using imc access-port host console requires that the gig
    > interface its connected to be "UP", so where would you cable it.  This is why
    > I suggest for each of the access methods a logical diagram, and use case be
    > put into the user manual, so that an intelligent decision can be made.
    >
    > -Ken
    > --
    > To respond to this post, please click the following link:
    >
    > <http://developer.cisco.com/group/ucse/forums/-/message_boards/view_message/54
    > 05086>
    >
    > or simply reply to this email.

    Subject: RE: New Message from Ken Coley in Unified Computing System E-Series Servers
    Replied by: Brett Tiller on 04-04-2012 04:36:16 PM
    Great.  Just sent you a meeting request.



    Thanks,



    Brett Tiller

    Custom Application Engineer

    http://developer.cisco.com/web/axp <http://developer.cisco.com/web/axp>

    http://developer.cisco.com/web/srev <http://developer.cisco.com/web/srev>





    From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
    Sent: Wednesday, April 04, 2012 12:05 PM
    To: cdicuser@developer.cisco.com
    Subject: New Message from Ken Coley in Unified Computing System E-Series Servers (UCSE) - UCSE Beta Tester Questions: RE: Pointer on getting CMIC to talk to the UCSE



    Ken Coley has created a new message in the forum "UCSE Beta Tester Questions":

    --------------------------------------------------------------
    I can make myself available at whatever time is good for you.

    -Ken
    --
    To respond to this post, please click the following link:

    <http://developer.cisco.com/group/ucse/forums/-/message_boards/view_message/5405023>

    or simply reply to this email.

    Subject: Re: New Message from Ken Coley in Unified Computing System E-Series Servers
    Replied by: Tuong Au on 04-04-2012 06:00:17 PM
    Hi Ken,

    Tried your scenario where IMC connected to G0/1 of router and to make it
    work we need to add default gateway in the ucse configuration:

    imc ip address 192.168.1.253 255.255.255.0 default-gateway 192.168.1.254

    Here is how I verified:

    ------[G0/2 Router G0/1]-----[IMC UCSE Module]

    PC:
    5.0.0.1/8
    route add 192.168.1.0 mask 255.255.255.0 5.0.0.2

    Router#show run int g0/2
    Building configuration...

    Current configuration : 91 bytes
    !
    interface GigabitEthernet0/2
    ip address 5.0.0.2 255.0.0.0
    duplex auto
    speed auto
    end

    Router#show run int g0/1
    Building configuration...

    Current configuration : 119 bytes
    !
    interface GigabitEthernet0/1
    ip address 192.168.1.254 255.255.255.0
    load-interval 30
    duplex auto
    speed auto
    end

    Router#show run int ucse 4/0
    Building configuration...

    Current configuration : 161 bytes
    !
    interface ucse4/0
    ip unnumbered GigabitEthernet0/1
    imc ip address 192.168.1.253 255.255.255.0 default-gateway 192.168.1.254
    imc access-port dedicated
    end

    Router#show run | i ip route
    ip route 192.168.1.253 255.255.255.255 ucse4/0
    Router#


    Thanks,
    Tom


    On 4/4/12 11:12 AM, "Cisco Developer Community Forums"
    <cdicuser@developer.cisco.com> wrote:

    > Ken Coley has created a new message in the forum "UCSE Beta Tester Questions":
    >
    > --------------------------------------------------------------
    > Brett,
    >
    > I now have it hooked up using external interface cabled to gig0/1 of the
    > router.
    >
    > I have the router configured as 192.168.1.254 and the commands for UCSE set
    > to:
    >
    > wsmtest#show run int ucse 2/0
    > Building configuration...
    >
    > Current configuration : 130 bytes
    > !
    > interface ucse2/0
    >  ip unnumbered GigabitEthernet0/1
    >  imc ip address 192.168.1.253 255.255.255.0
    >  imc access-port dedicated
    > end
    >
    > The router can now ping 192.168.1.253, but nothing outside the router can see
    > that IP address.
    >
    > -Ken
    > --
    > To respond to this post, please click the following link:
    >
    > <http://developer.cisco.com/group/ucse/forums/-/message_boards/view_message/54
    > 04886>
    >
    > or simply reply to this email.

    Subject: RE: Pointer on getting CMIC to talk to the UCSE
    Replied by: Ken Coley on 04-04-2012 06:03:17 PM
    Thanks for all your help.  Its up and running from both inside and outside the lab.