VWLC clients getting DHCP address from management VLAN
Hi,
We have a strange scenario whereby some wireless employees are obtaining addresses from the management VLAN.
Some details:
DHCP managed by MS DHCP 2008 R2 (in remote data centre)
Cisco vWLC AIR-CTVM-K9 running v7.6.110.0
AP's are a mix of 2602 and 3702 (46 and 2 of each respectively)
SSID's are employee, guest, and production devices (all mapped to their own interface with relevant VLAN tag as per normal)
AP's all in FlexConnect mode as per vWLC caveats
Some employees are receiving addresses in the wireless management VLAN. This network only has six DHCP addresses available as it is solely for AP's, WLC and HSRP gateway. Obviously this gets exhausted very quickly leaving us with a scenario where clients are not obtaining DHCP addresses.
I understand that with FlexConnect mode, it will assign IP's from the native VLAN. What I don't understand is why most clients receive addresses in the correct VLAN, but a handful do not, and then cannot get an address from DHCP. Obviously the ideal scenario would be to put the AP's into local mode but unless this has changed in a SW release then I don't believe it's possible...
My question is: How do I get ALL the employees to obtain addresses from their interface and not the management VLAN?
Thanks in advance.
Hi,
I think we need a closer look to your configurarion to eliminate some possibilities:
- What is the WLAN security you choose?
- What is the interface that is configured under the WLAN?
- Does your WLAN have local switching enabled?
- If your security is using RADIUS server, do you have AAA override enabled under the WLAN config?
- If your security is using RADIUS server, do you send any attributes to the users?
- You have eliminate that clients that got management vlan IPs are always on same AP or they can be on any AP.
HTH
Amjad
Similar Messages
-
Wireless Clients getting DHCP IP from other WLAN
Hi,
My client has a wireless setup consisting of a WLC 2112 and about 7 1131AG LWAPPs. There are two SSIDs, say CORP(mapped to VLAN 900) and GUEST(mapped to VLAN 901). Wireless clients get IP through DHCP. DHCP IP is configured in the Dynamic interface.
The problem is sometimes (not always), clients connecting to SSID CORP get a DHCP IP assigned for GUEST VLAN(VLAN 901).
Since it is happening randomly, clueless as to what is causing the problem.
Any inputs?
Regards
Gnan.
P.S Just to add though this could be irrelevant, only after making VLAN ID of the admin interface and AP Manager interface as '0', the APs could talk to the WLC and i was able to http to the WLC from the LAN.(WLC Mgmt, AP Mgmt IPs and AP Manager interface are in same VLAN).It sounds like the client may be connecting to the guest WLAN first, then connecting to the Corp WLAN.
As to the VLAN setting. 0 in the WLC means untagged. If your switchport has the switchport trunk native valn < x > command you would need to be untagged. Otherwise the switch would get a packet tagged with the native vlan, and then drop the traffic.
***if your management is in VLAN 1, the above is true with out the native setting, as VLAN 1 is native by default
HTH,
Steve
Please remember to rate helpful posts or to mark the question as answered so that it can be found later. -
Linksys WRT54GL won't get dhcp address from isp
I'm using Linux.
I just bought this router because it had good reviews on Newegg but for the past 4 hours I have gotten nowhere with it.
When I connect the router to the net and click the refresh button on the browser interface, the router doesn't go out and get a dhcp address. I see the initial click of the mouse that hits the modem but no information comes back. No addresses are updated.
I have tried cloning the mac address but that does no good either.
Any hints appreciated.
ThanksTry resetting the router for 30 secs in such a way that power light is blinking on the router.Also, try doing the complete network power cycle i.e., unplug the power cables from the modem & from the router.Then, plug in the power cable to the modem first once all the lights are solid on the modem you could plug in the power cable to the router & then try configuring the router & it will definately work!!!
-
Mac mini server refuses to get DHCP address from router
Everything was going along fine. But after a power outage the server goes to a 169. address when the router puts out 198. addresses. If I put a static 198. address in it sees the network but won't connect to the internet. I've flashed the router (everything else sees the router fine, 3 computers and a time capsule). I've had the hardware checked at the Apple store - it picked up an address right away. After narrowing everything down the problem has to be in the operating system. I even did a full time machine restore to the day before the storm. No luck. Anyone heard of this problem.
Mauricette has a point.
A server function is not designed to accept a floating or dynamic IP address. If that is the case, how do you create firewall rules that prevent those unnnecessary ports being left opened from being attacked by rogue machines in Romania and China on a hourly basis when you announce to the world that your server is available if the server IP address keep changing due to the DHCP lease change? Yes, they do have bots that do this VERY EFFICIENTLY!
By changing the very nature of your firewall rules by working with DHCP, you are opening ports you do not know to accommodate DHCP dynamic addressing, which was the reason why your Mac Mini Server stopped working in the first place. It's ok for a client, since a client isn't serving any files to any one right.
By using client based firewall rules, you are exposing your server to attacks and when they get through your Mini server, which they can if they are persistent, they get into your home network and then whatever file server services you have opened and unprotected at the time WILL BE copied by these people easily.
I have a client once who did just that. She was attacked, the hacker went through her network like a rampaging bull. They were from China. My Synology RAID server gets this attack all the time, but I have a well establish IDS system and the Synology RAID has logs that tracks attacks.
For a server setup. Use static IP and then build a strong firewall around it and protect it and never compromise.
Recently, I just noticed someone somehow hacked and broke my WPA-PSK AES passkey for one of my Wireless N network router. It was not set up with a strong password though, but thankgod I had a firewall around that so my internal networks were safe. So this teaches you that if someone wants in bad, they will get in.
Hope this helps. -
WiSM having trouble getting the IP from service-vlan DHCP
WiSM WLAN Service Module WS-SVC-WISM-1-K9 in 6509e running VSS IOs s72033-ipservicesk9_wan-mz.122-33.SXI2a.bin having trouble to get the IP from service-vlan DHCP.
The pertinent config is as follows.
vlan 300
name WiSM_Service_Vlan
interface Vlan300
description *** WiSM Service-Vlan
ip address 192.168.200.1 255.255.255.0
ip dhcp excluded-address 192.168.200.1
ip dhcp pool WiSM_Service-Vlan_300
network 192.168.200.0 255.255.255.0
default-router 192.168.200.1
wism service-vlan 300
vlan 183
name WiSM_Management
interface Vlan183
description *** WiSM Management Vlan ***
ip address 10.39.139.254 255.255.255.0
wism switch 1 module 4 controller 1 allowed-vlan 125,126,183,300
wism switch 1 module 4 controller 2 allowed-vlan 125,126,183,300
wism switch 2 module 4 controller 1 allowed-vlan 125,126,183,300
wism switch 2 module 4 controller 2 allowed-vlan 125,126,183,300
wism switch 1 module 4 controller 1 native-vlan 183
wism switch 1 module 4 controller 2 native-vlan 183
wism switch 2 module 4 controller 1 native-vlan 183
wism switch 2 module 4 controller 2 native-vlan 183
HO2NET0001#sh wism status
Service Vlan : 300, Service IP Subnet : 192.168.200.1/255.255.255.0
WLAN
Slot Controller Service IP Management IP SW Version Status
----+-----------+----------------+----------------+-----------+---------------
20 1 0.0.0.0 0.0.0.0 Service Port Up
20 2 0.0.0.0 0.0.0.0 Service Port Up
HO2NET0001#sh module
Mod Ports Card Type Model Serial No.
1 8 CEF720 8 port 10GE with DFC WS-X6708-10GE SAL13442Q5N
2 8 CEF720 8 port 10GE with DFC WS-X6708-10GE SAL13442GAL
3 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL13410N8P
4 10 WiSM WLAN Service Module WS-SVC-WISM-1-K9 SAD133101UY
5 5 Supervisor Engine 720 10GE (Active) VS-S720-10G SAL13442JE4
Mod MAC addresses Hw Fw Sw Status
1 0025.84f1.55b8 to 0025.84f1.55bf 2.1 12.2(18r)S1 12.2(33)SXI2 Ok
2 0025.84f1.4e58 to 0025.84f1.4e5f 2.1 12.2(18r)S1 12.2(33)SXI2 Ok
3 0027.0da7.c240 to 0027.0da7.c26f 3.2 12.2(18r)S1 12.2(33)SXI2 Ok
4 0023.5e25.7168 to 0023.5e25.7177 2.3 12.2(14r)S5 12.2(33)SXI2 Ok
5 001f.9e2a.2608 to 001f.9e2a.260f 3.1 8.5(3) 12.2(33)SXI2 Ok
Mod Sub-Module Model Serial Hw Status
1 Distributed Forwarding Card WS-F6700-DFC3C SAL13442EG9 1.4 Ok
2 Distributed Forwarding Card WS-F6700-DFC3C SAL13442H9T 1.4 Ok
3 Centralized Forwarding Card WS-F6700-CFC SAL13442HU9 4.1 Ok
4 Centralized Forwarding Card WS-SVC-WISM-1-K9-D SAD133200D6 2.1 Ok
5 Policy Feature Card 3 VS-F6K-PFC3C SAL13442E5S 1.1 Ok
5 MSFC3 Daughterboard VS-F6K-MSFC3 SAL13421AJZ 2.0 Ok
Mod Online Diag Status
1 Pass
2 Pass
3 Pass
4 Pass
5 Pass
HO2NET0001#sh vlan
300 WiSM_Service_Vlan active Gi1/4/9, Gi1/4/10
The service IP is supposed to have been populated with an address from the dhcp pool. I am also unable to connect to it by doing a session switch 1 slot 4 processor 1. I get the following upon attempting to do so:
HO2NET0001##session switch 1 slot 4 proc 1
The default escape character is Ctrl-^, then x. You can also type 'exit' at the remote prompt to end the session Trying 0.0.0.0 ...
Any assistance or ideas offered will be greatly appreciated.
Thanks,wired client is working & able to get IP from vlan 300 DHCP pool.
Here is the complete configuration.
Core-Switch6509#sh run
Building configuration...
Current configuration : 21462 bytes
upgrade fpd auto
version 12.2
service timestamps debug datetime msec
service timestamps log datetime msec
service counters max age 5
hostname
boot-start-marker
boot system flash sup-bootdisk:
boot-end-marker
security passwords min-length 1
logging buffered 8192
no aaa new-model
ip subnet-zero
ip dhcp excluded-address 192.168.200.1 192.168.200.2
ip dhcp pool wism-service-port
network 192.168.200.0 255.255.255.0
default-router 192.168.200.1
ip dhcp pool voiceFLR1
network 10.39.103.128 255.255.255.128
default-router 10.39.103.254
option 150 ip 10.39.139.240 10.39.139.241
ip dhcp pool voiceFLR2
network 10.39.104.128 255.255.255.128
default-router 10.39.104.254
option 150 ip 10.39.139.240 10.39.139.241
ip dhcp pool voiceFLR3
network 10.39.105.128 255.255.255.128
default-router 10.39.105.254
option 150 ip 10.39.139.240 10.39.139.241
no ip domain-lookup
vtp domain
vtp mode transparent
switch virtual domain 100
switch mode virtual
mls netflow interface
mls cef error action reset
spanning-tree mode pvst
spanning-tree extend system-id
wism service-vlan 300
wism switch 1 module 4 controller 1 allowed-vlan 125,126,183,300
wism switch 1 module 4 controller 2 allowed-vlan 125,126,183,300
wism switch 2 module 4 controller 1 allowed-vlan 125,126,183,300
wism switch 2 module 4 controller 2 allowed-vlan 125,126,183,300
wism switch 1 module 4 controller 1 native-vlan 183
wism switch 1 module 4 controller 2 native-vlan 183
wism switch 2 module 4 controller 1 native-vlan 183
wism switch 2 module 4 controller 2 native-vlan 183
diagnostic bootup level minimal
redundancy
main-cpu
auto-sync running-config
mode sso
vlan internal allocation policy ascending
vlan dot1q tag native
vlan access-log ratelimit 2000
vlan 101
name Grd_FLR_Data_Vlan
vlan 102
name Grd_FLR_Voice_Vlan
vlan 103
name MZ_FLR_Data_Vlan
vlan 104
name MZ_FLR_Voice_Vlan
vlan 105
name 1st_FLR_Data_Vlan
vlan 106
name 1st_FLR_Voice_Vlan
vlan 107
name 2nd_FLR_Data_Vlan
vlan 108
name 2nd_FLR_Voice_Vlan
vlan 109
name 3rd_FLR_Data_Vlan
vlan 110
name 3rd_FLR_Voice_Vlan
vlan 111
name 4th_FLR_Data_Vlan
vlan 112
name 4th_FLR_Voice_Vlan
vlan 113
name 5th_FLR_Data_Vlan
vlan 114
name 5th_FLR_Voice_Vlan
vlan 115
name 6th_FLR_Data_Vlan
vlan 116
name 6th_FLR_Voice_Vlan
vlan 117
name 7th_FLR_Data_Vlan
vlan 118
name 7th_FLR_Voice_Vlan
vlan 119
name 8th_FLR_Data_Vlan
vlan 120
name 8th_FLR_Voice_Vlan
vlan 121
name 9th_FLR_Data_Vlan
vlan 122
name 9th_FLR_Voice_Vlan
vlan 123
name 10th_FLR_Data_Vlan
vlan 124
name 10th_FLR_Voice_Vlan
vlan 125
name Wireless_Users
vlan 126
name Wireless_Guest
vlan 150
name Printer
vlan 151
name v151
vlan 152
name v152
vlan 153
name v153
vlan 154
name v154
vlan 155
name v155
vlan 183
name Network_Management
vlan 300
name WiSM_Service_Vlan
interface Port-channel1
description *** For 1st Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel2
description *** For 2nd Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel3
description *** For 3rd Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel4
description *** For 4th Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel5
description *** For 5th Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel6
description *** For 6th Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel7
description *** For 7th Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel8
description *** For 8th Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel9
description *** For 9th Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel10
no switchport
no ip address
switch virtual link 1
mls qos trust cos
no mls qos channel-consistency
interface Port-channel11
description *** For 10th Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel12
description *** For Ground Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel13
description *** For MZ Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel20
no switchport
no ip address
switch virtual link 2
mls qos trust cos
no mls qos channel-consistency
interface TenGigabitEthernet1/1/1
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
shutdown
interface TenGigabitEthernet1/1/2
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
shutdown
interface TenGigabitEthernet1/1/3
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 1 mode on
interface TenGigabitEthernet1/1/4
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 2 mode on
interface TenGigabitEthernet1/1/5
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 3 mode on
interface TenGigabitEthernet1/1/6
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 4 mode on
interface TenGigabitEthernet1/1/7
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 5 mode on
interface TenGigabitEthernet1/1/8
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 6 mode on
interface TenGigabitEthernet1/2/1
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 7 mode on
interface TenGigabitEthernet1/2/2
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 8 mode on
interface TenGigabitEthernet1/2/3
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 9 mode on
interface TenGigabitEthernet1/2/4
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 11 mode on
interface TenGigabitEthernet1/2/5
description *** Connected to Juniper Port Ten 0 Inside ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
switchport nonegotiate
interface TenGigabitEthernet1/2/6
no switchport
no ip address
interface TenGigabitEthernet1/2/7
no switchport
no ip address
interface TenGigabitEthernet1/2/8
no switchport
no ip address
interface GigabitEthernet1/3/1
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet1/3/2
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet1/3/3
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet1/3/4
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet1/3/5
switchport
switchport access vlan 154
interface GigabitEthernet1/3/6
switchport
switchport access vlan 154
interface GigabitEthernet1/3/7
switchport
switchport access vlan 154
interface GigabitEthernet1/3/8
switchport
switchport access vlan 154
interface GigabitEthernet1/3/9
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/10
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/11
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/12
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/13
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/14
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/15
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/16
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/17
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/18
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/19
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/20
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/21
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/22
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/23
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/24
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/25
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/26
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/27
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/28
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/29
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/30
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/31
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/32
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/33
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/34
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/35
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/36
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/37
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/38
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/39
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/40
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/41
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/42
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/43
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/44
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/45
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/46
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/47
switchport
switchport access vlan 107
switchport mode access
spanning-tree portfast edge
interface GigabitEthernet1/3/48
switchport
switchport access vlan 152
switchport mode access
interface GigabitEthernet1/5/1
no switchport
no ip address
shutdown
interface GigabitEthernet1/5/2
no switchport
no ip address
shutdown
interface GigabitEthernet1/5/3
no switchport
no ip address
shutdown
interface TenGigabitEthernet1/5/4
description *** Connected to CS-2 Port Ten 2/5/4 ***
no switchport
no ip address
mls qos trust cos
channel-group 10 mode on
interface TenGigabitEthernet1/5/5
description *** Connected to CS-2 Port Ten 2/5/5 ***
no switchport
no ip address
mls qos trust cos
channel-group 10 mode on
interface TenGigabitEthernet2/1/1
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
shutdown
interface TenGigabitEthernet2/1/2
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
shutdown
interface TenGigabitEthernet2/1/3
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 1 mode on
interface TenGigabitEthernet2/1/4
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 2 mode on
interface TenGigabitEthernet2/1/5
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 3 mode on
interface TenGigabitEthernet2/1/6
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 4 mode on
interface TenGigabitEthernet2/1/7
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 5 mode on
interface TenGigabitEthernet2/1/8
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 6 mode on
interface TenGigabitEthernet2/2/1
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 7 mode on
interface TenGigabitEthernet2/2/2
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 8 mode on
interface TenGigabitEthernet2/2/3
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 9 mode on
interface TenGigabitEthernet2/2/4
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 11 mode on
interface TenGigabitEthernet2/2/5
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface TenGigabitEthernet2/2/6
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface TenGigabitEthernet2/2/7
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface TenGigabitEthernet2/2/8
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface GigabitEthernet2/3/1
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet2/3/2
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet2/3/3
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet2/3/4
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet2/3/5
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/6
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/7
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/8
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/9
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/10
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/11
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/12
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/13
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/14
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/15
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/16
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/17
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/18
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/19
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/20
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/21
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/22
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/23
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/24
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/25
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/26
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/27
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/28
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/29
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/30
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/31
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/32
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/33
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/34
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/35
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/36
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/37
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/38
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/39
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/40
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/41
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/42
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/43
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/44
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/45
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/46
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/47
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/48
no switchport
no ip address
shutdown
interface GigabitEthernet2/5/1
no switchport
no ip address
shutdown
interface GigabitEthernet2/5/2
no switchport
no ip address
shutdown
interface GigabitEthernet2/5/3
no switchport
no ip address
shutdown
interface TenGigabitEthernet2/5/4
description *** Connected to CS-1 Port Ten 1/5/4 ***
no switchport
no ip address
mls qos trust cos
channel-group 20 mode on
interface TenGigabitEthernet2/5/5
description *** Connected to CS-1 Port Ten 1/5/5 ***
no switchport
no ip address
mls qos trust cos
channel-group 20 mode on
interface Vlan1
no ip address
interface Vlan101
description *** Grd Floor Data Vlan ***
ip address 10.39.101.126 255.255.255.128
interface Vlan102
description *** Grd Floor Voice Vlan ***
ip address 10.39.101.254 255.255.255.128
interface Vlan103
description *** MZ Floor Data Vlan ***
ip address 10.39.102.126 255.255.255.128
interface Vlan104
description *** MZ Floor Voice Vlan ***
ip address 10.39.102.254 255.255.255.128
interface Vlan105
description *** 1st Floor Data Vlan ***
ip address 10.39.103.126 255.255.255.128
interface Vlan106
description *** 1st Floor Voice Vlan ***
ip address 10.39.103.254 255.255.255.128
interface Vlan107
description *** 2nd Floor Data Vlan ***
ip address 10.39.104.126 255.255.255.128
interface Vlan108
description *** 2nd Floor Voice Vlan ***
ip address 10.39.104.254 255.255.255.128
interface Vlan109
description *** 3rd Floor Data Vlan ***
ip address 10.39.105.126 255.255.255.128
interface Vlan110
description *** 3rd Floor Voice Vlan ***
ip address 10.39.105.254 255.255.255.128
interface Vlan111
description *** 4th Floor Data Vlan ***
ip address 10.39.106.126 255.255.255.128
interface Vlan112
description *** 4th Floor Voice Vlan ***
ip address 10.39.106.254 255.255.255.128
interface Vlan113
description *** 5th Floor Data Vlan ***
ip address 10.39.107.126 255.255.255.128
interface Vlan114
description *** 5th Floor Voice Vlan ***
ip address 10.39.107.254 255.255.255.128
interface Vlan115
description *** 6th Floor Data Vlan ***
ip address 10.39.108.126 255.255.255.128
interface Vlan116
description *** 6th Floor Voice Vlan ***
ip address 10.39.108.254 255.255.255.128
interface Vlan117
description *** 7th Floor Data Vlan ***
ip address 10.39.109.126 255.255.255.128
interface Vlan118
description *** 7th Floor Voice Vlan ***
ip address 10.39.109.254 255.255.255.128
interface Vlan119
description *** 8th Floor Data Vlan ***
ip address 10.39.110.126 255.255.255.128
interface Vlan120
description *** 8th Floor Voice Vlan ***
ip address 10.39.110.254 255.255.255.128
interface Vlan121
description *** 9th Floor Voice Vlan ***
ip address 10.39.111.126 255.255.255.128
interface Vlan122
description *** 9th Floor Voice Vlan ***
ip address 10.39.111.254 255.255.255.128
interface Vlan123
description *** 10th Floor Voice Vlan ***
ip address 10.39.112.126 255.255.255.128
interface Vlan124
description *** 10th Floor Voice Vlan ***
ip address 10.39.112.254 255.255.255.128
interface Vlan150
description *** Printer Vlan ***
ip address 10.39.120.254 255.255.255.0
interface Vlan151
description *** Connected to Juniper FW Port Ten 0 ***
ip address 10.39.121.1 255.255.255.240
interface Vlan183
description *** Network Management Vlan ***
ip address 10.39.139.254 255.255.255.0
interface Vlan300
ip address 192.168.200.1 255.255.255.0
ip classless
ip route 0.0.0.0 0.0.0.0 10.39.140.169
ip route 0.0.0.0 0.0.0.0 10.39.121.14
no ip http server
no ip http secure-server
control-plane
dial-peer cor custom
line con 0
login local
line vty 0 4
login local
line vty 5 15
login local
mac-address-table aging-time 480
no event manager policy Mandatory.go_switchbus.tcl type system
module provision switch 1
slot 1 slot-type 227 port-type 60 number 8 virtual-slot 17
slot 2 slot-type 227 port-type 60 number 8 virtual-slot 18
slot 3 slot-type 147 port-type 61 number 48 virtual-slot 19
slot 4 slot-type 242 port-type 31 number 10 virtual-slot 20
slot 5 slot-type 254 port-type 31 number 2 port-type 61 number 1 port-type 60 number 2 virtual-slot 21
module provision switch 2
slot 1 slot-type 227 port-type 60 number 8 virtual-slot 33
slot 2 slot-type 227 port-type 60 number 8 virtual-slot 34
slot 3 slot-type 147 port-type 61 number 48 virtual-slot 35
slot 4 slot-type 242 port-type 31 number 10 virtual-slot 36
slot 5 slot-type 254 port-type 31 number 2 port-type 61 number 1 port-type 60 number 2 virtual-slot 37
end
Thanks & Awaiting for response. -
Configuring DNS when clients get DHCP from a Windows server
Hi
I'm getting to grips with OD and have managed to configure a test environment at home with static IPs and all the DNS entries being entered manually for each computer.
However, how do I configure the DNS in an environment where clients get their IPs from a Windows DHCP server (which I have no access to)?
Setting clients to have static IPs is not an option nor enabling DHCP on the Mac server, I suspect.
Your help is really appreciated.
SteveHi
Your suspicion is correct.
To be honest I would what is available on the Windows Server as the basis for your Open Directory deployment. If the Windows Server is already the DHCP Server odds are it is also the DNS Server. DNS can be provided to your clients using the Windows based DHCP service.
If you have no direct access to the windows server you should be able at the least ask the windows administrator to add a Host Record with a Reverse Pointer for the OSX Server. Make sure its resolving correctly first using the relevant tools first then add the IP address of the Windows Server in the network preferences pane on your OSX Server. Thereafter you should be able to promote from Standalone to Open Directory Master without too many problems.
If the Windows Server is using .local as its FQDN then it could scupper any chances you have of providing OSX LDAP services to your mac clients. It can work with .local, its just better if its not used.
Hope this helps – Tony -
Cannot get a DHCP address from my ISP
I just got a WRT54G router, I managed to configured it all. I can ping any computers on the network. What I cannot do is get my DHCP address from my isp, meaning that I can't connect to internet.
I am 100% sure that my ISP address was given by a DHCP server since that's how it was configured on my old router before it got smashed into pieces.
I have the latest firmware upgrade for the router (version 6) and it is correctly plugged in my modem.
What is strange is that couple of hours ago, I managed to get an address for about 15 minutes, then it dropped and I have not been able to pick a new one anymore, no matter what I do.
Anyone can help me?Achnod wrote:
Alright, but how do I do that?
Disconnect the power cord.
Or if its a telephony modem, hold the reset button until it reboots. -
Windows will not get a DHCP address from my OS X Server
Is there a trick I need to do to get my windows machines to get and address from my OS X Server?
i have had the same issue. Windows clients (XP, 2003, 7) just could not receive an address from the dhcp server.
I think i got it solved by removing an invalid line in my dhcp server config file.
This is what i did:
stop dhcp server
open /etc/bootpd.plist (you need admin rights to edit)
remove the following two lines:
<key>dhcp_domain_name</key>
<string></string>
save file
start dhcp server again
alternatively, you can fill the dhcp_domain_name with a valid domain name suffix. Both options seem to have worked just fine for me.
<key>dhcp_domain_name</key>
<string>whatever.mydomain.com</string>
Tips:
I am using Sublime Text for such tasks. It asks for administrator password when trying to save the file, much more convinient than trying to use TextEdit
To get to the /etc directory from your favorite text editor easily: Go to the standard open file dialog. Press Cmd+Shift+G. Type /etc and press enter
also see the official documentation:
https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/ man8/bootpd.8.html
dhcp_domain_name
The default DNS domain name (option code 15). If this property is not
present, the server will supply its own default domain name (if available). -
No Hyperv Virtuals get DHCP address - but Physical Host Can
HyperV Server 2012 Core on a dedicated machine on local domain.
Machine connected directly into local network that has a DC running DHCP.
None of the VM's can get a DHCP Address from the server. Even if i set static addresses still they cannot route anywhere, cannot even ping the HyperV server they are sat on but other local machines can!!!!
The physical host cant ping the
The physical HyperV server has no problem getting a DHCP address or any routing issues, nor do any of the other clients on the local network, including another HyperV server running server VM's
What ive tried so far
Deleted Virtual Switch and removed the NIC from the virtual hosts in HyperV Manager- then re-adding new one.
Put in a different network card
Removed Physical host from Domain, renamed machine to different name and re-joined
Used different IP addresses for the Physical host
Reloaded the HyperV server from scratch and created new VM.
Ive had HyperV previously running on this machine without problem, so now i cant see why i cant get it running again.
Anybody have any suggestions on what i can try next, im all out of ideas.Hi Fulgent,
I am assuming that , the hyper-v server have two NICs , one for host and the other one was configured as an external switch for VMs .
If the VMs can not access the dhcp and local network , please try to delete the external switch then uninstall the Physical NIC in device manager and click " scan for hardware changes " to reload it.
Try to create external virtual switch for VMs again .
Any further information please feel free to let us know .
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
How to get IP address from login screen in 10.7 Lion
Hi All,
In 10.7 I didn't find any option to get IP address from login screen as used to got in 10.4,10.5,10.6
ThanksJason,
is there any way to make that example
work with release 6.0, preverribly
with IE5 (native VM)?
The WHEN-CUSTOM-ITEM-EVENT Trigger
doesn't seem to fire.
Thanks
Anton Weindl
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Jason Pepper ([email protected]):
If you are using web deployed forms then you need to use a javabean to obtain the IP of the local machine - you can get one that does it here..
http://technet.oracle.com/sample_code/products/forms/listing.htm#pjcexamp
If you are running client server then there is a utility in d2kwutil.pll that allows you to read the registry and do things like get the IP address. d2kwutil is shipped with your copy of Forms - just have a look for it - the code is self documenting, but there is also a manual you can read too.
Jason Pepper
Principal Product Manager
Enterprise Internet Tools
Oracle Corp<HR></BLOCKQUOTE>
null -
How can I get the address from a map struct?
Hello,
Who knows how to get the address from a map struct, and what's the meaning of the eighth argument (addr) of ufs_getpage() ?
I developed a modular to encrypt certain files. The approach is: I�fll change the vnode's v_op pointer when opening a file which should be decoded. I make the vnode->v_op point to my own ops struct. I made a new ufs_getpage function like below:
static int newufs_getpage(struct vnode* vp, offset_t off, size_t len,
uint_t* protp, page_t* plarr[], size_t plsz,
struct seg* seg, caddr_t addr, enum seg_rw rw,
struct cred* cr)
call old ufs_getpage(vp, off, len, protp, plarr, plsz, seg, addr, rw, cr);
decode the page.
After reading some source code about kernel, I know the plarr is the page which is read from the disk. But I don't know how to get the address of the page. I tried like below, but failed.
caddr_t baseaddr;
page_t *pp;
pp = plarr[0];
�c�c
baseaddr = hat_kpm_page2va(pp, 0);
�c�c
I logged the baseaddr:
cmn_err(CE_NOTE, �gbaseaddr %s�h, baseaddr);
or
char _buff[8];
int _len;
copyinstr(baseaddr, buff, 8, &len);
cmn_err(CE_NOTE, �gbaseaddr %s�h, _buff);
But I found the baseaddr is not what I want. Is there something wrong with my approach? What's the meaning of the eighth argument (addr) of ufs_getpage()
By the way, is there any documents concerning to the functions such as segvn_fault�Appmapin/ppmapout except the source code?Hiya,
I think the address is the faulting address in segmap.
But why not have a look at the file event management framework in NFSv4:
http://cvs.opensolaris.org/source/xref/on/usr/src/uts/common/fs/fem.c
To support NFSv4 delegation, FEM provides hooks to intercept filesystem operations.
Maybe you could use that to implement what you want? Probably safer than doing what you are doing now. Go see fem_install().
Cheers,
R.
Message was edited by:
ralphyt -
2611XM refuses to grab a DHCP address from an upper router.
HI, first time here. Im a homeschooled student and trying to work on getting a CCNA. I ran into an issue which puts me in a stopping point. I have a Cisco 2611XM router in which im trying to pass internet traffic to a few select computers. The problem is the WAN (fa0/1) will not get an address from the d-link router which is handing out dhcp addresses to all my computers in the main network. Ive watched lots of youtube videos but only to validate Ive used the same methods they did. SO here is a quick run down of the topology.
cable modem>dlink router>cisco2611XM>dumbSwitch>Computer#3
> >LinksysSLMG224G 24 port switch>computers 1,2
As you can see my network splits off from the dlink into what needs to be 2 networks.
So why cant I get the WAN interface of the 2611XM to grab a dhcp address?
config
secureROUTER#sh run
Building configuration...
Current configuration : 1031 bytes
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname secureROUTER
boot-start-marker
boot-end-marker
enable secret 5 $1$fq4Z$ty8gmQfFw6v0sM2O0rW2D1
no network-clock-participate slot 1
no network-clock-participate wic 0
no aaa new-model
ip subnet-zero
ip cef
no ip domain lookup
interface FastEthernet0/0
description LAN
ip address 10.0.0.1 255.255.255.0
ip nat inside
duplex auto
speed auto
no cdp enable
interface FastEthernet0/1
description WAN
ip address dhcp
ip nat outside
no ip route-cache cef
no ip route-cache
duplex auto
speed auto
no cdp enable
ip nat inside source list 1 interface FastEthernet0/0 overload
no ip http server
ip classless
ip route 0.0.0.0 0.0.0.0 FastEthernet0/1
access-list 1 permit 10.0.0.0 0.0.0.255
no cdp run
banner motd ^CGet the fuck out!!^C
line con 0
line aux 0
line vty 0 4
password 7 111B1F5244000D
logging synchronous
login
endDuplicate post.
Go HERE. -
1811W router unable to get DHCP IP from Speedstream 4100
I have a Yahoo-ATT DSL installation with 1 dynamic IP address. It uses an ISP supplied speedstream 4100 DSL modem. The 4100 appears to take care of all the PPOE duties and DHCP connections from PCs or low-end routers (I'm temporarily using a NetGear unit) work fine.
BUT, when I swap the Netgear out for my new 1811W, the cisco unit is unable to obtain a DHCP address from the modem. I can see the request on the modem lights when I do a "no shutdown fastethernet0"...but I never get an IP address.
The speedstream appears to support 100Mbps and I have tried 100, 10 and Auto on the 1811W. I can look at the log on the modem and it does not show any activity by the modem's dhcp service. However, when I swap back to the netgear unit, I can see appropriate entries in the modem log.
The 1811 is new and I strongly suspect its working ...I tested it on a different DSL line that had static IP. I see a number of similar issues in this forum; but have not seen any resolution that seems to fit my situation.
Any help/suggestions would be appreciated...my next step will be log the DHCP packets with a sniffer. I think I know what I"ll see...1811W DHCP broadcast...no response. But, that won't help me resolve the issue.
Thanks,
Chuck McPHi, this would a config example once you configure the dsl modem for bridging:
http://www.cisco.com/en/US/tech/tk175/tk15/technologies_configuration_example09186a0080126dc0.shtml
look at the 2600 part. you can omit these commands that are for older versions:
vpdn enable
no vpdn logging
vpdn-group 1
request-dialin
protocol pppoe
Hope this helps, please rate post if it does! -
How to get MAC address from IP address in LAN
Hi all,
How to get MAC address from IP address in LAN (windows or any OS), I would have all IP addresses of my LAN, so I would like to know all MAC address.
Code examples are highly appreciated.
Thanks & Regards,
abel...abel wrote:
Yeah that is only working for local system, but how to get remote system's MAC ..?
Thanks for quick reply ...
Edited by: abel on Jan 28, 2009 12:10 AMIt is my understanding that only one person ever found the holy grail which you seek. But sadly [_he's dead_|http://forums.sun.com/profile.jspa?userID=649366]
As a curious aside how did you manage to get the list of IPs? -
AEX fails to get DHCP address, but works on DLink
Sorry for the long post -- I'm hoping the details will help you diagnose the problem faster in the long run.
My DLink router gets a DHCP IP address from the (Comcast) cable modem, but when I switch to the AirPort Extreme (5th gen, refurbished), it doesn't. It shows an autoconfiguration IP address of the 169.254 variety, suggesting that DHCP isn't working for the AEX. (Just fyi, my girlfriend's macbook can connect to the AEX and get 10.0.1.x IP addresses; I can ping the AEX over wifi.)
Airport Utiltiy shows a red number 2 with a single error indicating Internet failure to get IP address or something. The suggested solution is power-cycling the modem; failing that, contact the ISP. Contacting Comcast was amusing but useless...they gave me instructions for setting up AEX with a DSL modem -- twice -- without understanding my objection!
The AEX is configured for DHCP (not Static or PPPoE), and uses all stock settings (I did both a soft reset and used the Airport Utility to restore default settings...not sure if those two are the same).
I've tried power-cycling the router and cable modem numerous times, including leaving them off for 15+ minutes and leaving the AEX connected for 6+ hours. I tried using the DLink to release the DHCP reservation and then quickly switching the cable over to the AEX.
I read somewhere that resetting the "CMTS (cable modem termination system)" might help. I mentioned it to the Comcast tech support, but they didn't respond.
At this point, I'm not sure what else to try. It could be the refurbished unit is broken, but 95% of the time these sorts of things are configuration issues. (I know a fair amount about networking, but I'm new to Apple products so I could be doing something stupid.) I may try connecting the AEX to the LAN side of the DLink to see if it can get a DHCP address from that...but I'm clearly grasping at straws.
<whimpers>...Help?Update: The AEX does get a DHCP address when connected to the LAN side of the DLink gateway. (But the AEX doesn't get one when connected directly to the cable modem. Yet the DLink gets a DHCP address when connected to the cable modem.) So...??!?!!!
Maybe you are looking for
-
After upgrading to ios6 my iphone will not open .xls files in emails with the default viewer. Is there a fix for this? The same emailed .xls files still open on my ipad using ios5 while viewing email like they did on my iphone prior to upgrading. I h
-
There's a purple line on my iMac screen. How can I fix it? Is my LCD screen damaged?
-
Why does the line width of a printed chart/graph vary from the on screen width? Thanks CM
-
What is the BOL Attribute struc for CN- CHANNELCONTEXT in MKTPRJ_COMMCHNL?
Component Name: MKTPRJ_COMMCHNL View: MKTPRJ_COMMCHNL/OVEFChannels Context Node: CHANNELCONTEXT What is the BOL Attribute struc for CN- CHANNELCONTEXT in Component MKTPRJ_COMMCHNL? I want to enhance this structure to add a new checkbox attribute and
-
Hi, I stumbled over some strange behavior.... I tried to register a TestStand ActiveX callbacks, but I'm facing multiple problems: My first attempt for assigning the callback VI was the right-click "Create Callback VI" which brings then up a template