Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

No index entries found.

Network Files


Interface Traffic (Ingress or Egress)


To use IP/MPLSView interface files as the trending input, select Traffic > Trending > Network Files > Interface Traffic (Ingress) or Interface Traffic (Egress). These files list period-by-period ingress or egress traffic per interface.

In order to use these files, they must first have been loaded into your network project. To do so, select File > Load Network Files, select the Traffic tab, and press the ingress or egress buttons, respectively. Typically a user only specify one of these.

The file format is as follows:

NodeID Interface Direction - Period1 Period2 ... PeriodN
MYNODE1 POS0/1 A2Z 0 100200112 100601536 100400624 100601536

An alternative file format for interface traffic is:

LinkName Direction - Period1 Period2 ... PeriodN
MYLINK1 A2Z - 100200112 100601536 100400624 100601536
MYLINK1 Z2A - 5003683 5003822 5284499 683344

The units for the period data should be in bits per second.

Note: The NodeID must match the ID or name of one of the nodes in the muxloc file.


Trafficload (Demand, NCP, ...)


To use IP/MPLSView trafficload files as the trending input, select Traffic > Trending > Network Files > Demand Trafficload. These files list period-by-period traffic per demand.

In order to use these files, they must first have been loaded into your network project. To do so, select File > Load Network Files, Traffic tab, and press the “trafficload” button.

The file format is as follows:

DemandID Direction - Period1 Period2 etc…
MYDMD A2Z - 100200112 100601536 100400624 100601536

Or, for those with Node-Card-Port (NCP) data:
FromNodeCardPort Direction - Period1 Period2 etc… ToNodeCardPort Direction - Period1 Period2 etc… MYNODE.P3C5 A2Z - 100200112 100601536 100400624 100601536

Tunnel Trafficload (IP/MPLS only)


To use IP/MPLSView tunnel trafficload files as the trending input, select Traffic > Trending > Network Files > Tunnel Trafficload. These files list period-by-period traffic per LSP tunnel.

In order to use these files, they must first have been loaded into your network project. To do so, select File > Load Network Files, Device Specific tab, and press the trafficload button.

The file format is as follows:

NodeID:TunnelName Direction - Period1 Period2 etc…
MYNODE1:MYTUNNEL290 A2Z - 100200112 100601536 100400624 100601536

Peak Link Traffic


To use peak link traffic load files as the trending input, run an exhaustive single element failure from Simulation > Predefined Scenarios on a network with a trafficload file, which contains the period-by-period traffic per demand. For example, the sample fish network (/u/wandl/sample/IP/fish/spec.mpls-fish) could be used to generate a peak link traffic load since the specification file references a trafficload file with the period-by-period traffic per demand. After the failure simulation is complete, a file named PeakLinkLoad.< runcode> is created, which indicates for a particular link and a particular period, what was the worst link load experienced for that link, taking into consideration all of the single element failure simulations that were simulated on the network.

The file format is as follows:

Node,Interface,Dir,Peak_1,Peak_2,Peak_3,Peak_4,Peak_5,Peak_6,Peak_7,Peak_8,Peak_9,Peak_10,
ATL,LINK1,A2Z,25952066,31141680,36327296,36327296,41518908,46707684,46707684,36327296,31141680,25952066,

Load the file using Traffic > Trending > Network Files > Peak Link Traffic.

Modified: 2016-01-05