6500 Creating vLAN

I am trying to create a vlan in Cisco Catalyst 6509
Here is my partial config with details on each
Below interface gets a cable in from route which has 10.250.250.1 IP assigned to it
interface FastEthernet6/24
description wireless 2651 inside - f0/1
switchport
switchport access vlan 200
switchport mode access
Below is config for vlan200
interface Vlan200
ip address 10.250.250.2 255.255.255.0
Below is ip route
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.1.1
ip route 10.250.250.0 255.255.255.0 10.250.250.1
ip route 192.168.60.0 255.255.255.0 192.168.1.3
Now i have switch connected with fiber of Gb3/1
interface GigabitEthernet3/1
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
Below is vlan1
interface Vlan1
ip address 192.168.25.1 255.255.255.0 secondary
ip address 192.168.4.1 255.255.255.0 secondary
ip address 192.168.3.2 255.255.255.0 secondary
ip address 192.168.3.1 255.255.255.0 secondary
ip address 192.168.2.1 255.255.255.0 secondary
ip address 192.168.75.1 255.255.255.0 secondary
ip address 10.0.255.1 255.255.255.0 secondary
ip address 192.168.17.1 255.255.255.0 secondary
ip address 192.168.1.2 255.255.255.0
ip helper-address 192.168.1.131
no ip redirects
ip route-cache flow
I am connecting device to switches and trying to ping 10.250.250.2 or 10.250.250.1 it is not connecting.
Can someone help me here?

do you has "ip address 10.250.250.2 255.255.255.0" at interface Vlan200, then 10.250.250.0/24 is directly connected to your switch, why do yo has:
ip route 10.250.250.0 255.255.255.0 10.250.250.1
About the details of your config, i'm not clear, can you post a Diagram of this network ?

Similar Messages

Creating Vlans at Core layer switches ?

Is there a need to create vlans at core layer switches ? If yes what are the pros and cons for this practice ?
Actually i have seen some networks doing that!

Well this is the topology that i'm working on.
we have implemented the 3 layer approach.
1. At access layer: Switches are all L2 (for sure :) )
2. At distribution layer: All switches are L3 are routes for incoming data.
3. At core we have 2 6500 switches. One is configured as L3 and all vlans are created in it. Second is just as regular L2 device.
and ofcourse there are some switch blocks for server farms and the likes.
My issue is
1. why don't we create vlans at distribution layer switches.
2. Why one core switch is acting as L2 and other is acting as L3. What will happen in case of failure to the one acting as L3.
Ps: the second issue just came up in my mind.

4250-sx connecting to 6500 for vlan pair mode

I am not sure if this question should be asked on the ids forum or the switching forum. Please let me know if it is the wrong place to be asking.
Could someone perhaps help? It the first time we are configuring this setup so we need some help in configuring the SX interface on a 6500 switch.
We would like to connect our 4250-SX ips sensor (5.1) for inline vlan pair mode to a 6500 catalyst running ios software. The switch has a fiber SC type connection. We would like to find a document that best describes how the interface on the switch should be configured for successful operation for this solution. Can someone point us to this document? We have been told that the port will need to be configured as an 802.1q trunk. Is this correct?
We would also like to filter all unneeded vlans from propagating on to that trunk. What is the best way to do this?
Thanks in advance

Whether the port is fiber or copper won't really matter much.
The first step is determine between which 2 vlans you will want to do inline vlan pair monitoring.
The most direct solution is to pick one existing vlan, and create one brand new vlan.
Now trunk both of these vlans on the switch port where the sensor is connected:
Here is a basic example configuration for that switch port:
interface GigabitEthernet1/1
switchport
switchport access vlan 1
switchport trunk native vlan 1
switchport trunk allowed vlan 100-101
switchport mode trunk
no ip address
no shutdown
exit
Vlan 100 was the existing vlan, and vlan 101 was the newly created vlan.
The vlan 1 settings were just to ensure the port was set back to the default of vlan 1 for the access vlan; the vlan 1 setting is not used in the vlan pairing and is not in the list of allowed vlans for the trunk port.
NOTE: You will see that the mode must be forced to trunk. Also be aware that depending on the port you may also have to force the trunk type to 802.1q:
"switchport trunk encapsulation dot1q"
Now on the sensor itself you will want to create an inline vlan pair on that SX interface, and pair vlan 100 with vlan 101.
Now remember that vlan 101 was a new vlan and is empty. So right the now the sensor is doing inline monitoring between that empty vlan and the rest of your network. The trick now is to move Some of the ports from the original vlan into that new vlan.
If this is your first time setting this up, then I suggest you try this with a very simple network with 3 pcs that all talk to each other on the same subnet. All 3 pcs would be in the same vlan to begin with. After the steps above are done to create the new vlan and create the inline vlan pair on the sensor, the next step is to move pcs into the other vlan. So for one PC change it's switch port configuration to move just that one PC from the original vlan (100) to the new vlan (101).
Wait a minute for spanning-tree to run.
Now ensure that the PCs from the orginal vlan can communicate to the PC in that new vlan.
NOTE: Both vlans are for the same IP subnet. The sensor does not IP route between the subnets, it just switches or brides packets between the 2 subnets. So the IPs on the PCs do not change as they get moved to the other vlan.
If you run some tests you will see that the sensor will see all traffic between the PC in the new vlan talking to either of the PCs in the original vlan. But you will also find that if the 2 PCs in the original vlan talk to each other, the sensor is unlikely to see that traffic (on occasion it will, but the sensor is just receiving a copy during broadcast and multicast situations).
Typical deployments will have something like a firewall in the original vlan, and the Internal network machines moved to the new vlan. Or if the switch itself is routing, then the switch will have it's ip address on the original vlan, and all of the other machines will be moved to the new vlan.
You also have the option of creating additional inline vlan pairs. To do this just create a new vlan for every original vlan where you want to add inline vlan pair monitoring.
Then just add those vlans to the trunk allowed vlan command and create the pair in the sensor configuration.
So let's say you also wanted to pair vlans 104 and 105 together. Then the command would look like:
switchport trunk allowed vlan 100-101,104-105
Your question about how do you keep the unneeded vlans from propogating is answered by that same command above. The "allowed vlan" list will restrict the trunk to only carrying those vlans listed.

How to create VLAN on Cisco PIX 6.3?

Hi,
how to create vlan on pix-6.3? i am bit confused.
how do i assign a single internet face with multiple ip address(not secondary IP address) for each & every vlan?
how to i connect to the switch, i mean if i put "switch port mode trunk" on the switch side, what command should i need on the PIX "inside" interface? in router the command is "encapsulation dot1Q 1"
also is there any restrictions that only limited vlans can be created or it is unlimited?

hi
When you configure your interface, you usualy do it like that
interface ethernet0 auto
interface ethernet1 auto
Let's say that ethernet1 is a trunk with 2 vlan and a native vlan, you need to add to your config:
interface ethernet1 vlan100 logical
interface ethernet1 vlan200 logical
After that you need to name those interfaces and set the security level.
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif vlan200 V200 security4
nameif vlan100 V100 security6
This configuration will give you an interface(eth1) with 1 native vlan(inside) and 2 tagged vlan(v200 and v100)
PIX will not negociate a trunk, your switch config is correct.

Problem in creating Vlan on 3550

hi,
I have done stacking between two 3550 siwtches. On one switch already a Vlan is created and network is running. On another switch I have created another Vlan using "int Vlan 79" command and gave an ip address for that VLAN. Enabled routing for this ip address and configured many ports to access this VLAN and connected PCs also. When I give command "sh vlan id 79", the message is "No VLAN is found in database". I have checked the VTP domain mode it was in client mode, then I converted it into server mode, reboot the switch and create Int Vlan again. Result was same. Then just for trying I put command "VLAN 79" in config mode and now everything is running fine. It is showing it in database also.
My question is when we put "Int Vlan" command, generally it creates the VLAN, then why I need to out VLAN 79 command.
This is problem related to concept.
Looking forward for the suggestions.
Thanks

Hi Kanupriya,
When you run the command " Int vlan 79 " and assign and IP to this, you are actually creating a SVI or the layer-3 virtual interface on the switch. This will not create Vlan 79 as a L-2 vlan in the Vlan database. When you run the command " Vlan 79 " that created the Vlan 79 in the Vlan database and you were able to see that Vlan interface. Remember to first define a L2- vlan in Vlan databse always, then configure the ports on this vlan and then define the L3 SVI.
You can also configure the L2 vlan by going into vlan datbase :
Switch# Vlan database
Switch(vlan)# Vlan 79 name V79
Switch(vlan)#exit
HTH,
-amit singh

Want to create vlan on asa5510 (8.2)

User want to create on 5 network , 100.x , 200.x , 210.x , 250.x , 220.x .at the ASA5510, no enough port for 5 network.
So I want to create 4 vlans on eth 0/3. I can create vlan but i cannot run this command "
switchport mode trunk"   "
"switchport trunk allowed vlan list" how can be done for that?Thanks
Acctually i want to use like this
ASA5510-----4 vlans on eth 0/3------switch----vlan200,vlan210,vlan250,vlan220.
Ko Htwe

You don't have to configure "switchport mode trunk" on the ASA interface.
You just have to configure the sub interfaces under eth0/3 and configure vlan under that interface.
Eg:
interface eth0/3.200
   vlan 200
   ip address 200.200.200.1 255.255.255.0
   nameif vlan200-dmz
   security-level 50
interface eth0/3.210
   vlan 210
   ip address 210.210.210.1 255.255.255.0
   nameif vlan210-dmz
   security-level 55
Hope that helps.

Can create vlan group on eth0 after OVM Server installation?

Hi,
I have installed OVM server to use eth0 without vlan segment for ovm manager to manage OVM server.
Now if I want to use eth0 for virtual machine management purpose as well, can I edit this network, create vlan group on eth0,
one for server managent + cluster heartbeat + live migration
one for virtual machine management?
Or I have to reinstall OVM server with vlan segment on eth0?
Appreciate any comment on this.

it was the wrong mfc42.dll version

Can't create VLAN's with Cisco Network Assistant

Hello everyone
I have a problem with my newest Switch, a WS-C2960X-48TS-L
Normaly I can programm all my Switches with Cisco Network Assistant. But now I have a problem with creating VLAN's. I can create them, safe them but after a refresh, all the new VLAN's are gone!
I updated the CNA to the newest Build 6.0 and updated the Switch to 15.2(2)E, but nothing helps!
Over the CLI I can do everything, but this is not a option for me! To programm sometimes a switch CNA is perfect for me! If it works!!
Thanks
Tobi

yes I can programm the vlan's over CLI. That's works. I have not tested this if its really works, but the VLAN's are programmed.
hmm I checked the STP / VTP settings with a second identical Switch, but there are no differents. Made a backup of one Switch and restore on the other One, but I'm still not able to create VLAN's.
however, I contacted my vendor today, he tell me that it shouldt be a problem to take back the switch.
Best regards
Tobi

Help create VLAN for home use.

I use Cisco switch SG300 and SG200 series. I set my home network as attach picture.
I want set up VLAN with these condition
1.Every port can connect to internet through ADSL router.
2.VLAN10( Home alarm and IP camera ) can access by internat, connect by access point and PC file server
3.Every port can connect the PC file server
I am new for network and fail to try setup myself and not understand static route.
Thank you.
Jarey
[email protected]

Hi Jarey,
Are you sure you want to do this on the switch as opposed to the router? Are you going to use static IP addresses for the vlans or do you want your router to issue DHCP?
To proceed, using the switch for inter-vlan routing, make sure the SG300 is in layer 3 mode.
1. If you are currently in layer 2 mode, open a CLI connection and issue command:
set system mode router
Take note that this will delete your current config and the switch will reboot.
2. Create the vlans on your switch under VLAN Management -> create vlan
3. Go to IP Configuration -> ipv4 interface and assign each vlan a static IP for the switch in the subnet for the new vlan
4. Vlan Management -> Interface settings. I would leave all the ports as trunk ports, or change the ports to trunk if you have previously changed them.
5. Vlan Management -> Port VLAN membership. Assign your vlans to the appropriate ports.
6. When everything is all plugged in, you should be able to see the switch created static routes for you already under IP Configuration -> IPV4 static routes. Make sure all your subnets are there and are showing route type local
7. You may need to add a route such as 0.0.0.0 with the next hop being your router
At this point, you should be up and running, with all vlans connected to each other and to the internet.
If you want to restrict access across the vlans, you'll have to create access control lists.
You need to first create an ACL (Access control -> IPV4 based ACL) and give it a name. then go over to IPV4 based ACE where you put the actual access control rules.
This is a sample set of rules I made, it will block all access between two subnets (each vlan you created above will have to be its own subnet) and allow certain traffic such as 3389 - remote desktop, etc. You'll need to customize based upon your needs and subnet IPs. So for ex, to allow the Xboxes to access the file server, rather than any - any, you put the xbox subnet or specific IPs as the source, the file server as the destination, and the ports used as source ports. Remember to make the converse of the rule as well.
Then, go to Access Control -> ACL bindings and bind the access control list to the applicable ports.
Hope that helps, good luck with your set up.
Best,
David
Please remember to rate helpful posts and identify correct answers.

Creating VLAN on Cisco 3800 Series

Hello
I am new to networking. We have a Cisco 3800 series router with 64 ports. We have connected servers and PC's directly to the back of the router. Almost all of the ports are used with the exception of few. We would like to create a VLAN for the remaining few ports. I am able to telnet to the router or connect directly using hyper terminal.
I have been told that we cannot create VLAN's directly on the router. For that purpose we need to first get a switch and connect the switch to the router, then create VLAN’s using the switch. Can someone please provide some tips? Any suggestions would be nice…Thanks

Appreciate you getting back. Here is the "show vlan-switch" output
----------------------->
#show vlan-switch
VLAN Name                             Status    Ports
1    default                          active
1002 fddi-default                     active
1003 token-ring-default               active
1004 fddinet-default                  active
1005 trnet-default                    active
VLAN Type SAID       MTU   Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
1    enet 100001     1500 -      -      -        -    -        1002   1003
1002 fddi 101002     1500 -      -      -        -    -        1      1003
1003 tr    101003     1500 1005   0      -        -    srb      1      1002
1004 fdnet 101004     1500 -      -      1        ibm -        0      0
1005 trnet 101005     1500 -      -      1        ibm -        0      0
---------------------->
As before I do not see any VLAN's set up. How come all the ports are not showing up on default VLAN 1. Maybe I can create a new VLAN and assign 2 or 3 ports to it. Please advise...Thanks

Creating VLAN

How is VLANs configured on a switch ? What are the parameters defined while creating a VLAN/ Voice VLAN ? Since switch operates on layer 2 switch, is it required to define vlans on router as well. This might be very simple and basics of networking. Need to understand to clarify my doubts.
Thanks
Feroz
Sent from Cisco Technical Support iPhone App

HI Feroz,
VLAN is a virtual LAN. In technical terms, a VLAN is a broadcast domain created by switches. Normally, it is a router creating that broadcast domain. With VLAN’s, a switch can create the broadcast domain.
This works by, you, the administrator, putting some switch ports in a VLAN other than 1, the default VLAN. All ports in a single VLAN are in a single broadcast domain.
Because switches can talk to each other, some ports on switch A can be in VLAN 10 and other ports on switch B can be in VLAN 10. Broadcasts between these devices will not be seen on any other port in any other VLAN, other than 10. However, these devices can all communicate because they are on the same VLAN. Without additional configuration, they would not be able to communicate with any other devices, not in their VLAN.
Please find the details below:
Vlan on Switches:-
Two types of Vlan(Layer 2 - Layer3)
Layer 2 vlan:
config t# vlan
Eg:
Let’s say we wanted to create VLAN’s 5 and 10. We want to put ports 2 in VLAN 5 (Marketing) and port 3 in VLAN 10 (Human Resources). On a Cisco 2950 switch, here is how you would do it:
# vlan 5
#name marketing
vlan 10
name humanresouces
exit
int f0/2
switchport mode access
switchport access vlan 5
int f0/3
switchport mode access
switchport access vlan 10
Layer 3:
conf t# interface vlan 2
followed by ip address.
Please find below link which explains complete info on VLans.
http://www.cisco.com/en/US/docs/switches/lan/catalyst2950/software/release/12.1_9_ea1/configuration/guide/swvlan.html
2- Vlan on Router:
A vlan configuration on a router is slightly different than on a switch. On a switch, you would create the vlan and then the routed vlan interface.
On a router you tie a vlan to a subinterface. You need to create the subinterface and then do the encapsulation dot1q command. This command basically assigned the vlan to the subinterface. In this example, there are 2 vlans, vlan 100 and 201. On the eth 0/0 interface, I created two subinterfaces. fastethernet0/0.100 and f0/0.201. Notice that I matched the subinterface number with the vlan ID. You do not have to do this, but it is a best practice and really helps you as the administrator keep things organized. So, under f0/0.100, there is the encapsulation dot1q 100, which basically binds vlan 100 to subinterface f0/0.100, then I assigned the IP. The same is for the other subinterface. So the router is trunking two vlans on its f0/0 interface, vlan's 100 and 201.
interface FastEthernet0/0
no ip address
speed 100
full-duplex
interface FastEthernet0/0.100
description test Network
encapsulation dot1Q 100
ip address 192.168.102.1 255.255.255.128
no snmp trap link-status
interface FastEthernet0/0.201
description Office
encapsulation dot1Q 201
ip address 205.127.102.129 255.255.255.128
no snmp trap link-status
Kindly go through the same and reply back if you need any clarification on the same.
HTH
Regards
Inayath
*Plz rate the usefull posts.

Create VLAN on 3750 using SNMP

I'm trying to create a VLAN on a 3750 using SNMP. The document i've found is rather vague and from 2005. Has anybody done this successfully and if so can you share the process?
From what I understand you have to set the "vtpVlanEditOperation" to the desired mode but each time I set the integer to 2 for copy is get either bad security type or bad object type. Any help would be appreciated.
Here are some commands i've tried.
$ /usr/bin/snmpset -c {writeString} test 10.150.150.20 1.3.6.1.4.1.9.9.46.1.4.1.1.1 INTEGER 2
10.150.150.20: Bad object type: 1
$ /usr/bin/snmpset -c {writeString} 10.150.150.20 1.3.6.1.4.1.9.9.46.1.4.1.1.1 INTEGER 2
snmpset: No securityName specified
Thanks!

Also, please check and verify the following in your steps:
(a) The switch MUST be in a VTP domain with "server" mode. If the switch has client or other mode, it will not work. Check your "show vtp domain" command and see what your switch mode is in. --> This is usually the problem in most cases
(b) snmpset to build a mib table can be time sensitive. That is you need to wait.
(c) Did you follow these steps:
1. Destroy the row first:
snmpset -c private 14.32.6.12 vtpVlanEditRowStatus.1.111 integer 6
You should see something like:
CISCO-VTP-MIB::vtpVlanEditRowStatus.1.111 = INTEGER: destroy(6)
2. Set vtpVlanEditOperation to copy mode with an owner name:
snmpset -c private 14.32.6.12 vtpVlanEditOperation.1 integer 2 vtpVlanEditBufferOwner.1 s "testvlan"
You should see something like:
CISCO-VTP-MIB::vtpVlanEditOperation.1 = INTEGER: copy(2)
CISCO-VTP-MIB::vtpVlanEditBufferOwner.1 = STRING: "testvlan"
3. Set the row status to createAndGo, and build the table. For VLAN 111, vtpVlanEditDot10Said is 111+100000=100111 which in hex is 0001870F:
snmpset -c private 14.32.6.12 vtpVlanEditRowStatus.1.111 integer 4 vtpVlanEditType.1.111
integer 1 vtpVlanEditName.1.111 s "testvlan-vlan" vtpVlanEditDot10Said.1.111 x 0001870F
You should see something like:
CISCO-VTP-MIB::vtpVlanEditRowStatus.1.111 = INTEGER: createAndGo(4)
CISCO-VTP-MIB::vtpVlanEditType.1.111 = INTEGER: ethernet(1)
CISCO-VTP-MIB::vtpVlanEditName.1.111 = STRING: testvlan-vlan
CISCO-VTP-MIB::vtpVlanEditDot10Said.1.111 = Hex-STRING: 00 01 87 0F
4. Check the vtpVlanApplyStatus:
snmpwalk -c public 14.32.6.12 vtpVlanApplyStatus
You should see "succeeded(2)":
CISCO-VTP-MIB::vtpVlanApplyStatus.1 = INTEGER: succeeded(2)
5. Now set vtpVlanEditOperation to "apply" mode:
snmpset -c private 14.32.6.12 vtpVlanEditOperation.1 integer 3
You should see something like:
CISCO-VTP-MIB::vtpVlanEditOperation.1 = INTEGER: apply(3)
6. Now check the status again, and it should be still "succeeded(2)":
snmpwalk -c public 14.32.6.12 vtpVlanApplyStatus
CISCO-VTP-MIB::vtpVlanApplyStatus.1 = INTEGER: succeeded(2)
7. Now check your switch with "show vlan" and you should see a new VLAN 111.
8. Finally you can release the newly created VLAN 111:
snmpset -c private 14.32.6.12 vtpVlanEditOperation.1 integer 4
You should see something like:
CISCO-VTP-MIB::vtpVlanEditOperation.1 = INTEGER: release(4)
-Thanks
Vinod
**Encourage Contributors for free. RATE Them :) **

Create vlan on SRW2024

Hi guys,
I need help the proper way to create vlan on SRW2024....
i have 3 segments vlan 10,20 and 30...how to create and make sure this 3 vlan can ping each other, the proper steps, i've tried to follow the manual but have problem to understand the term using in linksys.
thank you guys

You won't be able to "ping" the vlan's from the same switch. Also, you can only setup one vlan from which the switch can be managed. This is defined under the SETUP->NETWORK SETTINGS section. Look for "Management VLAN." You'll only be able to ping the switch from ports assigned to that VLAN.
I'm betting you have no problems creating VLANs. What can be unclear is how to assign ports.
To add a port to a VLAN...
1-identify port
2-go into "VLAN Management" and then "Ports to VLAN"
3-go into the VLAN you want the port to be in (from the SELECT VLAN drop down)
4-set switch port mode to "Access" (if not already)
5-set membership to "UnTagged"
6-ensure the trunk is tagged in this VLAN
7-save
To MOVE a port to a different VLAN...
1-identify port
2-go into "VLAN Management" and then "Ports to VLAN"
3-go into the VLAN you want the port to be in (from the SELECT VLAN drop down)
4-set membership to "UnTagged"
5-save
As I've said before on this forum, I've found it is sometimes more straight forward with the srw2024 to setup a TFTP server on your PC...backup the config...edit the config...upload new config...reboot switch.

UC320W create vlan on srw2024P

Any documentation for creating the vlan for voice on the srw2024 and the required settings? Thnaks

You won't be able to "ping" the vlan's from the same switch. Also, you can only setup one vlan from which the switch can be managed. This is defined under the SETUP->NETWORK SETTINGS section. Look for "Management VLAN." You'll only be able to ping the switch from ports assigned to that VLAN.
I'm betting you have no problems creating VLANs. What can be unclear is how to assign ports.
To add a port to a VLAN...
1-identify port
2-go into "VLAN Management" and then "Ports to VLAN"
3-go into the VLAN you want the port to be in (from the SELECT VLAN drop down)
4-set switch port mode to "Access" (if not already)
5-set membership to "UnTagged"
6-ensure the trunk is tagged in this VLAN
7-save
To MOVE a port to a different VLAN...
1-identify port
2-go into "VLAN Management" and then "Ports to VLAN"
3-go into the VLAN you want the port to be in (from the SELECT VLAN drop down)
4-set membership to "UnTagged"
5-save
As I've said before on this forum, I've found it is sometimes more straight forward with the srw2024 to setup a TFTP server on your PC...backup the config...edit the config...upload new config...reboot switch.

Creating VLANs on established Pt to Multi Pt links

Hi all,
I have an exisiting Pt to Multipoint network of 1410 bridges. Connected to each bridge is a 1200 AP. I want to put the clients on one VLAN and the "equipment" on another VLAN.
I think I understand that you have to configure both interfaces on each device, starting with the furthest away device finally doing the root bridge last.
Instead of using the GUI to configure I am going to use the CLI. What I want to know is if I use the CLI and give the commands including a new SSID will I lose contact with the radio after I issue the command but havent finished the config?
I want to do this from the NOC and avoid serious ladder work.
Thanks,
Kim

It is a client thing, isn't it?
The first time they start the application the get asked.
If you want to do it afterwards then you run javaws and select Application/Create shortcuts.
I don't know of a way to force this from the jnlp.

6500 Creating vLAN

Similar Messages

Maybe you are looking for