Tuesday, 5 June 2018

Anyconnect NAM XML profile location

Windows 7:
C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Network Access Manager
Windows XP:
C:\Documents and Settings\All Users\Application Data\Cisco\Cisco AnyConnect Secure Mobility Client\Network Access Manager

Tuesday, 15 May 2018

Cisco IP Phones disconnect causes

Here is a List of the reason codes for LastOutOfServiceInformation

ReasonForOutOfService=10    --  TCPtimedOut - The TCP connection to the Cisco Unified Communication Manager experienced a timeout error
ReasonForOutOfService=12    --  TCPucmResetConnection - The Cisco Unified Communication Manager reset the TCP connection
ReasonForOutOfService=13    --  TCPucmAbortedConnection - The Cisco Unified Communication Manager aborted the TCP connection
ReasonForOutOfService=14    --  TCPucmClosedConnection - The Cisco Unified Communication Manager closed the TCP connection
ReasonForOutOfService=15    --  SCCPKeepAliveFailure - The device closed the connection due to a SCCP KeepAlive failure
ReasonForOutOfService=16    --  TCPdeviceLostIPAddress - The connection closed due to the IP address being lost.  This may be due to the DHCP Lease expiring or the detection of IP address duplication. 
                                                           Check that the DHCP Server is online and that no duplication has been reported by the DHCP Server
ReasonForOutOfService=17    --  TCPDeviceRegsistrationTimedOut - The device closed the TCP connection due to a registration timeout
ReasonForOutOfService=18    --  TCPclosedConnectHighPriorityUcm - The device closed the TCP connection in order to reconnect to a higher priority Cisco Unified CM
ReasonForOutOfService=20    --  TCPclosedUserInitiatedReset - The device closed the TCP connection due to a user initiated reset
ReasonForOutOfService=22   --  TCPclosedUcmInitiatedReset - The device closed the TCP connection due to a reset command from the Cisco Unified CM
ReasonForOutOfService=23    --  TCPclosedUcmInitiatedRestart - The device closed the TCP connection due to a restart command from the Cisco Unified CM
ReasonForOutOfService=24    --  TCPClosedRegistrationReject - The device closed the TCP connection due to receiving a registration rejection from the Cisco Unified CM
ReasonForOutOfService=25    --  RegistrationSuccessful - The device has initialized and is unaware of any previous connection to the Cisco Unified CM
ReasonForOutOfService=26   --  TCPclosedVlanChange - The device closed the TCP connection due to reconfiguration of IP on a new Voice VLAN
ReasonForOutOfService=27   --  TCPclosedPowerSavePlus - The device closed the TCP connection in order to enter Power Save Plus mode
ReasonForOutOfService=100    --  ConfigVersionMismatch - The device detected a version stamp mismatch during registration Cisco Unified CM
ReasonForOutOfService=104   --  TCPclosedApplyConfig - The device closed the TCP connection to restart triggered internally by the device to apply the configuration changes
ReasonForOutOfService=105    --  TCPclosedDeviceRestart - The device closed the TCP connection due to a restart triggered internally by the device because device failed to download the configuration or dial plan file
ReasonForOutOfService=106    --  TCPsecureConnectionFailed - The device failed to setup a secure TCP connection with Cisco Unified CM
ReasonForOutOfService=107    --  TCPclosedDeviceReset - The device closed the TCP connection to set the inactive partition as active partition, then reset, and come up from the new active partition
ReasonForOutOfService=108    --  VpnConnectionLost - The device could not register to Unified CM because VPN connectivity was lost
ReasonForOutOfService=200   --  ClientApplicationClosed - The device was unregistered because the client application was closed
ReasonForOutOfService=201   --  OsInStandbyMode - The device was unregistered because the OS was put in standby mode
ReasonForOutOfService=202   --  OsInHibernateMode - The device was unregistered because the OS was put in hibernate mode
ReasonForOutOfService=203   --  OsInShutdownMode - The device was unregistered because the OS was shut down
ReasonForOutOfService=204   --  ClientApplicationAbort - The device was unregistered because the client application crashed
ReasonForOutOfService=205   --  DeviceUnregNoCleanupTime - The device was unregistered in the previous session because the system did not allow sufficient time for cleanup
ReasonForOutOfService=206   --  DeviceUnregOnSwitchingToDeskphone - The device was unregistered because the client requested to switch from softphone to deskphone control
ReasonForOutOfService=207   --  DeviceUnregOnSwitchingToSoftphone - The device is being registered because the client requested to switch from deskphone control to softphone
ReasonForOutOfService=208   --  DeviceUnregOnNetworkChanged - The device is being unregistered because the client detected a change of network
ReasonForOutOfService=209   --  DeviceUnregExceededRegCount - The device is being unregistered because the device has exceeded the maximum number of concurrent registrations
ReasonForOutOfService=210   --  DeviceUnregExceededLoginCount - The device is being unregistered because the client has exceeded the maximum number of concurrent logons

Tuesday, 27 March 2018

Cisco ISE CoA Posture 5417 & 11103 errors

I was getting the following errors with client Posture and CoA.

In the switch I was missing the server-key from radius author

aaa server radius dynamic-author
client 1.1.1.1 server-key secretkey
auth-type all

Thursday, 15 March 2018

SX20 not registering with CUCM

I had an SX20 not registering with CUCM, the error stated "reason=Failed to decrypt/verify signature of .."

The trick was to delete the security certificates of CUCM from SX20.

Go to Configuration -> Security -> CUCM and select "Delete CTL/ITL"

It would register in the next minutes, no need to restart.

Friday, 9 March 2018

Fortinet SSL VPN Windows 10

Recently I had to connect to a remote VPN session using Fortinet SSL VPN.
I installed the simple SSL VPN via Microsoft store on Windows 10 and I run into an issue because the firewall was using an untrusted certificate.
There are no relative option to change in the settings of the client, so searching the Internet I found the following solution that worked:
When you declare your server name use the following URL,

https://<vpn.server.addresss>:443/realmname?ignore-certificate-errors=1


relative Fortinet forum thread:
https://forum.fortinet.com/tm.aspx?m=118768&mpage=3