How do you attach a modem to a N4000

[Lyn Syms]

Could someone please give me some advise on how to attach a modem to a N4000.
We currently have a modem attached to a PM16 DB Port module which is attached to Slot 10 Path 1/2 on the back of the server.

Can anyone give me some advise on how to see this device from the ioscan and how to configure it to the system??? Thanks

[James Murtagh]

Hi Lyn,

Take a look at the "Configuring HP-UX for peripherals" guide :

http://www.docs.hp.com/hpux/onlinedocs/B2355-90698/B2355-90698.html

Section 4, "Configuring terminals and modems" section gives you a step by step guide to configuring it.

Cheers,

James.

[Saurav_1]

Hi,

Connect the modem to the remote port of the N4000 server. you will find it in the set of 3 ports where console is connected. GO to GSP prompt by pressing Ctrl B on the console. Type CA to configure the remote port.
Remote Console Serial Port Modem Protocol: Bell
Remote Console Serial Port Modem bit rate: 9600 bits/s
Remote Console Serial Port Modem Flow Control: Software
Remote Console Serial Port Modem Transmit Configuration Strings: Enabled
Remote Console Serial Port Modem Presence: always connected.

type ER at gsp prompt and confirm whether U want to use modem for dialin & dial out or GSP prompt. multitech or HP modems must be used to remove compatibility issue.

Saurav

[Lyn Syms]

Hi,

Thanks for your responses. I have read the manaul but was a bit unsure about some of the points.

As the modem is connected via a PM16 DB port module (an expansion 16 port module) which is attached to a card in slot 10 Path 1/2 on the back of the server. (The modem is not attached via the remote modem port as we have 2 that need to be attached).

When I do an ioscan of the system I can see the following which I assume is for the the above slot/path but cannot see the modem.

ba 1 0/1 lba CLAIMED BUS_NEXUS Local
PCI Bus Adapter (782)
ba 2 0/2 lba CLAIMED BUS_NEXUS Local
PCI Bus Adapter (782)
I have noticed however that the mux2 and mux4 drivers are not installed, do you think this could be the problem?

[Stefan Stechemesser]

Hi,

for the 64 port PCI MUX card, you have to install the driver "pci_mux0". Then an "ioscan -fnC tty" should show your PCI MUX and the devicefiles. Information about creating modem devicefiles can be found in "man mksf" (scroll to the mux sections).
A tool for testing if the DB25 panel is working properly is /usr/bin/emux_diag. But of cause, you can connect your modem to the Remote Modem port on the Core I/O.

Best regards

Stefan

[Darren Prior]

Hi Lyn,

HP-UX doesn't actually "see" the modem, so there won't be anything special about the port in ioscan. What you can do, however, is to run ioscan -fun and attach the output to this thread.

Look for devices of class "tty" (ie in the left most column), you can then check the h/w address and see if any device files have been created for it.

regards,

Darren.

[Marlene Smith]

Lyn,

Once you have the drivers for the mux, you will need to add/create/modify entries in your /etc/uucp/Systems & Devices . Once these are complete - should work. If your machine has a support modem on it, use those entries as an example to configure yours.

As far as configuring the modem - use SAM - it's painless.
HTH

[Lyn Syms]

Hi everyone,

I have checked the ioscan which shows the following information:

tty 2 1/4/0/0 pci_mux0 CLAIMED INTERFACE PCI Serial (113f0868)
/dev/diag/mux2 /dev/diag/mux2_2
/dev/diag/mux2_1 /dev/mux2

However if I try to use sam to configure the modem it says:

There are no available ports on the highlighted (selected) mux/serial device
NOTE: One of the possible reasons this may happen is if you are trying to add a modem to a mux port that doesn't support modems .

We have a A6749A PCI 64 Port serial mux adaptor with a J2485A PM16 DM Port module attached....!

Do you need to create the device files for sam to be able to configure the modem?
The PCI_mux0 software is installed.

Thanks

Lyn

[Darren Prior]

Hi Lyn,

I spotted earlier that you mentioned using slot 10, h/w path 1/2 - however your ioscan output shows h/w path 1/4 - which is slot 9. It's possible to misread the slot numbers if your head isn't level with the slots!!!

It looks to me as if the tty device files weren't created after the mux was installed. I'd suggest you run insf -evH 1/4/0/0 to create the tty device files, then run SAM to add the modem.

regards,

Darren.

[Lyn Syms]

Hi Darren,

Thanks for the info, you were completely right about the slot it is slot 9 H/W Path 1/4, and I'm only short....!

I tried the insf -evH command but when using sam it still shows the following:

1/4/0/0 pci_mux0 EISA MUX (0 ports)

Do need any other drivers installed? ie mux2?

Thanks

Lyn

[Darren Prior]

Hi Lyn,

Haha - yeah it's awkward to read the slot numbers if you're either above or below them!

Have you now got some tty's visible when you look at the ioscan output? Did the insf give you their names as they were created, or did it return nothing to the command line?

regards,

Darren.

[Lyn Syms]

Hi ya,

The output from the insf was as follows:

insf: Installing special files for pci_mux0 instance 2 address 1/4/0/0

The ioscan shows the following:

tty 2 1/4/0/0 pci_mux0 CLAIMED INTERFACE PCI Serial (113f0868)
/dev/diag/mux2 /dev/diag/mux2_2 /dev/diag/mux2_1 /dev/mux2

When I go into sam to create add the modem it stills shows 0 ports as follows:

1/4/0/0 pci_mux0 EISA MUX (0 ports)

Do you need to create the special files with mksf manually?

Cheers

Lyn

[Darren Prior]

Hi Lyn,

Hmmm - I would have thought that insf would be able to create the tty's, however your example shows that it created no tty's. In this case I'd suggest using mksf to create a single tty for this h/w path on whatever port you wish to use a modem, then head into SAM.

regards,

Darren.

[Lyn Syms]

Created the files using the following mksf command:

mksf -d pci_mux0 -I 2 -v -a 1

Which output the following:

making cul2a1 c 77 0x020001

However when going into sam it still shows as 0 ports available.......helppppppp!!!!!!

Cheers

Lyn

[Darren Prior]

ah - that'll be because you created a cul device rather than a tty. SAM will only be able to add a modem on a port if there's a tty for it present.

I'd suggest you keep the -d and -v options to mksf that you used, ignore the -l2 -a 1, and instead add these options: -a 0 -H

regards,

Darren.

[Lyn Syms]

Hi ya,

I ran the mksf command you suggested and it created the device file /dev/tty2a1 with the following output from the ioscan:

tty 2 1/4/0/0 pci_mux0 CLAIMED INTERFACE PCI Serial (113f0868)
/dev/cul2a1 /dev/diag/mux2_1 /dev/mux2 /mux2 /dev/diag/mux2_2 /dev/tty2a1

Which shows the device files created but when you try to add the modem using sam it stills shows 0 ports on the mux board.

1/4/0/0 pci_mux0 EISA MUX (0 ports)

and gives the error:

There are no available ports on the highlighted(selected) mux/serial device.
NOTE: One of the possible reasons this may happen is if you are trying to add a modem to a mux port that doesn't support modems.

I'm not sure what to try now!!

Any suggestions, (only nice ones please)...

Thanks

Lyn

[Darren Prior · Accepted solution]

Hi Lyn,

Hmmm - you have 2 choices here:

1) create the other device files required manually, ie create cul and ttyd device files, then edit inttab if you want a getty set up.

2) investigate SAM in greater detail. Check whether you have the latest SAM patches, and that all the SAM filesets are configured.

regards,

Darren.