Switching

last person joined: 17 hours ago 

Ask questions and share experiences about EX and QFX portfolios and all switching solutions across your data center, campus, and branch locations.
  • 1.  annotate command

    Posted 04-02-2013 01:06

    Hi ,

    ı have added routing descriptions with annotate routing-options command .

    But i could not see annotate commands on shoıw configuration .

    How can  see annotates commands or routing-options descriptions .

     

    thnk



  • 2.  RE: annotate command

    Posted 04-02-2013 05:47

    Annotate is an interesting command. If you did the following:

     

    user@host# annotate routing-options "This is my annotate comment" 

     

    and then you did:

    user@host# show routing-options 

     

    You will not see your comment. 

     

    If you just do a show command you will see the comment as follows: 

     

    user@host# show

    . . . .

    . . . .

    /*This is my annotate comment */

    routing-options { . . . .

     

    So your annotations are not displayed within the context of a show statement for that stanza as they precede the stanza display. I hope that makes sense.



  • 3.  RE: annotate command

    Posted 04-04-2013 13:38

    muttbarker is correct! shows up before and after commit

    As far as I can tell, you can annotate the system defined hierarchy such as routing-options. And I tested it also. You can annotate a statement that exists.

    http://www.juniper.net/techpubs/en_US/junos10.1/information-products/topic-collections/swconfig-cli/topic-20962.html

    And it does show up in the configuration file. I have seen it so many times, and it is very useful. set <statement>

    Here is a quick test"

    {master:0}[edit]
    root@SW-1# show
    ## Last changed: 2013-04-04 18:34:55 UTC
    version 12.2R1.8;
    system {
           host-name SW-1;

    ....trimmed
              }
         }
    }
    /* test my comment */
    routing-options {
         /* This is my test comment */
          static {
                route 0.0.0.0/0 reject;
          }
    }
    vlans {
         vlan2100 {
                   vlan-id 2100;
                   interface {