Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure 
engine=1.12.7400:2.4.4,1.2.40,4.0.166 
definitions=2009-03-27_08:2009-03-27,2009-03-27,2009-03-27 signatures=0
X-Proofpoint-Spam-Details: rule=uncdefault_notspam policy=uncdefault score=0 
spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam 
adjust=0 reason=mlx engine=5.0.0-0811170000 definitions=main-0903270076

One more caveat - you must not be using the "more" logic and find at the sa=
me time - so "set len 0"
And a retraction on the no white space, you just can't put the search strin=
g in quotes.
Find is not case sensitive.

-----Original Message-----
From: Eaton, Ernest
Sent: Thursday, March 26, 2009 1:21 PM
To: Enterasys Customer Mailing List
Subject: RE: [enterasys] Include / Exclude / Grep on EOS

Please don't make me regret revealing this less documented prototype implem=
entation of the find command ;)

The current implementation does not support a quoted "" search string. The =
search string must not contain any white space. Because of the underlying i=
mplementation not all commands (like show support) are supported by find. T=
he spacing requirement for |find is also one of the reasons it is not forma=
lly announced.  I expect future versions of firmware to formally support th=
is feature with more options and complete coverage. As such we have not yet=
 considered enabling it on the ABC since the feature definition is incomple=
te.

Find should work for 6.11.01.0040. I just tried it with show port alias on =
a system here. Email me directly with your sample output of a failed comman=
d execution.

We value your suggestions
Ernie

-----Original Message-----
From: Stephen Faulkner [mailto:[email protected]]
Sent: Thursday, March 26, 2009 1:53 AM
To: Enterasys Customer Mailing List
Subject: Spam: RE: [enterasys] Include / Exclude / Grep on EOS

I fully support the need for | include and begin, or equivalent.  If Entera=
sys doesn't want to look too much like Cisco then grep is better than find,=
 but I am not fussy.  Should have been available ages ago.  Now that I am s=
pending most of my time with Catalysts and VRF and large config files, I ca=
nnot survive without the pipe inc and beg options.
The search option in the ER16 has also been extremely useful when running t=
housands of ACL lines.

However, we have  06.11.01.0040 firmware which for us is excellent in all w=
ays, but it DOESN'T work with |find.  Just outputs the entire command resul=
t (e.g. show config |find snmp just dumps everything).

And to me at least, it's more customary to have a space after the pipe sign=
.

Regards

Stephen
Oslo University Hospital



(In compliance with the Security Policy of Rikshospitalet HF , the content =
of this message (including any attachments) is of a non-sensitive nature)

-> -----Original Message-----
-> From: Bruce O'Donnell [mailto:[email protected]]
-> Sent: Thursday, March 26, 2009 2:50 AM
-> To: Enterasys Customer Mailing List
-> Subject: FW: [enterasys] Include / Exclude / Grep on EOS
->
-> Personally, I have never understood why a box the size of the N series
-> doesn't have a config list output sectioning for routing like the X
-> does. I have a customer with lengthy ACLs and it is quite cumbersome
-> to have to list out the whole L3 config to get to say VRRP or routing
-> protocols that are way near the end.
->
-> Something like ..
-> show run | begin vrrp
-> .. would help out a lot. It's just about finessing the manageability
-> of the products.
->
-> Also, Thanks Ernest for pointing out that find option. That will be
-> handy but should be in all the lines A,B,C etc. It's always valuable
-> input when the Enterasys people contribute here.
->
->
-> Bruce O'Donnell
-> Senior Network Specialist CCIE
-> NEC Australia Pty Ltd 26 Rodborough Road Frenchs Forest NSW 2086
->
-> -----Original Message-----
-> From: Eaton, Ernest [mailto:[email protected]]
-> Sent: Thursday, 26 March 2009 8:27 AM
-> To: Enterasys Customer Mailing List
-> Subject: RE: [enterasys] Include / Exclude / Grep on EOS
->
-> Try this on your N Series:
->
-> And3N 105(rw)->show port alias |find GREY_04 Alias on port fe.4.4 set
-> to:  GREY_04.
->
-> Note the space before | and the find directly after the | This will
-> not work with all commands like show support or router commands
->
-> In future versions we may improve options for the find or rename the
-> feature.
-> I think it is in most 6.xx firmware, definitely 6.11 and after.
->
->
-> -----Original Message-----
-> From: Clarke Morledge [mailto:[email protected]]
-> Sent: Wednesday, March 25, 2009 4:06 PM
-> To: Enterasys Customer Mailing List
-> Subject: Re: [enterasys] Include / Exclude / Grep on EOS
->
-> On Wed, 25 Mar 2009, Lou H. Goddard wrote:
->
-> > Greetings,
-> >
-> > It would be wonderful to be able to pipe the CLI output to grep.
-> More
-> > specifically, I'd love this feature to be implemented on the A/B/C2
-> and
-> > N7.
-> >
-> > For example, suppose you're looking for the port alias "Somehost."
-> You
-> > could do a show alias and sift through the output until you find
-> > Somehost.  Or, you could do a "show alias | include SomeHost" ala
-> Cisco
-> > style.
-> >
-> > Any other EOS users think this would be useful?
-> >
-> > Thanks,
-> > Lou Goddard
->
-> Lou,
->
-> Absolutely, yes!
->
-> My only caveat is that I wish the "Cisco style" had a more powerful
-> and flexible regex function.....
->
-> Clarke Morledge
-> College of William and Mary
-> Information Technology - Network Engineering Jones Hall (Room 18)
-> Williamsburg VA 23187
->
-> ---
-> To unsubscribe from enterasys, send email to [email protected] with the
-> body: unsubscribe enterasys [email protected]
->
->
->
-> ---
-> To unsubscribe from enterasys, send email to [email protected] with the
-> body: unsubscribe enterasys [email protected]
->
-> ---
-> To unsubscribe from enterasys, send email to [email protected] with the
-> body: unsubscribe enterasys [email protected]

---
To unsubscribe from enterasys, send email to [email protected] with the body=
: unsubscribe enterasys [email protected]



---
To unsubscribe from enterasys, send email to [email protected] with the body: 
unsubscribe enterasys [email protected]

Reply via email to