[comp.dcom.sys.cisco] Ping to aliases

dd@ariel.unm.edu (06/13/91)

Hello folks-

I am having to implement a process in an obscure way because a CISCO
terminal server doesn't respond to an ICMP echo request for an alias IP
address (currently it is ignored).  Is there a reason for this, or is
this something that might be feasible to implement (for example, you
might respond as if the CISCO terminal server *itself* had been
pinged)?

The obvious advantage to such an implementation is that a collection of
ports representing a service appears to be just any other IP-based
service - that is, if you ping it, it responds.  You would not be able
to distinguish such a collection of terminal server ports from a *real*
machine if this capability existed...

Thanks!

Don Doerner
University of New Mexico
Albuquerque, NM, 87131

BILLW@mathom.cisco.com (WilliamChops Westfield) (06/13/91)

    I am having to implement a process in an obscure way because a CISCO
    terminal server doesn't respond to an ICMP echo request for an alias IP
    address (currently it is ignored).  Is there a reason for this, or is
    this something that might be feasible to implement (for example, you
    might respond as if the CISCO terminal server *itself* had been pinged)?

This, uh, "misfeature" seems to be corrected in the currently shipping
release (8.2(4)).  Actually, it looks like it was fixed back before
release 8.1.  Unfortunately, a lot of random changes like this do not
get documented in the release notes.

Bill Westfield
cisco Systems.
-------

Michael A. Patton <MAP@lcs.mit.edu> (06/13/91)

   Date: Wed, 12 Jun 1991 14:09:07 +0100
   From: dd%ariel.unm.edu@triton.unm.edu

   ... because a CISCO terminal server doesn't respond to an ICMP echo
   request for an alias IP address (currently it is ignored).

This was fixed AGES ago.  It's at least in 8.1(25) which we've been
running over 6 months.  It wasn't in 7.1(7).  We didn't run anything
in between, so I can't be sure when it started working.

            __
  /|  /|  /|  \         Michael A. Patton, Network Manager
 / | / | /_|__/         Laboratory for Computer Science
/  |/  |/  |atton       Massachusetts Institute of Technology

Disclaimer: The opinions expressed above are a figment of the phosphor
on your screen and do not represent the views of MIT, LCS, or MAP. :-)