Couple of high level thoughts (attempted with minimal caffeination, so take with large conglomeration of NaCL and I may be whiffing on template syntax a bit):

This is almost complex enough you might want to look at using a proper parser (Parse::RecDescent, Marpa::R2) and build some sort of data structure to represent each "interface entry". Alternately maybe at least use "!\n" as your record separator and push the existing parsing logic off into its own sub (which then returns some sort of data structure . . .); doing that might help make sure you're not intermingling blocks and can (slightly more easily) start with a fresh parse state each one.

Also rather than a bunch of hardcoded print statements for something like this I'd use Template Toolkit (see also Template) and write something which takes the data produced by the parsing bits and then passes those to something which expands into the final output lines. 

[% MACRO interface_metainfo( if_info ) BEGIN %]
set interfaces ge-1/1/1 unit 23 description "[% if_info.description %]
+"
set interfaces ge-1/1/1 unit 23 encapsulation [% if_info.encapsulation
+ %]
set interfaces ge-1/1/1 unit 23 vlan-tags [% FOR tag IN if_info.vlan_t
+ags.keys %][% tag %] [% if_info.vlan_tags.$tag %][% END %]
## YADDA YADDA YADDA
[% END %]

[%- CLEAR -%]

[% FOR if IN interface_list %]
[% interface_metainfo( if ) %]
[% protocol_block( if ) %]
[% class_of_service_block( if ) %]
[% END %]

[download]

The cake is a lie.
The cake is a lie.
The cake is a lie.

In reply to Re: Cisco to Juniper - parser help by Fletch
in thread Cisco to Juniper - parser help by jamescmatt

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.