SIP 7960 to non-Cisco Switch

Does anyone know if a 7960 (SIP) phone can connect to a non-Cisco switch and separate the Voice traffic from the access port traffic?
I tried connecting a 7960 to a baystack 450T, configuring the switchport as a "tagged trunk", and then changing the Admin Vlan ID on the phone to the desired voice vlan. It looks as though the switch wants the access port traffic to be tagged as well.
Any help would be greatly appreciated!
Thanks,
Darin

Hi !
You need to configure a 802.1q trunk on your non-cisco switch. The 802.1q native vlan should be the one the PC is in. The voice vlan will be tagged.
Configure all parameters (like voice-vlan-id etc) on the phone manually (obviously CDP does not work). I have done it and it works fine (but i never tried on the switch you mentioned).
Inline Power will also not work because the 7960 is not 802.3af compliant (yet).
Mike

Similar Messages

Interconnecting cisco switches with non-cisco switches

I need help concerning interconnecting two Cisco switches (3550s) using a non-Cisco switch or hub on the LAN. I have noticed that the two Cisco switches connected using a non-Cisco switch are able to communicate well, however a PC connected to the non-Cisco switch/hub can not ping any device on the LAN. The non-Cisco device is a working one. When the two Cisco switches are connected using a Cisco switch, PCs connected to the interconnecting switch are able to ping. Whats the explanation? Please help.

Building configuration...
Current configuration : 3342 bytes
! No configuration change since last restart
version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
clock timezone GMT -2
ip subnet-zero
ip rcmd rcp-enable
ip rcmd remote-username cwuser
spanning-tree mode pvst
spanning-tree extend system-id
interface FastEthernet0/1
switchport mode dynamic desirable
interface FastEthernet0/2
switchport mode dynamic desirable
interface FastEthernet0/3
switchport mode dynamic desirable
interface FastEthernet0/4
switchport mode dynamic desirable
interface FastEthernet0/5
switchport mode dynamic desirable
interface FastEthernet0/6
switchport mode dynamic desirable
interface FastEthernet0/7
switchport mode dynamic desirable
interface FastEthernet0/8
switchport mode dynamic desirable
interface FastEthernet0/9
switchport mode dynamic desirable
interface FastEthernet0/10
switchport mode dynamic desirable
interface FastEthernet0/11
switchport mode dynamic desirable
interface FastEthernet0/12
switchport mode dynamic desirable
interface FastEthernet0/13
switchport mode dynamic desirable
interface FastEthernet0/14
switchport mode dynamic desirable
interface FastEthernet0/15
switchport mode dynamic desirable
interface FastEthernet0/16
switchport mode dynamic desirable
interface FastEthernet0/17
switchport mode dynamic desirable
interface FastEthernet0/18
switchport mode dynamic desirable
interface FastEthernet0/19
switchport mode dynamic desirable
interface FastEthernet0/20
switchport mode dynamic desirable
interface FastEthernet0/21
switchport mode dynamic desirable
interface FastEthernet0/22
switchport mode dynamic desirable
interface FastEthernet0/23
switchport mode dynamic desirable
interface FastEthernet0/24
switchport mode dynamic desirable
interface GigabitEthernet0/1
switchport mode dynamic desirable
interface GigabitEthernet0/2
switchport mode dynamic desirable
interface Vlan1
ip address
ip default-gateway
ip classless
ip http server
snmp-server community
snmp-server community
snmp-server location
snmp-server system-shutdown
snmp-server enable traps snmp authentication warmstart linkdown linkup coldstart
snmp-server enable traps config
snmp-server enable traps entity
snmp-server enable traps flash insertion removal
snmp-server enable traps bridge
snmp-server enable traps stpx
snmp-server enable traps rtr
snmp-server enable traps port-security
snmp-server enable traps vtp
snmp-server enable traps vlancreate
snmp-server enable traps vlandelete
snmp-server enable traps envmon fan shutdown supply temperature status
snmp-server enable traps MAC-Notification
snmp-server enable traps hsrp
snmp-server enable traps cluster
snmp-server enable traps copy-config
snmp-server enable traps syslog
snmp-server enable traps vlan-membership
line con 0
line vty 0 4
login
line vty 5 15
login
ntp clock-period 17180064
end

Passing Voice VLAN through a non-Cisco switch

Hi All,
Will a non-Cisco switch (no 802.1q support) that is putted beetween Cisco IP Telephone and Cisco Catalyst switch (which is configured with auxilary Voice Vlan) pass voice vlan frames and CDP?

Any switch should pass on either ISL(which is cisco properitary and hence not supported on non-Cisco) or IEEE 802.1Q frames or else it cannot support voice vlan support . And non-Cisco switches do not support CDP as it is once again Cisco proprietary protocol.

Ce 500 non-cisco switch

How should I configure the smartport on a catalyst express 500 switch if I am connecting a non-cisco switch like a small linksys. I dont think I can make the smartport a switch because it tries to trunk?? right??
And if I leave it as a PC it complains abouting having to many devices connected to it.
Would having it configured as something like an access point work??

Now, I noticed something very odd, I kept the switch option selected on the port on the ce 500 that the linksys was plugged in to and the devices plugged in downstream behind the linksys all kept the correct VLAN assignment. Phones were in the voice vlan and PC's were in the data vlan. Does not really make sense to me how this is working??

Non Cisco Switches

Dear ALL,
I am an IT Potfessional, Doing Network + . I have a questions:
1) Do Non Cisco Switches have Access and Trunk ports. What i mean is do non cisco switches distinguish between ethernet prots as trunk and access.
2) Do we need Cross talk cable for Connectine two non cisco switches preferably D-Link . Also How to interconnect a Cisco switch wioth non cisco switch.
Regards
Haseeb

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
As Daniel noted "decent" switches, i.e. manageable and supporting VLANs, will generally support VLAN tagging ports using the 801.2q standard. (NB: this standard allows VLAN tagging between different vendors.) Switches that support VLANs will distinguish between untagged (edge) ports (e.g. Cisco access) and the tagged ports (e.g. a Cisco trunk), but as Daniel also noted, their terminology might be different.
As Leo noted, many switches offer auto MDI/MDI-X. Surprisingly, this feature was often seen on unmanageable switches before it was seen on manageable switches. Also on older unmanageable switches, you might find a pair of physical ports that are the same logical port, one wired MDI and other wired MDI-X or you might find some button to change one port's MDI to/from MDI-X. Such "special" ports are often the "uplink" port. (NB: the purpose of the "uplink" port was to allow connecting it to another switch whether you had a straight through or cross over cable.)
If you do have a switch supporting auto MDI/MDI-X, or one with the earlier physical MDI/MDI-X options, you only need one switch, not both with such a feature, to support either a straight through or cross over cable. Of course, both switches might have such an option, which is fine too. Only if both switches are "hard wired", you'll need a cross over cable for a switch to switch connection.

ISE web auth for non-cisco switch(D-link 3528)

Is it possible to use ISE(inline posture node) to redirect the wired users to ISE guest portal ?
And the wired users will get full network access after they pass the web auth.

you can use ISE ln-line posture node with 3rd part switches
RADIUS access device must supply the following RADIUS attributes:
    Calling-Station-Id (for MAC_ADDRESS)
    User-Name
    NAS-Port-Type
    RADIUS accounting message must have the Framed-IP-Address attribute
VLAN, DACL features can be used but again it depends on switch models let us know specific switch models . Certain advanced use cases, such as those that involve posture assessment, profiling, and web authentication, are not consistently available with non-Cisco devices or may provide limited functionality,

Stacking a non-Cisco Switch with a Catalyst Express 500 switch

We are using a Cisco Catalyst Express 500 Ethernet switch and need to add another switch to get a few more ports. Is is possible to stack a Catalyst Express 500 Ethernet switch with a non-Cisco Ethernet switch. If so, is there any Cisco documentation telling how to do this?

If by stack, you mean connect the two switches via Ethernet ports, yes you should be able to do that. Depending on the port capabilities of the switches, and whether they have any special uplink ports, you might need to use a different Ethernet connecting cable (cross-over vs. straight thru).

WLC4402 connect to non-cisco switch?

I have 2 WLC4402-50 connected to an Extreme Black Diamond chassis, using GLC-T. I have configured LAG on the controllers to support the number of AP's needed and I have configured the ports on the switch to use LaCP aggregation because that is what is available. Is this a supported configuration or do I just need to leave those ports as non-LaCP ports?

just to help out anyone else using extreme, here is how I got it to work
first I define the src-dst ip load sharing like this
Switch#. configure sharing address-based L2_L3_CHK_SUM
and then I configure sharing on the ports (the port number between the sharing and grouping is just the master port number for the share)
Switch#. enable sharing 3:26 grouping 3:26, 3:56 algorithm address-based
Switch#. enable sharing 3:28 grouping 3:28, 3:58 algorithm address-based
and then I do the vlan config like
Switch#. create vlan "Wireless"
Switch#. configure vlan Wireless tag 250
Switch#. config vlan "default" add ports 3:26, 3:28 untagged
Switch#. config vlan "Wireless" add ports 3:26, 3:58 tag

Using FCoE connection to non Cisco switches

Hello,
does anyone know what port configuration needs to be configured on a Nexus switch that is connected to say Brocade switch or any other vendor that supports FCoE. I have created VLAN to VSAN mapping, i assume next step is to create a vfc device ? Since this is not connection to an initiator or a target but another FCoE capable switch, how do i need to configure this vfc ? Any tips ?
Thanks

Hi,
Looks like from the document that you referenced that this switch runs in NPV mode for FCoE:
FCoE features
Fibre Channel over Ethernet (FCoE*)
FIP & FCoE packets are all forwarded when DCB is configured
* FCoE frames as defined by T11 Committee
So, I would configure the Cisco Nexus switch for FCoE and NPIV
Configure the Nexus 5000 for FCoE and NPIV
There are several procedures that are required in order to configure the Nexus 5000 for FCoE and NPIV:
    Enable Feature FCoE
    Enable N Port Identifier Virtualization (NPIV) on the Nexus 5000
    Enable Nexus 5000 Quality of Service (QoS) for FCoE
    Enable Link Layer Discovery Protocol (LLDP)
    Configure VLAN
    Configure VSAN
    Map the VLAN to VSAN
Example:
feature lldp
feature fcoe
feature npiv
interface vfc130
bind interface Ethernet1/30
switchport mode F
no shutdown
interface Ethernet1/30
switchport mode trunk
switchport trunk allowed vlan 1,100
spanning-tree port type edge trunk
vsan database
vsan 100 interface vfc130
vlan 100
fcoe vsan 100
Example of QOS:
system qos
service-policy type qos input fcoe-default-in-policy
service-policy type queuing input fcoe-default-in-policy
service-policy type queuing output fcoe-default-out-policy
service-policy type network-qos fcoe-default-nq-policy
Best regards,
Jim

Configuring Switch for CCA is behind non-Cisco phone, NAC OOB VGW Deployment

Hi,
I need to configure the edge switch port to keep serving non-Cisco IP phone on deploying NAC as OOB VGW.
I appreciate your advise, but make sure 802.1x solution as the last option.
Thanks
Mike

Hi,
Please look at the config guide:
http://www.cisco.com/en/US/docs/security/nac/appliance/configuration_guide/48/cam/m_oob.html.
HTH,
Tiago
If this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it.

Does Supervisor Engine 6L-E compatible with Cisco Ws-C4506 Non-E switch?

Does Supervisor Engine 6L-E compatible with Cisco Ws-C4506 Non-E switch?

Yes, it is compatible with non-e chassis.
see below:
The Cisco Catalyst 4500 Supervisor Engine 6L-E is also compatible with classic Cisco Catalyst 4500 line cards, chassis (3-, 6-, and 7-slot), and power supplies, providing full investment protection.
link to data sheet:
http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-4500-series-switches/data_sheet_c78-530856.html
HTH

Using 802.1X and non-Cisco IP Phones

Hi there,
Having some questions about an 802.1x/non-Cisco ip phone setup and was hoping to find some answers/user-experience with this setup.
Main questions i'm facing:
1) When using non-Cisco ip phones (eg Nortel or Siemens) and a previous authorized client connected behind this ip phone gets disconnected. What will this action do with the authorized state of 802.1X on the switch port? WIll it stay authorized until the reauth timer expires or does it reject communication from any other device?
2) What about EAPOL-Logoff messages from the ip phone to the switch. Are these only used by Cisco phones when they experience a link-status change on data ports?
Thanks for sharing your thoughts

Overall, you need to try and deal with the fact that a machine can disappear from the network and the network may not know about it directly (i.e. Link doesn't go down).
I have no idea what other phones do, but Cisco phones send an EAPOL-Logoff when something is unplugged. This lets the switch know directly, and 1X session start is torn down immediately, closing what would be a security hole.
Fundamentally, re-auth is a workaround only, and this is not the reason to enable re-auth to begin with.
If your phone doesn't send an EAPOL-Logoff in this case, the switch might be left thinking an attack is underway when someone else tries to plug in (with presumably a different MAC). You do NOT want this to occur.
Hope this helps,

MARS topology in non-Cisco environment

In a heterogeneous, non-Cisco environment (e.g. Dell switches, Sidewinder firewall), is it possible to obtain accurate topology/visualization information? If so, how is this accomplished? Any other best-practices/gotchas for getting the most out of MARS in such environment would be helpful as well. Thank you.

We don't really have any topology information in MARS, and for the most part don't pay much attention to the topology or attack graphs/charts. Don't even use the summary page. We don't use the MARS for anything but collecting events. Maybe I don't know what I'm missing, but we get along just fine without(we even have a mostly Cisco network).

WLC in a non-Cisco network

I'm planning to use a Cisco WLC 5508 in a non-Cisco core network (switch and routers) and I'm wondering about the problems I can have.
For the moment, I can only think that I can't have CDP (Cisco Discovery Protocol) in the new core network (access switchs are cisco).
So, do you need CDP to run a Cisco Controller Based WLAN?
Maybe for Rogue Switchport tracing? Anything else?
Can I use a WLC connected to a non-Cisco core network?
More trouble?
Thanks

Cisco wlc's do not use LACP, LAG is non-negotiated, just on. 5508 also require 1g ports, it will not connect to anything less than this.
http://www.cisco.com/en/US/partner/docs/wireless/controller/7.0MR1/configuration/guide/cg_ports_interfaces.html#wp1182892
As for LWAPP/CAPWAP, you will need to make sure that if yo uare going through a firewall that UDP ports 12222/12223 for LWAPP and UDP port 5246/5247 are not blocked. You can use option43 on your DHCP server for the APs to find the controller.
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00808714fe.shtml
OR
DNS discovery—The access point can discover controllers through your domain name server (DNS). For the access point to do so, you must configure your DNS to return controller IP addresses in response to CISCO-LWAPP-CONTROLLER.localdomain or CISCO-CAPWAP-CONTROLLER.localdomain, where localdomain
is the access point domain name. When an access point receives an IP address and DNS information from a DHCP server, it contacts the DNS to resolve CISCO-LWAPP-CONTROLLER.localdomain or CISCO-CAPWAP-CONTROLLER.localdomain

Unable to Telnet / SSH to a particular cisco switch

Hello,
I have an unusual issue that I just can't seem to track down. We have a Windows Server 2008 R2 box that is unable to telnet or ssh to one switch in our network.
Server IP: 10.0.0.74
Cisco Switch IP: 10.1.0.7
I am able to access all other switches/routers on the 10.1.0.x network, but not this one. I ping and tracert by ip address and name.
We have a number other servers on our network and they all can access this switch
Example:
a. 10.0.0.73 can telnet/ssh to 10.1.0.7
b. 10.0.0.72 can telnet/ssh to 10.1.0.7
c. 10.0.0.50 can telnet/ssh to 10.1.0.7
d. My workstation (10.0.250.213) can telnet/ssh to 10.1.0.7
If anyone can help with troubleshooting further, I would greatly appreciate it.

Thanks for the reply Philippe! Here is the route print
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.74 266
10.0.0.0 255.255.0.0 On-link 10.0.0.74 266
10.0.0.74 255.255.255.255 On-link 10.0.0.74 266
10.0.255.255 255.255.255.255 On-link 10.0.0.74 266
10.10.0.0 255.255.0.0 On-link 10.0.0.74 266
10.10.0.74 255.255.255.255 On-link 10.0.0.74 266
10.10.255.255 255.255.255.255 On-link 10.0.0.74 266
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 10.0.0.74 266
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 10.0.0.74 266
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 10.0.0.2 Default
===========================================================================
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
1 306 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
Firewall is disabled and there is no active antivirus. Im pretty sure port blocking is not the issue. I am able to ssh and telnet from this box to every other switch/router in our network.
This server has Solarwinds on it and tracks the health of our network (servers, routers, switches, ups, ect.). The only reason we noticed an issue is because it stopped backing up the config for this particular switch. All other switchs/routers
config is backed up to this server every morning at 2:00AM.
With solarwinds, this server is also able to communicate with this switch via snmp / icmp and ping.
Thanks again for the help!

SIP 7960 to non-Cisco Switch

Similar Messages

Maybe you are looking for