vlan interfaces wont come up, gns3 limitation?

[kermitsfrog]

Hello,

Basic setup... both boxes are 2961s. R2 is the routing 'hub' in my gns project, R3 is a remote router, R2 fa1/2 > R3 fa1/2 is a trunk for vlans 100-110. created interface vlan 100 on both routers, trunk ports show up, switchport shows its allowing vlan range, interfaces stay down. Am i misunderstanding how to configure vlans or is this a gns3 limitation?

R2:

R2#sh run int fa1/2
Building configuration...

Current configuration : 133 bytes
!
interface FastEthernet1/2
switchport trunk allowed vlan 1,2,100-110,1002-1005
switchport mode trunk
duplex full
speed 100
end

R2#sh run int vlan 100
Building configuration...

Current configuration : 113 bytes
!
interface Vlan100
ip address 192.168.150.1 255.255.255.0
vlan-id dot1q 100
exit-vlan-config
!
end

R2#

R3

R3#sh run int fa1/2
Building configuration...

Current configuration : 133 bytes
!
interface FastEthernet1/2
switchport trunk allowed vlan 1,2,100-110,1002-1005
switchport mode trunk
duplex full
speed 100
end

R3#
R3#sh run int vlan 100
Building configuration...

Current configuration : 106 bytes
!
interface Vlan100
ip address 192.168.150.2 255.255.255.0
vlan-id dot1q 100
exit-vlan-config
!
end

R3#

[MHM Cisco World]

This not need under vlan

vlan-id dot1q 100

You need under switchport

Switchport trunk encapsulate dot1x <<- add this before config switchport mode trunk and allow vlan

Also you need under under vlan 

No shut

MHM

[kermitsfrog]

that was my configuration prior to attempting to add the vlans to the vlan interfaces and it was still down. I'm starting to think its a gns3 issue. Also, I have no shut the vlans, the line just does not show in the sh run, same with encap dot1q under switchports.

R2#sh run int fa1/2
Building configuration...

Current configuration : 133 bytes
!
interface FastEthernet1/2
switchport trunk allowed vlan 1,2,100-110,1002-1005
switchport mode trunk
duplex full
speed 100
end

R2#
R2#sh run int vlan 100
Building configuration...

Current configuration : 65 bytes
!
interface Vlan100
ip address 192.168.150.1 255.255.255.0
end

R2#
R2#sh int vlan 100
Vlan100 is up, line protocol is down
Hardware is EtherSVI, address is c002.e608.0000 (bia c002.e608.0000)
Internet address is 192.168.150.1/24
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 63
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 packets output, 0 bytes, 0 underruns
0 output errors, 1 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
R2#

R2(config-if)#switchport trunk enc
R2(config-if)#switchport trunk encapsulation dot
R2(config-if)#switchport trunk encapsulation dot1q
R2(config-if)#
R2#

R2#sh run int fa1/2

Building configuration...

Current configuration : 133 bytes
!
interface FastEthernet1/2
switchport trunk allowed vlan 1,2,100-110,1002-1005
switchport mode trunk
duplex full
speed 100
end

R2#

R3(config)#int fa1/2
R3(config-if)#swi
R3(config-if)#switchport tr
R3(config-if)#switchport trunk enc
R3(config-if)#switchport trunk encapsulation dot1
R3(config-if)#switchport trunk encapsulation dot1q
R3(config-if)#^Z
R3#
R3#sh run int f
*Mar 1 00:30:06.311: %SYS-5-CONFIG_I: Configured from console by console
R3#sh run int fa1/2
Building configuration...

Current configuration : 133 bytes
!
interface FastEthernet1/2
switchport trunk allowed vlan 1,2,100-110,1002-1005
switchport mode trunk
duplex full
speed 100
end

R3#

R3#sh run int vlan 100
Building configuration...

Current configuration : 65 bytes
!
interface Vlan100
ip address 192.168.150.2 255.255.255.0
end

R3#

R3#sh int vlan 100
Vlan100 is up, line protocol is down
Hardware is EtherSVI, address is c003.1484.0000 (bia c003.1484.0000)
Internet address is 192.168.150.2/24
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 2
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 packets output, 0 bytes, 0 underruns
0 output errors, 1 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
R3#

[MHM Cisco World]

I don't see 

Switchport trunk encapsulate dot1x?

Also 

Dis you add vlan ? By 

Vlan xxx 

MHM

[M02@rt37]

Hello @kermitsfrog 

Configure L2 vlan 

Under configure-terminal add vlan

vlan 100

Etc...

Under interface vlan (=SVI) configure only the IP address.

Checks:

#show vlan --check vlan config 

#show interface status --check interface trunk or access status 

[kermitsfrog]

was wondering if that had something to do with it, once again I'm falling victim to GNS3 limitations.... I'll have to see how to increase nv memory on these things later. I created the vlan through conf t but it would never 'take' - tried doing it through vlan database just now and received nvram error when exiting and forced to abort..... 

R3(vlan)#vlan 100
VLAN 100 added:
Name: VLAN0100
R3(vlan)#exit
% not enough space on flash to store vlan database. trying squeeze...
% error squeezing flash - (No device available)
Error on database apply 40: NV storage failure
Use 'abort' command to exit
R3(vlan)#exit
% not enough space on flash to store vlan database. trying squeeze...
% error squeezing flash - (No device available)
Error on database apply 40: NV storage failure
Use 'abort' command to exit
R3(vlan)#abort
Aborting....
R3#

[Martin L]

In addition to MHM, you also need vlans to be present in the vlan database; vlans 2,100-110.  For int vlan 100 to be UP u must have at least one port be active (access port vlan x and UP UP); Otherwise interface vlan 100 SVI will stay down state.  Same thing for switches; vlan present in database and active access port in vlan x for the SVI vlan x to be UP UP. 

What IOS of router do u use? 

Regards, ML
**Please Rate All Helpful Responses ** 

[kermitsfrog]

even when setting fa1/2 on r3 to access port for JUST vlan 100, it still stays down. GNS3 will not allow me to create the vlan database apparently (see above errors) - I will have to get this solved before I can continue building the lab. 

Thank you all for the replies, it seems I knew the problem all along and wanted to believe there would be a work-around.

[MHM Cisco World]

@Martin L ask good Q' not all ios image work as L2/L3 i.e. add vlan.

So please inform him which image you use' he can help you to decide correct image to rn SVI VLAN in router 

MHM

[MHM Cisco World]

For memory' you need to go to preference >router image> and increase memory there make it 512 instead of 128' but I am not so sure this will solve your issue' but anyway try it

MHM

[kermitsfrog]

I did end up fixing it. 

For any future googlers who have similar issues, the problem causing the 'lack of nvmemory' was due to the default PCMCIA size in GNS3 being set to '0 MiB' - increased to 4 - and then flash the router memory with the commands:
R3# erase flash:
R3# format flash:
R3# erase flash:

After this I was able to see 4mb of nvram in the routers and they accepted the vlan database creation - everything has worked since, my original config from the OP Post remains working (although the redundancy of allowing the vlans on the vlan interface can be omitted, I only put them there to try and find a 'workaround' to the nv issue.... but it did not seem to break anything either)

[Martin L]

Since GNS3 does not support switch image like CML does, I would recommend using CML; if u learning for CCNA, u can use Packet Tracer for free; it is not an emulator like GNS3 but it should be enough for basic of CCNA level knowledge. Of course, u can continue learning routing with GNS3

Latest CML comes with 2 excellent 2 IOU images: one for switching and one routing. Older one, IOLv2 is fixed and better now but I would use Iron IOU layer 2/3 image for switching at L3 and L2 be default;

good luck and have fun labbing !

Regards, ML
**Please Rate All Helpful Responses **

[kermitsfrog]

Unfortunately the cisco images are just to emulate cpe's - I am also emulating my normal network backbone consisting of nokia 7750/7790 and juniper mx980s for the route-sets and bgp backbone. so CML is not going to work for me. I rarely touch cisco stuff in my day-to-day, but for the purposes of our upcoming training I needed to be able to do a few things like this. Fortunately with a little toggling of the emu settings in GNS3 - everything seems to be communicating now - so we can continue building out our bgp peers for our training coming up soon.

Thank you again everyone 

[M02@rt37]

You're so welcome @kermitsfrog