DLSw question

Dear all,
Could anyone help me to clarify the following point on DLSw redundancy?
Is it true if DLSw redundancy (or recover) are transparent to user if the end stations lie on a token ring network ? On the other hand if the end stations lie on the ethernet LAN, the DLSw can re-established itself but it is not transparent to user. Can I make such a conclusion ?
thanks

Hi,
no, this statement is not true.
From an end systems perspective the recovery is always disruptive. No matter if you are on a tokenring or on a ethernet lan.
That means:
DLSw is about llc2 sessions at layer2. If your lan attached end system has a llc2 session with a cisco dlsw router and i.e. that router fails, the llc2 session with the end system will fail aswell.
After the end system has realized that the llc2 session is gone it cleans up its local connections and then tries to reestablish the llc2 connection. If another dlsw router is available, who can reach the requested remote host, than this connection will come up again. That means the end user sna session goes down and comes back up again.
The same is true if you are talking about dlsw+ ethernet redundancy.
There is more in the details/differences between ethernet and tokenring lan segments. I.e. on a tokenring you have a rif in each packet which can be used for loop control.
On ethernet you almost always have ethernet switches, where a cam table of a ethernet switch in any vlan for any mac address can only point to exactly one port on the switch.
If you have two dlsw routers connected that can reach the same remote host those two routers will both send frames with the same host mac address into the same switch on two different ports. This is where dlsw ethernet redundancy feature comes into play.
thanks...
Matthias

Similar Messages

  • =SNA/DLSw+ & Impact Question=

    Hi all,
    this is related to discussion:
    http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Network%20Infrastructure&topic=LAN%2C%20Switching%20and%20Routing&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dd82da4
    I opened this new one since my question was answered.
    Our Topology:
    Server---L2 switch---L3 Dist switch---Firewall---L3 switch(Core)--Firewall--CLOUD--IBM host
    The server would generate both IP and SNA traffic (port LU6.2). All media are ethernet. The L3 switches are DLSw+ capable. I don't know much about the firewalls and I don't have control in the cloud because its under a different administrator.
    Questions:
    1. if I would use DLSw+, I need to bridge the ethernet port of the L3 Dist switch connecting the Server side. But, the server's connection is part of a VLAN, so, in the config of L3 Dist Switch, I would need to bridge the VLAN to DLSw. Would this setup impact the original behaviour of my VLAN? The VLAN is a Switched VLAN interface routed to another VLANs also.
    2. Is it possible to control the port that would be used where the DLSW+ would pass through? I think I would have problems w/ our Firewall which requires source-destination ports and IPs to pass traffic.
    Any suggestions/opinions are very much welcome... thanks!!!
    rodney

    Hi,
    if you are using vlan interfaces already than your configuration would look similar to this:
    dlsw local-peer peer-id 10.10.10.1
    dlsw remote-peer tcp 0 20.20.20.1
    dlsw bridge-group 10
    interface loopback 0
    ip address 10.10.10.1 255.255.255.0
    interface vlan 234
    ip address ...
    bridge-group 10
    bridge 10 protocol vlan-bridge
    that would allow you to bridge sna traffic into dlsw.
    It assumes that 20.20.20.1 is the local peer configured on the partner router in front of the host.
    The local peer tied to the loopback interface is just an example.
    If you have i.e. more than one vlan you want to bridge than you can create multiple bridge-groups and you can configure multiple dlsw bridge-group statements. This way you bridge multiple vlans into dlsw but you dont bridge them together.
    If you know the sap's you are using for sna, default is 4 as far as i know. Most commonly known are 4,8,12 than you can create an access list like this:
    access-list 200 permit 0x0000 0x0d0d
    and apply it to the bridge-group command on the interface.
    interface vlan 234
    bridge-group 10
    bridge-group 10 input-sap-list 200
    that allows only sap's 0,4,8,12 with and without the response bit set into the bridge group and effectively blocks all other traffic.
    In respect to the tcp ports that dlsw is using over the WAN. Dlsw version 1, RFC1795, that is what cisco is using, opens always two tcp sessions at startup.
    This router starts the connection, it opens a tcp connection on the destination port 2065, source port is a random port above 11000.
    Now the receiving end is also opening a tcp session back to the first router. Destination port 2065, local, source port is a random port above 11000.
    Next the dlsw capabilities exchange happens and the two peers exchange their information. Once they detected that they both are cisco devices and that they both support the usage of only one tcp session in both directions the one with the "numerically higher ip address" will drop its connection on the local tcp port 2065.
    The remaining tcp connection is used for dlsw traffic in both directions.
    this is described in detail in RFC1795, section 7.6.7.
    thanks...
    Matthias

  • Design question about SNASw, DLSW and VDLC

    Hello,
    I have a question about Ethernet redundancy in an APPN environment.
    Let's have an example with 3 routers running SNASw that are on the SAME LAN (no vlans) as the Mainframe's OSA (one OSA only). APPN is configured on the Mainframe.
    Using DLSw+, all downstream PUs are connected to the 3 routers. Can I define in the VDLC interface of each router the SAME MAC address, and this MAC address be the destination MAC of the downstream PUs?

    Hi,
    yes, headend routers are the ones in front of the OSA/mainframe.
    If you replace a tokenring with ethernet in the data center/headend, than the snasw dlsw solution is almost perfect for you. If you use hpr/ip to connect upstream to the host you are all set.
    In that case you dont advertise any mac addresses on the local ethernet between the snasw/dlsw routers and the osa since it is hpr/ip. Basicaly ip routing only.
    From the clients perspective, they dont really know that there is a change since you replicate the old tokenring mac address as vdlc mac address/snasw port and the end systems still connect to them like they did before.
    In respect to dlsw ethernet redundancy we have to be a bit carefull not to mix the scenarios.
    Dlsw ethernet redundancy is designed for the branch. Not the data center.
    If you use dlsw ethernet redundancy with ethernet switches, and in almost all cases today ethernet means ethernet switches, you configure a mac address mapping between artificiall local mac addresses and your real remote mac address of the host.
    On each router you configure a unique local mac address. Than you point half of your end systems dmac to the local mac address configured on router1 and the other half to the local mac address configured on router2. That way you achive load balancing.
    The two routers exchange their mapping and in case router1 looses the connection to router2, router1 will activate the mapping it learned from router2 aswell and then take over those circuits additional.
    If you decide that you configure on router1 the local mac address equal to the remote mac address, because you have a large number of clients and can not simply change the damc's on all of them, than you need to configure a "dummy" mapping on router2 and router1 will get all the circuits in this example. router2 would be purely for redundancy in case router1 goes down.
    If you think about this than it is clear why dlsw ethernet redundancy is designed for the branch. In the branch we map local to remote mac addresses and the remote mac addresses are the hosts. Typically there are only a limited number of host mac addresses to map.
    If you turn this around and put dlsw ethernet redundancy on the host end than you have to map all clients. If you have only one or two clients this is certainly doable. But if you have a large nuber of clients this is simply not manageable.
    thanks...
    Matthias

  • SDLC - DLSW - EE(SNASW) question

    I have very little background knowledge of DLSW or SNASwitching, but here goes...
    I am currently trying to migrate an existing connection from SDLC -> DLSW ->token ring mainframe connection to SDLC -> DLSW -> SNASW EE.  My EE connection from the cisco router to hte mainframe is up and active, but I am unable to get the DLSW connection to work.  I have been able to get the Peers to CONNECT, but I do not have any DLSW circuits. 
    Remote Router
    dlsw local-peer peer-id 192.168.105.84
    dlsw remote-peer 0 tcp 10.248.3.36
    dlsw remote-peer 0 tcp 192.168.105.46
    dlsw remote-peer 0 tcp 192.168.105.47
    interface Ethernet0/0
    ip address 192.168.105.84 255.255.255.0
    interface Serial0/0
    no ip address
    shutdown
    interface BRI0/0
    no ip address
    shutdown
    interface Serial1/0
    description MPSM - MPS SDLC connection to MPS9 gateway
    bandwidth 19200
    no ip address
    encapsulation sdlc
    no keepalive
    sdlc role primary
    sdlc vmac 4534.0000.0900
    sdlc address C1
    sdlc xid C1 05310170
    sdlc partner 4800.0000.0000 C1
    sdlc dlsw C1
    interface Serial1/1
    description MPSM MT80MPS7 - IP80GG73
    bandwidth 19200
    no ip address
    encapsulation sdlc
    no keepalive
    sdlc role primary
    sdlc vmac 4534.0000.0700
    sdlc address C1
    sdlc xid C1 05310172
    sdlc partner 4800.0000.0000 C1
    sdlc dlsw C1
    interface Serial1/2
    description MPSM MT80MPS5 - IP80GG53
    bandwidth 19200
    no ip address
    encapsulation sdlc
    no keepalive
    sdlc role primary
    sdlc vmac 4534.0000.0500
    sdlc address C1
    sdlc xid C1 05310174
    sdlc partner 4800.0000.0000 C1
    sdlc dlsw C1
    RTGRAMIHQMPSM01#sho dlsw peer
    Peers:                state     pkts_rx   pkts_tx  type  drops ckts TCP   uptime
    TCP 10.248.3.36     CONNECT      58648     59193  conf      0    0   0     2w6d
    TCP 192.168.105.46  CONNECT    1085642   1212360  conf      0    2   0     2w6d
    TCP 192.168.105.47  CONNECT      58492     58492  conf      0    0   0     2w6d
    Total number of connected peers: 3
    Total number of connections:     3
    RTGRAMIHQMPSM01#sho dlsw circ
    Index           local addr(lsap)    remote addr(dsap)  state          uptime
    1929380244      4534.0000.05c1(04)  4800.0000.0000(04) CONNECTED          2w6d
    2969567635      4534.0000.07c1(04)  4800.0000.0000(04) CONNECTED          2w6d
    Total number of circuits connected: 2
    Data Center Router
    source-bridge ring-group 336
    dlsw local-peer peer-id 10.248.3.36
    dlsw remote-peer 0 tcp 192.168.105.84
    dlsw remote-peer 0 tcp 192.168.105.85
    interface Loopback0
    ip address 10.210.136.65 255.255.255.255
    interface GigabitEthernet0/1
    description VLAN526 to XWGRAMIDCFPIP01
    ip address 10.248.3.36 255.255.255.248
    duplex full
    speed 100
    media-type rj45
    negotiation auto
    interface FastEthernet0/2
    no ip address
    shutdown
    duplex auto
    speed auto
    interface GigabitEthernet0/2
    description VLAN529 to XWGRAMIDCFPIP02
    ip address 10.248.3.44 255.255.255.248
    duplex full
    speed 100
    media-type rj45
    negotiation auto
    interface GigabitEthernet0/3
    no ip address
    shutdown
    duplex auto
    speed auto
    media-type rj45
    negotiation auto
    snasw pdlog information
    snasw dlctrace buffer-size 10000
    snasw cpname NETMPS.GRSNAS01
    snasw dlus NETMPS.XD81
    snasw port SNSWPORT hpr-ip GigabitEthernet0/1
    snasw port DLSWPORT vdlc 336 mac 4800.0000.0000 conntype nohpr
    snasw link SW01XD81 port SNSWPORT ip-dest 204.90.2.14
    RTGRAMIDCSNAS01#sho dlsw peer
    Peers:                state     pkts_rx   pkts_tx  type  drops ckts TCP   uptime
    TCP 192.168.105.84  CONNECT      58652     58649  conf      0    0   0     2w6d
    TCP 192.168.105.85  CONNECT      58578     58578  conf      0    0   0     2w6d
    Total number of connected peers: 2
    Total number of connections:     2
    RTGRAMIDCSNAS01#sho dlsw circ
    RTGRAMIDCSNAS01#
    Like I said, I have little background knowledge about this connectivity.  If there is additional information that I could provide, please let me know.  Any help would be greatly appreciated.
    Thanks,
    Dave

    To answer one of your questions, as far as I know, SNASw performance might not be same as that of HPR/IP

  • DLSw circuit question

    Hello forum,
    there is a strange behaviour of a dlsw connection that I wish to discuss here.
    We had (long time ago) established a dlsw connection between two mainfrmes, one had an OSA T/R adapter and the other a 3745 in front. This circuit was up and running and soon we "forgot" about it. No problems were ever reported.
    Some months ago, we changed the T/R OSA to Ethernet OSA. Again, doing all necessary changes, the sessions were established ok. But we notice a strange behaviour. Every morning, the PU is in a strange state, either pending or conct and we have to vary inact/act the PU so that the sessions can be established. After about 1 to 2 minutes everyhing is ok.
    We do not have taken any traces or displays, but I wanted to ask, is it something to do with the dlsw circuit between the two MAC addresses (ETH OSA and 3745) dropping through the night?
    Is there any time limit that an established circuit is active?
    Can we change this time?
    During night, of course there is no activity between the two mainframes, so we guess a timer expires and the PU needs reactivation.
    HAPPY NEW YEAR!!!!

    I am trying to connect the following config:
    IBM Host A <-OSA-> Ethernet <--> router <-- Serial --> IP Cloud (FR / ??) <--> FEP (with FR support) <--> IBM Host B.
    IBM Host A runs CICS App, Terminals connected to the FEP on the IBM Host B side logon to CICS App on IBM Host A.
    The person before me designed the connection using FRAS. After a few weeks of trying, I found out it won't work.
    Based on the scanning throught this forum it seems that I can do this by using dlsw such as:
    IBM Host A <-OSA-> Ethernet <--> router (DLsw) <-- Serial --> IP Cloud (FR / ??) <--> router (DLsw) <--> FEP (with FR support) <--> IBM Host B.
    Since I am new to the network, I need a bit more help on the config on the IBM HOST A (VTAM XCA), both dlsw routers and the FEP on IBM Host B.
    Also at the moment the link is Frame-relay (direct). Can the IBM Host A with OSA card and the 2 dlsw routers able to utilise the same frame-relay link or we have to get another type of wan link?

  • Question on example "configuring qllc to eth with local switching"

    Hello,
    I am reffering to the example on page
    http://www.cisco.com/en/US/partner/tech/tk331/tk336/technologies_configuration_example09186a0080093fba.shtml
    Let's consider that the Mainframe is on the ethernet side (OSA card) and the station on the serial side. Then I guess the example will work fine.
    To make things more complecated, now suppose that there is another station on another serial let say s0/1, with its own x.121 address, whereas the station is on s0/0. Now, if the station also wants to speak x.25 with the server on s0/1, how this could be accomplished? Does the configuration of the s0/0 with the x25 map and qllc dlsw commands, forbids the station from talking to other serial interfaces? Or if I just add a x.25 route to the s0/1, then whenever station asks for the x.121 address of the server it will be guided there?
    Regards, Apostolos.

    I am sorry but I think the question as it was set was a bit confusing. So, please let me rephrase it using the same example as basis. Let's consider we have two AS400 (a & b) connected with x25 to two serials on a router. This router is connected with a x.25 serial interface with another router, at serial s0/0, which has two connections:
    i) Ethernet to mainframe (OSA)
    ii) Serial (s0/1) x25 to another server (Stratus)
    AS400A is to speak with OSA card whereas AS400B is to speak with the stratus server.
    If I configure the serial interface to map x25 address of AS400A to a vmac and guide this to OSA, then will the other AS400B be able to connect to the Stratus?

  • DLSw+ local switching, Ethernet to QLLC

    In the following url:
    http://www.cisco.com/en/US/partner/tech/tk331/tk336/technologies_configuration_example09186a0080093fba.shtml
    there is an example of using DLSw+ for connecting an ethernet device and a x.25 (QLLC) FEP. Is the opposite connection valid? For example, if the x.25 is at the branch level and ethernet at the Mainframe (OSA card), can DLSW+ still be used for connecting the device?
    I am asking this, because we have a case where various servers in various sites are connected with x.25 lines to the IBM 3745. The scope is to replace this IBM 3745 with a cisco router and OSA card.
    However, a change in all x.25 servers is out of the question (for the time being).

    yes, the scenario you describe is possible. In general everything you can do with dlsw local switching can also be done remote via dlsw.
    It is always a matter of working out the specific details how to configure qllc. If you need specific assistance with a configuration open a case with the tac and the issue will be worked on.
    thanks...
    Matthias

  • DLSW peer takes 20 min. to establish..Please Help !!!

    I have configured a Cisco 7304 with DLSW and the remote peer is not a Cisco router. When the local peer in the Cisco is not configured as promiscuous, it takes about 20min to 1h30min for the peers to get connected.
    If the local peer is configured as promiscous, it works good, but we dont want to use this configuration becasuse we want to control the connections on each router.
    What can I do in order to solve this problem ?
    Attached is the router configuration and the output of a "debug dlsw peers"

    Hi,
    based on the debug dlsw peer:
    00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:ADMIN-OPEN CONNECTION state:DISCONN
    00:02:00: DLSw: dtp_action_a() attempting to connect peer 172.25.252.254(2065)
    00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:DISCONN->WAIT_WR
    00:02:00: DLSw: Async Open Callback 172.25.252.254(2065) -> 11004
    00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:TCP-WR PIPE OPENED state:WAIT_WR
    00:02:00: DLSw: dtp_action_f() start read open timer for peer 172.25.252.254(2065)
    00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:WAIT_WR->WAIT_RD
    00:02:00: DLSw: passive open 172.25.252.254(2067) -> 2065
    00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:TCP-RD PIPE OPENED state:WAIT_RD
    00:02:00: DLSw: dtp_action_g() read pipe opened for peer 172.25.252.254(2065)
    00:02:00: DLSw: CapExId Msg sent to peer 172.25.252.254(2065)
    00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:WAIT_RD->WAIT_CAP
    00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP
    00:02:00: DLSw: dtp_action_j() cap msg rcvd from peer 172.25.252.254(2065)
    00:02:00: DLSw: Recv CapExId Msg from peer 172.25.252.254(2065)
    00:02:00: DLSw: Pos CapExResp sent to peer 172.25.252.254(2065)
    00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:WAIT_CAP->WAIT_CAP
    00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP
    00:02:00: DLSw: dtp_action_j() cap msg rcvd from peer 172.25.252.254(2065)
    00:02:0
    Torrejon0#0: DLSw: Recv CapExPosRsp Msg from peer 172.25.252.254(2065)
    00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:WAIT_CAP->WAIT_CAP
    00:02:00: DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP
    00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:SSP-CAP EXCHANGED state:WAIT_CAP
    00:02:00: DLSw: dtp_action_k() cap xchged for peer 172.25.252.254(2065)
    00:02:00: DLSw: closing read pipe tcp connection for peer 172.25.252.254(2065)
    00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:WAIT_CAP->PCONN_WT
    00:02:00: DLSw: Processing delayed event:TCP-PEER CONNECTED - prev state:PCONN_WT
    00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:TCP-PEER CONNECTED state:PCONN_WT
    00:02:00: DLSw: dtp_action_m() peer connected for peer 172.25.252.254(2065)
    00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:PCONN_WT->CONNECT
    at this point the dlsw peer is in state CONNECTED
    However you always get a tcp rst or fin right afterwards. Tcp tells dlsw to disconnect the peer.
    This can have two potential sources.
    The tcp stack on this router or the tcp stack on the remote router has closed the session.
    00:02:00: DLSw: dlsw_tcpd_fini() for peer 172.25.252.254(2065)
    00:02:00: DLSw: tcp fini closing connection for peer 172.25.252.254(2065)
    00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:ADMIN-CLOSE CONNECTION state:CONNECT
    00:02:00: DLSw: dtp_action_b() close connection for peer 172.25.252.254(2065)
    00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:CONNECT->DISCONN
    so the question really is where does the tcp rst come from? Who is closing the tcp connection?
    This sequence repeats itself over and over again until it finally stays up.
    You can do a
    debug ip tcp driver
    debug ip tcp transaction
    this will show you if you get a disconnect or if this router is sending one. However you have to be a bit carefull with the debugging if you have a lot of tcp activity going on in this router.
    Alternative is to take a sniffer trace on the WAN and find out who is sending the tcp reset/fin in that case.
    thanks...
    Matthias

  • Dlsw problem : stuck in WAIT_CAP

    Hi all
    we had a great problem with some snasw/dlsw routers.
    About all dlsw peers remained in WAIT_CAP state( except few resources where dlsw connection ok ) while no ip issues were present between central routers and dlsw remote routers....
    The appn snasw links seemed to be ok ( seeing the snasw link command )
    A question : there is a relationship between dlsw peer state and snasw link , ie there is an interaction between the 2 processes that could block dlsw peering establishement if there is a mistake on snasw=appn process??
    Thanks for feedbacks
    Stefano R.

    Stefano,
    the debugging is telling us that the tcp write and read pipe was opened. Ok so far. Next the router is sending his cap_ex message and then this router waits for the cap_ex from the peer. Which never arrives.
    So why is the cap exchange not arriving? It would be very much needed to see the debug from the other end at the same time to have a chance to understand what goes on.
    Feb 1 09:12:25.524: DLSw: START-TPFSM (peer 10.237.88.136(2065)): event:ADMIN-OPEN CONNECTION state:DISCONN
    Feb 1 09:12:25.524: DLSw: dtp_action_a() attempting to connect peer 10.237.88.136(2065)
    Feb 1 09:12:25.528: DLSw: END-TPFSM (peer 10.237.88.136(2065)): state:DISCONN->WAIT_WR
    Feb 1 09:12:26.037: DLSw: Async Open Callback 10.237.88.136(2065) -> 11241
    Feb 1 09:12:26.037: DLSw: START-TPFSM (peer 10.237.88.136(2065)): event:TCP-WR PIPE OPENED state:WAIT_WR
    Feb 1 09:12:26.037: DLSw: dtp_action_f() start read open timer for peer 10.237.88.136(2065)
    Feb 1 09:12:26.041: DLSw: END-TPFSM (peer 10.237.88.136(2065)): state:WAIT_WR->WAIT_RD
    Feb 1 09:12:26.726: DLSw: passive open 10.237.88.136(28757) -> 2065
    Feb 1 09:12:26.726: DLSw: START-TPFSM (peer 10.237.88.136(2065)): event:TCP-RD PIPE OPENED state:WAIT_RD
    Feb 1 09:12:26.726: DLSw: dtp_action_g() read pipe opened for peer 10.237.88.136(2065)
    Feb 1 09:12:26.726: DLSw: CapExId Msg sent to peer 10.237.88.136(2065)
    Feb 1 09:12:26.726: DLSw: END-TPFSM (peer 10.237.88.136(2065)): state:WAIT_RD->WAIT_CAP
    Here you see when the write pipe opens, when the read pipe goes up, the tcp connection from the other router came back to us and this router is sending his CapExId to the peer but we dont get a response and time out.
    thanks...
    Matthias

  • DLSW and the MAC that won't bridge....

    I'm trying to migrate from a CIP attached router (7204) to an OSA card on our mainframe for our SNA connectivity. I've run into a bit of an odd problem.
    It seems I can make a connection to the MAC on the OSA card from a subnet within my data center (I've tried several), but I can't make one work from a remote location via DLSW. The same connections work to the CIP attached router. To me, it looks like I have a problem with bridging, but I'm not 100% sure. I'm tring to connect to 00096b1ade31 on SAP 4.
    I have a DLSW tunnel up and running from my remote location directly to my core switch (6509). The MAC in question is attached directly to the same core switch. I have bridging enabled on the VLAN, but I don't see the MAC in the bridge table. I do however see the MAC in the MAC address table.
    WPG6509-A#SH DLSW REA
    DLSw Local MAC address reachability cache list
    Mac Addr status Loc. port rif
    0000.836c.4278 FOUND LOCAL TBridge-001 --no rif--
    0000.c1a2.e717 FOUND LOCAL TBridge-001 --no rif--
    0002.319c.6194 FOUND LOCAL TBridge-001 --no rif--
    0002.31b8.1483 FOUND LOCAL TBridge-001 --no rif--
    0002.31b8.1576 FOUND LOCAL TBridge-001 --no rif--
    0002.31b8.20e0 FOUND LOCAL TBridge-001 --no rif--
    0002.31c6.39c7 FOUND LOCAL TBridge-001 --no rif--
    0009.6b1a.de31 SEARCHING LOCAL
    0020.00a4.5a28 FOUND LOCAL TBridge-001 --no rif--
    0070.3006.5d03 FOUND LOCAL TBridge-001 --no rif--
    4000.2216.3002 FOUND LOCAL TBridge-001 --no rif--
    4080.0000.0000 FOUND LOCAL TBridge-001 --no rif--
    DLSw Remote MAC address reachability cache list
    Mac Addr status Loc. peer
    0002.31b8.1483 FOUND REMOTE 10.89.1.2(2065)
    0009.6b1a.de31 SEARCHING REMOTE
    4000.0255.1091 SEARCHING REMOTE
    WPG6509-A#sh mac-address-table | include de31
    * 300 0009.6b1a.de31 dynamic Yes 0 Gi2/1
    WPG6509-A#
    WPG6509-A#sh run int vlan 300
    Building configuration...
    Current configuration : 282 bytes
    interface Vlan300
    description Mainframe VLAN
    ip address 10.3.1.2 255.255.255.0
    no ip redirects
    ip directed-broadcast 176
    ip route-cache flow
    ip ospf network broadcast
    standby 3 ip 10.3.1.1
    standby 3 priority 125
    standby 3 preempt
    bridge-group 1
    hold-queue 1000 in
    end
    WPG6509-A#sh run int gig 2/12
    Building configuration...
    Current configuration : 92 bytes
    interface GigabitEthernet2/12
    switchport
    switchport access vlan 300
    no ip address
    end
    Other config tidbits:
    bridge 1 protocol vlan-bridge
    WPG6509-A#sh run | include dlsw
    dlsw local-peer peer-id 10.3.4.1
    dlsw remote-peer 0 tcp 10.123.1.1
    dlsw remote-peer 0 tcp 10.89.1.2
    dlsw remote-peer 0 tcp 10.149.2.1
    dlsw icanreach sap 0 4
    dlsw bridge-group 1
    Ideas welcome!

    Hi Tom,
    The OSA has to be set up in non-QDIO mode.
    Here is a link to an IBM redbook that should help, see Chapter 7.
    http://www.redbooks.ibm.com/abstracts/sg245948.html?Open
    I assume that you have an XCA and a Switched Major Node defined for this and both are active. When you see the MAC seraching, at the router local to the OSA, there is a test frame being sent out to the OSA. If the OSA answers test, then from the "show dlsw reach", it will change to "found".
    We did have a problem where voice discovery caused a problem for the OSA, but this would prevent the link from connecting, see Bug ID CSCea90470. Sounds like this is not the case here.
    I suggest sniffing the port where the OSA is connected to see if the test frame is going out to the OSA. If so and the OSA is not answering the test, then you may have to enlist IBM support at that point.
    Jim

  • How to host addresses with DLSw

    I'm not quite sure how to ask this question but...
    We have leveraged DLSw peers inside our data center. Leveraged meaning more than one client peers with them. How can I keep a client from advertizing unwanted host mac addresses to us and how can we keep from advertizing other clients mac addresses?
    I have been told that access list will not work with DLSW and am looking for somebody with first hand experiance/knowlage to share their experiance.
    ie when we do a show dlsw reachability I don't want to see every host a client has nor do I want client A to see client B's host.

    Hi,
    i assume you are talking about a secnario where you have a host end dlsw router, in the data center, and you have one or more branch routers which form dlsw peers with the host end router.
    On the host end you have some form of a host mac address reachable. this mac address is the address your clients are connecting too.
    There can be quite some different physical setups so that is why i try to keep this discussion a littlebit "high level".
    If you assume that your host end mac address, the one your clients connect too, is 4000.3745.0000, than you can simply configure on the hostend router:
    dlsw icanreach mac-address 4000.3745.0000
    dlsw icanreach mac-exclusive
    If you are in a pure sna environment and you i.e. have the sna saps 4 and 8 in use than you can also configure:
    dlsw icanreach sap 0 4 8
    All of these commands are advertised via runtime capabilities exchange to all connected dlsw remote peers.
    The first one:
    dlsw icanreach mac-address....
    Is creating a static dlsw reachability cache entry on the remote peers.
    That prevents them from exploring to all possible peers. They will only verify that the mac address in the static reach entry is really reachable via the peer the entry points to.
    dlsw icanreach mac-exclusive
    this one creates a filter, both on the branch and the host end router.
    On the branch router it prohibites dlsw canureach frames for any other mac address than the ones you have configured. In other words no sna explorer/test with a different dmac than the configured one is forwarded.
    On the host end router it prohibites the same with the source address. So it makes sure that no circuits can come up with any other mac address than the configured one. ( you can configure more than one address, either multiple statements or if it is a block of addresses you can use the address mask).
    dlsw icanreach sap 0 4 8
    this applies to all frames, basically on the branch routers it prohibits the forwarding of any other frame with dsap anything else than the configured one.
    Also:
    access-list do work with dlsw!
    one very simple and powerfull one is like this:
    access-list 200 permit 0x0000 0x0d0d
    i.e.
    interface ethernet x
    bridge-group 1
    bridge-group 1 input-lsap-list 200
    access-list 200 only allows saps 0, 4, 8, 12. Command and response.
    You can also apply the same list on a source-bridge statement on a tokenring interface.
    This one filters as close to the source as possible. Frames we dont want to transport dont even enter the router to be processed. However it requires a config step on every branch router. You can also apply address lists on the bridge-group or source-bridge statements.
    the dlsw icanreach filters work aswell but the router first processes the frame to figure out it needs to be dropped. But they are configured only on the host end, the central router.
    Let me know if you need more information.
    thanks...
    Matthias

  • CBWFQ: Question about the output of "show policy-map interface" command

    Hi everyone,
    I have a question about the output of "show policy-map interface" command.
    The following is the output of this command and lower side of the output shows
    (total queued/total drops/no-buffer drops) 0/342/0
    If the packets drop occur due to the situation of no enough buffer,
    "no-buffer drops" counted up. But "no-buffer drops" has not been counted up.
    The "no-buffer drops" is 0 (zero) but "total drops" are counted as 342.
    I guess there are other factors except "no-buffer drops" to add "total drops".
    But I can not find any information about "other factors".
    So I would like to know the "other factors" added to "total drops".
    reserch-3725#sh policy-map interface fastethernet0/1
    FastEthernet0/1
    Service-policy output: shaping
    Class-map: kdpc (match-all)
    146956873 packets, 115209221595 bytes
    5 minute offered rate 156000 bps, drop rate 0 bps
    Match: access-group name YOKOHAMA_to_CHINO
    Traffic Shaping
    Target/Average Byte Sustain Excess Interval Increment
    Rate Limit bits/int bits/int (ms) (bytes)
    9360000/9360000 58500 234000 234000 25 29250
    Adapt Queue Packets Bytes Packets Bytes Shaping
    Active Depth Delayed Delayed Active
    - 0 146956724 3539850811 2960247 3851843541 no
    Class-map: class-default (match-any)
    552458414 packets, 249687580329 bytes
    5 minute offered rate 242000 bps, drop rate 0 bps
    Match: any
    Traffic Shaping
    Target/Average Byte Sustain Excess Interval Increment
    Rate Limit bits/int bits/int (ms) (bytes)
    3072000/3072000 19200 76800 76800 25 9600
    Adapt Queue Packets Bytes Packets Bytes Shaping
    Active Depth Delayed Delayed Active
    - 0 552453209 573909865 30358216 2926188156 no
    Service-policy : policy1
    Class-map: dlsw (match-all)
    979578 packets, 264843255 bytes
    5 minute offered rate 0 bps, drop rate 0 bps
    Match: access-group name acl-dlsw
    Queueing
    Output Queue: Conversation 137
    Bandwidth 128 (kbps) Max Threshold 64 (packets)
    (pkts matched/bytes matched) 20922/17371500
    (depth/total drops/no-buffer drops) 0/0/0
    Class-map: telnet (match-all)
    29938 packets, 1806058 bytes
    5 minute offered rate 0 bps, drop rate 0 bps
    Match: access-group name acl-telnet
    Queueing
    Output Queue: Conversation 138
    Bandwidth 64 (kbps) Max Threshold 64 (packets)
    (pkts matched/bytes matched) 639/38900
    (depth/total drops/no-buffer drops) 0/0/0
    Class-map: class-default (match-any)
    551448911 packets, 249420939729 bytes
    5 minute offered rate 242000 bps, drop rate 0 bps
    Match: any
    Queueing
    Flow Based Fair Queueing
    Maximum Number of Hashed Queues 128
    (total queued/total drops/no-buffer drops) 0/342/0
    Your information would be appreciated.

    Details infomatiuon regarding show policy-map interface
    http://www.cisco.com/en/US/tech/tk543/tk545/technologies_tech_note09186a008010dd6a.shtml
    http://www.cisco.com/en/US/tech/tk543/tk760/technologies_tech_note09186a0080108e2d.shtml
    http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/qos_r/qos_s2g.htm#wp1146884

  • DLSW - Transparent Bridging via FE Subinterfaces?

    Hi. I have a 7206 router connected with FE to a Catalyst 6509, via 802.1Q trunking. Two VLANs. The router supports DLSW to remote sites, and the switch transports SNA traffic to the router with transparent bridging through one of the FE subinterfaces.
    What I'd like to do is establish DLSW peering between the router and another device on the local LAN -- in other words, also through the FE interface connected to the 6509. I don't have another physical FE interface on the router. Two questions:
    1) Is there any reason I would run into difficulty setting up another VLAN on the switch and another FE subinterface in the router, and using the new VLAN/subinterface for DLSW, while keeping the other subinterface configured to use transparent bridging?
    2) In that configuration, might there be any issue transporting SNA into and out of the router via the one FE subinterface configured with a bridge group and the other FE subinterface being used for the DLSW path? That is, I will need the router to decapsulate the SNA coming in via DSLW on one subinterface, and bridge it out the other subinterface, and vice-versa.
    Thanks for any guidance.

    I'm not sure how well I managed to explain the scenario in the previous post. An attempt to clarify:
    VLAN1 -\ FE.Subinterface1
    [6509] VLAN2 --> <=-802.1Q-=> FE.Subinterface2 [7206]
    VLAN3 -/ FE.Subinterface3
    6509
    VLAN 1: bridge group 1
    VLAN 2: bridge group 1
    VLAN 3: L2-only VLAN (no definition in the MSFC). Used only to transport DLSW (and other IP) traffic to and from a router also running DLSW to FE.Subinterface3 on the 7206 through the 802.1Q trunk.
    7206
    FE.Subinterface1: bridge-group 1
    FE.Subinterface2: bridge-group 1 (blocked by STP)
    FE.Subinterface3: not in a bridge group. The interface through which the 7206 communicates with an internal router running DLSW (transporting SNA for a device directly connected to that internal router).
    Traffic path
    SNA must travel between the device the 7206 is DLSW peering with through FE.Subinterface3, and a device (a mainframe OSA Express interface) the 7206's SNA traffic can reach via transparent bridging through FE.Subinterface1.
    The "steps": the 7206 uses FE.Subinterface3 to receive DLSW TCP/IP-encapsulated SNA traffic from the other DLSW router. The SNA traffic gets decapsulated in the 7206, and is bridged to the mainframe OSA Express interface via FE.Subinterface1. And of course the reverse, from the mainframe, transparently bridged into the 7206 through FE.Subinterface1 and sent via DLSW through FE.Subinterface3.
    Do-able? Thanks!

  • Questions on Print Quote report

    Hi,
    I'm fairly new to Oracle Quoting and trying to get familiar with it. I have a few questions and would appreciate if anyone answers them
    1) We have a requirement to customize the Print Quote report. I searched these forums and found that this report can be defined either as a XML Publisher report or an Oracle Reports report depending on a profile option. Can you please let me know what the name of the profile option is?
    2) When I select the 'Print Quote' option from the Actions drop down in the quoting page and click Submit I get the report printed and see the following URL in my browser.
    http://<host>:<port>/dev60cgi/rwcgi60?PROJ03_APPS+report=/proj3/app/appltop/aso/11.5.0/reports/US/ASOPQTEL.rdf+DESTYPE=CACHE+P_TCK_ID=23731428+P_EXECUTABLE=N+P_SHOW_CHARGES=N+P_SHOW_CATG_TOT=N+P_SHOW_PRICE_ADJ=Y+P_SESSION_ID=c-RAuP8LOvdnv30grRzKqUQs:S+P_SHOW_HDR_ATTACH=N+P_SHOW_LINE_ATTACH=N+P_SHOW_HDR_SALESUPP=N+P_SHOW_LN_SALESUPP=N+TOLERANCE=0+DESFORMAT=RTF+DESNAME=Quote.rtf
    Does it mean that the profile in our case is set to call the rdf since it has reference to ASOPQTEL.rdf in the above url?
    3) When you click on submit button do we have something like this in the jsp code: On click call ASOPQTEL.rdf. Is the report called using a concurrent program? I want to know how the report is getting invoked?
    4) If we want to customize the jsp pages can you please let me know the steps involved in making the customizations and testing them.
    Thanks and Appreciate your patience
    -PC

    1) We have a requirement to customize the Print Quote report. I searched these forums and found that this report can be defined either as a XML Publisher report or an Oracle Reports report depending on a profile option. Can you please let me know what the name of the profile option is?
    I think I posted it in one of the threads2) When I select the 'Print Quote' option from the Actions drop down in the quoting page and click Submit I get the report printed and see the following URL in my browser.
    http://<host>:<port>/dev60cgi/rwcgi60?PROJ03_APPS+report=/proj3/app/appltop/aso/11.5.0/reports/US/ASOPQTEL.rdf+DESTYPE=CACHE+P_TCK_ID=23731428+P_EXECUTABLE=N+P_SHOW_CHARGES=N+P_SHOW_CATG_TOT=N+P_SHOW_PRICE_ADJ=Y+P_SESSION_ID=c-RAuP8LOvdnv30grRzKqUQs:S+P_SHOW_HDR_ATTACH=N+P_SHOW_LINE_ATTACH=N+P_SHOW_HDR_SALESUPP=N+P_SHOW_LN_SALESUPP=N+TOLERANCE=0+DESFORMAT=RTF+DESNAME=Quote.rtf
    Does it mean that the profile in our case is set to call the rdf since it has reference to ASOPQTEL.rdf in the above url?
    Yes, your understanding is correct.3) When you click on submit button do we have something like this in the jsp code: On click call ASOPQTEL.rdf. Is the report called using a concurrent program? I want to know how the report is getting invoked?
    No, there is no conc program getting called, you can directly call a report in a browser window, Oracle reports server will execute the report and send the HTTP response to the browser.4) If we want to customize the jsp pages can you please let me know the steps involved in making the customizations and testing them.
    This is detailed in many threads.Thanks
    Tapash

  • Satellite P300D-10v - Question about warranty

    HI EVERYBODY
    I have these overheating problems with my laptop Satellite P300D-10v.
    I did everything I could do to fix it without any success..
    I get the latest update of the bios from Toshiba. I cleaned my lap with compressed air first and then disassembled it all and cleaned it better.(it was really clean insight though...)
    BUT unfortunately the problem still exists...
    So i made a research on the internet and I found out that most of Toshiba owners have the same exactly problem with their laptop.
    Well i guess this is a Toshiba bug for many years now.
    Its a really nice lap, cool sound (the best in laptop ever) BUT......
    So I wanted to make a question. As i am still under warranty, can i return this laptop and get my money back or change it with a different one????
    If any body knows PLS let me know.
    chears
    Thanks in advance

    Hi
    I have already found you other threads.
    Regarding the warranty question;
    If there is something wrong with the hardware then the ASP in your country should be able to help you.
    The warranty should cover every reparation or replacement.
    But I read that you have disasembled the laptop at your own hand... hmmm if you have disasembled the notebook then your warrany is not valid anymore :(
    I think this should be clear for you that you can lose the warrany if you disasemble the laptop!
    By the way: you have to speak with the notebook dealer where you have purchased this notebook if you want to return the notebook
    The Toshiba ASP can repair and fix the notebook but you will not get money from ASP.
    Greets

Maybe you are looking for

  • {SOLVED} no write permission to store downloads in /home/sources

    Morning folks ,   trying this ; moto4lin-svn dependencies: - qt3 (already installed) - libusb (already installed) - zlib (already installed) - gcc (already installed) - subversion (already installed) ==> Determining latest svn revision... -> Version

  • Transferring Purchases from old computer

    We used to have a Dell with iTunes that we made App store purchases for our family's iPod's. We now have an iMac, but none of the previously purchased apps are showing up. Is there a way to transfer from our iPods to our iMac without re-purchasing ev

  • Pass Data Into Second View Controller

    *My Setup:* I have a tab-bar program; I'm currently focusing on one tab, which has a nav controller The root controller works as expected. In one of the table view selection methods (didSelectAccessoryButtonAtIndex, or something similar), I initializ

  • How to install windows 7 and parallel 7 on my mac

    Hi folks, I Need help on how to install parallel 7 and Win 7 on my iMac running on 10.8 Can anyone one out there help me with the steps?

  • Unable to fetch site Error # 407

    Hi, When im trying to click Browse/Capture button in URL iView editor,..im facing this error. I have set the Proxy settings in the httpservice application and restarted the service. Any help is appreciated. Regards, Ricky