Multiple Ports & Mobility Groups

On our wireless network we have two 6509-E switches each with a WiSM and a 5508 WLC. The 5508 WLC only had one port connected to one of the 6509 units then we added another port on the 5508 to the other 6509. Do I need to add the IP and MAC address of the the second port of the 5508 to the existing Mobility Group?
Thanks for any help.
Jeff

When you adding mobility member you need to configure the Controller IP address & its MAC address (NOT the interface MAC address WLC connect to). Therefore in any connection type (LAG enabled or NOT) it has to be your 5508 controller IP address & its own MAC address.
If you type "show sysinfo" or "show mobility summary" on your 5508 you can get this information as shown below. Then you can add that onto your exisiting mobility group configuration of WiSM (you have to add WiSM detail on your 5508 mobility config as well)
(5508) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.5.102.0
System Name...................................... 5508
IP Address....................................... 10.10.10.10
Burned-in MAC Address............................ 64:00:F1:F5:B0:80
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
(5508) >show mobility summary
Mobility Protocol Port........................... 16666
Default Mobility Domain.......................... dmz
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0xe49d
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 9
Mobility Control Message DSCP Value.............. 0
Controllers configured in the Mobility Group
MAC Address IP Address Group Name Multicast IP Status
64:00:f1:f5:b0:80 10.10.10.10 dmz 0.0.0.0
HTH
Rasika
***** Pls rate all useful responses ****

Similar Messages

Mobility group same ssid multiple WLC

I have a 4400 and a 5508 WLC in the same location
We want to be able to roam between ap joined to both the 4400 and the 5508 using only one ssid
Do I only need to create a mobility group and add both WLC
then create only one WLAN on one of the controllers and it will be shared across bot WLC.
Or something else?

Resolution :
Yes you are correct. Please follow this link for Mobility groups and Roaming :
http://www.cisco.com/en/US/docs/wireless/controller/7.2/configuration/guide/cg_mobility.html

Mobility Group Table *MUST* be populated in each WLC in same mobility group

For what it's worth,
I recently discovered that when you have multiple controllers and want to implement Mobility Groups, more is needed than simply entering the same Default Mobility Group Name for each controller within the mobility group. The following is required:
a) The IP address of the "Virtual" interface on each controller must be identical on each controller within the mobility group.
b) The Default Mobility Group Name must be identical on each controller within the mobility group (case sensitive).
c) The mobility table must be populated with an entry for each controller within the mobility group.
Otherwise, you will see some inexplicable behavior such as:
* LWAP access points refusing to change to a different controller, even if their primary controller is explicitly set and the LWAP is rebooted.
* LWAP access points unable to find any other wireless controller other than the one pointed to by the "CISCO-LWAPP-CONTROLLER" DNS entry (presumably, this would also be the case if DHCP Option 43 is used to point the LWAP to a controller). Once the first controller reaches its max. capacity of LWAPs, no more LWAPs can join.
* Even MASTER CONTROLLER MODE has no effect.
Cisco TAC was able to explain the great mystery of the Mobilty Group Table to me. However, unless you know your problem is related to mobility groups issues, you might not know to start there (I know I didn't).
The least difficult method I have found for populating the mobility group table is as follows:
Build a text file with one entry for each controller in the mobility group as follows:
Log into the GUI for each controller and selecting: Controller -> Mobility Management -> Mobility Groups, click the "EDIT ALL" button and copy the MAC and IP address from the text box into a text file using NOTEPAD. Repeat this for each controller, creating a new line for each:
The format for the entries is as follows:
00:1a:6c:91:22:A0 192.168.20.44
00:1a:6c:91:22:B4 192.168.20.45
Once the text file is completed (one entry for each controller in the mobilit group), click the EDITALL button and copy the entire contents of the text file and paste it into the text box on the controller GUI, click the APPLY button and click Save Changes. Repeat for each controller.
Again, make sure that the following settings are IDENTICAL in each of the controllers in the Mobility Group:
* The IP address of the "virtual" interface ( Controller -> interfaces ) must be the same on all controllers.
* The "Default Mobility Domain Name" ( Controller -> General ) must be identical on each controller in the mobility group (note: the Mobility Domain Name is case sensitive).
After making changes directly to the controllers, a "refresh from controller" in the WCS might be needed to get the WCS to attempt to synchronize itself with the controllers.
Here is a link to the 4.2 Wireless Controller Configuration Guide which discusses this in greater detail.
http://www.cisco.com/en/US/products/ps6366/products_configuration_guide_chapter09186a00808e638b.html
It is unfortunate that there are currently no mechanisms in the WCS 4.2 to make these changes in bulk (i.e.: The WCS has no Controller Template to do this).
Also, if you ever need to replace a controller, you will need to update the Mobility Group Table in each controller in the Mobility Group (since the tables will have the MAC address of the old controller which will now be different in the new replacement controller).
Despite having used the "unified" product for some time now, there are still surprises from time to time. I just thought that I would share my experience for those who may want avoid it and/or who may be encountering any of odd the behavior described above.
- John

Hi John,
Nice work with this very relevant info! Please post a short reply here so that we can give this the nice rating it deserves :)
Thanks again!
Rob

ISE 1.2 and ACL's with multiple ports

When creating a DACL for my groups I used the Syntax " permit tcp any 192.168.20.0 0.0.0.255 eq 22 443" for one of my acl's inside the DACL and the syntax check validated it. When I pushed it to my groups it also worked but I have heard that this type of multiple port ACL in ISE is not supported. Does anyone know if this is accurate?

Thanks for the response but it's wrong. Cisco supports stacked ports in 1.2 for wired users. They carried over 1.1documentation to 1.2 and never updated it. We have it in writing from Cisco tac.

WLC 5508 * 2 & Mobility Group

What I am trying to configure is Mobility Groups.
My understanding is that this will allow AP to successfully register and fail over over seamlessly if any of the WLC had to fail ?
It could be I am confusing two things into one :( & I am totally confused and not understanding the benefits of mobility group mentioned above.
Also when a AP starts up and registers with the WLC ......I click on a registered AP > High Availability ( Primary / Sec / Tertiary ) all fields are blank...
Initially I also thought that once my SSO is all setup and working than those options "AP > High Availability" will get populated automatically but clearly not unless something is not working.
My current config is as follows:-
WLC 5508 * 2
WLC 1 - Primary
WLC 2 - HA SKU (Secondary )
Redundancy = SSO (Both AP and Client SSO)
=============
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.6.130.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.101.1
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS
System Name...................................... WLC5508
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. SSO (Both AP and Client SSO)
IP Address....................................... 10.31.66.21
Last Reset....................................... Software reset
System Up Time................................... 0 days 22 hrs 39 mins 57 secs
System Timezone Location......................... (GMT) London, Lisbon, Dublin, Edinburgh
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... GB - United Kingdom
Operating Environment............................ Commercial (0 to 40 C)
--More-- or (q)uit
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +38 C
External Temperature............................. +21 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 1
Number of Active Clients......................... 0
Burned-in MAC Address............................ F8:72:EA:EE:5B:B2
Power Supply 1................................... Present, OK
Power Supply 2................................... Absent
Maximum number of APs supported.................. 500
============================================
TA

TA,
Mobility and mobility groups are used for the wireless users roaming. What we know that a wireless users can roam between different APs within the same WLC, but when the SSID is used within multiple WLCs, and the client wanted to roam to an AP joined to another WLC, you would need to configure WLC mobility to maintain seamless roaming. For more info:
http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-0/configuration-guide/b_cg80/b_cg80_chapter_010001101.html
Now, I understand that your purpose is to have high availability for your APs. No this is done traditionally from the AP page, under HA tab, where you configure the WLCs names and IPs there. This can be done manually on each AP (you can use CLI to make it easier) or you can push a configuration template using a management server (WCS/NCS/CPI).
Configuring HA on the AP:
http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-0/configuration-guide/b_cg80/b_cg80_chapter_01110000.html
http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-0/configuration-guide/b_cg80/b_cg80_chapter_01110001.html
Using CPI to push AP configuration templates:
http://www.cisco.com/c/en/us/td/docs/wireless/prime_infrastructure/2-0/configuration/guide/pi_20_cg/temp.html
Now mobility may play a role in this, as if you have already configured mobility for your WLCs, then you won't need to configure a "name" for the WLCs when you add them under the HA tab in AP configuration page. That's it.
BR, Ala

WLC 7.3.101.0 Mobility group peer cannot up.

Hi Guys,
It seems the 7.3.101 version Mobility group peer cannot up,: refer to the attach,
Peer 1: version: 7.3.101
Peer 2: version 7.0.98
Peer3: version 7.2.103
Today we got new two WLC for Anchor use, and config the mobility group, but it's failed and cannot up, the ping is ok.

Chris is right here. One thing I tell my clients is to allow everything between the foreign and the anchor WLC's just to verify that the mobility can come up, then lock it down. Here is some links that explain what test is for what port.
http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a00809a30cc.shtml#qa8
Anchor Controller Positioning
Because the anchor controller is responsible for termination of guest WLAN traffic and subsequent access to the Internet, it is typically positioned in the enterprise Internet DMZ. In doing so, rules can be established within the firewall to precisely manage communications between authorized controllers throughout the enterprise and the anchor controller. Such rules might including filtering on source or destination controller addresses, UDP port 16666 for inter-WLC communication, and IP protocol ID 97 Ethernet in IP for client traffic. Other rules that might be needed include the following:
•TCP 161 and 162 for SNMP
•UDP 69 for TFTP
•TCP 80 or 443 for HTTP, or HTTPS for GUI access
•TCP 23 or 22 for Telnet, or SSH for CLI access
Depending on the topology, the firewall can be used to protect the anchor controller from outside threats.
For the best possible performance and because of its suggested positioning in the network, it is strongly recommended that the guest anchor controller be dedicated to supporting guest access functions only. In other words, the anchor controller should not be used to support guest access in addition to controlling and managing other LWAPP APs (LAPs) in the enterprise.
Sent from Cisco Technical Support iPhone App

Mobility groups with multicast - 7.4.100.60

Hello all,
I am not sure if this is a bug, but here we go. I configured 2 controllers in a mobility group using multicast signalling.
I expect that from the moment i enable multicast, the controller joins this group AND STAYS IN THIS GROUP so he will get messages from all other controllers.
On the first hop router, i can see the join:
#sh ip igmp mem 239.194.248.10
Flags: A - aggregate, T - tracked
       L - Local, S - static, V - virtual, R - Reported through v3
       I - v3lite, U - Urd, M - SSM (S,G) channel
       1,2,3 - The version of IGMP, the group is in
Channel/Group-Flags:
       / - Filtering entry (Exclude mode (S,G), Include mode (G))
Reporter:
       <mac-or-ip-address> - last reporter if group is not explicitly tracked
       <n>/<m>      - <n> reporter in include mode, <m> reporter in exclude
Channel/Group                  Reporter        Uptime   Exp. Flags Interface
*,239.194.248.10               10.102.78.98    00:00:05 02:54 2A     Vl350
However, this entry does not get refreshed. I have the impression that the controller does not reply to the IGMP general queries:
IGMP(0): Send v2 general Query on Vlan350 -> no replies
#sh ip igmp mem 239.194.248.10
Flags: A - aggregate, T - tracked
       L - Local, S - static, V - virtual, R - Reported through v3
       I - v3lite, U - Urd, M - SSM (S,G) channel
       1,2,3 - The version of IGMP, the group is in
Channel/Group-Flags:
       / - Filtering entry (Exclude mode (S,G), Include mode (G))
Reporter:
       <mac-or-ip-address> - last reporter if group is not explicitly tracked
       <n>/<m>      - <n> reporter in include mode, <m> reporter in exclude
Channel/Group                  Reporter        Uptime   Exp. Flags Interface
*,239.194.248.10               10.102.78.98    00:02:35 00:24 2A     Vl350
>> 20 seconds from expiry.
#sh ip igmp mem 239.194.248.10
Flags: A - aggregate, T - tracked
       L - Local, S - static, V - virtual, R - Reported through v3
       I - v3lite, U - Urd, M - SSM (S,G) channel
       1,2,3 - The version of IGMP, the group is in
Channel/Group-Flags:
       / - Filtering entry (Exclude mode (S,G), Include mode (G))
Reporter:
       <mac-or-ip-address> - last reporter if group is not explicitly tracked
       <n>/<m>      - <n> reporter in include mode, <m> reporter in exclude
Channel/Group                  Reporter        Uptime   Exp. Flags Interface
>> 20 seconds later, gone
>> At this moment the controller doesn't receive any messages anymore from remote controllers:
>>sh ip mroute 239.194.248.10
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
       L - Local, P - Pruned, R - RP-bit set, F - Register flag,
       T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
       U - URD, I - Received Source Specific Host Report,
       Z - Multicast Tunnel, z - MDT-data group sender,
       Y - Joined MDT-data group, y - Sending to MDT-data group
       V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 239.194.248.10), 00:05:38/00:00:21, RP 10.102.90.20, flags: SP
Incoming interface: Port-channel30, RPF nbr 10.102.78.13, RPF-MFD
Outgoing interface list: Null
This is seen on 8500 platform running 7.4.100.60
We have also WISMs running at 7.0.230.0, and there it can be seen that the entry refreshes every minute (like it should be)
IGMP(0): Received v2 Report on Vlan950 from 10.96.9.67 for 239.194.240.1
IGMP(0): Received Group record for group 239.194.240.1, mode 2 from 10.96.9.67 for 0 sources
IGMP(0): Updating EXCLUDE group timer for 239.194.240.1
IGMP(0): MRT Add/Update Vlan950 for (*,239.194.240.1) by 0
Shouldn't the controller at all times stay joined in its mobiility group ?

ok, some more debugging.
I loaded up 7.4.100.60 on a 5500 controller and got the same result.
NOTE: my global multicast settings are:
Controller->General: AP Multicast Mode: UNICAST
Controller->Multicast->Global Multicast is NOT enabled
Controller->Mobility->Multicast Messaging: enabled and group is 239.194.240.3
With this config, the IGMP entry is not retained, and i see on the controller the message (debug bcast all):
>>processEthernetIGMPpacket Received IGMP Pkt from DS when either igmp snooping or global multicast is disabled.
So, i then enabled Global Multicast (Controller->Multicast->Global Multicast to enable), and then the IGMP entry is refreshed:
bcastReceiveTask: Sep 05 13:11:17.734: IGMP packet received over vlanid = 102 from DS side
*bcastReceiveTask: Sep 05 13:11:17.734: received an IGMP query for multicast vlan = 102 address 0.0.0.0 intfnum = 3
*bcastReceiveTask: Sep 05 13:11:17.734: IGMP report scheduled for grp=0xefc2f003, vlan=102, intf=3, slot=70, maxRespTime=100
>>sh ip igmp membership 239.194.240.3
004586: Sep 5 15:11:50.710 CEST: IGMP(0): Send v2 general Query on Vlan101
Flags: A - aggregate, T - tracked
       L - Local, S - static, V - virtual, R - Reported through v3
       I - v3lite, U - Urd, M - SSM (S,G) channel
       1,2,3 - The version of IGMP, the group is in
Channel/Group-Flags:
       / - Filtering entry (Exclude mode (S,G), Include mode (G))
Reporter:
       - last reporter if group is not explicitly tracked
       /      - reporter in include mode, reporter in exclude
Channel/Group                  Reporter        Uptime   Exp. Flags Interface
*,239.194.240.3                10.102.180.218 00:38:51 02:28 2A     Vl102
Now, on the 5500 controller i can enable global multicast, while AP multicast mode is in UNICAST.
However, on the 8500 controller, running the same firmware (7.4.100.60), when i try to enable "Global Multicast", i get:
"Multicast-Unicast mode does not support IGMP/MLD snooping. Config mode to multicast-multicast first". I did not get this message on the 5500.
So when switching to Multicast->Multicast mode, and then enabled "Global Multicast", then it works.
This means that in order to have mobility messaging working on 8500 in multicast, you MUST put the AP Multicast Mode to Multicast AND you must enabled "Global Multicast", otherwise it won't work.

WLC 7.4.100.0 Mobility group control and data path down

Hi All,
Today i am facing issue with mobility group. i checked and found control and data path is down on foreign controller.I am able to ping anchor controller. Required ports are open on firewall but mping and eping fails. Any idea whats wrong. On Anchor controller, i have 7 foreign controller configured and among these 3 are working fine. Having problem with 4 foreign controller. Previously all are working fine and there is no changes made on network or firewall.

Post output of "show mobility summary" of your Anchor WLC & a non-working WLC. Also "show sysinfo" of those two controllers.
Regards
Rasika

WLC mobility group between 4404 and 5508 controllers

Mobility 'Control and Data Path Down' between 4404 and 5508 WLC's.
Hello, we have 5 x 4404 WLC's running 7.0.240.0 with mobility configured fine between them.
We have installed a 5508 with HA running 7.4.110.0, and have tried to add it to the mobility group, however we see 'Control and Data Path Down' between the new 5508 and all the 4404 controllers.
All controllers have:
The same virtual address
Management interfaces are in the same VLAN, and indeed all the controllers connect via the same pair of 3750X stacked switches.
The default mobility domain name is the same
4404 output when issung the command 'show mobility summary'
Symmetric Mobility Tunneling (current) .......... Enabled
Symmetric Mobility Tunneling (after reboot) ..... Enabled
Mobility Protocol Port........................... 16666
Default Mobility Domain.......................... SGH-Mobility
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0xe209
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 6
Mobility Control Message DSCP Value.............. 0
5508 ouput when issueing the command 'show mobility summary'
Mobility Architecture ........................... Flat
Mobility Protocol Port........................... 16666
Default Mobility Domain.......................... SGH-Mobility
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0xe209
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 6
Mobility Control Message DSCP Value.............. 0
I've spent quite some time double checking all the configurations to no avail.
Has anybody seen this problem before?
Kind regards
Dave Bell

Thanks Sandeep.
I am well versed with WLC's and mobility, however trying to add a 5508 to a mobility group with 4404's has come up with a bit of a curve ball.
All the 4404 controllers all joined the mobility group fine, no problems at all - its only the 5508 I am struggling with.
In theory its simple, populate the IP address, and MAC addres of the management interface of the remote WLC, as long as the management interfaces are in the same VLAN, and the Default Mobility Domain Name are the same it should come up.
Interestingly I have found the 5508 reports its own management interface MAC address incorrectly when viewing the Mobility Groups:
For example:
{Screen shot WLC1.jpg}
5508 management address is 10.95.x.x and when viewing the Mobility Management screen it shows its own MAC address as bc:16:65:f9:37:60.
however!
From our router is I do an sh arp | i 10.95.x.x (controller management address), I see:f872.eaee.becf.
{Screen shot wlc2.jpg}
Hence the WLC reports as: bc:16:65:f9:37:60
and
The network reports as: f872.eaee.becf for the same IP address.
I have changed the other WLC's to the MAC adress seen on the network for the new controller, aka changed from
bc:16:65:f9:37:60
to
f8:72:ea:ee:be:cf
I now see the controllers reporting the mobility with the new controller as 'Control Path Down', however I am at a loss as to what may be causing this?
Kind regards
Dave Bell

Add a FastEthernet interface to mobility group

I admit I don't completely understand mobility groups. I need to add a server on one of the wireless networks. I can't seem to figure out if there is a way to configure a port on a 6509 to be in the same wireless mobility group.
Thanks.
Edited: No need to respond. Just talked to TAC and found out this is not possible at this time.

i am quite new too. but i don't think you can. mobility group is for wireless part of the network, assigned to tunnel and ssid in the aps only.

How can I send a message to multiple contacts using "groups".

How can I send a message to multiple contacts using "groups".
It was easy on my sony ericssonn....do i need to download an app?

There is no group send option like you are looking for.
To send to a group you have to pick each person you want to send to and send as a group that way. Then don't delete that SMS thread and you can reuse it again later.
As for an app, well SMS works via your carrier and the OS, not something an App can do unless the app send the data to them (a third party) and then they relay it to the carrier. Do you really want to be sending your SMS to some 3rd party first?

Extended acl - multiple ports on same acl line

hello
i'm working on a (long) acl and have started looking at putting multiple ports on the same line
e.g.
instead of:
ip access-list extended test3
permit tcp any host 10.10.10.1 eq 80
permit tcp any host 10.10.10.1 eq 443
i'd use:
ip access-list extended test3
permit tcp any host 10.10.10.1 eq 80 443
its shortening the acl considerably but the question is:
does this method reduce the TCAM resources required (compared to writing the acl in long hand)?
what are the maximum number of ports that can be included on the same line - is it platform/ios dependant?
thanks
andy

Hello
No. I went ahead with the acl with multiple ports in each ACE and it worked fine. It was deployed on an old WS-C3750G-24PS-E and worked pretty well. When I checked the tcam on the switch I got the following output:
Cisco3750#show platform tcam utilization
CAM Utilization for ASIC# 0                      Max            Used
                                                         Masks/Values    Masks/values
IPv4 security aces:                          1024/1024         33/33
Note: Allocation of TCAM entries per feature uses
a complex algorithm. The above information is meant
to provide an abstract view of the current TCAM utilization
As there were other ACLs on the switch it was difficult to gauge if the multiple ports per ACE approach to ACLs actually saved any TCAM resources. If you find anything out post back - I'd be interested to hear.
thanks
Andy

Multiple ports on single node cannot communicate

I am a Sr. Tech Architect from SBC that it evaluating your product for utilization in our enterprise online order application in combination with the Solarmetric Kodo product.
I was able to install and utilize your application and line command, sample applications no problem on a single jvm utilizing multiple ports and all the members were being recognized no problem. Suddenly, they are no longer being picked up. I am using the packaged configuration xml files as is, just running multiple dos windows on a Win 2k box and launching the line command application. The only other development work I have been doing on the box is test deploys to Apache of the product along with the integration of the Kodo product in a WSAD 5.1 environment, however, I have both those applications shut down and rebooted the machine with no success. I tried running the multicast test just for kicks and got no response back. Scratching my head as to what my be the problem all of a sudden.
Thanks,
Scott

Scott,
Did you, by any chance, install and enable "Microsoft Loopback Adapter"? If so, you'd need to disable it. If not, could you please e-mail me the command line and some output of the multicast test.
Thanks,
Gene
[email protected]

Scan multiple ports on multiple computers

Hey guys,
I wrote the following batch script to use along with portqry tool which is availabe from microsoft download center.
The tool can scan multiple ports on a single computer, but it is not capable of scanning multiple ports on multiple computers in one attempt. Also it gives a big output which is a bit tough if you are trying to prepare a report.
Here is the batch file which takes input from server.txt where all the computer names present and scans for the below ports on each computer and gives you output in a beautiful way.
TCP: 135, 445, 1433, 1434, 1024, 1040
UDP: 1433, 1434
Copy and paste the below code in a batch file and use it along with portqry.exe.
echo off
for /f "tokens=* delims= " %%a in (server.txt) do call :vk %%a
:vk
portqry -n %1 -e 1434 -q -p udp
if errorlevel = 2 goto filtered_1434
if errorlevel = 1 goto failed_1434
if errorlevel = 0 goto success_1434
goto 135
:filtered_1434
Echo %1 udp Port 1434 is listening or filtered
goto 135
:failed_1434
Echo %1 udp Port 1434 is not listening
Goto 135
:success_1434
Echo %1 udp Port 1434 is listening
goto 135
:135
portqry -n %1 -e 135 -q -p tcp
if errorlevel = 2 goto filtered_135
if errorlevel = 1 goto failed_135
if errorlevel = 0 goto success_135
goto 445
:filtered_135
Echo %1 tcp Port 135 is listening or filtered
goto 445
:failed_135
Echo %1 tcp Port 135 is not listening
Goto 445
:success_135
Echo %1 tcp Port 135 is listening
goto 445
:445
portqry -n %1 -e 445 -q -p tcp
if errorlevel = 2 goto filtered_445
if errorlevel = 1 goto failed_445
if errorlevel = 0 goto success_445
goto 1433_tcp
:filtered_445
Echo %1 tcp Port 445 is listening or filtered
goto 1433_tcp
:failed_445
Echo %1 tcp Port 445 is not listening
Goto 1433_tcp
:success_445
Echo %1 tcp Port 445 is listening
goto 1433_tcp
:1433_tcp
portqry -n %1 -e 1433 -q -p tcp
if errorlevel = 2 goto filtered_1433_tcp
if errorlevel = 1 goto failed_1433_tcp
if errorlevel = 0 goto success_1433_tcp
goto 1434_tcp
:filtered_1433_tcp
Echo %1 tcp Port 1433 is listening or filtered
goto 1434_tcp
:failed_1433_tcp
Echo %1 tcp Port 1433 is not listening
Goto 1434_tcp
:success_1433_tcp
Echo %1 tcp Port 1433 is listening
goto 1434_tcp
:1434_tcp
portqry -n %1 -e 1434 -q -p tcp
if errorlevel = 2 goto filtered_1434_tcp
if errorlevel = 1 goto failed_1434_tcp
if errorlevel = 0 goto success_1434_tcp
goto 1024
:filtered_1434_tcp
Echo %1 tcp Port 1434 is listening or filtered
goto 1024
:failed_1434_tcp
Echo %1 tcp Port 1434 is not listening
Goto 1024
:success_1434_tcp
Echo %1 tcp Port 1434 is listening
goto 1024
:1024
portqry -n %1 -e 1024 -q -p tcp
if errorlevel = 2 goto filtered_1024
if errorlevel = 1 goto failed_1024
if errorlevel = 0 goto success_1024
goto 1040
:filtered_1024
Echo %1 tcp Port 1024 is listening or filtered
goto 1040
:failed_1024
Echo %1 tcp Port 1024 is not listening
Goto 1040
:success_1024
Echo %1 tcp Port 1024 is listening
goto 1040
:1040
portqry -n %1 -e 1040 -q -p tcp
if errorlevel = 2 goto filtered_1040
if errorlevel = 1 goto failed_1040
if errorlevel = 0 goto success_1040
goto 1433
:filtered_1040
Echo %1 tcp Port 1040 is listening or filtered
goto 1433
:failed_1040
Echo %1 tcp Port 1040 is not listening
Goto 1433
:success_1040
Echo %1 tcp Port 1040 is listening
goto 1433
:1433
portqry -n %1 -e 1433 -q -p udp
if errorlevel = 2 goto filtered_1433
if errorlevel = 1 goto failed_1433
if errorlevel = 0 goto success_1433
goto end
:filtered_1433
Echo %1 udp Port 1433 is listening or filtered
goto end
:failed_1433
Echo %1 udp Port 1433 is not listening
Goto end
:success_1433
Echo %1 udp Port 1433 is listening
goto end
:End

For what it's worth, I wrote a PowerShell script that does something like this a while back.
http://gallery.technet.microsoft.com/scriptcenter/97119ed6-6fb2-446d-98d8-32d823867131

Assigning Mobile Group to a User

I plan to use the <i>Mobile Group</i> filter for a SyncBO, to avoid too large data volumes on clients - BUT I find it very hard to administer through MEREP_PD and impossible to assign a user to a mobile group in advance of application deployment.
We are dealing with approx. 30 users and they should be allocated to 6 different Mobile Groups. Is there a way to allocate Users to Mobile Groups in advance of application deployment ?
Thanks.
Lars

after creating user in OID (which creates a user for portal also) You shold run the procedure in the portal schema:
PROCEDURE setdefgroup (
p_username varchar2,
p_groupname varchar2) IS
v_group_id number;
BEGIN
v_group_id := WWSEC_API.GROUP_ID
(p_name => upper(p_groupname));
wwsec_api.set_defaultgroup
(p_groupid => v_group_id,
p_username => upper(p_username));
END;
to asign the default group to a user.

Multiple Ports & Mobility Groups

Similar Messages

Maybe you are looking for