cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1531
Views
0
Helpful
3
Replies

UC320W WAN port unreachable

obencandemir
Level 1
Level 1

Hi all,

I am a new Cisco enthusiast and presently an end user. I have embarked on a learning adventure with networking and jumped in with both feet.

I have the following hardware:

Cisco 887VA Integrated Services Router

Cisco ES520 series 8 port switch

Cisco UC320W appliance (of course)

I had the router as part of my existing data network and so I followed the Greyfield Smart Design guidelines for voice only service.

I have selected this topology and have my connections as per the guidelines.

Summary:

Cisco 887VA (fast ethernet port 3) ---- VLAN 4 ----- (WAN port) UC320W

I have configured the 887 with the IP address 192.168.2.253 with mask 255.255.255.252 on vlan4.

On the WAN page of the UC320W I have configured it with IP address 192.168.2.254 and mask 255.255.255.252. I have set the gateway as 192.168.2.253. My DNS servers etc are from the ISP.

My router config for the setup is:

!

interface FastEthernet3

switchport access vlan 4

switchport mode trunk

no ip address

!

interface Vlan4

ip address 192.168.2.253 255.255.255.252

ip nat inside

ip virtual-reassembly in

!

ip nat inside source static tcp 192.168.2.254 8080 interface Dialer0 8080

Now when I try to ping the UC320W from the router I get no response:

cisco#ping 192.168.2.254

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.2.254, timeout is 2 seconds:

.....

Success rate is 0 percent (0/5)

and from the PING tool in the UC320W web interface the same:

PING 192.168.2.253 (192.168.2.253): 32 data bytes

From 192.168.2.253 icmp_seq=0 timed out

From 192.168.2.253 icmp_seq=2 timed out

From 192.168.2.253 icmp_seq=3 timed out

--- 192.168.2.253 ping statistics ---

6 packets transmitted, 0 packets received, 100% packet loss

---------------------

I cannot access the WAN port from anywhere.

What am I doing wrong? Any suggestions? Please feel free to make any or ask any further questions.

1 Accepted Solution

Accepted Solutions

Matthew Needs
Level 1
Level 1

Hi Ben,

First of all, there is a PMF file to allow ping on the UC's WAN port.. It's blocked by the UC's firewall by default.

https://supportforums.cisco.com/docs/DOC-16301

Try setting your Fa3 port to access.. It's a trunk at the moment. You're config is a little mixed up.

interface FastEthernet3

switchport access vlan 4

switchport mode access

FYI - If you need a port to be a trunk in the future with a different native VLAN(default is 1). Here is how you would do it..

interface FastEthernet3

switchport trunk encapsulation dot1q

switchport trunk native vlan 4

switchport mode trunk

Finally, double check your UC's remote access port is actually 8080 and that remote access is enabled through the GUI.

Hope it helps

Matt

View solution in original post

3 Replies 3

Matthew Needs
Level 1
Level 1

Hi Ben,

First of all, there is a PMF file to allow ping on the UC's WAN port.. It's blocked by the UC's firewall by default.

https://supportforums.cisco.com/docs/DOC-16301

Try setting your Fa3 port to access.. It's a trunk at the moment. You're config is a little mixed up.

interface FastEthernet3

switchport access vlan 4

switchport mode access

FYI - If you need a port to be a trunk in the future with a different native VLAN(default is 1). Here is how you would do it..

interface FastEthernet3

switchport trunk encapsulation dot1q

switchport trunk native vlan 4

switchport mode trunk

Finally, double check your UC's remote access port is actually 8080 and that remote access is enabled through the GUI.

Hope it helps

Matt

Hi Matthew,

Thank you for your response.

I made the changes and applied the PMF. I can now ping the UC320W successfully from my router and other computers in the network.

I can also access the configuration from the WAN port now also which I couldn't before the ping started working. That remains a little mysterious as I would have thought the appliance would have responded despite filtering the pings.

Anyhow it all works now so I'm very pleased.

I could make and receive calls before by the way; but the lack of a response was disturbing; even though the WAN status was showing received and transmitted packets.

Thank you again.

Glad to help. Have fun!

Matt

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: