Mailing List Archive: can't get ping on foundry

can't get ping on foundry

Jun 14, 2004, 2:42 PM

Post #1 of 5 (2238 views)

We have a new Serveriron going into production and are having some difficulties with getting it connected to the network.
When it is directly connected to my router, neither the router nor the foundry can ping each other.

Here is the relevant information on the foundry, I'm trying to get it connected to the network so we can upgrade the firmware:

ServerIron#ping 192.168.1.1
Sending 1, 16-byte ICMP Echo to 192.168.1.1, timeout 5000 msec, TTL 64
Type Control-c to abort
Request timed out.
No reply from remote host.
ServerIron#sh int
Port Link State Dupl Speed Trunk Tag Priori MAC Name
01 Down None None None None No Normal 00e0.5201.f906
02 Down None None None None No Normal 00e0.5201.f907
03 Down None None None None No Normal 00e0.5201.f908
04 Down None None None None No Normal 00e0.5201.f909
05 Down None None None None No Normal 00e0.5201.f90a
06 Down None None None None No Normal 00e0.5201.f90b
07 Up Forward Full 100M None No Normal 00e0.5201.f90c
08 Down None None None None No Normal 00e0.5201.f90d
09 Down None None None None No Normal 00e0.5201.f90e
ServerIron#sh ver
SW: Version 3.1.11T12 Copyright (c) 1996-1998 Foundry Networks, Inc.
Compiled on Nov 19 1998 at 18:50:39 labeled as SLB03111
HW: ServerIron Switch, serial number 01f906
240 MHz Power PC processor 603 (revision 7) with 32756K bytes of DRAM
8 100BaseT interfaces with Level 1 Transceiver LXT975
1 GIGA uplink interfaces, SX
256 KB PRAM and 8*2048 CAM entries for DMA 2, version 0807
256 KB PRAM and 4*1024 CAM entries for DMA 4, version 0104, SEEQ GIGA MAC
128 KB boot flash memory
4096 KB code flash memory
0 KB BRAM, BM version 02
128 KB QRAM
512 KB SRAM
Octal System, Maximum Code Image Size Supported: 1965568 (0x001dfe00)
The system uptime is 8 minutes 42 seconds

ServerIron#wr term
Current configuration:
!
global-protocol-vlan
!
!
!
!
ip address 192.168.1.2 255.255.255.0
ip default-gateway 192.168.1.1
!
interface e 1
!
interface e 2
!
interface e 3
!
interface e 4
!
interface e 5
!
interface e 6
!
interface e 7
!
interface e 8
!
interface e 9
!
end

And on the router, you can see that it has the foundry's MAC address in the ARP tables:

router#ping 192.168.1.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
nuclearworm#sh arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 192.168.1.1 - 0003.6bba.2d60 ARPA FastEthernet0/0
Internet 192.168.1.2 0 00a0.5201.f906 ARPA FastEthernet0/0

I've already tried different variations of hard-coding each end of the link. It may be a firmware issue but I can't rule that out until I can upgrade the firmware... and I can't upgrade the firmware until I get it connected to the network.

I'm pretty sure it's not the firmware though.

I started it in boot monitor mode and get the following:

BOOT MONITOR> ip address 192.168.1.2 255.255.255.0
BOOT INFO: set ip addr to 192.168.001.002, ip mask to 255.255.255.000
BOOT MONITOR> ip default_gateway 192.168.1.1
BOOT MONITOR> ping 192.168.1.1
No reply from remote host

If it's a firmware issue I'd think that it would work even if just in boot monitor mode.

I've tried all ports, it's an 8 port model and get the same results.

Anything else I should try? I couldn't find an option of upgrading the firmware through the serial port nor could I find any manuals for this older firmware.

Dan Norton
Network Administrator

can't get ping on foundry [ In reply to ]

dan at synccast

Jun 14, 2004, 4:20 PM

Post #2 of 5 (2208 views)

Permalink

Yes, I know it's old, that's why I'm trying to upgrade it with the
current rev (7.4).

I have plugged a laptop directly into it and still cannot get ping. See
the original message for my results with getting it on the network.

Dan Norton
CCNA, MCP
Network Administrator
WareNet/SyncCast
dan@ware.net
dan@synccast.com
(949) 417 - 2300 x 2360
(888) 927 - 3329 (Fax)
Emergency Cell Phone: 949-300-4215
SMS: emergency@ware.net
aim: deveyn
WebSite Development, Web Hosting, Connectivity, Colocation

"When the winds of change blow hard enough, the most trivial of things
can turn into deadly projectiles."

> -----Original Message-----
> From: Cliff Fogle [mailto:Cliff@ofoto.com]
> Sent: Monday, June 14, 2004 1:11 PM
> To: Dan Norton
> Subject: RE: [f-nsp] can't get ping on foundry
>
> Wow...what kind of serverIron is that? That code rev is
> rediculously old. Can you get a laptop hooked up to it and
> pinging? Then you could maybe use solarwinds tftp server to
> upload a new code base. Depending on the model type, the
> latest code revs are in 7.X to 9.X area...
>
> -----Original Message-----
> From: foundry-nsp-bounces@puck.nether.net
> [mailto:foundry-nsp-bounces@puck.nether.net] On Behalf Of Dan Norton
> Sent: Monday, June 14, 2004 11:42 AM
> To: foundry-nsp@puck.nether.net
> Subject: [f-nsp] can't get ping on foundry
>
> We have a new Serveriron going into production and are having
> some difficulties with getting it connected to the network.
> When it is directly connected to my router, neither the
> router nor the foundry can ping each other.
>
> Here is the relevant information on the foundry, I'm trying
> to get it connected to the network so we can upgrade the firmware:
>
>
>
> ServerIron#ping 192.168.1.1
> Sending 1, 16-byte ICMP Echo to 192.168.1.1, timeout 5000
> msec, TTL 64 Type Control-c to abort Request timed out.
> No reply from remote host.
> ServerIron#sh int
> Port Link State Dupl Speed Trunk Tag Priori MAC Name
> 01 Down None None None None No Normal 00e0.5201.f906
> 02 Down None None None None No Normal 00e0.5201.f907
> 03 Down None None None None No Normal 00e0.5201.f908
> 04 Down None None None None No Normal 00e0.5201.f909
> 05 Down None None None None No Normal 00e0.5201.f90a
> 06 Down None None None None No Normal 00e0.5201.f90b
> 07 Up Forward Full 100M None No Normal 00e0.5201.f90c
> 08 Down None None None None No Normal 00e0.5201.f90d
> 09 Down None None None None No Normal 00e0.5201.f90e
> ServerIron#sh ver
> SW: Version 3.1.11T12 Copyright (c) 1996-1998 Foundry Networks, Inc.
> Compiled on Nov 19 1998 at 18:50:39 labeled as SLB03111
> HW: ServerIron Switch, serial number 01f906 240 MHz Power
> PC processor
> 603 (revision 7) with 32756K bytes of DRAM
> 8 100BaseT interfaces with Level 1 Transceiver LXT975
> 1 GIGA uplink interfaces, SX
> 256 KB PRAM and 8*2048 CAM entries for DMA 2, version 0807
> 256 KB PRAM and 4*1024 CAM entries for DMA 4, version 0104,
> SEEQ GIGA MAC
> 128 KB boot flash memory
> 4096 KB code flash memory
> 0 KB BRAM, BM version 02
> 128 KB QRAM
> 512 KB SRAM
> Octal System, Maximum Code Image Size Supported: 1965568
> (0x001dfe00) The system uptime is 8 minutes 42 seconds
>
> ServerIron#wr term
> Current configuration:
> !
> global-protocol-vlan
> !
> !
> !
> !
> ip address 192.168.1.2 255.255.255.0
> ip default-gateway 192.168.1.1
> !
> interface e 1
> !
> interface e 2
> !
> interface e 3
> !
> interface e 4
> !
> interface e 5
> !
> interface e 6
> !
> interface e 7
> !
> interface e 8
> !
> interface e 9
> !
> end
>
>
>
> And on the router, you can see that it has the foundry's MAC
> address in the ARP tables:
>
> router#ping 192.168.1.2
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:
> .....
> Success rate is 0 percent (0/5)
> nuclearworm#sh arp
> Protocol Address Age (min) Hardware Addr Type Interface
> Internet 192.168.1.1 - 0003.6bba.2d60 ARPA
> FastEthernet0/0
> Internet 192.168.1.2 0 00a0.5201.f906 ARPA
> FastEthernet0/0
>
> I've already tried different variations of hard-coding each
> end of the link. It may be a firmware issue but I can't rule
> that out until I can upgrade the firmware... and I can't
> upgrade the firmware until I get it connected to the network.
>
> I'm pretty sure it's not the firmware though.
>
> I started it in boot monitor mode and get the following:
>
> BOOT MONITOR> ip address 192.168.1.2 255.255.255.0 BOOT INFO:
> set ip addr to 192.168.001.002, ip mask to 255.255.255.000
> BOOT MONITOR> ip default_gateway 192.168.1.1 BOOT MONITOR>
> ping 192.168.1.1 No reply from remote host
>
> If it's a firmware issue I'd think that it would work even if
> just in boot monitor mode.
>
> I've tried all ports, it's an 8 port model and get the same results.
>
> Anything else I should try? I couldn't find an option of
> upgrading the firmware through the serial port nor could I
> find any manuals for this older firmware.
>
> Dan Norton
> Network Administrator
>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
>
>
>

can't get ping on foundry [ In reply to ]

dan at synccast

Jun 14, 2004, 8:43 PM

Post #3 of 5 (2221 views)

Permalink

Ping self works fine, but the arp tables are not being populated on the
foundry when I try to ping other hosts.

Dan Norton
CCNA, MCP
Network Administrator
WareNet/SyncCast
dan@ware.net
dan@synccast.com
(949) 417 - 2300 x 2360
(888) 927 - 3329 (Fax)
Emergency Cell Phone: 949-300-4215
SMS: emergency@ware.net
aim: deveyn
WebSite Development, Web Hosting, Connectivity, Colocation

"When the winds of change blow hard enough, the most trivial of things
can turn into deadly projectiles."

> -----Original Message-----
> From: Michael Allen [mailto:mkallen@attglobal.net]
> Sent: Monday, June 14, 2004 5:31 PM
> To: Dan Norton
> Subject: RE: [f-nsp] can't get ping on foundry
>
> Dan, boot monitor is pretty low level, IMO that switch is
> hosed and in need of repair. If you can't ping a directly
> connected host (assuming ip's and masks are correct, and that
> you get link) from boot monitor, I would say its a hardware
> issue. You could try to ping itself from the console, to see
> if that works, and check the mac/arp table on it to see if it
> is learning anything (since it looks like the upstream router
> is), but I don't think those suggestions will be much help.
>
> Mike
>
> At 01:20 PM 6/14/2004 -0700, you wrote:
> >Yes, I know it's old, that's why I'm trying to upgrade it with the
> >current rev (7.4).
> >
> >I have plugged a laptop directly into it and still cannot
> get ping. See
> >the original message for my results with getting it on the network.
> >
> >Dan Norton
> >CCNA, MCP
> >Network Administrator
> >WareNet/SyncCast
> >dan@ware.net
> >dan@synccast.com
> >(949) 417 - 2300 x 2360
> >(888) 927 - 3329 (Fax)
> >Emergency Cell Phone: 949-300-4215
> >SMS: emergency@ware.net
> >aim: deveyn
> >WebSite Development, Web Hosting, Connectivity, Colocation
> >
> >"When the winds of change blow hard enough, the most trivial
> of things
> >can turn into deadly projectiles."
> >
> >
> >
> > > -----Original Message-----
> > > From: Cliff Fogle [mailto:Cliff@ofoto.com]
> > > Sent: Monday, June 14, 2004 1:11 PM
> > > To: Dan Norton
> > > Subject: RE: [f-nsp] can't get ping on foundry
> > >
> > > Wow...what kind of serverIron is that? That code rev is
> > > rediculously old. Can you get a laptop hooked up to it
> and pinging?
> > > Then you could maybe use solarwinds tftp server to upload
> a new code
> > > base. Depending on the model type, the latest code revs
> are in 7.X
> > > to 9.X area...
> > >
> > > -----Original Message-----
> > > From: foundry-nsp-bounces@puck.nether.net
> > > [mailto:foundry-nsp-bounces@puck.nether.net] On Behalf Of
> Dan Norton
> > > Sent: Monday, June 14, 2004 11:42 AM
> > > To: foundry-nsp@puck.nether.net
> > > Subject: [f-nsp] can't get ping on foundry
> > >
> > > We have a new Serveriron going into production and are
> having some
> > > difficulties with getting it connected to the network.
> > > When it is directly connected to my router, neither the
> router nor
> > > the foundry can ping each other.
> > >
> > > Here is the relevant information on the foundry, I'm
> trying to get
> > > it connected to the network so we can upgrade the firmware:
> > >
> > >
> > >
> > > ServerIron#ping 192.168.1.1
> > > Sending 1, 16-byte ICMP Echo to 192.168.1.1, timeout 5000
> msec, TTL
> > > 64 Type Control-c to abort Request timed out.
> > > No reply from remote host.
> > > ServerIron#sh int
> > > Port Link State Dupl Speed Trunk Tag Priori MAC
> Name
> > > 01 Down None None None None No Normal 00e0.5201.f906
> > > 02 Down None None None None No Normal 00e0.5201.f907
> > > 03 Down None None None None No Normal 00e0.5201.f908
> > > 04 Down None None None None No Normal 00e0.5201.f909
> > > 05 Down None None None None No Normal 00e0.5201.f90a
> > > 06 Down None None None None No Normal 00e0.5201.f90b
> > > 07 Up Forward Full 100M None No Normal 00e0.5201.f90c
> > > 08 Down None None None None No Normal 00e0.5201.f90d
> > > 09 Down None None None None No Normal 00e0.5201.f90e
> > > ServerIron#sh ver
> > > SW: Version 3.1.11T12 Copyright (c) 1996-1998 Foundry
> Networks, Inc.
> > > Compiled on Nov 19 1998 at 18:50:39 labeled as SLB03111
> > > HW: ServerIron Switch, serial number 01f906 240 MHz Power PC
> > > processor
> > > 603 (revision 7) with 32756K bytes of DRAM
> > > 8 100BaseT interfaces with Level 1 Transceiver LXT975
> > > 1 GIGA uplink interfaces, SX
> > > 256 KB PRAM and 8*2048 CAM entries for DMA 2, version 0807
> > > 256 KB PRAM and 4*1024 CAM entries for DMA 4, version 0104, SEEQ
> > > GIGA MAC
> > > 128 KB boot flash memory
> > > 4096 KB code flash memory
> > > 0 KB BRAM, BM version 02
> > > 128 KB QRAM
> > > 512 KB SRAM
> > > Octal System, Maximum Code Image Size Supported: 1965568
> > > (0x001dfe00) The system uptime is 8 minutes 42 seconds
> > >
> > > ServerIron#wr term
> > > Current configuration:
> > > !
> > > global-protocol-vlan
> > > !
> > > !
> > > !
> > > !
> > > ip address 192.168.1.2 255.255.255.0 ip default-gateway
> 192.168.1.1
> > > !
> > > interface e 1
> > > !
> > > interface e 2
> > > !
> > > interface e 3
> > > !
> > > interface e 4
> > > !
> > > interface e 5
> > > !
> > > interface e 6
> > > !
> > > interface e 7
> > > !
> > > interface e 8
> > > !
> > > interface e 9
> > > !
> > > end
> > >
> > >
> > >
> > > And on the router, you can see that it has the foundry's
> MAC address
> > > in the ARP tables:
> > >
> > > router#ping 192.168.1.2
> > >
> > > Type escape sequence to abort.
> > > Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is
> 2 seconds:
> > > .....
> > > Success rate is 0 percent (0/5)
> > > nuclearworm#sh arp
> > > Protocol Address Age (min) Hardware Addr
> Type Interface
> > > Internet 192.168.1.1 - 0003.6bba.2d60 ARPA
> > > FastEthernet0/0
> > > Internet 192.168.1.2 0 00a0.5201.f906 ARPA
> > > FastEthernet0/0
> > >
> > > I've already tried different variations of hard-coding
> each end of
> > > the link. It may be a firmware issue but I can't rule
> that out until
> > > I can upgrade the firmware... and I can't upgrade the
> firmware until
> > > I get it connected to the network.
> > >
> > > I'm pretty sure it's not the firmware though.
> > >
> > > I started it in boot monitor mode and get the following:
> > >
> > > BOOT MONITOR> ip address 192.168.1.2 255.255.255.0 BOOT INFO:
> > > set ip addr to 192.168.001.002, ip mask to 255.255.255.000 BOOT
> > > MONITOR> ip default_gateway 192.168.1.1 BOOT MONITOR> ping
> > > 192.168.1.1 No reply from remote host
> > >
> > > If it's a firmware issue I'd think that it would work
> even if just
> > > in boot monitor mode.
> > >
> > > I've tried all ports, it's an 8 port model and get the
> same results.
> > >
> > > Anything else I should try? I couldn't find an option of
> upgrading
> > > the firmware through the serial port nor could I find any manuals
> > > for this older firmware.
> > >
> > > Dan Norton
> > > Network Administrator
> > >
> > >
> > > _______________________________________________
> > > foundry-nsp mailing list
> > > foundry-nsp@puck.nether.net
> > > http://puck.nether.net/mailman/listinfo/foundry-nsp
> > >
> > >
> > >
> > >
> >
> >_______________________________________________
> >foundry-nsp mailing list
> >foundry-nsp@puck.nether.net
> >http://puck.nether.net/mailman/listinfo/foundry-nsp
>
>
>

can't get ping on foundry [ In reply to ]

cliftonr at tikitechnologies

Jun 14, 2004, 9:00 PM

Post #4 of 5 (2207 views)

Permalink

On Mon, Jun 14, 2004 at 05:42:54PM -0700, Dan Norton wrote:
> Ping self works fine, but the arp tables are not being populated on the
> foundry when I try to ping other hosts.

This sounds vaguely familiar, like it might be a problem I had in the
past getting a ServerIron up, but I can no longer remember the details
of how I solved it, or if this is in fact the same problem.

Are you using a cross-over cable between the Foundry and the router? I
remember I had some problems with MDX (auto-crossover detection) on
another switch screwing things up on the ServerIron, but I don't
remember if it related to this.

Also, a suggestion you disable VLANs and don't try to get them working
until you have other stuff going; I've found VLAN interoperability very
very touchy on the ServerIrons. That could conceivably be affecting
the ARP visibility.

-- Clifton

--
Clifton Royston -- cliftonr@tikitechnologies.com
Tiki Technologies Lead Programmer/Software Architect
Did you ever fly a kite in bed? Did you ever walk with ten cats on your head?
Did you ever milk this kind of cow? Well we can do it. We know how.
If you never did, you should. These things are fun, and fun is good.
-- Dr. Seuss

can't get ping on foundry [ In reply to ]

dan at synccast

Jun 14, 2004, 9:11 PM

Post #5 of 5 (2214 views)

Permalink

I tried both connection to a switch via xover cable with auto-neg on and
off (hard coded the ports) because Cisco auto-neg is pretty terrible.

As well as directly connected to a router via cat5 cable. Crossover
cable won't work when connecting foundry-router.

I also tried direct connection to a laptop via cat5.

I also don't have any vlans set up and if you look at my first post it
shows that vlan tagging is not active on all the interfaces and the port
shows up and in a forwarding state.

Dan Norton
CCNA, MCP
Network Administrator
WareNet/SyncCast
dan@ware.net
dan@synccast.com
(949) 417 - 2300 x 2360
(888) 927 - 3329 (Fax)
Emergency Cell Phone: 949-300-4215
SMS: emergency@ware.net
aim: deveyn
WebSite Development, Web Hosting, Connectivity, Colocation

"When the winds of change blow hard enough, the most trivial of things
can turn into deadly projectiles."

> -----Original Message-----
> From: Clifton Royston [mailto:cliftonr@tikitechnologies.com]
> Sent: Monday, June 14, 2004 6:00 PM
> To: Dan Norton
> Cc: Michael Allen; foundry-nsp@puck.nether.net
> Subject: Re: [f-nsp] can't get ping on foundry
>
> On Mon, Jun 14, 2004 at 05:42:54PM -0700, Dan Norton wrote:
> > Ping self works fine, but the arp tables are not being populated on
> > the foundry when I try to ping other hosts.
>
> This sounds vaguely familiar, like it might be a problem I
> had in the past getting a ServerIron up, but I can no longer
> remember the details of how I solved it, or if this is in
> fact the same problem.
>
> Are you using a cross-over cable between the Foundry and the
> router? I remember I had some problems with MDX
> (auto-crossover detection) on another switch screwing things
> up on the ServerIron, but I don't remember if it related to this.
>
> Also, a suggestion you disable VLANs and don't try to get
> them working until you have other stuff going; I've found
> VLAN interoperability very very touchy on the ServerIrons.
> That could conceivably be affecting the ARP visibility.
>
> -- Clifton
>
> --
> Clifton Royston -- cliftonr@tikitechnologies.com
> Tiki Technologies Lead Programmer/Software Architect
> Did you ever fly a kite in bed? Did you ever walk with ten
> cats on your head?
> Did you ever milk this kind of cow? Well we can do it. We
> know how.
> If you never did, you should. These things are fun, and fun is good.
>
> -- Dr. Seuss
>
>