Ping from VxWorks CLI 1

[autoint]

To confirm a route is working as expected (I think it is, based on a packet capture), I'm trying to ping a public IP address from a 3300 ICP (software version 9.0.0.41, not MCD) VxWorks command line. I'm connected to VxWorks using PuTTY. If I try something like:

-> ping 8.8.8.8

I see the response:

ping 8.8.8.8
invalid number: 8.8.

If (out of curiosity) I try:

-> ping 1

I see the response:

ping 1
PING : 56 data bytes
ping: timeout
no answer from
value = -1 = 0xffffffff

VxWorks seems to have implemented a ping command and I presume its purpose is the same as ping elsewhere. Can you offer some guidance on how to use ping in this context? Does it expect an IP address (of an unusual format?) or a hostname or...?

Why I want to try a ping test:

When I click Retrieve Licenses to update purchased options on the system, I see:

I see 2 apparently-related software error log entries:

From a packet capture when I try Retrieve Licenses, I see the 3300 successfully resolves sync.mitel-amc.com -> 216.191.234.91. The 3300 and (private) DNS server are on separate subnets, so I know the default route assigned to the 3300 is working at that level. I would like to confirm the 3300 can reach/ping 216.191.234.91. I am able to ping 216.191.234.91 from my PC (not on same subnet as 3300).

Thank you!

 

[autoint]

Pretty sure I figured out the ping question:

ping "<IP address>"

In other words, literally:

ping "216.191.234.91"

Now how to break out of a VxWorks ping command (in PuTTY session)?
Ctrl+C? Nope. Break? Nope. Ctrl+Break? Nope. Esc? Nope...

Now to figure out why my default route is working for other subnet, but not to public Internet...

 

[autoint]

Got it all sorted now.

I needed to add static route back to voice subnet and firewall/NAT rules, on edge router.

 

[autoint]

...oh, and to kill the ping process, just close the PuTTY process (window). Ugly but effective.

 

[techymitel]

You can use:

ping "1.2.3.4",4

This will ping 1.2.3.4 four times and then stop.

 

[AH64Armament]

Careful using CTRL+C or CTRL+Break, etc... in some versions of VXWorks, they will cause problems... in an OLD version of the 3300 (3300 release 4 or 5), a command that worked in previous version caused the system to crash.... We documented it with Mitel support, they had a patch the following week.

also early versions of the 3300 would allow 5 sessions to be connected - your putty session would be one session... if you exited hot (X-out), it would hold that session until the next reboot... when given the Logout or EXIT button - use it instead of the windows X-out... save trouble later.

Be sure to never allow something to perpetuate... always give it a defined stop.
Just as techymitel points out, use the command
>ping "1.2.3.4" ,4

Note the quotes around the 1.2.3.4, and the space after the end quote before the comma... Mitel support at one time or another said to make sure there is a space there... it works without the space, but they made a point to mention the importance of the space.