WCCP on Subinterfaces and Switch Modules with VLANs

When using WCCP redirects for Ethernet, do the redirect commands go on the subinterfaces if your trunking on a router FE? Also, if using a NM-16ESW, do the commands go on the physical interfaces, or on the VLAN?

HI,
if you are using WCCP you have to configure it on an per interface basis. If you are having 3 subinterfaces you want to apply wccp to, you have to configure it 3 times (once per interface).
This is because you are having 3 different IP-Address on the 3 subinterfaces and you do not necessarily have an IP-address configured on the main interface. Additionally you might want to handle HTTP traffic different on the subinterfaces.
Kind Regards,
Joerg

Similar Messages

SG-300 28P switches problem with VLAN Data and Voice, working all the time as Voice VLAN

Hi Everyone,
Thank you very much for your help in advance. I’m pulling my hair to fix the problem.
I just got the new SG-300 28P switches. My Bios ordered for me. I did not know how it runs until now... not an IOS based. I really do not know how to configure it.
I have 2 VLAN are Data and Voice.
-          Data VLAN ID is 2 IP 192.168.2.X/255.255.255.0
-          Voice VLAN ID is 200 IP 192.168.22.X/255.255.255.0
-          I created two vlans, in switch, Data and Voice.
-          On the port number 28, it is trunk by default, so I add Data vlan ID 2 tagged.
-          On the port number 26, it is trunk by default, so I add Voice vlan ID 200 tagged.
-          On the port number 27, I add Data vlan ID 2 tagged for Data vlan out.
-          Port settings No.1
I set it up as Trunk with Data vlan 2 untagged, and 200 Tagged (voice vlan). I plugged in a phone with a pc attached. But the PC will get to the vlan 200 to get the DHCP address, but no from vlan 2. The Phone works with correct vlan ip.
-          Port settings No.2
Trunk with vlan 1UP, 2T, and 200T. The phone is even worse. Would never pick up any IP from DHCP.
-          Port settings No.3
Access with 200U...of course the phone will work... and the PC could not get to its own vlan. Instead, the PC got an ip from the voice vlan. Not from VLAN 2.
I have Linksys phone I’m not sure if this help.
For more information I setup in switch,
            - enable voice vlan
- set the port on auto voice vlan
- enable LLDP-MED globally
- create a network policy to assign VLAN 200
- assign this network policy to the port the phone is connected to.
I hope this information help to help me to setup Data and Voice vlans, to plug the phone to work with vlan Voice 200 (IP rang 192.168.22.X), from phone to Pc and pc work as Data vlan 2 (IP rang 192.168.2.X).

I just got done setting up voice VLANs on an SF 300-24P and verified working. This was working with Cisco 7900 series phones connected to a Cisco UC setup.
Here's my sample config.
Note that I edited this by hand before posting, so doing a flat out tftp restore probably won't work. However, this should give you a clue. Also, don't take this as 100% accurate or correct. I've only been working with these things for about a week, though I've worked with the older Linksys SRW switches for a couple of years. I'm a CCNP/CCDP.
VLAN 199 is my management VLAN and is the native VLAN on 802.1q trunks.
VLAN 149 is the data/computer VLAN here.
VLAN 111 is the voice/phone VLAN here.
VLAN 107 does nothing.
interface range ethernet e(1-24)
port storm-control broadcast enable
exit
interface ethernet e1
port storm-control include-multicast
exit
interface ethernet e2
port storm-control include-multicast
exit
interface ethernet e3
port storm-control include-multicast
exit
interface ethernet e4
port storm-control include-multicast
exit
interface ethernet e5
port storm-control include-multicast
exit
interface ethernet e6
port storm-control include-multicast
exit
interface ethernet e7
port storm-control include-multicast
exit
interface ethernet e8
port storm-control include-multicast
exit
interface ethernet e9
port storm-control include-multicast
exit
interface ethernet e10
port storm-control include-multicast
exit
interface ethernet e11
port storm-control include-multicast
exit
interface ethernet e12
port storm-control include-multicast
exit
interface ethernet e13
port storm-control include-multicast
exit
interface ethernet e14
port storm-control include-multicast
exit
interface ethernet e15
port storm-control include-multicast
exit
interface ethernet e16
port storm-control include-multicast
exit
interface ethernet e17
port storm-control include-multicast
exit
interface ethernet e18
port storm-control include-multicast
exit
interface ethernet e19
port storm-control include-multicast
exit
interface ethernet e20
port storm-control include-multicast
exit
interface ethernet e21
port storm-control include-multicast
exit
interface ethernet e22
port storm-control include-multicast
exit
interface ethernet e23
port storm-control include-multicast
exit
interface ethernet e24
port storm-control include-multicast
exit
interface range ethernet g(1-4)
description "Uplink trunk"
exit
interface range ethernet g(1-4)
switchport default-vlan tagged
exit
interface range ethernet e(21-24)
switchport mode access
exit
vlan database
vlan 107,111,149,199
exit
interface range ethernet g(1-4)
switchport trunk allowed vlan add 107
exit
interface range ethernet e(21-24)
switchport access vlan 111
exit
interface range ethernet g(1-4)
switchport trunk allowed vlan add 111
exit
interface range ethernet e(1-20)
switchport trunk native vlan 149
exit
interface range ethernet g(1-4)
switchport trunk allowed vlan add 149
exit
interface range ethernet g(1-4)
switchport trunk native vlan 199
exit
voice vlan aging-timeout 5
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
voice vlan oui-table add 108ccf MyCiscoIPPhones1
voice vlan oui-table add 40f4ec MyCiscoIPPhones2
voice vlan oui-table add 8cb64f MyCiscoIPPhones3
voice vlan id 111
voice vlan cos 6 remark
interface ethernet e1
voice vlan enable
exit
interface ethernet e1
voice vlan cos mode all
exit
interface ethernet e2
voice vlan enable
exit
interface ethernet e2
voice vlan cos mode all
exit
interface ethernet e3
voice vlan enable
exit
interface ethernet e3
voice vlan cos mode all
exit
interface ethernet e4
voice vlan enable
exit
interface ethernet e4
voice vlan cos mode all
exit
interface ethernet e5
voice vlan enable
exit
interface ethernet e5
voice vlan cos mode all
exit
interface ethernet e6
voice vlan enable
exit
interface ethernet e6
voice vlan cos mode all
exit
interface ethernet e7
voice vlan enable
exit
interface ethernet e7
voice vlan cos mode all
exit
interface ethernet e8
voice vlan enable
exit
interface ethernet e8
voice vlan cos mode all
exit
interface ethernet e9
voice vlan enable
exit
interface ethernet e9
voice vlan cos mode all
exit
interface ethernet e10
voice vlan enable
exit
interface ethernet e10
voice vlan cos mode all
exit
interface ethernet e11
voice vlan enable
exit
interface ethernet e11
voice vlan cos mode all
exit
interface ethernet e12
voice vlan enable
exit
interface ethernet e12
voice vlan cos mode all
exit
interface ethernet e13
voice vlan enable
exit
interface ethernet e13
voice vlan cos mode all
exit
interface ethernet e14
voice vlan enable
exit
interface ethernet e14
voice vlan cos mode all
exit
interface ethernet e15
voice vlan enable
exit
interface ethernet e15
voice vlan cos mode all
exit
interface ethernet e16
voice vlan enable
exit
interface ethernet e16
voice vlan cos mode all
exit
interface ethernet e17
voice vlan enable
exit
interface ethernet e17
voice vlan cos mode all
exit
interface ethernet e18
voice vlan enable
exit
interface ethernet e18
voice vlan cos mode all
exit
interface ethernet e19
voice vlan enable
exit
interface ethernet e19
voice vlan cos mode all
exit
interface ethernet e20
voice vlan enable
exit
interface ethernet e20
voice vlan cos mode all
exit
interface ethernet e1
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e2
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e3
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e4
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e5
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e6
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e7
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e8
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e9
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e10
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e11
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e12
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e13
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e14
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e15
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e16
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e17
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e18
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e19
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e20
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e21
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e22
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e23
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e24
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet g1
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet g2
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet g3
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet g4
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e1
lldp med notifications topology-change enable
exit
interface ethernet e2
lldp med notifications topology-change enable
exit
interface ethernet e3
lldp med notifications topology-change enable
exit
interface ethernet e4
lldp med notifications topology-change enable
exit
interface ethernet e5
lldp med notifications topology-change enable
exit
interface ethernet e6
lldp med notifications topology-change enable
exit
interface ethernet e7
lldp med notifications topology-change enable
exit
interface ethernet e8
lldp med notifications topology-change enable
exit
interface ethernet e9
lldp med notifications topology-change enable
exit
interface ethernet e10
lldp med notifications topology-change enable
exit
interface ethernet e11
lldp med notifications topology-change enable
exit
interface ethernet e12
lldp med notifications topology-change enable
exit
interface ethernet e13
lldp med notifications topology-change enable
exit
interface ethernet e14
lldp med notifications topology-change enable
exit
interface ethernet e15
lldp med notifications topology-change enable
exit
interface ethernet e16
lldp med notifications topology-change enable
exit
interface ethernet e17
lldp med notifications topology-change enable
exit
interface ethernet e18
lldp med notifications topology-change enable
exit
interface ethernet e19
lldp med notifications topology-change enable
exit
interface ethernet e20
lldp med notifications topology-change enable
exit
interface ethernet e21
lldp med notifications topology-change enable
exit
interface ethernet e22
lldp med notifications topology-change enable
exit
interface ethernet e1
lldp med enable network-policy poe-pse
exit
interface ethernet e2
lldp med enable network-policy poe-pse
exit
interface ethernet e3
lldp med enable network-policy poe-pse
exit
interface ethernet e4
lldp med enable network-policy poe-pse
exit
interface ethernet e5
lldp med enable network-policy poe-pse
exit
interface ethernet e6
lldp med enable network-policy poe-pse
exit
interface ethernet e7
lldp med enable network-policy poe-pse
exit
interface ethernet e8
lldp med enable network-policy poe-pse
exit
interface ethernet e9
lldp med enable network-policy poe-pse
exit
interface ethernet e10
lldp med enable network-policy poe-pse
exit
interface ethernet e11
lldp med enable network-policy poe-pse
exit
interface ethernet e12
lldp med enable network-policy poe-pse
exit
interface ethernet e13
lldp med enable network-policy poe-pse
exit
interface ethernet e14
lldp med enable network-policy poe-pse
exit
interface ethernet e15
lldp med enable network-policy poe-pse
exit
interface ethernet e16
lldp med enable network-policy poe-pse
exit
interface ethernet e17
lldp med enable network-policy poe-pse
exit
interface ethernet e18
lldp med enable network-policy poe-pse
exit
interface ethernet e19
lldp med enable network-policy poe-pse
exit
interface ethernet e20
lldp med enable network-policy poe-pse
exit
interface ethernet e21
lldp med enable network-policy poe-pse
exit
interface ethernet e22
lldp med enable network-policy poe-pse
exit
lldp med network-policy 1 voice vlan 111 vlan-type tagged
interface range ethernet e(1-22)
lldp med network-policy add 1
exit
interface vlan 199
ip address 199.16.30.77 255.255.255.0
exit
ip default-gateway 199.16.30.3
interface vlan 1
no ip address dhcp
exit
no bonjour enable
bonjour service enable csco-sb
bonjour service enable http
bonjour service enable https
bonjour service enable ssh
bonjour service enable telnet
hostname psw1
line console
exec-timeout 30
exit
line ssh
exec-timeout 30
exit
line telnet
exec-timeout 30
exit
management access-list Management1
permit ip-source 10.22.5.5 mask 255.255.255.0
exit
logging 199.16.31.33 severity debugging description mysysloghost
aaa authentication enable Console local
aaa authentication enable SSH tacacs local
aaa authentication enable Telnet local
ip http authentication tacacs local
ip https authentication tacacs local
aaa authentication login Console local
aaa authentication login SSH tacacs local
aaa authentication login Telnet local
line telnet
login authentication Telnet
enable authentication Telnet
password admin
exit
line ssh
login authentication SSH
enable authentication SSH
password admin
exit
line console
login authentication Console
enable authentication Console
password admin
exit
username admin password admin level 15
power inline usage-threshold 90
power inline traps enable
ip ssh server
snmp-server location in-the-closet
snmp-server contact [email protected]
ip http exec-timeout 30
ip https server
ip https exec-timeout 30
tacacs-server host 1.2.3.4 key spaceballz timeout 3 priority 10
clock timezone -7
clock source sntp
sntp unicast client enable
sntp unicast client poll
sntp server 199.16.30.1
sntp server 199.16.30.2
ip domain-name mydomain.com
ip name-server 199.16.5.12 199.16.5.13
ip telnet server

Cisco/Linksys SLM224G SWITCH: Problem with VLANs

Hi!
I'm trying to set up VLANs in my racks. I have some knowledge about VLANs, but I still can't set it up in my way.
My situation:
I have PC which contains two virtual machines, which has to works as a routers between three networks: LAN1, LAN2, WAN. It's a bit complicated, but I'll try to draw it:
                                                 |-------------|
|----------------------------|                   |           e1|-to-eth1-VM2-----WAN
|VirtualMachine 1        eth0|---trunk-VLAN1&2---|g1         e2|-to-eth0-VM2-----LAN2
|eth0=VLAN1 eth1=VLAN2       |                   |           e3|-to-eth0-VM2-----LAN2 etc.
|                         PC |                   |   SWITCH e4|
|VirtualMachine 2            |                   |           e5|-to-eth1-VM1---wire-to-LAN2
|eth0=VLAN3 eth1=VLAN4   eth1|---trunk-VLAN3&4---|g2         e6|-to-eth0-VM1-----LAN1
|----------------------------|                   |           e7|-to-eth0-VM1-----LAN1 etc.
                                                 |-------------|
gX = Gigabit ports
eX = 100Mbit ports
VMX = Virtual machine number
wire-to = patch-cord connection between ports on the switch
Schema of routing and logical visibility:
LAN1---VM1-----VM2---WAN
              |
LAN2----------|
Important note is that LAN1 and LAN2 has to be separated (visible only through routers). WAN has to be visible only through VM2 for LAN2 and through by VM1 and VM2 for LAN1. It looks easy, but VLANs which I done on that switch seems to doesn't works.
I'm doing this like that:
Step1: VLAN Management / Create VLAN...
Creating VLANs from 1, 2, 3, 4 (numbers doesn't meters right now - I now that number 1 is restricted at the switch).
Step2: VLAN Management / Port to VLAN...
Setting up VLAN1 with ports g1, e5 (both tagged or untagged? - I haven't seen difference)
Setting up VLAN2 with ports g1, e6, e7, etc...
Setting up VLAN3 with ports g2, e2, e3, etc...
Setting up VLAN4 with ports g2, e1
Step3: VLAN Management / Port Setting...
Setting up port e1 to PVID4 (frame type=all I suppose, but what with "ingress filtering"?)
Setting up port e2 to PVID3
Setting up port e3 to PVID3
etc...
Setting up port e5 to PVID1
Setting up port e6 to PVID2
Setting up port e7 to PVID2
etc...
So, on that configuration and on that switch it doesn't work for me
I know that switch is seeing MACs from VLANs which are done by PC's, because when I get in "Admin / Dynamic Address" I can see MACs on correct ports and with correct VLAN ID. So the problem is to forward VLANs on their ports, next clear frames from IDs and let packets go (and back: take clear packets, add VLAN ID and send to gigabits ports).
Showed configuration is the one of many that I tried :/ but I think this one is the best one.
Or maybe I don't know VLANs as I think and that schema is impossible? Please tell me if I' doing sth wrong.
Regards
and waiting for any suggestions,
Lucas

You need to make sure that your VirtualMachine can send tagged frames if the VMs share physical ethernet ports on the host.
I count 4 different LAN segments but you have only 2 physical ports on your PC (router).
And VM2 requires 3 physical connections according to the list below.
Depending on the virtualisation software you can maybe create the connection PVM1 to VM2 internally inside the PC (logical connection)
Are these the connections you require ?
VM1 --- LAN1
VM1 --- VM2
VM2 --- WAN
LAN2 --- VM2
Is this correct ? Will your PC, Virtualisation Software/Hypervisor tag frames with VLAn tags ?
If this is true I can help you configure the switch.
Jo

Integrating a DSP and BlackFin Modules with LV 8.5

Hi all,
I am just posting my last trouble when I was using Labview software for an academic work.
So I'll try to summarize the topic.
So, the point was to integrate LB with DSP board specifically model BF537 from BlackFin.
The problem is: Not all version of Labview can support DSP Module (this is an extension that you should install to do the integration possible) and BlackFin Embedded application for BF537 as well.
Just to clarify: you should have the correct version of LV because after that, you should install DSP Module and then, BlackFin Embedded.
The LV 8.6 supports BlackFin Embedded but doesn't supports DSP Module. The LV 2009 and LV 2011 we have the same issue. You can read the respective guide of these versions just to check it out.
The only version of LV that can support DSP Module and Embedded Module for Blackfin Processors is version 8.5.
The problem would be solved if both Modules(DSP and BlackFin) would are easily available on NI site or other website.
I spent many hours searching with no success. For LV 8.5 the correct DSP Module is 2.5 and I could not find this specific Module on any ws. Regarding Module for Blackfin Processors I have no problem to download it.
I tried to contact NI local support of my country but they have slow answers and any engineer can help me although all have been very attentive by phone.
My solutions was contact USA engineer. The local team is very efficient and some minutes later the DSP Module 2.5 was available to download in this link:
ftp://ftp.ni.com/outgoing
(mario_2.5.zip)
If anyone has problem to download the file, please let me know. I will be so glad to help.

Hello.
Could you send us your VI (v8.5) please? Thanks.
Regards.
Romain D.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
NIDays 2010 : Conférence mondiale de l'instrumentation virtuelle
>>Détails et Inscription<<

Powering APs from a 2911 with PoE switch module

Good Morning everyone!
I am hoping someone can shed some light on an issue I am having at a client site.
Client has purchased a 2911 ISR and an 8 port switch module with PoE card with the intention of running 4 2602i access points being managed by a 2504 WLC on the same switch card.
Problem we have is that the APs come up but do not power up radios or cleanair. If I plug an AP into switch port 0/0 it comes up and works fine but not on any of the other ports. We saw this on a separate router, (they are doing the same setup to two sites), yesterday. That's why I was called in, as they could only get one AP working at a time.
I believed this was a faulty poe card as it looks as though the APs are just not getting enough power and are placing the radios into RESET mode. Moved to the other ISR and everything worked fine, left it running overnight came in and all was fine and dandy.
As the other router had only a basic config on we did the config which involved some ACLs and a few port configurations but nothing on the switch card and nothing pertaining to power. I am a wireless guy, not a router specialist so am a bit stymied. Sometime later we noticed that all of the APs had all radios in RESET state.
Next I wiped the config on the ISR and rebooted everything and everything came up fine so points towards not a hardware issue but configuration.
Where should I be looking?
I can't paste a full running config due to client constraints but if someone could point me in the direction I can clean parts of the config for sharing...

I believed this was a faulty poe card as it looks as though the APs are just not getting enough power and are placing the radios into RESET mode.
I haven't played with those modules for a long time, but what do you get when you run the command "sh power inline"?
2600 APs require a minimum of 15.4w PoE but the recommended is 20.0w PoE.

Function not found in library? 1127 switch module

I am trying to control individual relays in an 1127 switch module with a 1331 attached. Whenever I try to connect to it through the block diagram (or through example programs) I get an error stating "Function not found in library" or sub vi not executable. However when I try to control it from the switch executive front panel it seems to work correctly. When I follow the sub vi error chain I eventually arrive at the library node and I am told to configure it. However when I click configure I get options that are phrased slightly differently than the original sub vi name. How do I get the example code / control over the 1127 installed in an scxi chassis.

Raaron,
The SCXI 1127 is a Matrix / Multiplexer card. If we wanted to try to make it function similar to an SPDT, you will limit the number of "SPDTs" you can create. With the 1331 that can only be configured as a multiplexer and essentially used for a single "SPDT" [com(SPDT) = com (Mux), NC(SPDT) = Ch0 (Mux), NO(SPDT) = Ch1 (Mux)] . If you use the 1332 you have a 4x8 Matrix and can make it into 4 "SPDTs" [com(SPDT) = r0(Matrix), NC(SPDT) = c0(Matrix), NO(SPDT) = c1 (matrix)]. Both of these configurations will not really be normally closed, and you would have to configure it in software to close when you are using it.
If you are looking for a true SPDT I would look at the 1160, 1161 and 1166.
I am glad that it is working now, but I am still confused as to how you were having SW issues though. Maybe the device was being set up as a Traditional DAQ device and was installed on an OS that does not support Traditional DAQ? Resetting the device [for DAQmx use] may have fixed this? I am unsure without further information.
Frank,
National Instruments
Staff Software Project Engineer

Temporarily show tab bar upon switching tabs with the keyboard in fullscreen mode

I use Firefox in fullscreen mode and switch tabs with Ctrl + PgUp/PgDn. I need to peek at the tab bar when I switch tabs, to avoid searching for the desired tab with multiple shortcut presses.
Is there a way to temporarily show the tab bar when I switch tabs with the keyboard shortcut? I want the tab bar to hide again after, say, 2 seconds of no tab switching.

You can try to set the focus to the location bar with Ctrl+L before switching the tabs to make the toolbar and tab bar appear.

Configuring - Cisco 2921 with Switch Module/POE PS and 3750-x 24 port switch

This is what I have
- Cisco 2921 router
         with SM-ES2-24-P switch module and
                 POE power supply
-Cisco 3750x- 24 port Switch
I have port G1/0 (which connects to 24p Switch Module port g0/26 logically) configured with 3 sub interfaces (management, User and VOIP)
I want to connect 3750x to G0/1 on 2921 via fiber GBIC but want to use same three VLANs
I can not daisy chain 3750x via the switch module because it does not have fiber port.
I do not want to create another routed (g0/1) interface because I want to keep Users on both switches on the same subnet without further splitting the subnet in two.
I hope I am not making this confusing.
How can I bridge g1/0 and g0/1 so I can pass vlan traffic between two switches?
Second problem i have is ...
I have a VOIP connected to switch module (SM) and it is not getting any power.
I went in to all the interfaces on SM and issued power inline auto command
On the SM (sh power inline) - available is 0.0(w)
on the 2921 (sh power inline)
   - power supply status is good,
   - maximun power available is 280.
   - interface G1/0( which connects to SM)
      *device is unknown
      * powered off
     * allocated 0.0 watts.
I already tried resetting SM
Is there any other command I need to issue?
thanks for your help.

I'm having a similar issue. I can get trunked connectivity between the switch module and the router if I put the IP address on the router sub interface, but not if I put it on a VLAN interface. I was hoping to have it on a VLAN sub interface on the router so I could use Gig0/1 and Gig0/2 to connect other switches and have them on the same VLANs. I'm using Gig1/0 on the router side and Gig0/51 on the switch side (48-port module).
Any help? Am I on the wrong track altogether?

Two srw switches with vlans and pfsense gatway

Hi,
I've got a bit of a problem that a can't seem to get a handle of things.
I've got two srw 48 port switches that I would like to link together and then on to the pfsense box.
First I'd like to connect the two switches to see if everything works and then on connect the pfsense box.
Now I would be very great full if someone with a bit more experience with VLANs would be so kind to walk me trough the procedure of creating VLANs, configuring them to ports on the switch and connecting the whole thing to another switch.
This is what I've done so fare.
1. I created 3 VLANs on both switches (VLAN2-office,VLAN3-WiFi, VLAN5-VoIP). I've created these VLANs with the same tags on all the devices.
2. I configured the ports that connect the switches as trunk. (I can't seem to be able to configure anything else on this port. Is there something else I should configure on these ports?)
Now as fare as I understand the documentation the VLANs on each switch should now see each other.
I'm still not sure on how to configure a physical port to one VLAN. After creating the VLANs on both switches and connecting them trough the trunk port I set ports 10-20 to VLAN2 by going to VLAN Management -> Ports to VLAN I selected VLAN2 and marked ports general and untagged and saved the settings. I repeated the procedure on the other switch. Now if I stuck my network cable into one of this ports I didn't get an IP anymore form the DHCP witch means that they were on a different VLAN than the other ports so I setup another router to act as a test DHCP with a different IP range as the main DHCPto see if it works. Now when I connectedthe test router to one of the ports in VLAN2 and my PC to the same VLAN2 port I got the test IP no problem. But when I connected the PC to the other switch VLAN2 port nothing happened until I connected the test DHCP to one of the VLAN2 ports. So clearly the switch VLANs are not communicating.
Now I don't know did I forget something, made a mistake with some setting or I just don't know what I'm doing because I think I need to get the VLANs between switches working before tackling the pfsense connection.
I would be really great full if someone explains to me how to set these VLANs up so that they would work between switches.
Thank you for your help.

Hi,
I was successful and I did exactly that. I put all VLANs on trunk ports and the switch to switch to pfSense started to work.
The only thing that gave me some problems was the end port(port connecting to the device pc, phone, printer) configuration. I was under the impression that the port was supposed to be in general mode and tagged. But I figured out that the port is supposed to be in access mode and untagged and only a member of one VLAN(the one I wanted it to connect to).
Anyway all is working now and I've figured out all the kinks.
So thanks guys for the help.
Nice day to all.
Bye

Cisco WAAS and Content Switching Module compatiblity

We are planning to implement WAAS on our hub's 6500 core switches, so that TCP connections from the end sites users to the servers in the hub can be optimized. But we have the servers VLAN groups under the Cisco CSM module already. Are the client-server connections still able to be optimized by WAAS?

Hi Joe
let's seperate out the two topics here.
a) WAAS traffic interception with wccp
b) CSM
a) when you say vlan 200 is where target servers are connected, is that the CSM client side vlan? or the actual server vlan ?
the bottom line is you need to make sure the interface where you configure "ip wccp 61 redirect in" is recieving traffic from servers towards .
Good reference for WCCP best practices in 6500
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/white_paper_c11-629052.html
b) yes you can configure stickiness for session persistance as in below URL
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/csm/4.2.x/configuration/guide/addftrs.html
Thanks

Firewall Module with HSRP switches

Hello ,
We have implemented HSRP configuration between the core switches for 20 VLANs, as the following:
HSRP Configuration for switch 1;
Interface Vlan4
Description âVLAN Descriptionâ
Ip address 192.168.8.2 255.255.255.0
Standby 5 ip 192.168.8.1
Standby 5 timer 5 15
Standby 5 preempt
HSRP Configuration for switch 2;
Interface Vlan4
Description âVLAN Descriptionâ
Ip address 192.168.8.3 255.255.255.0
Standby 5 ip 192.168.8.1
Standby 5 timer 5 15
Standby 5 priority 50
Standby 5 preempt
Now, Only on the active core switch we have inserted a firewall Module to protect VLANs communication to each other while we dont have firewall on the standby switch. Im planning to implement firewall only on one switch if the VLAN fail the traffic will be diverted on the second switch without firewalling.
Would you please assist me on Firewall configuration when i have HSRP running as per my config.
Regards,

The transparent firewall feature greatly simplifies deployment in the data center for protecting hosts. The transparent firewalls also fit into existing networks with no Layer 3 changes and transparently pass Layer 3 traffic from routers, allowing interoperability with IP services such as Hot Standby Router Protocol (HSRP), Virtual Router Redundancy Protocol (VRRP), Gateway Load Balancing Protocol (GLBP), Multicast, and non-IP traffic such as Internetwork Packet Exchange (IPX), Multiprotocol Label Switching (MPLS), and bridge protocol data units (BPDUs).

Confussed between the vlan mode and switch mode AToMPLS

Folks,
Could someone explain to me in simple terms the difference between the 2. I am very confussed about how the VC concepts works.
So i Dot1q tagged packet comes into the switch, the switch applies 2 lables to it, outer and inner, and then it gets to the egress switch where the switches checks the dot1q tag again to decide what to do with the packet?
in vlan rewrite example have have difference vlans on both sides (ingress and egress) how does the switch or MPLS know that the packet is going from one vlan to the other?
Thanks,

Hello,
in AToM - as you described - there will be two labels involved, very much like in MPLS L3VPN. The top label will allow the transportation to the proper PE and the VC-label will identify the interface/port/VLAN.
With EoMPLS in VLAN mode the PEs will be able to transport dot1Q tagged frames from a CPE on a per-VLAN basis. The configuration includes the VLAN tags at both end of the MPLS VC. So the dot1Q header is stripped and transported and a new dot1Q header is created by the egress PE. The VLAN tags to be used are directly configured at each PE in the form of a subinterface with encapsulation dot1Q.
The decision where to forward the frame in the egress PE is solely determined from the VC label. Therefore one could even have the same VLAN for many customers. This is similar to IP address overlap in the MPLS L3VPN case.
I am not familar with the term "switch mode" you use above. The other option with EoMPLS is called "port mode" afaik. See f.e.
http://www.cisco.com/en/US/products/hw/routers/ps368/products_configuration_guide_chapter09186a00801e5c06.html#wp1128955
"Ethernet over MPLS
Ethernet over MPLS works by encapsulating Ethernet PDUs in MPLS packets and forwarding them across the MPLS network. Each PDU is transported as a single packet. There are various ways to configure Ethernet over MPLS:
VLAN modetransports Ethernet traffic from a source 802.1Q VLAN to a destination 802.1Q VLAN through a single VC over an MPLS network.
Port modeallows all traffic on a port to share a single VC across an MPLS network.
In port mode there will be no subinterfaces and VLAN tags defined at the PE routers. Instead all incoming ethernet frames will be "copied" from one port to another. I personally refer to this as an MPLS cloud playing the role of a "Cat5 cable simulator". The only thing a PE does besides transportation of ethernet frames is error checking (and dropping if the FCS is not correct).
Hope this helps! Please rate all posts.
Regards, Martin

How to resolve A VMWare portgroup with VLAN ID 0 cannot be founf on virtual switch vSwitch0.

Hi All,
I have deployed Microsoft private cloud using SCVMM, SCOM, SCCM, SCSM, SCO and SCSM Portal...
Also, i am using cloud service process pack runbooks and offerings for my vm provisioning in VM Ware platform...
After submitted the request vm got created but it is throwing an error in SCVMM jobs:
A VMWare portgroup with VLAN ID 0 cannot be found on virtual switch vSwitch0...
VLAN ID of the existing virtual switch vSwitch is 48 and that we cannot change...also we cannot create a new vswitch in DC...
How can i resolve this error...
Thanks in advance for your help...
Regards,
Sudheesh M A

Hi Alexander,
Thank for answering. I asked custumer to send some config file from the switch. I don´t how complete is this, but, regarding "mls cos" entries, we have:
no aaa new-model
switch 1 provision ws-c2960x-48ts-l
ip domain-name ecs.local
login on-failure trap
login on-success log
vtp mode transparent
mls qos
crypto pki trustpoint TP-self-signed-1837850112
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-1837850112
revocation-check none
rsakeypair TP-self-signed-1837850112
interface GigabitEthernet1/0/1
switchport access vlan 235
switchport mode access
srr-queue bandwidth share 1 70 25 5
priority-queue out
mls qos trust dscp
service-policy input ACCESS_INGRESS
interface GigabitEthernet1/0/2
switchport access vlan 235
switchport mode access
srr-queue bandwidth share 1 70 25 5
priority-queue out
mls qos trust dscp
service-policy input ACCESS_INGRESS
interface GigabitEthernet1/0/48
switchport access vlan 235
srr-queue bandwidth share 1 70 25 5
priority-queue out
mls qos trust dscp
service-policy input ACCESS_INGRESS
Is these entries make any sense for the behavior we are facing?
Thanks

6500 performance with mix of PFC3BXL, DFC3CXL and CFC modules

Am looking at a 6500 which has WS-SUP720-3BXL and WS-X6708 with DFC3 CXL.
It also has 5x 6748 cards with CFC installed.
If I check the platform mode its 3BXL, as its fallen back to the module fitted to the SUP720.
As this switch also has some line cards fitted with CFC's what is the total system forwarding capability?
Is it 30Mpps for all 5 of the 6748/CFC cards and a higher rate for the WS-SUP720-3BXL and WS-X6708, or 30Mpps across the whole system?
Initially I understood it to be 30Mpps across all slots, regardless of cards and modules fitted if a CFC existed in the chassis.
After reading several architecture documents now I'm not so sure it is that simple.

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
Traffic ingressing on a non-DFC card will use (and share) the sup's Mpps.
Traffic ingress on a DFC card will use the card's DFC Mpps.
Traffic egressing on either card, has already used the PPS of the ingress.
"All the links in the Cisco Virtual Switching Supervisor Engine 720 can be active simultaneously even in the redundant configurations, thereby increasing the supervisor throughput from 48 to 82 Mpps."
I.e. 48 Mpps since sup, 82 Mpps with 2nd sup.
BTW, the sup2T offers even more single sup PPS, 60 (?) Mpps.
You might find this of interest: http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/107258-C6K-PFC-DFC-CFC.html

VLAN Support at routers and switches

is there a table with howmany VLANs each of cisco routers and switches can support.
its not always written at the product data sheet.

hi
Do find the details for 1800 ISR series router..
802.1Q VLAN
A total of eight VLANs can be configured to segment a network and offer additional security and separation of network traffic.
VLAN Support
802.1Q VLAN supported on all 10/100BASE-T ports
VLAN Configured
8 VLANs
Wireless VLANs
16
7400 series has reached EOL/EOS status hence i couldnt find any datasheet for that model..
regds

WCCP on Subinterfaces and Switch Modules with VLANs

Similar Messages

Maybe you are looking for