topic Re: new ip assign in Operating System - OpenVMS

new ip assign

Deepak Raheja — Thu, 23 Sep 2010 09:07:38 GMT

Sir,
I am using an Aplhaserver DS10 with Open VMS7.3.Unfortunately one of the Ethernet port is malfunctioning and needs to be replaced,Could any body guide me to add a new IP to Ethernet card in open VMS.
Procedure in Steps will be warm welcomed

Regards,
Deepak Raheja

Re: new ip assign

Joseph Huber_1 — Thu, 23 Sep 2010 10:15:59 GMT

As long as the replaced interface is of the same type and controller number/letter, then there is nothing to do.

If this is not the case,, and the new interface is of different type, then, assuming the TCPIP software is "TCPIP services for VMS",aka UCX:
First, delete the old interface e.g. WE0:
TCPIP SET CONFIG NOINTERFACE WE0
TCPIP SET NOINTERFACE WE0

Then use @sys$manager:tcpip$config menu to define the IP parameter of the new interface:
Configuration options:
1 - Core environment

Re: new ip assign

Andy Bustamante — Thu, 23 Sep 2010 21:22:41 GMT

Adding to Joseph's response, delete the old configuration, shut down the system for card replacment, reboot then configure the new changed interface. Not required if you replace with the same class of adaptor.

TCPIP at this age could cause problems if started with an invalid interface, and you need to start TCPIP services to delete the configuration if the type of adapator has changed.

Re: new ip assign

Deepak Raheja — Fri, 24 Sep 2010 16:15:00 GMT

Thanks Andy/Joseph

I configured the IP address and set the speed Fast FD as per system requirement .But still I am unable to ping my Cisco Switch.Is there some more parameters needs to be set.

apart from @sys$manager:tcpip$config Can I assign an ip through Alpha BIOS too?

Is there some more parameters more to set ?

Regards,
Deepak Raheja

Re: new ip assign

Joseph Huber_1 — Fri, 24 Sep 2010 16:24:08 GMT

>> speed Fast FD as per system requirement
What system requirement ?
Usually speed should be auto-negotiation.
Is the Cisco box also the IP router ?
Did you configure routing after doing the new IP interface configuration ?
Did you restart TCPIP after configuration ?

And no, "Alpha BIOS", which we calle SRM console, can't configure the VMS TCPIPp stack.

Re: new ip assign

Deepak Raheja — Fri, 24 Sep 2010 16:45:28 GMT

Hello Joseph,
My cisco switch and router used Speed 100/Full duplex.More over my Other Ethernet port is also configured on Fast FD (Full duplex).So I use Fast FD.
Is there some requirement to add routing while i am using similar class ip which i was using(IP) in earlier port.
I reset the Decnet TCPIP services too after installing new card in Alphaserver Ds10

Any more ideas,(which i am missing perhaps)

Waiting from you,

Regards,
Deepak Raheja

Re: new ip assign

Joseph Huber_1 — Fri, 24 Sep 2010 16:58:01 GMT

If the routing has not changed, it should be o.k.,
but it does no harm to check it again using tcpip$config.

Independently of IP, check using LANCP to see if the link is up at all:
mcr lancp show device ewa0/internal
is Link state LINKUP ?

mcr lancp show device ewa0/counter
to see if there is incoming/outgoing traffic

Still I would set auto-negotiation via LANCP to see if it is working.

Re: new ip assign

Deepak Raheja — Fri, 24 Sep 2010 17:05:38 GMT

Hello Joseph,

Let me check the points told by you on tomorrow morning,I will update you the same

Regards,
Deepak Raheja

Re: new ip assign

Deepak Raheja — Sat, 25 Sep 2010 12:29:47 GMT

Hello Joseph

Could you please have a look on the attached file.It shows that the Counters are increasing but still I am unable to ping my CISCO switch with my newly installed ethernet card in DS10..

(Could you please let me know the steps procedure documents/any link for installing a new ethernet cards in Alphaserver DS10 with open VMS7.2 plateform

Regards,
Deepak Raheja

Re: new ip assign

Steven Schweda — Sat, 25 Sep 2010 13:48:13 GMT

> Could you please have a look on the
> attached file.

A Microsoft Word document may not be the best
way to convey plain text to a VMS audience.
Why not use plain text?

> [...] Unfortunately one of the Ethernet
> port is malfunctioning and needs to be
> replaced, [...]

You know this how? (If you don't know how to
replace the thing, do you know how to
diagnose a problem with it?) What, exactly,
was the _original_ problem?

> [...] More over my Other Ethernet port is
> also configured on Fast FD (Full duplex).
> [...]

Which "Other Ethernet port" is that?

I also recommend auto-negotiation, unless it
actually causes a problem. On my XP1000, the
firmware normally reports the results of its
auto-negotiation. I assume that a DS10 would
be at least that clever. (VMS does, too,
when it starts up, as I recall.)

> [...] after installing new card [...]

What, exactly did you remove? What, exactly,
did you install (and where)? What, exactly,
did you do after that? What, exactly,
happened when you did it?

Re: new ip assign

Joseph Huber_1 — Sat, 25 Sep 2010 14:14:01 GMT

The LAN counters look o.k.
Since You say EWA0 is malfunctioning, I would remove it as an IP interface:
TCPIP SET NOINTERFACE WE0
TCPIP SET CONFIG NOINTERFACE WE0
then shutdown/restart TCPIP.
I'm not really experienced in VMS TCPIP, but I can imagine the system tries to use the first interface enabled in the same subnet, the bad one.
Also check the routing tables
TCPIP SHOW ROUTE

Did You try to reach other destinations than the gateway in the same subnet ?
TCPIP SHOW ARP
shows eventually which ones are seen.

Re: new ip assign

Joseph Huber_1 — Sat, 25 Sep 2010 15:06:39 GMT

Also to check:
is the interface raechable from a different system: ping the the new interface (using its IP address, not name).
If it responds, than it is a hint it is working, and should work also outgoing if used, i.e. after EWA0 is disabled.

Re: new ip assign

Deepak Raheja — Tue, 28 Sep 2010 04:50:25 GMT

I have multiple Alpha server DS10 running at various different location. All DS10 servers using 2 Ethernet ports mounted on motherboard only calling LAN-A & LAN-B.
Suppose one site say EF0DS1 running on two LANs (LAN-A & LAN-B) at a remote location. The IPs for LANs are as followings:
EF0DS1 LAN-A â 172.16.136.74/26
EF0DS1 LAN-B â 172.16.166.74/26

Now EF0DS1 LAN-A became faulty and needs to be replaced so as it is mounted on a motherboard,We added a new Dual SCSI combo Ethernet card in PCI slot.We had that card spare in our stock so we choosed to used it.

Now as I already told it is a remote site,so before sending the card to there,I wanted to check the connectivity of that combo card on my plateform.As like the remote location DS10,I have a DS10 named EA0DS1,again running with two LANs(LAN-A LAN-B)The IPs are as followings

EA0DS1 LAN-A â 172.16.128.74/26
EA0DS1 LAN-B â 172.16.160.74/26

Now what I did I add my combo Ethernet card on my DS10 server(installed at plateform) and was able to see it in SHOW|MORE
EWC0 (newly installed combo card)

I assigned it a spare IP 172.16.128.111/26 set at FAST FD with LANCP and CORE Environment and INTERFACE options.I reset the DECNET TCPIP services after assigning IP to new card.I am able to see the counters increasing but surprisingly I am unable to ping my cisco switch/router(172.16.128.88/172.16.128.89)

Any Idea why it is not pinging ?

Regards,
Deepak Raheja

Re: new ip assign

Joseph Huber_1 — Tue, 28 Sep 2010 18:00:56 GMT

Did You try to remove the WE0 (EWA0) interface ?
Last time You showed EWA0: and EWC0: both connected, and EWA0: still counting.

Re: new ip assign

abrsvc — Tue, 28 Sep 2010 18:17:48 GMT

Make sure that the gateway addresses are set up correctly as well for the new cards.

Dan

Re: new ip assign

Deepak Raheja — Wed, 29 Sep 2010 03:26:51 GMT

Hello Joseph,
No I didnot remove EWA0(172.16.128.74)it is working as LAN-A (with motherbaord DS10 port)at present situtaion is

EWA0-172.16.128.74/26(working as LAN-A)onboard ethernet
EWB0-172.16.160.74/26(working as LAN-B)onboard ethernet

EWC0-172.16.128.111/26(not working)External card.I used a spare IP from LAN-A series.

Is it requires to unassign EWA0 if I am using a same class spare ip in same machine(for e.g EWC0 here).In other words can't I use two same class ip to access same LAN/Switch ?

Waiting for yours valuable views.

Regards,
Deepak Raheja

I have correctly set the gateway,Dan

Re: new ip assign

Joseph Huber_1 — Wed, 29 Sep 2010 05:38:59 GMT

If EWA0 is working, then no, need not be disabled.
But how do You know EWC0 is not working ?
Since EWA0 and EWC0 is in the same subnet, I assume it will go over EWA0: as long this is working ( I assume LAN failover is not setup according to the interface names).
Is the ping to cisco "not working" t
he only problem, or is there no connection to x.x.128.* at all on the system with working EWA0: ? The LAN counters showed a lot of traffic, both incoming and outgoing.
Are other protocols (Decnet, cluster, LAT) active ?

Re: new ip assign

Deepak Raheja — Wed, 29 Sep 2010 07:50:19 GMT

Thanks Joseph,
When I am removing my LAN-A(172.16.128.74) cable,in that case I should be able to ping my LAN A swich.But it is not pinging however IO counters are increasing.
Is it require to activate some protocols too,yet the same machine is working fine with same class IP i.e LAN-A. or we have to activate the services for each individual physical device say LAN A port,LAN B port, LAN c port. Sorry,But I doubt..
In my sense we needs to activate the protocols for machine specific.doesnot matter how much cards we insert in machine.
Waiting yours feedback.

Regards,
Deepak Raheja

Re: new ip assign

Joseph Huber_1 — Wed, 29 Sep 2010 08:26:10 GMT

>>
When I am removing my LAN-A(172.16.128.74) cable,in that case I should be able to ping my LAN A swich.
<<
No, since there is no LAN Failover, TCPIP will still trye to use EWA0:.Since You are not willing to disable interface WE0/EWA0 to prove that, I have no more ideas, somebody else ?
>>
Is it require to activate some protocols too,yet the same machine is working fine with same class IP i.e LAN-A. or we have to activate the services for each individual
<<
No, it was just a question: if e.g. DECnet would work, then the it proves the interface is o.k., but IP has a problem.

Also what was the answer to trying to access x.x.128.111 from the outside, i.e. ping from some other node ?
This would also prove the we2/ewc0 interface is o.k.

Re: new ip assign

Deepak Raheja — Wed, 29 Sep 2010 09:06:51 GMT

ok jOSEPH,
I think I should unassign LAN A(172.16.128.74), & then I should check the newly installed card behaviour(172.16.128.111).(ofcourse you were already asked to do)

I will let you know the result after doing the said activity.

Keep in touch

Regards,
Deepak Raheja