yeah, I can do all such things. but i specified "programmatically".
may be socket call to those boxes can help me differentiate routers and
switches in the subnet.
I am trying to find some common features among all switches which can be
know thru remote programming.
same with routers ...
May be  this is very vague on my part to try this stunt :-)





----- Original Message -----
From: Rico Ortiz 
To: 
Sent: Thursday, February 28, 2002 6:17 PM
Subject: RE: detect routers and switches [7:36873]


> OK how about telnet, 3rd party SNMP software..
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> ashish
> Sent: Thursday, February 28, 2002 6:34 PM
> To: [EMAIL PROTECTED]
> Subject: Re: detect routers and switches [7:36873]
>
>
> well, that's not my problem.
> I have to find a general way to find whether a remote IP box is a router
or
> a switch.
> That IP box can be of any vendor.
> and that remote box can be located across multiple networks.
>
> ----- Original Message -----
> From: Larry Letterman
> To:
> Sent: Thursday, February 28, 2002 3:07 PM
> Subject: RE: detect routers and switches [7:36873]
>
>
> > if its cisco gear, do a show cdp neighbor detail and it should show you
> > whats on the other end...
> >
> >
> > Larry Letterman
> > Cisco Systems
> > [EMAIL PROTECTED]
> >
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> > ashish
> > Sent: Thursday, February 28, 2002 2:30 PM
> > To: [EMAIL PROTECTED]
> > Subject: detect routers and switches [7:36873]
> >
> >
> > Hi,
> > this question is bit vauge.But thought you guys will surely be able to
> help
> > me
> > out :-)
> >
> > is there any way to tell programmatically , whether a remote box is a
> router
> > or a switch.
> >
> > Thanks,
> > Ashish




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=36916&t=36873
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to