Buy or Renew
Buy or Renew
COMING SOON: Umbrella and Secure Access release notes are coming to Cisco Community. The community will be in read-only August 16 – 19. Learn more.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
18652
Views
0
Helpful
6
Replies

"interface range vlan" Syntax

lbhoang
Level 1
Level 1

‎02-09-2005 02:32 PM - edited ‎03-02-2019 09:35 PM

On a Catalyst 6509 with Cat1a/MSFC1 in hybrid mode running CatOS 6.4(1) and IOS 12.1(8b)E10, what is the syntax for "interface range vlan"?

I'm trying to specify a range of VLANs, 1 through 910, to apply "no shut" on but it's not taking the syntax as shown below. VLANs 1 through 910 do exist on MSFC1 as verified with "sh ip int brief" and "sh run".

icat_b_msfc1(config)#int range vlan ?

<1-4094> Vlan interface number

icat_b_msfc1(config)#int range vlan 1 ?

, comma

- hyphen

<cr>

icat_b_msfc1(config)#int range vlan 1 - ?

<1-1005> last port number or vlan interface in port-range

icat_b_msfc1(config)#int range vlan 1 - 910 ?

, comma

<cr>

icat_b_msfc1(config)#int range vlan 1 - 910

interface range not validated - command rejected

icat_b_msfc1(config)#

It does take "int range vlan 1, vlan 910" but this only applies to vlans 1 and 910 and not 1 through 910.

Thanks in advance.

1 person had this problem
Labels:
0 Helpful
6 Replies 6

Prashanth Krishnappa
Cisco Employee
Cisco Employee

‎02-09-2005 05:20 PM

Double check to see if there are any missing VLANs. Also try doing it in blocks of 10 to be sure and see if it works.

Note: In 12.1 code you cannot create VLANs using range command

0 Helpful

lbhoang
Level 1
Level 1
In response to Prashanth Krishnappa

‎02-09-2005 11:04 PM

I tried "interface range vlan" with the hyphen option against the first two VLANs 1 and 10 and it still doesn't take but comma works fine.

icat_b_msfc1(config)#int range vlan 1 - 10

interface range not validated - command rejected

icat_b_msfc1(config)#int range vlan 1 , vlan 10

icat_b_msfc1(config-if-range)#exit

icat_b_msfc1(config)#

Funny thing is I used this command successfully the other day but with a newer IOS 12.1(23)E2. Perhaps the older IOS 12.1(8b)E10 doesn't like the hyphen option. I'll try again with the newer IOS just to confirm I'm not losing my mind.

Thanks for the suggestions.

0 Helpful

Kevin Dorrell
Level 10
Level 10
In response to lbhoang

‎02-10-2005 12:31 AM

That rings a bell. I know they have recently changed the behaviour wrt the hyphen and spaces. It used to be (number)(space)(hyphen)(space)(number), and I think they have removed or are removing the space reqirements. But whether this is the version dependency you are observing .... I don't know.

Kevin Dorrell

Luxembourg

0 Helpful

Prashanth Krishnappa
Cisco Employee
Cisco Employee
In response to lbhoang

‎02-10-2005 05:31 AM

I was able to do it fine in my lab. As I mentioned earlier, make sure all the VLAN interfaces are configured. As you can see in my lab, I have VLAN interfaces 1-10.

MSFC2#sh ver | include IOS

IOS (tm) MSFC2 Software (C6MSFC2-JSV-M), Version 12.1(8b)E15, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)

MSFC2#

MSFC2#sh ip int brief

Interface IP-Address OK? Method Status Protocol

Vlan1 unassigned YES manual up up

Vlan2 unassigned YES manual up up

Vlan3 unassigned YES manual up up

Vlan4 unassigned YES manual up up

Vlan5 unassigned YES unset administratively down down

Vlan6 unassigned YES unset administratively down down

Vlan7 unassigned YES unset administratively down down

Vlan8 unassigned YES unset administratively down down

Vlan9 unassigned YES unset administratively down down

Vlan10 unassigned YES unset administratively down down

MSFC2# conf t

Enter configuration commands, one per line. End with CNTL/Z.

MSFC2(config)#int range vlan 1 - 10

MSFC2(config-if-range)#no shut

MSFC2(config-if-range)#

12:24:24: %LINK-3-UPDOWN: Interface Vlan5, changed state to down

12:24:24: %LINK-3-UPDOWN: Interface Vlan6, changed state to down

12:24:24: %LINK-3-UPDOWN: Interface Vlan7, changed state to up

12:24:24: %LINK-3-UPDOWN: Interface Vlan8, changed state to down

12:24:24: %LINK-3-UPDOWN: Interface Vlan9, changed state to down

12:24:24: %LINK-3-UPDOWN: Interface Vlan10, changed state to up

12:24:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan5, changed state to down

12:24:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan6, changed state to down

12:24:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan7, changed state to up

12:24:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan8, changed state to down

12:24:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan9, changed state to down

12:24:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to up

MSFC2(config-if-range)#end

MSFC2#

12:24:30: %SYS-5-CONFIG_I: Configured from console by vty0 (127.0.0.11)

MSFC2#sh ip int brief

Interface IP-Address OK? Method Status Protocol

Vlan1 unassigned YES manual up up

Vlan2 unassigned YES manual up up

Vlan3 unassigned YES manual up up

Vlan4 unassigned YES manual up up

Vlan5 unassigned YES unset down down

Vlan6 unassigned YES unset down down

Vlan7 unassigned YES unset up up

Vlan8 unassigned YES unset down down

Vlan9 unassigned YES unset down down

Vlan10 unassigned YES unset up up

MSFC2#

0 Helpful

lbhoang
Level 1
Level 1
In response to Prashanth Krishnappa

‎02-10-2005 05:57 PM

The problem seems to be with MSFC1 and IOS 12.1(8b)E10 as it doesn't work on our two production and lab 6509 switches with identical Sup1a/MSFC1, IOS and configs. But, it does work with Sup1a/MSFC2, IOS 12.1(23)E2 and same config. Another reason to upgrade the OS which I'm apparently working on.

Sup1a/MSFC1 IOS 12.1(8b)E10:

icat_b_msfc1#sh ver | include IOS

IOS (tm) MSFC Software (C6MSFC-DSV-M), Version 12.1(8b)E10, EARLY DEPLOYMENT RELEASE SOFTWARE (fc3)

icat_b_msfc1#sh ip int brief

Interface IP-Address OK? Method Status Protocol

Vlan1 172.16.0.98 YES NVRAM up up

Vlan10 10.10.10.3 YES NVRAM up up

Vlan11 10.10.11.3 YES NVRAM up up

Vlan12 10.10.12.3 YES NVRAM up up

Vlan13 10.10.13.3 YES NVRAM up up

Vlan14 10.10.14.3 YES NVRAM up up

Vlan15 10.10.15.3 YES NVRAM up up

Vlan19 10.10.19.3 YES NVRAM up up

Vlan20 10.10.240.3 YES NVRAM up up

Vlan21 10.10.241.3 YES NVRAM up up

Vlan22 10.10.242.3 YES NVRAM up up

icat_b_msfc1#conf t

Enter configuration commands, one per line. End with CNTL/Z.

icat_b_msfc1(config)#int range vlan 1 - 10

interface range not validated - command rejected

icat_b_msfc1(config)#

Sup1a/MSFC2 IOS 12.1(23)E2:

icat_b_msfc1#sh ver | include IOS

IOS (tm) MSFC2 Software (C6MSFC2-DSV-M), Version 12.1(23)E2, RELEASE SOFTWARE (fc1)

icat_b_msfc1#sh ip int brief

Interface IP-Address OK? Method Status Protocol

Vlan1 172.16.0.98 YES NVRAM down down

Vlan10 10.10.10.3 YES NVRAM up up

Vlan11 10.10.11.3 YES NVRAM down down

Vlan12 10.10.12.3 YES NVRAM down down

Vlan13 10.10.13.3 YES NVRAM down down

Vlan14 10.10.14.3 YES NVRAM down down

Vlan15 10.10.15.3 YES NVRAM down down

Vlan19 10.10.19.3 YES NVRAM down down

Vlan20 10.10.240.3 YES NVRAM down down

Vlan21 10.10.241.3 YES NVRAM down down

Vlan22 10.10.242.3 YES NVRAM up up

icat_b_msfc1#conf t

Enter configuration commands, one per line. End with CNTL/Z.

icat_b_msfc1(config)#int range vlan 1 - 10

icat_b_msfc1(config-if-range)#

0 Helpful

glen.grant
VIP Alumni
VIP Alumni

‎02-09-2005 06:31 PM

Try putting a space between the 1 and the hypen and between the hyphen and 910 , interface range vlan 1 - 910 with a space between the numbers and the dash .

0 Helpful
Customers Also Viewed These Support Documents