VIC-2FXS ( Operation State is DOWN )

Hi,
After I shut and no shut the voice port
the Operation State became DOWN
Foreign Exchange Station 1/0/0 Slot is 1, Sub-unit is 0, Port is 0
Type of VoicePort is FXS
Operation State is DOWN
Administrative State is UP
The Last Interface Down Failure Cause is Administrative Shutdown
Description is not set
Noise Regeneration is enabled
Non Linear Processing is enabled
Non Linear Mute is disabled
Non Linear Threshold is -21 dB
Music On Hold Threshold is Set to -38 dBm
In Gain is Set to 0 dB
Out Attenuation is Set to 3 dB
Echo Cancellation is enabled
Echo Cancellation NLP mute is disabled
Echo Cancellation NLP threshold is -21 dB
Echo Cancel Coverage is set to 8 ms
Playout-delay Mode is set to adaptive
Playout-delay Nominal is set to 60 ms
Playout-delay Maximum is set to 200 ms
Playout-delay Minimum mode is set to default, value 40 ms
Playout-delay Fax is set to 300 ms
--More--
Any command we can make the Operation State DOMAIN mode without reset the router?
Thanks
Sim

Did you come accross this document. It could be of some help.
Understanding Foreign Exchange Station (FXS) Voice Interface Cards
http://www.cisco.com/en/US/tech/tk652/tk653/technologies_tech_note09186a0080094fac.shtml

Similar Messages

  • Putting PVDMs in NM-2V / VIC-2FXO / VIC-2FXS into DSP farm

    I have a Cisco 2650XM router with an NM-2V module with one VIC-2FXO and one VIC-2FXS card in it. I'm very new to Cisco voice stuff and want to get started with it. I'm trying to pool the PVDMs on this router into a DSP farm so that they can be used in CME 4.1 with call conferencing / transcoding / VoIP calls between Cisco IP Communicator and Cisco VoIP physical phones but I'm having issues doing so. I believe I'm supposed to create a DSP farm by going into "voice-card X" mode and assigning them to the DSP farm?
    I know that there are PVDMs present because they are listed when I do a "show voice dsp detail." I'm not sure if the PVDMs are present in the NM-2V module or actually on the VICs. Can someone offer advice?

    Yeah, the only cards / modules that I have in the router are the NM-2V, VIC-2FXO, and VIC-2FXS. Here is the "show diag" output as well as some other ones that may be useful.
    Press RETURN to get started!
    *Mar  1 00:00:05.949: %LINEPROTO-5-UPDOWN: Line protocol on Interface VoIP-Null0, changed state to up
    *Mar  1 00:00:25.281: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
    *Mar  1 00:00:25.970: %SYS-6-CLOCKUPDATE: System clock has been updated from 00:00:25 UTC Fri Mar 1 2002 to 17:00:25 AZT Thu Feb 28 2002, configured from console by console.
    *Mar  1 00:00:26.439: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
    *Mar  1 00:00:27.873: %SYS-5-CONFIG_I: Configured from memory by console
    *Jan  4 02:05:04.149: %SYS-5-RESTART: System restarted --
    Cisco IOS Software, C2600 Software (C2600-ADVENTERPRISEK9-M), Version 12.4(15)T14, RELEASE SOFTWARE (fc2)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2010 by Cisco Systems, Inc.
    Compiled Tue 17-Aug-10 05:40 by prod_rel_team
    *Jan  4 02:05:04.153: %SNMP-5-COLDSTART: SNMP agent on host KINASE is undergoing a cold start
    *Jan  4 02:05:04.322: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
    *Jan  4 02:05:04.322: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
    *Jan  4 02:05:05.435: %LINK-3-UPDOWN: Interface Foreign Exchange Office 1/0/0, changed state to up
    *Jan  4 02:05:05.435: %LINK-3-UPDOWN: Interface Foreign Exchange Office 1/0/1, changed state to up
    *Jan  4 02:05:05.439: %LINK-3-UPDOWN: Interface Foreign Exchange Office 1/1/0, changed state to up
    *Jan  4 02:05:05.439: %LINK-3-UPDOWN: Interface Foreign Exchange Office 1/1/1, changed state to up
    CNF-FILES: Clock is not set or synchronized, retaining old versionStamps
    CNF files update complete (post init)
    KINASE>en
    KINASE#show diag
    Slot 0:
    C2650XM 1FE Mainboard Port adapter, 1 port
    Port adapter is analyzed
    Port adapter insertion time unknown
    EEPROM contents at hardware discovery:
    Hardware Revision        : 3.0
    PCB Serial Number       FFFF
    Part Number              : 73-7755-04
    RMA History              : 00
    RMA Number               : 0-0-0-0
    Board Revision           : A0
    Deviation Number         : 0-0
    Product (FRU) Number     : C2650XM-1FE
    EEPROM format version 4
    EEPROM contents (hex):
      0x00: 04 FF 40 03 6E 41 03 00 C1 0B FF FF FF 46 46 46
      0x10: 46 FF FF FF FF 82 49 1E 4B 04 04 00 81 00 00 00
      0x20: 00 42 41 30 80 00 00 00 00 FF FF FF FF FF FF FF
      0x30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
      0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
      0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
      0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
      0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
    Slot 1:
    4 PORT Voice PM for C2600 Port adapter
    Port adapter is analyzed
    Port adapter insertion time unknown
    EEPROM contents at hardware discovery:
    Hardware revision 1.1                   Board revision H0
    Serial number     26333860            Part number    800-02491-02
    FRU Part Number     NM-2V=           
    Test history      0x0                   RMA number     00-00-00
    EEPROM format version 1
    EEPROM contents (hex):
      0x00: 01 65 01 01 01 91 D2 A4 50 09 BB 02 00 00 00 00
      0x10: 88 00 00 00 01 06 27 17 FF FF FF FF FF FF FF FF
      0x20: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
      0x30: FF FF FF FF FF FF FF FF FF FF FF FF
    VIC Slot 0:
    FXO Voice daughter card (2 port)
    Hardware revision 1.1                   Board revision J0
    Serial number     21522658            Part number    800-02495-01
    Test history      0x0                   RMA number     00-00-00
                                      Connector type    Wan Module
    EEPROM format version 1
    EEPROM contents (hex):
      0x20: 01 0D 01 01 01 48 68 E2 50 09 BF 01 00 00 00 00
      0x30: 98 00 00 00 00 07 22 01 FF FF FF FF FF FF FF FF
    VIC Slot 1:
    FXO Voice daughter card (2 port)
    Hardware revision 1.1                   Board revision J0
    Serial number     22783161            Part number    800-02495-01
    Test history      0x0                   RMA number     00-00-00
                      Connector type    Wan Module
    EEPROM format version 1
    EEPROM contents (hex):
      0x20: 01 0D 01 01 01 5B A4 B9 50 09 BF 01 00 00 00 00
      0x30: 98 00 00 00 00 11 16 01 FF FF FF FF FF FF FF FF
    KINASE#sh voice dsp detail
    DSP  DSP                DSPWARE CURR  BOOT                         PAK     TX/RX
    TYPE NUM CH CODEC       VERSION STATE STATE   RST AI VOICEPORT TS ABORT  PACK COUNT
    ==== === == ======== ========== ===== ======= === == ========= == ===== ============
    C542 001 01 None          9.4.7 IDLE  idle      0  0 1/0/0     NA     0      602/623
    C542 002 01 None          9.4.7 IDLE  idle      0  0 1/0/1     NA     0      593/590
    C542 003 01 None          9.4.7 IDLE  idle      0  0 1/1/0     NA     0      601/622
    C542 004 01 None          9.4.7 IDLE  idle      0  0 1/1/1     NA     0      593/590
    KINASE#sh dspfarm
    DSPFARM Configuration Information:
    Admin State: DOWN, Oper Status: DOWN - Cause code: ADMIN_STATE_DOWN
    Transcoding Sessions: 0(Avail: 0), Conferencing Sessions: 0 (Avail: 0)
    Trans sessions for mixed-mode conf: 0 (Avail: 0), RTP Timeout: 600
    Connection check interval 600 Codec G729 VAD: ENABLED
    KINASE#config t
    Enter configuration commands, one per line.  End with CNTL/Z.
    KINASE(config)#voice-card ?
      <0-1>  Voice interface slot #
    KINASE(config)#voice-card 0 ?
    % Unrecognized command
    KINASE(config)#voice-card 0?
    % Unrecognized command
    KINASE(config)#voice-card 0?
    % Unrecognized command
    KINASE(config)#voice-card 0/?
    % Unrecognized command
    KINASE(config)#voice-card 0
                              ^
    % Invalid input detected at '^' marker.
    KINASE(config)#voice-card 1
                              ^
    % Invalid input detected at '^' marker.
    KINASE(config)#
    KINASE(config)#voice-port 1/0/0
    KINASE(config-voiceport)#?
    Voice-port configuration commands:
      battery-reversal     Enable FXO battery-reversal detection
      bearer-cap           Specify the bear capability
      busyout              Configure busyout trigger event & procedure
      comfort-noise        Use fill-silence option
      connection           Specify Trunking Parameters
      cptone               Configure voice call progress tone locale
      default              Set a command to its defaults
      description          Description of what this port is connected to
      dial-type            Configure type of dialer for voice
      disc_pi_off          close voice path when disconnect with PI received
      echo-cancel          Echo-cancellation option
      exit                 Exit from voice-port configuration mode
      impedance            Specifies the terminating impedance of the interface
      input                Configure input gain for voice
      music-threshold      Threshold for Music on Hold
      no                   Negate a command or set its defaults
      non-linear           Use non-linear processing during echo cancellation
      output               Configure output attenuation for voice
      playout-delay        Configure voice playout delay buffer
      pre-dial-delay       FXO Pre-dial Delay
      ring                 Number of rings
      shutdown             Take voice-port offline
      signal               The signaling type for the interface FXS or FXO
      snmp                 Modify SNMP voice port parameters
      station-id           Configure station ID
      supervisory          Configure answer + disconnect supervision options
      threshold            Threshold [noise] for voice port
      timeouts             Configure voice timeout parameters
      timing               Configure voice timing parameters
      translate            Translation rule
      translation-profile  Translation profile
      trunk-group          Configure interface to be in a trunk group
      voice-class          Set voiceport voice class control parameters
    KINASE(config-voiceport)#
    Looks like the "voice-port" command works, but not the "voice-card" command.

  • CIFS Operational State Disabled.

    Hi All
    The CIFS service on a NME-WAE-502 is showing an "disabled" operational state however the Config State is "enabled" and reporting a "
    cifs_ao_down" alarm. I've tried re-enabling the accelerated service via the CLI and the console reports that it is enabled however the operational state of the acceleratored service remains disabled.
    WAE1#sh alarm
    Critical Alarms:
            Alarm ID                 Module/Submodule               Instance
       1 cifs_ao_down              wafs                         WAFS                    
    Major Alarms:
    None
    Minor Alarms:
            Alarm ID                 Module/Submodule               Instance
       1 primary_interface         CIFS_AO/primary_interface    CIFS_AO                 
    WAE1#sh license
    License Name   Status      Activation Date Activated By 
    Transport      not active
    Enterprise     active      05/22/2009      admin        
    Video          not active
    WAE1#sh cms info
    Device registration information :
    Device Id                            = 3806504                            
    Device registered as                 = WAAS Application Engine            
    Current WAAS Central Manager         = 10.###.###.##                        
    Registered with WAAS Central Manager = 10.###.###.##                        
    Status                               = Online                             
    Time of last config-sync             = Tue Jan  3 12:45:18 2012           
    CMS services information :
    Service cms_ce is running
    WAE1#sh acc
    Accelerator     Licensed        Config State    Operational State            
    cifs            Yes             Enabled         Disabled  
    epm             Yes             Enabled         Running   
    http            Yes             Enabled         Running   
    mapi            Yes             Enabled         Running   
    nfs             Yes             Enabled         Running   
    ssl             Yes             Enabled         Running   
    video           No              Enabled         Shutdown
    WAE1#conf t
    WAE1(config)#accelerator cifs enable
    Enabled windows-print accelerator
    Enabled cifs accelerator
    WAE1(config)#
    Does anyone know how to solve this issue?

    As requested:
    WAE1#sh alarm history detail
         Op Sev Alarm ID             Module/Submodule     Instance
       1 R  Cr  cifs_ao_down         wafs                 WAFS               
         Dec 31 16:57:20.389 EST, Processing Error Alarm, #000002, 10000:1000003
         CIFS Accelerator is down.
       2 R  Mi  primary_interface    CIFS_AO/primary_interface CIFS_AO            
         Dec 31 16:56:21.861 EST, Environment Alarm, #000001, 20000:20001
         primary-interface miss-configured. cifs-ao will work in passthrough mode.
    Op - Operation: R-Raised, C-Cleared
    Sev - Severity: Cr-Critical, Ma-Major, Mi-Minor
    WAE1#sh ver
    Cisco Wide Area Application Services Software (WAAS)
    Copyright (c) 1999-2011 by Cisco Systems, Inc.
    Cisco Wide Area Application Services (accelerator-k9) Software Release 4.4.3b (build b2 Oct 20 2011)
    Version: nme-wae-502-4.4.3b.2
    Compiled 16:38:43 Oct 20 2011 by damaster
    Device Id: 00:21:55:##:##:##
    System was restarted on Sat Dec 31 16:49:10 2011.
    The system has been up for 3 days, 2 hours, 38 minutes, 24 seconds.
    WAE1#sh disk detail
    Physical disk information:
      disk00: Present    080606BB6200WBFM69UF       (h01 c00 i00 l00 - Int DAS-SATA)
              114470MB(111.8GB)
    Mounted file systems:
    MOUNT POINT      TYPE       DEVICE                SIZE     INUSE      FREE USE%
    /sw              internal   /dev/sdb1            991MB     698MB     293MB  70%
    /swstore         internal   /dev/sdb2            991MB     562MB     429MB  56%
    /state           internal   /dev/sdb3           3967MB     137MB    3830MB   3%
    /local/local1    SYSFS      /dev/sdb7           5951MB     808MB    5143MB  13%
    /disk00-04       CONTENT    /dev/sdb6          96995MB   33965MB   63030MB  35%
    .../local1/spool PRINTSPOOL /dev/sdb8            991MB      16MB     975MB   1%
    No RAID devices present.
    Disk encryption feature is disabled.

  • Maxdb 7.7.4 wont start ERR_WRONGDBSTATE Operational State UNKNOWN

    Hi,
    We are running maxdb 7.7.4 on a linux suse 10 environment.
    The system was shutdown the other week and we cannot get it to restart
    When we try and restart we get the following in the dbm.prt
    client connection was established at 2010-11-03 01:13:04 (client process has process ID 4520 on computer 169.254.82.132).
    2010-11-03 01:13:04 0x00002cd0 INF        283 DBMSrv   Command 'auto_extend show' is being executed.
    2010-11-03 01:13:04 0x00002cd0 INF        419 DBMSrv   Command 'auto_extend' has ended with return code 0.
    2010-11-03 01:13:04 0x00002cd0 INF        283 DBMSrv   Command 'auto_update_statistics show' is being executed.
    2010-11-03 01:13:04 0x00002cd0 INF        419 DBMSrv   Command 'auto_update_statistics' has ended with return code 0.
    2010-11-03 01:13:08 0x00002cd0 INF        283 DBMSrv   Command 'db_online -f' is being executed.
    2010-11-03 01:13:08 0x00002cd0 ERR     -24580 DBMSrv   ERR_COMMAND_FAILED: Command 'db_online' has ended and failed with return code -24783.
                        0x00002cd0 ERR     -24783 DBMSrv   ERR_WRONGDBSTATE: Operational state UNKNOWN of the database instance is unsuitable.
                        0x00002cd0 ERR     -24779 DBMSrv   ERR_DBSTATENEEDED4: Database instance must be in one of the operational states OFFLINE, ADMIN, STANDBY or ONLINE.
    2010-11-03 01:13:15 0x00002cd0 INF        283 DBMSrv   Command 'db_online -f' is being executed.
    2010-11-03 01:13:15 0x00002cd0 ERR     -24580 DBMSrv   ERR_COMMAND_FAILED: Command 'db_online' has ended and failed with return code -24783.
                        0x00002cd0 ERR     -24783 DBMSrv   ERR_WRONGDBSTATE: Operational state UNKNOWN of the database instance is unsuitable.
    If we connect via dbmgui it shows it being in a u201Cunknown stateu201D
    If I run a db_state command via dbmcli it returns:
    OK
    State
    UNKNOWN
    If I run a show state command via dbmcli I get the following message ( sorry about the retype )
    OK
    ERR 11311 IPC idfile: u2018/sapdb/data/dbspeed/EP4u2019 open error, no such file or directory
    Bad magic number in /sapdb/data/wrk/EP4/rtedump_dir/RTEMemory_Table.0: 0x0x found (expected 0x184541191x)
    No mapping chunk entries found
    u2018RTECons_MemoryDumpMappingu2019 instance could not be created
    Failed to map memory dump files
    ERR 13638 RTE    RTE_ConsoleRequestCommunicatio.cpp:280
    ERR 13638 RTE    2010-11-22 07:13:45 RTE error 13638
    ERR 13638 RTE    Console: Server DB u2018EP4u2019 has not been started
    Any ideas ??
    Thanks in advance
    Gary Vaughan

    Hi,
    Problem solved - a big thankyou
    I actually had tried removing the directory contents but not the directory itself.
    I had not found the oss note.
    Thanks again
    Gary Vaughan

  • EtherCAT Error -2147138468 switching third party device to Safe Operational State

    I have been successful in importing and detecting/adding a Lenord + Bauer Ethercat Encoder (GEL235).
    Attached you will find the Device Profile.
    But when I try to switch the Scan Engine to "Active", I eventually receive this error message: "An error occured while attempting to switch the I/O scan mode. LabVIEW: (Hex 0x80DF0019) The deployment connection timed out."
    Trying to set the device EtherCAT Online State to "Safe Operational" on the slave device eventually returns "Error -2147138468 occurred at an unidentified location Possible reason(s): CoE operation fails because the CoE service is timeout. Ensure that each device in the EtherCAT network is powered on and properly connected."
    I can confirm that the device is properly powered and connected. The EtherCAT ethernet port on the cRIO has a solid, green link indicator and all status indicators on the encoder are in their normal operational state except for the "Run" led which is flashing evenly, meaning the current state is "PRE-OPERATIONAL".
    I can read the encoder position without any issues using "TwinCAT System Manager" from Beckhoff.
    Any idea/tips on how I should proceed from this point to troubleshooting/fix the issue?
    Regards,
    Danny Lepage
    CEL Aerospace Test Equipment LTD
    Attachments:
    ni_support.zip ‏90 KB

    You might want to share this information with the developers at Happauge

  • VM in state Shutting down forever

    After a Live Migration one of my VMs was frozen. Manager still showed it as running. I chose "Power Off" for that VM in Manager and now it is stuck in state "Shutting down". I rebooted the server this VM was running on and restarted the manager but nothing worked. I cannot remove it from the manager because all buttons are inactive. Any ideas?

    I checked and restarted the data collector. I also restarted the VM. Now the checker logs:
    INFO: ===start=== data collection 1,2,3 ...
    Nov 26, 2007 8:48:03 AM com.oracle.oardc.ovs.OVSDataCollector getSiteAgent
    FINE: site(10)=BX6S3_06 agent=https://192.168.249.216:8899
    Nov 26, 2007 8:48:03 AM com.oracle.oardc.ovs.OVSDataCollector$OVSPerfDataCollector run
    FINE: site(10) get_servers_perf=success:192.168.249.216=1.00:5470:38777;bx6s3-07-gi=1.00:3448:38777
    Nov 26, 2007 8:48:03 AM com.oracle.oardc.ovs.OVSDataCollector$OVSPerfDataCollector syncServerStatus
    INFO: syncServerStatus:activeServerNames=:bx6s3-07-gi::192.168.249.216:
    Nov 26, 2007 8:48:04 AM com.oracle.oardc.ovs.OVSDataCollector$OVSPerfDataCollector run
    FINE: site(10) get_vms_perf=success:34_vm1_rhel5=0.0:2055:0;56_vm2_oel5=0.0:2048:0;58_vm3_oel4u5=0.0:2048:0
    Nov 26, 2007 8:48:05 AM com.oracle.oardc.ovs.OVSDataCollector$OVSVMServerStatusChecker run
    FINE: site(10) get_live_vm_info=success:192.168.249.216=34_vm1_rhel5::5901;bx6s3-07-gi=56_vm2_oel5::5900,58_vm3_oel4u5::5901
    Nov 26, 2007 8:48:05 AM com.oracle.oardc.ovs.OVSDataCollector$OVSVMServerStatusChecker updateDBVMStatus
    FINE: vmInfo=56_vm2_oel5::5900
    Nov 26, 2007 8:48:05 AM com.oracle.oardc.ovs.OVSDataCollector$OVSVMServerStatusChecker updateDBVMStatus
    FINE: vmInfo=58_vm3_oel4u5::5901
    Nov 26, 2007 8:48:05 AM com.oracle.oardc.ovs.OVSDataCollector$OVSVMServerStatusChecker updateDBVMStatus
    FINE: vmInfo=34_vm1_rhel5::5901
    Nov 26, 2007 8:48:05 AM com.oracle.oardc.ovs.OVSDataCollector main
    INFO: ===done=== data collection 1,2,3.
    Seems that it gets the data vor this VM (in bold), but Manager still shows "Shutting down".

  • ACE 4710 Operations Virtual Servers showing Oper State as N/A

    Hi All,
    Just wondering if anyone has come across the following issue before:
    We currently have a pair of ACE4710 in HA running A3(2.7) and when we have added new virtual servers any new ones show up under the Operations - Virtual Servers window as showing their Oper State as N/A. as follows:
    However, clicking on the N/A brings up a window showing that the virtual server is Active and inservice and handling traffic. This doesn't appear to be affect the services using the VIPs that have N/A against them as all appears to be fine.
    Just wonder if anyone had seen this before and if there is a reason for it.
    Thanks for you help in advance.
    Ryan

    Thanks for you reply bhartsfield. I mostly work from the CLI as the network engineer but we have server engineers who use the GUI to take things in and out of service if they are conductinh maintenence on the servers. So along with the N/A status it also is missing the current connection count which is also used by the server guys.
    The last time I created a VIP I did it via the GUI to see if it was a GUI issue not syncing with the CLI. I have also forced the DM to sync with CLI, but it still has the same results.
    Thanks again for your reply, at least I know I am not alone in seeing this behaviour
    Regards
    Ryan

  • %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down

    Hello,
    On a 4402 wireless controller (7.0.220.0) with LAP1242AG-E-K9 and LAP1252AG-E-K9 access points I receive lots of messages like this:
    Dec  9 12:55:16 ap-a1 1466: AP:001a.2f58.d4d6: *Dec  9 11:55:16.174: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    Dec  9 12:55:17 ap-a1 1467: AP:001a.2f58.d4d6: *Dec  9 11:55:16.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    what is a little bit annoying, in particular for voice communications.
    Is there a way to get more information from any logs or is there a similar problem discussion anywhere on this forum?
    Thanks.

    Hi Konstantin,
    Unfortunately I do not think we have the radio status codes published, but I'll comment on them here:
    Status 51: Reset on transmit completion. I'm not 100%, but I think this means the radio was supposed to reset (due to another reason) but had data to transmit, so it completed TX and then reset.
    Status 52: Reset on completion of multicast packets. Similar to above, just with multicast traffic being queued up.
    Status 37: Generic interface reset (up/down), often seen during bootup or on configuration changes.
    Status 54: Radio interface was shutdown -- either configured by the user or perhaps part of the boot process.
    Status 67: Reset after changing hostname on the AP. This also would occur on bootup once the config is loaded.
    Status 71: Reset to update radio status on WLC. Also usually done upon AP joining the WLC after bootup.
    -Pat

  • CSS-11503 ISC State Change:DOWN

    I'm curious what kind of network errors caused my CSS to have a ISC State Change. Appears all services went down/suspended. Running 8.10.4.01 back to Catalyst 6509.
    After a couple days of running my CSS stops, troubleshooting what's going on.
    show
    02/03/2010 13:37:21:Enterprise:ISC State Change:DOWN, port-1 fail = No Physical Link, port-2 fail = No Interface Assigned
    02/03/2010 13:37:21:Generic:Virtual Router 9 down on interface 10.0.2.238
    02/03/2010 13:37:21:Generic:Virtual Router 100 down on interface 10.0.35.3
    02/03/2010 13:37:22:Enterprise:Service Transition:MATRIXPORTALQA_80 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:MATRIXPORTALQA_80 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:newwf135 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:newwf135 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:newwf31 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:newwf31 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:newwf47 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:newwf47 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_1350 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_1350 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_1354 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_1354 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_80 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_80 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_HOD_80 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_HOD_80 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_HOD_8999 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_HOD_8999 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_cmed -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_cmed -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_1350 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_1350 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_1354 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_1354 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_80 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_80 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_cmed -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_cmed -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws134 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws134 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_1350 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_1350 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_1354 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_1354 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_80 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_80 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_HOD_80 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_HOD_80 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_HOD_8999 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_HOD_8999 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_cmed -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_cmed -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws150_1350 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws150_1350 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws150_1354 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws150_1354 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws150_80 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws150_80 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws150_cmed -> suspended
    02/03/2010 13:37:23:Enterprise:Service Transition:us00hqws150_cmed -> down
    02/03/2010 13:37:23:Enterprise:Service Transition:us0999web135_80 -> suspended
    02/03/2010 13:37:23:Enterprise:Service Transition:us999web41_80 -> suspended
    02/03/2010 13:37:23:Enterprise:Service Transition:us999web46 -> suspended
    02/03/2010 13:37:23:Enterprise:Service Transition:us999web47_80 -> suspended
    02/03/2010 13:37:23:Enterprise:Service Transition:web110 -> suspended
    02/03/2010 13:37:23:Enterprise:Service Transition:web110 -> down
    02/03/2010 13:37:23:Enterprise:Service Transition:web111 -> suspended
    02/03/2010 13:37:23:Enterprise:Service Transition:web111 -> down
    02/03/2010 13:37:23:Enterprise:Service Transition:webface_ssl -> suspended
    02/03/2010 13:37:24:Generic:LINK UP for  1/1
    02/03/2010 13:37:25:Generic:COLD START
    02/03/2010 13:37:32:Generic:Virtual Router 9 idle on interface 10.0.2.238
    02/03/2010 13:37:32:Generic:Virtual Router 100 idle on interface 10.0.35.3
    02/03/2010 13:37:32:Generic:Virtual Router 9 backup on interface 10.0.2.238
    02/03/2010 13:37:32:Generic:Virtual Router 100 backup on interface 10.0.35.3
    02/03/2010 13:37:52:Generic:Virtual Router 9 master on interface 10.0.2.238
    02/03/2010 13:37:52:Generic:Virtual Router 100 master on interface 10.0.35.3
    02/03/2010 20:46:18:Enterprise:ISC State Change:DOWN, port-1 fail = No Physical Link, port-2 fail = No Interface Assigned

    I'm curious what kind of network errors caused my CSS to have a ISC State Change. Appears all services went down/suspended. Running 8.10.4.01 back to Catalyst 6509.
    After a couple days of running my CSS stops, troubleshooting what's going on.
    show
    02/03/2010 13:37:21:Enterprise:ISC State Change:DOWN, port-1 fail = No Physical Link, port-2 fail = No Interface Assigned
    02/03/2010 13:37:21:Generic:Virtual Router 9 down on interface 10.0.2.238
    02/03/2010 13:37:21:Generic:Virtual Router 100 down on interface 10.0.35.3
    02/03/2010 13:37:22:Enterprise:Service Transition:MATRIXPORTALQA_80 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:MATRIXPORTALQA_80 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:newwf135 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:newwf135 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:newwf31 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:newwf31 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:newwf47 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:newwf47 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_1350 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_1350 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_1354 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_1354 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_80 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_80 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_HOD_80 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_HOD_80 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_HOD_8999 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_HOD_8999 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_cmed -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws157_cmed -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_1350 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_1350 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_1354 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_1354 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_80 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_80 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_cmed -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00drws158_cmed -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws134 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws134 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_1350 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_1350 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_1354 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_1354 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_80 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_80 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_HOD_80 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_HOD_80 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_HOD_8999 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_HOD_8999 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_cmed -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws149_cmed -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws150_1350 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws150_1350 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws150_1354 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws150_1354 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws150_80 -> suspended
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws150_80 -> down
    02/03/2010 13:37:22:Enterprise:Service Transition:us00hqws150_cmed -> suspended
    02/03/2010 13:37:23:Enterprise:Service Transition:us00hqws150_cmed -> down
    02/03/2010 13:37:23:Enterprise:Service Transition:us0999web135_80 -> suspended
    02/03/2010 13:37:23:Enterprise:Service Transition:us999web41_80 -> suspended
    02/03/2010 13:37:23:Enterprise:Service Transition:us999web46 -> suspended
    02/03/2010 13:37:23:Enterprise:Service Transition:us999web47_80 -> suspended
    02/03/2010 13:37:23:Enterprise:Service Transition:web110 -> suspended
    02/03/2010 13:37:23:Enterprise:Service Transition:web110 -> down
    02/03/2010 13:37:23:Enterprise:Service Transition:web111 -> suspended
    02/03/2010 13:37:23:Enterprise:Service Transition:web111 -> down
    02/03/2010 13:37:23:Enterprise:Service Transition:webface_ssl -> suspended
    02/03/2010 13:37:24:Generic:LINK UP for  1/1
    02/03/2010 13:37:25:Generic:COLD START
    02/03/2010 13:37:32:Generic:Virtual Router 9 idle on interface 10.0.2.238
    02/03/2010 13:37:32:Generic:Virtual Router 100 idle on interface 10.0.35.3
    02/03/2010 13:37:32:Generic:Virtual Router 9 backup on interface 10.0.2.238
    02/03/2010 13:37:32:Generic:Virtual Router 100 backup on interface 10.0.35.3
    02/03/2010 13:37:52:Generic:Virtual Router 9 master on interface 10.0.2.238
    02/03/2010 13:37:52:Generic:Virtual Router 100 master on interface 10.0.35.3
    02/03/2010 20:46:18:Enterprise:ISC State Change:DOWN, port-1 fail = No Physical Link, port-2 fail = No Interface Assigned

  • ANM web services - Get operational state of an SfRserver

    Is there any way to obtain the operational state of a serverfarm realserver via the ANM (4.1) web services API?  The SfRserver data type includes the admin state (i.e. IS, ISS, or OOS) but I dont see a field for the operational state.  The ANM web GUI displays both an admin state and an operational state for a serverfarm realserver -- with the operational state indicating the latest probe status for the real server (e.g. "Up" or "Probe Failed") and I would like to obtain the same information but using the ANM web services interface.

    Hello Andrew,
    The API for ANM is purely for configuration, it does not return anything other than configuration.  The state of "inservice" or "out of service" relates to the command under the rserver:
    rserver host Server05
    ip address 172.16.35.14
    inservice <======= **Here**
    The probe states don't relate to the configuration, so the API doesn't have a plugin to that information.
    However - You could use SNMP seperately to gathter that probe state directly from the ACE and intigrate that into the page you are executing the API for.
    Regards,
    Chris Higgins

  • US States drop-down

    In the Contact Us form in FormsCentral, is there a way to put a drop down select window with the US States already populated in it?
    Thanks

    Hi;
    The "Product Order Form" Template includes a "State" drop-down menu, you can create a form from that Template and Copy (Ctrl+C or CMD+C on Mac) and then paste into your Contact Us form.
    Thanks,
    Josh

  • Vic-2fxs,vic-2fx0

    what is the difference between VIC-2FXS and VIC-2FXO?
    Can them just be used in WIC slots of cisco 2600?
    thanks in advance

    The VIC-2FXS is a station device and can provide loopstart and ground start service to a analog phone device. It will give you dialtone.
    The VIC-2FXO is a office card. IT is meant to provide a telco office type conenction. This is used to forward digits out to telphony networks. It will not give you dialtone. They cannot be used in a WIC slot of 2600, they can be used in a VIC slot. The 2600 would require a NM-2V, or NM-1V in order for these modules to work properly.

  • "ExecuteStatement finished with operation state: CLOSED_STATE" while executing Hive queries

    Hi,
    HiveODBC errors shows “InvalidSessionHandle” and “ExecuteStatement finished with operation state: CLOSED_STATE”.
    Two different errors, they occur intermittently when querying table rows and when trying to view column definitions through the Microstrategy app which is using the below-mentioned driver.
    Environment Description:
    I am using the followings:
    Hive Server2
    Cloudera ODBC Driver v. 2.5.13 (32 bit)
    Microstrategy application 
    Please suggest your views on this.
    Thanks,

    “InvalidSessionHandle” Error is resolved..
    only the “ExecuteStatement finished with operation state: CLOSED_STATE” error occurs..
    please suggest some views on this.
    Additional Description:
    I am Using CDH 5.2.1
    Thanks in advance.

  • Fc port 47 on fabric interconnect A oper state: failed, reason: Link failure: OLS received

    Hi,
    this UCS is connected to a qlogics SAN Fabric. We can see the LUN in ESX 5, but can't write. If we want write something to the LUN, we get the error above. We know that the qlogic Fabric is not supported by UCS, but its NPIV and i have a similar Installation which is doing fine.
    Any Ideas?
    Thanks, Marco

    Hello,
    NOS refers to "No operatioal sequence". Fibre channel has primitive seqences which are used to establish and maintain a link among the devices.
    During the initial login phase,
    1.Fiber channel switch sends a NOS signal
    2.HBA connected to it sends an "OLS (offline sequence) signal.
    3.Switch would send  a "Link reset"(LR)
    4.HBA responds with a "LRR (link reset response)"
    When a NOS received condition is met,
    •A signal loss or sync loss condition is detected.
    •The port is administratively shut down.
    •The port is operationally down.
    When the port status is in "link failure or not-connected" state, it means that the physical path is not completely active or no active signals has been sent. Check the cables/SFP's if pluged in properly and check the configuration (port type, speed and vsan settings) for further troubleshooting.

  • WCS Alarm Status shows green but LAP is unplugged ?! Oper Staus shows Down

    Hello,
    we are operating a Cisco WLAN environment with 1242 and 1131 LAP. Some of them have been converted from AP to LAP.
    Now we took some LAP off the wall.
    They are now packed in a box in our storage room.
    But the WCS is showing a green Alarm Status for these LAP and as Oper Status Down.
    How can that be ?
    Is there a way to fix this problem, because we want to see the Alarm Status in Red.
    Thx for all your input.
    Best Regards
    Christian

    This is very interesting. If I try to put myself in the WCS developer's shoes, I think:
    - if you get an alarm for missing AP, then acknowledge the alarm, WCS has no reason to re-display the same alarm. This is precisely what Acknowledge is for, to say "don't bother me with this issue anymore".
    - Even if you manually remove the AP from WCS, it clearly keeps some memory of it, at least for a while. This is something you can clearly see if you run a report of any kind, WCS has to keep track of objects even if you remove them.
    My suggestion would be:
    - Unacknowledge the alarm, then delete it... acknowledging an alarm is probably not the best way to deal with removing an AP. You would use Aknowledge for alarms such as "your neighbour AP keep being detected as rogue, you can't remove your neighbour AP but don't want to hear about this warning anymore." You acknowledge the alarm, WCS keeps it in its database and remembers NOT to bother you with it anymore (exactly what happens in your case).
    For an AP you remove, I would not acknowledge the alarm, but simply delete it after having removed the AP. This removes the alarm from the WCS database.
    If you ever re-plug this AP to the network, WCS may remember it, but any new alarm about it will display.
    Hope it helps
    Jerome

Maybe you are looking for