 
| Subject: | |
| From: | |
| Reply To: | |
| Date: | Tue, 26 Apr 2016 11:29:20 -0400 |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
Have you done any PING test to the Gateway - then further out. Do the results from TRACERT look correct to eliminate bad routing.
Has SNMP's been disabled. You are not losing connectivity due to ICMP Redirects.
Has the patch cable been replaced or even try a different patch panel port.
Billy Brewer
Manager Technical Services
(760) 707-8970
[log in to unmask]
> On Apr 26, 2016, at 11:04, Mark Ranft <[log in to unmask]> wrote:
>
> I think I may have a bad GSP/Multi-function I/O card in an A-Class.
> LINKCONTROL @,ALL shows the server is connected at 100-BT and full duplex.
> We have tried multiple smart switches set to force FULL/100. The transfer
> speed to a local server is slow.
>
> We are considering adding a 100-BT network card as one alternative. Does
> anyone else have any suggestions?
>
> Here is the output from LINKCONTROL:
> Linkname: LAN1 Linktype: PCI 100BT Linkstate: CONNECTED
>
> Physical Path: 0/0/0/0
> Current Station Address: 00-30-6E-C3-12-B3
> Default Station Address: 00-30-6E-C3-12-B3
> Current Multicast Addresses:
> 09-00-09-00-00-01 09-00-09-00-00-03 09-00-09-00-00-04
> 09-00-09-00-00-06
>
> Transmit bytes 52864347 Receive bytes
> 3076287183
> Transmits 951668 Receives unicast
> 2235642
> Transmits no error 951668 Receives broadcast
> 255359
> Transmits dropped 0 Receives multicast
> 0
> Transmits deferred 0 Receives no error
> 2490900
> Transmits 1 retry 0 Recv CRC error
> 0
> Transmits >1 retry 0 Recv Maxsize error
> 0
> Trans 16 collisions 0 Recv dropped: addr
> 101
> Trans late collision 0 Recv dropped: buffer
> 0
> Trans underruns 0 Recv dropped: descr
> 0
> Carrier losses 0 Recv dropped: other
> 0
>
> I think I may have a bad GSP/Multi-function I/O card in an A-Class.
> LINKCONTROL @,ALL shows the server is connected at 100-BT and full duplex.
> We have tried multiple smart switches set to force FULL/100. The transfer
> speed to a local server is slow.
>
> We are considering adding a 100-BT network card as one alternative. Does
> anyone else have any suggestions?
>
> Here is the output from LINKCONTROL:
> Linkname: LAN1 Linktype: PCI 100BT Linkstate: CONNECTED
>
> Physical Path: 0/0/0/0
> Current Station Address: 00-30-6E-C3-12-B3
> Default Station Address: 00-30-6E-C3-12-B3
> Current Multicast Addresses:
> 09-00-09-00-00-01 09-00-09-00-00-03 09-00-09-00-00-04
> 09-00-09-00-00-06
>
> Transmit bytes 52864347 Receive bytes
> 3076287183
> Transmits 951668 Receives unicast
> 2235642
> Transmits no error 951668 Receives broadcast
> 255359
> Transmits dropped 0 Receives multicast
> 0
> Transmits deferred 0 Receives no error
> 2490900
> Transmits 1 retry 0 Recv CRC error
> 0
> Transmits >1 retry 0 Recv Maxsize error
> 0
> Trans 16 collisions 0 Recv dropped: addr
> 101
> Trans late collision 0 Recv dropped: buffer
> 0
> Trans underruns 0 Recv dropped: descr
> 0
> Carrier losses 0 Recv dropped: other
> 0
> Trans jabber timeout 0 Recv watchdg timeout
> 0
> Link disconnects 0 Recv collisions
> 0
> Link speed 100 Recv overruns
> 0
> Link duplex Full Link auto sensed
> No
> Link mode 100Base-TX Core Secs since clear
> 602623
>
> And the NMMGR configuration:
> :netinfo
> NM Configuration Manager 32098-20016 B.07.06 (C) Hewlett Packard Co. 1992
> Reading commands from "NETINFOI.TEMP.SYS".
> NMMGR>openconf NMCONFIG.PUB.SYS
> NMMGR>summaryconf netxport
>
> CRITICAL SUMMARY - NETXPORT CONFIGURATION
>
>
> TUE, APR 26, 2016, 10:02 AM
> CONFIGURATION FILE NAME: NMCONFIG.PUB.SYS
> Validated subsystem.
>
>
> NODE NAME:
> BACKUP2.xxx.yyy
> TRANSPORT GLOBAL CONFIGURATION:
> Home Network Name:
> Maximum Inbound Buffer Memory: 2048
> Name Search Method: 1. (None selected)
>
> PACKET EXCHANGE PROTOCOL (PXP) CONFIGURATION:
> Checksum Enabled: Y
> Retransmission Interval (Secs): 10
> Maximum Retransmissions Per Request: 4
>
> TRANSMISSION CONTROL PROTOCOL (TCP) CONFIGURATION:
> Checksum Enabled: Y
> Maximum Number of Connections: 20000
> Retransmission Interval Lower Bound (Secs): 1
> Maximum Time to Wait For Remote Response (Secs): 180
> Initial Retransmission Interval: 2
> Maximum Number of Retransmissions: 8
> Connection Assurance Interval: 60
> Maximum Connection Assurance Retransmissions: 4
>
> CONFIGURED NETWORK INTERFACES:
>
> Network Interface Type: LAN
> Network Interface Name: LAN1
> Network Interface IP Address: C 192.168.005 220
> IP Subnet Mask: 255.255.255.000
> Network Segment Size: 1514
> HP UPC Number: 08-00-09
> Number of Outbound Buffers 4096
> Enable Ethernet: Y
> Enable IEEE802.3: Y
> Number of Store and Forward Buffers: 0
> Load Network Directory Mappings: No
>
> PROBE PROTOCOL CONFIGURATION:
> Proxy Enabled: No
>
> Probe Requests Proxy Requests
>
> 2 2 Retransmission Maximum
> 1 4 Retransmission Timeout (Seconds)
>
> ADDRESS RESOLUTION PROTOCOL (ARP):
> Retransmission Maximum: 2
> Retransmission Timeout Value: 1
>
> NETWORK INTERFACE LINKS:
> LINK NAME: LAN1 TYPE: BT100
> Enable Idle Device Timer: N
>
> Physical Path: 0/0/0/0
> Factory Configured address: Y
> Local station address: FF-FF-FF-FF-FF-FF
> Use Auto negotiation: N
> Link Speed: 100
> Full Duplex mode: Y
>
> INTERNET CONFIGURATION:
>
> Neighbor Gateway Name: OS Gateway IP Address: C 192.168.005
> 225
> Reachable Networks:
> IP Network Number IP Subnet Mask Hops
> ----------------- -------------- ----
> A 000 000.000.001
>
>
> -------------------------------------------------------------------------
>
> Output completed successfully.
>
>
> NMMGR>exit
> :
>
> Mark Ranft
> Pro3K
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|
