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

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

Problems with vlan and dot1q trunking port

Dear Folks,
i have problems with my AccessPoint Konfiguration.
Even when i set the Catalyst Port to trunk, i can only connect to VLAN 1 but not to VLAN 10.
and if i change the port to statik vlan 10 i can not connect to the ap but it works...
config below:
User Access Verification
version 12.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname 1200_PP_1
logging queue-limit 100
enable secret xxxx
clock timezone A 1
ip subnet-zero
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
ssid DEPACNGLW0HS
vlan 10
authentication shared
infrastructure-ssid
mobility network-id 10
speed basic-1.0 2.0 5.5 11.0
rts threshold 2312
channel 2412
antenna receive right
antenna transmit right
station-role root
interface Dot11Radio0.1
no ip route-cache
interface Dot11Radio0.10
encapsulation dot1Q 10 native
no ip route-cache
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 port-protected
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
bridge-group 1 spanning-disabled
interface FastEthernet0
no ip address
no ip route-cache
speed 100
full-duplex
ntp broadcast client
interface FastEthernet0.1
encapsulation dot1Q 1
no ip route-cache
bridge-group 254
no bridge-group 254 source-learning
bridge-group 254 spanning-disabled
interface FastEthernet0.10
encapsulation dot1Q 10 native
no ip route-cache
bridge-group 1
no bridge-group 1 source-learning
bridge-group 1 spanning-disabled
interface BVI1
ip address 10.2.2.222 255.255.255.0
no ip route-cache
ip default-gateway 10.2.2.2
ip http server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag/122-15.JA/1100
ip radius source-interface BVI1
bridge 1 route ip
line con 0
line vty 0 4
login local
line vty 5 15
login
end
it would be fine if anyone could help me....

You configure Layer 3 Mobility with WLSM. No trunking is required on the CAT switch. However, you need to set the switch port on the CAT switch as access port in VLAN 10.
Please post the WLSM and SUP720 configuration. Also, which VLAN do you want to access the AP?
The following URL may be useful for you to verify the configuration:
http://www.cisco.com/en/US/partner/products/hw/wireless/ps430/prod_technical_reference09186a00802a86a7.html

A problem with vlan.dat retrieval in the RME

Hello,
the customer has LMS 3.1 and he uses RME for the backup of config files and vlan.dat files from netwrok devices. It is working fine, but he has problem with backuping vlan.dat files from the following switches: Cat2960-8TC,-24TC, Cat2960G-24TC,-48TC,-8TC and Cat3560E-24TD-E,S. I downloaded the latest packages for these devices into RME. I changed the telnet timeout value from 32s to 70s. But this issue still exist:-( The running and startup config from these switches is downloaded without any problem. Is it a bug?
Thank you
Best Regards
Roman

Hello,
I tried it manually and the copy is working ( i had to create empty file in the tftp directory under CSCOpx):-( The error mesage is that ssh and telnet is not available and tftp doesn't support fetching of vlan.dat. But ssh is working on the switches (the running and startup config is fetched by RME without any problem from these switches). The credentials verifications is done with OK for ssh and enable secret for these switches.
Roman

Cisco Prime 2.1 problem with API/Client

Hi,
im having a problem with the API output i get from Cisco Prime Infrastructure. The URL im trying to GET info from is:
https://<URL>/webacs/api/v1/data/Clients
The output shows that im missing data from a specific ID. Example:
{"@url":"https:\/\/prime.lmv.lm.se\/webacs\/api\/v1\/data\/Clients\/1280389614","@type":"Clients","$":"1280389614"}
Then i try to GET the info regarding this ID: https://<URL>/webacs/api/v1/data/Clients/1280389614
{"errorDocument":{"httpResponseCode":500,"httpMethod":"GET","message":"No such entity as Clients \/ 1280389614.-PRS-101","id":"presentation.PRS-101","uriPath":"data\/Clients\/1280389614","queryParams":"{}"}}
So something is wrong here, so when i add ".full=true" parameter i get the following error as it cannot show the client data:
https://<URL>/webacs/api/v1/data/Clients.json?.full=true&.firstResult=1000&.maxResults=1000
{"errorDocument":{"httpResponseCode":500,"httpMethod":"GET","message":"Exception while invoking valueOf method 'getEnum' of enumeration class 'class com.cisco.ncs.nbi.client.ClientProtocolEnum'; nested exception is org.hibernate.HibernateException: Exception while invoking valueOf method 'getEnum' of enumeration class 'class com.cisco.ncs.nbi.client.ClientProtocolEnum'","exception":"org.springframework.orm.hibernate3.HibernateSystemException: Exception while invoking valueOf method 'getEnum' of enumeration class 'class com.cisco.ncs.nbi.client.ClientProtocolEnum'; nested exception is org.hibernate.HibernateException: Exception while invoking valueOf method 'getEnum' of enumeration class 'class com.cisco.ncs.nbi.client.ClientProtocolEnum'","uriPath":"data\/Clients","queryParams":"{.full=[true], .firstResult=[1000], .maxResults=[1000]}"}}
Any idea how to solve this issue, how can i find the client that is causing this problem? In my script im reading all the clients in the network to a third party application. But right now its hard to get this output in a smart way. It might be resolved in 2.2, but it feels like the data i corrupt in some way so i doubt that this error is related to the version?
Best Regards // Mattias Andersson

Hi,
I have also run into this problem on two different Prime 2.1-systems when trying to get all Client-data available. I haven't figured out a way to fix it more than making small calls (.maxResults=100) then trying to pin-point and skip the ID giving the error. I've been using 2.2 for a while now but haven't tested the Client-API that much yet. I'll experiment some more on it and see if I can recreate the problem to see if it's related to the version.

Multiple NI-Switch problems with PXI-2566 including blue screen

We've been having intermittent problems with our PXI-2566 for months now.
It seems like at some point the device and/or driver gets in a state where the open of the device causes a "blue screen." It traps in niswdk.dll (addr: ae9db759, base: ae9b7000, datestamp: 488e1ebe). The NI_Switch version on this system is 3.8.0f1. We now have the system configured to do a full kernel dump (as suggested in another thread).
We've seen some bad viStatus'es (that we've haven't been able to decode) returned from NI-Switch:
niSwitch_InitWithTopology - 0xBFFA6767
niSwitch_Connect - 0xBFFA4B50 -- I think this is the error that starts the downward spiral...
niSwitch_Disconnect & niSwitch_Connect - 0xBFFA495D (after 0xBFFA4B50 error)
We get a blue screen the next time we start our app -- best guess is on the niSwitch_InitWithTopology ("foo", NISWITCH_TOPOLOGY_2566_16_SPDT, VI_FALSE, VI_TRUE, ) call.
We'd seen these kind of problems several months back & switched out to a different PXI-2566 & they went away, but now they've come back. Not sure how much the relays have been stressed, but even if they were don't see why we'd get these types of failures. The card passes self-test (from Max), but I get errors running the soft front panel & can't get to the relay counts:
The system is running XP. The application uses MSVC, VISA, etc. This doesn't have anything to do with powering on/off the PXI chassis (another reason for blue screens).
Ideas for fixes or debugging ???

OK, 1 easy answer: the device name was set to "PXI1-NI2566" MAX allows this & we have no trouble using this name from our application, but apparently the "-" is invalid from the soft front panel app. So at least I can get to the switch counts now (and they're all <2000).
We did get another 0xBFFA6767 this morning, follow shortly by a blue screen & have a kernel dump. Does that help in tracking this down?
We've been running this application for many months. It's use of the 2566 is pretty simple and has not changed. It fails intermittently & we haven't been able to correlate the failure with any other events. The system in general has been pretty stable in terms of hardware & software changes.
There are a lot of devices in this system -- this is the only one we're having problems with. We have a rack-mounted PC interfacing to separate PXI & VXI chassis. Here are summaries from MAX & Device Manager:
Is this enough detail? The MXI interface card (MXI-4?) is currently PCIe, but had this same problem with the PCI version of the card
Can you be more specific about resetting after a 0xBFFA6767 to get closer to the fault?
The "other blue screen" events I was referring to were in a different thread on the NI forums. Those problems had to do power cycling the PXI (or powering it on after the PC) -- we know from experience not do that.

[SOLVED] systemd switch, problems with slim/bootup

My system will boot, giving me "OK" for everything it's doing. Then my system gives me a tty login prompt, but continues booting:
gestalt login: [ OK ] Starting Wicd.
[ OK ] Reached target multi-user.
[ OK ] Reached target graphical interface.
So if i just hit enter, it gives me another login prompt, then I can login, but X/fluxbox isn't started or anything.
My ~/.xinitrc:
exec startfluxbox
xset +fp /usr/share/fonts/local
xset fp rehash
systemctl list-units --type=target
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target masked active active graphical.target
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded active active Network
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
syslog.target loaded active active Syslog
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
14 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Graphical target isn't masked, like I thought it would be after reading this
systemctl status slim.service gives me:
slim.service - SLiM Simple Login Manager
Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
Active: failed (Result: exit-code) since Mon, 2012-11-26
Process: 305 ExecStart=urs/bin/slim -nodaemon(code=exited, status =1/FAILURE)
CGroup: name=systemd:/system/slim.service
systemd-analyze blame gives (just going to ignore the times)
wicd.service
systemd-vconsole-setup.service
systemd-binfmt.service
systemd-logind.service
systemd-modules-load.service
dev-hugepages.mount
systemd-udev-trigger.service
dev-mqueue.mount
systemd-udevd.service
proc-sys-fs-binfmt_service.mount
console-kit-daemon.service
polkit.service
systemd-tmpfiles-setup.service
home.mount
systemd-sysctl.service
tmp.mount
systemd-user-sesssions.service
systemd-remount-fs.service
slim isn't even on this list.
systemctl --failed
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
slim.service loaded failed failed SLiM Simple Login Manager
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
4 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Hopefully this isn't too much information (or completely irrelevant) for what might be a far simpler problem, but I'm just not sure what's going on. It might be worth noting that I only bothered to start switching to systemd today when I had to reboot and slim wouldn't start/get me into my WM(!) This is interesting to me, since I read (somewhere) that as of slim's last version, it would only work with systemd and not consolekit... but when I try:
pacman -Qi slim
It tells me that the last time I last updated/installed slim was November 5 of this year. Any ideas?
EDIT:
Latest nVidia drivers weren't working with my 7xxx integrated GPU. Downgrade to 304xx drivers or use nouveau.
Last edited by brokengestalt (2012-11-28 17:41:50)

I tried starting X manually (typing in "startx" at the prompt, and I get the following errors:
modprobe: ERROR: could not insert 'nvidia': No such device
Fatal server error:
no screens found
(EE)
Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
It looks like I'm just having problems with my video card, but I have the proprietary nVidia drivers installed and X installed. The systemd wiki page mentions no changes that I would need to make to my xorg or nvidia configuration...

Linksys Router BEFW11S4 problems with iphone

i have a linksys router bedfw11s4 version 4 and im having problems with wifi on my iphone
i can search and connect to my router but the interent is extremely slow
i have no problems with my laptop
i read some info on this board regarding changing it to static ip but im having problems figuring out how to config it
when i goto into my router setting i only see 1 DNS address

So on your IPhone you are getting connected to your Wireless Network, but the Internet is working slow, then i would suggest you to change some settings on your Router....
Once you login to the router setup page, Under Wireless ... Change the Wireless channel to 11-2.462GHz and click on Save Settings....
Then under Advacnce Wireless Settings.... Change the Beacon Interval to 75 >>Change the Fragmentation Threshold to 2304, Change the RTS Threshold to 2304 >>Click on "Save Settings".....
Now check if your IPhone, how is the Internet Speed....
If still slow then i would suggest you to upgrade the firmware of your Router....
Go to website linksysbycisco.com/downloads.........insert model no of your router in serach tab......select proper version of your router........download the firmware file......save that file on desktop..
Follow these steps to upgrade the firmware on the device : -
Open an Internet Explorer browser page on a computer hard wired to the router...In the address bar type - 192.168.1.1...Leave the Username blank & in Password use admin in lower case...
Click on the 'Administration' tab- Then click on the 'Firmware Upgrade' sub tab- Here click on 'Browse' and browse the .bin firmware file and click on "Upgrade"...
Wait for few seconds until it shows that "Upgrade is successful" After the firmware upgrade, click on "Reboot" and you will be returned back to the same page OR it will say "Page cannot be displayed".
Now reset your router :
Press and hold the reset button for 30 seconds...Release the reset button...Unplug the power cable from your router, wait for 30 seconds and re-connect the power cable...Now re-configure your router...

Router on a Stick with Cisco/Linksys SRW2024 Switch

Does anybody have experience with configuring a router on a stick type configuration with a non-Catalyst switch? I have a SRW2024 switch and a 2611 router. I would like to configure the switch with a trunk port and use dot1q encapsulation on subinterfaces on the router to route between the subnets. Configuring the router is simple, but the switch is very confusing and I just can't seem to get it to work. Any ideas? Is this even doable with this combonation of hardware?
Thanks in advance.
-Dan

The "Encapsulation dot1q 1 native" command is not a valid command on my router. Specifically, the native command is not an option. Perhaps that isn't in my IOS version?
IOS (tm) C2600 Software (C2600-JS56I-M), Version 12.0(7)T, RELEASE SOFTWARE (fc2)
IOS image: c2600-js56i-mz.120-7.T
However I did a whole lot of messing around with it today and I think I finally got it. The trouble is, IMHO, the switch menus are too messy and hard to understand. It seems to allow me to do impossible things which adds to the confusion.
Here's what worked for me:
My router config was correct to begin with.
Router-A (Cisco 2611):
interface Ethernet0/0
ip address 192.168.1.10 255.255.255.0
interface Ethernet0/0.2
encapsulation dot1Q 2
ip address 10.0.0.1 255.0.0.0
Switch (Linksys SRW20204):
Menu: Switch > VLAN Interface Settings
Select the port number of the port to be the trunk.
Set Port VLAN Mode to Trunk. Submit.
Menu: Switch > VLAN
Create a second VLAN with the ID of 2.
Add the ports to be "Included" on this VLAN.
Leave the workstation ports "Untagged".
(This is where I was screwing up)...
"Include" the Trunk port AND select "Tagged".
So basically, I was tagging the workstation ports and not the trunk port. But the correct way is the Trunk port must be Included on all VLANs and have Tagging turned on for all VLANs. All the workstation ports should be included on whatever VLAN they should be on but NOT Tagged. It makes sense now because a workstation would have no idea what to do with a tagged frame.
Why I can enable tagging on non-trunk ports is a mystery. They really should explain that better in the manual. Perhaps add some examples. I find the manual for this switch to be extremely vague overall.
Thakns for the help guys!
-Dan

Problem with VLAN Trunking within RHEL6.6 VM on Hyper-V 2012 R2?

Hello,
I'm wondering if there is a known issue with using a "trunk" mode interface within a RHEL6.6 VM? I found the following article:
https://technet.microsoft.com/en-us/library/dn531026.aspx
Where note 1 reads:
"For this specific RHEL/CentOS release, VLAN tagging may not work when used in conjunction with trunk mode".
I've been fighting with this for the better part of a day and can't figure out what I'm doing wrong. I have a RHEL 6.6 VM with two NICs. The first NIC is a standard access mode NIC - no problems there.
The second NIC has been set up as follows (via PowerShell):
    $a=Get-VmNetworkAdapter -VMName "My VM"
    Set-VMNetworkAdapterVlan -Trunk -VmNetworkAdapter $a[1] -AllowedVlanIdList 101-105 -NativeVlanId 1
Note that the physical switch and switchports are configured to send tagged packets for these VLANs as well.
I then set up a VLAN (eth1.102) based interface in the VM ... and never receive any traffic on it.
What I've observed is that:
A VM on the same physical host using the same virtual switch can communicate with the VM on the tagged VLAN
A pcap of the "eth1" interface (to which eth1.102 is bound) shows traffic for VLANs 101 through 105 arriving ... I just never see the traffic for VLAN 102 forwarded to the eth1.102 interface
An identical network configuration using Ubuntu 14.04.01 LTS works exactly as expected
It's this last point that has me wondering if the problem is with RHEL and not Hyper-V (or the physical/virtual switches involved).
I'm curious if anybody else has seen this behavior or, if RHEL 6.x is working for you, if you're using Intel or Broadcom NICs on the physical Hyper-V host?
Thanks,

This is indeed a known issue with RHEL.   There's a bug open with Red Hat on the issue, and our understanding is that they have a fix in progress that will be part of a RHEL 6.6 update.  You might inquire with Red Hat regarding
their bugzilla #1135347.
Michael Kelley, Lead Program Manager, Open Source Technology Center

LGS308 problem with vlan and multicast

Hello,
I have a LGS308 smart switch and am having problems putting multicast traffic on a specific vlan.
The switch is connected to a PC for management (vlan 1).
All ports are in acces mode, vlan 1 untagged.
I created vlan 2 and put it untagged on port 7 and 8.
Now, when I connect a multicast device (IPTV) on port 8, the switch becomes unresponsive and nothing works.
It seems the switch is flooded with multicast traffic.
Simply turning IGMP snooping on didn't help so I think it needs more configuration.
Is this a known problem?
ps: Once I have this simple setup running I'm planning for a more advanced setup with trunking 2 vlans (iptv + internet) to another switch over a single UTP cable. But first things first

Yes it should!
I have changed the setup like this:
Switch 1
port 1 - access mode - vlan 1U <---> Internet
port 2 - access mode - vlan 1U <---> PC
port 7 - access mode - vlan 2U <---> IPTV source (IGMP)
port 8 - trunk mode - vlan 1T + 2T <---> switch 2 port 8
Switch 2
port 7 - access mode - vlan 2U <---> IPTV source (IGMP)
port 8 - trunk mode - vlan 1T + 2T <---> switch 2 port 8
With this setup, I can reach both switches from my PC.
However, multicast doesn't work. I don't get IPTV on switch 2 port 7.

SPA112 - problem with VLAN

Hello,
recently I bought few of SPA112 gateways, and I have two problems:
1. provisioning using xml file; device is not using new vlan setting (other settings such as dialplan, line number, user and passwd are working correctly), what I'm trying to apply is identical to setting used in other Sipura devices:

<Enable_VLAN ua="na">yes</Enable_VLAN>
<VLAN_ID ua="na">127</VLAN_ID>
Also tried with putting above setting in <router-configuration> but no luck.
2. it seems that after putting gateway from web service to use vlan, it still sits on access. This is what I see:
VID VLAN Name                        MAC Address       Port Type
127 vlan127                          88-75-56-05-98-FA 26   Dynamic
499 vlan499                          88-75-56-05-98-FA 26   Dynamic
port setting is vlan499 - untagged, vlan127 - tagged. I want it to use only vlan127. Any help would be much appreciated, thanks.
FW version:
1.2.1 (004) Jul 27 2012

I managed to find how to set set vlan using xml, unfortunately it looks like this part of provisioning is broken on Cisco side.
Gateway created sample xml file in which part about vlans looks like this:
0
123   <- here is typo BTW
The part that is not working is , SPA doesn't respond to changes in this setting. is set correctly.

Linksys active x problem with web pages

When i install linksys active X for viewing live video with camera WVC54GCA i cannot open other web pages.I am using Windows XP and Internet explorer 8.Is there any solution for this problem???
Solved!
Go to Solution.

Installation of Active X does not prevent any web pages to load, if you have installed Active X then you certainly should be able to view all the web pages inclucding the web pages that contains flash that helps in viewing certain kinds of files, and displaying animation...
Adjust your browser settings :
Open an IE, click Tools >> Internet Options, then delete all files, cookies, history, forms...Goto "Connections", make sure Never Dial a Connection is checked, click on LAN Settings and make sure all the options are unchecked...Once you are done click on O.k...Close the IE and re-open it...
Did you try to browse the Internet using a different web browser ?

Cisco linksys WAP4410N WPS problem

dear all
i have two AP i set one as AP mode and another as WDS repeater
i disable WPS via ssh ad when i see wi-fi protected setup wps shown disabled
the problem until now when some body try to connect to the AP there is a message shown that addtional logon required
how can i solve this so any one can connect with no need only for wifi pass
in past i set the first ssid as default and not broadcast it and create second ssid that i can broadcast it
now i cannot only broadcast one ssid because the mode AP with alowed some repeaters
firmware version
2.0.6.1

Please check the below video link which can helpful for you in configuration:
Link-1: http://www.youtube.com/watch?v=C96Gdd_18G0
Link-2:
http://www.cisco.com/en/US/docs/wireless/access_point/csbap/wap4410n/administration/guide/WAP4410N_Admin_Guide.pdf

Cisco ISE 1.2 - Problem with Device Onboarding of internal users using AD Credentials

Dear experts,
We have implemented ISE 1.2 with WLC 7.5 in our organization. We are using Device Onboarding by letting the users enter their AD Username and Passowrd on Guest portal which then redirects them to device registration portal where they simply register their device and they get internet access.
The problem is that some users are unable to authenticate using this portal while some can successfully authenticate and register their devices. All users are of the same group in AD. Also, we have enabled this check on two places. One is when users connects to the SSID where the security WPA2-Enterprise uses 802.1x and asks for AD username password. The other is on the portal.
All users are able to connect to the SSID using their AD credentials. However, 30% of the users are not being authenticated when they are redirected to the Guest portal for device registration. Also, it gives no error or event on either ISE or on the mobille device. When the users enters their credentials, the same guest portal page comes back blank with no errors or logs anywhere.
Can someone guide me if there is some configuration mistake that I may have done or have someone faced this same issue and were/weren't able to resolve it.
Thanks in advance.
Jay

Our problem got solved. It was related to a few user accounts in AD. Usually any authentication on AD User Account is carried out using the User ID. However, during Web Authentication, Login ID/Name is also checked by ISE and should be same as User ID.
The problem you are facing might also related be to AD since we had the similar issue. try to check this on a laptop as the mobile portal gives no error if the user is unknown or invalid. Also, you can enable logs for web authentication which are off by default. It will give you a pretty good idea where the problem lies. And yeah, do not keep the web authentications log on for long, it can hang your ISE.
Anyways, thanks for all the support.

Cisco/Linksys SLM224G SWITCH: Problem with VLANs

Similar Messages

Maybe you are looking for