ISE Admin Access with AD Credentials fails after upgrade 1.2.1 to 1.3.0

Hello,
After upgrading ISE VM from 1.2.1 to 1.3.0.876, I can't connect on ISE with AD Credentials (Invalid Username or Password). It worked find before upgrading to 1.3.
On another ISE VM in 1.3.0.876 version (w/o upgrade) with this kind of configuration, it's OK.
I have double check the Post-upgrade tasks (particularly rejoining Active Directory). Everything worked find after this upgrade except the admin access with AD credentials.
I don't use user certificate-based authentication for admin access. So I didn't execute application start ise safe CLI.
My 802.1x wireless users passed authentication with AD credentials. So the ISE had correctly join my AD.
I didn't find anything related to this admin access with AD credentials failure in the output of show logging application ise and show logging.
I don't find anything related to this in bug search on Cisco tools.
I tried to :
- update the SID of my Admin AD Group, the result is still the same.
- delete my admin access with AD credentials configuration then make this configuration again, but still the same error.
Any ideas on this ? Could I find elements in another log ?
Regards.

Dear Markus,
After logging as user "prdadm"
su - prdadm
bssltests% bash-3.00$ ls -a
.                            .dbenv_bssltests.sh-old      .sapenv_bssltests.sh         startdb.log
..                           .dbenv_bssltests.sh-old10    .sapenv_bssltests.sh-new     startsap_.log
.bash_history                .dbsrc_bssltests.csh         .sapenv_bssltests.sh-old10   startsap_DVEBMGS00.log
.cshrc                       .dbsrc_bssltests.sh          .sapsrc_bssltests.csh        startsap_DVEBMGS01.log
.dbenv_bssltests.csh         .login                       .sapsrc_bssltests.sh         stopdb.log
.dbenv_bssltests.csh-new     .profile                     dev_sapstart                 stopsap_.log
.dbenv_bssltests.csh-old     .sapenv_bssltests.csh        local.cshrc                  stopsap_DVEBMGS00.log
.dbenv_bssltests.csh-old10   .sapenv_bssltests.csh-new    local.login                  stopsap_DVEBMGS01.log
.dbenv_bssltests.sh          .sapenv_bssltests.csh-old    local.profile                trans.log
.dbenv_bssltests.sh-new      .sapenv_bssltests.csh-old10  sqlnet.log
bash-3.00$
bash-3.00$
I have changed envt settings in .dbenv_bssltests.csh & .dbenv_bssltests.sh
.sapenv_bssltests.sh & .sapenv_bssltests.csh  [4 files]
Regards,
Ankita

Similar Messages

  • ISE Admin Access Authentication to RADIUS Token Server

    Hi all!
    I want to use an External  RADIUS Token Server for ISE Admin Access Authentication and Authorization.
    Authentication works, but how do I map the users  to Admin Groups? Is there a way  to map a returned RADIUS Attribute  (IETF "Class" or Cisco-AVPair "CiscoSecure-Group-Id") to an Admin Group?
    Thanks in advance,
    Michael Langerreiter

    ISE 1.3 does have an bug: Authentication failed due to zero RBAC Groups.
    Cisco Bug: CSCur76447 - External Admin access fails with shadow user & Radius token
    Last Modified
    Nov 25, 2014
    Product
    Cisco Identity Services Engine (ISE) 3300 Series Appliances
    Known Affected Releases
    1.3(0.876)
    Description (partial)
    Symptom:
    ISE 1.3 RBAC fails with shadow user & Radius token
    Operations > Reports > Deployment Status > Administrator Logins report shows
    Authentication failed due to zero RBAC Groups
    Conditions:
    RBAC with shadow user & Radius token
    View Bug Details in Bug Search Tool
    Why Is Login Required?
    Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
    Bug Details Include
    Full Description (including symptoms, conditions and workarounds)
    Status
    Severity
    Known Fixed Releases
    Related Community Discussions
    Number of Related Support Cases
    Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.

  • Unit test fails after upgrading to Kodo 4.0.0 from 4.0.0-EA4

    I have a group of 6 unit tests failing after upgrading to the new Kodo
    4.0.0 (with BEA) from Kodo-4.0.0-EA4 (with Solarmetric). I'm getting
    exceptions like the one at the bottom of this email. It seems to be an
    interaction with the PostgreSQL driver, though I can't be sure. I
    haven't changed my JDO configuration or the related classes in months
    since I've been focusing on using the objects that have already been
    defined. The .jdo, .jdoquery, and .java code are below the exception,
    just in case there's something wrong in there. Does anyone have advice
    as to how I might debug this?
    Thanks,
    Mark
    Testsuite: edu.ucsc.whisper.test.integration.UserManagerQueryIntegrationTest
    Tests run: 15, Failures: 0, Errors: 6, Time elapsed: 23.308 sec
    Testcase:
    testGetAllUsersWithFirstName(edu.ucsc.whisper.test.integration.UserManagerQueryIntegrationTest):
    Caused an ERROR
    The column index is out of range: 2, number of columns: 1.
    <2|false|4.0.0> kodo.jdo.DataStoreException: The column index is out of
    range: 2, number of columns: 1.
    at
    kodo.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4092)
    at kodo.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:82)
    at kodo.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:66)
    at kodo.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:46)
    at
    kodo.jdbc.kernel.SelectResultObjectProvider.handleCheckedException(SelectResultObjectProvider.java:176)
    at
    kodo.kernel.QueryImpl$PackingResultObjectProvider.handleCheckedException(QueryImpl.java:2460)
    at
    com.solarmetric.rop.EagerResultList.<init>(EagerResultList.java:32)
    at kodo.kernel.QueryImpl.toResult(QueryImpl.java:1445)
    at kodo.kernel.QueryImpl.execute(QueryImpl.java:1136)
    at kodo.kernel.QueryImpl.execute(QueryImpl.java:901)
    at kodo.kernel.QueryImpl.execute(QueryImpl.java:865)
    at kodo.kernel.DelegatingQuery.execute(DelegatingQuery.java:787)
    at kodo.jdo.QueryImpl.executeWithArray(QueryImpl.java:210)
    at kodo.jdo.QueryImpl.execute(QueryImpl.java:137)
    at
    edu.ucsc.whisper.core.dao.JdoUserDao.findAllUsersWithFirstName(JdoUserDao.java:232)
    at
    edu.ucsc.whisper.core.manager.DefaultUserManager.getAllUsersWithFirstName(DefaultUserManager.java:252)
    NestedThrowablesStackTrace:
    org.postgresql.util.PSQLException: The column index is out of range: 2,
    number of columns: 1.
    at
    org.postgresql.core.v3.SimpleParameterList.bind(SimpleParameterList.java:57)
    at
    org.postgresql.core.v3.SimpleParameterList.setLiteralParameter(SimpleParameterList.java:101)
    at
    org.postgresql.jdbc2.AbstractJdbc2Statement.bindLiteral(AbstractJdbc2Statement.java:2085)
    at
    org.postgresql.jdbc2.AbstractJdbc2Statement.setInt(AbstractJdbc2Statement.java:1133)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setInt(DelegatingPreparedStatement.java:390)
    at
    com.solarmetric.jdbc.PoolConnection$PoolPreparedStatement.setInt(PoolConnection.java:440)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setInt(DelegatingPreparedStatement.java:390)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setInt(DelegatingPreparedStatement.java:390)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setInt(DelegatingPreparedStatement.java:390)
    at
    com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.setInt(LoggingConnectionDecorator.java:1
    257)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setInt(DelegatingPreparedStatement.java:390)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setInt(DelegatingPreparedStatement.java:390)
    at kodo.jdbc.sql.DBDictionary.setInt(DBDictionary.java:980)
    at kodo.jdbc.sql.DBDictionary.setUnknown(DBDictionary.java:1299)
    at kodo.jdbc.sql.SQLBuffer.setParameters(SQLBuffer.java:638)
    at kodo.jdbc.sql.SQLBuffer.prepareStatement(SQLBuffer.java:539)
    at kodo.jdbc.sql.SQLBuffer.prepareStatement(SQLBuffer.java:512)
    at kodo.jdbc.sql.SelectImpl.execute(SelectImpl.java:332)
    at kodo.jdbc.sql.SelectImpl.execute(SelectImpl.java:301)
    at kodo.jdbc.sql.Union$UnionSelect.execute(Union.java:642)
    at kodo.jdbc.sql.Union.execute(Union.java:326)
    at kodo.jdbc.sql.Union.execute(Union.java:313)
    at
    kodo.jdbc.kernel.SelectResultObjectProvider.open(SelectResultObjectProvider.java:98)
    at
    kodo.kernel.QueryImpl$PackingResultObjectProvider.open(QueryImpl.java:2405)
    at
    com.solarmetric.rop.EagerResultList.<init>(EagerResultList.java:22)
    at kodo.kernel.QueryImpl.toResult(QueryImpl.java:1445)
    at kodo.kernel.QueryImpl.execute(QueryImpl.java:1136)
    at kodo.kernel.QueryImpl.execute(QueryImpl.java:901)
    at kodo.kernel.QueryImpl.execute(QueryImpl.java:865)
    at kodo.kernel.DelegatingQuery.execute(DelegatingQuery.java:787)
    at kodo.jdo.QueryImpl.executeWithArray(QueryImpl.java:210)
    at kodo.jdo.QueryImpl.execute(QueryImpl.java:137)
    at
    edu.ucsc.whisper.core.dao.JdoUserDao.findAllUsersWithFirstName(JdoUserDao.java:232)
    --- DefaultUser.java -------------------------------------------------
    public class DefaultUser
    implements User
    /** The account username. */
    private String username;
    /** The account password. */
    private String password;
    /** A flag indicating whether or not the account is enabled. */
    private boolean enabled;
    /** The authorities granted to this account. */
    private Set<Authority> authorities;
    /** Information about the user, including their name and text that
    describes them. */
    private UserInfo userInfo;
    /** The set of organizations where this user works. */
    private Set<Organization> organizations;
    --- DefaultUser.jdo --------------------------------------------------
    <?xml version="1.0"?>
    <!DOCTYPE jdo PUBLIC
    "-//Sun Microsystems, Inc.//DTD Java Data Objects Metadata 2.0//EN"
    "http://java.sun.com/dtd/jdo_2_0.dtd">
    <jdo>
    <package name="edu.ucsc.whisper.core">
    <sequence name="user_id_seq"
    factory-class="native(Sequence=user_id_seq)"/>
    <class name="DefaultUser" detachable="true"
    table="whisper_user" identity-type="datastore">
    <datastore-identity sequence="user_id_seq" column="userId"/>
    <field name="username">
    <column name="username" length="80" jdbc-type="VARCHAR" />
    </field>
    <field name="password">
    <column name="password" length="40" jdbc-type="CHAR" />
    </field>
    <field name="enabled">
    <column name="enabled" />
    </field>
    <field name="userInfo" persistence-modifier="persistent"
    default-fetch-group="true" dependent="true">
    <extension vendor-name="jpox"
    key="implementation-classes"
    value="edu.ucsc.whisper.core.DefaultUserInfo" />
    <extension vendor-name="kodo"
    key="type"
    value="edu.ucsc.whisper.core.DefaultUserInfo" />
    </field>
    <field name="authorities" persistence-modifier="persistent"
    table="user_authorities"
    default-fetch-group="true">
    <collection
    element-type="edu.ucsc.whisper.core.DefaultAuthority" />
    <join column="userId" delete-action="cascade"/>
    <element column="authorityId" delete-action="cascade"/>
    </field>
    <field name="organizations" persistence-modifier="persistent"
    table="user_organizations" mapped-by="user"
    default-fetch-group="true" dependent="true">
    <collection
    element-type="edu.ucsc.whisper.core.DefaultOrganization"
    dependent-element="true"/>
    <join column="userId"/>
    <!--<element column="organizationId"/>-->
    </field>
    </class>
    </package>
    </jdo>
    --- DefaultUser.jdoquery ---------------------------------------------
    <?xml version="1.0"?>
    <!DOCTYPE jdo PUBLIC
    "-//Sun Microsystems, Inc.//DTD Java Data Objects Metadata 2.0//EN"
    "http://java.sun.com/dtd/jdo_2_0.dtd">
    <jdo>
    <package name="edu.ucsc.whisper.core">
    <class name="DefaultUser">
    <query name="UserByUsername"
    language="javax.jdo.query.JDOQL"><![CDATA[
    SELECT UNIQUE FROM edu.ucsc.whisper.core.DefaultUser
    WHERE username==searchName
    PARAMETERS java.lang.String searchName
    ]]></query>
    <query name="DisabledUsers"
    language="javax.jdo.query.JDOQL"><![CDATA[
    SELECT FROM edu.ucsc.whisper.core.DefaultUser WHERE
    enabled==false
    ]]></query>
    <query name="EnabledUsers"
    language="javax.jdo.query.JDOQL"><![CDATA[
    SELECT FROM edu.ucsc.whisper.core.DefaultUser WHERE
    enabled==true
    ]]></query>
    <query name="CountUsers"
    language="javax.jdo.query.JDOQL"><![CDATA[
    SELECT count( this ) FROM edu.ucsc.whisper.core.DefaultUser
    ]]></query>
    </class>
    </package>
    </jdo>

    I'm sorry, I have no idea. I suggest sending a test case that
    reproduces the problem to support.

  • Anybody know why superdrives fail after upgrading os

    anybody know why superdrives fail after upgrading os

    Upgrading the OS often also triggers issues with PRAM.  If the PRAM battery is over 4 years old, then the Superdrive can fail.    If it is under 4 years old, zapping it can fix some issues like these.

  • Problems with your HP printer after upgrading to Windows 8.1

    If you are experiencing problems with your HP printer after upgrading to Windows 8.1 please click on the below link and install the HP Print and Scan Doctor and run the utility to fix the issue.
    www.hp.com/go/tools.
    I was an HP employee
    If I have helped you solve your issue please mark it as solved
    **Say Thanks By Clicking on the Kudos Star**

    Hi.....my laserjet 1536dnf mfp was working perfectly with win 8 pro....then I installed win 8.1 pro and now the computer ,which is part of a network,can not communicate with the scanner of the printer--it prints just fine. On another computer (running win 7 ) on the same network, the scanner and all other printer functions  work just fine.
          I have tried installing the latest drivers from HP......scanner still not "communicating" with computer.....also temporarily disabled firewall.....please help...all the best -David G (gossat)

  • Impossible Upload files with Filezilla FTP Client after upgrade win8 to win8.1

    Hi
    Things were working fine with win 8 but, after Upgrade to win 8.1 is not possible upload files with Filezilla  FTP Client.
    is there anyone facing same problem?
    thanks in advance for any answer to help me solve this issue 
    Regards 
    TC

    Hi,
    Please Change your transfer settings in site manager from either default or passive to active it to see what's going on.
    Also, check IE compatibility mode.
    In addition, I suggest you install all latest updates for Windows since these updates will improve and fix some known issues.
    Kate Li
    TechNet Community Support

  • Strange problem with my ipod 2g after upgrade to os 4.2

    Strange problem with my ipod 2g after upgrade to os 4.2
    the problem with volume some times when i switch on the ipod i hear the sound
    alarm rings it's work too i can hear it .. but the problem i cant hear anything else as yourtube or music i cant hear buttons sound when i typing
    i hope i get help

    I would try in order:
    - Reset the iPod:
    Reset iPod touch:  Press and hold the On/Off Sleep/Wake button and the Home
    button at the same time for at least ten seconds, until the Apple logo appears.
    - Restore the iPod from backu via iTunes.
    - Restore the iPod to factory defaults/new iPod.

  • Tpnotify with TPACK flag hangs after upgrading to Tuxedo 12c RP020

    Hi,
    We are experiencing issues with tptonify with TPACK flag set after upgrading to Tuxedo 12c. Looks like tpnotify is not returned or reporting errors. Is there anything to do with "009. Bug16506218 - TPNOTIFY WITH TPACK FLAG THROW OUT EXCEPTION"? Is there any documentation about the new flag TPACK_INTL?
    Thanks

    Hello,
    If all you have done is upgrade to Tuxedo12 the behavior should be the same. The TPACK flag definition is:
    "The request is sent and the caller blocks until an acknowledgement message is received from the target client"
    Is there any additional change(e.g. in your client) you have made?
    What Tuxedo version are you upgrading from?
    The bug 16506218 fix was for a jolt client exception and a JSH failure.
    Do you see an error or is the process which executes tpnotify() just hanging/blocking waiting for the ack message?
    The flag that you mention is actually an undocumented customer requested enhancement that went into Tuxedo 10.3.
    Are you using it? Using it changes the tpnotify() behavior dependent upon the client status.
    Regards,
    Bob Finan

  • I dont have any Add-ons with my FireFox. After upgrade to the latest version 26.0 I'm keep getting Script error "chrome://global/content/binding/popup.xml:580"

    Quite frequently I'm keep getting the error like "Script is not responding....I dont have any Add-ons with my FireFox. After upgrade to the latest version 26.0 I'm keep getting Script error "chrome://global/content/binding/popup.xml:580" Stop or Continue Script.
    Currently I don't have any Add-Ons installed in my FireFox, so I can suspect any Add-ons.
    I'm facing this issue only after the upgrade to 26.0 recently.

    Ifound this article:
    https://support.mozilla.org/pt-BR/questions/746499
    in this article the problem is similar not the same, but sdmitch16 had a intersting idea disable the chrome options
    and i search more in the internet i also found this:
    https://support.mozilla.org/pt-BR/questions/760704

  • HI! I am using iTunes with Windows 7 64bit.after upgrading itunes  to 10.5.2.11 it opens only once. If i close it, then it will not open again.the only way to open itunes is by disabling the APSDaemon.exe from the task manager.please help!

    HI! I am using iTunes with Windows 7 64bit.after upgrading itunes  to 10.5.2.11 it opens only once. If i close it, then it will not open again.the only way to open itunes is by disabling the APSDaemon.exe from the task manager.please help!

    Refer this article to reset Winsock to it's default.  Your PCTools may have inserted LSP.
    http://support.apple.com/kb/TS4123?viewlocale=en_US
    After reset and restarting windows, you may get a prompt to remap LSP, click no.

  • ISE admin , PSN and monitoring node fail-over and fall back scenario

    Hi Experts,
    I have question about ISE failover .
    I have two ISE appliaces in two different location . I am trying to understand the fail-over scenario and fall-back scenario
    I have gone through document as well however still not clear.
    my Primary ISE server would have primary admin role , primary monitoring node and secondary ISE would have secondary admin and secondary monitoring role .
    In case of primary ISE appliance failure , I will have to login into secondary ISE node and make admin role as primary but how about if primary ISE comes back ? what would be scenario ?
    during the primary failure will there any impact with users for authentication ? as far as PSN is available from secondary , it should work ...right ?
    and what is the actual method to promote the secondary ISE admin node to primary ? do i have to even manually make monitoring node role changes ?
    will i have to reboot the secondary ISE after promoting admin role to primary  ?

    We have the same set up across an OTV link and have tested this scenario out multiple times. You don't have to do anything if communication is broken between the prim and secondary nodes. The secondary will automatically start authenticating devices that it is in contact with. If you promote the secondary to primary after the link is broke it will assume the primary role when the link is restored and force the former primary nodes to secondary.

  • ISE admin server with 16 character hostname

    Our ISE admin servers were inadvertently built with 16 character hostnames. Active directory has a 15 character limit for hostnames. This causes the 16th character to be truncated. The secondary admin server fails to connect to AD because the hostname no longer looks unique. Is there a work around for this other than rebuilding the ISE servers?

    Hi Jeff,
    you need not rebuild your entire ISE nodes. You have to follow the below steps.
    Changing the Hostname or IP Address of a Standalone Cisco ISE Node
    You can change the hostname, IP address, or domain name of standalone Cisco ISE nodes. You cannot use “localhost” as the hostname for a node.
    Before You Begin
    If the Cisco ISE node is part of a distributed deployment, you must remove it from the deployment and ensure that it is a standalone node.
    Step 1 Change the hostname or IP address of the Cisco ISE node using the hostname , ip address, or ip domain-name command from the Cisco ISE CLI.
    Step 2 Restart the Cisco ISE application configuration using the application stop ise command from the Cisco ISE CLI to restart all the services.
    Step 3 Register the Cisco ISE node to the primary Administration node if it part of a distributed deployment.
    Note If you are using the hostname while registering the Cisco ISE node, the fully qualified domain name (FQDN) of the standalone node that you are going to register, for example, abc.xyz.com must be DNS-resolvable from the primary Administration node. Otherwise, node registration fails. You must enter the IP addresses and FQDNs of the Cisco ISE nodes that are part of your distributed deployment in the DNS server.
    After you register the Cisco ISE node as a secondary node, the primary Administration node replicates the change in the IP address, hostname, or domain name to the other Cisco ISE nodes in your deployment.
    Make sure that you also update the DNS record with new hostname and replace the certificate unless you are using wildcard cert.

  • Network Manager fails to connect with Huawei E3276 modem after upgrade

    Hi,
    I have Huawei E3276 (lsusb: Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard).
    I wasn't updating the system for a long time (since KDE 4.14.3), but after upgrade Network Manager can't connect anymore.
    I also tried on the fresh install on different machine (KDE + Plasma 5.3), but I get the same error...
    Error: failed to connect modem: Only IPv4 is supported by this modem.
    I realize that this problem has nothing to do with KDE, but with new version of NM + MM, systemd, dhcpcd or dhclient?
    Why now Network Manager don't use ppp like before upgrade (different connection type "cdc-wdm0")?
    I would be grateful for any advice.
    After upgrade (KDE 4.14.3 -> 15.04 apps/5.2 plasma):
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now CONNECTING
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> need-auth (reason 'none') [40 60 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect started...
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (5/8): Register
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (6/8): Bearer
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (7/8): Connect
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0) failed to connect modem: Only IPv4 is supported by this modem
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> failed (reason '(null)') [40 120 1]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now DISCONNECTED
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> Disabling autoconnect for connection 'Orange'.
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0): Activation: failed for connection 'Orange'
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): deactivating device (reason 'none') [0]
    Before upgrade (KDE 4.14)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) starting connection 'Orange'
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> NetworkManager state is now CONNECTING
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect started...
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (4/8): Wait to get fully enabled
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (5/8): Register
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (6/8): Bearer
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (7/8): Connect
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <warn> (ttyUSB0): port attributes not fully set
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (8/8): All done
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> (ttyUSB0): failed to look up interface index
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> using modem-specified IP timeout: 20 seconds
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> starting PPP connection
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> pppd started with pid 780
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    mar 23 19:31:33 AsusN56VZ pppd[780]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
    mar 23 19:31:33 AsusN56VZ kernel: PPP generic driver version 2.4.2
    mar 23 19:31:33 AsusN56VZ pppd[780]: pppd 2.4.6 started by root, uid 0
    mar 23 19:31:33 AsusN56VZ pppd[780]: Using interface ppp0
    mar 23 19:31:33 AsusN56VZ pppd[780]: Connect: ppp0 <--> /dev/ttyUSB0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Using interface ppp0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Connect: ppp0 <--> /dev/ttyUSB0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
    mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded: Welcome!!
    mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded: Welcome!!
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded
    mar 23 19:31:33 AsusN56VZ kernel: PPP BSD Compression module registered
    mar 23 19:31:33 AsusN56VZ kernel: PPP Deflate Compression module registered
    mar 23 19:31:35 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (umts -> hspa-plus)
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> PPP manager(IP Config Get) reply received.
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
    Linux Mint 17.1 KDE (works the same like Arch before update)
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) starting connection 'Orange Standard access - with image compression'
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTING
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect started...
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect state (3/8): Enable
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
    May 7 20:06:33 mint17-vm ModemManager[781]: <warn> (ttyUSB1): port attributes not fully set
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    May 7 20:06:34 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (80)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (4/8): Wait to get fully enabled
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (5/8): Register
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (6/8): Bearer
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> WWAN now enabled by management service
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (7/8): Connect
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (77)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (unknown -> lte)
    May 7 20:06:35 mint17-vm ModemManager[781]: <warn> (ttyUSB0): port attributes not fully set
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (8/8): All done
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> (ttyUSB0): failed to look up interface index
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> using modem-specified IP timeout: 20 seconds
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> starting PPP connection
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> pppd started with pid 2468
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    May 7 20:06:35 mint17-vm pppd[2468]: Plugin /usr/lib/i386-linux-gnu/pppd/2.4.5/nm-pppd-plugin.so loaded.
    May 7 20:06:35 mint17-vm pppd[2468]: pppd 2.4.5 started by root, uid 0
    May 7 20:06:35 mint17-vm pppd[2468]: Using interface ppp0
    May 7 20:06:35 mint17-vm pppd[2468]: Connect: ppp0 <--> /dev/ttyUSB0
    May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
    May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
    May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded: Welcome!!
    May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded
    May 7 20:06:35 mint17-vm kernel: [ 82.363825] PPP BSD Compression module registered
    May 7 20:06:35 mint17-vm kernel: [ 82.368188] PPP Deflate Compression module registered
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> PPP manager(IP Config Get) reply received.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) complete.
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: secondaries -> activated (reason 'none') [90 100 0]
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTED_GLOBAL
    Last edited by Shocker (2015-05-07 19:18:43)

    This week, after update, modem works again.
    However, there's a new bug in the kernel, which was not there before:
    kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    but the modem works and connects to the network.
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> Auto-activating connection 'Orange'.
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTING
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect started...
    may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect state (1/8): Unlock check
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (2/8): Wait to get fully initialized
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (locked -> initializing)
    may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:32:47 AsusN56VZ ModemManager[338]: Invalid mobile equipment error code: 50
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (initializing -> disabled)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (3/8): Enable
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <warn> (ttyUSB1): port attributes not fully set
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'locked' --> 'disabled' (reason: unknown)
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'disabled' --> 'enabling' (reason: user preference)
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <warn> (cdc-wdm0) failed to enable modem: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.InProgress: Cannot enable modem: already being enabled
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    may 24 09:32:48 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect started...
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (8/8): All done
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) scheduled...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) starting...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: prepare -> config (reason 'none') [40 50 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) successful.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) complete.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) started...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: config -> ip-config (reason 'none') [50 70 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Activation (wwp0s20u2i2) Beginning DHCPv4 transaction (timeout in 15 seconds)
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> dhclient started with pid 3624
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): IPv6 configuration disabled
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) complete.
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPDISCOVER on wwp0s20u2i2 to 255.255.255.255 port 67 interval 7
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPREQUEST on wwp0s20u2i2 to 255.255.255.255 port 67
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPOFFER from 10.X.X.X
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPACK from 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> address 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> plen 30 (255.255.255.252)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> gateway 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> server identifier 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> lease time 518400
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (wwp0s20u2i2): DHCPv4 state changed unknown -> bound
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) started...
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Joining mDNS multicast group on interface wwp0s20u2i2.IPv4 with address 10.X.X.X.
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: New relevant interface wwp0s20u2i2.IPv4 for mDNS.
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Registering new address record for 10.X.X.X on wwp0s20u2i2.IPv4.
    may 24 09:33:08 AsusN56VZ dhclient[3624]: bound to 10.X.X.X -- renewal in 252436 seconds.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) complete.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_LOCAL
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_GLOBAL
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Policy set 'Orange' (wwp0s20u2i2) as default for IPv4 routing and DNS.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Writing DNS information to /usr/bin/resolvconf
    may 24 09:33:09 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: successful, device activated.

  • ISE Admin Access Authentication against multiple AD/LDAP Identity Sources

    Hi all!
    We would like to grant admin cccess to our ISE deplyoment to users stored in multiple Active Directories. Since there is no trust relationship between these ADs, we created an LDAP Identity Source for each AD and also an Identity Source Sequence but in the UI we can only select one Identity Source.
    Any ideas how to solve this problem?
    Thanks in advance!
    Kind regards,
    Michael Langerreiter

    I did check in my lab and yes for admin access we can't select identity store sequence in authentication. We can only pick one external database. However, on the login page you may select the appropriate database before you enter the username and password.
    Jatin Katyal
    - Do rate helpful posts -

  • Identity Service Engine (ISE) Admin Access

    Is it possible to authenticate the ISE administrator via an external Radius Server? The option I find is that it will not work, 
    The manual reads: 
    In Cisco ISE, you can authenticate administrators via an external identity store such as Active Directory, LDAP, or RSA SecureID. There are two models you can use to provide authentication via an external identity store:
    Is this the case ?

    Sure you can!
    Make sure you have the RADIUS server added to the ISE (Administration > Identity Management > External Identity Sources  Select RADIUS Token from the left menu).
    Then head over to Administration > System > Admin Access.  Change the * Identity Source to your RADIUS Server and click Save
    Log out and you will see an new entry on the log in screen.  Click the dropdown for Identity Source and choose your RADIUS Server.  If this connection gets dropped for any reason, you can always log in using the internal identity source as a fallback.
    Please Rate Helpful posts and mark this question as answered if, in fact, this does answer your question.  Otherwise, feel free to post follow-up questions.
    Charles Moreton

Maybe you are looking for

  • Replacement option from Iphone 4s to 5s

    I have purchase a Apple iphone 4s from Landon, Do i have an option to replace this iphone with Apple Iphone 5s

  • Line by line intensity image generation

    I am in need of creating a 256x256 pixel intensity image which updates continuously line-by-line.  I tried using the "Create IntGraph Color Table.vi" example however the intensity image is displayed after the entire chart is processed.  How would I g

  • Shared varaible communication

    I am trying to connect to my compact field point using a shared varaible. I have done this successfully on my office computer, moved my compact field point into the test area and am trying to run the same softeware on my lab computer. I get the error

  • How do I set another admin user account

    Im having serious problems deleting a Nieman survey app from my admin acc n seems easiest way would be to just start another account as the guest acc otill works but just on safari?????

  • Diffferent contact info on iPhone and MBP

    I wish to start using iCloud with my iPhone and my MBP.  The problem is that I have different contact info on my iPhone than on my MBP.  The MBP contact info is the accurate info.  So I don't want the iPhone contact to sync with the MBP contacts but