Tag Archives: Controller

Domain Replication Issues – Fix Replication Issues

Posted on by

Fix Replication KB ID 0000301

Problem

You have one or more domain controllers in your Windows domain that is not replicating to one or more replication partners.

Fix Replication Issues: Solutions

Fix Replication Issues Step 1 DNS First!

Before you start make sure all the domain controllers are pointing the PDC emulator ONLY for their DNS settings.

1. On the PDC emulator > Start > run > dnsmgmt.msc {enter}.

2. Expand _msdcs.yourdomainname Right Click it > Properties > Set Dynamic updates to “Secure and non secure” > apply > OK.

3. Expand your-domain-name > Right Click it > Properties > Set Dynamic updates to “Secure and non secure” > apply > OK.

4. Right Click the Server-name above > All Tasks > Restart.

5. Expand _msdcs.your-domain-name again.

6. There should be a long GUID number there for each domain controller {an Alias (CNAME) entry}.

7. Delete them all (DONT delete the name server entries, or the SOA record!)

8. On each domain controller restart the netlogon service.

9. Back on the PDC emulator close and re-open the DNS management console.

10. Ensure those GUID entries have recreated (Note: You may need to apply the cup of coffee rule).

 

Domain Fix Replication Issues Step 2 Remove and recreate the Server replication Links

Start on the PDC emulator and repeat the process on all successive domain controllers.

1. Start > Administrative tools > Active directory Sites and Services.

2. Expand each server down to the NTDS settings.

3. Delete all the <automatically generated > entries and any manual ones so the right hand window is empty, (leave this window open). THIS IS SAFE DON’T PANIC.

4. Start > run > adsiedit.msc

5. Expand > Configuration > Expand “cn=configuration,dc=domainname” > Expand “cn=sites”.

6. Expand your site name i.e. “cn=default-fist-site-name” > Expand “cn=yourservername”.

7. Expand “cn=ntds settings”.

9. In the right hand window delete all the entries. Note: your previous actions should have already removed any possible entries from here, so don’t panic if there’s nothing here to delete!

Remember to do this this for ALL domain controller NTDS Settings containers!

10. Start > run > cmd {enter}.

11. Issue the following command.

[box]Repadmin /kcc [/box]

12. Switch back to Active directory Sites and Services > Right click NTDS settings on the server you are working on.

13. Select “All Tasks” > “Check replication Topology”.

Note: Your dialog prompt may be worded slightly differently to this one, that’s fine.

14. Right Click “Sites” at the top of the tree and select refresh.

15. Drill back down to the Servers NTDS Settings and then try to right click the connector on the right and “Replicate now”.

  1. Once everything is healthy go back to the two DNS zones we altered above, and change the properties back from Secure and Unsecure updates, to Secure updates ONLY!

Fix Replication Issues: Possible errors

Domain Replication Issues Possible Error 1 Target Principle Name is incorrect.

Cause: Either when attempting a manual domain replication or trying to access a resource on another machine.

1. If you are on a domain controller stop and disable the Key Distribution Center Service and stop it.

2. Start > Run > cmd {enter}.

3. Issue the following command;

[box]netdom resetpwd /s:server /ud:domainadministrator /pd:password123 {enter}.[/box]

Where</br server=name of the PDC emulator domain = your domain name password123=the domain administrators password.

4. Reboot the Server.

5. If it’s a domain controller restart the Key Distribution Center service and set its start-up to automatic.

6. Retry replication.

 

Domain Replication Issues Possible Error 2 The RPC server is unavailable.

The time on both the domain controllers may be out of sync

1. Start > run > cmd {enter} > Issue the following command;

[box]net time pdc-servername /set /y[/box]

2. If it gives you a permission error the carry out the procedure under “Target principal name is incorrect” above to reset the machine password.

Ref: http://support.microsoft.com/kb/257187

Fix Replication Issues Possible Error 3 The time between replications with this source has exceeded the tombstone lifetime. Replication has been stopped with this source.

Cause: Replication has been offline for a long time.

1. Start > Run > regedit {enter}.

2. Navigate To:

[box]HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNTDSParameters.[/box]

3. If the registry entry exists, modify it; otherwise create a new DWORD value by right-clicking Parameters.

4. Type Allow Replication With Divergent and Corrupt Partner and press Enter.

5. Double-click the entry and for the Value data type 1, then click OK.

6. Locate the “Strict Replication Consistency Key” change its value from 1 to 0 (zero).

6. Close the registry editor. You do not need to reboot after this change.

7. Retry Replication

Fix Replication Issues Possible Error 4 The destination server is currently rejecting replication requests.

Cause: Sometimes (usually after many failures) A DC will stop accepting replication.

1. Start > Run > cmd {enter}.

2. Issue the following commands;

[box]

repadmin /options your-server-name +DISABLE_OUTBOUND_REPL
repadmin /options your-server-name -DISABLE_OUTBOUND_REPL
repadmin /options your-server-name +DISABLE_INBOUND_REPL
repadmin /options your-server-name -DISABLE_INBOUND_REPL

[/box]

Fix Replication Issues Possible Error 5 This object may not exist because it may have been deleted and already garbage collected.

1. Start Run Regedit

2. Navigate to;

[box]HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNTDSParameters[/box]

3. If “Strict Replication Consistency does NOT exist > Click Add Value on the Edit menu > Add REG_DWORD > Strict Replication Consistency

4. Value data: If the value is 1, change it to 0.

Fix Replication Event ID Errors

Event 1388 or 1988 (A lingering object is detected).

1. Start > run > cmd {enter}

2. Issue the following command;

[box] repadmin /removelingeringobjects [/box]

Event ID 1113 and 1115 the destination server is currently rejecting replication requests.

1. See Possible Error 4 Above

When the problem has been rectified

Finish up by performing a Metadata cleanup on Active Directory

Remove Failed DC from Active Directory

Related Articles, References, Credits, or External Links

NA

NetApp – Four-Post Rail Kit

Posted on by

KB ID 0001007 

Problem

I’ve never really worked with NetApp equipment before, but today we had to rack a lot of DS2245 shelves, DS4246 shelves, and an FAS6250 controller. Every single one of these had the same rail kit.

After much swearing, and inserting and removing of cage nuts and bolts, someone committed the cardinal sin of actually reading the instructions. What he discovered was you don’t fit the cage nuts to the rack!

Solution

1. Yes, the cage nuts need to be INSERTED INTO THE RAILS. In the mounting kit you will find TWO TYPES of cage nuts (M6 and M5), they are labeled. Use the M5 cage nuts (they have an M5 engraved into the side of them). For the DS2245 and DS4246 shelves insert them like this.

Note: For the FAS6250 Controller, the cage nuts go in the opposite way round, like so

2. You can also insert cage nuts into the back of the rails, or fit them into the rack, (as normal).

3. To fit the rails into the rack use the bolts with the ‘thinner’ head. (Note The other M6 bolt in the kit wont fit, but if you have some M5 cage bolts kicking around DONT USE THEM, use the ones in the mounting kit.

4. Fit the rails into the rack, use bolts top and bottom at the front, and use all four at the back of each rack rail. Do not use screw collars.

5. At this point work out where the cage nuts need to be placed into the rack above the rail so when the shelf/controller is inserted into the rack the holes line up.

Note: This procedure may seem a little ‘odd’. Fitting nuts into rails is not something I’ve ever had to do before, but it works because the equipment has space to allow for the screw head like so;

 

Related Articles, References, Credits, or External Links

NA

Setup and Configure HP Wireless E-MSM720 Wireless Controller with HP E-MSM430 Access Points

Posted on by

KB ID 0000692 

Problem

We got some ‘demo stock’ in the office this week, I don’t do a lot of wireless, so I thought I would get it setup and have a look to see how easy/difficult it was.

Hardware used

HP E-MSM720 Premium Mobility Controller (J9694A)
HP E-MSM 430 Wireless N Dual Radio Access Point (J9651A)
HP HP 2915-8G-P-o-E Switch (J5692A)

The switch and controller are ‘tiny’ so if you want to put them in a cabinet you will need some ‘big brackets’, (or a shelf). I was disappointed that the controller didn’t have PoE on it (hence the reason we were supplied the switch). I was also disappointed the Access Point didn’t come with a network cable (seriously these things are pennies – and if a client buys hundreds of these things, someone will forget they also need an equal amount of network cables). In addition they are PoE, so you don’t get a power cable (or power injector) – so you cant even power them on without the network cable. That said all the gear is typical good quality HP Stuff. The documentation consists of a “quick setup sheet” for each piece of hardware and all the manuals are Online. I’m not a fan of manufacturers documentation at all, and HP’s is the same as most major vendors, to long, too complicated and to difficult to find what I’m looking for – I spent half a day reading pdf documents just trying to get the guest network working (a feat I will accomplish below with about three sentences and the same amount of pictures!)

Also See: Manually Configuring HP Wireless (MSM 720 controller) for Public and Private Wireless Networks

Solution

Initial Setup E-MSM720 Wireless Controller

1. Connect the controller to your network (Note: Don’t use the two dual personality ports 5 and 6).

2. The controller sets itself up on 192.168.1.1 put yourself on the same network range (see below).

3. Connect to https://192.168.1.1.

4. The MSM720 Default username and password are both admin.

5. Accept the EULA > Skip Registration > Set country > Save > Set the new password > Save.

6. Configure Initial Controller Settings > Start.

7. Set System name > Location > Contact > Login Message > Next > We’ve just set the Password so leave it blank > Next.

8. Enable/disable management interfaces > Next > Configure the network interfaces > Next.

These are allocated as follows, (out of the box!)

And are controlled by these two settings,

9. Set the time and timezone > Next > Apply.

Configure a Corporate WLAN with the E-MSM720 Wireless Controller

1. If not already there, select ‘Automated Workflow’ > Configure a wireless network for employees > Start.

11. Create an SSID > Next > Set the WPA Key > Next.

12. Choose what access points to apply these settings to > Next > Apply.

Note: At this point I had not powered on or touched the access points, so I just selected ‘All’.

Configure a ‘Guest’ WLAN with the E-MSM720 Wireless Controller

I had a nightmare getting this running, until I fully understood the VLAN, IP address and interface allocation, but if you set things up as specified above it will just work.

1. Automated Workflows > Create a wireless network for guests > Start.

2. Create and SSID > Next > Configure guest authentication (or leave open) > Set IP Settings for clients > Next.

3. Select APs to apply to > Next > Apply.

Setup the HP E-MSM 430 Wireless N Dual Radio Access Point

Well you have already done all the work! Simply connect the AP to a POE capable network outlet.

By default the AP is in ‘Controlled’ mode, so it will start looking for a controller as soon at it powers on, it can take a little while to boot (go get a coffee), you will see it appear in the controllers web interface when its pulled its configuration down.

Updating Firmware MSM70 and MSM430

Very slick! update the firmware package on the controller, and it will update all the access points for you.

Final thoughts

This is good quality gear, it has built in support for IPSEC, SSL, RADIUS and a myriad of other features that you would expect to find on an enterprise class wireless solution. HP might be concerned by their lack of wireless sales, but they could make the experience with these things better by making the web interface easier to navigate, (ask someone who has never used it before to delete a wireless network! – over 90 minutes it took me to locate the VSC bindings section to remove that!) I’ve already mentioned the documentation, I appreciate that it needs to be comprehensive but come on!

Related Articles, References, Credits, or External Links

HP E Series Wireless – Cannot Access Local LAN

Manually Configuring HP Wireless (MSM 720 controller) for Public and Private Wireless Networks

 

Change HP Wireless Access Points from Autonomous to Controlled Mode

Posted on by

KB ID 0000853 

Problem

I had a client this week who was putting in an MSM730 Wireless controller, and a few MSM460 Access Points. They already had an MSM460 in their meeting room, and I was asked to add that into the new setup on the controller as well.

Out of the box the access points are in controlled mode (look for a controller), if they don’t find one they assume they are in autonomous mode and either setup on 192.168.1.1 or get an address from DHCP (In the DHCP scope you will see the serial number of the AP as the name).

That’s great, but if you have deployed an AP in autonomous mode how do you change it back?

Solution

1. The Controller itself can still see the Access point(s) it puts them in the Autonomous APs section. You can also find the IP address the AP is using here as well.

2. Connect directly to the APs web console and log on (the default username and password is admin and admin).

Note: If you have forgotten the username and password you will need to hit the reset button on the back of the AP until the lights flash three times.

3. Navigate to Maintenance > System > Switch to Controlled Mode

Warning: This drops all the settings on this AP if you need them documents them first.

Related Articles, References, Credits, or External Links

Manually Configuring HP Wireless (MSM 720 controller) for Public and Private Wireless Networks

 

HP MSM Controller – Access Points Stuck ‘Waiting Acceptance’

Posted on by

KB ID 0000868 

Problem

When viewing the Controller > Controlled APs, You may see some of them stuck with a ‘Waiting Acceptance’ status.

Solution

This happens because the Access Point can contact the controller, (otherwise you wouldn’t even see it). But the controller cant get traffic back to the access point, to update its firmware, or to synchronize it. The root cause of this is usually because this access point is on another subnet that the controller cant get to.

1. Navigate to > Home > Network > IP Routes.

2. Add an ‘Active Route’ for the subnet the remote network the AP is on (in this example 10.3.0.0/16), and the gateway the controller needs to send the traffic to to get there, (in this example 10.1.0.254).

3. Apply the cup of coffee rule.

4. Remember before you can Synchronize it you will need to select the AP and ‘Authorize Locally’

Related Articles, References, Credits, or External Links

NA

 

HP MSM765zl and 775zl – Initial Setup and Routing

Posted on by

KB ID 0000917 

Problem

The MSM 765zl and 775zl, unlike the rest of the HP MSM controller series, do not have any physical Ethernet ports on them.

So before you can get to its web management interface, you need to be able to give it an IP address, and then the controller needs to be able to find a route back to where you are, assuming you are not on a flat unrouted/single VLAN. Obviously if you are directly connected to the same network segment then you can set the devices ‘default route’ from the web management console.

Solution

1. Connect to the chassis that the controller is in, either via telnet or console cable. As I outlined in an earlier article you need to find the controllers slot letter and index number with a services command. (If you are sat in front of the switch the slot letter should already be known!)

2. Now, connect to the MSM directly and give the controller its LAN and WAN IP addresses.

Note: HP call them LAN and WAN interfaces, (I know it’s confusing), the WAN interface does not have to connect to the WAN it only points in that direction. I’m assuming it’s a throw back from when these devices were developed by Colubris.

[box] CORE-SW# services F 2
CORE-SW(msm765-aplication-F)> enable
CORE-SW(msm765-aplication-F)# config
CORE-SW(msm765-aplication-F)(config)# interface ip wan
CORE-SW(msm765-aplication-F)(config-if-ip)# ip address 192.168.1.1/24
CORE-SW(msm765-aplication-F)(config-if-ip)# ip address mode static
CORE-SW(msm765-aplication-F)(config-if-ip)# end
CORE-SW(msm765-aplication-F)(config)# interface ip lan
CORE-SW(msm765-aplication-F)(config-if-ip)# ip address 10.254.0.100/16
CORE-SW(msm765-aplication-F)(config-if-ip)# ip address mode static
CORE-SW(msm765-aplication-F)(config-if-ip)# end
[/box]

3. Now if you are on the same network (or VLAN) as the controller, you should be able to connect to the web management console. If not you will need to do two further steps

a) Connect the TWO virtual ports of the MSM to the correct VLANs on the switch.

b) Add a route back to the network you are on, either by setting a default route (if there is only one) or a static route.

Connect The Two MSM Virtual Ports

At this point the MSM blade can be treated like any other blade with Ethernet ports on it. Above we found out the blade was in slot F, so the ports with show up on the chassis switch as F1 and F2.

Port number 1: Is the WAN/Internet port
Port number 2: Is the LAN port

At the very least the WAN port should be in a different VLAN like so;

[box]

CORE-SW> enable
Password xxxxxxxx
CORE-SW# configure terminal
CORE-SW(config)# vlan 210 name WifiLink
CORE-SW(config)# vlan 210
CORE-SW(vlan-210)# untagged F1
CORE-SW(vlan-210)# exit
CORE-SW(config)#

If all your LAN traffic is on VLAN 1 (which is the default), then the MSM LAN port will already be untagged in VLAN 1. If not you will also need to present the MSM LAN port to the LAN VLAN.

CORE-SW# configure terminal
CORE-SW(config)# vlan 10 name LANTraffic
CORE-SW(config)# vlan 10
CORE-SW(vlan-10)# untagged F2
CORE-SW(vlan-10)# exit
CORE-SW(config)#

[/box]

Adding Default and Static Routes to the MSM controller.

The controller needs a default route, or it will not be able to send traffic out of the local LAN. In a simple flat network that should be all that you need. But if you have multiple network segments (or VLANs), then it will also need a static route adding for each of these. This is important for both access to the web management console, and because your wireless access points need to be able to speak to the controller! If your wireless access points are on a different network you may need to follow the article below to let them know where the controller is.

Register HP Wireless Access Points With an HP MSM Controller on a Different Subnet

[box]

CORE-SW# services F 2
CORE-SW(msm765-aplication-F)> enable
CORE-SW(msm765-aplication-F)# config
CORE-SW(msm765-aplication-F)(config)# ip route gateway 0.0.0.0/0 192.168.1.254 1

If you need to add additional routes the syntax is the same as above.

CORE-SW(msm765-aplication-F)(config)# ip route gateway 10.100.0.0/16 10.254.0.254 1
CORE-SW(msm765-aplication-F)(config)# ip route gateway 10.200.0.0/16 10.254.0.254 1

[/box]

Now you should be able to connect to the web management console and configure your wireless networks, this process is identical to configuring the physical controllers, like the MSM 720 see the link below.

Manually Configuring HP Wireless (MSM 720 controller) for Public and Private Wireless Networks

Related Articles, References, Credits, or External Links

NA