stubborne

Moved a medpro to a new EPN/subnet. CANNOT get it on the network. I've double/tripled checked configs and ethernet switch settings. Has anyone experienced problems moving a medpro from one subnet to another? I'm wondering if it's configs are scrambled and for some reason won't accept the new configs

cha node-name ip (new name, with new IP address)
ch ip-interfac (new name, with gateway and subnet)
ch ethernet (set lan speed/duplex)

Those are the 3 commands I've been using. I'm not missing anything, am I?

__________________
Stu

dherve

Do you check on your switch?

Do you have level 1 on the switch?

Is there any mismatch speed/duplex between the change ethernet and the port of the switch?

When you did a list con board aabcc

PBXtech.info

 

stubborne

All looks fine. The board is there with no errors. No mismatch issues, the MAC/IP/Port show up in the arp table on the lan switch. OSI 1 and 2 look fine, it's 3 that's giving me fits. That board won't route traffic.

__________________
Stu

dherve

when you did a ping command of your medpro the result is ....

ten8ous1

IO know this sounds trivial and basic, but have you completely removed the translations for the board and started from scratch. One of my techs was in the same situation and it was as simple as completely removong the translations, not just disabling the ip interface and services.

Hope this helps.

mrgold

I am in-line with the previous post...do you resolve the issue? If so, how?

PBXtech.info

 

stubborne

Not resolved yet. The mud has gotten deeper. When I added this EPN, a shadow EPN was created as well. This has happened twice. What I mean is, I added cabinet 6, cabinet 2 was created too. Only, you can't see cabinet 2 in the 'list cabinet' command. The only way you can see it is by directly accessing by 'list conf car 2a'. 'lis conf all' doesn't show it either. I removed all the translations for cabinet 6 (2 disappeared), created a new EPN as cabinet 2. This time cabinet 6 was created as the shadow. Definately some corruption going on here. The issue has been escalated up the tier ladder, not sure where it resides today. Medpro is the only thing that doesn't work and I'm assuming because the board exists in the shadow config with no ip configurations. Clan works but it has an explicit port assigned in the data module for ethernet. All other telco - stations, trunks, etc - work fine. Again, explicit port assignments. CM 1.3

__________________
Stu

jsena

are you plugging into the same port on your LAN switch? If you changed the port on the switch, you need to program the new port the same as the old.

display ip-interface xyy
where xyy is the cab and port of the medpro
VLAN:

if the VLAN is 'n' then you are not using trunking on the data port, you'll need
"switchport access VLAN xx" on your LAN switch (assuming cisco IOS-based switch here)
where xx is the VLAN you want the medpro on.

if the VLAN is a number, you are using trunking on the data port. you'll need
"switchport mode trunk" on the LAN switch

If the PBX is expecting trunking and the LAN switch isn't or vice versa, you won't get talkpath.

stubborne

All is set as such. Cisco switchport access mode with proper vlan assigned (remember clan is working fine and configs are duplicated except for the ip address).

Avaya fixed the shadow cabinet issue. add cabinet 6 (shadow), then configuring some cards, then deleting cabinet 6.

Clan 2a09 10.x.x.190, Medpro 2a10 10.x.x.191
ping ip address 10.x.x.191 board 2a09 pass
ping ip address 10.x.x.190 board 2a09 pass
ping ip address 10.x.x.190 board 2a10 pass
ping ip address 10.x.x.191 board 2a10 fail
Medpro passes the ping test to clan, but fails ping test to itself and can't be pinged from any other network device, switch included. This is the 2nd board I've put in. I'm beginning to wonder if it's not the adaptor or some other hardware inbetween.

__________________
Stu

mrgold

hahahaha....vlans...

Have you tried moving one to another carrier? And yeah, those adapters do require the occasional replacement. What happens if you reverse the boards (after being completely removed, of course...)
I am curious, did Avaya say how the shadow cab was created. Did one of the boards still have an old config?

mrgold

Oh...what happens if you ping .191 with the board removed?

stubborne

Nope, chalked up to corruption. If the board is removed, all fail.

__________________
Stu