[N5K] in-band management issue

Hi there,
Due to security guidelines we only want to use the mgmt0-Interface as EOOB for managament traffic (ssh, ntp, snmp, aaa, ...).
So, based on NX-OS config/command ref.-guides in-band management access has to be explicitly enabled by using the 'management' keyword during SVI configuration, 'no management' is the interface default.
We thought this would be a pretty cool feature, because it secures the management plane to be accessed from produktion vlans, without using ACL.
But, surprisingly we were able to ssh to an produktion SVI on an N5K running 6.0.2n24 during a lab-session yesterday!
Is this only a software bug in the current release oder are we missing something?
(I had no chance the check against our N7K yet)
TIA,
Michael

The guide goes on to state that, "although the CLI does not prevent you from configuring routing protocols on a management SVI, we recommend that you do not configure them on management SVIs."
It seems to me that this management VLAN feature gives you the option of configuring a management VRF without the need for purchasing an OSI Layer 3 license for the N5K.
Don't forget to rate all helpful posts.

Similar Messages

  • Out-of-Band provisioning issue

    Hi there,
    I'm migrating from Configmanager 2007 to 2012 SP1 at a customer.
    With CM 2007 I'd succesfully implemented Out-of-band management. Now I'm having some issues with provisioning AMT from CM2012.
    The testing machines have never been provisioned with CM2007.
    The oobmgmt.log at the client logs succesful activated the device.
    At the server in the amtopmgr.log file the follwoing error is logged:
    Error: Can NOT get OTP from target device (MachineId = 16777220)
    I know this has to do with a one time password that is generated...I dont know where I have to look to resolve this issue.
    Part of the amtopmgr logfile:
    >>>>>>>>>>>>>>>Provision task (In Band Provision) begin<<<<<<<<<<<<<<<    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:23  
     5268 (0x1494)
    Provision target is indicated with SMS resource id. (MachineId = 16777220 DSK-0925.water.intern)    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:23    5268 (0x1494)
    Found valid basic machine property for machine id = 16777220.    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:23    5268 (0x1494)
    Warning: Currently we don't support mutual auth. Change to TLS server auth mode.    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:23    5268 (0x1494)
    The provision mode for device DSK-0925.water.intern is 1.    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:23    5268 (0x1494)
    The IP addresses of the host DSK-0925.water.intern are 10.10.128.76.    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:23    5268 (0x1494)
    Root hash of provisioning certificate is 2796BAE63F1801E277261BA0D77770028F20EEE4.    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:23    5268 (0x1494)
    Attempting to establish connection with target device using SOAP.    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:23    5268 (0x1494)
    Create provisionHelper with (Hash: FD16D8C6A482C73C12832BC19D5BCABD4460D5A3)    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:23    5268 (0x1494)
    Set credential on provisionHelper...    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:23    5268 (0x1494)
    Try to use provisioning account to connect target machine 10.10.128.76...    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:23    5268 (0x1494)
    Core version of target machine 10.10.128.76 is: 9.0.3.    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:24    5268 (0x1494)
    Succeed to connect target machine 10.10.128.76 using provisioning account #0.    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:24    5268 (0x1494)
    GeneralInfo.GetProvisioningState finished with HResult = 0x0, status = 0x0, clientErr = 0.    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:24    5268 (0x1494)
    Get device provisioning state is In Provisioning    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:24    5268 (0x1494)
    Error: Can NOT get OTP from target device. (MachineId = 16777220)    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:25    5268 (0x1494)
    CStateMsgReporter::DeliverMessages - Queued message: TT=1201 TIDT=0 TID='Unspecified' SID=13 MUF=0 PCNT=1, P1='DSK-0925.water.intern' P2='' P3='' P4='' P5=''    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:25    5268
    (0x1494)
    CStateMsgReporter::DeliverMessages - Created state message file: C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\ikjsq3c0.SMX    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:25  
     5268 (0x1494)
    >>>>>>>>>>>>>>>Provision task (In Band Provision) end<<<<<<<<<<<<<<<    SMS_AMT_OPERATION_MANAGER    28-10-2013 13:34:25  
     5268 (0x1494)
    Anyone has a good idea?
    Thanks in advance.
    Mark

    Hi Mark,
    I am experiencing the same issue you are, but only with one machine. I have over 1000 machines that have successfully provisioned, so it's a bit of a mystery at the moment.
    I have confirmed that my failing machine does have a OTP in the SCCM database by running the following query:
    select MachineID ,OTP from dbo.AMT_MachineProperties where HostName = '<machine name>'
    This shows a OTP for each machine, but I'm still having trouble with this one. Did you ever find a solution?
    Thanks,
    Russel

  • Question about creating Certificates for Out of Band management

    I would like to use out of band management for supporting clients in remote offices.  I am following the instructions at http://technet.microsoft.com/en-us/library/230dfec0-bddb-4429-a5db-30020e881f1e#BKMK_AMT2008_cm2012 in the "Deploying Certificates
    for AMT" section.  It says:
    If you cannot complete steps 18 or 19, check that you are using the Enterprise Edition of Windows Server 2008. Although you can configure templates with Windows Server Standard Edition and Certificate Services, you cannot deploy certificates using modified
    certificate templates unless you are using the Enterprise Edition of Windows Server 2008.
    My Certificate Authority server is Server 2008R2 Standard.  When I right click on Certificate Templates -> New -> Certificate Template to Issue, I do not see the ConfigMgr AMT Provisioning and ConfigMgr AMT Web Server Certificates.  I know
    the box says 2008 Standard isn't supported, but I am using 2008R2 Standard, not 2008.  Why am I not able to see either certificate.  If it is because I am using the Standard Edition, than how can I create the certificates needed?  Upgrading
    to Enterprise is not an available solution (cost reasons).  Does this mean that OOB management certificate creation is not supported on Server 2008R2 Standard, and so I will not be able to use ConfigMgr 2012 SP1 for out of band management because I am
    unable to generate the required certificates?

    Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
    In order to use the cert template, you must use an Enterprise version of Windows. Only the Enterprise (or datacenter) version have the right version of the Certificate server.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • SCCM out of band management

    SCCM has out of band managment ability, and it has a check box:
    "Enable BIOS password bypass for power on and restart command"
    I am not sure the meaning of BIOS passwrod since we could set both power on password and hdd password in BIOS.
    It means we could bypass both power on password and hdd password?

    Anoop,
    Will you help by explaining on this in detail?
    Kindly let me know which is the best ipmi tool to be used to display the server
    hardware details in SCOM management packs while I have to monitor at least 300 servers. I am aware of IPMITool.exe. IPMIUtil.exe etc. Same time,
    I am concerned about following points:
    1. Performance impact in a agent based system
    2. Performance impact in a agentless scom system
    3. Performance impact if the executable is running only in SCOM server
    4. Retrieving data out of band directly from BMC while OS is not running
    5. Is there any solution to avoid binding issues with BMC when concurrent calls are
       made by such tools to retrieve out of band inventory (IPMI) details.
       How to handle binding issues?
    regards
    scomdev
    SCOMDev

  • Out of Band Management (D-Link modem)

    Hi Guys,
    I have an issue with the Out of Band Management.
    It works with most of our routers, but it doesn't work with routers with new IOS.
    The IOS version of our new routers is 15.0(1)M2.
    The configuration of all the routers' Aux port is below:
    line aux 0
    exec-timeout 3 0
    modem InOut
    transport input all
    stopbits 1
    flowcontrol hardware
    The configuration of the d-link modem is below:
    ats0=1
    ats2=127
    ats37=9
    ate1
    atq1
    at&c1
    at&d2
    at&s1
    at&k0
    at&r0
    I tried different configuration combinations without any luck.
    The diagnostic reason I'm getting from the D-link modem is:
    DIAG <2A4D3263 0=10>      ß   Diagnostic Command Specification revision number
    DIAG <2A4D3263 1=00>     ß   Call Setup Result code  =  No previous call
    DIAG <2A4D3263 60=50>   ß   Termination Cause  =  AnyKeyAbort Call Control
    Disconnect Type
    Disconnect Reason Code
    Description
    3
    0x007
    The AT dial command was aborted . The AT dial command was aborted by the any key abort command. For example, the host modem originates a call. During connection establishment, prior to STEADY STATE, pressing any key will cause the AT dial command to be aborted.
    Disconnect Type
    Disconnect Type (Hex)
    Description
    3
    0x6...
    Condition occurred during call setup.
    Has any of you guys dealt with this issue before?
    I would appreciate it if you can share it.
    Thanks,
    Regards,

    tray cable with this scheme of pin connector
    RJ45 DB9
    1 7
    2 4
    3 3
    4 5
    5 5
    6 2
    7 1
    8 8
    init string at&F1S0=1

  • The Ultimate Guide to Resolving Profile and Device Manager Issues

    The following article also applies to issues after re-setting the severs' hostname. It also applies to situations where re-setting the Code Signing Certifictateas described by Apple has not resolved the issue.
    Hello,
    I have been plagued with Profile Manager and Device Manager issues since day one.
    I would like to share my experience and to suggest a way how to resolve issues such as device cannot be enrolled or Code Signing Certificate not accepted.
    I shall try to be as brief as possible, just giving an overview of the steps that resolved my issues. The individual steps have been described elsewhere in this forum. For users who have purchased commercial SSL certs the following may not apply.
    In my view many of these issues are caused by missing or faulty certificates. So let us first touch on the very complex matter of certificates.
    Certificates come in many flavours such as CA (Certificate Authority), Code Signing Certificate, S/MIME and Server Identification.
    (Mountain?) Lion Server creates a so-called Intermediate CA certificate (IntermediateCA_hostname_1") and Server Identification Certificate ("hostname") when it installs first. This is critical for the  operation of many server functionalities, including Open Direcory. These certs together with the private/public keys can be found in your Keychain. Profile  and Device Manager may need a Code Signing Certificate.
    The most straightforward way to resolve the Profile Manaher issues is in my view to reset the server created certicates.
    The bad news is that this procedure involves quite a few steps and at least 2 hours of your precious time because it means creating a fresh Direcory Master.
    I hope that I have not forgotten to mention an important step. Readers' comments and addenda are welcome.
    I shall outline a sensible strategy:
    1. Clone your dysfunctional server to an external harddrive (SuperDuper does a reliable job)
    2. Start the server fom the clone and shut down ALL services.
    3. It may be sensible to set up a root user access.
    4. Back-up all user data such as addess book, calendar and other data that you *may* need to set up your server.
    5. Open Workgroup Manager and export all user and workgroup accounts to the drive that you using to re-build your server (it may cause problems if you back-up to an external drive).
    6. Just in case you may also want to back-up the Profile Manager database and erase user profiles:
    In Terminal (this applies to Lion Server - paths may be diferent in Mountain Lion !)
    Backup: sudo pg_dump -U _postgres -c device_management > $HOME/device_management.sql
    Erase database:
    sudo /usr/share/devicemgr/backend/wipeDB.sh
    7. Note your Directory (diradmin) password for later if you want to re-use it.
    8. Open Open Server Admin and demote OD Master to Standalone Directory.
    9. In Terminal delete the old Certificate Authority
    sudo rm -R /var/root/Library/Application\ Support/Certificate\ Authority/
    This step is crucial because else re-building you OD Master will fail.
    9. Go back to Server Admin and promote the Standalone Directory to OD Master. You may want to use the same hostname.
    10. When the OD Master is ready click on Overview and check that the LDAP and Keberos Realm reflect your server's hostname.
    11. Go back to Workgroup Manager and re-import users and groups.
    NOTE: passwords are not being exported. I do not know how to salvage user passwords. (Maybe passwords can be recovered by re-mporting an OD archive - comments welcome! ).
    12. Go to Server App and reset passwords and (not to forget) user homefolder locations, in particular if you want to login from a network account!
    If the home directory has not been defined you cannot login from a network account.
    13. You may now want to restore Profile Manager user profiles in Terminal. Issue the following commands:
    sudo serveradmin stop devicemgr
    sudo serveradmin start postgres
    sudo psql -U _postgres -d device_management -f $HOME/device_management.sql
    sudo serveradmin start devicemgr
    14. You can now switch back on your services, including Profile Manager.
    In Profile Manager you may have to configure Device Management. This creates a correct Code Signng Certicate.
    15. Check the certificate settings in Server App -> Hadware -> Settings-> SSL Certificates.
    16. Check that Apple Push Notifications are set.(you easily check if they are working later)
    17. You may want to re-boot OS Server from the clone now.
    18. After re-boot open Server App and check that your server is running well.
    19. Delete all profiles in System Preferences -> Profiles.
    19. Login to Profile Manager. You should have all users and profiles back. In my experience devices have to be re-enrolled before profiles can be pushed and/or devices be enrolled. You may just as well delete the displayed devices now.
    20. Grab one of your (portable) Macs that you want to enrol and go to (yourhostname)/mydevices and install the server's trust profile. The profile's name  should read "Trust Profile for...) and underneath in green font "Verified".
    21. Re-enrol that device. At this stage keep your finger's crossed and take a deep breath.
    22. If the device has been successfully enrolled you may at last want to test if pushing profiles really works. Login to Profile Manager as admin, select the newly enrolled device. Check that Automatic Push is enabled (-> Profile -> General). Create a harmless management profile such as defining the dock's position on the target machine. (Do not forget to click SAVE at the end - this is easily missed here). If all is well Profile Manager will display an active task (sending) and the dock's position on the target will have changed in a few seconds if you are on a LAN (Note: If sending seems to take forever: check on the server machine and/or on your router that the proper ports are open and that incoming data is not intercepted by Little Snitch or similar software).
    Note: if you intend to enrol an Apple iPhone you may first need to install the proper Apple Configuration software.
    Now enjoy Profile and Device Manager !
    Regards,
    Twistan

    HI
    1. In Action profiles, logon to system and recheck correcion are available in action definition as well in condition configuration and the schedule condition is also maintained. but the display is not coming(i.e in the worklist this action is not getting displayed).
    You can check the schedule condition for the action and match the status values...or try recreating the action with schedule condition again....for customer specific ....copy the standard aciton with ur zname and make a schedule condition and check the same.
    2, In suppport team of incident when i give individual processor it throwing a warning that u r not the processor. but when i give org unit it is working perfectly. Could anyone guide on this.
    You need to have the empolyee role for BP ..goto BP and got here dropdown for ur bp and choose role Employee and then enter ur userid
    also make sure that u have the message processing role
    Hope it clarifies ur doubt and resolve ur prob
    Regards
    Prakhar

  • Power Mac G5 DP1.8GHz - Bad Logic Board or Power Management Issue?

    I have a Power Mac G5 DP1.8GHz/1.5GB/80GB which I bought non-working. It has not yet been disassembled or examined by a certified tech. This is it's issue (which replicates): the computer powers on. It makes a single warning tone, then the LED flashed at least 15 times (too fast to count). Then the posting chord is heard. Hard drive spins up. Then nothing (no video). Won’t boot from any disk. I have changed the RAM and tested the RAM banks with known-to-be-good RAM from another DP1.8GHz G5. The warning tone stopped once or twice after this switch, but then it didn’t chime. I changed the PRAM battery, but not with as new one. However, after installing the used one and then resetting the PMU, it displayed video briefly for the first time. While installed in the other 1.8GHz G5, the hard drive was formatted, given a clean install of OS X 10.4.11, and then moved into this computer where is never mounts. The computer is not accessible through TDM.
    Do I have a bad logic board? Bad CPUs? A power managment issue? A RAM issue?

    Through my own trial and error troubleshooting, I have found the CPUs to be in good working order and the logic board passes the Apple Service Diagnostic every time. Despite the installation of numerous pairs of modules that worked in another DP1.8GHz, the computer has a RAM issue-it gives the "no good RAM" tone most of the time when it powers up (after a PMU reset it does not). Also the computer boots from disk or into Open Firmware but the disk utility can't see either hard drive so I may have a bad SATA controller.

  • Color Management issues with Illustrator

    Can someone help me figure out the color management issues I'm getting when printing on an Epson 3880 from Illustrator?
    The image comes out severely red as evident on the face. I'm not getting the same problem when printing from Photoshop, even though I set same paper profile in printing dialog box.
    I attached two printed picture (one from Photoshop CC, and one from Illustrator CC) that I took with my iphone so that you can see the printed result.  Even when I try to simulate same thing using illustrator soft proofing process, the soft proof does not show me anything close to how it gets printed out. And I tried all device simulations to see if any would match it. Im using  CMYK SWOP v2 for Color space in both programs.

    Dougfly,
    Only an hour wasted? Lucky you. Color is an incredibly complex subject. First, forget matching anything to the small LCD on the back of your camera. That's there as a basic guide and is affected by the internal jpg algorithm of your camera.
    2nd, you're not really takeing a color photo with your digital camera, but three separate B&W images in a mosaic pattern, exposed thru separate red, green and blue filters. Actual color doesn't happen until that matrix is demosaiced in either your raw converter, or the in-camera processor (which relies heavily on camera settings, saturation, contrast, mode, etc.)
    Having said the above, you can still get very good, predictable results in your workflow. I have a few color management articles on my website that you might find very helpful. Check out the Introduction to Color Management and Monitor and Printer Profiling. In my opinion, a monitor calibration device is the minimum entry fee if you want decent color.
    http://www.dinagraphics.com/color_management.php
    Lou

  • In-Band Management Software for StorageTek 2530

    I'm trying to install the software needed for in-band management for a StorageTek 2530 SAS Array. Page 83 of Sun StorageTek Common Array Manager Software Installation Guide, 820-2934-10, list the following needed for Linux x86_64
    Linux:
    &#9632; SMagent-LINUX-90.00.A0.06-1.ia64.rpm
    &#9632; SMruntime-LINUX-90.10.A0.02-1.ia64.rpm
    I have downloaded SMagent-LINUX-90.00.A0.06-1.ppc64.rpm on the Sun website but I cannot find SMruntime-LINUX-90.10.A0.02-1.ia64.rpm
    Does anyone know where I can download it from?
    Thanks

    Download Sun StorageTek Common Array Manager In-Band Proxy Agent Packages 6.0.0 for Red Hat Enterprise Linux 4, English
    Download Information and Files
         Get the latest Java Runtime Environment to use Sun Download Manager
    Internet Explorer Users: Check the top of this page for a "Java(TM) Web Start ActiveX Control" message in the information bar. If it appears, click it to finish detecting your Java version.
    We were unable to detect a recent version of Java Runtime Environment (JRE) on your system. With the latest JRE, you can automatically download, install, and run Sun Download Manager (SDM) directly from this page. We highly recommend SDM to easily manage your downloads (pause, resume, restart, verify, and more). Visit java.com for the latest JRE.
    Sun StorageTek Common Array Manager 6.0 Documentation
    Sun StorageTek 2500 Arrays Documentation
    Sun StorageTek 6140 and 6540 Arrays Documentation
    Instructions: Select the files you want, then click the "Download Selected with Sun Download Manager" (SDM) button below to automatically install and use SDM (learn more). Alternately, click directly on file names to download with your browser. (Use of SDM is recommended but not required.)
    Your download should start automatically.
    If not, click the file link below.
    Sun Download Manager(SDM) installation should begin automatically.
    Once it is running, click Start to download the product.
    If your system does not support SDM, click the file link below to download.
    (For help with SDM, see SDM Troubleshooting.)
    Required Files Select All      File Description and Name      Size
         CAM 6.0 In-Band Management Installation Document
    InBand_Installation.html      25.95 KB
         CAM 6.0 In-Band Management Release Notes
    RELEASE_NOTES.txt      7.81 KB
    Optional Files Select All      File Description and Name      Size
         Agent for Linux running on ia64 (Intel Itanium) processors
    SMagent-LINUX-90.00.A0.06-1.ia64.rpm      0.45 MB
         Agent for Solaris SPARC platforms
    SMagent-SOL-90.00.00.06.pkg      1.77 MB
         Runtime package for Solaris SPARC platforms
    SMruntime-SOL-10.10.02.00.pkg      95.59 MB
         Agent for Linux running on Power PC 64-bit processors
    SMagent-LINUX-90.00.A0.06-1.ppc64.rpm      0.45 MB
         Agent for Linux running on 386 platform (AMD & Intel)
    SMagent-LINUX-90.00.A0.06-1.i386.rpm      0.45 MB

  • Setting up in-band management

    The problem I'm encountering is very similar to the following post " [In-Band Management configuration for 2530 array from T5120 on Solaris 10|http://forums.sun.com/thread.jspa?forumID=831&threadID=5338514] "
    Running the command java -classpath /opt/SMgr/agent/SMagent.jar devmgr.versioned.agent.DeviceIdentifier does not return any LUNs with Volume Access.
    SANtricity Storage Manager Devices, Version 90.00.00.06
    Built Wed May 23 09:02:26 CDT 2007
    Copyright (C) 1999-2007 LSI Logic Corporation. All rights reserved.
    /dev/rdsk/c8t600A0B800048A6A80000102D48A98B38d0s2 [Storage Array 6140, Volume groups1, LUN 1, Volume ID <600a0b800048a6a80000102d48a98b38>, Preferred Path (Controller-A): In Use]
    /dev/rdsk/c8t600A0B80004898B8000007B948A98A5Cd0s2 [Storage Array 6140, Volume homes1, LUN 0, Volume ID <600a0b80004898b8000007b948a98a5c>, Preferred Path (Controller-B): In Use]
    I'm worried about using lsscs to change it to say Access since groups1 and homes1 correspond to our two main storage pools(We are using zfs). Will I be unable to use in-band management? Or will I be able to change it with out causing any downtime?
    Thanks,
    David

    I have the same problem (no Volume Access LUN).
    Can somebody help?

  • In-Band Management configuration for f5100 array from T5440 on Solaris 10

    Hi All,
    I am trying to configure in-band management for storagetek array Sun Storage F5100 from T5440 server on Solaris 10.
    OS Installed on the server: Solaris 10 10/09
    Hardware : T5440
    Array : Sun Storage F5100
    Sun Storage F5100 have 20 FMODs which can see from format output. But In-Band management don't work, i want to manage it by CAM.
    /dev/rdsk/c2t0d0s2
    /dev/rdsk/c2t1d0s2
    /dev/rdsk/c2t2d0s2
    /dev/rdsk/c2t3d0s2
    /dev/rdsk/c2t4d0s2
    /dev/rdsk/c2t5d0s2
    /dev/rdsk/c2t6d0s2
    /dev/rdsk/c2t7d0s2
    /dev/rdsk/c2t8d0s2
    /dev/rdsk/c3t0d0s2
    /dev/rdsk/c3t1d0s2
    /dev/rdsk/c3t2d0s2
    /dev/rdsk/c3t3d0s2
    /dev/rdsk/c3t4d0s2
    /dev/rdsk/c3t5d0s2
    /dev/rdsk/c3t6d0s2
    /dev/rdsk/c3t7d0s2
    /dev/rdsk/c3t8d0s2
    Below are the packages i installed:
    host_sw_solaris_6.6.0.11
    SMagent-SOL-90.01.02.05.pkg
    SMruntime-SOL-90.60.02.01.pkg
    once after i installed the above packages i am getting below error
    SANtricity Storage Manager Agent, Version 90.01.02.05
    Built Wed May 06 06:21:07 CDT 2009
    Copyright 2009 Sun Microsystems Inc. All rights reserved. Use is subject to license agreement.
    Checking device /dev/rdsk/c0t2d0s2 : Skipping
    Checking device /dev/rdsk/c0t3d0s2 : Skipping
    Checking device /dev/rdsk/c2t0d0s2 : Skipping
    Checking device /dev/rdsk/c2t1d0s2 : Skipping
    Checking device /dev/rdsk/c2t2d0s2 : Skipping
    Checking device /dev/rdsk/c2t3d0s2 : Skipping
    Checking device /dev/rdsk/c2t4d0s2 : Skipping
    Checking device /dev/rdsk/c2t5d0s2 : Skipping
    Checking device /dev/rdsk/c2t6d0s2 : Skipping
    Checking device /dev/rdsk/c2t7d0s2 : Skipping
    Checking device /dev/rdsk/c2t8d0s2 : Skipping
    Checking device /dev/rdsk/c3t0d0s2 : Skipping
    Checking device /dev/rdsk/c3t1d0s2 : Skipping
    Checking device /dev/rdsk/c3t2d0s2 : Skipping
    Checking device /dev/rdsk/c3t3d0s2 : Skipping
    Checking device /dev/rdsk/c3t4d0s2 : Skipping
    Checking device /dev/rdsk/c3t5d0s2 : Skipping
    Checking device /dev/rdsk/c3t6d0s2 : Skipping
    Checking device /dev/rdsk/c3t7d0s2 : Skipping
    Checking device /dev/rdsk/c3t8d0s2 : Skipping
    The SMagent service attempted to start but terminated. Possible causes include: [1] The access volume is disabled in NVSRAM. [2] No controllers with compatible firmware were found. [3] The default logical unit number (LUN) assigned to the access volume (typically 7 or 31) is not in the range supported by the host or is already in use by the host for another device. See your storage management documentation for more details.
    Jul 23 13:56:47 sol10 SMagent: The SMagent service attempted to start but terminated. Possible causes include: [1] The access volume is disabled in NVSRAM. [2] No controllers with compatible firmware were found. [3] The default logical unit number (LUN) assigned to the access volume (typically 7 or 31) is not in the range supported by the host or is already in use by the host for another device. See your storage management documentation for more details.
    As per sun documentation i ran the below commands, but still i am getting above error.
    # setenv LD_LIBRARY_PATH /opt/SMgr/agent
    # java -classpath /opt/SMgr/agent/SMagent.jar devmgr.versioned.agent.DeviceIdentifier | grep "Volume Access"
    But any output with above commands.
    Any help would be really help ful.
    Thanks,
    gebilong

    Make sure the mapping to Access Group has not been deleted.
    Use the command /opt/SUNWsefms/bin/lsscs list -a array mappingYou must see samething like
    Volume:Access  LUN: 31mapped.via mapped.via.default.groupmapped.target.type mapped.via.default.group  Permission: Read Only
    ...If you don't see this recreate mapping
    /opt/SUNWsefms/bin/lsscs  map -a array -l 31 volume Accessand restart agent
    /etc/init.d/SMagent start

  • In-Band Management configuration for 2530 array from T5120 on Solaris 10

    Hi All,
    I am trying to configure in-band management for storagetek array 2530 from T5120 server on Solaris 10. I could able to connect the array from CAM software and it is showing as out-of-band. I can able to change the array name and IP address also. But when i try to configure In-Band Management i am having problems.
    OS Installed on the server: Solaris 10 5/08
    Hardware : T5120
    Array : Storage Tek 2530
    Below are the packages i installed:
    SMagent-SOL-90[1].00.00.06.pkg
    SMruntime-SOL-10[1].10.02.00.pkg
    once after i installed the above packages i am getting below error
    "SANtricity Storage Array Host Agent, Version 90.00.00.06
    Built Wed May 23 09:02:26 CDT 2007
    Copyright (C) 1999-2007 LSI Logic Corporation. All rights reserved.
    Checking device /dev/rdsk/c1t0d0s2 : Skipping
    The SMagent service attempted to start but terminated. Possible causes include: [1] The access volume is disabled in NVSRAM. [2] No controllers with compatible firmware were found. [3] The default logical unit number (LUN) assigned to the access volume (typically 7 or 31) is not in the range supported by the host or is already in use by the host for another device. See your storage management documentation for more details.
    The Host Context Agent did NOT start because 0 controllers were found.
    Oct 9 19:51:10 proto-hd1 SMagent: The SMagent service attempted to start but terminated. Possible causes include: [1] The access volume is disabled in NVSRAM. [2] No controllers with compatible firmware were found. [3] The default logical unit number (LUN) assigned to the access volume (typically 7 or 31) is not in the range supported by the host or is already in use by the host for another device. See your storage management documentation for more details.
    Oct 9 19:51:10 proto-hd1 SMagent: The Host Context Agent did NOT start because 0 controllers were found."
    As per sun documentation i ran the below commands, but still i am getting above error.
    # setenv LD_LIBRARY_PATH /opt/SMgr/agent
    # java -classpath /opt/SMgr/agent/SMagent.jar devmgr.versioned.agent.DeviceIdentifier | grep "Volume Access"
    Any help would be really help ful.
    Thanks,
    Raja

    Make sure the mapping to Access Group has not been deleted.
    Use the command /opt/SUNWsefms/bin/lsscs list -a array mappingYou must see samething like
    Volume:Access  LUN: 31mapped.via mapped.via.default.groupmapped.target.type mapped.via.default.group  Permission: Read Only
    ...If you don't see this recreate mapping
    /opt/SUNWsefms/bin/lsscs  map -a array -l 31 volume Accessand restart agent
    /etc/init.d/SMagent start

  • Charm - how manage issues after go live phase

    Hi all,
    ny customer use Charm Implementation project for managing roll-outs of new countries in his SAP ECC Landscape.
    Now Test Phase is going to end and he asks himself: "how can I manage issues after go live in Charm?"
    If I have to create additional TRs for bug fixing in the weeks after go-live can I manager them in Charm?
    I know there is the function for create TR direct in Talsk List, is this the correct way?
    In other words, do I manage issues after go-live out of Change Documents using Task list?
    As you know, Is there any best practices from SAP od from elsewhere?
    Thanks o lot
    Giovanni Lippolis

    Hi Miguel, Bob and Jansi,
    thanks for you contributions.But I realize I didn't explained myself completly.
    My situation is similar to what Bob described,
    I'm not in an ideal world (do you remember Clint Eastwood and Kevin Costner), and I think neither you.
    But, in my case there are not open TR to be recovered in project, but I suppose I'll have to open some TR (I hope a few) for fixing bug that will happen in production in the days post roll-out.
    So I wouldn't like to manage there fix in a maintenance project, because the reason of these bugs is in TR imported in roll-out.
    What I would like to do is to regress project to the Test phase (I don't need new CR and NC!) and open few Test Messages for fixing bugs.
    I'suppost It should be possilble.In your opinion?
    Ideas?
    Thnks a lot.
    Giovanni
    So what

  • Colour Management Issue with PS CS3 and Leopard 10.5.2

    Hi Everyone,
    Since I have installed Leopard I am having colour management issues with Photoshop CS3 and my Canon i9950 printer.
    My screen is calibrated with a Spyder and I used to ask Photoshop (in 10.4.11) to manage colour when printing and used the Spyder profile. Everything came out as I saw it on screen.
    Now in leopard when I do the same thing everything comes out too yellow on the print. If I ask Photoshop to let the printer manage the colour it is too red. If I use the default colour management (photoshop managing the colour and it choosing the colour space it is better, but still too yellow).
    Photoshop gives the hint to turn off colour management in the printer but there is no option for this and it also said the same thing before of course (when it worked in 10.4.11).
    Any ideas?
    Thanks.

    >It was working perfectly in Tiger with the monitor profile.
    You were lucky.
    the monitor profile is so Photoshop can display your images correctly.
    the working space is Adobe RGB, sRGB, BruceRGB, ect... these are all known color spaces so when the file goes to another computer there is a consistent color space for reference. If you use your monitor profile as a working space then nobody else knows what is going on with your file.
    when you print you need to use the printer profile for the type of paper you are printing on this is supplied by the printer manufacturer. you can also have custom profiles made.
    you need to read up on color management:
    http://www.gballard.net/psd.html
    http://digitaldog.net/

  • Colour Management issue With Leopard and PS CS3

    Hi Everyone,
    Since I have installed Leopard I am having colour management issues with Photoshop CS3 and my Canon i9950 printer.
    My screen is calibrated with a Spyder and I used to ask Photoshop (in 10.4.11) to manage colour when printing and used the Spyder profile. Everything came out as I saw it on screen.
    Now in leopard when I do the same thing everything comes out too yellow on the print. If I ask Photoshop to let the printer manage the colour it is too red. If I use the default colour management (photoshop managing the colour and it choosing the colour space it is better, but still too yellow).
    Photoshop gives the hint to turn off colour management in the printer but there is no option for this and it also said the same thing before of course (when it worked in 10.4.11).
    Any ideas?
    Thanks.

    You need to use the correct printer profile for the paper you're using. If the printer didn't come with any pre-built profiles, check Canon's web site to see if they have any profiles available for your printer that you can download.
    Printer profiles are very specific. You can't take take a profile for glossy Epson paper and expect it to work very well for Canon glossy paper.

Maybe you are looking for