3 Replies Latest reply on Feb 11, 2015 12:01 PM by noor

    I'm having problems with the interface range command

    diggly New Member

      When I use the interface range command on several gigabit switchports, I frequently get an error "%Invalid interface: 0/xx" on one of the ports.  Reissuing the command will either work, give me the same error, or give me the same error on a different port number.  This seems (and I'm not sure about this) to be worse when the ports are non-contiguous.

       

      If/when the interface command is accepted and I get into the interface configuration, I get the same error when I issue commands.  I frequently have to issue them over and over again before they are accepted.  Even the Exit command has this behavior.

       

      Example:

       

      ZCCSP-EDGE3(config)#$int range gig 0/4,0/6,0/8,0/10,0/12,0/14,0/16,0/18,0/22,0/26,0/28,0/30,0/34,0/36,0/38,0/40,0/42,0/44,0/46,0/48

      %Invalid interface: 0/26

      ZCCSP-EDGE3(config)#$int range gig 0/4,0/6,0/8,0/10,0/12,0/14,0/16,0/18,0/22,0/26,0/28,0/30,0/34,0/36,0/38,0/40,0/42,0/44,0/46,0/48

      ZCCSP-EDGE3(config-giga-swx 0/4, 0/6, 0/8, 0/10, 0/...)#

       

      Failed the first time, succeeded the second time.  Then:

       

      ZCCSP-EDGE3(config-giga-swx 0/4, 0/6, 0/8, 0/10, 0/...)#switchport mode trunk

      %Invalid interface: 0/26

      ZCCSP-EDGE3(config-giga-swx 0/4, 0/6, 0/8, 0/10, 0/...)#switchport mode trunk

      %Invalid interface: 0/42

      ZCCSP-EDGE3(config-giga-swx 0/4, 0/6, 0/8, 0/10, 0/...)#switchport mode trunk

      %Invalid interface: 0/42

       

      Note the change in port number in the Invalid interface reference.  Never did get that to work.

       

      It seems the more ports there are, the more likely this is to not work.  Is this just not doable, am I doing something wrong, what could it be?

       

      I'm running AOS 10.9.4 on a 1638P.  This particular switch has only been up three days and I have been having this problem for a while on all my 1638s, so I don't think that a restart is the answer

       

      Thanks for any help.

        • Re: I'm having problems with the interface range command
          deltranathaniel New Member

          Hello diggly,

              

               I have never used that kind of switch. From what you have shown it sounds like a bug. Try updating the firmware. Maybe that will fix it. A new one just came out on 12/2/14. If this doesn't help try doing a small amount, like 6 ports at a time to see if you can. And increase it by like two each time to see if your theory about their being too many is right. Then contact tech support and see if they have fix.

           

          I hope that helps.

               Nathaniel

          1 of 1 people found this helpful
            • Re: I'm having problems with the interface range command
              diggly New Member

              Thanks deltranathaniel.  This is a production switch so I'm a little hesitant to upgrade the firmware.  When I said its uptime was 3 days I failed to mention that it had been up for at least 6 months before that, so this isn't a new switch I'm trying to configure.  I may have one available in a week or so that I can experiment with.  The number of ports definitely seems to have an effect, but I also believe it's the way they are specified.

               

              "int range gig 0/1-48" works every time.  "int gig range 0/1,0/2,...,0/48" would almost surely fail.

               

              The range command is awesome when it works.  Can reduce hours of Web Interface drudgery to just a few minutes of work.