IBM Token Ring 16/4 PCI adapter2?

I've been scouring the web looking for drivers/instructions/help on installing this particular card on a Solaris 7 box. IBM only supports the M$ line and OS/2. Some people had posted asking about it, but no answers...
The system recognizes the card - I get a link light on my MAU when I boot up, but there isn't a tr0 device to plumb. I'm kind of a Solaris newbie (didn't have any problems with Linux or FreeBSD :), does anyone have any suggestions? Offline replies are also fine ([email protected]).
Thanks in advance,
SfS

Similar Messages

DLSw over WAN to Ethernet to Token Ring

Currently, a 3745 in Portland is token ring attached and SNA traffic travels that ring to an IBM 2210 router.
That IBM router connects to a second token ring, which a Cisco 2613 is also connected to. From there
the traffic travels DLSw over the WAN (3 T1s, Multilink PPP bundle) to a 7507 in Cincinnati where a 3745
is connected via serial.
3745-TIC<->TR<->2210<->TR<->2613(DLSw)<->WAN<->(DLSw)7507<->LIC-3745
The 7507 serial port is configured as follows:
interface Serial4/3
description 3745 LIC connection for Fred Meyer DLSW
mtu 4400
no ip address
encapsulation sdlc
no ip mroute-cache
no keepalive
serial restart-delay 0
clockrate 125000
sdlc vmac 4000.3745.0000
sdlc N1 35200
sdlc address 29 seconly
sdlc partner 4000.0910.0008 29
sdlc dlsw 29
The 2613 has an ethernet. The folks in Portland want to move off of the TR and on to Ethernet.
They will replace the IBM router with one that has both TR and ENET.
If we move to the ethernet, the result will be:
3745-TIC<->TR<->2210<->ENET<->2613(DLSw)<->WAN<->(DLSw)7507<->LIC-3745
Should I change the MTU size on the serial port to 1500 (Ethernet)?
Are there any changes that should occur on the 3745/Mainframe side?
Do you see any other issues?

You cannot increase the MTU for ethernet larger than 1500 bytes because 802.3 (the standard for ethernet) does not allow that.
You may see issues. The problem is that both 3745 does not know the existance of the ethernet. If either 3745 sends a packet larger than 1500 bytes, the 2613 will drop the packet. (I am not an expert on 2210, I do not know if the 2210 is smart enough to segment the SNA packet into 2. I doubt it does, but please confirm it with IBM.) This causes the remote FEP detects a gap in SDLC, LLC2, or TH sequence number. No matter which layer detects the problem. The end result is still the same. The DLSw circuit will be disconnected.
There are several suggestions to your problem:
1. Make sure the both FEP will not send any PIU larger than 1500 bytes. This can be done either on the NCP gen or modtab. Checking the modtab is tough because your system programmers have to know all application running over the link. Then, they have to check the corresponding modtab entry for the applications.
2. run DLSw between 7507 to IBM 2210
3. directly connect the 2613 to the TIC (3745)

Token ring

can anyone explain in an easy way how this works, do people still use it, do you still need a switch to set this up or is it from pc to pc ?
thanks

Token Ring ... I thought I was out, but they pulled me back in ......
Token Ring, as the name suggests, uses a logical ring topology (topology = "What shape is it?") that is usually a physical star (i.e., central hub, with spokes to the hosts).
One of the hosts on the ring is considered a "Master;" he generates a bit pattern that is recognized as a "token."
The Token is send to the Master's downstream neighbor. The rule of Token Ring is that a station is not allowed to put data on the ring unless it controls the Token.
If the station that has the Token doesn't have any data to send, it regenerates the Token and sends it to his downstream neighbor. This continues ("passing the Token") until one of the hosts has data to send.
If the host has data, it sets a flag in the Token, affixes the data, and send the Token+Data downstream.
As each host receives the Token+Data, it looks at the destination address. If it is addressed to him, he copies the data (and send it up the stack), sets another flag in the Token to indicate the the data was "copied." When the transmitting station gets the Token(+Data) back, he sees the "copied" flag, and flushes the data.
The Master watches the Token+Data circulate on the ring; if he sees the same Token+Data more than once, he decides that the transmitter was lost and removes the Data, regenerates the Token, and sends it on.
That's it in a very basic nutshell.
You cannot do back-to-back connections with Token Ring ... you must use a Multi-Station Access Unit (MAU) or a device that emulates one (Token Ring Switch). This is because the original Token Ring was meant to be able to have MAUs in the ceiling (for example) where there is no power. Each station provides (indivisually and collectively) the power to operate the MAU.
The 802.5 spec also provides a sequence for how a host enters the ring ... that cannot really be emulated in a host-to-host connection.
Again, that's it in a very brief nutshell. There is not enough space in a single post to provide a detailed description.
Token Ring is still being used in some shops, most are using "Big Iron" (IBM Mainframes). Token Ring is very dependable and provides a self-healing physical architecture.
It tends to be a little on the expensive side.
Let us know if you have any additional questions.
Good Luck
Scott

Pcmcia token ring card problems or how to compile a module?

i have a pcmcia token ring ibm card. i run 2.6.23-ARCH kernel. I know that the correct module is ibmtr_cs (from a previous distribution). When i trie to modprobe ibmtr_cs it tells me that the module doesn't exist. Searching my system i found that in /usr/src/linux-2.6.23-ARCH/include/linux/ibmtr.h there is something like a module... Does this mean that i have to compile my own kernel? in this case how can i do it? is it possible to compile only the module?
thanks nik
Last edited by nicnikf (2008-01-18 19:57:08)

nicnikf wrote:
i have a pcmcia token ring ibm card. i run 2.6.23-ARCH kernel. I know that the correct module is ibmtr_cs (from a previous distribution). When i trie to modprobe ibmtr_cs it tells me that the module doesn't exist. Searching my system i found that in /usr/src/linux-2.6.23-ARCH/include/linux/ibmtr.h there is something like a module... Does this mean that i have to compile my own kernel? in this case how can i do it?
thanks nik
Maybe you only have to compile that module, for your kernel, instead of a whole kernel recompile? On how to do that, I don't know, sorry.
Maybe someone else knows.

SNA Server on Ethernet cannot talk to AS/400 on token ring

We have an SNA server on Ethernet and it cannot talk to a token ring device Q159462 from microsoft suggests to disable LLC local Acknowledgement.
Does anyone have any suggestions and how can I disable LLC?

You can do DLSw FST. I do not find an example of FST. The configuration guide for FST is as follows:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fibm_c/bcfpart2/bcfdlsw.htm#1002472
Basically, it has a very similar configuration as TCP encaupsulation. Just replace "TCP" by "FST" in the dlsw remote-peer statements.
Please note that FST does not offer segmentation/fragmentation. If the LLC2/DLC frames are larger than 1400+ bytes, the router just drops the packets. Make sure that the token ring stations do not send packets larger 1400+ bytes.
For your information, RIF passthrough is another useful option. Please note that RIF pass through DOES NOT support token ring to ethernet, as documented in the following URL:
http://www.cisco.com/warp/public/cc/pd/ibsw/ibdlsw/tech/dls24_rg.htm
One final comment. I have been supporting DLSw and Cisco routers for 4 years. I have worked with a lot of customers setting up MS SNA server and Cisco routers. I have never worked on a case which Cisco routers fail to forward SAMBE. I am working with the development group and find out if this is an IOS bug or not.

Connecting ethernet to token ring

I'm having trouble trying to configure cisco 2612 router to connect SNA server to datacenter host. please refer to connectivity below.
SNA server--eth----router--t/r--control unit--modem-SDLC---modem---FEP
the controller unit has token ring card installed on it and it's connected to router's t/r port..i configured the router with SR/TLB but no success, what we did we temporarily removed the router and add token ring adapter on the same SNA server then connect direct to control unit and it's work but we need to implement the connectivity shown above..thanks

Hi Matthias,
working topology:SNA server with 2 NIC ethenet and T/R
--eth-SNA-t/r---control unit-modem--sdlc--modem--FEP
with router:not working
SNA-eth-router-t/r-control unit-modem-sdlc-modem-FEP
please checked the router config below, thanks
Current configuration : 686 bytes
version 12.1
no service single-slot-reload-enable
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
hostname Router
enable secret 5
ip subnet-zero
no ip routing
source-bridge ring-group 20
source-bridge transparent 20 10 2 5
interface Ethernet0/0
ip address 10.10.50.2 255.255.255.0
no ip route-cache
bridge-group 2
interface TokenRing0/0
no ip address
no ip route-cache
ring-speed 16
source-bridge 5 2 20
ip default-gateway 10.10.50.1
ip classless
ip http server
bridge 2 protocol ieee
bridge 2 bitswap-layer3-addresses
line con 0
line aux 0
line vty 0 4
password
login
Ethernet0/0 is up, line protocol is up
Hardware is AmdP2, address is 000e.3853.fae0 (bia 000e.3853.fae0)
Internet address is 10.10.50.2/24
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:01, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue :0/40 (size/max)
5 minute input rate 1000 bits/sec, 2 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
3789 packets input, 364786 bytes, 0 no buffer
Received 2964 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
354 packets output, 39668 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
TokenRing0/0 is up, line protocol is up
Hardware is HAWKEYE, address is 0070.1cca.5f87 (bia 0070.1cca.5f87)
MTU 4464 bytes, BW 16000 Kbit, DLY 630 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation SNAP, loopback not set
Keepalive set (10 sec)
ARP type: SNAP, ARP Timeout 04:00:00
Ring speed: 16 Mbps
Duplex: half
Mode: Classic token ring station
Full duplex capable
Source bridging enabled, srn 5 bn 2 trn 20 (ring group)
spanning explorer disabled
Group Address: 0x00000000, Functional Address: 0x0800011A
Ethernet Transit OUI: 0x000000
Last Ring Status 00:05:14 (0x2000)
Last input 00:00:00, output 00:00:03, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue :0/40 (size/max)
5 minute input rate 1000 bits/sec, 1 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
2794 packets input, 449251 bytes, 0 no buffer
Received 962 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
390 packets output, 31117 bytes, 0 underruns
0 output errors, 0 collisions, 8 interface resets
0 output buffer failures, 0 output buffers swapped out
0 transitions

How to handle DLSw for SDLC and token-ring to same remote peer

We have the need to have SDLC and token-ring connections from one local router to a the same remote site. Currently we have a remote peer for token-ring:
dlsw port-list 10 TokenRing0/0
dlsw remote-peer 10 tcp a.b.c.d lf 1500
We have an SDLC link on a serial port. I understand that SDLC is part of group 0. How do I also get the SDLC traffic to the same remote peer? Is it as simple as adding another remote peer statement to the same IP?
dlsw remote-peer 0 tcp a.b.c.d lf 1500

Do you have your token ring configuration complete to bridge to DLSW ?
for example;
source-bridge ring-group 2000
dlsw local-peer peer-id 150.150.10.1
dlsw remote-peer 0 tcp 150.150.10.2
interface loopback 0
ip address 150.150.10.1 255.255.255.0
interface serial 0
ip address 150.150.11.1 255.255.255.192
interface serial 1
description PU2 with SDLC station role set to secondary
no ip address
encapsulation sdlc
no keepalive
clockrate 9600
sdlc role primary
sdlc vmac 4000.9999.0100
sdlc address 01
sdlc xid 01 05d20006
sdlc partner 4000.1020.1000 01
sdlc dlsw 1
interface serial 2
description Node Type 2.1 with SDLC station role set to negotiable or primary
encapsulation sdlc
sdlc role prim-xid-poll
sdlc vmac 1234.3174.0000
sdlc address d2
sdlc partner 1000.5aed.1f53 d2
sdlc dlsw d2
interface tokenring 0
no ip address
ring-speed 16
source-bridge 100 1 2000
source-bridge spanning
If your SDLC link is working through DLSW (it is in DLSW ring group 10 according to your first configuration statement and port list statement and must match at both ends), it should be an easy modification to add the token ring configuration to join the bridge to the remote DLSW router.
See;
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fibm_c/bcfpart2/bcfdlsw.htm#1003756
best of luck

Token Ring Connectivity issue

I have a network set up at work with 2 MAC PROs, an iMAC and a partitioned DROBO NAS connected via token ring. The Partitioned DROBO is connected to MAC 3 via ISCSI. An alias for each of the drobo partitions was created on the desktop of MAC 3. Mac 2 and 1 on the network can connect to partition one of the drobo, labled NUMBER 1, however the alias for partition 2, "NUMBER 2" is sending MAC 1 and MAC 2 to their internal hard drives. I have checked the alias for NUMBER 2 and it is pointing to the right location. I have checked the permissions for "NUMBER 2" and they mirror the NUMBER 1 drobo partition. At this point I am at a loss and any help that can be given would be appreciated. Thank you ahead of time.

Won't you share some more details of what the problem (and the solution) turned out to be?
Some readers attempt to find answers to the same problem, and do a search. If they turn up your post, there could be more insight to help them solve their problem, but you have not included any.

Routers Vs 3745 token-Ring

I am a beginner on technology Cisco, here my problem. Today I have 2 3745 with a different address Token Ring, I replace this old technology by a router Cisco 72XX and a card CPA, I hope that you include/understand me. Now, I use card CPA. How to make to keep the same SAP addresses on the 2 addresses Token Ring of the 3745, while using on the Cisco the function "lan Token Ring". Which are the commands to be activated on the router to describe this function

Hi Francis, The quick answer is that the SAPs are defined and activated in "XCA" nodes on the mainframe. You may want to have a look at -
http://www.cisco.com/en/US/partner/tech/tk331/tk332/technologies_tech_note09186a0080094248.shtml
to walk you through the process.
Rgds, Dan

DLSw Token Ring to Ethernet - Remote Peer MAC

Hi,
Refer to following link, http://www.cisco.com/en/US/partner/tech/tk331/tk336/technologies_configuration_example09186a0080093ecd.shtml
If there is host attached Ring 500 with MAC 0000.1111.0000 (non-canonical) ,another host attached to router B E0, MAC 0000.2222.0000 (canonical)
1) If I configure dlsw mac-address command at router A , should the MAC address configure should change non-canonical ?
2) If I want to configure dlsw mac-address command at router B , is the configure MAC address remain as non-canonical ?
May be you can explain more about the scenerio about when or where to bit swap the MAC address of configuration.
Best Regards.

Hi,
I get confusing. To make it simple I include the config and example.
Assume Token ring host is non-canonical and ethernet host is canonical. Please refer R1 & R2 config at the end.
Regards.
Scenario 1
Token Ring Host ---- R1 ===DLSW=== R2 ----Ethernet Host
(Answer)
XXXX.XXXX.XXXX - should convert to non-canonical
YYYY.YYYY.YYYY - remain non-canonical
Scenario 2
Ethernet Host ---- R1 ====DLSW==== R2 --------Ethernet Host
(Answer)
XXXX.XXXX.XXXX - should convert to non-canonical
YYYY.YYYY.YYYY - should convert to non-canonical
OR ?
XXXX.XXXX.XXXX - remain canonical
YYYY.YYYY.YYYY - remain canonical
which one ??
Best Regards.
R1
dlsw local-peer peer-id 1.1.1.2
dlsw remote-peer 0 tcp 1.1.1.1
dlsw mac-addr XXXX.XXXX.XXXXX remote-peer ip-address 1.1.1.1
R2
dlsw local-peer peer-id 1.1.1.1
dlsw remote-peer 0 tcp 1.1.1.2
dlsw mac-addr YYYY.YYYY.YYYY remote-peer ip-address 1.1.1.2

Token Ring Redundancy

Does anyone knows a way to create a virtual mac in a token environment.
I can't use HSRP becouse the MAC i am trying to deploy isn't a functional one.

I can't use the Bia command becouse when there is a comutation from the active to the standby router, de virtual Mac address is automaticaly changed ( the other router bia address).

Virtual Token Ring Interfaces

One of my 6500 MSFCs has a number of these virtual interfaces configured - though there are no associated interface configuration commands.
I can't find any explanation about what these are for on CCO. I strongly suspect that I can delete them, but I have to be sure.
Can anyone help?

Hi,
virtual tokenring interfaces are typically used in an environment where snasw is used.
Historically this was/is the entry point when you have physical tokenring interfaces and you srb into the virtual tokenring and then you define the virtual tokenring interface as a snasw port. Can also be used with srtlb and physical ethernet.
The downstream appn/sna devices would then connect to the mac address defined on the virtual tokenring interface.
To make a long story short a 6500 msfc does neigher support physical tokenring interfaces nor snasw.
So as long as there is no other configuration on your system. Something like a dspu might be able to use the vtok, then you can simly delete the vtok interfaces.
thanks...
Matthias

5505 FDDI connectivity to IBM mainframe

hi,
I have the following:
1-IBM mainframe:
- has two OSA cards (with FDDI ports)
- Each OSA has two IP address's one for TEST and one for Production
- The two OSA have different MAC address.(user defined MAC)
2- two Ciso 5505:
-Each switch has FDDI module
The old setup:
Before,I have 2 old hubs (not cisco) connecting to the two OSA through token ring,the mainframe OSAs are configured now for this setup.
The new setup (which I want to make)
to connect the two 5505 to the two OSA by FDDI ,in this case I'll get two dual ring ,one for each OSA.
I would like to know what is the correct connection between them?
Do I need to add additional configuration between the two OSA on the mainframe (since now I'll have Dual ring not single ring)?
please I need any information about this problem.

Since there has been no response to your post, it appears to be either too complex or too rare an issue for other forum members to assist you. If you don't get a suitable response to your post, you may wish to review our resources at the online Technical Assistance Center (http://www.cisco.com/tac) or speak with a TAC engineer. You can open a TAC case online at http://www.cisco.com/tac/caseopen
If anyone else in the forum has some advice, please reply to this thread.
Thank you for posting.

17" IBM LCD Monitor

I have an 17" IBM LCD Monitor with VGA. Kan I hook it up to my MacBook with a mini DVI to VGA, and what about the resolution? In windows I use 1280 * 1024, but it seems the the highest resolution for a non-widescreen is 1024 * 768. Will that change when i connect the cabel, or do I have to live with the low resolution?

I had some time and went back to disabling monitors / video cards and trying different series of configs. I have a solution of sorts that I can work with. I wish my original config could work but this config I have now will suffice.
My method to finding a working solution was along the lines of robodog2’s. I went down to just one monitor (IBM 17”, GeForce FX5500 128mb PCI) and experienced the same problem. I then went down to one 19” monitor (Dell 19” Quadro NVS 290 256mb PCIe) and problem was solved. I then brought back up the second Dell 19” monitor (on same NVS 290 vid card) and everything worked fine. I had excellent playback in the Program monitor. I then brought the IBM monitor back online but I left the first 19” monitor as my “primary monitor” and everything worked perfect. I tried to drag Premiere window to the IBM and the problem returned-no playback in Program monitor. But I was able to drag the window back to the Dell and playback worked fine.
My normal set up was to have the IBM be my main monitor and I worked off the two Dell monitors. Seems I now have to have a Dell monitor be my “primary monitor” under Display Properties…Settings, for Premiere to work properly. I’ll just have to re-arrange some desktop work space but I can set up the IBM to act like my primary and work on the Dells. Apparently something in Premiere see’s something in the “primary monitor” video card it likes.
Thanks to all who offered help. I’m still a bit confused as to why my original configuration wouldn’t work though. But I’ll consider my problem answered as of this time.
Jeff

Rsrb with multiple ring groups on head ends with one phy ring?

working on an issue for a customer and I cant find good documentation on this anywhere for multiple ring-groups
have 2 routers, each with 2 ring groups connected on a mau terminating multiple serial connections (wan, hence the rsrb) and utilizing rsrb tcp with local ack. The configuration was done sometime ago. It was set up to utilize frame which now they are using ptp t1s. I see in the remote routers they are forwarding pakcets to both routers to ring 20. (there are 2 routers if one fails then it is meant to learn its path to the CIP through the other router)
---------router1
source-bridge ring-group 30
source-bridge ring-group 31
blahblah peers tcp local-ack
int t0
source-bridge 20 1 30 <----notice bridge 1
source-bridge spanning
int t1
source-bridge 20 1 31 <----notice bridge 1
source-bridge spanning
--------router2
source-bridge ring-group 30
source-bridge ring-group 31
blahblah peers tcp local-ack
int t0
source-bridge 20 2 30 <----notice bridge 2
source-bridge spanning
int t1
source-bridge 20 2 31 <----notice bridge 2
source-bridge spanning
I thought the physical rings had to be different in order to run parrallel links. Or are different bridge #'s feasible? The end issue they are having is that when links bounce, they are not releasing the tcp session and the show llc shows remote sides as busy and the head end as connected. (then obviously removal of local ack fixed the issue)
Not ready to live without local ack... could the same ring # on both routers be the issue since they are on the same mau and destined for the same location?
==MAU to CIP==
| | | | all physical connection on mau are ring 20
router1 router2
| | | | | ring groups 30 and 31 configured on both routers with 1 statement to each router in the network per router (so each remote side is only connected to either ring group 30 or 31 (not both since you can only do over token ring) and the show source-bridge is showing forwards to each head end router's physical ring 20. I thought I would see one with forwards the other 0 since first response, but then saw the bridge # differed.)

case was opened over a month ago with no luck or serious help. Have had great luck in the past with tac, but this one was frustrating and nothing was done.
case#D039413
And the remote routers connect directly to the cip with LLC2. (end to end connection, not remote to router 1 and 2 to CIP)
show llc shows the local mac of the gateway and the cip token.
the network goes like this
rr = remote router
fr= frame relay
ptp= ptp t1
rtr1 and rtr2 = router 1 and 2
rr--fr--rr--ptp--rtr1 and rtr2 ---rr---cip
I have tried numerous things on this and its apparent that the only option is dlsw and I have pressed the issue enough to start on it with test segments.
my theory was when the host queried the gateway, its first reply was local-ack on rtr2 (could be rtr1 but for theory we will say rtr2) which was giving back RR and the other end was actually in a disconnect state and sending rnr's to the rtr1 (in this exapmple the host was talking thru rtr2 to the remote side and the remote side was trying the opposite router) which local ack would reply to the supervisor frames
what was causing the problems in my opinion is the host provider does not utilize local ack since they only have lanned token rings and the customer provides their own wan routers. So the explorer would be answered quicker by the other router and that would be the source route bridged path to the remote side, where the other sides local ack and rif cache was routing through the opposite router. Unfortunately the site where we collected the data on I can not test since I have transitioned it to dlsw to solve their issues and show them the benfits of dlsw

IBM Token Ring 16/4 PCI adapter2?

Similar Messages

Maybe you are looking for