Help configuring trunking port in Packet Tracer

[Clay Plaga]

I'm practicing a configuration in packet tracer that I will recreate on a real 2960 switch. I'm trying to configure an interface on a 2960 switch as a trunk port that will be connected to a Cisco aironet 700 access point. I want the 2960 interface to pass traffic on 2 vlan's, 10 and 20.   I have the vlan's configured on the 2960 in packet tracer. I think  I also have the interface configured as a trunking port, but I'm not sure I'm using the correct show command to confirm the trunking port is set up correctly. Can someone help me with the information I need to get started with this configuration?

Thank You.

[Jon Marshall]

int <x/y>
switchport mode trunk
switchport trunk allowed vlan 10,20

to view it -

"sh int trunk"

Jon

[Clay Plaga]

Thank You for the help. I have configured the switch as you instructed, but the "sh int trunk" command doesn't produce an output. Am I in the wrong mode to use the command? I've included a screen shot.

I am using PT 6.2

[Jon Marshall]

Is the interface up and connected to something ?

Jon

[Clay Plaga]

No it is not. When I come back from lunch, I will connect an access point-PT to that interface in packet tracer. Thanks.

[Clay Plaga]

Thank You very much, I can see it now. I have two questions.

1.Is the vlan supposed to be administratively down, and if not, how do I bring it up? 

(screen shot included)

2. This is about the native vlan. From what I understand, native vlan's pass traffic with the frames untagged. If the frame is untagged with no vlan ID number, how can it be part of a vlan? What is it used for. I'm new to all this so I hope I'm asking the question correctly

.

Thanks again.

[Jon Marshall]

1) it's not the vlan that is down, it is the L3 interface for that vlan.

Whether or not you need it up depends on whether you are using that vlan for either management or your 2960 is capable of routing and you have clients in that vlan.

2) the native vlan is simply the vlan that is untagged on the trunk link. It is still a vlan and by default it is vlan 1 that is untagged.

You must make sure that the device on the other end of the trunk agrees on the native vlan because there is no vlan tag. So they must agree on the native vlan because they have no other way of knowing which vlan untagged frames are meant to be in.

If this was a switch you were connecting it wouldn't really matter (as long as they matched) other than the fact you usually want to use a different vlan as the native one but it would still work.

I'm not familiar with APs but I seem to recall reading something about APs, the native vlan and management so you may need to use the native vlan for management.

Sorry I can't be more precise but I don't really have much experience with wireless.

Jon

[Clay Plaga]

Thanks for all the information.

1) it's not the vlan that is down, it is the L3 interface for that vlan

So I think your saying I would have to set up a router on a stick, or have a multi layer switch to bring up the interface that the AP is connected to. I'm going to mess around with it in PT, and see if I can figure it out.

Thanks.

[InayathUlla Sharieff]

Please note the svi to be up, the blah needs to be present in clean database and second:-the blah needs to have one active interface in it.

Hth

Regards

Inayath