PVC Traffic Classes

After you configure the FRADs with the frame add command, PacketWise automatically creates classes and partitions for the PVCs it discovers on the FRADs it polls. It retrieves the serial interface name from the FRAD and creates a folder class under both /Inbound and /Outbound in the traffic tree. Then, it populates the folder with a child class for each PVC it detects.

Note: Do not remove or rename a FRAD folder in the class tree, as it is required to maintain the proper ordering of the PVC classes.

PacketWise automatically takes the following steps:

1. Creates a folder class for each FRAD interface using the following name format: <sysname>-<ifname>
   
   <sysname> is the FRAD's system name and <ifname> is the internal name of the FRAD serial interface.
   
   For example: /Inbound/frad1-Se1
   
   
2. Under each FRAD folder class, creates a child class for each PVC that exists on the given FRAD, using the following convention: PVC_xxx where xxx represents the DLCI value for the PVC.
   
   For example: /Inbound/frad1-Se1/PVC_100
   
   Matching rules are configured automatically, based on the IP routing tables in the FRAD.
   
   
3. If traffic discovery is turned on, PacketWise creates child classes under each PVC class for the applications and protocols it detects on that PVC.

The Inbound portion of a Frame Relay traffic tree might look something like this:

Inbound
   frad1-se1
     PVC_100
       HTTP
       FileMaker
       NetBIOS-IP
       ...(other classes)
     PVC_101
       HTTP
       POP3
       FTP
       Oracle-netv2
       NetBIOS-IP
       ...(other classes)
     PVC_102
       HTTP
       POP3
       MPEG-Audio
       Telnet
       NetBIOS-IP
       ...(other classes)
    frad2-se2
      PVC_103
        HTTP
        POP3
        NetBIOS-IP
        ...(other classes)
      PVC_104
        HTTP
        POP3
        NetBIOS-IP
        ...(other classes)

PacketGuide™ for PacketWise® 7.4