Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

parse JunOS SRX logs without a source NAT rule name #284

Merged
merged 2 commits into from
Dec 11, 2018
Merged

parse JunOS SRX logs without a source NAT rule name #284

merged 2 commits into from
Dec 11, 2018

Conversation

inetAnt
Copy link
Contributor

@inetAnt inetAnt commented Dec 3, 2018

It appears that some logs may not have a source NAT rule name defined.
When this is the case, 'source rule RULE' is replaced by 'N/A N/A'.

parse JunOS SRX logs without a source NAT rule name
5770ccd 
It appears that some logs may not have a source NAT rule name defined.
When this is the case, 'source rule RULE' is replaced by 'N/A N/A'.
@coveralls
Copy link

coveralls commented Dec 3, 2018 •
edited
Loading

Coverage Status

Coverage remained the same at 43.037% when pulling 5770ccd on inetAnt:junos_srx_no_src_lan into 5883f19 on napalm-automation:develop.

@mirceaulinic mirceaulinic added this to the 0.8.0 milestone Dec 11, 2018
@mirceaulinic mirceaulinic merged commit 9109834 into napalm-automation:develop Dec 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
bug junos message
Projects
None yet
Milestone
0.8.0
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@inetAnt @coveralls @mirceaulinic