Frame Relay vs MPLS

Why does the Cisco CCNA certification cover Frame Relay if MPLS is the more used WAN technology?

CCNA is more like a foundation building certification. So it tends to cover a whole array of topics, but all at the basic level, just enough to give food for thought, and a fair level of understanding how each technology works. To cover MPLS would not have been appropriate in CCNA as MPLS needs the foundation as well as the routing level professional knowledge already in place..
But again with one level below CCNA certification, this may change probably, and they may cover light basics of MPLS. So that you can actually study the operations in professional and expert level certifications. Just a thought.
HTH-Cheers,
Swaroop

Similar Messages

  • Circuit 1/e1, what is this ? is it frame-relay or mpls or other ? help me?

    I read in one of Job descritpion  "Experience of working on circuit(T1/E1,T3/E3,Ethernet) troubleshooting would be preferred".
    Could u please help me this circuit  t1/e1,etc. Is it covered in ccnap or ccnp rs ?
    Is it frame-relay or mpls or  other ?
    Could you please explain or suggest me the book/blog/doc/etc.

    Please refer this:
    http://www.ad-net.com.tw/index.php?id=500

  • Frame Relay and MPLS

    Hi,
    I want to ask about the frame relay and MPLS.
    Frame Relay Scenerio
    The frames reached at the frame relay network and forwarded on the basis of DLCI. All the VCs are defined prior to the traffic on the network on the basis of DLCI (This is just like the MPLS network as packets are forwarded on the basis of Labels).
    Now my Question is How can MPLS is used in frame relay network or what are its affects in the presence of DLCI (As DLCIs are also performing the same task and also works on layer 2) or these two are different equivalent technologies ?

    Hi Muhammad,
    The answer is : MPLS is working on FR like it's working on ethernet. Because the FR and Ethernet are running on Layer2. It's told that MPLS is working at layer 2.5 , meaning that is between Layer 3 , and Layer 2. So in order to work it needs a layer2 forwarding in your case FR's DLCI. On top of the Layer 2 it is the MPLS header.
    Dan

  • Frame-Relay through MPLS cloud

    Hi All ,
    Can anybody explain if I make a MPLS pe act as a frame-relay sw too is there in LDP related issue or not ?

    It is possible to use Frame Relay switches as Label, Switching Routers. Such Frame Relay switches run network layer routing algorithms (such as OSPF, IS-IS, etc.), and their forwarding
    is based on the results of these routing algorithms. No specific
    Frame Relay routing is needed.
    When a Frame Relay switch is used for label switching, the top
    (current) label, on which forwarding decisions are based, is carried
    in the DLCI field of the Frame Relay data link layer header of a
    frame. Additional information carried along with the top (current)
    label, but not processed by Frame Relay switching, along with other
    labels, if the packet is multiply labeled, are carried in the generic
    MPLS encapsulation defined in [STACK].
    Check this out.
    http://www.ietf.org/rfc/rfc3034.txt

  • AToM Frame Relay over MPLS

    Is it possible to have multipoint topologies with FRoMPLS? In other words, if I'm receiving some Frame Relay PVCs on one physical interface on a PE, can I transport some of them to one remote PE and others to another remote PE? Or do I need to have separate physical interfaces to talk to different remote PEs?
    Thanks
    Tarek

    On the PE router, you can indeed take each one of the DLCIs from a same physical interface and connect them to a different egress PE.
    Hope this helps,

  • MPLS Verses Frame Relay

    I am looking for any comparison document between Frame Relay and MPLS
    Can anyone help me to find such a document ?
    Thanks
    Kind Regards
    Mohamed Abdallah

    If you are looking for a security comparison there is a draft document from Michael Behringer at : http://www.ietf.org/internet-drafts/draft-behringer-mpls-security-00.txt
    Hope this helps.
    -Ives-

  • Difrence between ... MPLS over Frame-Relay ATM

    Hai all,
    Sorry to ask very basic quiestion ..can some one tell what is the difrnce and advantage of MPLS over ATM and Frame-Relay ......pls provide me a better link ..for refrnce
    Thanks in advance
    Lijesh

    MPLS over ATM or MPLS over Frame-Relay it's not good idea, because if you use cell-mode labeling, you find someone limitation at this technology. DLCI and VPI/VCI value at this protocols it's not have large space. If you know how operate cell-mode, try to look at just for sample bits length with DLCI value at Frame-Relay protocol or VPI/VCI value at ATM protocol… Of course you can use same cheat like VCI-merge, but I think it's not very good idea.
    Building new network infrastructure at this protocols it's not good idea… It's good idea to fast implement MPLS technology in old network infrastructure build with this protocols (just for sample, you can linked ATM forwarding plane and MPLS forwarding plane (in this situation you can abandon to use fixed configuration VPI/VCI for IP network and can use benefits offered ATM technology with MPLS)), but not for new network infrastructure. If you need to offer services with this protocols, you can use Any Transport Over MPLS technology.
    For more information look at this page - http://www.cisco.com/en/US/tech/tk436/tk798/tsd_technology_support_protocol_home.html

  • Frame Relay access into MPLS with QOS

    My provider is telling me that I can take my frame relay network and map it into their MPLS network. Basically all my sites would connect into the providers Frame network and then mapped into the proivders MPLS network. Now I know this will work; but my concern is VoIP and QOS. If I have a single PVC and I am marking VoIP packets with an IPPREC of 5 how will the providers frame realy network see that? And how will it be honered from CE => Provider FR => PE => P => PE => Provider FR => CE

    Todd, I doubt how would your SP provide you guranteed QOS SLA's with that setup. As there is no one to one mapping of PREC/EXP values to FR based QOS.
    But although, if he gurantees or ensures that the FR access cloud is never going to be congested and everything is fifo in there then he can provide your per hop QOS behaviour based on your PREC value across the MPLS cloud.
    HTH-Cheers,
    Swaroop

  • MPLS - Frame Relay

    Hi
    I am trying to understand the build we have on our CE routers from the Service Provider. Frame-relay encapsulation is build on the Wan interface with LMI configured/dlci enabled on sub-interface. At the PE end, there is also Frame-relay configuration on the PE end...How does that work? Does Cisco have any docs that I could read?

    Hello Mary,
    on the PE router there is a Frame-relay interface and sub-interfaces.
    the PE-CE link is the VRF access link what is different on the PE side is the presence of the command ip vrf forwarding VRF-name in the correct FR subif.
    Then the MPLS cloud includes the backbone links of the PE routers.
    see the following link for an introduction to MPLS VPN
    http://www.cisco.com/en/US/docs/net_mgmt/vpn_solutions_center/1.2/provisioning/user/guide/VPN_UG1.html
    Hope to help
    Giuseppe

  • Do you think isdn and frame-relay expire?

    in new ccnp book i didnt see any thing about isdn and some object
    even in ccna exam i didnt see any question about isdn and if i remember about frame-relay
    what's your opinion?do you think isdn and frame-relay expire?is there any place for this technology on it nowadays?
    thanks

    Hi Reza,
    if you are talking about new CCNP curriculum, then ISDN and Frame relay technologies are no longer included there. ISDN and Frame relay were included in the Remote access paper of CCNP old curriculum but now that paper is replaced by Secure Converged Wide Area Networks paper which includes MPLS, IPSec VPNs and other technologies.
    But as Rick said in earlier post that ISDN and frame relay are still very much in use.
    hope it helps ... rate if it does ....

  • Can't ping routers across point-to-point frame-relay

    'evening,
      Really basic setup.  Designed with Packet Tracer, trying to ping routers across a point-to-point frame-relay.  I've designed this according to three different training sources who all say the same thing.  Yet, all pings failed.
    The shows:
    R1
    R1#copy run st
    Destination filename [startup-config]? 
    Building configuration...
    [OK]
    R1#show run
    Building configuration...
    Current configuration : 883 bytes
    version 12.2
    no service timestamps log datetime msec
    no service timestamps debug datetime msec
    no service password-encryption
    hostname R1
    no ip domain-lookup
    interface FastEthernet0/0
     no ip address
     duplex auto
     speed auto
     shutdown
    interface FastEthernet0/1
     no ip address
     duplex auto
     speed auto
     shutdown
    interface Serial1/0
     no ip address
     encapsulation frame-relay
    interface Serial1/0.12 point-to-point
     ip address 192.168.12.1 255.255.255.0
     frame-relay interface-dlci 102
    interface Serial1/0.13 point-to-point
     ip address 192.168.13.1 255.255.255.0
     frame-relay interface-dlci 103
    ip classless
    end
    R1#show frame-relay lmi
    LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 638       Num Status msgs Rcvd 638
     Num Update Status Rcvd 0       Num Status Timeouts 16
    LMI Statistics for interface Serial1/0.12 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 0         Num Status msgs Rcvd 0
     Num Update Status Rcvd 0       Num Status Timeouts 16
    LMI Statistics for interface Serial1/0.13 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 0         Num Status msgs Rcvd 0
     Num Update Status Rcvd 0       Num Status Timeouts 16
    R1#show frame-relay map
    Serial1/0.12 (up): point-to-point dlci, dlci 102, broadcast, status defined, active
    Serial1/0.13 (up): point-to-point dlci, dlci 103, broadcast, status defined, active
    R1#show frame-relay pvc
    PVC Statistics for interface Serial1/0 (Frame Relay DCE)
    DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.12
    input pkts 14055       output pkts 32795        in bytes 1096228
    out bytes 6216155      dropped pkts 0           in FECN pkts 0
    in BECN pkts 0         out FECN pkts 0          out BECN pkts 0
    in DE pkts 0           out DE pkts 0
    out bcast pkts 32795   out bcast bytes 6216155
    DLCI = 103, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.13
    input pkts 14055       output pkts 32795        in bytes 1096228
    out bytes 6216155      dropped pkts 0           in FECN pkts 0
    in BECN pkts 0         out FECN pkts 0          out BECN pkts 0
    in DE pkts 0           out DE pkts 0
    out bcast pkts 32795   out bcast bytes 6216155
    R2
    R2#SHOW RUN
    Building configuration...
    Current configuration : 772 bytes
    version 12.2
    no service timestamps log datetime msec
    no service timestamps debug datetime msec
    no service password-encryption
    hostname R2
    no ip domain-lookup
    interface Serial1/0
     no ip address
     encapsulation frame-relay
    interface Serial1/0.12 point-to-point
     ip address 192.168.12.2 255.255.255.0
     frame-relay interface-dlci 201
    ip classless
    end
    R2#show fr map
    Serial1/0.12 (up): point-to-point dlci, dlci 201, broadcast, status defined, active
    R2#show fr pvc
    PVC Statistics for interface Serial1/0 (Frame Relay DTE)
    DLCI = 201, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.12
    input pkts 14055       output pkts 32795        in bytes 1096228
    out bytes 6216155      dropped pkts 0           in FECN pkts 0
    in BECN pkts 0         out FECN pkts 0          out BECN pkts 0
    in DE pkts 0           out DE pkts 0
    out bcast pkts 32795   out bcast bytes 6216155
    R2#show fr lmi
    LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 679       Num Status msgs Rcvd 678
     Num Update Status Rcvd 0       Num Status Timeouts 16
    LMI Statistics for interface Serial1/0.12 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 0         Num Status msgs Rcvd 0
     Num Update Status Rcvd 0       Num Status Timeouts 16
    R3
    R3#show run
    Building configuration...
    Current configuration : 772 bytes
    version 12.2
    no service timestamps log datetime msec
    no service timestamps debug datetime msec
    no service password-encryption
    hostname R3
    interface Serial1/0
     no ip address
     encapsulation frame-relay
    interface Serial1/0.13 point-to-point
     ip address 192.168.13.2 255.255.255.0
     frame-relay interface-dlci 301
    ip classless
    end
    R3#show fr map
    Serial1/0.13 (up): point-to-point dlci, dlci 301, broadcast, status defined, active
    R3#show fr lmi
    LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 703       Num Status msgs Rcvd 702
     Num Update Status Rcvd 0       Num Status Timeouts 16
    LMI Statistics for interface Serial1/0.13 (Frame Relay DTE) LMI TYPE = CISCO
     Invalid Unnumbered info 0      Invalid Prot Disc 0
     Invalid dummy Call Ref 0       Invalid Msg Type 0
     Invalid Status Message 0       Invalid Lock Shift 0
     Invalid Information ID 0       Invalid Report IE Len 0
     Invalid Report Request 0       Invalid Keep IE Len 0
     Num Status Enq. Sent 0         Num Status msgs Rcvd 0
     Num Update Status Rcvd 0       Num Status Timeouts 16
    R3#show fr pvc
    PVC Statistics for interface Serial1/0 (Frame Relay DTE)
    DLCI = 301, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.13
    input pkts 14055       output pkts 32795        in bytes 1096228
    out bytes 6216155      dropped pkts 0           in FECN pkts 0
    in BECN pkts 0         out FECN pkts 0          out BECN pkts 0
    in DE pkts 0           out DE pkts 0
    out bcast pkts 32795   out bcast bytes 6216155
      Any input would really be appreciated.
    Thanks

    Turns out the mistake was not adding a mask to the subnet. Ex:
    Router_2(config_router)# network 192.168.0.0 0.0.255.255
    Router_2(config_router)# network 172.27.0.0 0.0.255.255
    Doing that on both routers made the hosts capable of pinging each other.
    Thanks for the tips everyone 

  • Connection from remote sites (Frame Relay WAN) to AS/400 dissapears

    Hello,
    We have the following problem appearing in our environment:
    All connections from remote sites dissapears unexpected from AS/400. After 2-3 minutes remote users get normal connectivity again.
    The environment is the the following:
    Frame Relay/ATM WAN (Frame Relay on remote sites and ATM in datacenter) comes to Cisco 7204VXR router which connected to LAN switch with 10/100/1000 ports. AS/400 with Fast Ethernet interface also connected to the similar LAN switch. CEF is enabled on the router, IOS version 12.4.3a. We have ETHSTD *ALL parameter set on AS/400. Remote users uses TCP/IP and Telnet but there are a number of 5494 controllers wich uses SNA.
    We got the problem for the first time after we enabled CEF on the router.
    I suspect that the cause of problem is Ethernet frames of different standards due to ETHSTD *ALL, but can neither reproduce the problem nor understand why it behaves so.
    Have anybody had similar problem?
    I would be very thanksfull if somebody can help me to solve it.
    Thank you in advance.
    //Mikhail Galiulin

    Hi Martin,
    Cisco 7200 itself can access AS/400 as well as all other hosts in the same with AS/400 LAN. There is no any outage in communications which goes to another LAN segment via Netscreen firewall while the communication via Cisco is down. Only those hosts which connected via Cisco are experiencing the problem. I can not say where the traceroute from AS/400 stucks (there are other people who maintain the machine and they never could catch the exact moment of outage).
    To turn off CEF I treat as the last option actually and unfortunatelly there is no guarantee that software upgrade will help (we have 12.4.3a now).
    So first of all I'm trying to understan WHY it happens because I can not see any systematics in the problem appearance. It can happen 3 times under 2 days and then dissapear for 1-2 months...
    //Mikhail Galiulin

  • Configuring Frame-Relay and the Frame-Relay Switch To Participate in WAN Routing

    Hey,
    My WAN in my voice lab is currently functional between all of my routers HQ, BR1, and BR1 with full-mesh connectivity.  I am using my PSTN router for the frame-relay switching as is shown in the attached configs.  I have used the connect commands for the PVC routing logic.  
    connect HQ-BR1 Serial0/3/0 101 Serial0/2/0 201 
    connect HQ-BR2 Serial0/3/0 102 Serial0/2/1 301 
    connect BR1-BR2 Serial0/2/0 202 Serial0/2/1 302 
    My question concerns the possibility of getting the PSTN router to participate in the WAN and the OSPF routing process?  The connect command tells how the PVCs are to be connected and pass through the PSTN router.  Is there anyway to do it so that a PVC connects to the PSTN router itself?
    I would specifically like to create a connection between the HQ and PSTN router over the WAN.  If anyone has any insight on this I would really appreciate it.
    Thank you.

    Hello Adam,
    you don't need to do FR switching.
    You just need to configure a back to back PVC associated to a p2p subinterface under PSTN router interface se0/3/0 and HQ:se0/1/0. the new PVC can be 103 on both sides
    PSTN
    interface ser0/3/0.103 point-to-point
    ip address 10.1.13.1 255.255.255.0
    frame-relay interface-dlci 103
    HQ
    interface ser0/1/0.103 point-to-point
    ip address 10.1.13.1 255.255.255.0
    frame-relay interface-dlci 103
    note: I was able to do this using the older syntax frame-relay route under interface configuration on frame relay switch. I would expect to work for you too with newer syntax connect.
    Hope to help
    Giuseppe

  • 2621 as a Frame Relay switch & terminal server?

    Is it unwise to use a 2621 as a combined Frame Relay switch & terminal server in a home lab? Both functions seem to move a general-purpose router into the dedicated use category.
    Likewise, is it true than configuring a router to serve as a Frame Relay switch isn't memory intensive?
    If I am wrong in my assumptions, please feel free to correct my misperceptions.
    Thanks.

    Using the 2621 for frame and TS should be fine. I do it in my lab and have never had a problem.

  • Troubleshooting Frame relay

    Dear Sir/Madam,
    I have Frame relay CIR 256 kps with configure as follow:
    factory#show run
    Building configuration...
    Current configuration : 2126 bytes
    version 12.2
    service timestamps debug uptime
    service timestamps log uptime
    no service password-encryption
    hostname factory
    enable secret xxx
    enable password xxx
    ip subnet-zero
    interface FastEthernet0/0
    ip address 192.168.0.1 255.255.254.0
    ip access-group 100 in
    duplex auto
    speed auto
    interface Serial0/0
    bandwidth 256
    no ip address
    encapsulation frame-relay
    no fair-queue
    traffic-shape rate 192000 24000 24000 1000
    frame-relay lmi-type ansi
    frame-relay ip rtp header-compression
    ip rtp reserve 16384 100 192
    interface Serial0/0.1 point-to-point
    description connected to Office
    ip address 192.168.50.2 255.255.255.0
    no cdp enable
    frame-relay interface-dlci 16
    interface Serial0/1
    no ip address
    shutdown
    interface Serial0/2
    no ip address
    shutdown
    ip classless
    ip route 0.0.0.0 0.0.0.0 192.168.50.1
    ip http server
    ip pim bidir-enable
    access-list 100 permit tcp any any eq www
    access-list 100 permit tcp any any eq smtp
    access-list 100 permit tcp any any eq ftp
    access-list 100 permit tcp any any eq pop3
    access-list 100 permit tcp any any eq ident
    access-list 100 permit tcp any any eq 443
    access-list 100 permit tcp any any eq 3389
    access-list 100 permit tcp any any eq ftp-data
    access-list 100 permit tcp any any eq 143
    access-list 100 permit tcp any any eq telnet
    access-list 100 permit tcp any any eq 161
    access-list 100 permit tcp any any eq domain
    access-list 100 permit udp any any eq domain
    access-list 100 permit tcp any any eq 139
    access-list 100 permit udp any any eq netbios-ns
    access-list 100 permit tcp any any eq 135
    access-list 100 permit udp any any eq snmp
    access-list 100 permit tcp any any eq 8080
    access-list 100 permit ip host 192.168.0.22 any
    access-list 100 permit ip host 192.168.0.23 any
    access-list 100 deny ip any any
    access-list 100 deny eigrp any any
    snmp-server community public RO
    line con 0
    line aux 0
    line vty 0 4
    password xxx
    login
    end
    factory#show int s0/0
    Serial0/0 is up, line protocol is up
    Hardware is PowerQUICC Serial
    MTU 1500 bytes, BW 256 Kbit, DLY 20000 usec,
    reliability 255/255, txload 61/255, rxload 56/255
    Encapsulation FRAME-RELAY, loopback not set
    Keepalive set (10 sec)
    LMI enq sent 8861, LMI stat recvd 8861, LMI upd recvd 0, DTE LMI up
    LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
    LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE
    Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0
    Last input 00:00:00, output 00:00:00, output hang never
    Last clearing of "show interface" counters 1d00h
    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 57000 bits/sec, 13 packets/sec
    5 minute output rate 62000 bits/sec, 14 packets/sec
    663283 packets input, 419498487 bytes, 0 no buffer
    Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
    16 input errors, 9 CRC, 7 frame, 0 overrun, 0 ignored, 0 abort
    820043 packets output, 138740120 bytes, 0 underruns
    0 output errors, 0 collisions, 1 interface resets
    0 output buffer failures, 0 output buffers swapped out
    0 carrier transitions
    DCD=up DSR=up DTR=up RTS=up CTS=up
    factory#
    When show int s0/0 I see that:16 input errors, 9 CRC. I think errors from service provider? because I alway use under 100 kps but still have some errors.
    Thanks very much,
    NhuongPham

    When you're able, schedule some downtime for this circuit, and have your provide do some loopback testing on an off-hours time. Simply open a trouble ticket with them, indicating that you're taking CRC errors at the customer-premisis-equipment. 16 input hours per day doesn't seem like alot, but it's still worth checking out, especially since your WAN provider should do this for free.

Maybe you are looking for

  • Quicktime Pro crashes when trying to save file

    I just quicktime pro, and so far it keeps crashing on me when I try to save a video file. Here are the steps: 1. Open a video file (m4v) 2. Overlay text on the first few seconds of the video 3. Save video 4. CRASH! I'm not sure if this helps, but I g

  • Driver for intel cs330 webcam on windows 7

    HI I have a great old webcam a Intel CS330, but i have just bought a new computer and its runing windows 7 and i cant seem to find a driver for it :( Could you please tell me where i may get this from if it is avalible or if it will be anytime soon.

  • Create Tab Groups not working

    I have just tried to follow the Help topic at https://support.mozilla.org/en-US/kb/what-are-tab-groups#w_how-do-i-create-a-tab-group, to create groups of tabs relating to same subject, ready to save the tab group as a Favourite/Bookmark. With the Tab

  • Activity Reports: What are anonymous users?

    Hi All I have created activity reports to monitor the number of hits in portal. It shows up 2 categories of users. One is Authenticated and the other is Anonymous. The number of Anonymous users in the report are too many, can you experts please expla

  • Import slides into Cap 3

    I'm working on a large project and the designer sends me their file, i have to add a quiz to it at the end so i normally import/slides from an existing one. The file is 10 meg, if i insert just one question slide (and results page) into my existing f