Sponsored Content
Special Forums UNIX and Linux Applications Infrastructure Monitoring Agent Installation Issue on Ops Center Post 302759439 by DukeNuke2 on Tuesday 22nd of January 2013 10:17:42 AM
Old 01-22-2013
did you test the connection to the rsc card manually and updated the firmware to latest level?
 

7 More Discussions You Might Find Interesting

1. Solaris

Sun xVM Ops Center 1.1

I have 180 Solaris 7, 8 and 9 servers to patch and am looking at using xVM Ops Center. Has anyone here had any experience with it? (1 Reply)
Discussion started by: mr_crosby
1 Replies

2. Solaris

Sun Ops Center

Hi, Can anyone share the link to download sun ops centre i have sun partner account, but i unable find the link Thanks RJS (3 Replies)
Discussion started by: rajasekg
3 Replies

3. Solaris

OPS Center Email Notifications

Hi, Does any one know how to configure email notifications (to exchange) in Oracle Enterprise Manager 11g OPS Center? I have gone through the documentation and have done everything it asked, but still no notifications via email. I get the following error: At the OS level i tried sending email... (20 Replies)
Discussion started by: Mack1982
20 Replies

4. UNIX and Linux Applications

Autosys remote agent installation issue

We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys. But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2 schedulers cannot exist in the same server.... (0 Replies)
Discussion started by: hidnana
0 Replies

5. AIX

Autosys remote agent installation issue

We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys. But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2 schedulers cannot exist in the same server.... (0 Replies)
Discussion started by: hidnana
0 Replies

6. UNIX for Advanced & Expert Users

Autosys remote agent installation issue

We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys. But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2 schedulers cannot exist in the same server.... (0 Replies)
Discussion started by: hidnana
0 Replies

7. Solaris

Ops Center AI wrong IP

Hello, I have problems with Automated Installer on Solaris 11. I tried provision Solaris 11 on my T5-1B server from Ops Center, but AI set wrong IP address for manifest SMF. My Ops Center server has two IP addresses 10.236.102.219 and 10.226.21.141. Second IP is in subnet for provisioning of... (25 Replies)
Discussion started by: olibertu
25 Replies
ACTCTRL(8)						    Linux System Administration 						ACTCTRL(8)

NAME
actctrl - configure IBM Active 2000 ISDN adaptor SYNOPSIS
actctrl [-d Driver-Id] action options ... DESCRIPTION
actctrl is used to setup the IBM Active 2000 ISDN device driver and for downloading the firmware into the ISDN card. The use of actctrl makes sense, if you are using an IBM Active 2000 card only. OPTIONS
-d Driver-Id selects the S0 interface named by Driver-Id. Driver-Ids are defined during driver initialisation. See act2000(4) for a description of the syntax to be used for modularized and monolithic driver versions. This option must be used to identify the S0 interface if more than one S0 interface is existent. If a single IBM Active 2000 is used, it may be omitted. If using more than one card, sup- port for the other cards is enabled with the add action of actctrl. Ids may not start with digits or small x, because these values are misinterpreted as numeric parameters by insmod. For loading the module, always the newest modutils package should be used to avoid problems during load. The following actions may be given to actctrl. add [bus[ port[ irq[ id]]]] enables support for an additional card in the driver. bus is is an integer describing the bus-type of the card. Currently, the only value which is allowed here is 1 meaning ISA-bus. In the future, the values 2 (for MCA) and 3 (for PCMCIA) will be available. port is either an integer describing the base port, or the string auto which enables autoprobing. irq is either an integer describing the IRQ to use, the string auto, which enables grabbing of the next free IRQ or the string none which enables polled mode for this card. id is an arbitrary string for referencing the card at a later time. dproto protocol [msn0,msn1, ... msn9] selects the D-channel protocol and defines MSN's if using Euro protocol. protocol may be either the string 1tr6 or the string euro. If selecting Euro protocol, a comma-separated list of up to 10 MSN's may be appended. For defining an empty entry in this list, use a dash. load firmware downloads the firmware into the card and starts operation. Usually the images are located in '/lib/firmware/isdn'. The firmware is named bip1120.bpl. dump is available if the program is configured using the --enable-dump option only. The contents of internal driver variables is dumped on stdout. FILES
'/lib/firmware/isdn'/bip1120.bpl This is the image of the firmware designed for both the German 1TR6 protocol and Euro ISDN. BUGS
No bugs so far. AUTHOR
(C) 1997 by Fritz Elfert <fritz@isdn4linux.de> SEE ALSO
isdnctrl(8), act2000(4), isdnctrl(4), ttyI(4). isdn4k-utils-3.13 1999/09/06 ACTCTRL(8)
All times are GMT -4. The time now is 01:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy