Cisco limitations

Does any one have the idea there is any restriction of implementing Ciso New devices such as
Cisco1921-Sec/K9
and also remote sessions are allowed for terminal sessions.
Please reply soon
Regrds,
Danish Raza

What kind of limitations are you talking about?
And please do not solicit for quick answers on a freely contributed forum.

Similar Messages

Limited lifetime warranty

Hi,
I got this AIR-LAP1142N-E-K9 bought in may 2011 which is completely dead.
have tried to get in contact with the cisco tac regarding this, and they state is not under warrnanty anymore.
What do cisco mean by limited lifetime warranty?

The "Cisco Limited Lifetime Hardware Warranty" and "Cisco Extended Limited Lifetime Hardware Warranty" were in response to HP.
At one point, our Cisco SE and AM tried to deny these programs existed. When I showed them the link they changed their mind and said it's only valid for US and Canada. We challenged them to show us the details to back up their claims and they went quiet.
This program is very, very unpopular within Cisco. It gives me the impression that this program was announced to the public without consultation within Cisco.

Chs435hdc

hope to get help with my fios dvr. it is not properly formatting a 2TB drive. it appears to have formatted it as 1TB, at most.
the first question: can the 435 properly format a 2TB drive as such? esata iomega pro.
do I have any options with the 435...as fios customer? codes, format config options, something? NOTE: I recently moved; previously had a 7216 that properly formatted the drive. current projection, attached to 435, put the drive at ~125HD hours, but while attached to 7216 over ~300HD hours. it appears per tivo's latest claim with the 2TB internal, ~300HD hours is about right. not close with the 435. why??
so, is this a cisco limitation or has fios inexplicably dampened progress, cisco only.
for the record: fios technical support, after 2 hours, had no idea--continued to preach recommended drives; then pushes me off to the car wash folk; my best bet is somewhere else. they did not get it that the drive works but has not been formatted to its potential, and that my push is to find out why and if I can do something about it not called swap, tivo, or cancel.
imo, if this not a cisco limitation, cisco should find out why fios limiting their boxes. when dealing with HD storage, the more the better.
any help, thoughts, recommendations would be greatly appreciated. thanks.
john

for those interested given I appear to have stumped this otherwise eager group with what should be childs play for a cisco insider. the cisco box is inferior. per fios FINALLY, they would not limit the box format potential, so that narrows it down to unable to address the 2TB. shame on cisco, box produced <2 years ago.
updated HD storage is closer to 100HD hours. pitifiul.
I conclude, however, that I have been communicated so many contradictions by fios with other topics that it is possible someone else would tell me they limit the box. it no longers matters, case closed. cisco dvr and fios are bad mix--the cisco is sluggish, flakey, and worse of all, stupid.
moderator, please close lively discussion; no longer attending.

Linksys SE2800 and jumbo frames

Does the Linksys SE2800 gigabit 8 port switch support jumbo frames? Anyone have this switch? Any issues? Looking to replace a netgear gigabit switch that likes to forget that it has gigabit machines connected to it.

Hi Michael,
Actually had a chat with a colleague at linksys regarding your question, but he referred me to a datasheet, which left me with the question I started with. The technician said yes it suppported Jumbo frames but he could post me nothing in black and white..
Why not look at the Cisco Small Business umnanaged product the SG100D-08. It offers as the datasheet suggets;
Peace of mind:
All Cisco 100 Series switches are protected for the life of the product by the Cisco Limited Lifetime Hardware Warranty
Also, even though an unmanaged product, this series supports such features as;
1. Green Energy—Efficient Technology
The Cisco SG 100D-08 switch supports Green Energy-efficient
Technology. It can enter sleep mode, turn off unused ports, and adjust
power as needed. This increases energy efficiency to help businesses use
less power and save money.
2. Jumbo Frame Support
The Cisco SG 100D-08 switch supports frames up to 9,000 bytes called
jumbo frames. Jumbo Frame support improves network throughput and
reduces CPU utilization during large file transfers, such as multimedia files,
by allowing larger payloads in each packet.
regards Dave

2504 software update

Hi
I have just bought a new 2504 WLAN controller and 2x 2602 lightweight APs. I can't get them to talk because the controller has v7.2 software and needs to be at least 7.3. The unit has a mfg date oh Oct 12. Is there a way to get the upgrade with it being a new product without having an additional support contract on it?
Sent from Cisco Technical Support iPad App

In addition to Scott's recommendation, can you also ask your vendor to provide you with a Cisco Service Contract to allow you to download the 2500 firmware?
Just to give you a heads-up, please don't be fooled by your vendor to purchase a "maintenance contract" with your 2600 AP as all 802.11n-capable APs now have Cisco Limited Lifetime Warranty. You may need a maintenance contract to the 2504 should it fail.

German menu language on 7960G SIP Phone

Hi All
I have flashed a 7960G SCCP Phone to SIP Firmware.
Is there any possibility to give this phone another menu language, like german?
Or is this running only on SCCP Firmware?
Thank you

Hi,
thank you for the help.
Now I have these files in my TFTP Server.
These are my files:
OS79XX.TXT
P0S3-08-12-00
SEP0014A8924D6D.CNF.XML
<device>
<devicePool>
<callManagerGroup>
<members>
<member priority="0">
<callManager>
<ports>
<ethernetPhonePort>2000</ethernetPhonePort>
</ports>
<processNodeName> </processNodeName>
</callManager>
</member>
</members>
</callManagerGroup>
</devicePool>
<versionStamp>{Jan 01 2005 00:00:00}</versionStamp>
<loadInformation>P0S3-08-12-00</loadInformation>
<userLocale>
<name>German_Germany</name>
<langCode>de</langCode>
</userLocale>
<networkLocale>Germany</networkLocale>
<idleTimeout>0</idleTimeout>
<authenticationURL></authenticationURL>
<directoryURL></directoryURL>
<idleURL></idleURL>
<informationURL></informationURL>
<messagesURL></messagesURL>
<proxyServerURL></proxyServerURL>
<servicesURL></servicesURL>
</device>
SIP0014A8924D6D.cnf
# SIP Configuration Generic File
# Line 1 appearance
line1_name: 01010101001
# Line 1 Registration Authentication
line1_authname: "UNPROVISIONED"
# Line 1 Registration Password
line1_password: "UNPROVISIONED"
# Line 2 appearance
line2_name: football
# Line 2 Registration Authentication
line2_authname: "UNPROVISIONED"
# Line 2 Registration Password
line2_password: "UNPROVISIONED"
####### New Parameters added in Release 2.0 #######
# All user_parameters have been removed
# Phone Label (Text desired to be displayed in upper right corner)
phone_label: "" ; Has no effect on SIP messaging
# Line 1 Display Name (Display name to use for SIP messaging)
line1_displayname: "User ID"
# Line 2 Display Name (Display name to use for SIP messaging)
line2_displayname: ""
####### New Parameters added in Release 3.0 ######
# Phone Prompt (The prompt that will be displayed on console and telnet)
phone_prompt: "SIP Phone" ; Limited to 15 characters (Default - SIP Phone)
# Phone Password (Password to be used for console or telnet login)
phone_password: "cisco" ; Limited to 31 characters (Default - cisco)
# User classifcation used when Registering [ none(default), phone, ip ]
user_info: none
SIPDefault.cnf
# SIP Default Generic Configuration File
# Image Version
image_version: P0S381200
language: german
# Proxy Server
proxy1_address: "" ; Can be dotted IP or FQDN
proxy2_address: "" ; Can be dotted IP or FQDN
proxy3_address: "" ; Can be dotted IP or FQDN
proxy4_address: "" ; Can be dotted IP or FQDN
proxy5_address: "" ; Can be dotted IP or FQDN
proxy6_address: "" ; Can be dotted IP or FQDN
# Proxy Server Port (default - 5060)
proxy1_port: 5060
proxy2_port: 5060
proxy3_port: 5060
proxy4_port: 5060
proxy5_port: 5060
proxy6_port: 5060
# Proxy Registration (0-disable (default), 1-enable)
proxy_register: 0
# Phone Registration Expiration [1-3932100 sec] (Default - 3600)
timer_register_expires: 3600
# Codec for media stream (g711ulaw (default), g711alaw, g729a)
preferred_codec: g711ulaw
# TOS bits in media stream [0-5] (Default - 5)
tos_media: 5
# Inband DTMF Settings (0-disable, 1-enable (default))
dtmf_inband: 1
# Out of band DTMF Settings (none-disable, avt-avt enable (default), avt_always - always avt )
dtmf_outofband: avt
# DTMF dB Level Settings (1-6dB down, 2-3db down, 3-nominal (default), 4-3db up, 5-6dB up)
dtmf_db_level: 3
# SIP Timers
timer_t1: 500 ; Default 500 msec
timer_t2: 4000 ; Default 4 sec
sip_retx: 10 ; Default 10
sip_invite_retx: 6 ; Default 6
timer_invite_expires: 180 ; Default 180 sec
####### New Parameters added in Release 2.0 #######
# Dialplan template (.xml format file relative to the TFTP root directory)
dial_template: dialplan
# TFTP Phone Specific Configuration File Directory
tftp_cfg_dir: "" ; Example: ./sip_phone/
# Time Server (There are multiple values and configurations refer to Admin Guide for Specifics)
sntp_server: "" ; SNTP Server IP Address
sntp_mode: directedbroadcast ; unicast, multicast, anycast, or directedbroadcast (default)
time_zone: EST ; Time Zone Phone is in
dst_offset: 1 ; Offset from Phone's time when DST is in effect
dst_start_month: April ; Month in which DST starts
dst_start_day: "" ; Day of month in which DST starts
dst_start_day_of_week: Sun ; Day of week in which DST starts
dst_start_week_of_month: 1 ; Week of month in which DST starts
dst_start_time: 02 ; Time of day in which DST starts
dst_stop_month: Oct ; Month in which DST stops
dst_stop_day: "" ; Day of month in which DST stops
dst_stop_day_of_week: Sunday ; Day of week in which DST stops
dst_stop_week_of_month: 8 ; Week of month in which DST stops 8=last week of month
dst_stop_time: 2 ; Time of day in which DST stops
dst_auto_adjust: 1 ; Enable(1-Default)/Disable(0) DST automatic adjustment
time_format_24hr: 1 ; Enable(1 - 24Hr Default)/Disable(0 - 12Hr)
# Do Not Disturb Control (0-off, 1-on, 2-off with no user control, 3-on with no user control)
dnd_control: 0 ; Default 0 (Do Not Disturb feature is off)
# Caller ID Blocking (0-disbaled, 1-enabled, 2-disabled no user control, 3-enabled no user control)
callerid_blocking: 0 ; Default 0 (Disable sending all calls as anonymous)
# Anonymous Call Blocking (0-disabled, 1-enabled, 2-disabled no user control, 3-enabled no user control)
anonymous_call_block: 0 ; Default 0 (Disable blocking of anonymous calls)
# DTMF AVT Payload (Dynamic payload range for AVT tones - 96-127)
dtmf_avt_payload: 101 ; Default 101
# Sync value of the phone used for remote reset
sync: 1 ; Default 1
####### New Parameters added in Release 2.1 #######
# Backup Proxy Support
proxy_backup: "" ; Dotted IP of Backup Proxy
proxy_backup_port: 5060 ; Backup Proxy port (default is 5060)
# Emergency Proxy Support
proxy_emergency: "" ; Dotted IP of Emergency Proxy
proxy_emergency_port: 5060 ; Emergency Proxy port (default is 5060)
# Configurable VAD option
enable_vad: 0 ; VAD setting 0-disable (Default), 1-enable
####### New Parameters added in Release 2.2 ######
# NAT/Firewall Traversal
nat_enable: 0 ; 0-Disabled (default), 1-Enabled
nat_address: "" ; WAN IP address of NAT box (dotted IP or DNS A record only)
voip_control_port: 5060 ; UDP port used for SIP messages (default - 5060)
start_media_port: 16384 ; Start RTP range for media (default - 16384)
end_media_port: 32766 ; End RTP range for media (default - 32766)
nat_received_processing: 0 ; 0-Disabled (default), 1-Enabled
# Outbound Proxy Support
outbound_proxy: "" ; restricted to dotted IP or DNS A record only
outbound_proxy_port: 5060 ; default is 5060
####### New Parameter added in Release 3.0 #######
# Allow for the bridge on a 3way call to join remaining parties upon hangup
cnf_join_enable : 1 ; 0-Disabled, 1-Enabled (default)
####### New Parameters added in Release 3.1 #######
# Allow Transfer to be completed while target phone is still ringing
semi_attended_transfer: 1 ; 0-Disabled, 1-Enabled (default)
# Telnet Level (enable or disable the ability to telnet into the phone)
telnet_level: 1 ; 0-Disabled (default), 1-Enabled, 2-Privileged
####### New Parameters added in Release 4.0 #######
# XML URLs
services_url: "" ; URL for external Phone Services
directory_url: "" ; URL for external Directory location
logo_url: "" ; URL for branding logo to be used on phone display
# HTTP Proxy Support
http_proxy_addr: "" ; Address of HTTP Proxy server
http_proxy_port: 80 ; Port of HTTP Proxy Server (80-default)
# Dynamic DNS/TFTP Support
dyn_dns_addr_1: "" ; restricted to dotted IP
dyn_dns_addr_2: "" ; restricted to dotted IP
dyn_tftp_addr: "" ; restricted to dotted IP
# Remote Party ID
remote_party_id: 0 ; 0-Disabled (default), 1-Enabled
####### New Parameters added in Release 4.4 #######
# Call Hold Ringback (0-off, 1-on, 2-off with no user control, 3-on with no user control)
call_hold_ringback: 0 ; Default 0 (Call Hold Ringback feature is off)
####### New Parameters added in Release 6.0 #######
# Dialtone Stutter for MWI
stutter_msg_waiting: 0 ; 0-Disabled (default), 1-Enabled
# RTP Call Statistics (SIP BYE/200 OK message exchange)
call_stats: 0 ; 0-Disabled (default), 1-Enabled
xmlDefault.CNF.XML
<?xml version="1.0"?>
-<Default>
-<callManagerGroup>
-<members>
-<member priority="0">
-<callManager>
-<ports>
<ethernetPhonePort>2000</ethernetPhonePort>
</ports>
<processNodeName/>
</callManager>
</member>
</members>
<loadInformation6 model="IP Phone 7910"/>
<loadInformation124 model="Addon 7914"/>
<loadInformation9 model="IP Phone 7935"/>
<loadInformation8 model="IP Phone 7940"/>
<loadInformation7 model="IP Phone 7960">P0S3-8-12-00</loadInformation7>
<loadInformation20000 model="IP Phone 7905"/>
<loadInformation30008 model="IP Phone 7902"/>
<loadInformation30002 model="IP Phone 7920"/>
<loadInformation30019 model="IP Phone 7936"/>
<loadInformation30006 model="IP Phone 7970"/>
<loadInformation30018 model="IP Phone 7961"/>
<loadInformation30007 model="IP Phone 7912"/>
</callManagerGroup>
</Default>
The folders "German_Germany"; "germany" and the file German_Germany.aar are in TFTP folder,too. But my phone is doing nothing with this files.
This is the log of TFTP Server:
Rcvd DHCP inform Msg for IP 192.168.0.9, Mac 02:70:7E:7F:09:01 [04/03 13:21:54.559]
Rcvd DHCP inform Msg for IP 192.168.0.9, Mac 02:70:7E:7F:09:01 [04/03 13:21:58.562]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:14:A8:92:4D:6D [04/03 13:22:45.892]
Previously allocated address 192.168.0.6 acked [04/03 13:22:45.893]
Connection received from 192.168.0.6 on port 50798 [04/03 13:22:46.037]
Read request for file <CTLSEP0014A8924D6D.tlv>. Mode octet [04/03 13:22:46.038]
File <CTLSEP0014A8924D6D.tlv> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:22:46.038]
Connection received from 192.168.0.6 on port 50798 [04/03 13:22:47.036]
Read request for file <CTLSEP0014A8924D6D.tlv>. Mode octet [04/03 13:22:47.036]
File <CTLSEP0014A8924D6D.tlv> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:22:47.036]
Connection received from 192.168.0.6 on port 50798 [04/03 13:22:51.035]
Read request for file <CTLSEP0014A8924D6D.tlv>. Mode octet [04/03 13:22:51.036]
File <CTLSEP0014A8924D6D.tlv> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:22:51.036]
Connection received from 192.168.0.6 on port 50799 [04/03 13:22:51.056]
Read request for file <SEP0014A8924D6D.cnf.xml>. Mode octet [04/03 13:22:51.057]
File <SEP0014A8924D6D.cnf.xml> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:22:51.057]
Connection received from 192.168.0.6 on port 50800 [04/03 13:22:51.085]
Read request for file <SIP0014A8924D6D.cnf>. Mode octet [04/03 13:22:51.086]
File <SIP0014A8924D6D.cnf> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:22:51.086]
Connection received from 192.168.0.6 on port 50801 [04/03 13:22:51.105]
Read request for file <MGC0014A8924D6D.cnf>. Mode octet [04/03 13:22:51.105]
File <MGC0014A8924D6D.cnf> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:22:51.105]
Connection received from 192.168.0.6 on port 50802 [04/03 13:22:51.124]
Read request for file <XMLDefault.cnf.xml>. Mode octet [04/03 13:22:51.127]
Using local port 65426 [04/03 13:22:51.127]
<XMLDefault.cnf.xml>: sent 3 blks, 1077 bytes in 0 s. 0 blk resent [04/03 13:22:51.135]
Connection received from 192.168.0.6 on port 50803 [04/03 13:22:51.180]
Read request for file <P0S3-8-12-00.loads>. Mode octet [04/03 13:22:51.180]
Using local port 65427 [04/03 13:22:51.180]
<P0S3-8-12-00.loads>: sent 1 blk, 458 bytes in 0 s. 0 blk resent [04/03 13:22:51.183]
Rcvd DHCP inform Msg for IP 192.168.0.9, Mac 02:70:7E:7F:09:01 [04/03 13:24:17.151]
Rcvd DHCP inform Msg for IP 192.168.0.9, Mac 02:70:7E:7F:09:01 [04/03 13:24:20.150]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:14:A8:92:4D:6D [04/03 13:24:34.219]
Previously allocated address 192.168.0.6 acked [04/03 13:24:34.220]
Connection received from 192.168.0.6 on port 50823 [04/03 13:24:34.258]
Read request for file <SIPDefault.cnf>. Mode octet [04/03 13:24:34.259]
Using local port 64133 [04/03 13:24:34.259]
Connection received from 192.168.0.6 on port 50823 [04/03 13:24:35.250]
Read request for file <SIPDefault.cnf>. Mode octet [04/03 13:24:35.250]
Using local port 64134 [04/03 13:24:35.250]
Connection received from 192.168.0.6 on port 50823 [04/03 13:24:39.250]
Read request for file <SIPDefault.cnf>. Mode octet [04/03 13:24:39.250]
Using local port 64135 [04/03 13:24:39.250]
<SIPDefault.cnf>: sent 13 blks, 6203 bytes in 0 s. 0 blk resent [04/03 13:24:39.284]
Connection received from 192.168.0.6 on port 50824 [04/03 13:24:39.485]
Read request for file <SIP0014A8924D6D.cnf>. Mode octet [04/03 13:24:39.485]
File <SIP0014A8924D6D.cnf> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:24:39.485]
TIMEOUT waiting for Ack block #1 [04/03 13:24:49.260]
TIMEOUT waiting for Ack block #1 [04/03 13:24:50.251]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:14:A8:92:4D:6D [04/03 13:26:50.610]
Previously allocated address 192.168.0.6 acked [04/03 13:26:50.611]
Connection received from 192.168.0.6 on port 50857 [04/03 13:26:50.649]
Read request for file <SIPDefault.cnf>. Mode octet [04/03 13:26:50.649]
Using local port 64137 [04/03 13:26:50.649]
Connection received from 192.168.0.6 on port 50857 [04/03 13:26:51.641]
Read request for file <SIPDefault.cnf>. Mode octet [04/03 13:26:51.642]
Using local port 64138 [04/03 13:26:51.642]
Connection received from 192.168.0.6 on port 50857 [04/03 13:26:55.641]
Read request for file <SIPDefault.cnf>. Mode octet [04/03 13:26:55.641]
Using local port 64139 [04/03 13:26:55.642]
<SIPDefault.cnf>: sent 13 blks, 6203 bytes in 0 s. 0 blk resent [04/03 13:26:55.676]
Connection received from 192.168.0.6 on port 50858 [04/03 13:26:55.874]
Read request for file <SIP0014A8924D6D.cnf>. Mode octet [04/03 13:26:55.875]
File <SIP0014A8924D6D.cnf> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:26:55.875]
TIMEOUT waiting for Ack block #1 [04/03 13:27:05.651]
TIMEOUT waiting for Ack block #1 [04/03 13:27:06.645]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:14:A8:92:4D:6D [04/03 13:28:40.670]
Previously allocated address 192.168.0.6 acked [04/03 13:28:40.671]
Connection received from 192.168.0.6 on port 50797 [04/03 13:28:40.813]
Read request for file <CTLSEP0014A8924D6D.tlv>. Mode octet [04/03 13:28:40.813]
File <CTLSEP0014A8924D6D.tlv> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:28:40.814]
Connection received from 192.168.0.6 on port 50797 [04/03 13:28:41.803]
Read request for file <CTLSEP0014A8924D6D.tlv>. Mode octet [04/03 13:28:41.804]
File <CTLSEP0014A8924D6D.tlv> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:28:41.804]
Connection received from 192.168.0.6 on port 50797 [04/03 13:28:45.803]
Read request for file <CTLSEP0014A8924D6D.tlv>. Mode octet [04/03 13:28:45.803]
File <CTLSEP0014A8924D6D.tlv> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:28:45.804]
Connection received from 192.168.0.6 on port 50798 [04/03 13:28:45.824]
Read request for file <SEP0014A8924D6D.cnf.xml>. Mode octet [04/03 13:28:45.824]
File <SEP0014A8924D6D.cnf.xml> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:28:45.824]
Connection received from 192.168.0.6 on port 50799 [04/03 13:28:45.853]
Read request for file <SIP0014A8924D6D.cnf>. Mode octet [04/03 13:28:45.853]
File <SIP0014A8924D6D.cnf> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:28:45.853]
Connection received from 192.168.0.6 on port 50800 [04/03 13:28:45.874]
Read request for file <MGC0014A8924D6D.cnf>. Mode octet [04/03 13:28:45.876]
File <MGC0014A8924D6D.cnf> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:28:45.876]
Connection received from 192.168.0.6 on port 50801 [04/03 13:28:45.895]
Read request for file <XMLDefault.cnf.xml>. Mode octet [04/03 13:28:45.895]
Using local port 64147 [04/03 13:28:45.895]
<XMLDefault.cnf.xml>: sent 3 blks, 1077 bytes in 0 s. 0 blk resent [04/03 13:28:45.898]
Connection received from 192.168.0.6 on port 50802 [04/03 13:28:45.935]
Read request for file <P0S3-8-12-00.loads>. Mode octet [04/03 13:28:45.936]
Using local port 64148 [04/03 13:28:45.936]
<P0S3-8-12-00.loads>: sent 1 blk, 458 bytes in 0 s. 0 blk resent [04/03 13:28:45.937]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:14:A8:92:4D:6D [04/03 13:30:28.597]
Previously allocated address 192.168.0.6 acked [04/03 13:30:28.597]
Connection received from 192.168.0.6 on port 50787 [04/03 13:30:28.636]
Read request for file <SIPDefault.cnf>. Mode octet [04/03 13:30:28.636]
Using local port 64149 [04/03 13:30:28.636]
Connection received from 192.168.0.6 on port 50787 [04/03 13:30:29.627]
Read request for file <SIPDefault.cnf>. Mode octet [04/03 13:30:29.628]
Using local port 64150 [04/03 13:30:29.628]
Connection received from 192.168.0.6 on port 50787 [04/03 13:30:33.627]
Read request for file <SIPDefault.cnf>. Mode octet [04/03 13:30:33.628]
Using local port 64151 [04/03 13:30:33.628]
<SIPDefault.cnf>: sent 13 blks, 6203 bytes in 0 s. 0 blk resent [04/03 13:30:33.658]
Connection received from 192.168.0.6 on port 50788 [04/03 13:30:33.856]
Read request for file <SIP0014A8924D6D.cnf>. Mode octet [04/03 13:30:33.856]
File <SIP0014A8924D6D.cnf> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:30:33.857]
Rcvd DHCP inform Msg for IP 192.168.0.9, Mac 02:70:7E:7F:09:01 [04/03 13:30:41.756]
TIMEOUT waiting for Ack block #1 [04/03 13:30:43.637]
TIMEOUT waiting for Ack block #1 [04/03 13:30:44.629]
Rcvd DHCP inform Msg for IP 192.168.0.9, Mac 02:70:7E:7F:09:01 [04/03 13:30:44.759]
Rcvd DHCP inform Msg for IP 192.168.0.9, Mac 02:70:7E:7F:09:01 [04/03 13:32:11.253]
Rcvd DHCP inform Msg for IP 192.168.0.9, Mac 02:70:7E:7F:09:01 [04/03 13:32:14.253]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:14:A8:92:4D:6D [04/03 13:33:50.655]
Previously allocated address 192.168.0.6 acked [04/03 13:33:50.656]
Connection received from 192.168.0.6 on port 50795 [04/03 13:33:50.696]
Read request for file <SIPDefault.cnf>. Mode octet [04/03 13:33:50.696]
Using local port 62124 [04/03 13:33:50.696]
Connection received from 192.168.0.6 on port 50795 [04/03 13:33:51.685]
Read request for file <SIPDefault.cnf>. Mode octet [04/03 13:33:51.686]
Using local port 62125 [04/03 13:33:51.686]
Connection received from 192.168.0.6 on port 50795 [04/03 13:33:55.685]
Read request for file <SIPDefault.cnf>. Mode octet [04/03 13:33:55.685]
Using local port 62126 [04/03 13:33:55.685]
<SIPDefault.cnf>: sent 13 blks, 6203 bytes in 0 s. 0 blk resent [04/03 13:33:55.723]
Connection received from 192.168.0.6 on port 50796 [04/03 13:33:55.915]
Read request for file <SIP0014A8924D6D.cnf>. Mode octet [04/03 13:33:55.915]
File <SIP0014A8924D6D.cnf> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [04/03 13:33:55.915]
TIMEOUT waiting for Ack block #1 [04/03 13:34:05.698]
TIMEOUT waiting for Ack block #1 [04/03 13:34:06.691]
Is there anybody, who can help me with this problem.

Anybody know a reseller that would download/sell a firmeware for 2504 wireless controller or what service to buy to be able to get it?

anybody know a reseller that would download/sell a firmeware for 2504 wireless controller or what service to buy to be able to get it?

Be aware that you do not need to purchase SmartNET for your APs.
Thanks for the ratings, Marek.
Be aware that nearly all 802.11n APs (some exclusion to AP1250) are covered under the new Cisco Limited Lifetime Warranty. Read through the link provided. This is why I posted that you do not need maintenance contract for the APs. The main thing to understand is that if you need to RMA your AP, it'll take 10-business days for the replacement part to be sent.
I have spoken to some Cisco Authorized Reseller and some Cisco TAC engineers who insist that the Cisco LLW don't exist or doesn't apply to BLAH model. Don't be fooled.

Cisco 6248 Connectivity Limitations

Hello,
I am new to the UCS Fabric Interconnects and am wondering if there are limitations to connecting a Cisco 3925 Gen 2 ISR (desinated Voice Gateway) to a fabric interconnect, specifically a 6248 with the latest version of code. It appears that the FI's support 802.1Q VLAN encapsulation and trunking, which is typically configured in the cisco voice world for any downstream switchport interface to pass Voice, Data, Server VLAN's to the corresponding devices. It also appears that the FI's will support some forms of quality service, like Priority Queing. I have not seen where the FI's support LLQ or CBWFQ. So at the end of the day I would like to know if there are any limitations to connecting a Cisco 3925 Gen 2 ISR to which will be used as a Voice Gateway. I know that typically its best practice to connect to some other switch, but since the FI has the capabilitiy to running in "switched-mode" I didnt know if this would work. Thanks to all that review this as well as thanks in advance to anyone who lends any thoughts
- TA

SAN port-channels are not supported between UCS FI and Brocade SAN switches. You will need to use individual links.
Leave the UCS fibre channel in default end-host-mode. This will connect to Brocade in the Access Gateway mode (Cisco's NPIV)

Network becomes limited or unavailable as soon as i connect to cisco anyconnect secure mobility client, version - 3.1.05170

Hiee,
I am using cisco anyconnect secure mobility client, version - 3.1.05170 , in my windows 8.1 PC to access vpn to my office desktop. But as soon as i connect cisco anyconnect client, my wifi networks becomes limited or unavailable. Thus, i am not able to get remote access to my office desktop. And not even able to access any other websites also. But as soon as i disconnect from the cisco anyconnect vpn client, every thing becomes normal, and the exclamation mark from the network icon also disappears.
kindly help me in this regard.
Thanks and regards
Neeraj

There are a few things to consider here:
- The IPSec VPN client is EoL, so even if we consider this as a bug, it wouldn't be fixed
- fixing the file server access would break the DHCP renew which means there is no completely clean way to fix this, at least not at the IP level since the client can't route to the same destination using 2 different paths.
Is there any chance we could do a static policy NAT for the DHCP traffic so it appears to come from another IP? It's twisted and it may not work (the client might use the DHCP server IP embedded inside the payload and not the source IP) but if it does, then we'd fix the overlap.
Could the server use another IP address for the DHCP service (much like using a loopback for a certain service on a router?)
A third solution would be to NAT the destination server IP on the ASA for traffic from the IP pool going to the server. We'd need DNS doctoring as well to resolve the server's name to the NATted IP. This way the server would appear from the VPN client as being at a different IP, thereby fixing the overlap.
All these potential solutions are quite involved... you may be better off wityh a simpler design: splitting of your server into 2 or using something else to do DHCP for the VPN clients.

Did Cisco ISE have limitation for policy setting?

Deat All,
Did anyone know about Cisco ISE limitation about policy setting?
Right now my setting for windows posture policy around 200 windows patch checking, did ISE have limitation such as maximum windows patching policy line?
Thanks you
Best Regards

Here is the nswer for your first question.
Cisco ISE profiler collects a significant amount of endpoint data from the network in a short period of time. It causes Java Virtual Machine (JVM) memory utilization to go up due to accumulated backlog when some of the slower Cisco ISE components process the data generated by the profiler, which results in performance degradation and stability issues.
To ensure that the profiler does not increase the JVM memory utilization and prevent JVM to go out of memory and restart, limits are applied to the following internal components of the profiler:
Endpoint Cache—Internal cache is limited in size that has to be purged periodically (based on least recently used strategy) when the size exceeds the limit.
Forwarder—The main ingress queue of endpoint information collected by the profiler.
Event Handler—An internal queue that disconnects a fast component, which feeds data to a slower processing component (typically related to a database query).
For more information go through :
http://www.cisco.com/c/en/us/td/docs/security/ise/1-2/user_guide/ise_user_guide/ise_prof_pol.html#12624

Cisco 1602e AP bandwidth limiting, qos question.

I have a few AIR-SAP1602E-A-K9, and I was wondering if they are able to do any type of QoS or bandwidth throttling/limiting based on destination ip address or perhaps even just limiting the speed of that wireless interface? Essentially we'd like it so people on the "Internet only" ssid can use a certain amount of bandwidth - like 4mb or something. If this AP simply can't do it, then are there any suggestions for what I should do instead? Thanks in advance for any assistance!

You have an autonomous AP and its really not possible to limit the traffic. You might be able to setup am acl on the router to limit the bandwidth as long as these users are on a different subnet than your internal user. Others in the past have used a 3rd party wifi hotspot software. These software you can have users login or not, but you can control bandwidth. Some are paid versions and some are free. You would just have to look around and try them.
Sent from Cisco Technical Support iPhone App

Cisco firewall rate limited syslogs and MARS

We're getting a ton of informational packets (tcp build / teardown) from firewalls here. I can kill this at the source (drop to "notification" level, filter out the build / teardown events, etc.) but would rather not throw this stuff away (good clues in an investigation).
I can filter this on the MARS side so rules don't fire, but that doesn't address the performance hit at the firewall, or the traffic on the network.
I can rate limit at the firewall - if I do will MARS be able to parse this out properly - i.e if there's a rule that fires on a 100 count for example, and a firewall that's set to rate limit a certain event to, say, every 200 instances of the event, and single syslog shows up at MARS with rate limited information in the packet, will the MARS rule fire?
hope this makes sense - thanks

What kind of firewall are you running? ASA? FWSM? Something else?
If you're running an ASA, the ideal solution would be to implement Netflow Secure Event Logging (NSEL). This feature uses Netflow v9 to handle security event logging along with traffic flow data. Using NSEL can provide performance improvements over syslog, both on the ASA, and on your network.
Part of the configuration process includes a command to disable the redundant syslog types already handled by NSEL. Many of those are the same types of logs you mentioned (buildups/teardowns, etc). It's very simple to configure - you can read more about it here, in the ASA 8.2 CLI Configuration Guide:
Configuring Network Secure Event Logging (NSEL)
If you're running a FWSM, the same option isn't available. Instead, you might want to reconsider disabling some of the log types that aren't really providing much benefit relative to the load. In fact, Cisco themselves recommend disabling some of the more unimportant (but frequent) log types.
From the "Cisco SIEM Deployment Guide", one of the "Smart Business Architecture" design guides (emphasis mine):
At logging level Informational, Cisco recommends disabling the following messages, as they are of little interest for SIEM analysis: 305010: The address translation slot was deleted 305011: A TCP, UDP, or ICMP address translation slot was created 305012: The address translation slot was deletedTo disable these messages, use the following configuration commands: no logging message 305010 no logging message 305011 no logging message 305012For more aggressive tuning, you may also consider disabling the following messages: 302014: A TCP connection between two hosts was deleted 302016: A UDP connection slot between two hosts was deletedIf dynamic Network Address Translation (NAT) is not configured on the appliance, message 302013 (for TCP connection slot creation) can also be disabled.
So, that's at least 6 possible log types that can be disabled with no impact: 302013, 302014, 302016, 305010, 305011, and 305012. And that's straight from Cisco's own documentation.
Now, to expand on that ...
- if 302016 (UDP teardown) can be disabled, why not 302015 (UDP create)?
- similarly, what about 302020 and 302021 (ICMP)? Disable those as well?
Final list:
302013
302014
302015
302016
302020
302021
305010
305011
305012
In the end, though, only you can determine which options are acceptable for your environment.
Note: all 3020xx log types listed are disabled automatically during the NSEL configuration process.

Cisco 2950 rate limiting

Good evening I must limit the rate bandwidth of a host plugged on my Fastethernet.
In my lab configuration I try in conjunction the comand: class-map policy-map and a access-list that match my interesting traffic as follow below:
class-map match-all CM5
match access-group name maclist1
policy-map PM5
class CM5
police 50000000 4096 exceed-action drop
mac access-list extended maclist1
permit any any
This the output of my #sh int
5 minute input rate 5577000 bits/sec, 442 packets/sec
5 minute output rate 247000 bits/sec, 388 packets/sec
Anyone have try to limiting the bandwidth on the switch 2950 with IOS Version 12.1(22)E3
Can anyone tell me the aright parameter of policy-map to limite the rate at 15 or 20Mbps?
Any information that you can send me are welcomed.
Best Regards
Davide

police 50000000 4096 exceed-action drop is policing at 50 Mbps. You want 15 Mbps. Also, you will not see drops until the ingress traffic rate on that port exceeds 50 Mbps. Eventhough, the input rate output is at 5 min interval which would not really gie you an accurate idea of how much traffic is ingressing, I doubt that the traffic is exceeding the policed value. In testing this also, you need to make sure that the upload is coming from the PC where the policed ingress is configured since the police is only supported in ingress. What that basically means is if you FTP/Download from the PC with the police you will find that the download speed is still well above the policed rate that's because the the download on this PC's perspective is an egress rate. Just something to think about when policing on ingress. This platfomr does not support egress policing.
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat2950/12122ea5/2950scg/swqos.htm#wp1025402

GRE tunnel feature limitation on Cisco Catalyst 4500X

Hi,
I have a customer with three sites. They have the Cisco catalyst 4500-X at each sites and wish to create GRE tunnels between each of these switches.
I have a vague reference which tells me the Cisco cat 4500-x or any cat 4500 for that matter does have severe limitations when GRE tunnels are created, especially limiting the bandwidth to 70kbps. Its also not recommended for data traffic but control plane traffic.
Please advice.

No experts to answer this?

Bandwidth limitations of Cisco 7246

What is the throughput of a 7246 UBR?
I have 2 in service and it appears I can only get a maximum of 40Meg .
I am using MC16C card and NPE225 engines each card has approx. 700 customers on it.
If we upgrade to a 7246vxr with NPEG1 and MC28U.
What would max throughput be?
Thanks
Dave

Hi
ACS performance is a very complex issue and depends largely on
1) auth protocol (anything eap is SLOW)
2) backend (anything external is SLOW)
3) server CPU
We did some performance tests a few years ago and could get up to 1000 auths/sec for MSCHAP against internal DB.
AD authentication/group mapping can take several seconds to complete.
ACSs big problem is limited concurrency when authentication time is high. There are some bottlenecks that effectively limit the number of concurrent authentications to 20. This is the max number of tcp/ip connections between CSRadius/CSTacacs and CSAuth. Inside CSRadius there are 50 dedicated authentication threads multiplexing requests over the 20 tcp/ip connections to CSauth. Messages to CSauth are blocking - so 20 simultaneous authentications that took 1 second would cap performance to 20 auths/sec.
EAP-TLS and now EAP-FAST are really really slow becase they send multiple rounds over RADIUS using challenge/response marshalled between the device and the 802.1x supplicant.
Putting ACS onto a quad CPU server wont reduce back-end external db latency or increase concurrency.
The only way to increase performance is to add more servers... and then you'll also have to get into load balancing :(
IMHO Cisco needs to make a low cost "ACS on a blade" and have one in each device. Have the config pushed down from a central database.
Darran

Cisco limitations

Similar Messages

Maybe you are looking for