Warning in VCS and TMS (inherited from TMS Agent mode)

Similar Questions

• BGP announcement: How do I remove the attributes "next hop" and "metrics" inherited from OSPF?

  Hello

  I use a router THAT WAN Cisco ASR1001 connected via BGP AS65075 with our ISP.

  This router is connected through OSPF with our Cisco 7206VXR/NPE-G2 firewall.

  Topology:

  ISP <- bgp="" -="">RT 1001 <- ospf="" -="">FW 7206 <->LAN

  On the WAN router, static routes are set to null0 to always announce our class C networks.

  Route IP 192.168.10.0 255.255.255.0 Null0 250

  ...

  Network guidelines are placed in our BGP configuration:

  router bgp 65075

  The log-neighbor BGP-changes

  neighbor EBGP-PEER-IPv4-peer group

  EBGP-PEER-IPv4 neighbor fall-over bfd

  neighbour 192.168.88.138 distance - as 65200

  192.168.88.138 a neighbor EBGP peers PEERS-IPv4

  192.168.88.138 ISP IPv4 neighbor description

  next password 192.168.88.138 7 unknown

  !

  ipv4 address family

  ...

  network 192.168.10.0

  ...

  a neighbor EBGP-PEER-IPv4 soft-reconfiguration inbound

  EBGP-PEER-IPv4 neighbor distribute-list prefix-v4 on

  an EBGP-PEER-IPv4 neighbor prefix-maximum 100

  neighbor EBGP-PEER-IPv4-1 filter list out

  neighbor 192.168.88.138 activate

  neighbor 192.168.88.138 filter-list 2

  output-address-family

  A part of these networs are also learned through OSPF. If these routes are present in the routing table:

  RT-01 #sh ro ip 192.168.10.0

  Routing for 192.168.10.0/24 entry

  Known via "ospf 1", distance 110, metric 20, type extern 2, metric 1 forward

  Published by bgp 65075

  Last update to 192.168.0.79 on Port - channel1.28, 7w0d there is

  Routing descriptor blocks:

  * 192.168.0.79, from 192.168.0.71, 7w0d there is, through Port - channel1.28

  See metric: 20, number of share of traffic is 1

  Because these roads are active in the rounting table. Announcing BGP based on his and attributes "next hop" and "metric" are inherited from OSPF:

  RT-01 #sh ip bgp neighbors 192.168.88.138 announced-routes

  ...

  Network Next Hop path metrics LocPrf weight

  ...

  * > 192.168.10.0 192.168.0.79 20 32768 I

  ...

  Is it possible to remove the legacy of OSPF into BGP attributes?

  How to set the "next hop" to the value 0.0.0.0 and "metric" to 0?

  Thank you

  Best regards

  Jérôme

  Hello Berthier,

  NEXT_HOP is a hill & attribute mandatory path including the eBGP value is the IP address of the BGP peer (specified in the neighbor's remote control) where the router learns the prefix. Thus, your peers (eBGP) will still see the IP 192.168.88.138 in your BGP Next Hop as updates. I agree you the output of the command ' sh ip bgp neighbors 192.168.88.138 roads announced "can be confusing, but not worried about it.

  Metric 20 is cause of path must be acquired by OSPF. Copy in default atributte MED BGP metric. So I see that you have only a peer is very important change this value because MED is not transitive, if this value is not propagated by other ACE access your provider. Anyway, if you want to change, you must:

  1. create a list of prefixes with one or more prefixes that you want to "reset" the MED value:

  list of prefixes prefix-to-reset-MED seq 5 permit 192.168.10.0/24

  list of prefixes prefix-to-reset-MED seq 10 permit X.X.X

  2. create a roadmap

  allowed to reset - MED card route 5

  match of prefix-to-reset-MED IP prefix-list

  the metric value 0

  road map provided to zero-MED allowed 10

  !

  The last road map is necessary to ensure that the rest of the prefixes are sent.

  3. apply the road map

  a neighbor EBGP-PEER-IPv4-roadmap given to zero-MED on

  Concerning

• TMS, VCS and Jabbber "impossible to connect to the TMS on the VCS agent".

  Dear,

  We have Cisco TMS, VCSC and jabber deployment, we did before commissioning the VCSC and TMS and jabber worked well, but after the upgrade the VCSC v7.2 to jabber version 8.2 has stopped working and I can not connect more and when I go to the TMS and connect to the VCS I get "unable to connect to the TMS on the VCS agent" Please notify

  What TMS version do you use?  And you are using Extension of provisioning of the TMS (TMSPE)?

  Looks like you are using TMS Agent Legacy, which has been supported in VCS X7.2 and has since been removed from X8.1.  You will need to migrate to TMSPE and very probably upgrade your server TMS as well if you do not meet the minimum version.

  Cisco TMSPE 1.0 Deployment Guide

  Here's the guide deployment for TMSPE 1.0, there are newer versions, but 1.0 is one that you want to migrate from legacy Agent TMS.  Once installed and migrate your data, you can then go to the most recent version, which is 1.4 (see below).

  Cisco TMSPE with VCS 1.4 Deployment Guide

• Do we need to purchase the license to upgrade the VCS, VCSe and TMS?

  Hello

  We need to get a new license when upgraded version of VCS, VCSe and TMS?

  Hi Kelvin,

  xxx. OVA files are package files to deploy the VCS on virtualize platforms.

  Release key are required to upgrade the VCS for major updates. for p. ex. upgrade of x 6 x 7 software version worm.

  However for improvements minor as x7.2 to x7.2.2 these are the released hotfix version or bux fixes release and you don't need a license for this upgrade.

  in any case if you your devices are less covered by valid contract you can get the license key anytime just contact cisco license team on "[email protected] / * /" and they should be able to provide the necessary license.

  Rgds

  Alok

• Removing VCS of TMS and TMSPE migration problem

  We prepare to start using TMSPE, however it must first disable replication on all VCS via MSD MSD Agent.  There is a VCS that have failed has been deleted afterwards, but we cannot delete TMS because TMS Agent replication is enabled.  We cannot have the Agent MSDS tab to disable the replication because the VCS is offline (i.e. it was removed) - it just goes to the 'Connection' tab whenever I try.

  So, how can we migrate to TMSPE if TMS don't delete us the VCS in offline mode or at least turn Replication Agent MSDS for it?

  Hey Nick

  Try to run this SQL query:

  USE TMSNG

  UPDATE field_SystemField SET BolValue = 0 WHERE field_Field_Id = 1072

  UPDATE Cluster SET EnforceTMSAgentDataReplication = 0

  This should clear the replication on all VCs added to the TMS (even the zombie ones like the one you have), once it is executed, you can try to purge the VCS.

  / Magnus

• Integration of CUCM, CTS and TMS

  We currently have a 8.6/CTS-Man/CTMS CUCM environment for our telepresence system.  All systems are CTS only.  Currently, connect us to a Tandberg system via Server CUBE/VCS/telepresence.

  We are looking at the possibility of integrating the two systems together.  This would involve decommissioning our CTS-man and using their existing planning TMS.  Networks would be open to each other so that they didn't cross highway of CUBE/VCS.

  Can someone tell me please to some documents on the integration of the TMS with our CUCM for planning?

  Furthermore, is it possible to have a single MSDS to perform the planning on the two CUCM registered CTS and saved VCS Tandberg endpoints end points, as well as to perform planning tasks for Community trade marks and MSE8000/telepresence Server?

  Thank you

  Hi Nick

  It is a very good question, and the bellows are drawn from the responses on the features that each product can provide you (CTS - Man and TMS) however as we know the TP Cisco world is changing and moving quickly if the bellows has been updated / changed and can someone comment on this topic will be great for us

  Meetings 1-booking

  TMS:

  -adhoc and meetings,

  -3rd-party endpoints reservation.

  -Ms Exchange, Domino, and API

  CTS - Man:

  -mainly used for endpoints STC booking

  -You can book and include cisco webex

  -Ms Exchange, domino and API

  2 features

  TMS:

  -End suppliers Multi points

  -Telephone directories

  -planning of conf

  -management endpoints (monitoring, Reporting, strong alerts... etc)

  -commissioning

  -integration with 3rd party such as Ms exchange

  -"There is no button to push" for the endpoints of CTS (you can add CTS alis for TMS rooms and book it or add the E164 of the external endpoint CTS as a participant and not these means are a button to push the meeting!

  CTS-MAN

  -integration of calendar

  -Midware between CTS, CUCM system and society of calendaring system

  -provide 'a button to push' scheduled meetings

  -provide interoperability simplified such planning via Cisco MXE

  -Live English option and CTMS geographical selection

  for each of them can provide you with options and features and its depends on the needs of your business, you could keep both or just go with one, if you have endpoints of VCS I would say for sure to the TMS

  HTH

  Marwan

• VCS VCS - E, TMS, TMSPE, Jabber/Movi authentication

  Just trying to figure the best way to approach this.

  I have read the documentation and the best approach seems to get to the VCS VCS-E to Active Directory and the synchronization of the TMS with AD for user account creation. This would avoid the need to records movi proxy for control of VCS and would ensure that all (SIP and H323) registration for the VCS-E would be authenticated.

  I don't think that my client will allow the VCS-E talk to AD.

  So, what are my options?

  If I SIP proxy of VCS-E records the VCS control, how are they managing H323? I don't want just any point endpoint h323 register with the VCS-E. I need to authenticate them. The customer has exernal h323 endpoints that they would like to sign up for VCS - E. I know I could put registration rules to restrict only some URI SIP, H323 IDs etc but it's really just security by obscurity.

  The local on VCS and VCS-E database can be used for authentication Movi/SIP and H323 records? I know that I would have to duplicate accounts and passwords on both.

  What books commissioning and address through registration to the VCS-E? Would it still work?

  Any suggestions on the best way to handle this in the safest way possible without breaking things?

  If I go with the control of VCS and VCS Expressway with authentication Active Directory (directly) on the control method of the VCS as described in the guide of authentication devices, I'm looking for the reality that I will not be able to restrict who can register for the VCS-E? At this time should I just seek to restrict the search for rules to only authenticated users?

  Thank you

  Jon

  Hey Jon,

  MOVI/Jabber you won't have to worry about authenticating H323. With your endpoints however you can just use the database local to authenticate or H350 (more can be read about in the guide of the Provisioning device referred to as Tomo). You can create a different generic for all your endpoints (less secure if which is discovered). But by combining this feature with a political appeal will ensure better security.

  I highly doubt that your client will allow you to leave the talk VCSE in AD. For movi/jabber users, you can create another subfield and use a regex pattern for point movi/jabber users to authenticate it as. * (\.movi)@domain.com. In addition, you can refer to this fragment and others have used in the past.

  In a secure design, the VCS (control and Highway) would require identification for registration information.

  The Control of VCS would have Active Directory Service active and joins the Active Directory domain. For VCS authenticate the credentials of Movi/Jabber on Active Directory before the SUBSCRIPTION for the supply is sent to the service of commissioning, the default Zone would be set to verify the credentials. For requests for SUBSCRIPTION from the highway, the area on the VCS control would also to verify the credentials. It handles authentication for the provision.

  The next part is the record of the Movi/Jabber client. The subzone to which the customer will register must also be set to verify the credentials. Here's everything you need for internal records (registration to the VCS control).

  For the Highway, things get a little more complicated. For commissioning subscription, the SUBSCRIPTION is forwarded to the VCS control. With the area on the VCS game to check the credentials, you're all set. Now on registration to the highway. The subzone to which the customer will register to must be defined to check credentials. From the motorway VCS don't have direct access to Active Directory, we use local credentials on the highway. A set of credentials should be configured in VCS Configuration > authentication > devices > local database. You will create a single name and password all Movi/Jabber clients will use. The end user has NO need to know these credentials. The username and password is provided to the Movi/Jabber client via configuration data it has received. To set up these data, MSDS, you must configure a SIP of authentication user name and password for SIP authentication in the configuration of the commissioning. For these options to be available, you must ensure that you have downloaded the configuration template xml for the Movi/Jabber version you are using. The xml file is included in the zip package full of the client which can be downloaded on www.cisco.com. So, who will be recording from the highway. Now, this creates an interesting situation with VCS control. The internal Movi/Jabber client will receive the same provisioning configuration and will attempt to use those same credentials when you register for the control of VCS. The VCS control is already set to authenticate against Active Directory and Active Directory ONLY registration.

  You will need to create an account in Active Directory corresponding to these credentials. The Active Directory account didn't need special access. It is used only for authentication purposes. A few things to keep in mind: SIP authentication user name and password for SIP authentication are stored in clear text configuration configuration. This means that the data is sent in clear text. To be sure that these data are not compromised on the wire, do not forget that you are using for your communication SIP Movi/Jabber TLS.

  With this directories will always work as jabber should be authenticated in order to receive directories. Your physical endpoint points will work differently with how they receive books and whether or not they are able to communicate with MSDS (unless you choose to configure endpoints also if those you are capable).

  It is in no way the design as safe as possible. It is to you to ensure that your environment is as secure as possible and therefore tested. The best way to fix everything is a well-defined appeal policy designed with your specific needs.

  The foregoing is in no way a recommendation but just a little more information to chew while looking to choose and implement what is best for you.

  Adam

• AD authentication environment VCSe, VCSC and TMS

  Hello

  We have VCSe, VCSC and TMS work with commissioning on the VCSC through TMS.

  VCS, Version 6.1, 13.1 TMS

  Movi (4.3) external Clients have registration with the VCSC. VCSe does proxy registration.

  Users have been configured on the MSDS. There is still no configured AD authentication.

  Everything works fine.

  We now want to configure AD authentication.

  There are several deployments to do, but for me, some of them are not so sure than others.

  I need a top secure deployment.

  I need ideas to make the deployment.

  Thank you

  Martin

  Hi Martin,

  I understand perfectly what you want, but I do not understand why. When you set a directory of provisioning in TMS to be integrated with AD, users are imported automatically according to the 'search string', that you are configuring. But passwords are not imported from AD, basic information only from users are imported. When any user try to connect, TMS challenge for authentication in real time.

  For me it is not a problem, because the MSDS do not save passwords in its own database. Is this a problem for you? Why?

  If you try to do it only because you want to limit which users are allowed to use the customer Movi, if your problem is the following, so you can solve it by using a 'search filter' in the configuration directory configuration, so that you afin que vous serez will be able to import only users who belong to a specific group, for example.

  Please, explain to me why you want to do.

  Paulo Souza

• Conductor XC2.2 and TMS 14.3 automatic connects

  Hello

  I've also seen a topic on current versions of beta XC2.2 conductor and TMS 14.3, so I'll post my question here.

  I use the conductor with VCS, CUCM, MCU 4505 and TS. I am able to create ad hoc via CUCM and VCS and regular calls through TMS conferences.

  If I create a conference with automatic connect and the conductor in the call I can see that the MCU or TS tries to achieve a participant, but not with the URI. To use my email address (findme ID) to call me, but instead, it uses strange URI identifiers: [email protected]/ * /: 5073

  1.1.1.1 is the IP address of the driver. On the front part @ I do not know where it comes from, but it looks like an internal identifier.

  These are the logs of the MCU for a test with a participant conference to be connected automatically:

  13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: "Videokonferenz 101" is 13307 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], numerische Favorites auf ID '88800010 '. 13308 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], pine Favorites auf "114". 13309 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], Gast-PIN options auf "114". 13310 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [101 Videokonferenz], busy 'public '. 13311 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] content mode set to 'convert '. 13312 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] Stummschaltung EIB participation [Audio = deaktiviert] 13313 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] Stummschaltung EIB participation [video = deaktiviert] 13314 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [101 Videokonferenz], Layoutsteuerung uber FECC/DTMF "use FECC and relief to DTMF". 13315 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], maximum Dauer Favorites auf 'permanent '. 13316 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], Ende Favorites auf "kein Enddatum. 13317 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] auto remove time limit set to "600 seconds". 13318 13:38:06 admin API /HTTP/TCP/1.1.1.1:38141 API-Endpunkt-Einstellungen Info: Endpunkt [e922d880ee1854c242ba94e69b113af: [email protected]/ * /: 5073] via API zu Conference "Videokonferenz 101" added 13319 13:38:06 admin API /HTTP/TCP/1.1.1.1:38141 Info API-Endpunkt-Einstellungen: Endpunkt [3805: [email protected]/ * /: 5073] via API Conference "Videokonferenz 101" added zu 13320 13:38:36 API admin /HTTP/TCP/1.1.1.1:38149 Info API-Endpunkt-Einstellungen: Endpunkt [3806: [email protected]/ * /: 5073] via API zu Conference "Videokonferenz 101" added

  Unfortunatetly newspapers are in German, but I think you can see that there are a few strange added URI.

  If I create a conference without a conductor the log shows the URI:

  13386 14:07:14 /HTTP/TCP/172.21.10.12:52001 Info API-Endpunkt-Einstellungen admin API: Endpunkt [Paul Woelfel: [email protected] / * /] via API zu Conference ' 1234 - Videokonferenz 07/08/2013 "added.

  1.1.1.1 is the IP of the conductor (of course not the real IP ;-))

  Someone at - test the latest versions as expirenced this question?

  Hi Paul,.

  You use the conductor and VCS B2BUA deployment? If so, this behavior is correct. MCU must not call endpoint directly, MCU must compose a unique URI of the driver, something like [email protected]/ * /, so Condcutor will take this URI and route the call to VCS replacing this strange URI of the right destination SIP URI according to what you have planned.

  But to make it work, MCU must not be registered for VCS, MCU should only be integrated with driver, without registration, SIP and H323 for VCS.

  Can you confirm what type of deployment you have? What integration between your MCU and conductor?

  Concerning

  Paulo Souza

  Please note the answers and mark it as "answered" as appropriate.

• How to take backup for VCSC, VCSE, MCU and TMS. I'm new in the world of video. A brief step by step would be appreciated

  How to take backup for VCSC, VCSE, MCU and TMS. I'm new in the world of video. A brief step by step would be appreciated.

  You can back up each server by following these steps:

  For VCS, see "Backup and recovery of data from VCS" section in the Cisco VCS Administrator Guide X8.5, page 340.

  For MCU, see "upgrade and save the MCU" section in the Cisco Telepresence MCU series online help 4.5, page 212.

  For MSDS, see back up and restore SQL Server databases you will back up the database of TMS 'tmsng' of the SQL Server itself.  It could either be hosted locally on the TMS server if you have installed TMS with the default settings, or an external user provided SQL server.

• Question about commissioning of the E20s - CUCM and TMS

  If we now run software CUCM 8.6.2 and 4.1 E20.  I played with CUCM and TMS supply by and a few questions.

  It seems that there are some features that can be set via the TMS models that cannot be resolved via CUCM (MTU, custom, etc commands).  Is it possible to apply these settings through TMS while having the unit registered in CUCM?

  Essentially, I want my call recording platform CUCM and control, but want to keep the granularity that TMS offers in terms of commissioning etc..  I expect the same problems with C-series, etc.

  Am I right in saying that, in order to get the E20 to join CUCM, I need to define the external Manager to "CUCM", and thus eliminate any possibility of TMS to manage? Otherwise, what is I could have managed by TMS and then set the SIP of the E20 to point to CUCM via templates in TMS?

  Any tips on that?

  Hello

  Having both TMS and CUCM to manage endpoints is not a good idea (yet). TMS and CUCM will return to each of the other toes with unpredictable results.

  With TMS 13.2, I understand that you should be able to import the CUCM in TMS and then find all systems registered to it and import these into TMS, however in this case TMS plan only systems conferences and will manage them not active (you can see status of the call as well).  13.2 TMS is not yet released, so that's what I said must be in this version.

  So basically now if you use CUCM, use CUCM provisioning and don't use TMS.  We focus on interactions with systems registered with CUCM TMS and it will be more developed on this in the future.  I recommend you check out the TMS13.2 release notes released to see if it is mentioned.

  Thank you

• Import and export directory for CUCM and TMS

  How can I configure TMS and CUCM use of TMS directory for an endpoint registered to CUCM? I've added to TMS but and TMS can shoot CUCM Phonebook, but how does he see the directory for other infrastructure in TMS to fill in the directory of CUCM CUCM?

  tms_not_supported.PNG

  

  If the endpoint of telepresence is running TC7.0 or later, you can configure in CUCM using TMS as a source of spare phone book, there are also TMS 14.4.  Refer to the Administration of the TC on CUCM 10.5.1 endpoints (TC7.2) on page 24 for more information.

• Why are the breakpoints and the page from the master page settings not inherited by all pages?

  Hello

  I've been busy creating a sensitive site with points to stop and a fluid width. Everything works now on my master page. But I found my breakpoints and the parameters of the page were not inherited from my master page for all other pages. To manually create all exactly the same breakpoints would be a lot of work. Can someone help me with the please my problem?

  Kind regards

  Tim

  When you apply a master page with breakpoints to another page, the breakpoints are displayed as markers of white triangle. All you need to do is add your breakpoints in the same place as markers.

  The reasoning behind this is likely that sometimes the content of the page should be changed more than the constant elements in the master.

  I hope this helps.

  David

  Creative muse

• Error TMS agent Portal

  Hi all

  I have exactly the same problem as described in this discussion: tmspe-tms-aent-page.  If I try to connect to http://TMS/tmsagent/tmsportal (or https).  I get the error message "an error has occurred. ' Reload the page and try again.  See the attached file.

  With TMS 14.6.1 and TMSPE 1.4 installed on Windows 2008 R2 server standard edition server.

  TMS is running for a couple of months with this version very well. Recently, I've implemented CMR after conductor and new mm410v has been added to you video below. A model was created and applied to a group of users. This group has the authorization requested to the meeting of the book.

  I got the same error message when I click on the button "Edit CMR in the portal".

  If I try as http://tmsipaddress/api/v0/version suggested link I get a page not found error.

  Default Web site also has an HTTPS binding.

  I'm stuck because I am not able to solve problems more.

  Cisco TAC after webex session ask me follow up with Microsoft!

  Any suggestion or advice is welcome.

  Thanks in advance.

  Ahmed

  TMSPE working before trying to add CMR, or is this a new installation?

  Java has been updated recently? TMSPE 1.4 requires Java 7 update 51, I know that's not far from the version you use, but it is worth it to try the version that offers the deployment guide.

  It could also be that Windows is missing a required service pack, see tms-agent-ui - error message.

• Why is the 200 GB $44.99 a plan inherited from year more expensive than the monthly plan the new 200 GB $2.99 a month plan ($35,88) - what's the catch here?

  Why is the 200 GB $44.99 a plan inherited from year more expensive than the monthly plan the new 200 GB $2.99 a month plan ($35,88) - what's the catch here? is there a reason why the new plan is less expensive? they are trying to phase out the inheritance plan? is there a difference in storage w the new plan and the legacy for the difference in price (of the problems of the different devices w - computer laptop Mac, iPhone, iPad?)

  The only difference is that it is charged monthly.

  As shown in the following, you may be able to increase your storage space or reduce your costs by opting for the monthly package. Annual storage iCloud - Apple Support plans