Default interface reset issue after ISE configuration

Hi,
We're testing VOIP phones with ISE. ISE detects the phones by MAB and places them in our Voice VLAN with a DACL for security, this works fine.
After the tests I configured the port to a non ISE port (default interface) and added the normal working configuration.
Result is that the IP phone doesn't get an IP address. If I plug the same phone on a different interface on the same switch it's working again.
I have no idea why this strange behavior occurs, maybe someone can help me out.
Thanks, Michael

A reboot solves the problem temporary, so it looks like the running switch holds back some old configuration until a reboot

Similar Messages

[Solved] Default interface routing issues

I have two network interfaces connected to my newly installed ArchLinux server, one LAN and one WAN connection. The trouble is that all traffic that is trying to connect to the wan interface gets no response, while the LAN connection work without any issue.
I am using udev to change my interfaces to lan0 and wan0, and i use netcfg to load the diffrent profiles.
Lan0 uses a static local ip 192.168.0.118 with 192.168.0.2 as gateway
Wan0 uses dhcp with dynamic ip from my ISP.
When i manually bring down my lan0 interface all my traffic goes through wan0 correctly, and it even responds to external calls.
So i belive the issue lies somewhere in the local routing?
I am trying to post all config files needed directly.
/etc/rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# LANG in /etc/locale.conf takes precedence
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="sv_SE.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Stockholm"
KEYMAP="sv-latin1"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
MODULES=()
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="yes"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="weed-devil"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
#interface=eth0
#address=
#netmask=
#broadcast=
#gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This requires the netcfg package
NETWORKS=(sluggy local)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
# If you are sure nothing else touches your hardware clock (such as ntpd or
# a dual-boot), you might want to enable 'hwclock'. Note that this will only
# make a difference if the hwclock program has been calibrated correctly.
# If you use a network filesystem you should enable 'netfs'.
DAEMONS=(syslog-ng !ufw !network net-profiles @alsa crond dbus sshd lircd sensors mysqld @ddclient @hddtemp httpd samba stunnel sabnzbd sickbeard)
/etc/network.d/sluggy
CONNECTION='ethernet'
DESCRIPTION='A basic dhcp ethernet connection using iproute'
INTERFACE='wan0'
IP='dhcp'
## for DHCPv6
#IP6='dhcp'
## for IPv6 autoconfiguration
#IP6='stateless'
/etc/network.d/local
CONNECTION='ethernet'
DESCRIPTION='A basic static ethernet connection using iproute'
INTERFACE='lan0'
IP='static'
ADDR='192.168.0.118'
GATEWAY='192.168.0.2'
output of route -nl
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.2 0.0.0.0 UG 0 0 0 lan0
0.0.0.0 85.24.137.1 0.0.0.0 UG 203 0 0 wan0
85.24.137.0 0.0.0.0 255.255.255.0 U 203 0 0 wan0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 lan0
I have had this server running Ubuntu for the past 2 years with the same setup on the NIC's and there everything worked, so I guess i have become a little lazy.
*EDIT* Updated my post with "code" block instead of quote
Last edited by kurri (2011-11-01 22:07:14)

kurri, please edit your post.
When pasting code, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode
like this
It makes the code more readable and more convenient to scroll through.

Enrollment issues after Benefits Configuration Changes

Two of our Disability plans will no longer need to use Cost Groupings as a variant because all enrollees will have the same rates. I changed the configuration 'Define Cost Variants' screen (which has no effective date) to reflect this and added a new cost rule with a blank cost group effective 1/1/2011. All of the existing cost groups for this plan are now delimited as of 12/31/2010.
When we try to enroll employees in these plans for 1/1/2011 Annual Enrollment, the results are inconsistent. For some employees, the plans just don't show up on the enrollment screen. For those who are currently in the plans, the plan shows up, but if you try to enroll them, you receive this error message 'No entry for plan LTD1 / cost variant FINS / key //////0000000000000'. If I change the enrollment date to 1/2/2011, the error goes away.
For employees where the plan does show up, and they have never been enrolled in the plan, the enrollment works fine for 1/1/2011.
Can anyone help?
Thanks

hello,
I have seen this error before and it was usually linked to incorrect configuration.
You should check your feature CSTV1 Cost grouping and make sure it returns the correct entry for the employee
Hope this help
Sarah

Having issues after installing Essbase V9.3.1,configuring the SQL interface

I am having issues after installing Essbase V9.3.1 and configuring the SQL interface. we are using UNIX/AIX box for our Essbase server and UDB DB2 9.1 SP6 as our SQL Interface.
When tried to run an ESSCMD script to perform BUILDDIM operation on Essbase application using the load rule (with the SQL interface), got the error as recorded in the application log file and is attached at the bottom and the .odbc.ini file on the server looks as follows.
Can somebody tell me whether .odbc.ini needs any correction or what else should I do to correct the issue and able to work thru using SQL interface? Appreciate any help provided in this regard. Thanks,
.odbc.ini
[ODBC Data Sources]
DOLU003=IBM DB2 ODBC DRIVER
[DOLU003]
Driver=/home/db2inst1/sqllib/lib/libdb2.a
Database=DOLU003
[ODBC]
Trace=0
TraceFile=odbctrace.out
InstallDir=/home/db2inst1/sqllib/odbclib
[Mon Apr 20 15:16:29 2009]Local/New_Bud/Budget/Olapadm/Info(1021020)
Cannot read SQL driver name for [] from [home/hyperion/.odbc.ini]
[Mon Apr 20 15:16:43 2009]Local/New_Bud/Budget/Olapadm/Info(1013091)
Received Command [SQLRetrieve] from user [Olapadm]
[Mon Apr 20 15:16:43 2009]Local/New_Bud/Budget/Olapadm/Info(1021020)
Cannot read SQL driver name for [] from [home/hyperion/.odbc.ini]
[Mon Apr 20 15:16:43 2009]Local/New_Bud/Budget/Olapadm/Info(1021004)
Connection String is generated
[Mon Apr 20 15:16:43 2009]Local/New_Bud/Budget/Olapadm/Info(1021041)
Connection String is [DSN=DOLU003;UID=...;PWD=...]
[Mon Apr 20 15:16:43 2009]Local/New_Bud/Budget/Olapadm/Info(1021006)
SELECT Statement [SELECT * FROM DB2OLADM.BD_DIMENSION_DEF_PC WHERE DIMENSION_ID
= 12 ORDER BY TREE_NODE_NUM, PARENT_NODE, CHILD_NODE] is generated
[Mon Apr 20 15:16:44 2009]Local/New_Bud/Budget/Olapadm/Info(1021013)
ODBC Layer Error: [7] ==> [[DataDirect][ODBC 20101 driver]6013]
[Mon Apr 20 15:16:44 2009]Local/New_Bud/Budget/Olapadm/Info(1021014)
ODBC Layer Error: Native Error code [0]
[Mon Apr 20 15:16:44 2009]Local/New_Bud/Budget/Olapadm/Error(1021001)
Failed to Establish Connection With SQL Database Server. See log for more information
--------------------------------------------------------------------------------------------------------------------------------------------

I had similar errors when first setting up the SQL interface. Are you on a 64 bit operating system on the essbase server? If so Essbase needs to use the 32 bit odbc driver, not the default 64 bit driver.
The 32 bit driver is still available here SysWOW64\odbcad32.exe <-----This is the 32 bit (Use)
The Administrative tools by default uses system32\odbcad32.exe <----This is the 64 bit (Don't Use)
Once I opened the 32 bit driver interface directly and set it up the errors went away.

Failed to issue COM RESET successfully after 3 attempts. Failing...

Just in case anyone else has this problem, and wants to claw their eyes out.
I upgraded the Hard Disk in my MacBook Pro about four days ago (the new MBP, summer 2009 with SD card). I installed a Hitachi Travelstar 7K320. It worked awesome for about four days, until I went to run the EFI Firmware Update this morning.
My machine stopped booting. I held Command-V to get the verbose boot output, and eventually got the message: Failed to issue COM RESET successfully after 3 attempts. Failing... - which is where the boot halted.
I removed the Hitachi and restored the stock drive, and the laptop now booted fine. I think it's something Apple will have to look into.

I believe posting relevant facts is productive, & a very relevant fact here is that you are trying to use a drive with an interface (SATA-II) that Apple does not currently support in its laptops.
SATA-I controllers are supposed to be compatible with SATA-II drives, but many of them are not. The problem is how some controllers implement auto negotiation, which is supposed to tell the drive to fall back to SATA-1 speeds with the slower controllers. Some SATA-II drives have a jumper to force the slower speed if auto negotiation doesn't work; some do not.
How this compatibility problem came about, & why the jumper is required, is complicated but the short version is that at least four different specification bodies had some responsibility in producing SATA specifications, & not all controllers were designed to the same standards. This includes not just the controllers Apple has been using but those in many PC's as well.
So I agree that Apple dropped the ball, but not necessarily the way you might think: it should have made it very clear that the firmware update implemented an unsupported interface speed, that it might cause problems, & (most importantly) provided a reversion strategy to the former firmware if it did.
Hopefully, Apple will take another 'swing' at this & either provide that reversion strategy or a new update that at least allows the controller to work more reliably with the faster interface. But until then, unless your drive has the jumper, my previous suggestion is probably the best you can do.
BTW, none of the current mechanical drives available for laptops can saturate a SATA-1 bus except for brief bursts from the drive's buffer, so the real loss in performance of running a single SATA-II drive at SATA-1 speeds is almost negligible, something you might notice in a benchmark but not in real-world use.

Sun x4170 ILOM - Can't get to the web interface 2 days after password reset

Just bought a used x4170. I was able to get iLOM on the network and get to the web interface logon screen after setting the IP for it.
I tried logging on but the password was not given to me. So I connected to the serial interface (rj45) from another machine and used putty to connect. Got to the preboot point and was able to reset the password to default, Rebooted.
I was then able to log into iLOM. That was 2 days ago. Today for some reason, I can't get into iLOM. It pings but I can't get to the web interface. I get the IE error "cannot connect" or unable to connect or something like that.
I'm completely new to this brand of server so consider me completely ignorant on all aspects of the hardware.......lol
Thanks

Hello
By default, you connect to the server’s service processor (SP) using the out-of-band network management port (NET MGT). The ILOM sideband management feature enables you to select either the NET MGT port or one of the server’s Gigabit Ethernet ports (NET 0, 1, 2, 3), which are in-band ports, to send and receive ILOM commands to and from the server SP. In-band ports are also called sideband ports.
You can refer more here : https://docs.oracle.com/cd/E19269-01/820-7959-11/820-7959-11.pdf
If you want to use the NET MGT port of ILOM, then your output should display similar to below
-> show /SP/network
/SP/network
    Targets:
        interconnect
        ipv6
        test
    Properties:
        commitpending = (Cannot show property)
        dhcp_clientid = none
        dhcp_server_ip = xxxxxxxxx
        ipaddress = xxxxxxxxx
        ipdiscovery = dhcp
        ipgateway = xxxxxxxxx
        ipnetmask = xxxxxxxxx
        macaddress = 00:10:E0:65:2F:20
        managementport = MGMT   <<<<<<<<<<<<<<
        outofbandmacaddress = 00:10:E0:65:2F:20
        pendingipaddress = xxxxxxxxx
        pendingipdiscovery = dhcp
        pendingipgateway = xxxxxxxxx
        pendingipnetmask = xxxxxxxxx
        pendingmanagementport = MGMT    <<<<<<<<<<<<
        pendingvlan_id = (none)
        sidebandmacaddress = 00:10:E0:65:2F:21
        state = enabled
        vlan_id = (none)
Hope this helps.
Best Regards
Bhavyesh

Default printer resetting after reboot in Windows 7 x64

I'm managing a domain with roughly 450 clients, all running Windows 7 Ent x64, and about 50 printers. All clients have the same desktop image with the exception of a few desktops need special additional software. I push out printers via GPO and it was
running fine until recently. The client pc would reset it default printer every time the pc reboot or log off. First, there was only a handful and now it spreads to almost half the number of pc are being effect with this problem. I've tried different
approaches, even completely rewrite the GPOs with no success. The pc would reset to either PDFCreator or OneNote or XPS or Fax. I found that if I re-image the client desktop the default printer would remain default but I'm keeping that as the
last option since it involves with data migrating and probably consumes a whole lot of time (200+ effected pc). Any leads or suggestions are much appreciated, my clients are not happy and they are chewing me alive :)
I must add that setting default printer via GPO is not an option for me since people with different groups or branches are sharing the same building/floor.

Hi,
I’m not able to get security clearance to send these files to public, I apologize for that, is there a particular section/part that
I should pay attention to from that report? I went through a report just now and I’m not sure what to look for. Would you mind to give me some direction? Thanks again
>> Please try to review the promon log. The Device value in the following Registry path contains the user's default printer:
HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows\Device.
We can use process monitor to view what issue cause the registry key reset.
There is a scenarios for your reference:
One or more network printer connection under
HKCU\Printers\Connections\<NetworkPrinterSubkey>
are missing the "Server" registry key.
Resolution:
Start Regedit.exe
Export HKCU\Printers\Connections to have a backup of the key
View the network printer registry subkeys under HKCU\Printers\Connections if on the right hand side it is missing the registry value "Server" then delete the Network Printer subkey under HKCU\Printers\Connections
Longer Term Solution: Remove the bad Network Printer Share from the server and/or update the print driver on the print server.
>>GPMC.log is just to evaluate if there are some policy cause the Default Printer reset.
>>Event Viewer is a User Interface to find the possible problem convenient.
If the issue persist, as the present situation, we cannot get more information for further analysis, please try to contact
directly with a Microsoft Support Professional to analyze the problem.
To obtain the phone numbers for specific technology request please take a look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see
http://support.microsoft.com/directory/overview.asp for regional support phone numbers.
Thank you for your understanding and I hope this will be resolved soon.
Best Regards
Elytis Cheng

Hard Drive dead? - Failed to Issue COM RESET successfully after 3 attempts.

Hello, i think my 13" 2.53Ghz Unibody (mid2009) MBP's hard drive has had it's last spin. I was using it normally in bootcamp, when windows7 froze, so I rebooted holding the power button....windows wouldnt start any more...ok, so i tried to boot into OSX...stuck at the loading screen with the apple.
Went into verbose mode and it stops at "Failed to issue COM RESET successfully after 3 attempts. Failing..." Google says this has to do with the hard drive.
Did a extensive hardware test (boot + D), all OK, booted from install disk and tried to run disk utility, but it crashed when trying to locate the drives (didn't even list the drive on the right pane). Single User mode wont load either, will give the same COM RESET message. I am literally out of options here.
Is there something i can do to either fix this or verify 100% that my hard disk is truly dead?
I have a backup in timemachine so the data is ok, but the timing couldnt be worse, i have no time to fix this now and needed a working laptop, highly frustrating.
thanks for any tips

nobrex wrote:
Hello, i think my 13" 2.53Ghz Unibody (mid2009) MBP's hard drive has had it's last spin. I was using it normally in bootcamp, when windows7 froze, so I rebooted holding the power button....windows wouldnt start any more...ok, so i tried to boot into OSX...stuck at the loading screen with the apple.
Went into verbose mode and it stops at "Failed to issue COM RESET successfully after 3 attempts. Failing..." Google says this has to do with the hard drive.
Did a extensive hardware test (boot + D), all OK, booted from install disk and tried to run disk utility, but it crashed when trying to locate the drives (didn't even list the drive on the right pane). Single User mode wont load either, will give the same COM RESET message. I am literally out of options here.
Is there something i can do to either fix this or verify 100% that my hard disk is truly dead?
I have a backup in timemachine so the data is ok, but the timing couldnt be worse, i have no time to fix this now and needed a working laptop, highly frustrating.
thanks for any tips
Welcome to the Apple Forums!
Your HDD is probably dead, since the error doesn't appear to indicate something wrong with the motherboard. Just buy a new 2.5" HDD. I don't know about prices in Brazil, but here in the US, a 1TB drive runs for around US$100. Also, check on eBay for people who upgraded their drive and are selling their Apple drive. Some will ship to Brazil, and you can score those for $50-100.
I hope you backed up your hard drive. If not, you'll have to do the whole reinstallation process.

Hp envy 15 Echo issues after reset

Hey, I bought my Hp envy 15-a6 sleekbook like 5 days ago and i factory reset it after some programs disappeared. Now the sound has a echo when I use headphones. Thanks in Advance!

Hi,
Try the below code
77984968
"I work for HP."
Please click the "White Kudos" star to say thanks for helping.
Please mark "Accept As Solution" if my help has solved your problem.

Duplicate Ethernet Interface - Connection Issues

Hi,
Recently, after rebooting, I had a continuous stream of error messages on my login terminal, and I couldn't connect to the network.
[ 669.236979] genirq: Flags mismatch irq 0. 00000080 (eth0) vs. 00015a20 (timer)
[ 670.235840] genirq: Flags mismatch irq 0. 00000080 (eth0) vs. 00015a20 (timer)
[ 671.234701] genirq: Flags mismatch irq 0. 00000080 (eth0) vs. 00015a20 (timer)
# ping www.google.com
ping: unknown host www.google.com
# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether de:34:07:d0:d9:29 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000 ## Duplicate interfaces?
link/ether 00:24:1d:a2:f7:c5 brd ff:ff:ff:ff:ff:ff
# ifconfig eth0 up
SIOCSIFFLAGS: Device or resource busy
# ifconfig eth1 up
# dhcpcd eth1
dhcpcd[732]: version 5.6.4 starting
dhcpcd[732]: eth1: sending IPv6 Router Solicitation
dhcpcd[732]: eth1: rebinding lease of 192.168.1.3
dhcpcd[732]: eth1: acknowledged 192.168.1.3 from 192.168.1.1
dhcpcd[732]: eth1: checking for 192.168.1.3
dhcpcd[732]: eth1: sending IPv6 Router Solicitation
dhcpcd[732]: eth1: leased 192.168.1.3 for 2592000 seconds
dhcpcd[732]: forked to background, child pid 780
# ping www.google.com
64 bytes from bom03s02-in-f18.1e100.net (74.125.236.146): icmp_seq=1 ttl=56 time=11.6 ms
After manually configuring eth1, and assigning it an IP, everything works normally. Another bunch of curious messages at boot up were these:
[ 0.271521] pci 0000:01:07.0: BAR 1: error updating (0xfde00000 != 0x000000)
[ 0.271553] pci 0000:01:07.0: BAR 3: error updating (0xfdf10008 != 0x000008)
[ 0.271583] pci 0000:01:07.0: BAR 2: error updating (0x00c001 != 0x00cc09)
What would be a clean way to fix this?
Thanks in advance!

Thanks for the replies.
In an attempt to establish whether it was the computer or the router I plugged in an old speedtouch 510 router which I had lying around - this worked first time, so I guess it's the netgear that is the issue and I will need to reset it and re-enter all the details, unless anyone knows of a quicker way...?

Issues After Disabling IPv6 on Your NIC on SBS 2008

If you uncheck the IPv6 protocol from your network interface card on your Windows SBS 2008 server you may see the following issues after a reboot:
Microsoft Exchange services fail to start
Server hangs at “Applying Computer Settings…” (can eventually logon after 30 – 60 minutes)
Network icons show as offline
Some or all of the following events
Application Log Events
Source: MSExchange ADAccess
Event ID: 2114
Task Category: Topology
Level: Error
Description:
Process MAD.EXE (PID=2088). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185,
“Microsoft LDAP Error Codes.” Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
Source: MSExchange ADAccess
Event ID: 2601
Task Category: General
Level: Warning
Description:
Process MSEXCHANGEADTOPOLOGY (PID=952). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,…>
– Error code=80040a01.
The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
Source: MSExchange ADAccess
Event ID: 2102
Task Category: Topology
Level: Error
Description:
Process MAD.EXE (PID=2088). All Domain Controller Servers in use are not responding: SBS.sbs2008.local
Source: MSExchange ADAccess
Event ID: 2105
Task Category: Topology
Level: Warning
Description:
Process MAD.EXE (PID=2088). Exchange Active Directory Provider failed to obtain DNS records for domain sbs2008.local. DNS Priority and Weight for the Domain Controllers in this domain will be set to the default values 0 (priority) and 100 (weight).
Source: MSExchange ADAccess
Event ID: 2114
Task Category: Topology
Level: Error
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=952). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge
Base article 218185, “Microsoft LDAP Error Codes.” Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
Source: MSExchangeFBPublish
Event ID: 8197
Task Category: General
Level: Error
Description:
Error initializing session for virtual machine SBS. The error number is 0x80040a01. Make sure Microsoft Exchange Store is running. Also, make sure that there is a valid public folder database on the Exchange server.
Source: MSExchangeTransportLogSearch
Event ID: 7005
Task Category: General
Level: Error
Description:
Microsoft Exchange couldn’t read the configuration from the Active Directory directory service because of error: Failed to load config due to exception: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Exchange Topology service on server
localhost did not return a suitable domain controller.
System Log Events
Source: Service Control Manager
Event ID: 7044
Task Category: None
Level: Warning
Description:
The following service is taking more than 16 minutes to start and may have stopped responding: Microsoft Exchange System Attendant
Source: Service Control Manager
Event ID: 7022
Task Category: None
Level: Error
Description:
The Microsoft Exchange Transport service hung on starting.
Source: Service Control Manager
Event ID: 7024
Task Category: None
Level: Error
Description:
The Microsoft Exchange Information Store service terminated with service-specific error 0 (0×0).

Hi,
Based on your description, it seems to be the same as the following blog.
Issues
After Disabling IPv6 on Your NIC on SBS 2008
Did you mean that encounter the same issue? If so, there is a resolution in that blog, please check if can
help you solve the issue.
If any other issue exists or any update, please don’t hesitate to let me know and provide more details. It
will help me understand clearly.
Best regards,
Justin Gu

3G interface resets but signal looks good

Hi All,
can anyone explain what this means.I have enabled the following debugs. everytime I look at it there is no issue with the signal. But my guess is the router interface is resetting due to the signal. Can anyone explain if its due to 3G signalling
Router 881G
CELLULAR:
DATA debugging is on
DM debugging is on
ASYNC debugging is on
RDM debugging is on
CALLBACK debugging is on
PPP:
PPP authentication debugging is on
PPP protocol errors debugging is on
PPP protocol negotiation debugging is on
BAP:
BAP negotiation debugging is on
BAP error debugging is on
3688676: Mar 29 08:48:33.641 BRU: Ce0 PPP: Outbound ip packet dropped, line protocol not up
3688677: Mar 29 08:48:33.641 BRU: Ce0 PPP: Outbound ip packet dropped, line protocol not up
3688678: Mar 29 08:48:33.641 BRU: Ce0 PPP: Outbound ip packet dropped, line protocol not up
3688679: Mar 29 08:48:33.641 BRU: Ce0 PPP: Outbound ip packet dropped,
3688700: Mar 29 08:48:36.749 BRU: new DSR value received, 1
3688701: Mar 29 08:48:36.749 BRU: old value: handshakes->DSR= 1
3688702: Mar 29 08:48:38.741 BRU: %LINK-3-UPDOWN: Interface Cellular0, changed state to down
3688703: Mar 29 08:48:38.741 BRU: Ce0 PPP: Sending cstate DOWN notification
3688704: Mar 29 08:48:38.745 BRU: Ce0 PPP: Processing CstateDown message
3688705: Mar 29 08:48:49.326 BRU: new DSR value received, 1
3688706: Mar 29 08:48:49.326 BRU: old value: handshakes->DSR= 1
3688707: Mar 29 08:48:49.758 BRU: new DSR value received, 1
3688708: Mar 29 08:48:49.758 BRU: old value: handshakes->DSR= 1
3688709: Mar 29 08:48:56.582 BRU: %LINK-3-UPDOWN: Interface Cellular0, changed state to up
3688710: Mar 29 08:48:56.590 BRU: %DIALER-6-BIND: Interface Ce0 bound to profile Di1
3688711: Mar 29 08:48:56.590 BRU: Ce0 PPP: Sending cstate UP notification
3688712: Mar 29 08:48:56.594 BRU: Ce0 PPP: Processing CstateUp message
Cellular0 is up, line protocol is up
Hardware is 3G Modem-HSPA/UMTS/EDGE/GPRS-850/900/1800/1900/2100MHz / Global
Description: [cewan-phy]
MTU 1500 bytes, BW 5760 Kbit/sec, DLY 20000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, LCP Open
Open: IPCP, loopback not set
Keepalive not supported
Interface is bound to Di1 (Encapsulation PPP)
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 2d03h
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: Class-based queueing
Output queue: 0/1000/0 (size/max total/drops)
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
     53671 packets input, 15696493 bytes, 0 no buffer
     Received 0 broadcasts (0 IP multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     62119 packets output, 13733542 bytes, 0 underruns
     0 output errors, 0 collisions, 5 interface resets
     0 unknown protocol drops
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions
     DCD=up DSR=up DTR=up RTS=up CTS=up
Hardware Information
====================
Modem Firmware Version = K2_0_7_19AP C:/WS/F
Modem Firmware built = 10/26/09
Hardware Version = 1.0
International Mobile Subscriber Identity (IMSI) = 206012210378433
International Mobile Equipment Identity (IMEI) = 359109030082750
Integrated Circuit Card ID (ICCID) = 8932002100084586363
Mobile Subscriber International Subscriber
IDentity Number (MSISDN) =
Factory Serial Number (FSN) = D57138003301002
Modem Status = Online
Current Modem Temperature = 46 deg C, State = Normal
PRI SKU ID = 9993165, SKU Rev. = 1.0
Profile Information
====================
Profile password Encryption level: 7
Profile 1 = ACTIVE*
PDP Type = IPv4
PDP address = <ip address masked>
Access Point Name (APN) = internet.proximus.be
Authentication = None
Username: , Password: 02
* - Default profile
Data Connection Information
===========================
Data Transmitted = 10775742 bytes, Received = 12294276 bytes
Profile 1, Packet Session Status = ACTIVE
        IP address = <ip address masked>
Profile 2, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 3, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 4, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 5, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 6, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 7, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 8, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 9, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 10, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 11, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 12, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 13, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 14, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 15, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Profile 16, Packet Session Status = INACTIVE
        Inactivity Reason = Normal inactivate state
Network Information
===================
Current Service Status = Normal, Service Error = None
Current Service = Combined
Packet Service = HSPA (Attached)
Packet Session Status = Active
Current Roaming Status = Home
Network Selection Mode = Automatic
Country = BEL, Network = PROXI
Mobile Country Code (MCC) = 206
Mobile Network Code (MNC) = 1
Location Area Code (LAC) = 2603
Routing Area Code (RAC) = 208
Cell ID = 20324
Primary Scrambling Code = 466
PLMN Selection = Automatic
Registered PLMN = BEL PROXIMUS , Abbreviated = PROXI
Service Provider =
Radio Information
=================
Radio power mode = ON
Current Band = WCDMA 2100, Channel Number = 10588
Current RSSI = -84 dBm
Band Selected = Auto
Number of nearby cells = 1
Cell 1
        Primary Scrambling Code = 0x1D2
        RSCP = -84 dBm, ECIO = -2 dBm
Modem Security Information
==========================
Card Holder Verification (CHV1) = Disabled
SIM Status = OK
SIM User Operation Required = None
Number of Retries remaining = 3

Hi Marco,
    Connection goes down intermittently and it stays up for very long time, more than a day some time or some time certain no of hours. I am not running any ping. I am not sure about the timing it takes between IPCP is completed ("IPCP: State is Open") and the link is closed ("I TERMREQ").
IOS c880data-universalk9-mz.151-1.T1.bin
Model 881G
One of my friend said there is a bug on 881G router IOS not sure about it though, but he hasnt seen my debug output.
This is the bug he was saying but I am not sure if mine is related to that as my CHAT script dont seem to be time out.
Problem Code: Error Messages, Logs, Debugs Software Version: C880DATA-universalk9-mz.151-2. Problem Details: Customer is running traffic over the 3card in a 881G. It fails however I can see from "show cell 0 all" that the modem has 3G coverage and a good signal as the RSSI is good. However the chat script continues to timeout. The configuration has not changed and it has worked and fails intermi
Thanks in Advance for your help
I have attached the debug of the CHAT script when the link goes down and come back.
3706575: Apr 1 08:51:03.995 BRU: Ce0 PPP: Outbound ip packet dropped, line protocol not up
3706576: Apr 1 08:51:03.995 BRU: Ce0 PPP: Outbound ip packet dropped, line protocol not up
3706577: Apr 1 08:51:03.995 BRU: Ce0 PPP: Outbound ip packet dropped, line protocol not up
3706578: Apr 1 08:51:03.995 BRU: Ce0 PPP: Outbound ip packet dropped, line protocol not up
3706579: Apr 1 08:51:03.999 BRU: Ce0 PPP: No remote authentication for call-out
3706580: Apr 1 08:51:03.999 BRU: Ce0 LCP: Event[Timeout-] State[Closing to Closed]
3706581: Apr 1 08:51:03.999 BRU: Ce0 LCP: Event[DOWN] State[Closed to Initial]
3706582: Apr 1 08:51:03.999 BRU: Ce0 PPP: Phase is DOWN
3706583: Apr 1 08:51:04.007 BRU: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0, changed state to down
3706584: Apr 1 08:51:06.007 BRU: %LINK-5-CHANGED: Interface Cellular0, changed state to reset
3706585: Apr 1 08:51:06.011 BRU: Ce0 DDR: has total 0 call(s), dial_out 0, dial_in 0
3706586: Apr 1 08:51:06.011 BRU: %DIALER-6-UNBIND: Interface Ce0 unbound from profile Di1
3706587: Apr 1 08:51:06.011 BRU: Ce0 PPP: Sending cstate DOWN notification
3706588: Apr 1 08:51:06.011 BRU: Ce0 PPP: Processing CstateDown message
3706589: Apr 1 08:51:06.015 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706590: Apr 1 08:51:07.015 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706591: Apr 1 08:51:08.015 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706592: Apr 1 08:51:09.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706593: Apr 1 08:51:10.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706594: Apr 1 08:51:11.083 BRU: %LINK-3-UPDOWN: Interface Cellular0, changed state to down
3706595: Apr 1 08:51:11.083 BRU: Ce0 PPP: Sending cstate DOWN notification
3706596: Apr 1 08:51:11.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706597: Apr 1 08:51:11.087 BRU: Ce0 PPP: Processing CstateDown message
3706598: Apr 1 08:51:12.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706599: Apr 1 08:51:13.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706600: Apr 1 08:51:14.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706601: Apr 1 08:51:15.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706602: Apr 1 08:51:16.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706603: Apr 1 08:51:17.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706604: Apr 1 08:51:18.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706605: Apr 1 08:51:19.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706606: Apr 1 08:51:20.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
3706607: Apr 1 08:51:21.011 BRU: Ce0 DDR: re-enable timeout
3706608: Apr 1 08:51:21.083 BRU: Ce0 DDR: rotor dialout [best] least recent failure is also most recent failure
3706609: Apr 1 08:51:21.083 BRU: Ce0 DDR: rotor dialout [best] also has most recent failure
3706610: Apr 1 08:51:21.083 BRU: Ce0 DDR: rotor dialout [best]
3706611: Apr 1 08:51:21.083 BRU: Di1 DDR: Nailing up the Dialer profile [attempt 16]
3706612: Apr 1 08:51:21.083 BRU: Di1 DDR: Dialer dialing - persistent dialer profile
3706613: Apr 1 08:51:21.083 BRU: Ce0 DDR: Dialing cause Persistent Dialer Profile
3706614: Apr 1 08:51:21.083 BRU: Ce0 DDR: Attempting to dial cellprofile1
3706615: Apr 1 08:51:21.083 BRU: CHAT3: Attempting async line dialer script
3706616: Apr 1 08:51:21.083 BRU: CHAT3: Dialing using Modem script: cellprofile1 & System script: none
3706617: Apr 1 08:51:21.083 BRU: CHAT3: process started
3706618: Apr 1 08:51:21.083 BRU: CHAT3: Asserting DTR
3706619: Apr 1 08:51:21.087 BRU: CHAT3: Chat script cellprofile1 started
3706620: Apr 1 08:51:21.087 BRU: CHAT3: Sending string: ATDT*99***1#
3706621: Apr 1 08:51:21.087 BRU: CHAT3: Expecting string: CONNECT
3706622: Apr 1 08:51:21.091 BRU: CHAT3: Completed match for expect: CONNECT
3706623: Apr 1 08:51:21.091 BRU: CHAT3: Chat script cellprofile1 finished, status = Success
3706624: Apr 1 08:51:23.171 BRU: %LINK-3-UPDOWN: Interface Cellular0, changed state to up
3706625: Apr 1 08:51:23.171 BRU: Ce0 DDR: Dialer statechange to up
3706626: Apr 1 08:51:23.175 BRU: %DIALER-6-BIND: Interface Ce0 bound to profile Di1
3706627: Apr 1 08:51:23.175 BRU: Ce0 DDR: Dialer call has been placed
3706628: Apr 1 08:51:23.175 BRU: Ce0 PPP: Sending cstate UP notification
3706629: Apr 1 08:51:23.179 BRU: Ce0 PPP: Processing CstateUp message
3706630: Apr 1 08:51:23.183 BRU: PPP: Alloc Context [852C2C68]
3706631: Apr 1 08:51:23.183 BRU: ppp23 PPP: Phase is ESTABLISHING
3706632: Apr 1 08:51:23.183 BRU: Ce0 PPP: Using dialer call direction
3706633: Apr 1 08:51:23.183 BRU: Ce0 PPP: Treating connection as a callout
3706634: Apr 1 08:51:23.183 BRU: Ce0 PPP: Session handle[AE000017] Session id[23]
3706635: Apr 1 08:51:23.183 BRU: Ce0 LCP: Event[OPEN] State[Initial to Starting]
3706636: Apr 1 08:51:23.183 BRU: Ce0 PPP: No remote authentication for call-out
3706637: Apr 1 08:51:23.183 BRU: Ce0 LCP: O CONFREQ [Starting] id 1 len 20
3706638: Apr 1 08:51:23.183 BRU: Ce0 LCP:    ACCM 0x000A0000 (0x0206000A0000)
3706639: Apr 1 08:51:23.183 BRU: Ce0 LCP:    MagicNumber 0xE74DCDE6 (0x0506E74DCDE6)
3706640: Apr 1 08:51:23.183 BRU: Ce0 LCP:    PFC (0x0702)
3706641: Apr 1 08:51:23.183 BRU: Ce0 LCP:    ACFC (0x0802)
3706642: Apr 1 08:51:23.183 BRU: Ce0 LCP: Event[UP] State[Starting to REQsent]
3706643: Apr 1 08:51:23.191 BRU: Ce0 LCP: I CONFREQ [REQsent] id 7 len 25
3706644: Apr 1 08:51:23.191 BRU: Ce0 LCP:    ACCM 0x00000000 (0x020600000000)
3706645: Apr 1 08:51:23.191 BRU: Ce0 LCP:    AuthProto CHAP (0x0305C22305)
3706646: Apr 1 08:51:23.191 BRU: Ce0 LCP:    MagicNumber 0x813CA39C (0x0506813CA39C)
3706647: Apr 1 08:51:23.191 BRU: Ce0 LCP:    PFC (0x0702)
3706648: Apr 1 08:51:23.191 BRU: Ce0 LCP:    ACFC (0x0802)
3706649: Apr 1 08:51:23.191 BRU: Ce0 LCP: O CONFACK [REQsent] id 7 len 25
3706650: Apr 1 08:51:23.191 BRU: Ce0 LCP:    ACCM 0x00000000 (0x020600000000)
3706651: Apr 1 08:51:23.191 BRU: Ce0 LCP:    AuthProto CHAP (0x0305C22305)
3706652: Apr 1 08:51:23.191 BRU: Ce0 LCP:    MagicNumber 0x813CA39C (0x0506813CA39C)
3706653: Apr 1 08:51:23.191 BRU: Ce0 LCP:    PFC (0x0702)
3706654: Apr 1 08:51:23.191 BRU: Ce0 LCP:    ACFC (0x0802)
3706655: Apr 1 08:51:23.191 BRU: Ce0 LCP: Event[Receive ConfReq+] State[REQsent to ACKsent]
3706656: Apr 1 08:51:23.191 BRU: Ce0 LCP: I CONFACK [ACKsent] id 1 len 20
3706657: Apr 1 08:51:23.191 BRU: Ce0 LCP:    ACCM 0x000A0000 (0x0206000A0000)
3706658: Apr 1 08:51:23.191 BRU: Ce0 LCP:    MagicNumber 0xE74DCDE6 (0x0506E74DCDE6)
3706659: Apr 1 08:51:23.191 BRU: Ce0 LCP:    PFC (0x0702)
3706660: Apr 1 08:51:23.191 BRU: Ce0 LCP:    ACFC (0x0802)
3706661: Apr 1 08:51:23.191 BRU: Ce0 LCP: Event[Receive ConfAck] State[ACKsent to Open]
3706662: Apr 1 08:51:23.199 BRU: Ce0 PPP: Queue CHAP code[1] id[1]
3706663: Apr 1 08:51:23.211 BRU: Ce0 PPP: Phase is AUTHENTICATING, by the peer
3706664: Apr 1 08:51:23.211 BRU: Ce0 CHAP: Redirect packet to Ce0
3706665: Apr 1 08:51:23.211 BRU: Ce0 CHAP: I CHALLENGE id 1 len 35 from "UMTS_CHAP_SRVR"
3706666: Apr 1 08:51:23.211 BRU: Ce0 PPP: Sent CHAP SENDAUTH Request
3706667: Apr 1 08:51:23.211 BRU: Ce0 LCP: State is Open
3706668: Apr 1 08:51:23.211 BRU: Ce0 PPP: Received SENDAUTH Response FAIL
3706669: Apr 1 08:51:23.211 BRU: Ce0 CHAP: Using hostname from interface CHAP
3706670: Apr 1 08:51:23.211 BRU: Ce0 CHAP: Using password from interface CHAP
3706671: Apr 1 08:51:23.211 BRU: Ce0 CHAP: O RESPONSE id 1 len 41 from
3706672: Apr 1 08:51:23.219 BRU: Ce0 CHAP: I SUCCESS id 1 len 4
3706673: Apr 1 08:51:23.219 BRU: Ce0 PPP: Phase is FORWARDING, Attempting Forward
3706674: Apr 1 08:51:23.223 BRU: Ce0 PPP: Phase is ESTABLISHING, Finish LCP
3706675: Apr 1 08:51:23.223 BRU: Ce0 PPP: Phase is UP
3706676: Apr 1 08:51:23.223 BRU: Ce0 IPCP: Protocol configured, start CP. state[Initial]
3706677: Apr 1 08:51:23.223 BRU: Ce0 IPCP: Event[OPEN] State[Initial to Starting]
3706678: Apr 1 08:51:23.223 BRU: Ce0 IPCP: O CONFREQ [Starting] id 1 len 22
3706679: Apr 1 08:51:23.223 BRU: Ce0 IPCP:    Address 0.0.0.0 (0x030600000000)
3706680: Apr 1 08:51:23.223 BRU: Ce0 IPCP:    PrimaryDNS 0.0.0.0 (0x810600000000)
3706681: Apr 1 08:51:23.223 BRU: Ce0 IPCP:    SecondaryDNS 0.0.0.0 (0x830600000000)
3706682: Apr 1 08:51:23.223 BRU: Ce0 IPCP: Event[UP] State[Starting to REQsent]
3706683: Apr 1 08:51:23.227 BRU: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0, changed state to up
3706684: Apr 1 08:51:24.223 BRU: Ce0 IPCP: I CONFNAK [REQsent] id 1 len 16
3706685: Apr 1 08:51:24.223 BRU: Ce0 IPCP:    PrimaryDNS (0x81060A0B0C0D)
3706686: Apr 1 08:51:24.223 BRU: Ce0 IPCP:    SecondaryDNS (0x83060A0B0C0E)
3706687: Apr 1 08:51:24.223 BRU: Ce0 IPCP: O CONFREQ [REQsent] id 2 len 22
3706688: Apr 1 08:51:24.223 BRU: Ce0 IPCP:    Address 0.0.0.0 (0x030600000000)
3706689: Apr 1 08:51:24.227 BRU: Ce0 IPCP:    PrimaryDNS (0x81060A0B0C0D)
3706690: Apr 1 08:51:24.227 BRU: Ce0 IPCP:    SecondaryDNS (0x83060A0B0C0E)
3706691: Apr 1 08:51:24.227 BRU: Ce0 IPCP: Event[Receive ConfNak/Rej] State[REQsent to REQsent]
3706692: Apr 1 08:51:25.231 BRU: Ce0 IPCP: I CONFNAK [REQsent] id 2 len 16
3706693: Apr 1 08:51:25.231 BRU: Ce0 IPCP:    PrimaryDNS (0x81060A0B0C0D)
3706694: Apr 1 08:51:25.231 BRU: Ce0 IPCP:    SecondaryDNS (0x83060A0B0C0E)
3706695: Apr 1 08:51:25.231 BRU: Ce0 IPCP: O CONFREQ [REQsent] id 3 len 22
3706696: Apr 1 08:51:25.231 BRU: Ce0 IPCP:    Address 0.0.0.0 (0x030600000000)
3706697: Apr 1 08:51:25.231 BRU: Ce0 IPCP:    PrimaryDNS (0x81060A0B0C0D)
3706698: Apr 1 08:51:25.231 BRU: Ce0 IPCP:    SecondaryDNS (0x83060A0B0C0E)
3706699: Apr 1 08:51:25.231 BRU: Ce0 IPCP: Event[Receive ConfNak/Rej] State[REQsent to REQsent]
3706700: Apr 1 08:51:25.423 BRU: Ce0 IPCP: I CONFREQ [REQsent] id 2 len 4
3706701: Apr 1 08:51:25.423 BRU: Ce0 IPCP AUTHOR: Done. Her address 0.0.0.0, we want 0.0.0.0
3706702: Apr 1 08:51:25.423 BRU: Ce0 IPCP: O CONFACK [REQsent] id 2 len 4
3706703: Apr 1 08:51:25.427 BRU: Ce0 IPCP: Event[Receive ConfReq+] State[REQsent to ACKsent]
3706704: Apr 1 08:51:25.427 BRU: Ce0 IPCP: I CONFNAK [ACKsent] id 3 len 22
3706705: Apr 1 08:51:25.427 BRU: Ce0 IPCP:    Address (0x0306B2904FF3)
3706706: Apr 1 08:51:25.427 BRU: Ce0 IPCP:    PrimaryDNS (0x810651A93C6B)
3706707: Apr 1 08:51:25.427 BRU: Ce0 IPCP:    SecondaryDNS (0x830651A93C6B)
3706708: Apr 1 08:51:25.427 BRU: Ce0 IPCP: O CONFREQ [ACKsent] id 4 len 22
3706709: Apr 1 08:51:25.427 BRU: Ce0 IPCP:    Address (0x0306B2904FF3)
3706710: Apr 1 08:51:25.427 BRU: Ce0 IPCP:    PrimaryDNS (0x810651A93C6B)
3706711: Apr 1 08:51:25.427 BRU: Ce0 IPCP:    SecondaryDNS (0x830651A93C6B)
3706712: Apr 1 08:51:25.427 BRU: Ce0 IPCP: Event[Receive ConfNak/Rej] State[ACKsent to ACKsent]
3706713: Apr 1 08:51:25.443 BRU: Ce0 IPCP: I CONFACK [ACKsent] id 4 len 22
3706714: Apr 1 08:51:25.475 BRU: Ce0 IPCP:    Address (0x0306B2904FF3)
3706715: Apr 1 08:51:25.475 BRU: Ce0 IPCP:    PrimaryDNS (0x810651A93C6B)
3706716: Apr 1 08:51:25.475 BRU: Ce0 IPCP:    SecondaryDNS (0x830651A93C6B)
3706717: Apr 1 08:51:25.475 BRU: Ce0 IPCP: Event[Receive ConfAck] State[ACKsent to Open]
3706718: Apr 1 08:51:25.475 BRU: Ce0 IPCP: State is Open
3706719: Apr 1 08:51:25.475 BRU: Di1 IPCP: Install negotiated IP interface address
3706720: Apr 1 08:51:25.479 BRU: Ce0 DDR: dialer protocol up
3706721: Apr 1 08:51:25.479 BRU: Di1 DDR: Persistent Dialer Profile nailed up successfully
Cheers
Raj

"default interface" equivalent for SG300/500 switches?

Can anyone tell me if there is an equivalent CLI command to reset an interface configuration to default?
In IOS it is "default interface <interface>" which removes all configuration from that switch port. I don't seem to be able to find the same in the SG series CLI.
Thanks,
Rob

Hello Rob,
There isn't an equivalent command on the SG series switches, but I will be bringing it up as a feature request, because it would be quite useful.
Until then the only way to reset a port would be to use all of the no versions of the commands, which I know can be a bit of a pain.
Thank you for choosing Cisco,
Christopher Ebert - Advanced Network Support Engineer
Cisco Small Business Support Center
*please rate helpful posts*

Internet Explorer issues after installing Update KB2955163 on Windows 8

Dear,
Since we've installed Windows update KB2955163 on Windows 8, we've been experiencing the following issues:
- After using Internet Explorer for a long while (one hour or longer), some websites won't work properly anymore. For example: list boxes and pop-ups don't appear.
- After using Internet Explorer for a long while (one hour or longer), employees can't access any external webpages. They receive a message saying the webpage isn't available. Reconfiguring the Proxy-settings will temporarily fix this problem.
*The above problems don't appear on all of our computers running Windows 8.
We've found the only fix for these problems, is to uninstall Windows update KB2955163.
All of our affected systems are running Windows 8 Enterprise x64, and come from various manufacturers (Dell / HP etc.).
Is anyone of you guys familiar with these specific issues regarding Windows update KB2955163?
Many thanks in advance,
Thom

Hi,
Did this issue occur on all computers which installed that update?
In generally, it's not most likely be Windows update cause.
Let's narrow down the issue:
Have you tried to reset the Internet Explorer to check the result:
1.Close all Internet Explorer windows that are currently open.
2.Open the desktop, and then tap or click the Internet Explorer icon on the taskbar. Changing your settings will affect both Internet Explorer and Internet Explorer for the desktop.
3.Tap or click the Tools button, and then tap or click
Internet options.
4.Tap or Click the Advanced tab, and then tap or click
Reset.
5.In the Reset Internet Explorer Settings dialog box, tap or click Reset.
6.When Internet Explorer finishes applying default settings, tap or click
Close, and then tap or click OK. You'll need to restart your PC for these changes to take effect.
If it persists, perform a clean boot to see if it caused by some third-party software:
How to perform a clean boot in Windows
http://support.microsoft.com/kb/929135
Karen Hu
TechNet Community Support

Boot issue after shutdown plus power - no problem after restart or after removing power cord

Hello,
I have a Pavilion Elite m9275.nl desktop. I experience boot issues after a regular shut down.
After a regular shut down and pressing the power button within a few seconds/minutes, it keeps hanging in the HP startup / BIOS screen, Windows 8 won't boot, the hard drive light doesn't flash;
After a restart from Windows (instead of shut down) it boots correctly from the c-drive. No hard-drive problems at all;
After a shut down and removing the power cord for 10-15 minutes, it boots correctly from the c-drive. No hard-drive problems at all.
When the PC does not boot, F10 (to enter BIOS settings) does not work neither, so it seems to be a hardware or BIOS issue.
I already replaced the CMOS battery and already loaded default BIOS settings.
During a succesful boot or after pressing F10 (to enter BIOS settings) the screen shows some disk information right after the BIOS. This is the screen that says something like "press CTRL-I to start configuration utility". During a succesful boot the hard disk light flashes shortly before displaying that screen. During an unsuccesful boot the hard disk doesn't flash.
Before replacing a hardware component, I need to know what to replace...
Could it be the hard disk controller or hard disk is defect?
Where is the hard disk controller stored?
Can I upgrade the firmware of the hard disk controller?
BUT: why does it work when I remove the power cord for 15 minutes or after a restart (instead of a shutdown and than pressing power)?
Many thanks in advance,
Sjoerd-Jaap Westra

sjwestra
I apologize for the delay in responding to your post. First I am glad you were able to resolve your initial issue and to help I have included a link to a document 'Bios Setup Utility Information and Menu Options' that will provide you with instructions on how to enter the Bios and provides additional information on navigating it as well.
http://goo.gl/HIclUV
If you need any further information please re-post.
Thank you for your post.
Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
Dunidar
I work on behalf of HP
Find out a bit more about me by checking out my profile!
"Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

Default interface reset issue after ISE configuration

Similar Messages

Maybe you are looking for