UC540 - Email Notification troubleshooting

[dlpoloway]

Hello,

I recently completed some network changes at our office and would like to get the Email Notifications working on our UC540.  I was going to call TAC but then read the this unit has reached end of life for support..  So I'm hoping there are some guru's out there that can send me some advice.

Our network

ISP MODEM / ROUTER / DHCP / DNS @ 192.168.1.1

UC540

WAN - FastEthernet0/0  - Static 192.168.1.2

Vlan1  (Data) 192.168.0.1

Vlan100 (Voice) 10.1.1.1

CUE - Loopback0 - 10.1.10.2

So I think my issue is an easy one.  

CUE Routing to FastEthernet0/0 or 192.168.1.1

Logging into the UC540 and pinging "aspmx.l.google.com" from command line works.

When I login to  service-module integrated-Service-Engine 0/0 session

And try to ping  Restricted Gmail SMTP server @ "aspmx.l.google.com"  it fails

and as expected the notification trace failed with "Unknown smtp host"

I'm a novice at routing and have tried static routes that I think should work but no joy.

Any suggestions on routes and steps? 

I mainly use the CCA but can get around CLI as long as the steps are clear.

[Brandon Buffin]

Sounds like CUE does not have a DNS server. From the CUE CLI you can configure with the command "ip name-server x.x.x.x".

Brandon

[dlpoloway]

Thanks Brandon,

This may be part of it but I also can't ping IPv4 addresses on the WAN interface.

Tried a NAS box and one other PC @ 192.168.1.7 / 192.168.1.110 and both timed out.

I'm struggling a bit understanding the command hierarchy at the different levels but will share what I can determine.

The main unit:

UC_540#show ip name-server
192.168.1.1

Correct

At the service engine I can't figure out how to display the name server but the routes are:

se-10-1-10-1# show ip route
Main Routing Table:
DEST        GATE          MASK                     IFACE
10.1.10.0   0.0.0.0        255.255.255.252     eth0
0.0.0.0       10.1.10.2    0.0.0.0                     eth0

Darcy

[Brandon Buffin]

Is 192.168.1.1 the default gateway for your network? Does this device have a route for 10.1.x.x pointing to 192.168.1.2? It sounds like the rest of your network does not know how to get to 10.1.x.x. Another way to approach this would be to make the data VLAN of the UC540 match the rest of your network. For example assign the data VLAN 192.168.1.2. This would avoid some issues with using the WAN port (NAT, etc.) since it appears that another device on the network is performing these WAN functions.

Brandon