[rancid] Re: Searching for Half-duplex Interfaces

[Mike Ashcraft]

Close. You need to trim the data in router.db

for rtr in $(cat router.db | cut -d: -f1); do clogin $rtr ... ; done 


Mike



-----Original Message-----
From: rancid-discuss-bounces at shrubbery.net
[mailto:rancid-discuss-bounces at shrubbery.net] On Behalf Of Pabon, Nestor
Sent: Friday, January 11, 2008 4:20 PM
To: Ed Ravin
Cc: rancid-discuss at shrubbery.net
Subject: [rancid] Re: Searching for Half-duplex Interfaces

So the list of routers is in:

/opt/rancid/data/mpls-routers

Does this mean that 

"for rtr in ...list..."

Becomes

"for rtr in /opt/rancid/data/mpls-routers/router.db"

Regards,
Nestor

 

-----Original Message-----
From: Ed Ravin [mailto:eravin at panix.com] 
Sent: Friday, January 11, 2008 3:29 PM
To: Pabon, Nestor
Cc: rancid-discuss at shrubbery.net
Subject: Re: [rancid] Re: Searching for Half-duplex Interfaces

On Fri, Jan 11, 2008 at 02:33:32PM -0700, Pabon, Nestor wrote:
> I'm not sure I conveyed my goal correctly.
> 
> If I use clogin or log directly into the router I know I can query
> issuing the following:
> 
> "sh interface | i Half-duplex"
> 
> But this will only return something like:
> 
> "Half-duplex, 10Mb/s, 100BaseTX/FX"

But if you followed John's instructions (repeated below, with slight
edits
for clarity), you would get something much better than that.  Note the
regexp which will match things like:

     FastEthernet0/0/0 is up, line protocol is up

So you'll see the interface names, and then their duplex settings if
they are Ethernet-based.

--------

   for rtr in ...list...
   do
       clogin -c 'show interfaces | inc (line protocol|duplex|speed)'
$rtr >>output.file 2>&1
   done


_______________________________________________
Rancid-discuss mailing list
Rancid-discuss at shrubbery.net
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss