Question on the Service-module IP address

I have what I hope is a simple question. I am in the process of configuring a UC560 and a UC540 for a 2-site company. Most of the administration will be done from site 1, which means I'll have to connect to site 2 using a VPN.

My question is, in order for CCA to work, does the service-module IP address have to be changed from its default 10.1.10.1 on both units? I was planning on making site 1 10.1.10.1 and site 2 10.1.20.1.

Does this fit in with best practice, or is this just over complicating things?

Share:

Replies

Your assumption is correct, changing it to 10.1.20.1 is perfectly fine, it is consistent too

Just on a side note, please make sure that CCA correctly modifies the loopback address as well, I have seen it miss this from time-to-time so just have a quick peek on the UC-540 that it does this.... Although you don't have to worry about this on the UC-560 as it uses VLAN-90 instead of a loopback

Thank you for your help. Not to complicate things, but where in CCA Would I go to change this? I see that there are some "web sites" that are hosted in the UC on on the IP address of the service module (10.1.10.1), as well as some ACL entries. Is there a clean way to change this in CCA without going through and making the changes with CLI?

Well my memory is getting bad in my old age (Or so my kids tell me ) but I believe this to be in the routing section, if you look in the navigation menu you should see it there (On the left hand side) and on the UC-560 you will see 3 VLAN's that are configurable, VLAN-1, VLAN-90 & VLAN-100 assuming they all remained as default, however on the UC-540 you will only see 2, VLAN-1 and VLAN-100 as the UC-540 uses loopbacks for the CUE module.

ON the UC-540 you will be changing VLAN-100 to the 10.1.20.X subnet, on the UC-560 it would be VLAN-90 (Well at least I think that's how it goes from memory ) Anyways once you see it, it should be self explanatory I hope

Oh and VLAN100 is the voice VLAN, not the service-module (CUE) IP address on UC540. You can change VLAN100 to your heart's content, however as I said, changing the module IP is not supported (although accomplished easily with some CLI and CUE config changes).

You will need the UC Express certification to get CLI support, which is being retired, not to be replaced, so frankly not sure where a partner is to turn for CLI support now.

You are right, i was mistakenly referring to the UC540, not the UC560.

The support parameters are very cut and dry now, I'm not sure when you last called on them, however there is no escalation path for any CLI, and the new stance is that if the feature does not exist in CCA, you should consider the feature doesn't exist on the platform. I have had this direct from the product and support teams. Also if you make CLI changes, your configuration is unsupported in its entirety.

I am very disappointed with this specifically, as we have been doing this for a long time, since UC520 was launched, and had clients on TAC support without these issues. We often need to use CLI for some of the most basic of features which are lacking in CCA.

What is truly upsetting is that they haven't put key features in CCA, then leave you out in the cold when you return to CLI in desperation. We are now looking at dropping the product entirely.

Couldn't agree more, and glad that it's not just me. You and I both know how powerful this product is, such a shame it is restricted by a weak GUI tool and a sub-standard support structure.

I was told "this is because so many of our partners had problems and lacked the skills required", so it looks like the sales people have won in this instance, and it is now UC for dummies. It used to be you needed some skills to implement and maintain these systems, but it's clear Cisco just want to move more units.

I would happily, however it is being retired and I have a month before the cert is no longer attainable. Not sure I have the time to study up on the 'Cisco way' to do the exams in a month, only to then find the cert will be retired in the short term, not to be replaced by anything.

Thank you everybody for the info. Cisco ended up telling me the same thing. I am curious though, how people manage to get around the situation I am in.

As I've said, there are 2 locations each with a UC500 device. We are going to be doing the majority of the UC administration from one location, so things like going to 10.1.10.1 to upload a prompt, or even creating a user in CCA (Which interacts with CUE) will be challenging for the remote location (since all requests to 10.1.10.1 will go to the local UC).

Although David, I'm not sure you can 'lock yourself out', you can always access the service-module from the IOS using the service-module command which doesn't use IP as it functions like an internal interface.

You could consider doing what I'm doing - change the CUE module IP (a few CME CLI changes plus a few changes in the CUE module config), then change it back if you need support.

There are some good articles on here about it, although the last one I looked at overlooked the CUE side of the configuration which is a critical component, so make sure you do both sides - CME & CUE config changes. I believe there is a good Cisco article on it.