3300: IP 5550 Console/Keypad - out of service?

[pichels]

Hi,

We tried changing the network configuration of the 3300 by just one subnet.

Example:
We are still on VLAN1.
We "were" using 203.57.229.X.
Changed to 203.57.228.X

And after a 3300 reboot - we could not see the IP console.
Although the console could pickup a DHCP address and showed it came from the e2t Switch(3300) and and the tech's laptop also was picking up DHCP as well.
Of course - we could ping the 3300 from the IP console PC.

We also changed the IPPBX??? variables in the SystemSettings.cfg in config dir for the IP console to the correct 3300 IP address and then back to the original again.

Appeared that the keypad was at fault - it had a "red" light indicator lit as if it was disconnected or not talking to the 3300?

I am not very familiar with the 5550 keypad.
But, there is a passthru Ethernet cable that the PC connects thru it and why does the PC seem to talk to the 3300 and we can get into the Web Admin Gui as well?

We even tried an "IP LOAD 2<device ID> and that did not seem to work.
We powered off the keypad and rebooted the IP Console PC many times.

And so after we changed all the System Config and DHCP config info in the forms back to the original values under System configuration - we still "have" an issue with the Keypad or IP console and the 3300 still does "not" see it?

I am not sure what went wrong?
Any ideas or need more details?
Please let me know.

Thx. for any help.

-SP

 

[kwbMitel]

Remove as many variables as possible before assuming the keypad is at fault.

I would start by plugging it into the same subnet as the controller to see if it can register from there.

Also, did you remember to reprogram the Static address for the console in the DHCP settings?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[pichels]

Hi KwbMitel!

We are on the same Vlan but will plug into the switch network.

We have a hub hanging off the port off the switch.

However, we ran a export of all DHCP settings and are not sure what you mean by the last statement - Static Address for Console in DHCP settings?

Thanks much.

-SP

 

[tlpeter]

The ipconsole has a static ip configured in the dhcp scope



ACSS - SME (IP Office)
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[pichels]

Hi tlpeter,

Where is the the DHCP Scope?

Under DHCP-> DHCP Options?

Sorry we are very literal here - just trying to find the right form and sub-forms.

Thanks!

-SP

 

[kwbMitel]

OK Literal it is.

From the Help Files: If the 3300 ICP is part of a cluster, all IP Consoles must be assigned a Static IP Address.

This may not apply in your case.

If it does, the form would be: DHCP Static IP

There may also be DHCP options setup specific to the Static IP such as Gateway and VLAN

Here's a thought, Plug a phone into the jack that the console is using and observe the boot sequence. This might tell you where things are wrong.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[pichels]

Hi KwbMitel,

Do you sleep? <grin>

Thanks for responding - guess what we found out?

Bad cabling.

I can't figure out why/how the PC connected to the 3300 thru a mile of Ethernet can function properly?

And yet the keypad had the red Light indicator and is a pass thru for the same cabling as the PC - could not!?!

Suppose 1 wire of the 2 pairs(4) in the Cat 5 is used by the keypad?
I still don't get it...

Any ideas?

I appreciate your quick responses guys!
Kudos to the experts here.

-SP

 

[kwbMitel]

I've seen cables work for PC's for DHCP and not work for phones. Can't offer a reason.

I still recommend you move the keypad closer to the source or plug in a phone to observe the boot sequence. Either or both will yield useful info.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[kwbMitel]

Oh, and as for the sleeping, the time stamp on the post is GMT and I'm currently working on PST (-8)

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[kwbMitel]

Actually the timestamp is not GMT afte all but it is later than my current timezone.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[pichels]

Thanks - We did move the keypad and console closer - plugged right into the 3300 switch.
That is how we found out.

I had setup a configuration that had the 3300 and keypad plugging into a Cisco 3750 switch and the 3300 into a switch and meeting in the middle.

Now I ran the cable straight thru to avoid any issues.
We still had a bad cable up front by the receptionist...

-SP