MSE 8510 TelePresence Server Migration - Issue of license

I am following the process of conversion to a MCU 8510 into a server TS 8710.

I ordered and received the migration SKU 0-dollar and have the code PAK

Part number of top-level

L-8000-CHLIC-PAK MSE 8000 chassis Licenses PAK PIDs

Option part number
L-8000-TSMO telepresence screen Option Migration, order L-8000-CHLIC-PAK

Key question: will be recorded against this pak:

  1. The SN # MSE 8050 supervisor blade
  2. The SN # MSE chassis
  3. The SN # 8510 blade to be converted.

There are good docs on the conversion process of loading software and the process.

But nothing that I could find references exactly what SN # to use when registering the PAK for this process.

The option TSMO key will apply to the MSE 8000 chassis.

You are right, that the document is not clear where to apply, but it is also mentioned (very badly) on pg 12, in the section reference to the function keys.

Tags: Cisco Support

Similar Questions

  • Content of telepresence server migration

    Hi all

    We have TCS v5.3 connected to SIN with all your records.

    In the meantime we installed the VM v6.1 TCS and configured the same way as that of 'former '. Everything works fine. The only thing left to do, connect to NAS.

    We will be able to access all records of new TCS by simply connecting to NAS, given that each record has an owner/creator which is the 'old' CHT? Is there a procedure how to do other than that described in the Administrator's guide for a new TCS for a NAS empty?

    Should we use assistant migration? I read that some people had problems run this software properly and access their records after migration.

    Thank you.

    Petar

    You can simply connect the new Sin TCS because without the former CHT base nothing will be linked.  You must follow the TCS 6.1 Migration Wizard tool Guide, there are steps for those who have their stored media on a NAS.  I've never had a problem myself with a migration of TCS and I conducted several with all the media recording a NAS.

  • 4.0U2 > 4.1 server migration issue

    I'm currently experimenting with a VC 4.0u2 & gt; 4.1 migration. I install a new Windows 2008R2 host for the VC and have run the migration tool on the old Victoria Cross, and then again on the new VC to import the configuration. I'm a little confused as to what to do once the migration is completed successfully... I disconnect the old VC, withdraw the AD and then set the parameters of the new Victoria Cross to the former (IP address, host name)? I leave the IP and hostname as new entities and then edit info on the ESX servers and within the view? Which is better?

    Thanks in advance.

    My Blog: http://rebootuser.com

    If you have found this device or any other useful post please consider the use of buttons useful/correct for award points.

    Hello

    Take a look at this thread http://communities.vmware.com/thread/281955

    Kind regards

    Micke

  • cluster with telepresence Server 8710

    Hello

    Currently, I want to deploy the client conference and here is the list that I bought for my client:

    -telepresence Server 8710 with 24 licenses x 2

    -MSE 8000

    -License CUCM

    -VCS license

    My questions are:

    1. from the Cisco documentation, I know that 2 of my server of telepresence could be clustered. 1 my server Teleprsence will be the master blade and the other will be the blade of the slave. By doing this, my server of telepresence is already grouped?

    2. I don't have a driver's license, but I know that this driver could manage 1 telepresence Server wethere that she is not allowed. I tried to manage my my server in cluster of telepresence, but he said that driver had 2 telepresence managed server. I thought that my number of clustered server of telepresence in 1 for conductor. Can someone explain this?

    3. what happened to the deployment guide if I want to use all my 24 licenses? From my understanding, 1 Telepresence Server Blade can only manage 12 licensing screen and cascade could not been since I couldn't do it as remotely managed. Help, please.

    Thank you.

    Telepresence Server MSE 8710 installing blades are autonomous, it is not until you configure using the blade of supervisor MSE 8050 they will become a cluster.  See clustering on pg 90 of the Supervisor MSE 8050 Help Guide.  I don't know how a cluster server Telepresence would manage a conference which exceeded a unique ability of blades that was within the cluster, but according to the help guide of supervisor, it is said that the master blade could allocate licenses video port to the participants in the Conference that could be a big conference or several small conferences.  I would say, just create a conference and start adding in the participants and see what happens.

    Looking at the conductor data sheet it is said that the Essentials (or the free version) can support '1' (independent), since a cluster behaves as a single server, but in reality it is more than 1 server it probably not supported.  The conductor Admin Guide on pg 17, it is confirmed that the free version of conductor does not support cluster conference bridges.  It seems that if you want to use with driver cluster conference bridges, you must at least move to select conductor (middle version), because the free version does not support.

    If you use driver for some reason, you should be able to configure the 8710 blades runs remotely managed mode, I have several configured this way, but they are all autonomous blades, none is in a cluster.  Help server TelePresence MSE 8710 Mode guide managed remotely on the basis

    Is there a particular reason that you must use a driver, why not use the blades of telepresence Server 8710 MSE mode managed locally in a cluster?  Help server TelePresence MSE 8710 Mode guide managed locally based

  • Why replace MSE 8510 MCU 4.4 with Telepresence Server (3.1)

    We have a with MCU 4.4 MSE 8510. Looking at the software accessible to the general public, that looks like that I could replace the software with the telepresence instead server software.

    Why I do this? What can I win (and lose) by? I don't have any old CTS systems, just Jabber, MXP and C systems. Is telepresence server software that is actively developed while the old software MCU is not?

    Thank you

    I agree with you, Codian MCU is the best.   =)

    This is why I think Cisco is not going to add MCU multi-screen support, because if MCU multi-screen support, I don't know that all customers would not want to migrate to server TP or buy a new server TP.

    But because of these two main features of server TP, we think about its use, who are the multimonitor support and support for the optimization of the resources with the driver.

    Many Cisco! As always... In this way, they can keep the two products on the market, MCU and GST.

    Paulo Souza

    My answer was helpful? Please note the useful answers and do not forget to mark questions resolved as "responded."

  • Cisco Telepresence Server/Cisco Telepresence driver/Cisco VCS - C / Cisco TMS license

    A big problem with the fact that I'm stuck is licensing. Really, I have tried many things to find the solution for it, but could not.

    I have actually made all of these servers (mentioned in the title) in my lab in preparation for the CCNP Collaboration certification at home.

    I am not able to complete some laboratories due to license issue (I guess). Y at - it an option to get the demo license for all these servers?

    I would be really greatfull if someone can suggest me the solution and/or the licenses required to complete all the stuff for my CCNP Collab tag.

    Best regards

    Dipak Singh

    TMS and VCS - C when installed without licenses, are automatically set mode of demonstration/test with some availability of license to test with. If needing a VCS-E, you will need to do to your account manager and they should be able to get you the time limited licenses good because I think that 90 days.

    Conductor Essentials is free, which means that you can install and get full functionality without the need of all licenses, but you are limited to 1 conference bridge and no grouping is allowed.

    TelePresence Server require licenses to function, once again, reaching out to your account manager for this.

    At the end of the day, you should reach to your account manager for all of this, as they should be able to help get timed license if you need.

  • Telepresence server pool exceeds the capacity of the license

    1, CUCM 11.0;

    2, cisco TelePresence driver XC4.2

    3, cisco TelePresence server on VM 4.3 (1.13)

    LIC-TP-SMP

    and especially the licenseis on the way.

    When I tested the video-conference with these devices that I have, I got an error:

    conferencefactory. "" "Controller: Level ="INFO"Event ="alarm triggered"Id ="50099"UUID ="fd65270e-9426-42f0-b27a-b6ad733c0e43"gravity ="error"detail ="telepresence server pool exceeds the capacity of the license: cannot create conferences as insufficient TelePresence Server license resource is available in the pool"

    I can say that the error I've met, because of the License (LIC-TP-SMP) I missed?

    You mentioned that the SMP license is "on the way"-If you have not all installed licenses? Conductor will support the old model of the "display license" or multi-stakeholder model, but whatever you use you must installed licenses or it won't work. That error seems to indicate that you have no license installed, it won't work until you solve that.

  • License Server Migration (update 3.5 to 4.1)

    Hello

    Like many, I plan my ESX 3.5 to ESXi 4.1 upgrade.  I'll probably have lots of questions until I'm ready to move forward.  This is my first, which seems to be a simple 1 but I just want to confirm.

    So until I am able to blow ESX 3.5 and install ESXi 4.1 on my hosts, I will need manage guests 3.5 4.1 vCenter Server.

    Currently my Virtual Center Server 2.5U6 is also my license server.  VSphere upgrade guide, I need to install the license server on a new machine and manually migrate the old server to the new license file.

    Not a big deal, but I was wondering:

    If I could just leave the license on the old server, Virtual Center 2.5 Server (with all other services VMware has is stopped and disabled) and point the new vCenter Server for that?

    or

    If it is preferable to install the 3.5 license server on the new vCenter Server, point to itself until I have all of my set hosts to level and can remove the installed 3.5 Server licenses and update licenses then?

    If I could just leave the license on the old server, Virtual Center 2.5 Server (with all other services VMware has is stopped and disabled) and point the new vCenter Server for that?

    or

    If it is preferable to install the 3.5 license server on the new vCenter Server, point to itself until I have all of my set hosts to level and can remove the installed 3.5 Server licenses and update licenses then?

    You can go both ways. I usually prefer the first to avoid the installation of the old license on the new vCenter Server Server server, but is not really a big difference. Simply enter the location of the 'old' license server in the new vCenter Server 4 (for example [email protected]) license tab. That's all.

    André

  • Difficulties of transmission C40 to MSE 8510 via H323

    Nice day

    I currently have intermittent problems between a codec C40 and my MCU. When the device is composed in the bridge it does not have audio or video, it passes however.

    There is no shortage of receive audio or video when composed through SIP (MCU) or dial directly from another endpoint via H323.

    The unit was stable until I upgraded to TC6.2.0. I upgraded C40s all across the country and no other issues brought to the point. The problem persisted after that I get the system back to 6.1.2.

    After the failure of the downgrade I upgraded to 6.2.0 and resetting the device. Once reset, I did a restore of the TMS system.

    The unit is problematic since the installation. I have known problems that the unit could not pick up thermometers grounded which caused the device past security mode and increase the speed of the fans. In order to solve the problem, I upgraded the software twice. Currently, the unit may not in standby mode.  I also found the camera freezes and needs a reboot to restore functionality.

    System details:

    C40: TC6.2.0.20b1616

    MSE 8510: 4.4 (3.42)

    VCS C/E: X7.2.2

    Just a few comments on that for those who are interested.

    This is a bug in x 6.2 and 6.1.1

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

    TC6.2 fail to send ack of the OLC to MCU intermittently

    CSCui47228

    Description

    Symptom:
    TC6.2 not send OLC ack to MCU intermittently.
    Conditions:
    call with the MCU, intermittently receive no video and audio of MCU
    Workaround solution:
    try to reconnect to the call once again

    Last modification:

    Ms 9,2013

    Status:

    Fixed

    Severity:

    Serious 2

    Product:

    Cisco Telepresence System Integrator C series

    Support requests:

    0

    Known affected releases:

    6.2.x

    6.1.1

    Known fixed releases:

    6.3

    6.2.1

  • What is the token Telepresence Server?

    I have a problem when 3 screen point of end (CTS3000, TX9000) call to the server of telepresence.

    Telepresence server have a newspaper "Issue of EDGE (do not attempt negotiation TIP/MUX (insufficient tokens specified)"

    What is telepresence Server chips?

    Hello

    In short, the chips are what the telepresence server use to become more granular with use of the licenses of the screen - screen Licenses amounted to a certain number of chips the GST follows in-house - and different combinations of resolution, number of screens and audio type out the chips.

    This is how the TPS breaks down screen Licenses into halves and the wings as you see in the capacity table GST Release notes Conference - see page 18 of the following link:

    http://www.Cisco.com/c/dam/en/us/TD/docs/Telepresence/infrastructure/TS/...

    -Jonathan

  • 8710 GST MSE and MSE 8510 blade clustering

    These can simple questions, but I can't seem to find clear answers to these questions. You can cluster telepresence MCU MSE 8510 blade with GST MSE 8710 blades? And if yes, what version of the software do I need to have each blade running? I'm looking to upgrade our MCU at GST and I want to just make sure I have all the info I need. Thank you.

    Hello Eddie,

    You can only cluster the same blades.  Example, MCU with other 8510 8510 s up to 3 blades and GST 8710 with other 8710 s up to 4 blades.  The exception to this rule is if you are migrating your MCU 8510 to GST blades by installing the MCU to the GST software on the 8510, see Running_TS_Software_on_MCU_MSE8510 on how to do this, so these blades MCU 8510 now becomes and should then be treated as GST 8710 blades.

    All blades that should be included in a cluster must be running the same version of the software.

  • Telepresence Server / conductor

    I have a question about setting up locations and licenses on telepresence Server/conductor.

    In the lab guide, you can create a site with AD Hoc and conferences go to one location. This require two licenses of location?

    So you must put in place an MCU on telepresence BLAH ad hoc calls?  I use the telepresence server and conductor on VMware. It is connected to an IX5000.  Video calls go work with the three end points... but I can't have special video calls to work and that's really the question. I suspect that it's because I have only one license and the only defined place ad - hoc and configuration of Rendezvous.

    When I try and add the third endpoint video none of the video is active and the conductor was not aware of any current conference.

    Hope make sense

    Hello

    The ix5000 works in the same way that the CTS and make endpoints TX, she doesn't have the ability to promote a conference for a multimedia resource with a MRGL, only to make an audio call only and it fill in the call or the Conference on what it is. If you try to use it on a video endpoint it will join an audio only.

    An another endpoint that supports ad-hoc escalation as endpoints software TC can make climbing to the multimedia resource (conductor in this case) and bring the ix5000 to a conference.

    -Jonathan

  • Server VCenter 4 and license

    Hi all

    I installed a new VCenter4 that will replace the current VC 2.5.

    The problem I have is that I still have a few hosts version 3.02 and 3.5, I guess I need to have a license server as well to them.

    The question is: How can I move the license from the former vcenter server to the new?

    I have problems with my existing hosts by adding them to the new VCenter v4?

    Thanks in advance.

    Daniele

    Hello.

    The migration of the license server is covered in the Upgrade Guide, and it's a fairly simple process.  There has been problems reported with the help of the standalone license server on Windows 2008 (one download), then you might want to install the media U6 vCenter 2.5 license server if you are using Windows 2008.

    Good luck!

  • Media Port Mode on a MSE 8510

    Hello

    I would like a confirmation, currently we have a blade in our MSE 8510 and the Media Port is set to HD.

    • This means that we have 20 HD video Ports available (up to 20 endpoints will be able to connect)
    • We have also 20 dedicated ports for streaming.
    • Finally, we have 20 additional voice Ports.

    The problem is that we have a meeting that it will take 26 video Ports, if I put it in the SD, we have about 40 SD video Ports. But no content or audio ports.

    Will be what this means if 26 end points to connect I have 14 left ports and ports audio and content will begin to use my video ports?

    I'd connect 26 people on my MSE 8510, with about 10 people connecting via audio and all end points will receive the content.

    Please see attached picture.

    Yes, if you share your content, will consume you a port video, same thing for one participant audio that connects to the Conference.

  • Telepresence server, control assets drops Conference after 30 seconds

    Much of community support.

    I have the following Setup:

    10.5 (1) version CUCM

    Conductor of telepresence Version XC2.3

    Telepresence Virtual Server Version: 4.0 (2.8)

    EX60 TC 7.1.4

    Cisco 9971, Firmware 1.0000 SR1

    Some other phones (7962, 6941)

    All the end points are saved to CUCM.

    When I do a conference appointment without active active control, everything works fine.

    When I activate the active control (according to ActiveControlDeploymentGuideR3.pdf) the Conference ends after 30 seconds.

    the Conference ends even if I have only one participant at the Conference and any of the phones that I use.

    In CUCM, I configured the relevant parameter in the SIP profile (according to ActiveControlDeploymentGuideR3.pdf)

    on the EX60 I use Active Control, so I see the list of participants and I am able to change the layout of the Conference within these 30 seconds.

    any ideas why this happens?

    the journal of the conductor shows nothing statement

    the telepresence server log looks like this:

    327 14:17:09.170 APP Info Conference "8080.MeetMe_mtg' created
    328 14:17:09.264 SIP Info Incoming call on 192.168.33.xxx:37124
    329 14:17:09.264 APP Info "' Call 24: incoming new SIP call of '[email protected] / * /"
    330 14:17:09.379 APP Info Call 24: 'Buero_EX60_Test' has now joined Conference "8080.MeetMe_mtg".
    331 14:17:09.386 IX Info Call 24: no encrypted connection to 192.168.xx.xx:31135 for protocols: ping, xccp
    332 14:17:09.814 CMGR Info Call 24: ActiveControl negotiated
    333 14:17:46.736 SIP Error Call 24: end of appeal because INVITE it transaction timeout
    334 14:17:46.736 CMGR Info Call 24: disconnection, '[email protected] / * /"-timeout.
    335 14:17:46.736 APP Info Call 24: shoot call them "Buero_EX60_Test" - destroy at request end. timeout
    336 14:17:46.736 SIP Error Call 24: BYE transaction failed because the network error
    337 14:17:46.740 SIP Warning Cannot determine the destination for the incoming message transaction
    338 14:17:46.741 SIP Warning Request received from out-of-call
    339 14:17:48.989 APP Info Conference "8080.MeetMe_mtg": deleted via API (not of participants)

    Journal of the conductor, it seems that CUCM closes the connection to RE-INVITE during the transition between the lobby.

    There are several possible reasons, but the best way to determine "why" would be to open a track on CUCM.  More precisely a SDI/SDL (are later versions of CUCM SDL only) track on the CUCM 10.0.2.52 node.  Search for RE-INVITE him entering the IP phone and examine the lines of nearby log for some reason why.

    Alternatively, you can try a few other things:

    #1: Look in Service CUCM settings in the editor, then Cisco Call MAnager to the advanced parameter 'Maximum incoming message size' (there is an Advanced button, you must click above to expose this setting).  If you upgraded your CUCM from an earlier version, this value may need door to 11000 to manage RE-INVITE him to the conductor.

    #2: try disabling the Protocol iX on the SIP, conductor profile and the alias of the meeting of the conductor.

    MP.

Maybe you are looking for