Issue of Cisco SF 100-24
We use a Cisco SF 100-24 Switch for a few months now number free of charge. Big storm has come a few nights ago and knocked out our power, because so far the problems with the switch. Some port of LED lights are lit with no cable connected, while some connected ports remain off when a cable is connected. Don't know how to solve this problem. I have reset the switch several times, and the same lights are switched on and off. Any advice would be greatly appreciated. Thank you.
Looks like the switch got zapped by a fluctuation of current transitional... Good luck.
You can call the helpdesk small business (link below), but without looking a statemement of warranty, I guess that Cisco is not responsible for cuts power or ground problems caused by a lightning strike.
http://www.Cisco.com/en/us/support/tsd_cisco_small_business_support_center_contacts.html
Good luck
Best regards, Dave
Tags: Cisco Support
Similar Questions
-
DMP 4400 G RS 232 connection with Cisco LCD 100 PRO 40N
Hello world
I know this question has been asked a little before, but I still have trouble affecting the DMM to control Cisco LCD 100 PRO 40N (Samsung) via the RS232 DMP connection!
I searched and read every post on this forum, ('Samsung_MDC_RS232_Protocol_Ver - 21.pdf' & rs232.tx_hex =) tried but not vain.
We have DMS VmWare demo (signs & Cast 5.2, Show and part 5.2) and 4400G with firmware 5.2.
Also, I connected the series RS232 9 pin female to female that came with the TV on the DPM 4400 G and in the port RS232 TV, configured the DMP in the Task tab view control forward as you can see in the picture to set and define the type of TV for Cisco 40N and Power ON and another task for the display OFF. What I'm doing wrong here!
Any input will be greatly appreciated!
You must first activate rs232 on the DMP. For Cisco views, use the system task called "RS-232: control supported, non-DMTech poster. This will cause the DMP restart. Once it has restarted, you should then be able to use the rs232 codes or the built in display of DMM controls. I tested on the same Cisco display with cable included as has managed to turn the screen off and back on orders of DMM.
-
Routing issue of Cisco VPN Client ASA
Hi, I use a Barracuda NG for firewalls and I would use a Cisco ASA 5505 for VPN Client connections. But I have the problem that I can't get a connection to the VPN PC connected to the internal network. But I can reach the VPN connected PC from the inside. Here is a diagram of my network:
Here the IP Configuration and the routing of the Barracuda firewall table:
I have a route on the Barracuda NG to the 10.10.10.0/24 network VPN Client on eth0.
The 192.168.1.0/24 LAN I ping the Client comes with Client VPN 10.10.10.11 as it should. But I can't ping or access network resources in the local network for AnyConnected customer's PC that connected through the VPN.
Here is the config Cisco ASA:
: Saved : : Hardware: ASA5505, 512 MB RAM, CPU Geode 500 MHz : ASA Version 9.2(2) ! hostname leela names ip local pool VPN-Pool 10.10.10.10-10.10.10.200 mask 255.255.255.0 ! interface Ethernet0/0 switchport access vlan 2 ! interface Ethernet0/1 ! interface Ethernet0/2 ! interface Ethernet0/3 ! interface Ethernet0/4 switchport access vlan 5 ! interface Ethernet0/5 ! interface Ethernet0/6 ! interface Ethernet0/7 ! interface Vlan1 nameif inside security-level 100 ip address 192.168.1.250 255.255.255.0 ! interface Vlan2 nameif outside security-level 0 ip address dhcp ! interface Vlan5 nameif dmz security-level 50 ip address 172.16.0.250 255.255.255.0 ! ftp mode passive clock timezone CEST 1 clock summer-time CEDT recurring last Sun Mar 2:00 last Sun Oct 3:00 dns domain-lookup inside dns server-group DefaultDNS name-server 192.168.1.10 same-security-traffic permit inter-interface same-security-traffic permit intra-interface object network obj_any subnet 0.0.0.0 0.0.0.0 object network VPN-Pool subnet 10.10.10.0 255.255.255.0 description VPN-Pool object network NETWORK_OBJ_10.10.10.0_24 subnet 10.10.10.0 255.255.255.0 access-list inside_access_in extended permit ip any any access-list inside_access_in extended permit ip object VPN-Pool any access-list dmz_access_in extended permit ip any any access-list global_access extended permit ip any any access-list outside_access_in extended permit ip any any pager lines 24 logging enable logging asdm informational mtu inside 1500 mtu outside 1500 mtu dmz 1500 no failover icmp unreachable rate-limit 1 burst-size 1 no asdm history enable arp timeout 14400 no arp permit-nonconnected nat (inside,dmz) source static any any destination static NETWORK_OBJ_10.10.10.0_24 NETWORK_OBJ_10.10.10.0_24 no-proxy-arp route-lookup inactive access-group inside_access_in in interface inside access-group outside_access_in in interface outside access-group dmz_access_in in interface dmz access-group global_access global route dmz 0.0.0.0 0.0.0.0 172.16.0.254 1 route inside 0.0.0.0 0.0.0.0 192.168.1.254 tunneled timeout xlate 3:00:00 timeout pat-xlate 0:00:30 timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02 timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00 timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00 timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute timeout tcp-proxy-reassembly 0:01:00 timeout floating-conn 0:00:00 dynamic-access-policy-record DfltAccessPolicy server-type microsoft user-identity default-domain LOCAL aaa authentication enable console LDAP_SRV_GRP LOCAL aaa authentication http console LDAP_SRV_GRP LOCAL aaa authentication ssh console LDAP_SRV_GRP LOCAL aaa authentication serial console LOCAL http server enable 444 http 192.168.1.0 255.255.255.0 inside snmp-server location Vienna crypto ipsec ikev2 ipsec-proposal DES protocol esp encryption des protocol esp integrity sha-1 md5 crypto ipsec ikev2 ipsec-proposal 3DES protocol esp encryption 3des protocol esp integrity sha-1 md5 crypto ipsec ikev2 ipsec-proposal AES protocol esp encryption aes protocol esp integrity sha-1 md5 crypto ipsec ikev2 ipsec-proposal AES192 protocol esp encryption aes-192 protocol esp integrity sha-1 md5 crypto ipsec ikev2 ipsec-proposal AES256 protocol esp encryption aes-256 protocol esp integrity sha-1 md5 crypto ipsec security-association pmtu-aging infinite crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set ikev2 ipsec-proposal AES256 AES192 AES 3DES DES crypto map inside_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP crypto map inside_map interface inside crypto map dmz_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP crypto map dmz_map interface dmz crypto ca trustpoint ASDM_TrustPoint0 enrollment self subject-name CN=leela proxy-ldc-issuer crl configure crypto ca trustpoint ASDM_TrustPoint1 enrollment terminal crl configure crypto ca trustpool policy crypto ca certificate chain ASDM_TrustPoint0 quit crypto ikev2 policy 1 encryption aes-256 integrity sha group 5 2 prf sha lifetime seconds 86400 crypto ikev2 policy 10 encryption aes-192 integrity sha group 5 2 prf sha lifetime seconds 86400 crypto ikev2 policy 20 encryption aes integrity sha group 5 2 prf sha lifetime seconds 86400 crypto ikev2 policy 30 encryption 3des integrity sha group 5 2 prf sha lifetime seconds 86400 crypto ikev2 policy 40 encryption des integrity sha group 5 2 prf sha lifetime seconds 86400 crypto ikev2 enable dmz client-services port 443 crypto ikev2 remote-access trustpoint ASDM_TrustPoint0 telnet timeout 5 no ssh stricthostkeycheck ssh 192.168.1.0 255.255.255.0 inside ssh timeout 30 ssh key-exchange group dh-group1-sha1 console timeout 0 dhcpd auto_config outside ! dhcpd address 192.168.1.254-192.168.1.254 inside ! threat-detection basic-threat threat-detection statistics access-list no threat-detection statistics tcp-intercept dynamic-filter updater-client enable dynamic-filter use-database ntp server 192.168.1.10 source inside ssl trust-point ASDM_TrustPoint0 dmz ssl trust-point ASDM_TrustPoint0 inside webvpn enable dmz no anyconnect-essentials anyconnect image disk0:/anyconnect-macosx-i386-3.1.05170-k9.pkg 1 anyconnect image disk0:/anyconnect-win-3.1.05170-k9.pkg 2 anyconnect image disk0:/anyconnect-linux-3.1.05170-k9.pkg 3 anyconnect image disk0:/anyconnect-linux-64-3.1.05170-k9.pkg 4 anyconnect profiles AnyConnect_client_profile disk0:/AnyConnect_client_profile.xml anyconnect enable tunnel-group-list enable group-policy DfltGrpPolicy attributes default-domain value group-policy GroupPolicy_AnyConnect internal group-policy GroupPolicy_AnyConnect attributes wins-server none dns-server value 192.168.1.10 vpn-tunnel-protocol ikev2 ssl-client webvpn anyconnect profiles value AnyConnect_client_profile type user group-policy portal internal group-policy portal attributes vpn-tunnel-protocol ssl-clientless webvpn url-list none username tunnel-group AnyConnect type remote-access tunnel-group AnyConnect general-attributes address-pool VPN-Pool authentication-server-group LDAP_SRV_GRP default-group-policy GroupPolicy_AnyConnect tunnel-group AnyConnect webvpn-attributes group-alias AnyConnect enable tunnel-group Portal type remote-access tunnel-group Portal general-attributes authentication-server-group LDAP_SRV_GRP default-group-policy portal tunnel-group Portal webvpn-attributes group-alias portal enable! ! ! policy-map type inspect dns preset_dns_map parameters message-length maximum client auto message-length maximum 512 ! prompt hostname context no call-home reporting anonymous hpm topN enable : end no asdm history enable
Can someone please help me solve this problem?
When I tried to solve this I didn't choose which interface the Packet Tracer?
The interface inside or DMZ interface? Inside, he says it will not work with the dmz but the error did not help me
Anyone here knows why it does not work?
Hello
Inside LAN is directly connected to the right firewall VPN... then I don't think you have to have the itinerary tunnele... can you try to remove the road tunnel mode and check.
entrance to the road that is static to achieve 10.10.10.11 as its display is correct...
Route by tunnel watch also with 255 administrative distance. I've never used that in my scenarios... lets see...
Concerning
Knockaert
-
Dear all
I'm testing the MRA of VCS - C and VCS-E feature
I use the firewall architecture 3 ports that the VCS - C and CUCM are placed inside with the same subnet.
The VCS-E is placed in the DMZ and static use of the ASA 5510 1-1 NAT to translate private IP address: 172.16.0.225 to the public IP address, for example 100.1.1.1
In the context of VCS - C, I use the FQDN of the SCV - F that map to the public IP of VCS-E (100.1.1.1)
And the VCS-E use the FQDN of the SCV - C to map to the IP private of VCS - C
Area traversed in VCS - C is active, but the area crossed in VCS - E is inactive, it is said that server inaccessible.
I found that my VCS-E is not the license of the Advanced Networking option.
In the VCS-E ip settings page, there is not any NAT setting
I want to ask if I need to use NAT, in addition to the NAT of firewall functionality, I need also the license of advanced networking option to activate NAT in VCS - E?
Or it may work to use only the function NAT firewall without NAT for the VCS - F?
Also, I put the reflection of the NAT to my ASA 5510
Hello
The option networking advanced to activate NAT on VCS - E or the edge of the highway is a requirement for the crossing of firewall deployment.
Useful guide:
Deployment Configuration Guide (Control with Expressway) Cisco VCS Basic (X8.7)
With your case about the progress of the deployments of networks, you will need to follow the 3 firewall ports using single VCS Expressway LAN Interface DMZ on the guide on page 60.
Kind regards
Acevirgil
-
1602i-e-k9 AP and WLC 5508 issue of Cisco
Dear forum participants,
I experience a problem connection Access Point 1602i-e-k9 to WLC 5508
I upack and taken an AP on the network, it appears on the WLC (monitor > all APs), I can see it using the link details for several time.
Then he desappears, restart does not help.
I searched the forum for solutions, made AP reset via command "cli rommon-like" + button "MODE" and "reset" . After that, the same thing happens again: he appears on WLC and disappears.
What I am doing wrong?
Brief info on devices and newspapers partial
Please see the full changelog of the AP attached (contains info after the reset command has been entered).
The AP Info
looking at the picture...
extracting information (283 bytes)
Image info:
Version suffix: k9w8-. 152 - 2.JB
Image name: ap1g2-k9w8 - mx.152 - 2.JB
The release directory: ap1g2-k9w8 - mx.152 - 2.JB
The iOS Image size: 9400832
Total image size: 9769472
Image device: Wireless LAN | LWAPP
Family pictures: AP1G2
Wireless switch management Version: 7.4.100.0
WLC Info
Name of the manufacturer... Cisco Systems Inc..
Product name... Cisco controller
Version of the product... 7.4.100.0
Bootloader Version... 1.0.1
Retrieving Image Version field... 6.0.182.0
Firmware version... Console USB 1.3, 1.6 Env FPGA, 1.27
Build Type....................................... DATA + WPS, LDPE
Journal of the AP
reset
[BEGIN] 20.03.2013 14:09:31
Are you sure you want to reset the system (y/n)? There
System reset...
Boot from flash
* 00:00:15.627 Mar 1: % LWAPP-3-CLIENTERRORLOG: Config flash load failed. Initialization of Cfg
* 00:00:15.631 Mar 1: % CAPWAP-3-Journal of ERROR: could not load the configuration of flash. Reset to the default configuration
* 00:00:16.671 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed to uplwapp_crypto_init: MIC present and analyzed successfully
No source of bridge-Group 1-learning
^
Invalid entry % detected at ' ^' marker.
% Without Gateway default route, if not an interface point, may affect performance
* 00:00:46.131 Mar 1: % CDP_PD-4-POWER_OK: all disabled radio - power INJECTOR_CONFIGURED_ON_SOURCE online source
* 00:00:49.411 Mar 1: DHCP-6-ADDRESS_ASSIGN %: BVI1 Interface assigned address DHCP 172.17.254.6, mask 255.255.255.0, hostname AP0006.f618.1d3b
Translate "CISCO-CAPWAP-CONTROLLER"... the domain server (172.17.254.1)
* 00:01:00.347 Mar 1: % CAPWAP-5-DHCP_OPTION_43: the 172.17.254.203 drive address obtained by DHCP
* 00:01:00.347 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.
* 00:01:09.347 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-CAPWAP-CONTROLLER
* 00:01:19.347 Mar 1: % 3-CAPWAP-ERRORLOG: go join a capwap controller
looking at the picture...
extracting information (283 bytes)
Image info:
Version suffix: k9w8-. 152 - 2.JB
Image name: ap1g2-k9w8 - mx.152 - 2.JB
The release directory: ap1g2-k9w8 - mx.152 - 2.JB
The iOS Image size: 9400832
Total image size: 9769472
Image device: Wireless LAN | LWAPP
Family pictures: AP1G2
Wireless switch management Version: 7.4.100.0
Extraction of the files...
AP1G2-k9w8-MX.152-2.JB/ (directory) 0 (bytes)
extraction of ap1g2-k9w8-mx.152-2.JB/K5.bin (75790 bytes)
* 14:10:57.000 20 Mar: % CA
extraction ap1g2-k9w8-mx.152-2.JB/S2.bin (9328 bytes)
extraction of ap1g2-k9w8-mx.152-2.JB/S5.bin (106106 byte) PWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:10:57.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:10:57.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:10:57.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:10:57.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:10:57.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:10:57.543 Mar 20: % CAPWAP-3-Journal of ERROR: could not process the encrypted package capwap 172.17.254.203perform archive download capwap: / ap1g2 tar file
* 14:10:57.547 Mar 20: % CAPWAP-6-AP_IMG_DWNLD: not found required image on AP. image controller download.
extraction ap1g2-k9w8-mx.152-2.JB/info (283 bytes)
AP1G2-k9w8-MX.152-2.JB/HTML/ (directory) 0 (bytes)
AP1G2-k9w8-MX.152-2.JB/HTML/level/ (directory) 0 (bytes)
AP1G2-k9w8-MX.152-2.JB/HTML/level/1/ (directory) 0 (bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/forms.js (17492 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/appsui.js (563 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/ap_home.shtml.gz (1297 bytes)
AP1G2-k9w8-MX.152-2.JB/HTML/level/1/images/ (directory) 0 (bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/images/info.gif (399 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/images/cisco-logo-2007.gif (1648 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/images/background_web41.jpg (732 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/images/login_homeap.gif (19671 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/config.js (25507 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/sitewide.js (16554 bytes)
extraction of ap1g2-k9w8-mx.152-2.JB/html/level/1/officeExtendap.css (41801 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/back.shtml (512 bytes)
AP1G2-k9w8-MX.152-2.JB/HTML/level/15/ (directory) 0 (bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapBanner.htm (7114 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapConfig.shtml.gz (2864 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapSummary.htm (718 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapHelp.htm (5013 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapMain.shtml.gz (3350 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapEvent.shtml.gz (988 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/K2.bin (5830 bytes)
extraction of ap1g2-k9w8-mx.152-2.JB/8005.img (200872 bytes)
extraction of ap1g2-k9w8-mx.152-2.JB/ap1g2-k9w8-mx.152-2.JB (9196955 bytes)
* 14:12:57.694 Mar 20: % 3-CAPWAP-ERRORLOG: white event 48 & combination State 10.
* 14:12:57.694 Mar 20: % 3-CAPWAP-ERRORLOG: SM Manager: failed to process the message of the timer. Event 48, State 10
* 14:12:57.694 Mar 20: % CAPWAP-3-Journal of ERRORS: do not handle the message from the timer.
* 14:12:57.694 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the message of the timer.
extraction info.ver (283 bytes)
Removal of target version: flash:/ap1g2-k9w8-mx.152-2.JB...done.
New image of the software installed in flash:/ap1g2-k9w8-mx.152-2.JB
System to use new IMA configuration
Flash event log entry: / event.log...
GE... done.
Download of archive: 212 seconds
* 14:14:28.389 Mar 20: upgrade successfully, the system image is now reloading
* 14:14:28.425 Mar 20: % SYS-5-RELOAD: reload requested by capwap image download proc. reload reason: NEW IMAGE DOWNLOAD.
* 14:14:28.425 Mar 20: % LWAPP-5-CHANGED: CAPWAP changed State to DOWN
Event.log written
Boot from flash
* 00:00:53.107 Mar 1: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 00:00:54.031 Mar 1: DHCP-6-ADDRESS_ASSIGN %: BVI1 Interface assigned address DHCP 172.17.254.7, mask 255.255.255.0, hostname AP0006.f618.1d3b
* 00:00:54.107 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 00:00:54.163 Mar 1: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 00:00:55.163 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
Translate "CISCO-CAPWAP-CONTROLLER"... the domain server (172.17.254.1)
* 00:01:04.927 Mar 1: % CAPWAP-5-DHCP_OPTION_43: the 172.17.254.203 drive address obtained by DHCP
* 00:01:04.927 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.
* 00:01:13.927 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-CAPWAP-CONTROLLER
* 00:01:23.927 Mar 1: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:16:30.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:16:30.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:16:30.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:16:30.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:16:30.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:16:30.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:16:30.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:16:49.211 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:16:49.211 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:16:49.211 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:16:49.267 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:16:49.287 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:16:49.287 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:16:49.303 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:16:49.343 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:16:50.287 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:16:50.335 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:16:50.343 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:16:51.327 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:16:51.335 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:16:51.379 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:16:51.387 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:16:51.395 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:16:52.379 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:16:52.387 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:16:52.423 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:16:53.423 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:16:59.343 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:16:59.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:16:59.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:16:59.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:16:59.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:16:59.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:16:59.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:16:59.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:17:17.699 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:17:17.699 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:17:17.699 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:17:17.755 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:17:17.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:17:17.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:17:17.783 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:17:17.819 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:17:18.771 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:17:18.819 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:17:18.827 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:17:19.811 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:17:19.819 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:17:19.863 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:17:19.871 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:17:19.879 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:17:20.863 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:17:20.871 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:17:20.907 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:17:21.907 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:17:27.819 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:17:28.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:17:28.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:17:28.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:17:28.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:17:28.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:17:28.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:17:28.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:17:47.203 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:17:47.203 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:17:47.203 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:17:47.259 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:17:47.275 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:17:47.275 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:17:47.287 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:17:47.323 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:17:48.275 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:17:48.323 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:17:48.331 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:17:49.315 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:17:49.323 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:17:49.367 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:17:49.375 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:17:49.383 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:17:50.367 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:17:50.375 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:17:50.411 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:17:51.411 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:17:57.323 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:17:57.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:17:57.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:17:57.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:17:57.547 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:17:57.547 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:17:57.547 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:17:57.547 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:18:15.699 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:18:15.699 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:18:15.699 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:18:15.755 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:18:15.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:18:15.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:18:15.799 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:18:15.831 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:18:16.771 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:18:16.835 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:18:16.843 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:18:17.827 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:18:17.835 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:18:17.879 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:18:17.887 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:18:17.895 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:18:18.879 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:18:18.887 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:18:18.923 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:18:19.923 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:18:25.831 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:18:26.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:18:26.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:18:26.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:18:26.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:18:26.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:18:26.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:18:26.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:18:44.699 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:18:44.699 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:18:44.699 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:18:45.163 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:18:45.183 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:18:45.183 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:18:45.195 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:18:45.227 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:18:46.183 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:18:46.231 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:18:46.239 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:18:47.223 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:18:47.231 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:18:47.275 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:18:47.283 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:18:47.291 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:18:48.275 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:18:48.283 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:18:48.319 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:18:49.319 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:18:55.227 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:18:55.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:18:55.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:18:55.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:18:55.547 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:18:55.547 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:18:55.547 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:18:55.547 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:19:13.695 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:19:13.695 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:19:13.695 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:19:13.751 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:19:13.767 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:19:13.767 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:19:13.783 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:19:13.815 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:19:14.767 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:19:14.827 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:19:14.835 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:19:15.819 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:19:15.827 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:19:15.871 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:19:15.879 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:19:15.887 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:19:16.871 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:19:16.879 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:19:16.915 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:19:17.915 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:19:23.815 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:19:24.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:19:24.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:19:24.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:19:24.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:19:24.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:19:24.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:19:24.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:19:42.695 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:19:42.695 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:19:42.695 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:19:42.751 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:19:42.767 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:19:42.767 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:19:42.783 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:19:42.815 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:19:43.767 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:19:43.815 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:19:43.823 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:19:44.807 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:19:44.815 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:19:44.859 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:19:44.867 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:19:44.875 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:19:45.859 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:19:45.867 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:19:45.903 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:19:46.903 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:19:52.815 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:19:53.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:19:53.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:19:53.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:19:53.547 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:19:53.547 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:19:53.547 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:19:53.547 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:20:12.111 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:20:12.111 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:20:12.111 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:20:12.167 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:20:12.183 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:20:12.183 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:20:12.199 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:20:12.231 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:20:13.183 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:20:13.235 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:20:13.243 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:20:14.227 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:20:14.235 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:20:14.279 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:20:14.287 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:20:14.295 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:20:15.279 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:20:15.287 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:20:15.323 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:20:16.323 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:20:22.231 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:20:22.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:20:22.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:20:22.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:20:22.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:20:22.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:20:22.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:20:22.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:20:40.699 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:20:40.699 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:20:40.699 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:20:40.755 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:20:40.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:20:40.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:20:40.787 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:20:40.819 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:20:41.771 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:20:41.819 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:20:41.827 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:20:42.811 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:20:42.819 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:20:42.863 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:20:42.871 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:20:42.879 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:20:43.863 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:20:43.871 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:20:43.907 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:20:44.907 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:20:50.819 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:20:51.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:20:51.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:20:51.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:20:51.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:20:51.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:20:51.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:20:51.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:21:10.107 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:21:10.107 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:21:10.107 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:21:10.163 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:21:10.179 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:21:10.179 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:21:10.191 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:21:10.227 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:21:11.179 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:21:11.227 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:21:11.235 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:21:12.219 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:21:12.227 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:21:12.271 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:21:12.279 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:21:12.287 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:21:13.271 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:21:13.279 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:21:13.315 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:21:14.315 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:21:20.227 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:21:20.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:21:20.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:21:20.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:21:20.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:21:20.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:21:20.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:21:20.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
[END] 20.03.2013 14:21:55
Azim,
I wonder if the regulatory domain of the AP is correct.
Please provide the result following (authorization according to Leo)
1 WLC: sh sysinfo
2 PA: sh version
3 PA: HS inventory
Thank you.
Amjad
Rating of useful answers is more useful to say "thank you".
-
Issue between Cisco and ESX switch
It is a small deployment with an ESX Server running a Windows Small Business SERVER 2003.
ESX server has 2 network cards, previously a NIC was connected to a small FastEthernet Switch netgear and all workstations have been working on it.
I replaced the netgear with a Cisco WS-C2960S-24TS-S and the field still works fine, the problem is that I can't connect to the service console or the VI client from a computer connected to the switch.
I can't ping the IP switch ESX service console and also can not ping the switch since the service console.
Switch and ESX console can ping the Windows Virtual Machine and the virtual machine can ping both of them. Therefore, I can get to the VI client via Wirtual Machine (not the best scenario to manage one of its right VMS ESX host?)
I don't know what the problem is, but it sounds a lot there is a problem with the configuration of port / vlan on the cisco switch.
Can a Cisco expert help out me here?
Here are some details of the configuration.
Port group service Console and the port Vm group do not use no matter what config VLAN on the ESX Server.
CONFIG NETWORK ESX
Name PCI Driver link speed Duplex MAC address MTU Description
vmnic0 0b: 00.00 bnx2 up to 1000Mbps Full 00: 1a: 64:b6:06:92 1500 Broadcom Broadcom NetXtreme II BCM5709 1000Base-T Corporation
vmnic1 0b: 00.01 bnx2 up to 100 Mbit/s Full 00: 1a: 64:b6:06:94 1500 Broadcom Broadcom NetXtreme II BCM5709 1000Base-T Corporation
vusb0 nickname cdc_ether Up 0Mbps 02: 1a: 64:b6:06:99 half 1500 unknown unknown
Switch name Num used Ports configured Ports MTU rising ports
64 6 64 1500 vmnic0 vSwitch0
Name PortGroup VLAN ID used rising Ports
PORTS 0 1 vmnic0 VM GROUP
0 1 vmnic0 Console service
Switch name Num used Ports configured Ports MTU rising ports
64 3 64 1500 vmnic1 vSwitch1
Name PortGroup VLAN ID used rising Ports
BIG POND ADSL 0 1 vmnic1
Port Group/DVPort IP IP family name address Netmask Broadcast Enabled TYPE
vswif0 Service Console IPv4 192.168.0.100 255.255.255.0 192.168.0.255 true STATIC
Lo encap:Local Loopback link
INET addr:127.0.0.1 mask: 255.0.0.0
RACE of LOOPING 16436 Metric: 1
Dropped packets: 1310258 RX errors: 0:0 overruns: 0 frame: 0
Dropped packets: 1310258 TX errors: 0:0 overruns: 0 carrier: 0
collisions: 0 txqueuelen:0
RX bytes: 4531037961 (4.2 GiB) TX bytes: 4531037961 (4.2 GiB)
vmnic0 Link encap HWaddr 00: 1a: 64:B6:06:92
RUNNING BROADCAST MULTICAST MTU:1500 metric: 1
Dropped packets: 94579247 RX errors: 0:0 overruns: 0 frame: 0
Dropped packets: 99834049 TX errors: 0:0 overruns: 0 carrier: 0
collisions: 0 txqueuelen:1000
RX bytes: 127899970453 (119.1 GiB) TX bytes: 19056702095 (17.7 GiB)
Interruption: 209 memory: 92000000-92012100
vmnic1 Link encap HWaddr 00: 1a: 64:B6:06:94
RUNNING BROADCAST MULTICAST MTU:1500 metric: 1
Dropped packets: 3585973 RX errors: 0:0 overruns: 0 frame: 0
Dropped packets: 3018690 TX errors: 0:0 overruns: 0 carrier: 0
collisions: 0 txqueuelen:1000
RX bytes: 2304776001 (2.1 GiB) TX bytes: 1021855293 (974,5 MiB)
Interruption: 217 memory: 94000000-94012100
vswif0 Link encap HWaddr 00:50:56:45:43:6 C
INET addr:192.168.0.100 Bcast:192.168.0.255 mask: 255.255.255.0
RUNNING BROADCAST MULTICAST MTU:1500 metric: 1
Dropped packets: 367248 RX errors: 0:0 overruns: 0 frame: 0
Dropped packets: 126300 TX errors: 0:0 overruns: 0 carrier: 0
collisions: 0 txqueuelen:1000
RX bytes: 33905320 (32.3 MiB) TX bytes: 154760077 (147,5 MiB)
vusb0 Link encap HWaddr 02: 1a: 64:B6:06:99
RUNNING BROADCAST MULTICAST MTU:1500 metric: 1
Fall of RX packets: 341442 errors: 0:0 overruns: 0 frame: 0
Dropped TX packets: 0 errors: 0:0 overruns: 0 carrier: 0
collisions: 0 txqueuelen:1000
RX bytes: 26973918 (25.7 MiB) TX bytes: 0 (0.0 b)
CISCO SWITCH CONFIGURATION
Port on which the ESX nic is connected to:
interface GigabitEthernet0/1
switchport mode trunk
switchport nonegotiate
switchport port-security
aging of the switchport port security 2
security violation restrict port switchport
inactivity of aging switchport port-security type
macro description cisco-computer desk
spanning tree portfast
spanning tree enable bpduguard
!
******************************************
CONFIGURATION OF VLAN
!
interface Vlan1
IP 192.168.0.253 255.255.255.0
!
interface Vlan2
Description management Vlan
no ip address
!
interface Vlan10
Test description Vlan
IP 192.168.121.253 255.255.255.0
!
Default IP gateway 192.168.0.1
Any help would be appreciated.
Thank you
I think I've seen this before. I'm not super familiar with this switch, but I think that the problem is with cisco-computer office macro.
Try using the macro switch cisco instead since you are addressing a vSwitch on the other end. You can always check the mac address table and see if your Mac to the vswif (service console) make their appearance. If they are not then appear this is an inconsistency in the port between the Cisco Switch and vSwitch.
Louis
-
Hello. I have 2 pc.s. both with vista home premium installed. they do not have the same programs installed. the path of the problem folder is the following. C:\Users\user\AppData\Local\VirtualStore. on my laptop, this folder is absolutely empty. on the desktop the virtualstore folder is big close to 100 GB. that totally filled my hard drive. is it possible to disable this folder safely, so I can free up space on my hard drive
Hello, maveric8673
Do you recognize the files?
If there are files that you saved in a specific program in the folder?It is usually more old programs will try to save files / settings to a location requiring the administration of rights which translates the writing files in the folder Windows virtualstore. A marker is also created so that if the program accesses this file again, it will point to the file in the virtualstore folder. If you use an older or not designed for Vista program and its economy at this place, try to update the program.
According to the files, removing items from the folder may affect programs, but yes, you should remove them manually.
David
Microsoft Answers Support Engineer
Visit our Microsoft answers feedback Forum and let us know what you think. -
Hello world
I use the router Cisco E1200 wireless to my office building. The only way I was able to access the internet is by connecting the network to the internet port. Problem is that I have two network drives, I need access to this network.
I'm doing a static routing on the WAN port, but it keeps telling me "invalid static route.
How would you recommend that I have set up access to these network via the WAN port drives?
EDIT: I connect with a Mac Leopard installed.
In the installation type you want, it seems impossible to make a static routing since you do not have access to the main router of the network. You need to make changes on the main router for static routing to work on the secondary router (E1200). Now, there is another way to configure your router so that you can access the drives on the main network. Instead of static routing, you can cascade. LAN to LAN connection to be precise. Sense of the main network, it should go to the ethernet port on the E1200. There are several changes that you do on the router E1200 to make this possible. See the link below:
Editing cascading (connecting) a Linksys router to another router
-
Never seen any ports light up in red. (Or what looks like red for me, I'm colorblind.) I can't find any info on why it would be anything but blue. Any ideas?
The LED lights in green when the port is connected to a Gigabit port or blue when the port is connected to a 10/100 port.
Have you tried to connect your computer to any other Ethernet port on the router?
-
Issue of Cisco Quickvpn Windows 8
I am connected using Cisco Quickvpn using windows 7, which works correctly. I have a windows computer 8 that connects using quickvpn but I can only ping the gateway, I cannot reach any other device on the network. Support of Cisco was not able to help me.
Ah good stuff, good to know
-
Easy vpn server issues of Cisco 800 series.
Hello.
I want to deploy the easy vpn server on cisco 876 and 877 10 routers and access from a remote location (company headquarters). When I leave the firewall of the router off the vpn server works. When I turn it on it doesn't.
Although I allow all traffic to my ip for example 80.76.61.158 I can't access the vpn server.
I tried a place to let the firewall off and it worked fine.
I use SDM to configure the vpn server. Any ideas what I can do with the cause of firewall I really can't leave it "open."
Thanks in advance.
It would be a good idea to paste the configuration of the VPN server to the firewall.
Kind regards
Kamal
-
Issue of Cisco AnyConnect VPN access
We have configured a Cisco ASA 5505 with access AnyConnect. It works very well. However, these users can't ping on the private network devices. We have configured all devices on the network with an address 10.10.10.0/24 space. The inside interface of the ASA I 10.10.10.1/24 and the VPN return addresses are 10.10.10.50 - 10.10.10.65/24.
They users can use SSH and Oracle or MySQL calls but can't ping. Obviously, I'm looking for something.
Thank you.
Dwane
Hi Sylvie,.
Most likely, your ASA missing no. - nat between inside the interface and remote vpn-pool address range.
Quick Trobule shooting, thanks for posting your config and do not forget to remove the config security information.
What version of your ASA?
Thank you
Rizwan James
-
Issue of Cisco ASA 5505 Anyconnect Client NAT'ing
Hello
We have a split_tunnel RA Vpn configuration in a branch that works very well in all areas except the destinged of traffic for a specific website using https. This provider does not allow HTTPS connections to bring some outside IP addresses.
Essentially, this should work like this:
RAVPN_client (10.4.4.0/27)--> https request to the (208.x.x.x) vendor_ip---> ASA55XX--> NAT_to_outside_ip--> to the vendor_ip (208.x.x.x) https request
I need to understand how you would approach from ONLY this https traffic specific to the RA VPN without having to change the installer otherwise.
Internal hosts (aka behind the ASA physically) have not any question at this site, as would his nat ip address outside that we expect.
Here is what we use for the NAT Exemption it list 10.2.2.x, 192.168.100.x, and 172.23.2.x are other remote sites we have. The 10.4.4.0/27 RA VPN users don't have no problems connecting to them, regardless of the Protocol:
Note to inside_nat0_outbound access-list of things that should not be Nat would
access extensive list ip 10.12.1.0 inside_nat0_outbound allow 255.255.255.0 10.2.2.0 255.255.255.0
access extensive list ip 10.12.1.0 inside_nat0_outbound allow 255.255.255.0 192.168.100.0 255.255.255.0
access extensive list ip 10.12.1.0 inside_nat0_outbound allow 255.255.255.0 172.23.2.0 255.255.255.0
access extensive list ip 10.12.1.0 inside_nat0_outbound allow 255.255.255.0 10.4.4.0 255.255.255.224
access extensive list ip 10.4.4.0 inside_nat0_outbound allow 255.255.255.224 192.168.100.0 255.255.255.0
access extensive list ip 10.4.4.0 inside_nat0_outbound allow 255.255.255.224 10.2.2.0 255.255.255.0
access extensive list ip 10.4.4.0 inside_nat0_outbound allow 255.255.255.224 172.23.2.0 255.255.255.192
Here is the list of interesting traffic that we push to the customers through the tunnel of the VPN connection.
VPN_splitunnel to access extended list ip 192.168.100.0 allow 255.255.255.0 any
VPN_splitunnel of access list scope 10.2.2.0 ip allow 255.255.255.0 any
Access extensive list ip 10.12.1.0 VPN_splitunnel allow 255.255.255.0 any
Access extensive list ip 172.23.2.0 VPN_splitunnel allow 255.255.255.192 all
Access extensive list ip 10.4.4.0 VPN_splitunnel allow 255.255.255.224 all
VPN_splitunnel list extended access permit ip host 208.x.x.x any newspaper<- this="" is="" the="" vendors="" external="" ip="" address="" (obfuscated="" for="" security="" but="" you="" get="" the="">
Here's the rest of the nat configuration:
NAT-control
Overall 101 (external) interface
NAT (inside) 0-list of access inside_nat0_outbound
NAT (inside) 101 0.0.0.0 0.0.0.0
Configuring VPN RA:
IP mask 255.255.255.224 local pool VPNPool 10.4.4.5 - 10.4.4.30
WebVPN
allow outside
AnyConnect essentials
SVC disk0:/anyconnect-dart-win-2.5.0217-k9.pkg 1 image
SVC disk0:/anyconnect-macosx-i386-2.5.2001-k9.pkg.zip 2 image
enable SVC
tunnel-group-list activate
internal RAVPN group policy
RAVPN group policy attributes
value no unauthorized access to banner
value of banner that all connections and controls are saved
banner of value this system is the property of MYCOMPANY
banner value disconnect IMMEDIATELY if you are not an authorized user.
value of server WINS 10.12.1.11 10.2.2.11
value of 10.12.1.11 DNS server 10.2.2.11
Split-tunnel-policy tunnelspecified
value of Split-tunnel-network-list VPN_splitunnel
type tunnel-group RAVPN remote access
attributes global-tunnel-group RAVPN
address pool VPNPool
authentication-server-group NHCGRPAD
Group Policy - by default-RAVPN
tunnel-group RAVPN webvpn-attributes
enable RAVPN group-alias
Can someone ' a Please direct me as to what I'm doing wrong? I was assuming that since I don't have Ip 208.x.x.x address in the list of inside_nat0_outbound that it would be NAT had, but appears not to be the case (out of packet - trace below)
Packet-trace entry outside tcp 10.4.4.6 34567 208.x.x.x detailed https
*****************************************************************************
Phase: 1
Type:-ROUTE SEARCH
Subtype: entry
Result: ALLOW
Config:
Additional information:
in 0.0.0.0 0.0.0.0 outdoors
Phase: 2
Type: ACCESS-LIST
Subtype: Journal
Result: ALLOW
Config:
Access-group outside_access_in in interface outside
outside_access_in list extended access permitted ip VPN_ips 255.255.255.224 host 208.x.x.x Journal
Additional information:
Direct flow from returns search rule:
ID = 0xd7bd3b20, priority = 12, area = allowed, deny = false
Hits = 2, user_data is 0xd613bf80, cs_id = 0 x 0, flags = 0 x 0 = 0 protocol
SRC ip = VPN_ips, mask is 255.255.255.224, port = 0
IP = 208.x.x.x DST, mask = 255.255.255.255, port = 0, dscp = 0 x 0
Phase: 3
Type: IP-OPTIONS
Subtype:
Result: ALLOW
Config:
Additional information:
Direct flow from returns search rule:
ID = 0xd7df8fa0, priority = 0, sector = inspect-ip-options, deny = true
hits = 2256686, user_data = 0 x 0, cs_id = 0 x 0, reverse, flags = 0 x 0 = 0 protocol
SRC ip = 0.0.0.0 mask 0.0.0.0, port = 0 =
DST ip = 0.0.0.0 mask = 0.0.0.0, port = 0, dscp = 0 x 0
Phase: 4
Type: VPN
Subtype: ipsec-tunnel-flow
Result: ALLOW
Config:
Additional information:
Direct flow from returns search rule:
ID = 0xd87c8fc8, priority = 12, area = ipsec-tunnel-flow, deny = true
hits = 550, user_data = 0 x 0, cs_id = 0 x 0, flags = 0 x 0 = 0 protocol
SRC ip = 0.0.0.0 mask 0.0.0.0, port = 0 =
DST ip = 0.0.0.0 mask = 0.0.0.0, port = 0, dscp = 0 x 0
Phase: 5
Type: HOST-LIMIT
Subtype:
Result: ALLOW
Config:
Additional information:
Direct flow from returns search rule:
ID = 0xd7dfbd28, priority = 0, domain = host-limit, deny = false
hits = 1194, user_data = 0 x 0, cs_id = 0 x 0, flags = 0 x 0 = 0 protocol
SRC ip = 0.0.0.0 mask 0.0.0.0, port = 0 =
DST ip = 0.0.0.0 mask = 0.0.0.0, port = 0, dscp = 0 x 0
Phase: 6
Type: IP-OPTIONS
Subtype:
Result: ALLOW
Config:
Additional information:
Reverse flow from returns search rule:
ID = 0xd7df8fa0, priority = 0, sector = inspect-ip-options, deny = true
hits = 2256688, user_data = 0 x 0, cs_id = 0 x 0, reverse, flags = 0 x 0 = 0 protocol
SRC ip = 0.0.0.0 mask 0.0.0.0, port = 0 =
DST ip = 0.0.0.0 mask = 0.0.0.0, port = 0, dscp = 0 x 0
Phase: 7
Type: CREATING STREAMS
Subtype:
Result: ALLOW
Config:
Additional information:
New workflow created with the 2380213 id, package sent to the next module
Information module for forward flow...
snp_fp_tracer_drop
snp_fp_inspect_ip_options
snp_fp_tcp_normalizer
snp_fp_translate
snp_fp_adjacency
snp_fp_fragment
snp_ifc_stat
Information for reverse flow...
snp_fp_tracer_drop
snp_fp_inspect_ip_options
snp_fp_translate
snp_fp_tcp_normalizer
snp_fp_adjacency
snp_fp_fragment
snp_ifc_stat
Result:
input interface: outdoors
entry status: to the top
entry-line-status: to the top
output interface: outside
the status of the output: to the top
output-line-status: to the top
Action: allow
*****************************************************************************
Thank you
Jason
You are on the right track with you divided the tunnel configuration. You need to add is the pool of Client VPN to be coordinated to your external ip address, IE: same as your local users of the ASA when he tries to access the intellectual property of the provider (208.x.x.x), allowing more traffic in and out of the same interface for traffic of U-turn.
Here's what you need to set up:
permit same-security-traffic intra-interface
nat-to-vendor ip 10.4.4.0 access list permit 255.255.255.224 host 208.x.x.x
NAT (outside) 101-list of nat-to-vendor access
The foregoing will allow VPN pool to be coordinated to your ASA outside the ip address of the interface when accessing the seller (208.x.x.x).
1 small correction to your ACL split tunnel:
-The following line is incorrect and should be deleted in the tunnel of split ACL:
Access extensive list ip 10.4.4.0 VPN_splitunnel allow 255.255.255.224 all
(As 10.4.4.0/27 is your pool of Client VPN, you do not add these subnet to your list of split tunnel. List of Split tunnel are only the network that you are difficult to access and sent through your VPN tunnel).
Hope that helps.
-
I have a windows server 2012 running IME to manage my IPS devices on the network. When I do a scan of nessus on this server, it tells me ports 22.80 and 443 are open, even if IIS is not running. I can SSH for looping, but cannot authenticate.
IME launch a web daemon and open SSH on the host computer, on which he works? I'm trying to understand what application/service opens these ports.
My IME (version running on Windows Server 2008 R2 7.2.7) appears to open a declaration for the IPS sensors channel managed by using https (tcp/443) as the port target and an ephemeral TCP port as the source. (IMEjava.exe method)
The other ports it is listening on that concern the PRTG server and the Kiwi syslog daemon, I am also running on this host.
-
Issue of Cisco G & D installation
1. I would like to use the ip address of the proxy located at Injection vlan, is it possible?, as a general rule, the ip of the proxy has been diverting the vlan, but I don't have, I want to use injection vlan ip address IP of proxy.
2. anonymous try to connect to our custody. If denied that connection hijacking msfc vlan by the acl, currently our guards configured public ip address announced by bgp. Finally, we have a private ip address to configure our guard. Is it no problem in using the private ip address?
Please let me know if there is anything I can do for you in the history of the following tag.
Thank you.
The ip address of the proxy is used to establish a connection with the mode area hard, it is up to you to make sure that the area address is routable to the guard. Usually, we recommend to configure on the subnet of the vlan injection.
Maybe you are looking for
-
ICH kann die iCloud foto library use um meine Fotos von different devices auf einem zu co-chair dazu? Can I use the foto iCloud library to consolidate my fotos from different devices on a single device? At ist mein Ziel: My goal: Matrix von allen mei
-
eStudio 281 digital copier, printer, Fax, Scanner
Hello We have a Toshiba eStudio 281, which is connected to a Microsoft Windows network. I want to ensure that only certain users can print in color on it so that other users can print only in black and white. I can't find this information in the manu
-
I have windows7 on my sony laptop now my webcam is not working how to fix it
I can't use my webcam at all... I've put on Skype and can chat but I cannot use the webcam. How can I fix it when I ran a ck it says my webcam was ok
-
Error code OxC004E003 7 ultimate windows
Diagnostic report (1.9.0027.0):-----------------------------------------Validation of Windows data--> Validation code: 0Code of Validation caching online: 0x0Windows product key: *-* - 8T4YH - KM9TB-4PY2WWindows product key hash: WoIzABGnhIILQfDi6my3
-
Hi allI use oracle 10g R2 64 bits on 64-bit windows server 2008.I am facing problem with a table, which seems to be supposed to be a table partitioned, because it expects the 80000 lines per year.This is the normal table for the table script create t