Tag Archives: BOOTP

Business, Finance, Occupation & Industry

Belden's Lumberg Automation Brand Adds the LioN-R Series for PROFINET and EtherNet/IP Applications

Leave a comment

By Business Wirevia The Motley Fool

Filed under:

Belden’s Lumberg Automation Brand Adds the LioN-R Series for PROFINET and EtherNet/IP Applications

ST. LOUIS–(BUSINESS WIRE)– Belden Inc., a global leader in signal transmission solutions for mission-critical applications, has extended its Lumberg Automation product line in the Americas region to include three new I/O modules featuring industrial protection class IP67. They provide secure connection between actuators/sensors and control units even under the harshest environmental conditions. Providing additional support for real-time (RT) and isochronous real-time (IRT) communication, the modules offer 16 digital channels configured as inputs, outputs or a combination of both. All versions come with an encapsulated metal housing, vibration-resistant M12 connection technology and short-circuit proof outputs. Galvanic separation between the I/O channels and the LAN connection ensures reliable data transmission. The behavior of output channels in the event of a fault can be defined via a fail-safe function (PROFINET). What’s more, the easy diagnostics concept allows faults to be located swiftly. An integrated dual-port switch (10/100 Mbit/s) allows both line and ring topologies.

Designed to operate in more extreme environments, the I/O modules have an operating temperature range of -10°C to +60°C and a 24VDC power supply for industrial environments.

Both LAN ports are equipped with four-pole M12 connectors with D coding. The 16 I/O sockets, each of which can send and/or receive two digital signals, have five-pole A-coded M12 connectors. To prevent confusion, both the I/O connectors and the network ports are color-coded.

The IP address for the modules is set up via the BOOTP or DHCP protocol. The controller user interfaces can be used for direct configuration of the modules. The optimum arrangement of the I/O slots makes them easy to use, even with T distributors.

Hiyam Wakeem, product manager for Lumberg Automation, adds insight to the LioN-R for PROFINET: “Key differentiator features relative to the competition are the fail safe function, high temperature range and full galvanic isolation. LioN-R can be integrated with the Lumberg LioN-Link product offering.”

She goes on to add, “LioN-R modules for the EtherNet/IP application are ruggedized and provide maximum security for EtherNet/IP data communication, guaranteeing highly productive machines and systems.”

  • For more information on LioN-R modules for PROFINET applications, download the Product Bulletin.
  • The Product Bulletin the LioN-R modules for EtherNet/IP applications is also available for download.

Lumberg Automation products …read more
Source: FULL ARTICLE at DailyFinance

Linux

Help with NMAP

Leave a comment

By renoir611

I’m seeing a persistent address showing up on my firewall router logs. The address is 10.98.115.9:67, and is broadcasting to 255.255.255.255. I know that this would typically signal a BOOTP service, such as a bootp server announcing itself on the network. But I can’t isolate which machine it is. I have only one machine running, then turn off the standalone wireless router and the switch, but it continues to show up. I ran nmap against it, and it automatically included another, completely different, IP in the scan. It’s got me baffled. Here’s the output:

Code:
Ximian1 FC30-3DA9 # nmap -v -unprivilege - Pn 10.98.115.9

Starting Nmap 6.00 at 2013-04-01 18:03 PDT
Invalid target host specification: -
Initiating Ping Scan at 18:03
Scanning 2 hosts [2 ports/host]
Completed Ping Scan at 18:03, 2.35s elapsed (2 total hosts)
Initiating Parallel DNS resolution of 2 hosts. at 18:03
Completed Parallel DNS resolution of 2 hosts. at 18:03, 0.04s elapsed
Nmap scan report for 10.98.115.9 [host down]
Initiating Connect Scan at 18:03
Scanning Pn (80.68.93.100) [1000 ports]
Discovered open port 587/tcp on 80.68.93.100
Discovered open port 25/tcp on 80.68.93.100
Discovered open port 110/tcp on 80.68.93.100
Discovered open port 22/tcp on 80.68.93.100
Discovered open port 995/tcp on 80.68.93.100
Discovered open port 53/tcp on 80.68.93.100
Discovered open port 21/tcp on 80.68.93.100
Discovered open port 80/tcp on 80.68.93.100
Completed Connect Scan at 18:04, 16.47s elapsed (1000 total ports)
Nmap scan report for Pn (80.68.93.100)
Host is up (0.17s latency).
rDNS record for 80.68.93.100: tedside.pitcairn.net.pn
Not shown: 988 closed ports
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
25/tcp open smtp
53/tcp open domain
80/tcp open http
110/tcp open pop3
135/tcp filtered msrpc
139/tcp filtered netbios-ssn
445/tcp filtered microsoft-ds
587/tcp open submission
593/tcp filtered http-rpc-epmap
995/tcp open pop3s

Read data files from: /usr/bin/../share/nmap
Nmap done: 2 IP addresses (1 host up) scanned in 18.90 seconds

Can anyone shed light on this behavior?

PS. it’s not a one-off thing, I ran it several times and every time it did the same.

…read more
Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

Assistance w/-44P-270

Leave a comment

By RAVC01

Hello,

I was recently given an RS/6000-44P-270 and am attempting to resurrect it for personal use. My current status is as follows:

1 – Required to restore default boot sequence (floppy, scsi, ethernet),
2 – BOOTP fails, restarting does not help surpass this.

What is the most likely cause of this?

I have three RS/6000-44P-270 manuals (i.e., Setup, Users Guide and, Service) and used these documents to identify the hurdles I have identified to this point.

This current issue suggests AIX cannot be accessed. This suggests to me one of several possibilities and need assistance to reduce this list further to a single source so I can successfully return this box to service.

1 – AIX removed from HD at decommission. Does this make sense? I suspect this is unlikely.

2 – The scsi drive is not being accessed (I should have checked electrical connections but, my current issues suggest drive is connected properly but, may not be functioning properly.

Other interpretations?

Please advise.

Thanks,

Rick

…read more
Source: FULL ARTICLE at The UNIX and Linux Forums