DHCP scope increase and changes in wlc

hi,
i am using wlc 4402 with a mgt ip 172.26.150.x/24 and ap manager ip 172.26.150.x/24, my all ap get the ip address from dhcp . currently in dhcp server 172.26.150.3 to 254 dhcp scope is configured. at mysite some devices are configured like ipad,iphone or galaxy tab with mac binding in dhcp server. now this pool is almost full. i have a policy configured for these devices for mac binding is done in DHCP. to increase pool what are the changes i need to do in wlc. what are the changes i need to do in dhcp server . is policy made for mac binding in dhcp server will get affected by this ?
regards
rajat

Hi Rajat,
Use a /23 range ip address rather than using 172.26.150.x/24. So at first this change need to be carried out on the L3 device (which will the default gateway of the WLC managment interface). Accordingly the AP managment ip and ap manager ip's subnet mask is going to change from /24 to /23.
Then ensure that on the dhcp server you expand the scope from /24 to /23. This is will not affect the MAC bindings as long as you are using the same ip range with a different subnet mask.
Hope that helps
Regards
Najaf
Please rate when applicable or helpful !!!

Similar Messages

Getting "Error in setting DHCP Scope Network and Netmask"

Hello Cisco Experts - I'm trying to setup a new DHCP scope on my Cisco 2504 and am getting the error referenced above. Here are the settings I am using:
I have another range setup in exactly the same way only it runs from 10.35.209.65 through 10.35.209.90. Can anyone point me in the right direction for what I'm doing wrong? Thanks in advance!

Good question.
Here is the screeshot of the scope I just activated:
What IOS Version are you running? I have 7.4.100.0 on mine.
Please Rate Helpful posts and mark this question as answered if, in fact, this does answer your question. Otherwise, feel free to post follow-up questions.
Charles Moreton

Multiple DHCP scopes on WLC 5508 (not showing leases?)

I have 2 DHCP scopes set up on a wlc 5508, one for the AP's and another for a wlan, the leases for the AP's scope show up, but the one that the clients on the WLAN are on do not show up in the "show leases" is that a bug? normal?

Customers using Cisco Unified Wireless solutions have been reporting issues with the DHCP support provided on the Wireless LAN Controller (WLC). Some of these issues are software bugs or debugability problems. Others are due to lack of proper understanding on the DHCP implementation.
This document describes the different DHCP operations on the wireless controller, which provides consistent and accurate information to customers in an effort to reduce the related customer issues and TAC cases.
Please refer to the following link: http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/110865-dhcp-wlc.html

Monitoring DHCP scope on WLC 5508

Hi,
I have DHCP configured on the anchor controller but I don't know when DHCP scope is full on it. Do you have any idea or experience how to monitoring exhausted DHCP scope on WLC 5508?
Regarding

Ok but WLC can send syslog messages and base on this we can create an alarm. When DHCP scope is full on the WLC then controller inform us about this:
DHCP Server: Nov 13 11:34:56.321: %DHCP-3-SEND_OFFER_FAIL: dhcpd.c:278 Unable to send DHCP offer. Could not allocate appropriate ip address from the scope
*DHCP Server: Nov 13 11:34:56.321: %DHCP-4-ADDR_NOT_ALLOCATED: serverpacket.c:205 No IP addresses to give -- OFFER abandoned -- packet dropped
*DHCP Server: Nov 13 11:34:52.416: %DHCP-3-SEND_OFFER_FAIL: dhcpd.c:278 Unable to send DHCP offer. Could not allocate appropriate ip address from the scope
*DHCP Server: Nov 13 11:34:52.416: %DHCP-4-ADDR_NOT_ALLOCATED: serverpacket.c:205 No IP addresses to give -- OFFER abandoned -- packet dropped
so If only I could detect this sentence from the syslog messages than I could create an alarm.

Ip source guard feature and dhcp DHCP scope exhaustion (client spoofs other clients)

Hi everybody.
A dhcp server assigns ip adress based on mac address carried by client hardware field in dhcp packets.
One potential attack is when a rogue host mimics different mac addresses and causes dhcp server to assign the ip addresses until no ip address is left for legitimate host.
For e.g a host h1 with mac1 has assigned ip address by dhcp server as:
199.199.199.1 mac1
Dhcp server has the above entry in its database.
Using hacking tools such as Yersinia or Gobbler one can create a dhcp discover messages each time creating a different mac for client hardware field in dhcp server thereby causing a dhcp server to assign ip addresses because to dhcp server , these are legitimate dhcp discover messages with each carrying a different mac in client hardware addresses.
You might say use dhcp snooping and it will prevent that ( dhcp scope exhaustion) and configure the switch to check if src mac matches the client hardware address in dhcp message. But still we can creat spoofed discover messages where src mac in ethernet header will match the client hardware address in dhcp discover message. We still did not overcome the problem.
You might say use IP source guard feature but will it really prevent that problem from happening?
Let me illustrate it :
h1---------f1/1SW---------DHCP server
Let say we have configured dhcp snooping on sw1 and f1/1 is untrusted port. The switch has following dhcp binding
199.199.199.1    mac1   vlan1 f1/1
Next we configure ip source guard to validate both src mac and src ip against the dhcp bindings . When we configures ip source guard first , it will allow dhcp communication only so a host can request ip address and a dhcp binding can be built. After that ip source guard will validate src ip or src mac or both against the dhcp binding.depending upon how we configure ip source guard.
In our case we have configured ip source guard to validate both src mac and src ip against the dhcp binding.
A dhcp binding is already created as:
199.199.199.1 mac1 vlan 1 f1/1
Now using the hacking tools Yersinia or Gobbler on h1, we create our first spoofed dhcp discover message where src mac=mac2 in ethernet header and client harware address= mac2 in dhcp discover message. Since switch is configured with ip source guard feature and therefore allows dhcp discover message to pass through. Dhcp server upon receiving the dhcp message assigns another ip address from the pool. Now the dhcp server has following entries:
199.199.199.1 mac1
199.199.199.2 mac2.
We can continue to craft spoofed dhcp discover messages as mentioned above and have dhcp server keep assigning ip addresses until the whole pool is exhausted.
So my question is how does ip source guard in conjuction with dhcp snooping prevent this particular attack from happening? ( i.e DHCP scope exhaustion)
I really appreciate your input.
thanks and have a great week.

Thanks Karthikeyan.
First of all, we gather all the information about the locations of legitimate dhcp servers in our network. Once we have this information, we will configure the ports used to reach them as trusted. All the ports where end users will connect will be untrusted and therefore subject to dhcp snooping .
it means if any of user connected in that switch/vlan runs a dhcp services like vmware for eg. Snooping will prevent the dhcp/bootp servers connected to that port will not be able to process.
Yes that is correct. Because dhcp snooping feature will check these ports for the messages usually sent by dhcp server such as dhcp offer, etc. If the end user is running dhcp server using virtual machine, that port should be configured as trusted if it is dertermined that end user is running a legitimate dhcp server using vm ware.
When we have the dhcp snooping it prevents the 1st level of hacking itself. I don't think so it will have any impact on dhcp address releasing.
I am sorry. You lost me here. What is 1 level of hacking?
Dhcp snooping checks for dhcp messages such as dhcp release, dhcp decline.on untrusted port against the dhcp bindings.
Here is why;
h1---------SW1-------dhcp server
               |
             h2
Let say we don't have dhcp snooping in above attack and h2 is a legitimate user has already assigned ip address 199.199.199.2 by dhcp server. Thus the dhcp server has an entry:
199.199.199.2 mac2
Next we connect rogue user and it gets ip address 199.199.199.1 now the dhcp server has entries:
199.199.199. 1 mac1
199.199.199.2   mac2
Now using hacking tools, h1 create a fake dhcp release message with 199.199.199.199.2   mac2
Dhcp server upon receiving this message, will release the ip address and returns it to the pool.
By using DHCP snooping, switch will peer inside dhcp release message and checks against the binding. If there is conflict, it will drop the message.
IFor e.g
If have dhcp snooping configured , then switch will have adhcp binding as:
199.199.199.1    mac1    vlan 1   f1/1 lease time
199.199.199.2     mac2    vlan 2    f1/2 lease time.
If h1 tries to send fake dhcp release with ip address 199.199.199.2    mac2
Switch will check ip address 199.199.199.2 and mac2 against the binding related to f1/1 . Sw will find a conflict and therefore drops the dhcp release packet.
Thanks

Is there a way for internal DHCP Scope to release scope addresses when the wifi client has disconnected?

DHCP scope is configured on a WLC 5508.
I'm checking if there' a way for WLC to clear the dhcp leasing when a user is diconnected from wireless?

Unless the client sends a DHCP Release upon disconnect, which is not mandaded in the protocol, the lease will simply remain until it has expired. If you're concerned with running out of leases, you only have 2 options.
1. reduce the lease time of your dhcp scope
2. increase the network size to accomodate more usable addresses.
There isn't a way to force a DHCP address lease to be "cleared" from the WLC simply because the client was disconnected.

Clients unable to connect and get DHCP - LAP1142N AP and 5508 WLC

Hi,
I have 19 locations, each with 1 or more LAP1142N AP's in FlexConnect mode, AP's are primed using CAPWAP to my 5508 WLC at the datacenter. The AP's join the WLC without issue every time. I have two WLAN's, one guest and one staff, the guest network is open and obtains DHCP from a WatchGuard XTM33 firewall at each of the remote locations. The staff side is WPA2/RADIUS and DHCP is assigned from the WLC. Each AP is assigned a static IP that is not in the DHCP scope. For example: DHCP scope on the branch firewall is 192.168.1.10-250 the AP will be assigned static IP of 192.168.1.1.. The AP's are connected to a HP procurve switch that has a untagged VLAN, the firewall is using the native vlan 1 and so is the AP.
I have been running this network for over a year and it has not had a single issue until the last two weeks. Nothing on the network has changed or has been upgraded.
Now for the issue: The issue I am seeing is that clients are no longer able to connect to the AP and do not get DHCP assigned to them. I am able to get it working, if I remove the static IP from the AP, the AP will reboot, join the controller, then begin working, users can connect and DHCP is assigned from the firewall as it should. However, If the AP then reboots, the AP will join back to the controller but no clients can connect nor do they get a DHCP address. So, I then reassign a static IP to the AP again and it reboots, connects to the controller and clients then can connect and get DHCP.
Attached is a running config from one of the APs
I've found several posts on this topic, in fact the patch of unassigning or reassigning static IP is one that I found. However, I wanted to post this to see if there is any further assistance I can get on this. I am also waiting on my SmartNet to start up and will be contacting Cisco support as well.
Thanks for any help.

Alright, so I finally figured out the issue with this. I had a Mobility Anchor set on the guest WLAN and once I removed that all started working again.
What is Mobility Anchor?
A. Mobility Anchor, also referred to as Guest tunneling or Auto Anchor Mobility, is a feature where all the client traffic that belongs to a WLAN (Specially Guest WLAN) is tunneled to a predefined WLC or set of controllers that are configured as Anchor for that specific WLAN. This feature helps to restrict clients to a specific subnet and have more control over the user traffic. Refer to the Configuring Auto-Anchor Mobility section of Cisco Wireless LAN Controller Configuration Guide, Release 7.0 for more information on this feature.

Windows 2008 R2 DHCP scope change - Netsh Exec not working

OK, there seems to be a disconnect between Netsh documentation and how it actually works. We are in the process of re-addressing ALL our DHCP scopes (joys of a buy-out) and using the steps outlined in numerous MS articles and Blogs etc... we should
be able to use "Netsh dhcp server scope 192.168.1.0 dump > scope1.cfg" then modify the cfg file with the new scope address (i.e. change all 192.168.1. to lets say 10.10.5.). Then use netsh exec scope1.cfg (yes, the file modified) to
create the new scope which would contain all the "stuff" the current scope has (reservations, options, etc).
Well, all we get is the response "The following command was not found: |".
Environment is as follows:
Account is a domain admin
working on a RDP session on the DHCP server
Server is Windows 2008 R2 (current functioning DHCP server)
Using administrative CMD (elevated)
have tried changing context into Netsh | DHCP | Server and default CMD - all "no go"
supporting link from MS: http://technet.microsoft.com/en-us/library/cc772372(v=ws.10).aspx#BKMK_1
There's a lot of discussions around this, but I haven't seen any response that says how to actually do it. export/import won't work for us since we have to update the scope info. With almost 100 scopes to update, we really need this functionality!
(or similar method)
Any assistance would be greatly appreciated.

OK... It seems the issue is with the dump file. I actually got exec to run once with a dump file which wasn't modified.  The stupid part is it only ran one time, I could not duplicate it.   Since
I've beat this thing to death and no one could offer any assistance (Hello MS?), I'm not wasting any more time on it.   Luckily, I was able to figure out an alternate method.
Looking at the dump file I realized all the lines are just a straight NetSh commands, which means all I needed to do is grab the lines and preface them with NetSh. Like this...
for /f "tokens=*" %a in ('type scope.cfg ^| find /i "dhcp"') do NetSh %a
where scope.cfg is your dump file.   This runs perfect and seems to be the exact thing that exec should be doing. I did flip the "SET STATE 1" to "0" so the scope was deactivated (Don't forget to run it in an elevated
prompt).
Hope this helps someone else so they aren't spending days for nothing!

Client Authentication/Authorization via ISE & AD, Posture Registry Key, and mapped to specific DHCP scope by AD membership

Hi Team,
I'm currently working on a configuration entailing WLC and ISE where the customer wants a single SSID,and wants his wireless clients to authenticate successfully if they pass a registry key compliance. Additionally, they want clients to received a different IP address or get mapped to a different DHCP scope based on the Microsoft AD group they belong too. for example:
Client authenticating with registry key and in AD group ABC that passes authentication gets IP address or subnet for AD group ABC.
Client authenticating with registry key and in AD group XXX that passes authentication gets IP address or subnet for AD group XXX.
Clients---->WLC------>ISE-----> MS AD ( groups ABC, XXXX, YYY )
currently using EAP-PEAP/MSCHAPv2
Does anyone have any idea or pointers or can refer me somewhere that I can read on how to accomplish this? Not sure on how to do the registry compliance check nor what attributes will allow me to map the client to a DHCP Scope based on this AD group membership?
Thanks...

Do check cisco how to guides you will get step by step configuration of the current requirement

Internal DHCP scope for AP on WLC 7.0 (on diff subnet)

hi All,
I would like to know if it is possible to assign dhcp pool on a different subnet to the WLC management interface?
Eg: Management Interface is on 172.16.4.100 /24
I would like to use the WLC Internal DHCP to assign IP to my APs on the a different range 172.16.2.x /24
Is that possible?
I have tried assigning dhcp scope for the AP within the same subnet as the management interface and it works. But that is not my requirement
Apparently i need my AP to be sitting on a different vlan
please advise

No its not possible.. this works only if the AP and the WLC management interface is in the same subnet!! to ur issue we use something called as DHCP OPTION 43, google search DHCP OPTION 43 + cisco, the first link that u get wil help you!!
Please dont forget to rate the usefull posts!!
Regards
Surendra

DHCP scope in WLC.

hi all,
please any one confirm ,is it possible to configure the DHCP scope for APs in WLC ?
i am having 5508 controller connected to L3 switch..if it is possible what need to be done for that.
thanks in advance.
venkat

Hi Venkat,
WLC can lease IPs to APs only if we configure the pool in the same subnet as that of management interface.. having said that, its no possible to assign diff pool for AP which resides in diff subnet on the WLC.. We need to go for either Pool on the Layer 3 device or DHCP server.
IP MAC binding is already enabled on the WLC by default.. AFAIK, this is more usefull for PASSIVE clients rather to active
Lemme know if this answered ur question and please dont forget to rate the usefull posts
Regards
Surendra

WLC dhcp scope issue

Hi,
We are facing this problem
we are using guest SSID with captive portal authentication.
We are using below step to conect to network
1) User will click on guest SSID & get IP from DHCP scope
2) User will open google.com & then it will redirect to authentication page - we need to provide userid/pass & then we will able to access internet
Problem
Assume user only do Step -1 , Then My dhcp scope is utilizing
How can we restrict the same to 'geneuine' user, any option/workaround ?
br/subhojit

I have to agree with e. Shortening theeaae will help.
But the kny way to keep people off the WLAN would be to use a PSK so that only authorized users can get on.
HTH
Steve

DHCP scope full, event ID 1020

Hi, one of our Windows 2008 R2 Domain controllers is returning the following warning message on almost a daily basis:
Log Name: System
Source: Microsoft-Windows-DHCP-Server
Date: 19/11/2014 11:32:41 AM
Event ID: 1020
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: computername.domain.x.x
Description:
Scope, 10.x.x.0, is 83 percent full with only 39 IP addresses remaining.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
 <Provider Name="Microsoft-Windows-DHCP-Server" Guid="{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}" EventSourceName="DhcpServer" />
 <EventID Qualifiers="0">1020</EventID>
 <Version>0</Version>
 <Level>3</Level>
 <Task>0</Task>
 <Opcode>0</Opcode>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2014-11-19T00:32:41.000000000Z" />
 <EventRecordID>12980</EventRecordID>
 <Correlation />
 <Execution ProcessID="0" ThreadID="0" />
 <Channel>System</Channel>
 <Computer>computer.domain.x.x</Computer>
 <Security />
</System>
<EventData>
 <Data>10.x.x.x</Data>
 <Data>83</Data>
 <Data>39</Data>
</EventData>
</Event>
Upon review of Microsoft Support online, I found the following article which illustrates a few options:
http://support.microsoft.com/kb/255999/en-au
What would be the logical choice for us, having the 10.x.x network?
Ideally, it would be good not having to re-subnet anything if possible, or re-create the scope.
Would a scope extension require a reboot of the server? Never done this before, so thought I should ask.

Hi,
According to your description, my understanding is that DC prompts an warning event ID 1020, indicate 83% full with DHCP scope.
By default, the threshold value for firing of event 1020 is 80%. Estimate devices number, contrast with the number of IP address in this scope, if the percentage is less than 80%, you may try to reduce the lease duration and decrease the cleanup interval.
This can help to speed the reclaiming of expired scope IP addresses.
To reduce the lease duration:
1.At the DHCP server, click Start, point to Administrative Tools, and then click
DHCP.
2.In the DCHP console tree, right-click the scope you want to configure, and then click
Properties.
3.On the General tab, under Lease duration for DHCP clients, type the new lease duration.
To use a Netsh command to set the cleanup interval time:
1.At the DHCP server, click Start, click Run, type
cmd, and then press ENTER.
2.Type netsh dhcp set databasecleanupinterval <NewInterval> (where "NewInterval" is the amount of time in minutes between DHCP database cleanups).
As an existing DHCP scope, its subnet mask can’t be changed. If the Start Address and
End Address do not currently include all addresses for your specific subnet, you can increase the number of addresses in the scope by extending the
Start Address or End Address in the scope properties. This operation needn’t reboot.
If neither of above 2 suggestions is applicable, new a DHCP scope or reference
KB255999 (resubnetting and superscoping). At the same time, you need to change your network topology.
Best Regards,
Eve Wang

Fragents and Change Orders

I'm new to P3. I need to manage a large 2 year public
works building construction schedule in downtown Los
Angeles, with numerous and frequent changes to the
schedule due to change orders, RFI's etc. Of course, these
changes result in increases/decreases to cost and time,
which need to be monitored and dealt with as part of the
overall project. Some say that fragnets are the best way
to insert these changes into the schedule. Some say
fragnets are problematic. I have no experience with
fragnets and I want to get off on the right foot. What
have you project managers and project engineers found most
effective for inserting and managing change order and RFI
items?

Nat:
Thank you very much for
your response.
Your
explanation of fragnets was very useful. I will make a
point of saving and reusing repetitive groups of
activities. In my case, SOMD (slab-on-metal-deck) is
very repetitive. Also, exterior building finishes such
as plaster (exterior sheathing, lath, scratch coat,
brown coat, cure, finish coat, cleanup). Interior
finishes activities are also often identical from
floor to floor.
The issue with
RFI's is usually not so critical. I mentioned 1200
RFI's but relatively few impact the schedule and must
be coded in. But it is more than 48. In my case, the
most common reason for entering an RFI into the
schedule is when the
consultant/Architect/Engineer/State Agency exceeds the
contractually agreed upon time limit for response to a
design-related RFI, or his response is irrelevant
requiring a second round of RFI's to resolve the
problem (revise and resubmit for title-block
exceptions, for example, happens frequently). 
It is easy to ignore these delays,
and recording them in the schedule can really irritate
the consultant, but when they become a habit, the
cumulative impact on the schedule can be significant.
Therefore, I need to be able to track these RFI delays
effectively within the schedule. Of course, an RFI
always has a number that is tracked inside Expedition
as well.
The bigger problem is
Change Orders. As you know, when the Owner wants
something added to the work, or a problem in the
design results in an increase in the scope of work
(there are many other possible reasons of course) a CO
is requested. As a general rule, most change orders
contain both a cost increase as well as a time
extension. This time extension is the problem,
because, especially on public works projects, the
Owner/CM does not want to grant time an extension, and
even when they do, they will only grant it when it
impacts the critical path, and only after there is no
float remaining (you will see why this distinction is
important as you read further). The critical path
condition makes sense, but the idea that my float is
the Owner's to eat for his CO work is grating,
especially when facing potential LD's. 
To top it off, some Owners/CMs insist
that all time delays be dealt with at the end of the
project, when the actual time delay resulting from a
CO can be calculated, instead of simply estimated, as
is common practice (corresponding language is inserted
into the CO to that effect instead of a defined time
extension). My position is that if they refuse to
grant a time extension based on an estimate, then the
cost given in the CO, which is nothing more than an
estimate, should also be replaced with T&M, and
the budget be damned. Needless to say, that position
has not won me many friends in the trailer across the
way.
You might suggest that we
should refuse the extra work if a time extension is
not granted up front. If we did that, they would hit
our bond in a heartbeat. A contractor's lot in life
seems to be to make lawyers (Deo volente, may the burn
in hell) wealthy.
In the case
of the Owner/CM refusing to grant time for
non-critical path CO's, my position is that, while the
CO work may not be on the critical path this instant,
in many cases, the critical path can change
dramatically, sucking CO work into it that was
previously separated from it by weeks. That very thing
has happened on a school project located in a major
city we are doing.
The project
has extensive tubular secondary steel at the exterior
of the two buildings. This tube steel, ranging in size
from 4" diameter to 20" diameter curves around, and up
and down, the exterior of the structure. I do not
exaggerate when I say that it is more complicated than
a roller coaster. I will send pictures if you are
interested. It supports curvilinear LG framing, which
in turn supports a combination of plaster, brick
veneer and metal panels. Very phantasmagorical stuff.
Being a complicated 3-D arrangement of rigid steel,
the architect's drawings were incomplete, (we should
have expected that) and changed frequently (4 times)
during fabrication, resulting in detailing problems
and a two month delay in erection. Lots of unforeseen,
fit-scribe-cut-repeat of long, heavy, curved, twisting
pieces of long steel hanging from crane hooks has been
required.
We have recovered
most of that time, but only by doing a great deal of
out-of-sequence work.
As you
can imagine, this mess generated a ton of CO's, but
the Owner would not agree to grant time extensions
until the end of the project, and even then, only on
CO's that are provably on the critical path. When
combined with electrical changes impacting utility
buildings, cable pulls, elevators, manlift and even
exterior finishes, and then with added off-site work,
topped off by submittal-review delays by State
agencies, the critical path has flapped around like a
flag in the wind, with CO's going in and out of it. In
many cases, this means that a particular item of
ongoing CO work has delayed the critical path for a
period of time, but not for the entire duration of the
CO work. So calculating the exact impact of the CO
during the period it was on the critical path has not
been easy.
I anticipate there
will be huge disagreement about these calculations at
the end of the project when we have the "come to
Jesus" time/money resolution meeting with the
Owner/CM.
BTW, the CM always
insists that CO's be dealt with as fragnets, but that
doesn't always make sense because the nature of CO
work is often one-of-a kind, not repetitive stuff. But
he has fragnets on the brain, it seems, so we call
them fragnets to humor him.
 Anyway, as you can imagine, tracking the dynamic
(vs. static) effect of CO's on the schedule has been
difficult. I am almost tempted to try calculus methods
to calculate time consumed over time (if you get my
meaning). Any experience analyzing schedules using
differential equations? Someone must have done it
before....
Right now I am
using activity codes to track them, but I am wondering
if there is a better way.
 
I have other projects, without the
same delays, but similar Owner/CM mindset regarding
CO's
Now you know the long
story. Any suggestions?
 Stan

Scope of IDOC changes in hierarchies

Hi Guys
I want to know wthat is the scope of IDOC changes inhierarchie.
Nx, kiran

Hi Srinivas,
I would like to confirm some things. First your IDoc struc had field2 which is of length less than 132 and then you increased it to 132. Now you are now using WE19 to test your IDoc. The reference IDoc no. that you gave was the IDoc that had been generated while the length was less than 132.
If this is what you have done, then you will have this issue. I will tell you why. When you created the IDocs, this field was less than 132, then in the EDIDD-SDATA which is a character field of length 1000 bytes would have got filled with a different position.
Say for example you have two fields in a segmentthey are A(of lenght 10) and B(of length 20). When you create IDoc, EDIDD-SDATA(which actually contains data would have been like the following:
Say if A = 'ABC', B = 'DEF'
EDIDD-SDATA = 'ABC DEF '
If you see it carefully it is a string of charachter where A starts at 1st and B starts at 11th position of the string. Now you changed length of A to 15. Then A would start from 1st Position upto 15th position while B starts from 16th upto 35. Hence when the WE19 tool extracts data from EDIDD, it extracts it as:
A = 'ABC DEF '
B = space
Hope this answers your question.
Regards,
Srikanth
PS: Same will be the case with WE09 as well. The IDocs which was created before changing the length will still look distorted.
Message was edited by: Srikanth Lodd
Message was edited by: Srikanth Lodd

DHCP scope increase and changes in wlc

Similar Messages

Maybe you are looking for