Change Interface to Interface Group for WLAN

Hi Guys,
We have 2 WISMs here and one WLAN connected to interface "Int1" and they are working fine. For now, we want to expand the IP addresses of this SSID, so we created several VLANs as well as some interfaces in WLC and created a interface group to contain all the interfaces (includes to original "Int1"). When we tried to change the interface to the interface group under that SSID, we found that the clients lost the connection. We even tried to put only the "Int1" in the interface group. Is there any way to expand the IP addresses without network outage? Thanks!

Check the following link for proper interface grouping.
http://mrncciew.com/2013/02/27/configuring-dynamic-interfaces-on-wlc/
NOte:re-create and re-test the Int group with few Interface in the group and then add more.

Similar Messages

Change transaction type group for transaction type

Hi
Is it possible to change the transaction type group for a TTY.For ex i want to change for 270 and 151 -TTY GRP -32 and 33 respectively.As of now it is TTY grp is 25 and 10.I need to change this so that in Asset history sheet when i do ABT1N i want these values to be in field transfer and not in acquisition and retirement in respective company codes.
Where is TTY grp are set for TTY.Can it be modified.Please suggest.

For creating transaction type see the wiki.
In the transaction types you assign them!
For 151
SPRO:
Financial Accounting / Asset Accounting / Transactions / Acquisitions / Define Transaction Types for Acquisitions.
Assign there the asst hist group you need for this transaction type
For 270
SPRO:
Financial Accounting / Asset Accounting / Transactions / Retirements / Define Transaction Types for Retirements
Assign there the asst hist group you need for this transaction type

BAPI or FM to change the PO release group

Hi,
I would like to change the PO release group (EKKO-FRGGR).
I could not find the way to change this field through BAPI BAPI_PO_CHANGE.
Please suggest me any BAPI or FM!
Thanks,
Khanh

Hi,
It seems ME_REL_STRATEGIE_EKKO is used for creating a new PO.
I want to change the PO release group for a specific PO only.
And the BAPI BAPI_PO_RELEASE seems to change the Release Code, not Release Group!!!
Please advice!
Thanks,
Khanh
Edited by: Khanh Nguyen on Sep 23, 2010 2:37 PM

How to use Start Task Group for Workflow Interface

Hi all,
anyone who can tell me how to use the Interface IFWFTSKGRP (Start Task Group for Workflow Interface)?
As far as I understood the documentation it can be used to restrict the selection of workflows that can be started in the Generic Object Services. But the question is how to implement it.
Best regards,
Carsten
Edited by: Carsten Drewes on Jun 10, 2009 10:30 AM

Hi, Carsten,
(probably it's a bit too late to post an answer after 3 years , but I'll post it in case someone else needs it)
You should implement GetTaskGroup method.
The code should return id of the task group (otype TG, mantained in PFTC) that holds the list of workflow definitions.
Here is a sample implementation. It's taken from FORMABSENC business object. It belongs to SAP demo workflow "Notification of Absence". I suppose it should be present in most systems and you can see it in action.
begin_method gettaskgroup changing container.
DATA: taskgroup LIKE rhobjects-object.
*- set task group
taskgroup = 'TG70000023'.
*- set result
swc_set_element container result taskgroup.
end_method.

AP group vs WLAN override interface priority

Hi,
SW version 4.2.207.0
Which interface(VLAN ID) of SSID has priority while AP is configured with WLAN override?
One configured in AP group or one configured in WLAN SSID.
Example:
LAP1 is in AP group with SSID1 to interface VLAN2 mapping
WLAN SSID1 has mapping to interface VLAN3
LAP1 has WLAN override enable for SSID1.
Clients connected to LAP1 will be in VLAN2 or VLAN3?
Thanks for clarifying.

clients will be connecting to VLAN3. WLAN overrides what WLAN needs to be enabled/broadcasted on specific AP while AP group overrides WLAN to VLAN mappings.
http://www.cisco.com/en/US/docs/wireless/controller/4.2/configuration/guide/c42wlan.html#wp1127323
Configuring WLAN Override
By default, access points transmit all defined WLANs on the controller. However, you can use the WLAN override option to select which WLANs are transmitted and which are not on a per access point basis. For example, you can use WLAN override to control where in the network the guest WLAN is transmitted, or you can use it to disable a specific WLAN in a certain area of the network.
Configuring Access Point Groups
In a typical deployment, all users on a WLAN are mapped to a single interface on the controller. Therefore, all users associated with that WLAN are on the same subnet or VLAN. However, you can override this default WLAN setting to distribute the load among several interfaces or to group users based on specific criteria such as individual departments (for example, marketing) by creating access point groups (formerly known as site-specific VLANs). Additionally, these access point groups can be configured in separate VLANs to simplify network administration
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008073c723.shtml
AP Group VLANs with Wireless LAN Controllers Configuration Example

SG300 cant change the Link Local address for an IPv6 interface

There seems to be no apparent way to change the Link Local address for an IPv6 interface
If I create more than one interface they all appear to have the same Link Local address

Never mind, I figured it out
By adding a Link Local address to an interface, it overides the existing one on the interface

Question on Interface Groups and Mobility

Hi everyone.
I have a small question.
I have two 5508 controllers with 6 Access Points (3 on each controller). The network layout has one AP on one controller, one on the other, 45 degrees and about 100ft apart from each other.
In this layout the clients roam from one AP to the other, one controller to the other, but there are certain times where the client loses connectivity to the network (layer 3). I don't see any disconnect or roaming messages in the controller logs, but the laptop shows a "!" sign in its wireless connection (win 7).
It can take from a few seconds to several minutes for it to get an ip address and connectivity again.
Now, for my setup:
I have 3 interfaces with different VLANs, and an interface group that binds those 3 interfaces together. The interfaces are called the same on both controllers, and the interface group as well.
The wlan number is the same, as the SSID configuration.
The question is:
When the client roams to the other controller, does it retain the same interface/VLAN configuration? I have found documentation stating that when the user roams and the WLC has the same subnet, it goes with no issues, but it doesn't mention interface groups. Could it be that in some handovers the client falls in a different VLAN even when it is in the same interface group?
Thanks in advance for your help.

Are these two WLC in same mobility group ? If that is the case clients should not change the IP when they roam from one WLC to another. Even in interface group configuration it should work like this.
Here is sample config I did to test this out (I haven't use interface group, but as per my understanding It should not make any difference).
http://mrncciew.com/2013/03/17/l3-inter-controller-roaming/
HTH
Rasika

Dynamic interface group assignment

Wir testen aktuell das dynamische vlan assignment mit dem wlc (version 7.3.101) und dem microsoft nps server. das überschreiben der vlan id anhand einer zutreffenden netzwerkrichlinie funktioniert einwandfrei. nun stellt sich die frage, ob das überschreiben auch möglich ist, wenn auf dem wlc für eine ap-group eine interface gruppe anstelle eines einzelnen vlans definiert ist. hat jemand erfahrungen damit gemacht? konkret sieht der aufbau wie folgend aus:
vlan 100-110 sind in als interface group01 zusammengefasst.
unter ap groups ist eine ssid mit dieser interface gruppe01 konfiguriert.
unter wlan ist eine ssid mit: radius server overwrite interface und: allow aaa override konfiguriert.
auf dem nps gibt es eine zutreffende netzwerkrichtlinie mit radius attribute:
framed-protocol = ppp
service-type = Framed
Tunnel-Medium-Type 802
Tunnel-Pvt-Group-Id = gruppe01 (Name der Interface Gruppe, analog VLAN)
Tunnel-Type = VLAN
--> Wenn wir eine einfache VLAN ID angeben funktioniert es, mit dem Namen der Interface Gruppe funktioniert es nicht.
Hat jemand erfahrung, ob das zuweisen einer interface gruppe per radius attribut möglich ist?

Thank you for your answer.
if i define a single vlan id, everything works fine. but we try to make this work with an interface group instead of a single vlan... i am not shure if this is possible or not.. i just read the following release notes:
AAA Override Support for Interface Groups
This release supports AAA override for interface groups.
This feature extends the current access point group and AAA override architecture where access point groups and AAA override can be configured to override the interface group WLAN that the interface is mapped to. This is done with multiple interfaces using interface groups.
so if i change the single vlan id from tunnel-private-group-id attribute to the interface group it doesnt work anymore...

FlexConnect & Interface Groups

I have a WLC 5508 running 7.4.121.0 where several sites have APs in FlexConnect mode.
For those sites I also have interface groups (this is just an example, i have more than one group)
Site 1 - Group 1 - vlan 110 (faculty) and vlan 112 (students)
Site 2 - Group 2 - vlan 210 (faculty) and vlan 212 (students)
Under WLAN -> Advanced -> AP Groups
I select Site 1 Group Name and add a new WLAN SSID to Interface/Interface Group mapping.
When I go to Wireless and select a FlexConnect AP from Site 1 and then go to the FlexConnect Tab -> VLAN Mappins the VLAN ID is wrong (neither 110 or 112). I can of course manually change it to 110 but then any clients on vlan 112 on that SSID can't connect to the network.
Is there a way to specific a VLAN ID when using Interface group and Flexconnect?

Do you have configured local switching and use AAA overide to asign the VLAN for faculty and students? Else can you give some more information about the configuration.
With local switching and VLAN AAA overide you need to create sub-interfaces on the AP's. You can do this in the Flexconnect group (one per site). Then go tho VLAN-ACL mapping and add the VLAN's you need on this site .

7206 G1 boot issue: No interface specified for interface_command

I can't seem to find out what this command means? I am pasting a config into a new router, do I need to paste in a certain order?
It boots just fine after it decompresses again, but it leaves me with a very lengthy boot time.
Core_7206_1#write mem
Building configuration...
[OK]
Core_7206_1#reload
Proceed with reload? [confirm]
*Jun 7 01:16:43.547: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload Command.
System Bootstrap, Version 12.3(4r)T3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2004 by cisco Systems, Inc.
C7200 platform with 1048576 Kbytes of main memory
Readonly ROMMON initialized
Self decompressing the image : ########################################################################### [OK]
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% Cannot set multilink group. Interface Multilink2 does not exist
% Cannot set multilink group. Interface Multilink2 does not exist
% Cannot set multilink group. Interface Multilink2 does not exist
% Cannot set multilink group. Interface Multilink9 does not exist
% Cannot set multilink group. Interface Multilink9 does not exist
% Cannot set multilink group. Interface Multilink10 does not exist
% Cannot set multilink group. Interface Multilink10 does not exist
% Cannot set multilink group. Interface Multilink3 does not exist
% Cannot set multilink group. Interface Multilink3 does not exist
% Cannot set multilink group. Interface Multilink3 does not exist
% Cannot set multilink group. Interface Multilink3 does not exist
% Cannot set multilink group. Interface Multilink3 does not exist
% Cannot set multilink group. Interface Multilink3 does not exist
% Cannot set multilink group. Interface Multilink7 does not exist
% Cannot set multilink group. Interface Multilink7 does not exist
% Cannot set multilink group. Interface Multilink4 does not exist
% Cannot set multilink group. Interface Multilink4 does not exist
% Cannot set multilink group. Interface Multilink5 does not exist
% Cannot set multilink group. Interface Multilink5 does not exist
% Cannot set multilink group. Interface Multilink8 does not exist
% Cannot set multilink group. Interface Multilink8 does not exist
% Cannot set multilink group. Interface Multilink11 does not exist
% Cannot set multilink group. Interface Multilink11 does not exist
% Cannot set multilink group. Interface Multilink6 does not exist
% Cannot set multilink group. Interface Multilink6 does not exist
% Cannot set multilink group. Interface Multilink6 does not exist
% Cannot set multilink group. Interface Multilink12 does not exist
% Cannot set multilink group. Interface Multilink12 does not exist
Self decompressing the image : ###################################################################################################################################################################################################################################################### [OK]
              Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
           cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706
Cisco IOS Software, 7200 Software (C7200-ADVIPSERVICESK9-M), Version 12.4(15)T7, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Thu 14-Aug-08 03:06 by prod_rel_team
Image text-base: 0x600089D8, data-base: 0x632911A0
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
Cisco 7206VXR (NPE-G1) processor (revision B) with 983040K/65536K bytes of memory.
Processor board ID 31651452
SB-1 CPU at 700MHz, Implementation 1025, Rev 0.2, 512KB L2 Cache
6 slot VXR midplane, Version 2.7
Last reset from power-on
PCI bus mb1 (Slots 1, 3 and 5) has a capacity of 600 bandwidth points.
Current configuration on bus mb1 has a total of 90 bandwidth points.
This configuration is within the PCI bus capacity and is supported.
PCI bus mb2 (Slots 2, 4 and 6) has a capacity of 600 bandwidth points.
Current configuration on bus mb2 has a total of 490 bandwidth points.
This configuration is within the PCI bus capacity and is supported.
Please refer to the following document "Cisco 7200 Series Port Adaptor
Hardware Configuration Guidelines" on Cisco.com <http://www.cisco.com>
for c7200 bandwidth points oversubscription and usage guidelines.
2 FastEthernet interfaces
3 Gigabit Ethernet interfaces
4 Channelized T1/PRI ports
2 Channelized T3 ports
509K bytes of NVRAM.
Installed image archive
250880K bytes of ATA PCMCIA card at slot 2 (Sector size 512 bytes).
16384K bytes of Flash internal SIMM (Sector size 256K).
Press RETURN to get started!
*Jun 7 01:21:56.191: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*Jun 7 01:21:56.195: %LINEPROTO-5-UPDOWN: Line protocol on Interface VoIP-Null0, changed state to up
*Jun 7 01:21:56.195: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
*Jun 7 01:21:56.195: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to up
*Jun 7 01:21:56.199: %LINK-3-UPDOWN: Interface T3 1/0, changed state to down
*Jun 7 01:21:56.199: %LINK-3-UPDOWN: Interface T3 2/0, changed state to down
*Jun 7 01:21:56.199: %LINEPROTO-5-UPDOWN: Line protocol on Interface IPv6-mpls, changed state to up
*Jun 7 01:21:56.199: %LINK-3-UPDOWN: Interface FastEthernet4/0, changed state to down
*Jun 7 01:21:56.199: %LINK-3-UPDOWN: Interface FastEthernet4/1, changed state to down
*Jun 7 01:21:56.199: %ENVM-4-ENVWARN: NPE Inlet measured at 54C/129F
*Jun 7 01:21:56.207: %ENVM-4-ENVWARN: NPE Outlet measured at 54C/129F
*Jun 7 01:21:56.535: %SYS-6-CLOCKUPDATE: System clock has been updated from 01:21:56 UTC Mon Jun 7 2004 to 20:21:56 GMT Sun Jun 6 2004, configured from console by console.
*Jun 7 01:21:57.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
*Jun 7 01:21:57.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
*Jun 7 01:21:57.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
*Jun 7 01:21:57.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet4/0, changed state to down
*Jun 7 01:21:57.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet4/1, changed state to down
*Jun 7 01:21:57.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel3, changed state to down
*Jun 7 01:21:57.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel10, changed state to down
*Jun 7 01:21:57.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel11, changed state to down
*Jun 7 01:21:57.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel13, changed state to down
*Jun 7 01:21:57.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel20, changed state to down
*Jun 7 01:21:57.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel30, changed state to down
*Jun 7 01:21:57.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel40, changed state to down
*Jun 7 01:21:58.199: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
*Jun 7 01:21:58.451: %SYS-5-CONFIG_I: Configured from memory by console
*Jun 7 01:21:59.359: %SYS-5-RESTART: System restarted --
Cisco IOS Software, 7200 Software (C7200-ADVIPSERVICESK9-M), Version 12.4(15)T7, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Thu 14-Aug-08 03:06 by prod_rel_team
*Jun 7 01:21:59.399: %ENTITY_ALARM-6-INFO: ASSERT CRITICAL GBIC Slot 0/1 GBIC is missing
*Jun 7 01:21:59.399: %ENTITY_ALARM-6-INFO: ASSERT CRITICAL GBIC Slot 0/2 GBIC is missing
*Jun 7 01:21:59.399: %ENTITY_ALARM-6-INFO: ASSERT CRITICAL GBIC Slot 0/3 GBIC is missing
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/1:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/2:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/3:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/4:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/7:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/8:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/9:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/10:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/11:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/12:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/14:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/15:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/16:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/17:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/18:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/19:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/20:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/21:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/23:0, changed state to down
al1/0/24:0, changed state to downOWN: Interface Seri
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/25:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/26:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/27:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial1/0/28:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/1:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/2:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/4:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/5:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/6:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/7:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/8:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/9:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/10:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/11:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/12:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/13:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/14:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/15:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/16:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/17:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/18:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/19:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/20:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/22:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/24:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/25:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/26:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/27:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/28:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial3/3:0, changed state to down
*Jun 7 01:21:59.631: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Jun 7 01:21:59.631: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*Jun 7 01:21:59.663: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
*Jun 7 01:21:59.663: %LINEPROTO-5-UPDOWN: Line protocol on Interface NVI0, changed state to up
*Jun 7 01:21:59.695: %ENTITY_ALARM-6-INFO: ASSERT MAJOR T31/0 Physical Port Link Down
*Jun 7 01:21:59.695: %ENTITY_ALARM-6-INFO: ASSERT MAJOR T32/0 Physical Port Link Down
*Jun 7 01:21:59.695: %ENTITY_ALARM-6-INFO: ASSERT INFO Fa4/0 Physical Port Administrative State Down
*Jun 7 01:21:59.695: %ENTITY_ALARM-6-INFO: ASSERT INFO Fa4/1 Physical Port Administrative State Down
*Jun 7 01:21:59.695: %SNMP-5-COLDSTART: SNMP agent on host Core_7206_1 is undergoing a cold start
*Jun 7 01:22:00.239: %SYS-6-BOOTTIME: Time taken to reboot after reload = 318 seconds
*Jun 7 01:22:00.783: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
*Jun 7 01:22:00.783: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to down
*Jun 7 01:22:06.667: %ENTITY_ALARM-6-INFO: ASSERT MAJOR T31/0 Transmitter is sending remote alarm
*Jun 7 01:22:06.667: %ENTITY_ALARM-6-INFO: ASSERT MAJOR T31/0 Receiver has loss of signal
*Jun 7 01:22:07.915: %ENTITY_ALARM-6-INFO: ASSERT MAJOR T32/0 Transmitter is sending remote alarm
*Jun 7 01:22:07.915: %ENTITY_ALARM-6-INFO: ASSERT MAJOR T32/0 Receiver has loss of signal
                                                                                           Core_7206_1>
Core_7206_1>

Those must be coming from the boot image, which doesn't have all the feature support as the regular IOS image. The messages are just warnings when configuring some of the features that the boot images doesn't understand.

Interface Group in WLC

Hi to who will see my case
I have WLC configured by 3 Interfaces groups , 5 interfaces for each group (each group used by one SSID) .
SSID-EMPLOYEE
     EMPLOYEE-GROUP
          -EMPLOYEE-INTEFCAE-1 DHCP is MS server 2003 (Scope 10.21.4.0/22)
          -EMPLOYEE-INTEFCAE-2 DHCP is MS server 2003 (Scope 10.21.8.0/22)
          -EMPLOYEE-INTEFCAE-3 DHCP is MS server 2003 (Scope 10.21.12.0/22)
          -EMPLOYEE-INTEFCAE-4 DHCP is MS server 2003 (Scope 10.21.16.0/22)
          -EMPLOYEE-INTEFCAE-5 DHCP is MS server 2003 (Scope 10.21.20.0/22)
and the same for SSID-STUDENT and SSID-VOICE.
My labtob sometimes connects with the EMPLOYEE-INTEFCAE-1 and sometime with the second interface and so, How can I force it to connect with one interface all the time or how can I prevent the WLC to use the second interface as long as the first interface is not full.
because I need to reserve an IP address in the DHCP server from the first scope for my labtob, once I connect to the network I will get the same reserverd Address , but in my case I reserved the IP but the controller forced my labtob to connect the second interface and new scope.
Regards
Mahmoud

The interface group treats hosts in a similar fashion to round-robin.
1st host:group member 1
2nd host:group member 2
3rd...
4th...
until the last group member is reached and then it goes back to one.
Not sure if there is a way to force a host to a particular group member, unless of course you use a dedicated wlan bound to the particular subnet. This would not utilize the interface grouping though.
Perhaps a NAC solution could add some control over which network the laptop lands in....

5508 WLC Interface Groups

We have not configured or used interface groups in our wireless deployments, and I am just curious if there are any issues or caveats experienced with using these? We have a few instances where we have setup a /23 network for a specific wlan. I undertsand this increases broadcasts. Would interface groups be preferred over using a /23 or even maybe a /22 to accomodate addressing?

By default, the WLC will not forward broadcast. There are pro's an con's to interface groups... if your doing multicast, that can be an issue unless you specify an multicast vlan. I have used interface groups because customer standardize on /24, so I would combine a bunch of /24's to create an interface group. I have customers with /23 and /23 and others with no issues... but I look at it as on the wired side. You okay with /23 and or /22 on the wired side?
Thanks,
Scott
*****Help out other by using the rating system and marking answered questions as "Answered"*****

Flexconnect - local-switching - Interface Groups - multiple subnets/vlans

So I'm trying to setup an "interface-group-like" configuration on some Flexconnect APs with local switching enabled in order to support multiple subnets/VLANs linked to a single SSID.
Does anyone know if this is possible or have any suggestions?
I've tried:
AP Groups - One SSID which would require central switching for it to be of use (I think).
AP Groups - Creating an additional SSID and then placing the APs in a group per site. This works but is going to be difficult to manage if I have 400+ sites running this sort of setup.
For reference, my end goal is to have multiple (400+) branch sites with the same WLAN mapped to 3 or 4 different VLANs in order to split the subnets up into smaller chunks (/23s or /24s). These VLANs are all switched locally and are uniform in numbering across all the sites from a layer 2 perspective.
Thanks,
Ric

Interface groups is not an available feature on FlexConnect. FlexConnect doesn't support layer 3 roaming if devices roam from one FlexConnect ap to another and the wlan to vlan mappings are different. This is a limitation to FlexConnect along with a few others listed in the FlexConnect deployment guide.
-Scott

User Interface Template for Interactive Report Region

In 3.2, where do we set the user interface template for Interactive Reports region?
No matter what out of the box theme I switch to, the Interactive Reports region shows the same. What and where do I change the template so that alternating rows use two different colors?

There is no template for Interactive Reports like for a "normal" report. You need to modify the CSS and supply your own for this to happen.
I believe most things are tagged with #apexir - firebug with Firebox is invaluable. This thread may help:
Re: changing the look and feel of interactive report.

Error: no interface action for sender or receiver found

Hello,
I have configured a asynchronous RFC to JDBC scenario.
When i try to execute the end to end scenario , the message in SXMB_MONI is with a green flag(scheduled) and queue status is yellow and when i double the message , the trace shows following message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">Work Process ID: 25711</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = HXD</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2010-05-24T12:23:09Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 3CA00D0C20460CD10B3CA18E3C804118</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0004</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0004</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface Z_SD_HP_SALESORG</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:rfc:functions</Trace>
<Trace level="1" type="T">--no interface action for sender or receiver found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
</SAP:Trace>
The pipeline steps on the left hand side in sxmb_moni shows only inbound Message i.e remaining steps are not executed.
When i try the execute message by directly sending message from Runtime Workbench , the scenario is executed successfully.
Please help.
Thanks & Regards,
Loveena

Hello,
The problem was with the Client. Our Xi is running on Client 200 wheras at runtime it was picking up the default client 001.
So after changing the default Client 001 to 200.
The scenario was working fine.
But from the third time onwards again it is taking the default Client and I am facing the issue.
I guess it is some Cache problem. Can anybody tell me how to refresh the cache.
Thanks ,
Loveena

Change Interface to Interface Group for WLAN

Similar Messages

Maybe you are looking for