1252 VLAN does not

Similar Questions

• VLAN does not work on my ESXi 4.1

  Hello world

  I thank I could achieve this configuration fairly quickly, but it looks like I forgot something.

  I want to connect to a real machine, I'll call her server to one of my virtual machine, using a 802. 1 q VLan. To do this:

  -on my physical netgear switch, I created a new VLAN 802. 1 q, which has the id: 100. My server is connected to a port without a label to this VLAN '100 '.

  My ESXi is connected to a port marked to this VLAN '100 '.

  - then I created a new group of ports in the vswitch linked to my ethernet interface physical ESXi (the one that is connected to the netgear switch). I implemented the VLAN 100 id in this port group.

  -J' I set up my VM so that it uses this interface ethernet port group.

  The problem is when my ping on my server VM, it gets no answer: I see the appeal by the virtual machine on my server with tcpdump, then the response from the server with arp ARP response, but this arp reply never saw my VM.

  So it seems that communication is correct VM to the server but no server VM. I use an ESXi DELL server with some ethernet interfaces and the one I use (broadcom interface) for the VLAN is not the management interface.

  Thanks much for any help!

  Alex

  Alex

  If your ESXi is connected only to physical port 1 and port is shared resources on the physical switch, then you should have a unique vSwitch in your ESXi. On this vSwitch, create two ports: one for one for VM3 and VM2. Give each group of port id VLAN different (2 for "port_group_2") and 3 for "port_group_3" and attach each VM to its corresponding port group.

  Franck

• 3rd interface VLAN does not add properly

  Hello

  I have some difficulty with a switch 300 series running in mode of L3. I created two VLANS each with an interface IP that work well without any problems. The problem I have is when adding a third interface VLAN and IP - for some reason the switch seems not add the subnet in its routing as a directly connected route table.

  The first and second VLAN add correctly. It seems to be the third. I have factory default, the switch and still the same. Version is 1.1.2.0.

  The Setup is as follows:

  VLAN1 - 10.20.2.253/24

  VLAN2 - 192.168.2.253/24

  VLAN3 - 192.168.3.253/24

  Ping results are:

  switch27b42e #ping 10.20.2.253

  Ping 10.20.2.253 with 18 bytes of data:

  18 bytes from 10.20.2.253: icmp_seq = 1. time = 0 ms

  18 bytes from 10.20.2.253: icmp_seq = 2. time = 0 ms

  18 bytes from 10.20.2.253: icmp_seq = 3. time = 0 ms

  18 bytes from 10.20.2.253: icmp_seq = 4. time = 0 ms

  -10.20.2.253 PING Statistics-

  4 packets transmitted, 4 packets received, 0% packet loss

  round-trip (ms) min/avg/max = 0/0/0

  switch27b42e #ping 192.168.2.253

  Ping 192.168.2.253 with 18 bytes of data:

  18 bytes to 192.168.2.253: icmp_seq = 1. time = 0 ms

  18 bytes to 192.168.2.253: icmp_seq = 2. time = 0 ms

  18 bytes to 192.168.2.253: icmp_seq = 3. time = 0 ms

  18 bytes to 192.168.2.253: icmp_seq = 4. time = 0 ms

  -192.168.2.253 PING Statistics-

  4 packets transmitted, 4 packets received, 0% packet loss

  round-trip (ms) min/avg/max = 0/0/0

  switch27b42e #ping 192.168.3.253

  Ping 192.168.3.253 with 18 bytes of data:

  PING: net-unreachable

  PING: net-unreachable

  PING: net-unreachable

  PING: net-unreachable

  -192.168.3.253 PING Statistics-

  4 packets transmitted, 0 packets received, 100% packet loss

  Additional output which can be interesting:

  switch27b42e #show ip int vlan 1

  Type of priority status done IP address

  Broadcast

  ------------------- ----------- ---------- ---------- -----------

  static 10.20.2.253/24 disable invalid

  switch27b42e #show ip int vlan 2

  Type of priority status done IP address

  Broadcast

  ------------------- ----------- ---------- ---------- -----------

  static 192.168.2.253/24 disable invalid

  switch27b42e #show ip int vlan 3

  Type of priority status done IP address

  Broadcast

  ------------------- ----------- ---------- ---------- -----------

  static 192.168.3.253/24 disable invalid

  switch27b42e #show ip route

  Maximum parallel paths: 1 (1 after reset)

  IP routing: enabled

  Code: C - connected, S - static, D - DHCP

  C 10.20.2.0/24 is directly connected vlan 1

  C 192.168.2.0/24 is directly connected vlan 2

  What I am doing wrong?

  Thank you in advance.

  Craig

  Hi Craig,.

  I don't think you're doing anything wrong.

  The command line shows that this IP for VLAN3 interface is not connected, or at least nothing is connected physically VLAN3.

  Connect a PC VLAN3 and see if the interface road happens.

  I guess just that nothing is plugged physically vlan3.

  regards Dave.

• VLAN does not not as expected

  Current configuration:

  Firewall and route point for two networks (personal and guest).  A port (port 1) for personnel and port (port 2) separate for the guest.    Port 1 (staff) on the FW goes to a Dell connect 2724 with default config managed.   All staff resources are on the dell connect.  Also on the dell connect is a point of wireless access for staff.  Port 2 (comments) plugs directly into a guest wifi AP (separate from the staff).  Everything works.

  State:

  The wireless access point that we use is the Engenius EAP350 and it has the ability to have the SSID 8 each in their own VIRTUAL local area network.  I'm looking to move the two networks wireless on a single access point.

  To do this I moved the FW 2 port to a port of the printer dell connect (port 9) and put it in 2 PVID and changed the dell connect the port connected to the existing personal wifi AP (port 7) a trunk (tag 2) port.  all other parameters are always default.  Personal wifi is the vlan 1 and wifi of comments is vlan 2 and labeled on the AP.  My hypothesis is that them VLAN are marked with the AP, authorized by the dell connect port port trunk and then requests DHCP for VLANs we then go to the FW through port a and dhcp vlan 2 go to the fw on port 9.  It did not work.  So to remove the AP of the equation all together, I've done 10 on the dell port connect a PVID in vlan 2 also and plugged in my laptop.  Since the port 9 and 10 are the two access ports in vlan 2, all dhcp requests should be met by the FW on the correct subnet.  However, it did not work.  any ideas or examples that can be sent on the configuration of the access and trunk.  I am very well versed on them with cisco, but dell connect do it a little different.

  the AP can send some unidentified VLAN 1? If you are not correct, you will need to establish another VIRTUAL local network you can send Tags images for, for example, VLAN 3. And not use VLAN 1.

• App 5.1 server does not not on different VLANS

  Helloooo

  I just installed a new server and I use the server application. Everything seemed to work fine until I moved my iMac to a VLAN different. Profiles and update settings do not push to the iMac and sit at a stadium in waiting. Also to register the new iMacs on the server I get to the login server window and it crashes it and does not authenticate. Screen opens by saying that I can open a second window and registration. When I try to register, I get an unknown error and that it fails. It seems timeless. I tried to change a lot of settings prescribed by other users, but nothing helped. Someone at - it advice on what could be the problem.

  See you soon

  Sean

  Hello

  I took the easy on this way and bring a USB ethernet to my mac so that I have two physical interfaces. An in each VLAN.

  There are other ways to do this, and this is a good article:

  https://blog.Pivotal.IO/Labs/Labs/using-deploystudio-across-Subnets-a-Path-Not-t Aken

  Kind regards

  Erik

• Cisco NAC appliance - after a success does not change users to connect to the vlan propper

  Hello

  I am new to cisco NAC BURNERS and I have to troubleshoot an implementation. It is a real OOB IP gateway configuration. Users can connect to the Pentecost the CCA, but after the connection of this success, they remain on the role not authenticated, as well as on this vlan. I checked the SNMP protocol and seems to work very well. Also, I checked the logs on nac_manager.log and there is nothing surprising, in fact I see nothing about this user or IP address that connects.

  Also the user does not appear on the list of users online on cam.

  Can someone help me figure out how can I fix? version 4.8, I'll post any information requested

  Thank you

  We recently had the problem with Windows AD SSO and Windows 7 clients.

  Would authenticate the XP clients very well, however, Windows 7 clients would not authenticate and will remain just on the authenticated vlan.

  Our question was looking for CASE SSO account, we installed on AD. It only support the encryption, WHICH has no Windows 7 64. We turned off "Use OF THE encryption" on the account authentication UNIQUE AD and re-tested.

  What are the parameters of the port-profile to which is applied the switchport?

  What is the map settings vlan ports trunk not approved or confidence?

• SG200 SG200 VLAN Trunk does not

  I have 2 switches SG200-8 and I'm trying to cross the two switches of trunking VLAN, I configured IG1 article on both switches as a port trunk with native VLAN1 and VLAN2 tag.  VLAN 1 and 2 exist on both switches.

  Traffic on VLAN 1 passes without problem, but traffic on VLAN2 does not at all.  I confirmed that changing the trunk to tagged VLAN1 and VLAN2 native allows traffic then on VLAN2 flow through the switch but not so traffic on VLAN1.

  I also tried this as a SHIFT and a general port with the same results, everyone knows about this problem?

  Hi Ultrique01,

  I thank very you much for all the tests. This isn't very common hardware problem, but we might need to consider specifically your switches.

  At this point I suggest you to contact our Small Business Support Center and open the ticket:

  http://www.Cisco.com/c/en/us/support/Web/TSD-Cisco-small-business-suppor...

  Kind regards

  Aleksandra

• VLAN and the SSID does not not in the Web Interface

  We have a couple of APs which do not show the VLAN and via the web interface of AP SSID.  If you go to the SSID Manager page in the web interface, the page rises but doesn't show any SSID configured.  It goes the same for Services - Vlan.  This page appears but does not show in any VLANS configured.  If you telnet to the APs, you see the mssid listed and all the SSID interfaces.  The SSID on the access point is functional and working.  It is just so hard to use the web interface for these APs.  I tried to compare configs running on APs where the web interface does not show this and APs that it shows, but cannot see any differences.

  Thank you.

  Have you tried with different browsers?

  Nicolas

• 6248 VLAN do not receive the DHCP scope

  I created two new DHCP scopes in my windows server 2003:

  192.168.2.0 - public, and
  192.168.3.0 - VOIP.

  This DHCP server is connected to a Dell powerconnect 2708, which is connected to our new powerconnect 6248P via fiber point-to-point.

  In the new computers on network on the default 1 VLAN are correctly attributed IPs as they connect.

  I issued the following commands to the 6248 CLI:

  Enable
  Configure
  database of VLAN
  VLAN 20
  VLAN 30
  output

  Configure
  range of interface ethernet 1/1-g1/g2
  switchport mode general
  VLAN allowed switchport General add 20
  switchport General pvid 20
  l2relay DHCP
  output

  Configure
  range of interface ethernet 1/1-g3/g6
  switchport mode general
  VLAN allowed switchport General add 30
  switchport General pvid 30
  l2relay DHCP
  output

  interface ethernet 1/g11
  switchport mode general
  VLAN allowed switchport General add 20
  VLAN allowed switchport General add 30
  l2relay DHCP
  output

  Configure
  interface vlan 20
  name 'PUBLIC '.
  Routing
  IP 192.168.2.1 255.255.255.0
  IP helper 192.168.1.150
  output

  Configure
  interface vlan 30
  name "VOIP."
  Routing
  address 192.168.3.1 255.255.255
  IP helper 192.168.1.150
  output

  IP routing

  I also added all traffic on VLAN 20 and 30 of VLAN on ports 1/g11 (6248) and port 2 (2708). VLAN 1 access was removed from ports 1/1/g1-g6 (6248)

  Everything seems to have been set correctly, but I can't get a response from the DHCP server on all ports attached to VLAN 20. The powerconnect 2708 switch is unable to pass the baton to the server? Is it possible that something falls in the point to point?

  I would greatly appreciate any comments or suggestions, thanks!

  The 6248 has no default gateway. It wont let me put 192.168.1.1 because he does not reside in the same subnet as the 6248 (192.168.99.1)

  The 2708 has listed 192.168.1.1 as its default gateway.

  At this point, the network has too many complexities for me to unravel. I am very happy that at least I solved for DHCP when we finally migrate our server to the new location.

  Once the server is up, and the gateway/firewall are directly connected to the 6248; I will review the correct configuration of this network.

  Some advice to those who might have a similar problem: check your management VLAN. It may not be the same VLAN 1 if you plan to routing to work from VLAN 1 to nowhere else because the VLAN management cannot be routed. Also check static routing of your access point, make sure the front door has a return of the ips of your VLAN, IE: 192.168.2.0 255.255.255.0 gateway_ip

  That's all for now. Thank you to all who have contributed

• PowerConnect 6200 ACL does not seem to work

  Hello

  I have a total of four 6248 s two groups at different locations that are configured with VRRP + OSPF.  I tried to set up a simple ACL on either a VLAN to allow a portion of the traffic and block everything else, but I can't make it work.  I have tried many combinations to try to get this working, but so far without success.  It's just a simple ACL, which should allow the web/http traffic on the 10.1.30.100 server and blocks everything else.

  The only type of ACE that seem to work are either a "deny ip any any" or "permit ip any any" If you try an ACE with a destination host and subnet mask 0.0.0.0 it's just all this blocking.  Has anyone else had problems of the ACL or is it just my incompetence in preventing me from getting the 6200 ACL work properly?  I didn't have this problem, get the ACL list to work on our Cisco 2811 routers, just at the moment where I tried on the PC6248s.

  1. config
  2. int vlan 720
  3. no ip-group vlan720-in in access
  4. output
  5. No list of access-vlan720-en
  6. access-list vlan720-in permit tcp any 10.1.30.100 0.0.0.0 eq 80
  7. int vlan 720
  8. IP access-group vlan720-in in
  9. output
  10. output
  11. copy, run start
  12. There

  Just an update on this issue.  I worked with Dell to determine why the ACL does not seem to work.  We discovered that the 6200 apply ACL to the traffic as a VLAN ACL Cisco card as opposed to a router ACL entry.  This causes the ACL to apply to not only routed or transferred but also traffic switched in the same VLAN.

  This has been the source of my problems that my traffic is not limited to a single 6200.  I developed a simple laboratory to check that the 6200 applied traffic switched in the same VLAN ACL.

  First the 6200 has one ACL applied to VLAN5 both PC1 and PC2 are in VLAN 5.  They are both on the same subnet 192.168.5.0/24.  The ACL has a statement of "permit icmp any one" but nothing else.  The PC1 and PC2 are running Windows XP Pro with IIS is installed for the test.  The firewall on both is disabled.

  PC #1 IP: 192.168.5.2/24
  PC #2 IP: 192.168.5.3/24

  [6200]
  |    |
  |    |
  |   [2950T #2] <-->[PC #2]
  |
  |
  [2950T #1] <-->[PC #1]

  In this scenario PC1 and PC2 can ping each other without problem because of the permit icmp any any statement, but you cannot access the IIS site on each of the other computers.

  Dell said that this is normal and if you want communication VLAN VLAN you 'license ip ' to make it work properly.  I also found that traffic back from other VLANs were also denied because of the ACL applied on all of the incoming traffic.  As a solution, the license statement should be included for ALL traffic back to the limited subnet other subnets.  So in this case "ip enable any ".

  I find it a bit annoying that ACL is applied in the form of maps of VLAN not like real incoming router ACL as they are on similar Cisco devices as the 3750.  So there is a work around.  I hope they can solve the problem in a future update, because I really think that the 6200 is a great device.

  Here you can see the difference between VLAN ACLs cards and router entry ACL where they are applied in what concerns local traffic to VLAN.
  http://www.Cisco.com/en/us/docs/switches/LAN/catalyst3750/software/release/12.2_25_see/configuration/guide/swacl.html#wp1572522

• Force10 MXL - VLAN is not routing.

  I'm trying to set up a simple installation Layer 3 on stacked MXL Force10 switches.

  ManagementEthernet 0/0 90.21.0.175 YES manual upward, upward
  VLAN 33 10.1.33.1 YES manual upward, upward
  VLAN 101 10.1.32.1 YES manual upward, upward
  VLAN 103 192.168.103.1 YES manual upward, upward

  MXL-stack #sho vlan

  Q: U - no identified, the T - tag

  Ports Status Description Q NUM
  * 1 U active Te 0/3-6, 11-14, 17-23, 25-32
  U Te 1/3-6, 11-14, 16-23, 25-31

  EENET active 33 U Te 1/15<>
   
  101 production Dynamics network T Te 0/1-2, 7-8, 15-16, 24, 44<==10.1.33.x>
  T Te 1/8,24,32
                                          
  External network active 103 T Te 0/8,16,24<==192.168.103.x>
  T Te 1/1-2, 8, 24, 32
  U Te 1/7

  Route ip MXL-stack #sho

  Destination Gateway Dist/metric was last modified
  -----------                          -------                                ----------- -----------
  C Direct 10.1.32.0/24, Vl 101 0/0 3d2h
  C Direct 10.1.33.0/24, Vl 33 0/0 00:13:51
  C Direct 192.168.103.0/24, Vl 103 0/0 3d1h

  Battery Switch MXL
  Ping result message
  192.168.103.13 fail
  10.1.32.21 success
  10.1.33.10 success

  192.168.103.13 - default gateway is 192.168.103.1
  Ping result message
  192.168.103.1 success
  192.168.103.11 success
  10.1.32.1 success
  10.1.32.21 fail
  10.1.33.1 fail - 192.168.103.1 inaccessible Destination network

  10.1.32.21 - default gateway is 10.1.32.1
  Ping result message
  192.168.103.1 success
  192.168.103.13 fail
  10.1.33.1 success
  10.1.33.10 success

  10.1.33.10 - default gateway is 10.1.33.1
  Ping result message
  192.168.103.1 success
  192.168.103.13 fail
  10.1.32.1 success
  10.1.32.21 success

  I have my hosts on my different threads pointed to the stack for their default gateways, and I want my MXL battery to switch packets at layer 3 connectivity between subnets.  The part which I stem is why is my vlan 103 does not communicate?  I can't even he ping of the MXL battery that has the vlan on it.  This should be the easiest thing in the world, but it is a failure.  Someone has an idea?

  I am pleased to hear that the routing has started working. I agree, it seems strange that would not work one day and then work the next day. Were all devices removed or added to the network between the two days? Or any small changes to config?

  To remove a configuration you issue clear config

  http://www.force10networks.com/CSPortal20/TechTips/0080_HowDoISaveMyConfiguration.aspx

  The latest firmware is 9.3.0.0. Which provides overall improvements and would be calling and updated.

  iSupport portal (Web): http://www.force10networks.com/support/
  E-mail: [email protected]
  Phone (USA and Canada): 866-965-5800
  Phone (International): + 1-408-965-5800

  Can monitor to see if the problem back to the top again.

• 2504 and 3802i new installation does not

  Hello

  I installed a new WLC 2504 and new APs 3802i, however the APs are not fully functional. They keep cycling the RED/GREEN/BLUE LED, which I don't see in the troubleshooting guide. WLC running 8.3.102.0, APs connect, take a license, but none of the radios come and he can't even see 2.4 Ghz I installed 5508 s front and WiSMs and did not have this problem with 1252/1142/2602 APs. Don't know what the hell miss me, and hoping that the group can help out me. TAC was told that they do not receive enough power that is a scripted response. Watch controller PoE as PoE/power. I had to install a device on the controllers pack? I went from 8.1.115.0 (plant) right to 8.3.102.0 because the 115 does not support the 3802 s.

  Summary of access points

  Total   Upward   Down   802.11A/n/AC radio   In detail 802.11b/g/n Radios   In detail Dual-Band radio   In detail All APs   In detail

  3800 require PoE + (802.3at) to operate. Because you got a line card PoE will not work correctly. See below for the required power for 3800 series.

  http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-3/b_cisco_aironet_series_2800_3800_access_point_deployment_guide/b_cisco_aironet_series_2800_3800_access_point_deployment_guide_chapter_01010.html

  Not sure what you want for a console output, so I posted AP run-config and show log:

  If you have a complete when console output AP trying to register, we can see exactly the problem at hand. Even with the limited log messages you can see is the negotiation of PoE has failed. If you have any PoE switch + you can confirm a 3802 works without any problem. In this way, you can confirm the problem with PoE HTH Rasika * Pls note all useful responses *.

• ESXi-&gt; Cisco 3850-&gt; router upstream routing does not

  Please see the attached diagram.

  I currently have the installation of "router on the stick" and I move to lass on Cisco 3850 battery. Initially, I moved VLAN100.  I can ping to each of the directly connected devices (i.e. the router 3850 and 2911). I can't do a ping to a virtual machine on vlan 100 router and vice versa. Here's what works what doesn't work.

  Work in both sense

  VM (172.16.100.51) <->GW on IVR (172.16.100.254)

  VM (172.16.100.51) <->an another IVR (172.16.230.254)

  VM (172.16.100.51) <->Int L3 on 3850 (10.2.2.2)

  L3 on 3850 (10.2.2.2) int <->int L3 on 2911 (10.2.2.1)

  SVI on 3850 (172.16.100.254) <->int L3 on 2911 (10.2.2.1)

  Does not not in both directions:

  VM (172.16.100.51) <->L3 interface on 2911 (10.2.2.1)

  VM (172.16.100.51) <->else NOT routed on 3850

  I have following routes on 2911 and 3850.

  3850:
  IP route 0.0.0.0 0.0.0.0 10.2.2.1

  2911:

  IP route 172.16.100.0 255.255.255.0 10.2.2.2

  IP route 172.16.230.0 255.255.255.0 10.2.2.2

  If in theory everything that comes from 172.16.100.51 no 3850 premises must be sent to 10.2.2.1 since it is the default route on 3850.

  I suspect that this is a problem with the license. I have IP Base feature set stack license 3850. I have checked using the license to show and display the version controls.

  According to this FAQ Cisco, http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-3850-..., routing should work because I do not have more than 16 static routes and I'm only using base L3 routing features.

  I am at a loss here. What is going on? Can someone please confirm?

  I bought WS-C3850-24 t-S,

  http://www.Cisco.com/c/en/us/TD/docs/switches/LAN/catalyst3850/software/...

  thinking that I would be able to use Lass and keep all traffic to get into the routers as switches upstream of our most ancient were only L2.

  It looks like an upgrade for all IP Services features is possible.

  https://cisco3850.wordpress.com/2015/04/22/licensing-for-cisco-catalyst-....

  That I have to upgrade the image so or can I just pass the license using the built-in commands described here.

  http://www.Cisco.com/c/en/us/TD/docs/switches/LAN/catalyst3850/software/...

  I hope that I don't have to reboot switches because this configuration is currently using this stack as the core and distribution.

  Any help is appreciated.

  Thank you

  Turning and the "IP routing" did?

• Apple AirPrint works Linksys E1000 - does not RV-220W

  As said subject line - have a linksys E1000 unit which the AirPrint service works anywhere wireless iPhone - iPad and Mac Books, when printing on an Epson Workforce 545 wireless printer. States of firmware to be updated on the Epson.

  Recently replaced the E1000 with a unit of RV-220w and get "no printer found" on iphones - ipads. Work on MacBook Air unit.

  Hello discovery service is enabled on the RV220w - active feature WMM on the SSID (by article I read) - IGMP enabled by another article I read, still does not.

  Have re-installed the E1000 as temporary until I can find a solution on this issue. If someone has any suggestions, would be appreciated. Very little info, go the route of google search. TIA

  halmillett,

  Go to the Wireless-> basic settings. Check if "Wireless Isolation in SSID" is enabled. If so, disable it and try to print wireless. If this does not work, try to connect the printer to the router with an ethernet cable temporarily and a test. I use a RV220W at home with a Brother wireless printer and it works perfectly since all devices Wi-wired and wireless.

  Everything is on the same VLAN?

  Just reply with the results.

  -Marty

• Regular disk defragmentation does not intervene. Computer can be in mode "sleep" during the defragmentation?

  Disk defragmentation. will take place every week at 01:00.  Computer is in "standby" at that time.  Is this why disk frag does not happen every week?  When I defragment manually I have to confirm the status of administrator... it would have something to do with it?  I use Windows 7 Home Premium.

  Hello Lauren,

  Thanks for posting your query in Microsoft Community Forum.

  You did it any significant hardware or change software on the computer before this problem?

  I understand that disk defragmentation does not work as expected. When this works even if your computer is in "sleep". Therefore, I would suggest trying the following steps and check if the problem persists.

  Method 1:

  Step 1: Check if the Disk Defragmenter service is running.
  a. click Start and type services.msc in the search box.
  (b) in the Services window, double-click the Disk Defragmenter service.
  c. check if the Disk Defragmenter service is set to Automatic Started .

  Step 2: The question may arise also because of the intervention of third-party software. So, I suggest clean boot of the system and check if the scheduled defragmentation works.

  How to perform a clean boot in Windows
  http://support.Microsoft.com/kb/929135

  Note: See "how to reset the computer to start normally after a boot minimum troubleshooting" to prepare the computer to start as usual after a repair. "

  Method 2:

  Try to set the Defragmenter to wake up the computer from the mode "sleep" and check if it works.

  1. Click Start, type taskschd.msc and press enter.
  2. In the left pane, click the arrow next to the Task Scheduler Library, Microsoftand Windows to expand the folders.
  3. Click the defrag folder.
  4. In the center pane, right-click on ScheduledDefrag and click Properties.
  5. Click the general tab.
  6. Check the box run with the highest privileges .
  7. Click the Conditions tab.
  8. Check the box to enable the computer to run this task and click OK.
  9. Close Task Scheduler.

  Check if the Defragmenter works to wake up the computer from the mode "sleep" as expected.

  If Disk Defragmenter does not at all, then we can see the post from Bill R TechSpec responded on 19 May 2011 in the following thread.

  http://answers.Microsoft.com/en-us/Windows/Forum/Windows_7-performance/Windows-7-Disk-Defragmenter-does-not-work/87965977-1252-E011-8dfc-68b599b31bf5

  Hope this information is useful. If the problem still persists, please post back for further assistance, we will be happy to help you.