Config-Archive Issue on PI 1.3

Hi Everyone,
      Customer has recently installed PI 1.3 software, and then used it to back up or restore devices' config. However, when imported all devices into PI 1.3 by csv template and set up some setting about schedule daily job of configuration-archives, we found that the status of the lastest archive still displayed the initial inventory collection on "Configuration Archives", it seems that PI can't automatically get devices' configuration daily, however we can find the schedule jobs display success. That's so weird.
       Most of devices are Cisco 800 series(such as 871、887 etc) and two of them are WLC(5500 and 7500), all version of them satisfy with PI 1.3 Support devices datasheet's requestment.
       All of devices have been added into ACS 5.4 and used TACACS + to authenticate user by AD account. PI just uses local account to login and uses 15-level username and password to telnet devices to get their configuration file. In LMS case , we can try to edit the prompt symbol in tacacs file on lms server. In this case, we have checked the ACS AAA report and found that the PI has normally used some commands to get configuration such as show running-config, copy etc.
       Please give some advices, thx in advance.
Regards,
Tira

Any update?

Similar Messages

Lms 4.2 , Config Archival issue

Hi
Please have a look to the below image , what is the reason for this failed Archival and how to solve this issue
thanks
Ibrahim

The 25 success means LMS is working fine.
The 277 failed means LMS has problems communicating with these devices.
Causes can be:
Bad credentials
ACL's on the device not permitting LMS ip address to talk to the device.
protocols (TELNET, SSH, RCP, SCP) not running on the devices.
firewalls or ACL's on routers not permitting LMS protocols.
Pick a single device, test the protocols comming from the server to the device, test credentials.
Cheers,
Michel

Error Message in config Archive in RME in LMS 4.2

I got the below error message in the config archive in the LMS 4.2.
CM0056 Config fetch failed for 10.0.0.10 Cause: CM0204 Could not create DeviceContext for 797 Cause: CM0202 Could not access 10.0.0.10 via SNMP. Action: Check the Read Community string Action: Check if required device packages are available. Action: Check if protocol is supported by device and required device package is installed.
Switch model type is 3560 and 2960
Please tell me the reason for this issue.

Are you usig only TFTP option to archive configuration. Try to use the telnet/ssh. TFTP as a protocol set for config archive.
Check the Credential verificatio job to see if the crendentials are configured correctly.
-Thanks

LMS 4.2.5 Syslog/Automated Action/Config mgmt issue

LMS 4.2.5 on Windows
We use the server as it's own Syslog server. The Syslog collector status is fine. I see syslogs coming into the server. However, I just made some changes on a router so ran a syslog report on it, but nothing was returned. I Tested the Collector Subscription and everything was fine.
We also have Automated Actions configured on certain syslog messages (duplex mismatch for example). There is an AA configured to send my team e-mails when this event occurs. There was a device that had two days worth of syslog messages complaining about this issue. Yet, we only received about 10 e-mails from the LMS system on it.
Another issue is with Configuration Mgmt. I fixed the duplex mismatch listed above and went to check the config tree to see if or when something changed. The last config archive was pretty old and I know changes were made on the device since then. This tells me that the LMS server didn't get notified of the config change or it would have gone out and checked it.
The one thing in common on all of the above is Syslog messages. LMS will take actions based on receiving these messages and those actions don't seem to be firing.
Any ideas would be greatly appreciated.
Thanks,
Mike S.

To confirm if the device is sending the syslogs and they are being received by LMS server properly, check the $NMSROOT/log/syslog.log and see it has the syslog from the device.
Unless syslog is there on syslog.log, we don't expect LMS to react on any AA.
For configuration backup, try to sync the device config by initiating a manual job to update the latest configuration from device. Even if there is no Automated Action working, you should still have a reoccurring/scheduled job configured to archive configuration backup periodically.
Following is a document I created for Syslog troubleshooting :
Ciscoworks LMS : Syslog in a Nutshell!
-Thanks
Vinod
**Encourage Contributors. RATE Them.**

RME config archive problem - lms 3.2

just wondering if anyone else has seen this.
about a month or so ago, I grabbed about 6 or 7 patches for our ciscoworks machine, across cm, rme, and cs. (yeah, we were a little behind)
after applying these patches, it seems, all of the 2960s and 4948s are failing the config archive with the following:
cm00139: could not archive config:cause: action: verify that device is managed and credentials are correct. Increase timeout
value if required.
so I've triple checked the credential set applied to these devices, adjusted timeout and retry values, and have gotten nowhere.
Deleting these devices doesn't seem to help, they are rediscovered just fine, but the config archive continues to fail.
Other than maybe trying to reinstall the rme patches (or uninstall) that were recently applied, I'm out of ideas. This is LMS 3.2.1 with
cm 5.2.2
cs 3.3.1
rme 4.3.2
running on windows server 08.
So if anyone may have seen this and/or has any advice, I'd appreciate it. Thanks - chris

ok, so it's been a year and a half since last post. So in addition to the above mentioned archive failures with the 4948s, the 4948s were also showing up in config out of sync summary. The only difference that were showing between running and startup was the ntp clock period.
I did see that the clock period statement was in the exclude list for routers and a bunch of other things, but not for the 4948s. I added this as an exclusion yesterday. Today when I checked, all 4948s are archiving now, and are off the out of sync report. Never would have crossed my mind to check there, but that exclusion seems to have done the trick. Maybe someone else can use this if they're seeing the same thing. - chris

Cisco Prime 2.2 Config Archive get Partial-Success

Good morning everyone!
I have a question regarding Cisco Prime Infrastructure 2.2 and Config Archive. Im trying to backup a configuration for an old WS-CBS3020-HPQ blade with IOS version 12.2(58)SE1 and im getting an error under "Fetch vlan" that says :
Couldn't able to collect VLAN on the device. TFTP server not accessible from device.
Im not sure what this means? It gets partial-success, but the error message worries me. Im not able to find anything in the logs or by searching for the error code. Anyone have any idea where to look? The credential is correct, i tripple checked :)

I tried using the "tftp-server flash:" command, but didnt help. Im also seeing this problem with a couple of Cisco 3750x switches.

Config Archive Failure

This image shows that I have Telnet, SSH, TFTP and HTTPS configured for Config Fetch. What am I missing?
Thanks Joseph!
I don't know why, but nearly ALL of my Config Archive VLAN is failing. I am receiving the following:
TELNET: Failed to establish TELNET connection to xxx.xxx.xxx.xxx - Cause: Connection refused. Command failed VLAN Config fetch is not supported using RCP. VLAN Config fetch is not supported using TFTP.
The above switch is using SSH - not Telnet, but it doesn't try???
The other error is:
Command failed Could not detect SSH protocols running on the device VLAN Config fetch is not supported using RCP. VLAN Config fetch is not supported using TFTP.
On this one, it should be using Telnet as that is what is supported on this particular switch.
I have verified the credentials are set up correctly for both of these.
Also, this isn't isolated - it's happening on 293 devices. Only 2 are successful.
Any help would be GREATLY appreciated! I am running LMS 3.2

The following is what I see in the logs:
],ERROR,[Thread-1926],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,1355,VLAN RUNNING Config fetch Failed for csw-a1xc-201-004
[ Fri Oct 08 06:27:18 MDT 2010 ],DEBUG,[Thread-1926],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,1361,Message : Command failedSSH: Failed to establish SSH connection to x.x.x.x -
Cause: Authentication failed on device 3 times.
VLAN Config fetch is not supported using TFTP.
Please ensure that you have the credentials corrected in the DCR under Common Services --> Device and Credentials --> Devices Management --> Select all the devices in question, edit credentials.
1. Ensure the primary enable username and password is correct and populated.
2. Ensure you are using the correct SNMP RO/RW community string and must be populated.
3. Ensure that all firewall rules allow traffic to and from LMS and devices. Check port 69 UDP and high ports number are allowed.
4. If this is a multi-home system with two nic cards, go to RME ---> Administration --> System Preferences --> RME Device Attribute --> Add Natted RME IP Address
Afterwards, rerun the device credential verification to test for telnet, ssh, SNMP RO and RW and ensure it passes. Then do a sync archive and let me know the results.

Partially Collected Config Archive

Hello,
For 3 switches config archive is partially collected,After searching from enough threads i have done the below but still no sucess
i have given enough rights to tftpboot dir for caususer
created a vlan.dat in tftpboot folder
manually copied vlan.dat from switch to the file in vlan.dat
start a job of syn but no sucess.
Any hints experts.
Thanks

Dear's
Waiting for ur replies??
Thanks.

Call manager and rme config archive report

Hi,
I know that rme does not support the call manager for config archive. It is clear.
The RME home page show config archive status for failed devices and there are some devices which are not supported by RME config archive.
I've set this devices to suspended state in RME but config archiv is trying with this devices also.
This is a financial costumer and the local Financial supervisory authority would like to see all devices config is saving successfully.
How can i exclude the call manager and similar devices from config archiv process and status reports?
Regards,

Hi,
I would like to qoute from RME help.
Working With Suspended Devices
Suspended device state cannot participate in any RME application flows but all historical data pertaining to the device will continue to be maintained by RME.
Nevertheless the RME is trying to fetch the config from suspended devices!!!
What is the truth in this thing?
Regards,

Prime Infrastructure 2.1 - Config Archive

In PI2.1, is it possible to send the config archive of my devices to a network drive? TIA

PI will always save the configurations into its database. That database is always on the PI server itself.
You can export the configurations from the database via a manual process - you could probably script it and kick it off via cron if you are handy with that sort of thing.
The export process is explained in a post by Vinod Arya in the Prime Infrastructure Ask the Expert thread.
(Edit - corrected link)

Config Archive for Call Manager

Hello,
It give me the attahced error fo r config archive for call manager.

The supported devices page shows each supported device, and what features are supported:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/device_support/table/lms32sdt.html

Config archive failed for devices no longer on DCR

RME reported 30 devices failed config archive but this devices are already removed from DCR but RME keep reporting this devices. how I can clean up thiese devices from RME?
Thanks

You can contact TAC, and they can give you the procedure to surgically remove these device records from the RME database.

RME Issues: Config Status & Config Archive

Hi All,
1. While trying to generate Device Manageability Status Report, I noticed that the Config Status of all devices is Failed. The reason for the failure on all the device is as follows:
Failed to establish TELNET connection to 10.180.9.172 -Cause: Authentication failed on device 3 times Failed to detect SSH version running on the device.
Can anyone help with the solution to this?
2. Also, the RME Collection Status as shown in the attachment shows that no archive was successfully collected on any of the devices. How can I resolve this issue?
3. How do I generate a report of Configuration Changes performed by users from RME?
Thank you in advance.

This error typically means you have not filled in the correct credentials for the devices in DCR. In order to fetch configs from devices you need to populate the SNMP read-write credentials and/or the telnet/SSH username, password, and enable password.
Once you have configs getting archived, and assuming you're sending syslog messages from your devices to RME, you can run a Change Audit (within RME) report to see the config changes that have been made by your users.

BW Archiving issue - Data not being picked up

Hi,
I am using ADK Archiving to archive a cubes data ( to application server files). The config is working perfectly in DEV however in QA I get "0 data records copied in volumes of 0 KB" even though data is present for the selection criteria.
I do not see any authorization issue or other error in job log... Anyone seen this issue before ? Please advise.
Thanks

Hello,
Are the requests compressed? In 700, the data in the infocube must be compressed or it cannot be archived.
Best Regards,
Vincent

Config archive of Cisco 4404/4402 WLC devices

Hi,
I am currently having an issue backing up WLC devices in CiscoWorks LMS 3.2. i can see that from an inventory perspective they are discovered correctly. I have tested the credentials on the CLI and that works fine, but when doing a archive collection from the ciscoworks application it fails, stating that it is a timeout issue.
I have noticed that when trying to connect via the CLI using SSH example below, it does not just prompt for a password, it prompts for the username again, i am not sure if this is the issue
ssh -l test 10.1.2.3
Any assistance will be much appreciated
Kind Regards
James

Hi
telnet output on port 22:
Trying *.*.*.*
Connected to *.*.*.*
Escape character is '^]'.
SSH-2.0-OpenSSH_4.0
Protocol mismatch.
Connection to *.*.*.* closed by foreign host.
Failed info in job output:
CM0151 PRIMARY RUNNING Config fetch failed for hostname Cause: fig from device: java.net.SocketTimeoutException: Read timed out Action: Check if protocol is supported by device and required device package is installed. Check device credentials. Increase timeout value, if required.
dcmaservice.log output:
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-5],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,triggerConfigFetch,52,#### Start of Sweep Tue Apr 13 10:46:48 BST 201
0 ####
[ Tue Apr 13 10:46:48 BST 2010 ],WARN ,[Thread-6033],com.cisco.nm.rmeng.util.DCRWrapperAPIs,getResultFromQuery,3315,SQLException occurred as connection closed. Re-connecting
to DB...
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,769,Inside RMEDeviceContext's getCmdSvc ....
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,774,Protocol and Platforms passed = SSH , RME_WLC
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,786,Iam inside ssh ....
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,787,Initial time_out : 0
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,792,Computed time_out : 60
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,800,After computing time_out : 60
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshCmdSvc,819,inside getSshCmdSvc with timeout : 60000
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshProtocols,872,Inside getsshprotocols with time out : 60000
[ Tue Apr 13 10:46:54 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshCmdSvc,826,SSH2 is running
[ Tue Apr 13 10:47:00 BST 2010 ],ERROR,[Thread-6033],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,error,19,Warning: Received USERAUTH_SUCCESS in response to 'none' authen
tication request
[ Tue Apr 13 10:47:23 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.xms.xdi.pkgs.SharedDcmaWLC.transport.WLCCliOperator,getCmd2Fetch,342,SNMP initialization completed
[ Tue Apr 13 10:47:23 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.xms.xdi.pkgs.SharedDcmaWLC.transport.WLCCliOperator,getCmd2Fetch,349,Current Running image version:NoSuchIns
tance
[ Tue Apr 13 10:47:23 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.xms.xdi.pkgs.SharedDcmaWLC.transport.WLCCliOperator,getCmd2Fetch,351,Using the latest command as image veris
on is greater than 5.2
[ Tue Apr 13 10:48:25 BST 2010 ],ERROR,[Thread-6033],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,error,19,IOException received during block() of Channel[UInt32[ 0 ]:UInt
32[ 0 ]]
[ Tue Apr 13 10:48:26 BST 2010 ],ERROR,[Thread-6033],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,678,PRIMARY RUNNING Config fetch Failed for
hostname
[ Tue Apr 13 10:48:26 BST 2010 ],INFO ,[Thread-1],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,run,99,#### End of Sweep Tue Apr 13 10:48:26 BST 2010 ####
SNOOP output:
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Syn Seq=1825561549 Len=0 Win=49640 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Ack=669720941 Seq=1825561550 Len=0 Win=50040
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Ack=669720961 Seq=1825561550 Len=0 Win=50040
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Fin Ack=669720961 Seq=1825561550 Len=0 Win=50040
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Syn Seq=2323886065 Len=0 Win=32850 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Ack=669720962 Seq=1825561551 Len=0 Win=50040
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673581283 Seq=2323886066 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673581303 Seq=2323886066 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673581303 Seq=2323886066 Len=15 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673581303 Seq=2323886081 Len=248 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673581943 Seq=2323886329 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673581943 Seq=2323886329 Len=144 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582407 Seq=2323886473 Len=16 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582407 Seq=2323886489 Len=52 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582459 Seq=2323886541 Len=68 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582495 Seq=2323886609 Len=60 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582547 Seq=2323886669 Len=76 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582583 Seq=2323886745 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673582707 Seq=2323886789 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582775 Seq=2323886789 Len=52 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673582879 Seq=2323886841 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582879 Seq=2323886841 Len=52 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582931 Seq=2323886893 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582931 Seq=2323886937 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583039 Seq=2323886981 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583083 Seq=2323887025 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583127 Seq=2323887069 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583171 Seq=2323887113 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583215 Seq=2323887157 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583259 Seq=2323887201 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583303 Seq=2323887245 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583347 Seq=2323887289 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673583407 Seq=2323887333 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583407 Seq=2323887333 Len=60 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583467 Seq=2323887393 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673583535 Seq=2323887437 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583535 Seq=2323887437 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673583595 Seq=2323887481 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583595 Seq=2323887481 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583639 Seq=2323887525 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673583707 Seq=2323887569 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583707 Seq=2323887569 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583775 Seq=2323887613 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583843 Seq=2323887657 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583887 Seq=2323887701 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583931 Seq=2323887745 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583975 Seq=2323887789 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584019 Seq=2323887833 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584063 Seq=2323887877 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584107 Seq=2323887921 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584151 Seq=2323887965 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584219 Seq=2323888009 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584219 Seq=2323888009 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584287 Seq=2323888053 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584287 Seq=2323888053 Len=52 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584339 Seq=2323888105 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584415 Seq=2323888149 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584415 Seq=2323888149 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584483 Seq=2323888193 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584483 Seq=2323888193 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584527 Seq=2323888237 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584587 Seq=2323888281 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584587 Seq=2323888281 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584647 Seq=2323888325 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584707 Seq=2323888369 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584751 Seq=2323888413 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584795 Seq=2323888457 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584839 Seq=2323888501 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584883 Seq=2323888545 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584927 Seq=2323888589 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584971 Seq=2323888633 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585015 Seq=2323888677 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673585075 Seq=2323888721 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE UDP D=161 S=53008 LEN=77
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585075 Seq=2323888721 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673585135 Seq=2323888765 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585135 Seq=2323888765 Len=68 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585203 Seq=2323888833 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673585735 Seq=2323888877 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585735 Seq=2323888877 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673585735 Seq=2323888921 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673587523 Seq=2323888921 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673587523 Seq=2323888921 Len=36 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673587523 Seq=2323888957 Len=128 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673587524 Seq=2323889085 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Fin Ack=673587524 Seq=2323889085 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Syn Seq=3874994962 Len=0 Win=49640 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Ack=754769594 Seq=3874994963 Len=0 Win=50040
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Fin Ack=754769594 Seq=3874994963 Len=0 Win=50040
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Rst Seq=3874994964 Len=0 Win=50040
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Rst Seq=3874994964 Len=0 Win=0
Kind Regards
James

Config-Archive Issue on PI 1.3

Similar Messages

Maybe you are looking for