Shell Programming and Scripting

No need to define X="*" if you don't need it. I proposed that because in the first version you wanted all three *cpes when $1 was empty. So - remove that and just print the error message.
Then, to be on the safe side, set X="" before the case, and execute the awk only if X is non-empty: [ $X ] && awk '...' ...

I thought I could get away with not defining X="*"but that was the first thing I tried and it fails. So, without X="*", I get every single device (including ones I didn't specify) sorted by software version. No error message.

Setting X=""before the caseand adding [ $X ] &&in front of my awkfixed it!

One task to go, and I hope I'm done with this. Just need to figure out how to do my -vto search for specific software versions matched against the first 5 characters of the version, skipping the first character [for the search, but still printing it

Example of what my awklooks at in show.version

JUNOS Base OS boot [12.3R7.7]

I'm honestly not sure how to even start this in my awk.

I'm assuming it requires another sub (...)but my brain is refusing to cooperate. I spent a good chunk of my night searching out the answer to the last problem before giving in to ask you for help, so I feel a little fried.

So how would you pass the -v (plus version info) to cver? Like cver -c -v 12.3R, i.e. second and third parameter? What error checking needs to be done?

Yeah, exactly like that. At minimum, they need to be able to search the first two digits and at max the whole thing. Searching only the first digit would be the equivalent of not using -v.

All software versions start with two digits, followed by a .
The place after .contains a single digit of 0-9
After that the next character is either R or S
After R or S it seems the next digit could be 0-9 or double digit like 11 followed by a . then a single digit 0-9

I don't want to limit any of the engineers from being able to search a full version, because I don't know how specific of a version someone might want to search for. I do know at minimum, they have to use -vfollowed by two digits.

If whatever they search for doesn't exist, a simple "No match found" message will suffice.

Ex:

Code:

cver -c -v 14
No match found

Whatever they do search that exists shows everything up to what they searched and includes anything that may be after it.

Ex:

Code:

cver -c -v 12.3
[12.3R6.6] device1-r0.cpe.domain.net
[12.3R6.6] device2-r0.cpe.domain.net
[12.3R7.7] device3-r1.cpe.domain.net
...

I hope that answers your questions.

Well, this is becoming more and more complicated, and more and more error checking would need to be done, like parameter count, value validation, etc. - which I neglect here, or leave it up to the reader, resp.
OK, run the awk like

Code:

 awk -vSRCH=$3" '/JUNOS/ && /boot/ && $5 ~ "^\[" SRCH {...}'...

This doesn't check for $2 to be -v, and if $3 is missing, field 5 in the file is just checked to start with the [ char.

Yeah, I'll tackle this tonight when I come in for my shift. For now, it's quitting time and I need rest. Thanks again!

---------- Post updated 03-24-16 at 01:07 AM ---------- Previous update was 03-23-16 at 07:29 AM ----------

Ok, so I gave it a shot and it breaks my -c, -e, -ocommands.

Your suggestion
awk -vSRCH=$3" '/JUNOS/ && /boot/ && $5 ~ "^\[" SRCH {...}'...

I got a missing double quote error trying to paste into shell. Added it around $3.

[ $X ] && awk -vSRCH="$3" '/JUNOS/ && /boot/ && $5 ~ "^\[" SRCH {...}'...

Then gave me:

Code:

clmbn-eng2.eng:~% cver -c
awk: nonterminated character class ^[
 input record number 3, file /home/clmbn-eng2/a/rwalker/svn/nw_config_data/device1-e0.cpe.domain.net/show.version
 source line number 1

So I added [] around "^\["and got -c, -e, -o working again.

[ $X ] && awk -vSRCH="$3" '/JUNOS/ && /boot/ && $5 ~ "[^\[]" SRCH {...}'...

Now it gets interesting...

cver -c -vruns the same as cver -c, but I'm ok with that. The engineers will figure out that won't work so well for them without an actual search term after -v. Ultimately, it would be cool if -vwas undefined by the user if it worked like my (*)where it does echo "Unrecognized or incomplete command.\nUse -h for help."but really, I'm not too worried about that.

cver -c -v 1prints a list of all versions with 1 in them, but not all of them oddly. I don't get all of version 10 or any results for 12 and 13. Searching any digit 0-9 (except 1) will return a list of any software version that has any of those numbers in it anywhere in the version.

cver -c -v 10doesn't print any software versions starting with 10. Instead, it printed a list of versions with 10 in it somewhere else.

Ex:
[11.4R10.3] device-e0.cpe.domain.net

cver -c -v 11prints nothing. From the example above, I have devices with software version 11.

cver -c -v 12prints nothing. I have multiple devices software versions starting with 12.

cver -c -v 13prints nothing. I do have one device in -c with a 13. software version.

cver -e -v 14prints nothing. I do have one device in -e with a 14. software version.

---------- Post updated at 04:05 AM ---------- Previous update was at 01:07 AM ----------

I think I fixed it.

Do this:
"[\[^]"

Instead of this:
"[^\[]"

Now I have

[ $X ] && awk -vSRCH="$3" '/JUNOS/ && /boot/ && $5 ~ "[\[^]" SRCH {...}'...

I regret it doesn't work out that well for you. Unfortunately I could do only very basic testing without some serious test data, but it worked for me. Must be a awk version problem, probably with the escaping of the [ char. It's just that char that needs escaping. Try $5 ~ "^[[]" SRCH. It needs the ^ in front!
Sorry for missing the matching double quote.