Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - rikko

Pages: [1] 2
1
...Then you have to figure out which co-worker did the upgrade to get access back.

I know who did the upgrade, it's always the same person, but he is not available any more. I suspect he used his root account, much like I'm trying to do with mine.

2
Adding server manager access in the account doesn't automatically allow that username access, they also need to exist as a user in server manager.

You also need to enable the option in "System Properties > System Feature Settings > Shared System Options" for it to give you the option when you login to ESM. Otherwise you need to go to https://{MiVB IP}/server-manager to access it directly.

Hi sarond, thanks for the info. I was looking for something like this, a "simple switch". :)

To give you some context, I'll explain why I'm sure something has been changed (other than the obvious update). I'm far from an expert in Mitel systems, but without a doubt, creating new root user and giving them server manager access never stopped me before. I know this to be a fact, because we have couple of outside users with root privileges, who on occasion access the system remotely. When I go to a new site, I create my own root account, so that I can track the changes made by me vs everyone else.

Edit:"Talking about shared system options, yes server manager access was disabled. Enabling it however, did not allow me to access it. I can see the login screen when I manually point to it (does not appear as a button still), but it does not recognize my user/pass combo. Not the new one, nor the existing ones.
"

Is it possible there's something else I'm missing?

Edit: I guess system took a few minutes to distribute the new setting. I can now access Server Manager. I've also found that root users with Desktop Tool enabled, do not see the Server Manager button.

3
There were no unsuccessful attempts to login...  ;D

I've tested three different root accounts, none have access to Server Manager.

4
Mitel MiVoice Business/MCD/3300 / Server Manager access not available
« on: August 08, 2025, 10:27:46 AM »
Hey guys,

I've been out of office for some time, about half a year, and once I returned I've found that our system has been updated to 9.0.3.15 (we never run latest versions). With it, my root account lost server access, even though it's enabled in User Authorization Profiles.

What am I missing?

5
Mitel MiVoice Business/MCD/3300 / Re: MXe-III performance improvement
« on: October 23, 2024, 11:23:40 AM »
Hey Dutch,

you make valid points, I would have to give it some thought. Though, the direction where my job is heading may not be in line with the proposition. For the time being, I'm in peace with MXe's being turdishly slow.

Thanks for the explanation.

6
Mitel MiVoice Business/MCD/3300 / Re: MXe-III performance improvement
« on: June 25, 2024, 12:57:08 PM »
The only reason there's analogue connectivity is due to back-compatibility with outdated systems (none physically present atm). Each hardware piece in our communication chain supports at least SIP, so that answers that. However, much like in every other large business machine, change is not always welcome, particularly if it involves expenditure of monetary resources. :)

Appreciate your response.

7
True, manbusy didn't help, trying was good for practice though. :)

However, what did help, was restarting the service on the equipment connected to Module #2, Port #1 (not in alarm). And just like that, all digital link alarms have cleared (even though physically not connected to this piece of equipment). I mean, wtf...  :o

Thank you all for your inputs.

8
Cheers ZuluAlpha, I thought it'll be a rabbit hole to go down through...  ;D
I'll await for this other system vendor to give some feedback, and then go from there.

In the interim, question for all, can manbusy be applied to digital links?

9
Yeah, tried that first, refused to clear the type. The guy who I replaced mentioned that he faced this issue earlier in the year, and it was cleared by the technician who maintains the system which MXe connects to, through Module1/Port1.

Reluctantly I said OK, it makes no sense in my mind, but then, it also doesn't make sense that between the two MXe's that have identical physical connections and apparently configuration (from what I gathered), only one reports the fault.

Thanks for the involvement, I'll let you know how it goes.

10
Mitel MiVoice Business/MCD/3300 / Re: MXe-III performance improvement
« on: June 03, 2024, 10:33:09 AM »
Thanks for pitching in. My primary problem with MXe-III is overall response. Like, anything that I do through a web interface, be it accessing Users and Devices, or exporting a form, or generating a backup, you name it, it takes what subjectively forever in comparison with two virtual nodes in the system. And this is the same with both of my MXe's. Unfortunately I do have to keep them, as they're sort of acting like a gateway to satellite telephones, which currently require a plain analogue connection. In the future I guess none of that stuff will be needed, but who's gonna wait until then. :)

Ok, good to know it already has a Gb LAN. So then there's no means in increasing processing power (other than virtualization)?

11
Mitel MiVoice Business/MCD/3300 / MXe-III performance improvement
« on: June 01, 2024, 03:07:48 AM »
Hi All,

I find my MXe-III units to be rather slow. Did anyone have this impression, and did you try to improve the response?
I'm thinking about the things such as the RAM increase, ethernet interface replacement with Gb units (not sure if it's even possible), SSD/SAS installation...

Cheers

12
It can't be seen from the attached screenshots, this one is reporting link alarms.

13
I definitely did, and it the config is the same, yet no alarm. I'm scratching my head here...

14
Thanks for the explanation. I'll dig around it a bit.

What additionally confuses me is that my other MXe-III unit does not report the same fault, even though they have same physical connections and same port/framer configuration.  :o

15
Hi All,

I have a MXe-III unit with two modules, both Dual Framers. I have both modules connected to other equipment via port #1 only, port #2 being unoccupied. For some reason unknown, after the last system restart, I now have a Digital Link error on port #2 of module #1 (also indicated by a red lit LED). Module #2 port #2 is not reporting any faults. It is my assumption that system pulled an old configuration from not sure where, and is now alarming due to port being down. If that's the case, I wonder why the previous restart did not cause the same issue (some one month prior).

Question 1: If for testing purposes I disable module #1, by removing it's definition under Modules/Controller Module Configuration menu, will that permanently remove all configuration items for this module? Meaning, after I re-establish the configuration for the module, will protocols and individual port settings be pulled out from records, or would I have to re-configure them manually? In essence, is the port configuration lost with removing the module logically?

Question 2: How to get on about deactivating port #2 on module #1? I'm spinning in circles a little bit, to be honest. It's seems like an over-complicated method to define configuration for a port, to me, but let's attribute that to my personality.  ;D

Thanking you all in advance

Pages: [1] 2