Lights Out Management - not accessable outside subnet

Have a new out of the box XServe and have configured the Lights Out Management Card for one interface port. Works great locally and on the same subnet, however, outside the subnet can not connect to it. Server is in a layer 3 environment, does the Lights Out protocol use broadcast packets (as those could be what is being blocked).
Lights Out Port has IP, Subnet mask, and Gateway configured properly (double checked, and triple).
Thanks

i 'believe' LOM does not work outside the local subnet. annoyingly.
not even sure why.
[quote]Using Server Monitor
The Xserve comes with the Server Monitor application. You can find Server Monitor in
/Applications/Server/ and on the Admin Tools disc that comes with the Xserve. You can
use Server Monitor to:
 Check the current status of the Xserve and its components, including
 Drive module status
 Power supply status and system internal voltages
 Network interface status and activity level
 Temperatures of critical internal components
 Cooling fan status
 Review basic Xserve information such as
 Uptime
 Mac OS X Server version running on the Xserve
 Amount and type of memory installed in each slot
 Model and capacity of each drive module
 Shut down, start up, or restart the Xserve
 Generate an Apple System Profiler report for the Xserve
 Send email alerts in response to changes in the status of the Xserve
You can run Server Monitor on the Xserve or on any computer that can connect to the
same network. [/quote]
notice the last line....
if anyone figures anything out i'd be grateful. i thought i'd use the second enet int'fce and configure it for LOM, giving it a second WAN IP, but i abandoned that idea for some reason.. can't remember why that wasn't working....
also, this may help: http://www.afp548.com/article.php?story=20070211101829496
Message was edited by: dtich
Message was edited by: dtich

Similar Messages

  • Asking for Lights out Management?

    Running 10 iMacs & 10 Min Macs.
    We can lock, restart, power off, control, all of that.
    But as soon as we try to power on from shutdown, it comes up with ARD not active, and Lights out management not supported.
    Obviously LOM has been discountinued with Xserve, but has it been integrated somewhere else?
    I dont understand how it can be asking for LOM when it doesn't exist anymore.
    Is there a solution to this? How can we power the mac's on using remote desktop?
    And yes, before you ask, they are intel based.
    Ross.

    Hi
    ". . .  but has it been integrated somewhere else?"
    As of yet, no. It's not clear if Apple ever will? It has only ever been available on Intel XServes only.
    "I dont understand how it can be asking for LOM when it doesn't exist anymore?"
    It's not specifically asking for it as clearly LOM does exist but not on your hardware. ARD supports this feature if you're supporting hardware that does which can only be Intel XServe models.
    "Is there a solution to this? How can we power the mac's on using remote desktop?"
    Yes - you walk round to them and power them on. You can't use ARD to do this. You can however use ARD to send a terminal command that will set a power management schedule that goes some way in doing this for you. Mind you if you're having to go round to them all to switch them on you may as well apply the schedule settings locally. In an ideal world and assuming you have a mac server you can either define the settings you want in the build image you use to push out to rest or apply the settings using MCX.
    Depending which method you use the Macs will have to be switched on at some point.
    Questions specific to ARD are better asked in the dedicated ARD Forum here:
    https://discussions.apple.com/community/servers_enterprise_software/apple_remote _desktop
    HTH?
    Tony

  • Lights-Out Management is not showing full status

    Hi,
    Since I upgraded my Intel XServe to Leopard, I don't get the full Lights-Out Management (LOM) status any more.
    In Server Monitor it is only showing the status for:
    - Power
    - Temperature
    - Blowers
    - Security
    Not the
    - Info
    - Memory
    - Drives
    - Network
    Any idea what's wrong?
    Thanks,
    JO

    http://discussions.apple.com/thread.jspa?threadID=1256863&tstart=0

  • Lights Out Management...

    Hi all,
    I'm having troubles getting LOM to work on my new Intel XServe. During the Setup Assistant, without knowing anything about this feature, I happily skipped setting it up, thinking that it would be easy to enable it later (if deemed useful). The server is installed as a gateway (eth0 is WAN and eth1 is LAN), it is running local DNS, NAT, DHCP, Firewall and I can access the Server Admin and Workgroup Manager remotely using the domain name that points to the server.
    Now when I go to the Server Monitor locally on the server and try to connect via. 127.0.0.1, it seems to connect briefly (i.e. the status lights at the bottom of the app change to green for a second), then the server listing itself disappears from the Server Monitor (i.e. the interface appears that I've never added a server). Now, if I try to add the server again (using the same local credentials), it says that that server has already been configured. The only way to remove this vanishing entry is to relaunch Server Monitor and delete the offending entry in the few seconds before it connects and vanishes again.
    I've tried using the "Setup Local Server" menu option in the Server Monitor, but it's not clear to me what these values should be and everything that I've tried so far doesn't work. Should the port 1 have the same settings as my WAN port and port 2 the same as my LAN port?
    Any help would be appreciated as guessing and testing isn't getting me too far and I'm concerned that by skipping the configuration of LOM in the Setup Assistant, I've made this impossible to turn on now.
    Thanks for any suggestions,
    Mike P

    Thanks for this.
    I've read that Apple doc already (to no avail), but thanks for the link anyways, others might find it useful.
    Just so I understand your suggestion, when configuring Lights Out Management for LAN access, I should use Server Monitor -> Setup Local Server and change port 2 (I assume that port 2 would correspond to eth1 which is my LAN port distributing addresses in the 192.168.1.* range) by picking a valid IP within that range (e.g. 192.168.1.100), and filling in my subnet mask and router information (255.255.0.0 / 192.168.1.1 respectively)? This would then allow access to the server through Server Monitor while connected locally to the LAN via. 192.168.1.100?
    Does this imply that for WAN access to Lights Out Management I would need my ISP to provide me with 2 static IP addresses (one for Lights Out and the other for web / internet services)?
    Thanks again,
    Mike P

  • How Do I Disable Lights Out Management (LOM)?

    I was happily running 10.5 Server yesterday on my Intel XServe. The outside world was able to see my web server just fine.
    I updated to 10.6 Server late last night and now my http service is not visible to the outside world (or local LAN for that matter).
    Suspecting it has something to do with Lights Out Management (LOM).
    How do I get LOM to turn loose of the local IP address of the ethernet interface?

    What makes you think the LOM has anything to do with this?
    There are about two million other things I'd check before I'd worry about the LOM. In fact I can't even think how the LOM could have have effect.
    For a start have you verified the services are running? What do the logs say? Can you hit the web service from the machine itself? What about other services that should be running on the machine?
    Have you checked the network configuration to make sure the server's IP address hasn't changed, that the default route is set correctly?
    Then there are external factors to consider - maybe coincidences that occurred around the same time as your upgrade and may be masking the problem. Have you checked that your port forwarding is set correctly in your router? Are you sure your ISP hasn't started blocking port 80 traffic?

  • Lights Out Management - Crashing / Resetting

    It appears that Light-Out-Management is crashing, and I would like to know if there is a way to restart the LOM controller manually.
    I have a Quad-Core Intel Xeon Xserve (XServe2,1).
    - 2GB of memory (from factory)
    - 80GB boot drive, 1TB drive modules in bays 2 and 3.
    - 1 power supply
    - no expansion cards
    - connected to storage arrays via Firewire 800
    - both ethernet ports are in use, 1 connected to the internal network via gigabit ethernet, the other to the fallback ISP
    I have have configured Lights Out Management via Server Monitor. It typically works well, delivers information, sends notifications when needed. The lights-out management controller seems to crash or stop functioning regularly. I can only tell this has happened when I stop receiving notifications and the machine no longer appears in the Server Monitor list. The network connection to the machine is up and all other services seem to function normally. If I remote into the machine and do "Configure Local Machine" in Server Monitor, I get the marble of doom for about a minute, and when the Configure Local Machine interface does appear, all of the settings are zeroed out. (i.e. 0.0.0.0 for IP, subnet and router. username and password are blank.) Trying to re-enter the settings delivers an unhelpful error.
    Restarting the machine does not help, when it reboots the LOM settings are still zeroed out. However if I shut down the machine and have the power disconnected for a short time (until the back panel lights go out) and then power up the machine, everything goes back to normal.
    This is the only Intel Xserve in the rack, and the only one running 10.5. All the others are G5s running 10.4 or Ubuntu. Server Monitor runs well on the other OS X machines.

    This problem has existed since the Intel Xserve was released. I haven't found a solution yet. The LOM usually comes back when I remove power from both power supplies for 15 seconds or so, but I'm not inclined to shut down my servers as frequently as the LOM quits.
    It would be valuable for us if it worked, since its ipmi compliant.

  • Lights-Out Management Settings - Confusion

    Just installed my new Intel Xserve. There doesn't seem to be any documentation for Lights-Out Management settings. At first I decided to just copy the external and internal network settings for LOM. The assistant didn't accept that. Then I used another real IP numer for the external and different one out of my internal net for the second interface (server internal IP 192.168.2.1 LOM 192.168.2.2). To no avail. Whenever I try to connect to these addresses using server monitor I get no answer from the server.
    Could someone please explain a typical setting for LOM?
    Thank you very much in advance!

    Tim,
    I could not get your suggestion to work. So I called Apple. Together Apple and I could not get it working either.
    So I am back to square one. The biggest problem here folks is the terminology. In the Server Assistant (that runs automatically after the server operating system has been installed) talks about "channels," not ports. I am making the assumption that they are talking about Primary Port and Secondary Port or Port 1 or Port 2. Geez, talk about inconsistency!
    Tim: When you say your "secondary port," I am not sure whether you are referring to Port 2 on the physical server. I don't have an Ethernet cable running to, nor I do intend to, as this should work on Port 1, no?
    I plugged an Ethernet cable into Port 2 of the server and still no dice. I can ping the IP address I put in Server Monitor for LOM on either primary port or "secondary" port from another computer. I just cannot use its IP address on a remote computer to get it working!
    The Apple guy said on the phone that you need to use the LOM IP address, and alluded to the terminal to change it, but also inferred that this can also be done in Server Monitor as Tim spoke about earlier by adding the srever as local host (127.0.0.1).
    Very frustrating... Other than this fault, I am sure that the server works fine, but I would like to have this ironed out before I proceed.
    By the way, the settings for LOM are stored on the logic board and will be automatically filled in if you erase and install the Server Monitor hardware.
    Some one please write if you get this more concretely nailed down, and of course, I will keep everyone apprised if I make any headway get this working.

  • Lights-Out Management Firmware Update

    I tried to execute the Lights-Out Management Firmware Update, which Apple released, today.
    But my Xserve always gives my an error, when I start the update application.
    Lights-Out Management Firmware Update: Bad executable (or shared library)
    Does anybody have the same problem?
    Thanks and Regards,
    JO

    There's a new firmware update out, version 1.1. I tried simply using Software Update but no luck. It seemed to think it installed both 1.0 and 1.1, but all I saw was 1.0, which (still) did not work.
    But I tried something else, and I think this works. I cannot test it until tomorrow when I can actually touch the server (to unplug it).
    Open the Terminal application and do the following (omitting the "% " which I include to indicate the prompt).
    % sudo rm /Applications/Server/Xserve\ Lights-Out\ Management\ Firmware\ Update.app
    % sudo rm /Library/Receipts/LOMUpdate.pkg
    % sudo softwareupdate -i LOMUpdate-1.1
    The last step is important. It should only download the 1.1 updater. This seemed to work for me. that is, it downloaded the 1.1 updater, which I was able to run (from /Applications/Server/). However it tells me I need to shut down and unplug the the Xserve for one minute, then boot up, then install the update. I cannot do that until I'm back at work tomorrow. We'll see!
    --greg
    Message was edited by: Greg Welch

  • Lights-Out-Management - Same or different IP ?

    Hello,
    I manage 5 remote xservers (intel - recent model) which are located in a data center. ARD and remote desktop is fine, but lights-out-management is not working
    reliably.
    Which is the correct way to set it up?
    I have tried two ways:
    A) Configuring LOM to use the same IP as the server itself
    B) Dedicating a different IP to the LOM interface.
    It wasn't working well on (A), so we gave each server a second IP, just for the
    LOM. However in ARD there is no way to add this second IP as part of the machine details in the Edit details window. Just the user/pass details for LOM. If I configure for (B), in Scanner I can see the servers listed by their LOM IP, but they are not responsive to PowerOn, Shutdown etc requests issued from ARD.
    How do others have LOM configured?
    and does it work well for you for remote management?
    Thanks
    Paul

    The LOM needs to have it's own IP. It has to be unique, and ARD expects that it is. "B" is the correct configuration.
    You should add the Server to ARD using the IP address assigned to the server, not the LOM. I believe ARD "asks" the Server what it's LOM IP address is once the LOM username and password is supplied.

  • X2100M2 Embedded LIghts Out Manager best practice

    Hi guys,
    I'm in worry about the best practice of configuring network interface on a X2100M2 Solaris 5.10 for the Embedded LIghts Out Manager. Hope you can help. I haven't find any documents of it which explain the best practice.
    Here is the situation :
    I've have 4 network interfaces but I only need two of them. So I decide to use the bge0 and the bge1 interfaces.
    bge0 is the server interface with an IP with .157
    bge1 is the ELOM interface with an IP with .156
    In the past, it was the reverse : bge0 was the ELOM with .156 and bge1 was the network server int. with .157
    Could you please guys let me know what is the best practice? Does the int.0 must be the server one? Is it possible to have network problem with this kind of configuration?
    Thanks
    Cheers,

    hi guys,
    No one have a clue? I've got some dukeDolars to offer...
    Tks

  • Xserve PowerPC G5: Configuring Lights-Out Management (LOM)

    Can Lights-Out Management be configured using Server Monitor on an Xserve PowerPC G5? Thank you.
    I was wondering because the "Configure Local Machine" feature is disabled.

    Hi,
    I'm afraid the G5 Xserve doesn't have Lights Out. It's a feature only found on the Intel Xserves.
    All the best
    Beatle

  • New Intel Xserve Lights Out Management dies

    Have a new Xserve with LOM. Problem is that after about 1/2 an hour of monitoring with the Server Monitor application from my desktop MacPro the Xserve stops responding via Server Monitor. The only way to get it to work again is to reboot the server. Not good. Anyone else seeing this behavior? Anyone have a fix or can someone from Apple confirm this is a known problem?
    Thanks!

    Ok, Having fought with this for the last 2 days, lack of solid documentation, etc, here's my results:
    First set dns and reversedns (obviously)
    EN0 set to 10.0.1.51
    EN1 Disabled
    ILO1 set to 10.0.1.52
    ILO2 set to 0.0.0.0
    This configuration worked, occasionally, but had numerous "Failed to contact server", and remote ipmitool was SLOW.
    EN0 set to 10.0.1.51
    EN1 Disabled
    ILO1 set to 0.0.0.0
    ILO2 set to 10.0.1.52
    This configuration worked, even less than the first, and remote ipmitool acted slow, but returned nothing.
    EN0 set to 10.0.1.51
    EN1 set to 10.0.1.52
    ILO1 set to 0.0.0.0
    ILO2 set to 10.0.1.52
    This configuration worked, occasionally, but had numerous "Failed to contact server", and remote ipmitool was SLOW.
    EN0 set to 10.0.1.51
    EN1 set to 0.0.0.0 (Static IP, and all fields cleared)
    ILO1 set to 0.0.0.0
    ILO2 set to 10.0.1.52
    This configuration works, consistanly and remote ipmitool was very fast.
    The command I was using to test ipmitool was:
    $ ipmitool -H 10.0.1.52 -U USERNAME -P PASSWORD chassis status
    In addition, I found that ANY changes to the IP for EN1 or ILO1/2 caused the ILO module to get lost, and require a reboot. (unplug method)
    Thus, this is the method I found to get it working, after setting DNS and RDNS for the 2 IP addresses I was to use:
    1) Unplug the power from the XServe for 10 seconds at least (others recommend 30, but I believe that as soon as all lights are off, that's sufficient)
    2) In Network Preferences, set up Built-in Ethernet 1 as you'd like for whatever network access you will need.
    3) In Network Preferences, enable (if off) Built-in Ethernet 2, and clear all fields. IP address will default to 0.0.0.0, Subnet Mask will default to 255.255.255.0, and all other fields will be blank.
    4) In server admin, use "Configure local Machine" to default all values on Port 1 so that IP and gateway are 0.0.0.0 and subnet mask is 255.255.255.0, then switch to Port 2, configure the settings you want the ILO port to use. (do not use the same IP as EN0 obviously).
    5) Set the username and password for the ILO user. (I had NO problems whatsoever with usernames less than 8 characters contrary to reports to this extent) You MUST enter a password again, regardless if it's been set in the past, then apply the settings (authenticate if necessary).
    6) Shutdown, and disconnect the power once more to shutdown ILO.
    7) Boot, make sure the XServe can login to itself at localhost with the ILO login name and password.
    8) On another system on the same subnet, run:
    $ ipmitool -H IPADDRESS -U USERNAME -P PASSWORD chassis status
    (replacing IPADDRESS with the ILO's IP address and USERNAME and PASSWORD with the ones you set in step 5)
    9) if you see something like:
    System Power : on
    Power Overload : false
    Power Interlock : inactive
    Main Power Fault : false
    Power Control Fault : false
    Power Restore Policy : always-on
    Last Power Event : ac-failed
    Chassis Intrusion : inactive
    Front-Panel Lockout : inactive
    Drive Fault : false
    Cooling/Fan Fault : false
    you should be fine, and Server Monitor on the remote system should connect fine.
    The conclusion is that the key to getting this running is in enabling EN1, yet not giving it any TCP configuration.
    Hope this helps someone out there...

  • Could not access two subnets

    Hello,
    We have 2 subnets in differnet locations, both are connected via IPSec VPN, 192.168.1.0  and 192.168.2.0
    Can access 192.168.1.2 to 192.168.2.2 and vice versa but from other IP not possible
    x.x.x.x indicates public ip of HO
    xx.xx.xx.xx indicates public ip of branch
    In HO [192.168.1.0] using cisco 1941 please see the below config
    version 15.2
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    hostname HO
    boot-start-marker
    boot system flash0 c1900-universalk9-mz.SPA.152-2.T.bin
    boot-end-marker
    enable secret 5 $1$OAdT$6oO4MRgeqLLswhYJ1MrQ1/
    no aaa new-model
    no ipv6 cef
    ip auth-proxy max-login-attempts 5
    ip admission max-login-attempts 5
    ip dhcp excluded-address 192.168.1.1
    ip dhcp excluded-address 192.168.1.2 192.168.1.49
    ip name-server x.x.x.x
    ip name-server x.x.x.x
    ip cef
    multilink bundle-name authenticated
    crypto pki token default removal timeout 0
    crypto pki trustpoint TP-self-signed-4155682894
    enrollment selfsigned
    subject-name cn=IOS-Self-Signed-Certificate-4155682894
    revocation-check none
    rsakeypair TP-self-signed-4155682894
    crypto pki certificate chain TP-self-signed-4155682894
    certificate self-signed 01
      3082022B 30820194 A0030201 02020101 300D0609 2A864886 F70D0101 05050030
      31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
      69666963 6174652D 34313535 36383238 3934301E 170D3132 31313231 30323033
      30345A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
      4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D34 31353536
      38323839 3430819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
      8100C569 6AE9BC8C B3151335 D5B65344 CE66C09D 21397F80 B61A1B88 18CD5647
      2C17C13E 6E40BD61 CC40EB38 06C45B2E 9B90346D 93594CFC 104CD1F6 FC00ECA4
      3849440F 81130037 7F4C8600 C59E8B2C 77D40781 55714284 CF3B1622 528A3B56
      4CF2FA62 1AC88250 33C9D8E7 CF868D5F 456C8C03 3D387DD6 BB9F1405 6B713899
      551D0203 010001A3 53305130 0F060355 1D130101 FF040530 030101FF 301F0603
      551D2304 18301680 142A4B7F 1185A51A 72C6E1ED FB8C94A5 60FCA1FD 75301D06
      03551D0E 04160414 2A4B7F11 85A51A72 C6E1EDFB 8C94A560 FCA1FD75 300D0609
      2A864886 F70D0101 05050003 81810071 863A10FA 57C3350F 6D9D47C7 5CAF71FD
      6C7B4E05 001CF020 FDD65D31 0222968A B5992645 89164D80 E3022EA4 2D0A4F66
      5B0FC75D 98C3E547 07612401 FF90AED6 127C186C 6220E15C 7E8BB62A E2C6D151
      09CDE38E FD5F1D4C 4F4137D7 45BE3B8C A6354921 784DD88A 75A95737 46D0BD36
      A83F6B52 74C15C46 37C727ED 1569BC
            quit
    license udi pid CISCO1941/K9 sn FCZ1523C51L
    license boot module c1900 technology-package datak9
    username admin privilege 15 secret 5 $1$nZ..$VIWkm8aaxLSpX1M4EaQrc0
    redundancy
    crypto isakmp policy 2
    authentication pre-share
    crypto isakmp key cisco123 address xx.xx.xx.xx
    crypto ipsec transform-set ASA-IPSEC esp-des esp-sha-hmac
    crypto map SDM_CMAP_1 1 ipsec-isakmp
    set peer xx.xx.xx.xx
    set transform-set ASA-IPSEC
    match address 100
    interface Tunnel0
    no ip address
    interface Embedded-Service-Engine0/0
    no ip address
    shutdown
    interface GigabitEthernet0/0
    description connection to dreamnet
    ip address x.x.x.x 255.255.255.252
    ip nat outside
    ip virtual-reassembly in
    duplex auto
    speed auto
    crypto map SDM_CMAP_1
    interface GigabitEthernet0/1
    description local lan interface $ES_LAN$
    ip address x.x.x.x 255.255.255.248
    ip virtual-reassembly in
    duplex auto
    speed auto
    interface FastEthernet0/1/0
    ip address 192.168.1.7 255.255.255.0
    ip nat inside
    ip virtual-reassembly in
    duplex auto
    speed auto
    ip forward-protocol nd
    ip http server
    ip http authentication local
    ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    ip nat inside source route-map nonat interface GigabitEthernet0/0 overload
    ip route 0.0.0.0 0.0.0.0 x.x.x.x
    access-list 100 remark SDM_ACL category=4
    access-list 100 remark IPSec Rule
    access-list 100 permit ip 192.168.1.0 0.0.0.255 192.168.2.0 0.0.0.255
    access-list 110 deny   ip 192.168.1.0 0.0.0.255 192.168.2.0 0.0.0.255
    access-list 110 permit ip 192.168.1.0 0.0.0.255 any
    route-map nonat permit 10
    match ip address 110
    control-plane
    line con 0
    line aux 0
    line 2
    no activation-character
    no exec
    transport preferred none
    transport input all
    transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
    stopbits 1
    line vty 0 4
    privilege level 15
    login local
    transport input telnet
    scheduler allocate 20000 1000
    end
    In Branch [192.168.2.0] using cisco asa 5510 please see the below config
    ASA Version 8.2(5)
    hostname ciscoasa
    enable password 8Ry2YjIyt7RRXU24 encrypted
    passwd 2KFQnbNIdI.2KYOU encrypted
    names
    interface Ethernet0/0
    nameif Sat
    security-level 0
    ip address 192.168.3.200 255.255.255.0
    interface Ethernet0/1
    nameif Lan
    security-level 100
    ip address 192.168.2.1 255.255.255.0
    interface Ethernet0/2
    shutdown
    no nameif
    no security-level
    no ip address
    interface Ethernet0/3
    shutdown
    no nameif
    no security-level
    no ip address
    interface Management0/0
    nameif management
    security-level 100
    ip address 192.168.10.1 255.255.255.0
    management-only
    ftp mode passive
    clock timezone AST 3
    object-group protocol DM_INLINE_PROTOCOL_1
    protocol-object ip
    protocol-object icmp
    access-list Sat_access_in extended permit object-group DM_INLINE_PROTOCOL_1 host x.x.x.x host xx.xx.xx.xx
    access-list Lan_nat0_outbound extended permit ip any 192.168.2.192 255.255.255.224
    access-list Lan_nat0_outbound extended permit ip 192.168.2.0 255.255.255.0 192.168.1.0 255.255.255.0
    access-list Sat_1_cryptomap extended permit ip 192.168.2.0 255.255.255.0 192.168.1.0 255.255.255.0
    pager lines 24
    logging enable
    logging asdm informational
    mtu Sat 1500
    <--- More --->
    mtu Lan 1500
    mtu Lan1 1500
    mtu management 1500
    ip local pool pool 192.168.2.201-192.168.2.210 mask 255.255.255.0
    no failover
    icmp unreachable rate-limit 1 burst-size 1
    no asdm history enable
    arp timeout 14400
    global (Sat) 1 interface
    nat (Lan) 0 access-list Lan_nat0_outbound
    nat (Lan) 1 0.0.0.0 0.0.0.0
    route Sat 0.0.0.0 0.0.0.0 192.168.3.1 1
    timeout xlate 3:00:00
    timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
    timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
    timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
    timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
    timeout tcp-proxy-reassembly 0:01:00
    timeout floating-conn 0:00:00
    dynamic-access-policy-record DfltAccessPolicy
    http server enable
    http 192.168.10.0 255.255.255.0 management
    http 192.168.1.0 255.255.255.0 Sat
    http x.x.x.x 255.255.255.240 Sat
    <--- More --->
    http xx.xx.xx.xx 255.255.255.0 Sat
    http 192.168.2.0 255.255.255.0 Lan
    no snmp-server location
    no snmp-server contact
    snmp-server enable traps snmp authentication linkup linkdown coldstart
    crypto ipsec transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac
    crypto ipsec transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac
    crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
    crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
    crypto ipsec transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
    crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
    crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
    crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac
    crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
    crypto ipsec transform-set ESP-DES-SHA esp-des esp-sha-hmac
    crypto ipsec security-association lifetime seconds 28800
    crypto ipsec security-association lifetime kilobytes 4608000
    crypto map Sat_map 1 match address Sat_1_cryptomap
    crypto map Sat_map 1 set pfs group1
    crypto map Sat_map 1 set peer x.x.x.x
    crypto map Sat_map 1 set transform-set ESP-DES-SHA
    crypto map Sat_map interface Sat
    crypto ca trustpoint _SmartCallHome_ServerCA
    crl configure
    <--- More --->
    crypto ca certificate chain _SmartCallHome_ServerCA
    certificate ca 6ecc7aa5a7032009b8cebcf4e952d491
        308205ec 308204d4 a0030201 0202106e cc7aa5a7 032009b8 cebcf4e9 52d49130
        0d06092a 864886f7 0d010105 05003081 ca310b30 09060355 04061302 55533117
        30150603 55040a13 0e566572 69536967 6e2c2049 6e632e31 1f301d06 0355040b
        13165665 72695369 676e2054 72757374 204e6574 776f726b 313a3038 06035504
        0b133128 63292032 30303620 56657269 5369676e 2c20496e 632e202d 20466f72
        20617574 686f7269 7a656420 75736520 6f6e6c79 31453043 06035504 03133c56
        65726953 69676e20 436c6173 73203320 5075626c 69632050 72696d61 72792043
        65727469 66696361 74696f6e 20417574 686f7269 7479202d 20473530 1e170d31
        30303230 38303030 3030305a 170d3230 30323037 32333539 35395a30 81b5310b
        30090603 55040613 02555331 17301506 0355040a 130e5665 72695369 676e2c20
        496e632e 311f301d 06035504 0b131656 65726953 69676e20 54727573 74204e65
        74776f72 6b313b30 39060355 040b1332 5465726d 73206f66 20757365 20617420
        68747470 733a2f2f 7777772e 76657269 7369676e 2e636f6d 2f727061 20286329
        3130312f 302d0603 55040313 26566572 69536967 6e20436c 61737320 33205365
        63757265 20536572 76657220 4341202d 20473330 82012230 0d06092a 864886f7
        0d010101 05000382 010f0030 82010a02 82010100 b187841f c20c45f5 bcab2597
        a7ada23e 9cbaf6c1 39b88bca c2ac56c6 e5bb658e 444f4dce 6fed094a d4af4e10
        9c688b2e 957b899b 13cae234 34c1f35b f3497b62 83488174 d188786c 0253f9bc
        7f432657 5833833b 330a17b0 d04e9124 ad867d64 12dc744a 34a11d0a ea961d0b
        15fca34b 3bce6388 d0f82d0c 948610ca b69a3dca eb379c00 48358629 5078e845
        63cd1941 4ff595ec 7b98d4c4 71b350be 28b38fa0 b9539cf5 ca2c23a9 fd1406e8
        18b49ae8 3c6e81fd e4cd3536 b351d369 ec12ba56 6e6f9b57 c58b14e7 0ec79ced
    <--- More --->
        4a546ac9 4dc5bf11 b1ae1c67 81cb4455 33997f24 9b3f5345 7f861af3 3cfa6d7f
        81f5b84a d3f58537 1cb5a6d0 09e4187b 384efa0f 02030100 01a38201 df308201
        db303406 082b0601 05050701 01042830 26302406 082b0601 05050730 01861868
        7474703a 2f2f6f63 73702e76 65726973 69676e2e 636f6d30 12060355 1d130101
        ff040830 060101ff 02010030 70060355 1d200469 30673065 060b6086 480186f8
        45010717 03305630 2806082b 06010505 07020116 1c687474 70733a2f 2f777777
        2e766572 69736967 6e2e636f 6d2f6370 73302a06 082b0601 05050702 02301e1a
        1c687474 70733a2f 2f777777 2e766572 69736967 6e2e636f 6d2f7270 61303406
        03551d1f 042d302b 3029a027 a0258623 68747470 3a2f2f63 726c2e76 65726973
        69676e2e 636f6d2f 70636133 2d67352e 63726c30 0e060355 1d0f0101 ff040403
        02010630 6d06082b 06010505 07010c04 61305fa1 5da05b30 59305730 55160969
        6d616765 2f676966 3021301f 30070605 2b0e0302 1a04148f e5d31a86 ac8d8e6b
        c3cf806a d448182c 7b192e30 25162368 7474703a 2f2f6c6f 676f2e76 65726973
        69676e2e 636f6d2f 76736c6f 676f2e67 69663028 0603551d 11042130 1fa41d30
        1b311930 17060355 04031310 56657269 5369676e 4d504b49 2d322d36 301d0603
        551d0e04 1604140d 445c1653 44c1827e 1d20ab25 f40163d8 be79a530 1f060355
        1d230418 30168014 7fd365a7 c2ddecbb f03009f3 4339fa02 af333133 300d0609
        2a864886 f70d0101 05050003 82010100 0c8324ef ddc30cd9 589cfe36 b6eb8a80
        4bd1a3f7 9df3cc53 ef829ea3 a1e697c1 589d756c e01d1b4c fad1c12d 05c0ea6e
        b2227055 d9203340 3307c265 83fa8f43 379bea0e 9a6c70ee f69c803b d937f47a
        6decd018 7d494aca 99c71928 a2bed877 24f78526 866d8705 404167d1 273aeddc
        481d22cd 0b0b8bbc f4b17bfd b499a8e9 762ae11a 2d876e74 d388dd1e 22c6df16
        b62b8214 0a945cf2 50ecafce ff62370d ad65d306 4153ed02 14c8b558 28a1ace0
        5becb37f 954afb03 c8ad26db e6667812 4ad99f42 fbe198e6 42839b8f 8f6724e8
    <--- More --->
        6119b5dd cdb50b26 058ec36e c4c875b8 46cfe218 065ea9ae a8819a47 16de0c28
        6c2527b9 deb78458 c61f381e a4c4cb66
      quit
    crypto isakmp identity address
    crypto isakmp enable Sat
    crypto isakmp enable Lan
    crypto isakmp policy 10
    authentication crack
    encryption aes-256
    hash sha
    group 2
    lifetime 86400
    crypto isakmp policy 20
    authentication rsa-sig
    encryption aes-256
    hash sha
    group 2
    lifetime 86400
    crypto isakmp policy 30
    authentication pre-share
    encryption aes-256
    hash sha
    group 2
    lifetime 86400
    <--- More --->
    crypto isakmp policy 40
    authentication crack
    encryption aes-192
    hash sha
    group 2
    lifetime 86400
    crypto isakmp policy 50
    authentication rsa-sig
    encryption aes-192
    hash sha
    group 2
    lifetime 86400
    crypto isakmp policy 60
    authentication pre-share
    encryption aes-192
    hash sha
    group 2
    lifetime 86400
    crypto isakmp policy 70
    authentication crack
    encryption aes
    hash sha
    group 2
    lifetime 86400
    <--- More --->
    crypto isakmp policy 80
    authentication rsa-sig
    encryption aes
    hash sha
    group 2
    lifetime 86400
    crypto isakmp policy 90
    authentication pre-share
    encryption aes
    hash sha
    group 2
    lifetime 86400
    crypto isakmp policy 100
    authentication crack
    encryption 3des
    hash sha
    group 2
    lifetime 86400
    crypto isakmp policy 110
    authentication rsa-sig
    encryption 3des
    hash sha
    group 2
    lifetime 86400
    <--- More --->
    crypto isakmp policy 120
    authentication pre-share
    encryption 3des
    hash sha
    group 2
    lifetime 86400
    crypto isakmp policy 130
    authentication crack
    encryption des
    hash sha
    group 2
    lifetime 86400
    crypto isakmp policy 140
    authentication rsa-sig
    encryption des
    hash sha
    group 2
    lifetime 86400
    crypto isakmp policy 150
    authentication pre-share
    encryption des
    hash sha
    group 2
    lifetime 86400
    <--- More --->
    crypto isakmp policy 170
    authentication pre-share
    encryption des
    hash sha
    group 1
    lifetime 86400
    telnet xx.xx.xx.xx 255.255.255.224 Sat
    telnet 192.168.10.0 255.255.255.0 management
    telnet timeout 5
    ssh xx.xx.xx.xx 255.255.255.224 Sat
    ssh timeout 5
    console timeout 0
    dhcpd address 192.168.2.101-192.168.2.200 Lan
    dhcpd dns 192.168.2.2 8.8.8.8 interface Lan
    threat-detection basic-threat
    threat-detection statistics access-list
    no threat-detection statistics tcp-intercept
    webvpn
    enable Sat
    svc enable
    group-policy DfltGrpPolicy attributes
    vpn-tunnel-protocol IPSec l2tp-ipsec svc webvpn
    group-policy KKKK_1 internal
    <--- More --->
    group-policy KKKK_1 attributes
    dns-server value 8.8.8.8
    vpn-tunnel-protocol IPSec
    group-policy KKKK internal
    group-policy KKKK attributes
    vpn-tunnel-protocol svc webvpn
    webvpn
      url-list none
      svc ask enable
    username aslam password ZB9WJGrSUPUGLGwR encrypted privilege 0
    username aslam attributes
    vpn-group-policy KKKK
    username aslu password /3qnLbX8e8tM0LIe encrypted
    tunnel-group KKKK type remote-access
    tunnel-group KKKK general-attributes
    address-pool pool
    default-group-policy KKKK_1
    tunnel-group KKKK-1 type remote-access
    tunnel-group KKKK-1 general-attributes
    address-pool pool
    tunnel-group x.x.x.x type ipsec-l2l
    tunnel-group x.x.x.x ipsec-attributes
    pre-shared-key *****
    <--- More --->
    class-map inspection_default
    match default-inspection-traffic
    policy-map type inspect dns preset_dns_map
    parameters
      message-length maximum client auto
      message-length maximum 512
    policy-map global_policy
    class inspection_default
      inspect dns preset_dns_map
      inspect ftp
      inspect h323 h225
      inspect h323 ras
      inspect rsh
      inspect rtsp
      inspect esmtp
      inspect sqlnet
      inspect skinny 
      inspect sunrpc
      inspect xdmcp
      inspect sip 
      inspect netbios
      inspect tftp
    <--- More --->
      inspect ip-options
    service-policy global_policy global
    prompt hostname context
    call-home reporting anonymous
    Cryptochecksum:a0d50431d7d29fd35edf9fcabfa4434b
    : end
    Hope anybody can help on this matter...

    What network/s do you want to access?
    From what network do you want to access it/them?

  • Is the integrated lights out manager supporting snmpd or just traps?

    Hi,
    we have a x4200 here and are pretty fine with it. But we woul'd like to ask the ilom for some information via snmp. I now that snmp exists on the ilom there. I created an user-account just fine and there's also a port I can choose (161) and the version of snmp (v3). Everything fine so far but I can't connect to it.
    Neither telnet nor nmap show an open port 161? So I can't connect to it with snmpwalk or things like that.
    What am I missing? Is ilmo not supporting snmp but just thos traps things? Any idea what I could have done wrong? As said in the webinterface of ilom everything looks okay it's just the port is not open so I guess snmpd is not running there.

    Usually, there is a router/firewall between your servers and the rest of the internet. For example, this is how we do this: We use a subnet seperat from the ones we use for the operating system itself and only allow access to this subnet via VPN tunnels. That way, all those management interfaces are not accessible from the outside and we don't have to worry about attacks against them.

  • Lights Out Management IP/Hardware Address

    I've got LOM working with a unique IP adress on Port 2. The internet is connected on Port 1, and the LAN on Port 2. Since Xserve is also serving as a router and as a DHCP server, I'd like to block out the LOM IP address from the DHCP pool by giving it a static IP address. If I do this, what MAC address do I need to asign to it? If I use the MAC address for the ethernet port, won't this foul up all the LAN services which are using a different IP address on the same ethernet port to get to the services?
    XServe   Mac OS X (10.4.8)  

    > The static IP address assignment pane in the X-Serve Server Admin software will not lock out an IP address unless a MAC address is given
    That's the wrong approach and not what that feature is designed for.
    The 'static addresses' in DHCP are used to assign the same IP address to a given machine so that when that MAC device requests an IP address, it gets a consistent answer. The LOM shouldn't use DHCP, so putting in the DHCP static table is moot.
    Instead you should use a specific range of IP addresses for dynamic hosts and a separate set for static devices (including LOM), making sure the two do not overlap.
    For example, if you're using the subnet 192.168.123.0/24, you could use something like 192.168.123.1 through 192.168.123.200 for DHCP addresses, and 192.168.123.201 through 192.168.123.254 as static addresses (including things like your router, LOM devices, etc.). Of course you can vary the ranges according to whether you have more DHCP or static devices in your network, and if you start from opposite ends (e.g. start the static devices at .254 and work downwards), you can always adjust the split without major impact (e.g. lower to .150 if you find that 54 static addresses isn't enough, or raise it to .220 if you need more DHCP addresses and you haven't reached that far down with static devices).
    Since the DHCP server doesn't assign anything over .200, it doesn't need to know anything about devices that have static addresses.
    This approach has the advantage that if you change your DHCP server at any time (e.g. delegate the task to your firewall) you don't have to worry about re-entering all the MAC addresses for those static devices. In addition, if your DHCP server fails for any reason, you still know where your critical devices are on the network.

Maybe you are looking for