IP Office and Application Server VLAN 1

[Gartech]

Looking for any suggestions to help troubleshoot a routing issue-

After a power loss this weekend, our workstations on the data VLAN (10.64.32.0/24) cannot PING or connect to the IP Office Manager which is on a 10.64.16.024 network.

Vendor is unable to assist us today.

I am looking at any possible router or switch configuration that may not have been saved after the installation.

Does the IP Office have in its configuration a gateway IP address so it can communicate with other sub-nets?

 

[Pepp77]

By default the IPO should have

IP = 0.0.0.0
SN = 0.0.0.0
GW = 10.64.16.1

Or equivalent

| ACSS SME |

 

[gknight1]

as long as there are routes that look something similar to this, then the IPO should be good.

10.64.32.0
255.255.255.0
10.64.x.x - where x= the gateway of the vlan the IPO is on that is used to route to the data vlan

and

10.64.16.0
255.255.255.0
10.64.x.x - where x= the gateway of the vlan the IPO is on

 

[Gartech]

I can ping the GW (10.64.16.1) from my workstation but I am curious now what interface that is actually.

I see it named on my switch -

ip dhcp pool Voice
network 10.64.16.0 255.255.255.0
dns-server 10.64.32.15 10.1.1.250
default-router 10.64.16.1
option 242 ascii MCIPADD=10.64.16.5,10.50.2.15,MCPORT=1719,HTTPSRVR=10.64.16.5

 

[gknight1]

it is possible that there is another gateway IP for the data vlan, it all depends on how everything is setup.

 

[Gartech]

Our gateway for data vlan has a named interface in the configuration -

interface GigabitEthernet0/0.5
encapsulation dot1Q 5
ip address 10.64.16.1 255.255.255.0

 

[gknight1]

up top you said your data vlan was 10.64.32.x and your voice vlan was 10.64.16.x.

 

[Gartech]

That is correct.
The IP Office IP is 10.64 16.5 and the Avaya application server (One X Portal) is 10.64.16.6

Neither of these now respond to PING requests from the 10.64.32.0 network.

The phones register, thankfully.

 

[gknight1]

that is probably because the phones are on the voice vlan, so there is now routing involved...

try to ping from the 10.64.16.5 IPO to the 10.64.16.1 gateway device and see if you get any response
try to ping from the 10.64.16.5 IPO to a machine on the data vlan and see if you get any response, if this fails...
try to ping from the 10.64.16.1 gateway device to a machine on the data vlan and see if you get any response

 

[Gartech]

try to ping from the 10.64.16.5 IPO to the 10.64.16.1 gateway device \to a machine on the data vlan and see if you get any response, if this fails...

My IP Office Manager will not launch - cannot find the IPO in the discovery?​

try to ping from the 10.64.16.1 gateway device to a machine on the data vlan and see if you get any response

Not sure where the 10.64.16.1 gateway device is​

 

[gknight1]

sounds like you need a network team to help

 

[gknight1]

or statically address yourself on the voice vlan and go from there. FYI, you ping from System Status, not Manager

 

[snowman50]

Ipo manager discovery won't work on different subnets.

When you launch the manager ,open configuration.,
In the discovery tab bottom right, ip offic directly 255.255.255.255 change this to the ipo address and hit refresh a few times.
If there are routes between the vlans then you should see the ipo then.

Although if you can't ping the ipo then this may not work either.

 

[Gartech]

Thanks to everyone who helped with this thread.

Issue was discovered where a switch port mode was not saved in the running config on the switch and it reverted back to access instead of trunk after a power failure.

Once that was corrected the routing returned to normal.